hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.6.3 Test coverage | CRR number Test case number N1 1 C1 5, 6 C2 - C3 7 C4 8 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.6.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Normal call writeStatusCode(200) appendHeaderVariable( headerKeywordNameId= 1, value= [header1header2], valueOffset= 0, valueLength= 7) finalizeHeader(); appendContent([OK],0,2); flush(); HTTPResponse ( statusCode= "200" Header("Accept")= "... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.7.1 Conformance Requirement | The method with following header shall be compliant to its definition in the API. void flush() ETSI ETSI TS 102 835 V8.1.0 (2012-03) 60 (Release 8) 6.1.5.7.1.1 Normal execution • CRRN1: Sends all data contained in the HTTP response. • CRRN2: If this method is invoked in fixed buffer mode after a previous invocation of ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.7.2 Test area files | Specific triggering: None: Test Source: Test_Api_1_Hrs_Flus.java. Test Applet: Api_1_Hrs_Flus_1.java. Cap File: Api _1_Hrs_Flus.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.7.3 Test coverage | CRR number Test case number N1 1, 2, 3, 5 N2 2 N3 6 N4 4 C1 - |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.7.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Normal case + Chunk off writeStatusCode(200) finalizeHeader(); appendContent([OK],0,2); flush(); HTTPResponse ( statusCode= "200" Header("Content-Length")= "2" contentBody= "OK" ) 2 Repeat flush + chunk off writeStatusCode(200) finalizeHead... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.8.1 Conformance Requirement | The method with following header shall be compliant to its definition in the API. int getRemainingResponseBufferSize() 6.1.5.8.1.1 Normal execution • CRRN1: Returns the remaining size of the Response Buffer available for this applet. • CRRN2: The size returned by this method is guaranteed until the next header data is ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.8.2 Test area files | Specific triggering: None: Test Source: Test_Api_1_Hrs_Grrs.java. Test Applet: Api_1_Hrs_Grrs_1.java. Cap File: Api_1_Hrs_Grrs.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.8.3 Test coverage | CRR number Test case number N1 1, 2, 3 N2 3 N3 1 N4 2 C1 4 C2 5 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.8.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Remaining content data writeStatusCode(200) finalizeHeader() remaining = getRemainingResponseBufferSize(); appendContent( data = [aaa...] offset = 0 length = remaining ) flush() HTTPResponse ( statusCode= "200" Header("Content-Length")= rem... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.9.1 Conformance Requirement | The method with following header shall be compliant to its definition in the API. void reset() throws ScwsException 6.1.5.9.1.1 Normal execution • CRRN1: Clears the Response Buffer content. • CRRN2: Reset the state of the HttpResponse Object to its initial state. • CRRN3: All the header variables and content that was a... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.9.2 Test area files | Specific triggering: None: Test Source: Test_Api_1_Hrs_Rset.java. Test Applet: Api_1_Hrs_Rset_1.java. Cap File: Api_1_Hrs_Rset.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.9.3 Test coverage | CRR number Test case number N1 1, 2, 3 N2 1, 2, 3 N3 1, 2, 3 C1 6 C2 7 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.9.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Reset StatusCode writeStatusCode(204) reset(); HTTPResponse ( statusCode= "200" Header("Content-Length")= "2" contentBody = "OK" ) writeStatusCode(200); finalizeHeader(); appendContent([OK],0, 2); flush(); 2 Reset Header writeStatusCode(500... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.10.1 Conformance Requirement | The method with following header shall be compliant to its definition in the API. void sendError(short errorCode) 6.1.5.10.1.1 Normal execution • CRRN1: Sends an error code to the SCWS. • CRRN2: The HTTP response is sent immediately by the SCWS no other data is send by the SCWS. • CRRN3: Missing header variables are ad... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.10.2 Test area files | Specific triggering: None: Test Source: Test_Api_1_Hrs_Sene.java. Test Applet: Api_1_Hrs_Sene_1.java. Cap File: Api_1_Hrs_Sene.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.10.3 Test coverage | CRR number Test case number N1 1, 2, 3, 4, 5, 6 N2 1, 2, 3, 4, 5, 6 N3 1, 2, 3, 4, 5, 6 N4 1, 2, 3, 4, 5, 6 P1 7 C1 8, 9 C2 10 C3 11 ETSI ETSI TS 102 835 V8.1.0 (2012-03) 67 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.10.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Normal use case : Return an Informational code (1xx) a // SC_CONTINUE sendError(100) Not testable b // SC_SWITCHING_PROTOCOLS sendError(101) Not testable 2 Normal use case : Return a Successful code (2xx) a // SC_OK sendError(200) HTTPRespo... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.11.1 Conformance Requirement | The method with following header shall be compliant to its definition in the API. void setContentType(short type) throws ScwsException 6.1.5.11.1.1 Normal execution • CRRN1: Sets the content type of the HTTP response. 6.1.5.11.1.2 Parameter Errors • CRRP1: if parameter type is not correct according to SCWSConstants, a ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.11.2 Test area files | Specific triggering: None: Test Source: Test_Api_1_Hrs_Scot.java. Test Applet: Api_1_Hrs_Scot_1.java. Cap File: Api_1_Hrs_Scot.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.11.3 Test coverage | CRR number Test case number N1 1, 2, 3, 4, 5 P1 6 C1 7, 8 C2 - C3 9 C4 10 ETSI ETSI TS 102 835 V8.1.0 (2012-03) 71 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.11.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 All success type a // CONTENT_TYPE_IMAGE_GIF writeStatusCode(200) setContentType(4); finalizeHeader(); appendContent([OK],0,2); flush(); HTTPResponse ( statusCode= "200" Header("Content-Type")= "image/gif" Header("Content-Length")= "2" cont... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.12.1 Conformance Requirement | The method with following header shall be compliant to its definition in the API. void writeStatusCode(short code) throws ScwsException 6.1.5.12.1.1 Normal execution • CRRN1: Write an HTTP status code into the outgoing buffer. 6.1.5.12.1.2 Parameter Errors • CRRP1: if parameter code is unknown with respect to the HTTP ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.12.2 Test area files | Specific triggering: None: Test Source: Test_Api_1_Hrs_Wstc.java. Test Applet: Api_1_Hrs_Wstc_1.java. Cap File: Api_1_Hrs_Wstc.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.12.3 Test coverage | CRR number Test case number N1 1, 2, 3, 4, 5, 12 P1 6 C1 7 C2 8 C3 9 C4 10 C5 11 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.12.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Normal use case : Return a basic page with an Informational status code (1xx) a // SC_CONTINUE writeStatusCode(100) Not testable b // SC_SWITCHING_PROTOCOLS writeStatusCode(101) Not testable 2 Normal use case : Return a basic page with a Su... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2 SCWS Runtime Environment | |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1 Applet state | 6.2.1.1 Invokation of applets not in state selectable Test Area Reference: Api_2_Aps_Ivns. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.1.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.3): • Only an Applet that is in selectable state can be invoked by the SCWS. ETSI ETSI TS 102 835 V8.1.0 (2012-03) 79 (Release 8) 6.2.1.1.1.1 Normal execution • CRRN1: Only an applet in selectable state can be invo... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.1.2 Test area files | Specific triggering: Unrecognized envelope: Test Source: Test_Api_2_Aps_Ivns.java. Test Applet: Api_2_Aps_Ivns_1.java. Cap File: Api_2_Aps_Ivns.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.1.3 Test coverage | CRR number Test case number N1, N2 1 N1, N2 2 N1, N2 3 N1, N2 4 N1, N2 5 N1, N2 6 N1, N2 7 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.1.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Invoke an applet LOCKED / UNLOCKED with HTTP methods: POST 1. Send POST HTTP REQUEST (1) to Api_2_Aps_Ivns_1 2. Lock the applet Api_2_Aps_Ivns_1 (non selectable state) 3. Send POST HTTP REQUEST (2) to Api_2_Aps_Ivns_1 4. Unlock the applet A... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.2.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588, clause 4.2): • If the Applet is in a non selectable state, its registration to the SCWS is still valid. ETSI ETSI TS 102 835 V8.1.0 (2012-03) 82 (Release 8) 6.2.1.2.1.1 Normal execution • CRRN1: If the Applet is in a non select... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.2.2 Test area files | Specific triggering: Unrecognized envelope Test Source: Test_Api_2_Aps_Regv.java. Test Applet: Api_2_Aps_Regv_1.java. Cap File: Api_2_Aps_Regv.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.2.3 Test coverage | CRR number Test case number N1 1 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.2.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation Map an applet in non selectable state 1. Register Api_2_Aps_Regv_1 to SCWS 2. Lock the applet Api_2_Aps_Regv_1 (non selectable state) 3. Map the Api_2_Aps_Regv_1 (1) 4. Unlock the applet Api_2_Aps_Regv_1 ( selectable state) 5. Send a HTTP REQ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.2 Response sending | All tests regarding sending of a response are implicitely covered by the test cases in clause 6.1.5. ETSI ETSI TS 102 835 V8.1.0 (2012-03) 83 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.3 Exception handling | 6.2.3.1 No exception shall be propagated as HTTP error to the terminal Test Area Reference: Api_2_Exh_Noex. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.3.1.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.4): • Exceptions thrown by the invoked Applet shall not be propagated to the terminal, and the SCWS shall send an error status code according to HTTP 1.1[1]. In case of "chunked mode", some response data could have... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.3.1.2 Test area files | Specific triggering: Unrecognized envelope: Test Source: Test_Api_2_Exh_Noex.java. Test Applet: Api_2_Exh_Noex_1.java. Cap File: Api_2_Exh_Noex.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.3.1.3 Test coverage | CRR number Test case number N1 1 N2 2 N3 3 ETSI ETSI TS 102 835 V8.1.0 (2012-03) 84 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.3.1.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Applet throws an exception Byte[] array = new byte[2] Array[3] = 0x00; java.lang. ArrayIndexOutOfBoundsException is thrown HTTPResponse ( statusCode = "500" ) 2 In "chunked mode", applet throws an Exception AFTER writeStatusCode () enableCh... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.4 Response Header Management | 6.2.4.1 Send status code indicating success Test Area Reference: Api_2_Rhm_Scis. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.4.1.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.5): • The following headers shall be added by the SCWS if not provided by the application: - Status line, indicating success status (200 – OK or 204 – No Content) 6.2.4.1.1.1 Normal execution • CRRN1 : If an Applet... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.4.1.2 Test area files | Specific triggering: Unrecognized envelope: Test Source: Test_Api_2_Rhm_Scis.java. Test Applet: Api_2_Rhm_Scis_1.java. Cap File: Api_2_Rhm_Scis.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.4.1.3 Test coverage | CRR number Test case number N1 1 N2 2 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.4.1.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Invoke an applet that returns data finalizeHeader(); appendContent([OK], 0, 2); flush(); HTTPResponse( statusCode= 200 Content-Length: 2 contentBody= "OK" ) 2 Invoke an applet that returns no data finalizeHeader(); flush(); HTTPResponse( st... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5 Availability of ProactiveHandler / ProactiveResponseHandler | 6.2.5.1 Incoming Http request Test Area Reference: Api_2_Pro_Inhr. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.1.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.6). The ProactiveHandler shall be available for applets that are invoked by an incoming Http request (i.e. by one of the methods doGet(), doPost(), doDelete(), doHead(), doOptions(), doPut(), and doTrace()) in the ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.1.2 Test area files | Specific triggering: Unrecognized envelope: Test Source: Test_Api_2_Pro_Inhr.java. Test Applet: Api_2_Pro_Inhr_1.java. Cap File: Api_2_Pro_Inhr.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.1.3 Test coverage | CRR number Test case number N1 1 – 7 ETSI ETSI TS 102 835 V8.1.0 (2012-03) 87 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.1.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Applet is triggered by doGet() Get reference to the ProactiveHandler. Invocation of ProactiveHandler.getCapacity() returns a value greater than 0. HTTPResponse ( statusCode = "200" ) 2 Applet is triggered by doPost() Get reference to the Pr... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.2.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.6). If available, the ProactiveHandler shall be available for these applets until they have sent the complete Http response to the SCWS. 6.2.5.2.1.1 Normal execution • CRRN1: In chunked mode, retrieve a reference t... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.2.2 Test area files | Specific triggering: Unrecognized envelope: Test Source: Test_Api_2_Pro_Avco.java. Test Applet: Api_2_Pro_Avco_1.java. Cap File: Api_2_Pro_Avco.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.2.3 Test coverage | CRR number Test case number N1 1 N2 2 N3 3 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.2.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Get reference to the ProactiveHandler in chunked mode. Data appended to the HttpResponsebuffer before invocation of ProactiveHandler is sent in the http response. Prov.Loc.Info(IMEI) HTTPResponse ( Content complete statusCode = "200" ) 2 Ge... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.3.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.6). The availability of the ProactiveResponseHandler shall depend on the availability of the ProactiveHandler as defined in TS 102 241 [12], except that it is available until the termination of the method that was ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.3.2 Test area files | • n/a. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.3.3 Test coverage | • n/a. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.3.4 Test procedure | • n/a. 6.2.5.4 Triggering through the ToolkitInterface Test Area Reference: Api_2_Pro_Tool. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.4.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.6). Applets implementing the ToolkitInterface as defined in TS 102 241 [12] in addition to the SCWS interface will be triggered in the processToolkit() method upon reception of any Toolkit event. 6.2.5.4.1.1 Normal... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.4.2 Test area files | Specific triggering: Unrecognized envelope: Test Source: Test_Api_2_Pro_Tool.java. Test Applet: Api_2_Pro_Tool_1.java. Cap File: Api_2_Pro_Tool.cap. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.4.3 Test coverage | CRR number Test case number N1 1 ETSI ETSI TS 102 835 V8.1.0 (2012-03) 90 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.4.4 Test procedure | Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation 1 Applet is triggered by doGet() Register to EVENT_PROACTIVE_HANDLER_AVAILABLE. When applet is triggered in processToolkit() set a flag. Trigger applet again by goGet() and check if flag is set. Applet is triggerd in processToolkit() after re... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.5.1 Conformance Requirement | The SCWS Framework implementation shall be compliant to the following statement (TS 102 588 [2], clause 4.6): Implementation dependent on a central CAT_TP multiplexing application as defined in TS 102 225 [14] may be present in the card. It must not block the ProactiveHandler when an applet is invoked by an incoming Ht... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.5.2 Test area files | • n/a. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.5.3 Test coverage | • n/a. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.5.4 Test procedure | • n/a. ETSI ETSI TS 102 835 V8.1.0 (2012-03) 91 (Release 8) Annex A (normative): Class, methods and SCWSFramework tests acronyms A.1 Smart Card Web Server part ScwsExtensionRegistry Ser ScwsExtension Set ScwsExtensionService Ses HttpRequest Hrq HttpResponse Hrs A.1.1 Class ScwsExtensionRegistry Method name Acronyms sta... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 1 Scope | The present document specifies the File Format used to store and playback DVB services. The audio/video properties of the services that may be contained in this format are defined by specifications TS 101 154 [3] for MPEG-2 Systems services, and TS 102 005 [4] for RTP carried elementary stream services. The present doc... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 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... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems". [2] ETSI TS 101 162: "Digital Video Broadcasting (DVB); Allocation of identifiers and codes for Digital Video ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 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. Not applicable. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 3 Definitions and abbreviations | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 14496-12 [30], ISO/IEC 13818-1 [27] and the following apply: descriptive metadata: metadata which carries descriptions of the content that is useful to a human NOTE: This is also sometimes referred to as "attractor" or "attractor metad... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project 4CC Four Character Code AC-3 Dolby AC-3 audio coding system NOTE: According to TS 102 366 [6]. AMR-WB+ Adaptive MultiRate WideBand+ AVC Advanced Video Coding NOTE: See also H.264/AVC [37]. BCG Broadband ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4 Use of the DVB File Format | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.1 File identification | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.1.1 File extension | The extension 'dvb' shall be used for files where the major brand is one of the DVB File Format brands as specified in clause 4.2. Readers should allow mixed case for the characters in the extension. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.1.2 MIME types | See annex A. ETSI ETSI TS 102 833 V1.2.1 (2011-03) 14 |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.1.3 Brands | A DVB file shall have the file type box 'ftyp' at the beginning. If the file type box is not present at the beginning of a file, it shall be assumed that this file was not generated according to the present document. NOTE: If the file type box is present at the beginning, a reader should parse it first and decide depen... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.2 Branding | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.2.1 General | Brands are indicated in the file type box 'ftyp', defined in clause 4.3 of ISO/IEC 14496-12 [30], which shall be present in conforming files. The fields of the file type box shall be used as follows. major_brand identifies the "best use" of the file and should match the file extension. For files with extension '.dvb' a... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.2.2 Common constraints for all DVB brands | The following constraints shall be followed in all DVB files regardless of which DVB brands are listed. For all brands defined within the present document: • The size of 'moov' box shall be less than or equal to 1 Mbyte. • The size of any 'moof' box shall be less than or equal to 300 kbyte. NOTE 1: These size limits al... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.2.3 The 'dvt1' brand | The four-character code 'dvt1' is used for the DVB Transport Stream brand. Either the major brand or one of compatible brands shall be 'dvt1' in DVB file recordings from a transmission conforming to TS 101 154 [3]. Files including the 'dvt1' brand shall be constrained as follows: • There shall be at least one MPEG2-TS ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.2.4 The 'dvr1' brand | The four-character code 'dvr1' is used for the DVB RTP brand. Either the major brand or one of compatible brands shall be 'dvr1' in DVB file recordings from a transmission conforming to TS 102 005 [4]. Files including the 'dvr1' brand shall be constrained as follows: • There shall be no references to external data outs... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.2.5 Use of branding | Every DVB file shall contain the compatible brand 'iso3' as defined in ISO/IEC 14496-12 [30], which indicates that each DVB file is conformant to the third edition of the ISO base media file format. When media tracks are present, the brand corresponding to the media format shall be present in the list of compatible bra... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.3 Overview of newly introduced boxes | The present document defines the new boxes listed in table 4. Also, a number of existing boxes of the ISO base media file format are extended. Table 4: New boxes defined in the present document Box description Clause dstg DVB sample to group box 5.3.4.2 dsgd DVB sample group description box 5.3.4.3 srmc System Renewabi... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 4.4 Overview of new track types | The present document specifies the new sample entries for track types used in the present document, listed in table 5. Table 5: Track types defined in the present document Index Index description Clause mlix Movie-level index track 5.3.2.1.3 ixse DVB serial index track 5.3.3.2 keym Key Message reception track 5.4.2.2 |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5 Box definitions and usage | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1 Descriptive metadata | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.1 Introduction | The DVB File Format stores content related, descriptive or annotative metadata in common file format structures, agnostic to the actual metadata schema(s) used. In this clause, the storage mechanism for such metadata is described. A metadata schema for storing a minimal mandatory description is defined. Furthermore, th... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2 Usage of metadata box | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.1 Overview | The metadata box 'meta' (defined in clause 8.11.1 of ISO/IEC 14496-12 [30]) serves as the main entry point for descriptive metadata. Exactly one metadata box shall occur at file level, called the primary metadata box. Additional metadata boxes referencing descriptive metadata defined in the present document shall only ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.2 Handler reference box | The handler type specified in the mandatory handler reference box 'hdlr' of a metadata box defines the format, encoding and interpretation of the descriptive metadata items referenced from that metadata box. Table 6 lists the formats defined and supported by the DVB File Format. Table 6: Handler types of a metadata box... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.2.1 TV-Anytime descriptive metadata | Descriptive metadata items with a handler type of 'dtva' shall adhere to the TV-Anytime DVB profile, as defined in clause 8 of TS 102 323 [5], and shall be stored as a textual, schema-valid, XML document, as detailed in clause 5.1.2.6. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.2.2 IPDC ESG descriptive metadata | Descriptive metadata items with a handler type of 'ipdc' shall adhere to TS 102 471 [7] and shall be stored as a textual, schema-valid, XML document, as detailed in clause 5.1.2.6. ETSI ETSI TS 102 833 V1.2.1 (2011-03) 20 |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.2.3 BCG descriptive metadata | The format of descriptive metadata items in the Broadband Content Guide (BCG) metadata as defined in TS 102 539 [10] is identical to that of TV-Anytime metadata and so shall be stored as described in clause 5.1.2.2.1. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.2.4 Proprietary descriptive metadata | If a metadata box has a handler type of 'uri', this metadata box shall contain a URI box 'uri' that identifies the type and the interpretation of the descriptive metadata items referenced from that metadata box. The URI mechanism shall be used to provide proprietary extensions. If desired, a UUID may be encoded into th... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.2 Primary item box | Each metadata box shall contain a primary item box 'pitm', defined in clause 8.11.4 of ISO/IEC 14496-12 [30]. The primary item box shall identify the item that contains the main descriptive metadata element. This shall be the default descriptive metadata item. NOTE: The choice of which item is indicated by the primary ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.1.2.3 Data information box | The data information box 'dinf' shall not be present in a metadata box with a handler type defined in the present document. NOTE: This implies that the descriptive metadata for a handler type defined in the present document is contained within the same file. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.