hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.2.3.4.2 Butterfly authorization request | TP Id SECPKI_ITS-S_ BFK_AUTH_01_BV Summary Check that the ITS-S sends the EtsiTs103097Data to the Enrolment Authority (EA) to request a batch of authorization tickets Check that this message is encrypted and addressed to a single recipient. Reference ETSI TS 102 941 [1], clause 6.2.3.5.1 Configuration CFG_BFK_AUTH_ITS-... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.2.4 CTL handling | TP Id SECPKI_ITS-S_CTL_01_BV Summary Check that the IUT trusts the new RCA from the received ECTL Reference ETSI TS 102 941 [1], clause 6.3.5 Configuration CFG_CXL_P2P PICS Selection Expected behaviour with the IUT does not trust the CERT_RCA_NEW and the IUT has received the TLM CTL containing the CERT_RCA_NEW ensure t... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.2.5 CTL distribution | All test purposes in this clause may be included in the test sequence if following PICS items are set: PICS_SECPKI_ECTL_BROADCAST = TRUE or PICS_SECPKI_CTL_BROADCAST = TRUE TP Id SECPKI_ITS-S_CTLDIST_01_BV Summary Check that the IUT retransmits the newly received Delta CTL Reference ETSI TS 103 601 [6], clause 4.2.1.4 ... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.2.6 CRL handling | TP Id SECPKI_ITS-S_CRL_01_BV Summary Check that the IUT accept the received CRL information Reference ETSI TS 102 941 [1], clause 5.4.2 Configuration CFG_CXL_P2P PICS Selection Expected behaviour with the IUT contains valid RootCA certificate (CERT_IUT_A_RCA) and the IUT has not received yet the CRL information issued ... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.2.7 CRL distribution | TP Id SECPKI_ITS-S_CRLDIST_01_BV Summary Check that the IUT starts broadcasting the CRL using P2P protocol when CRL information is received Reference ETSI TS 103 601 [6], clause 5.4.2 Configuration CFG_CXL_P2P PICS Selection UC-SEC-07.2 Expected behaviour with the IUT is configured to support P2P CRL distribution and t... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3 Common CA behaviour | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.0 Overview | All test purposes in the present clause may be included in the test sequence if one of the following PICS items are set: PICS_SECPKI_IUT_RCA = TRUE; or PICS_SECPKI_IUT_AA = TRUE; or PICS_SECPKI_IUT_EA = TRUE. ETSI ETSI TS 103 525-2 V2.1.1 (2024-09) 55 |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1 Certificate validation | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.1 Basic certificate content | TP Id SECPKI_CA_CERTGEN_01_BV Summary Check that the issuing certificate has version 3 Reference ETSI TS 103 097 [2], clause 6 IEEE Std 1609.2™ [3], clause 6.4.3 PICS Selection PICS_GN_SECURITY Expected behaviour with CA is in 'operational' state ensure that when the CA is requested to issue the certificate then this c... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.2 Check certificate region validity restriction | TP Id SECPKI_CA_CERTGEN_05_BV Summary Check that the CA is able to issue the certificate with the well-formed circular region validity restriction Reference IEEE Std 1609.2™ [3], clauses 6.4.20, 6.4.17 and 5.1.2.4 PICS Selection PICS_GN_SECURITY AND PICS_SEC_CIRCULAR_REGION Expected behaviour with CA is in 'operational... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.3 Check ECC point type of the certificate signature | TP Id SECPKI_CA_ CERTGEN_10_BV_XX Summary Check that the certificate signature contains ECC point of type set to either compressed_lsb_y_0, compressed_lsb_y_1 or x_coordinate_only Reference IEEE Std 1609.2™ [3], clauses 6.3.29, 6.3.30 and 6.3.31 PICS Selection PICS_GN_SECURITY AND PICS_SEC_EXPLICIT_CERTIFICATES AND X_P... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.4 Check ECC point type of the certificate public keys | TP Id SECPKI_CA_CERTGEN_11_BV Summary Check that the certificate verification key contains ECC point of type set to either compressed_lsb_y_0, compressed_lsb_y_1 or uncompressed Reference IEEE Std 1609.2™ [3], clause 6.4.38 PICS Selection PICS_GN_SECURITY AND PICS_SEC_EXPLICIT_CERTIFICATES AND X_PICS Expected behaviour... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.5 Verify certificate signatures | TP Id SECPKI_CA_CERTGEN_13_BV_01 Summary Check the explicit certificate signature Reference ETSI TS 103 097 [2], clause 6 PICS Selection PICS_GN_SECURITY AND PICS_SEC_EXPLICIT_CERTIFICATES AND X_PICS Expected behaviour with the CA is in 'operational' state and the CA is authorized with explicit certificate containing t... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.6 Verify certificate permissions | TP Id SECPKI_CA_CERTGEN_14_BV Summary Check that all PSID entries of the appPermissions component of the certificate are unique Reference IEEE Std 1609.2™ [3], clauses 6.4.28 and 5.1.2.4 PICS Selection PICS_GN_SECURITY Expected behaviour with the CA is in 'operational' state ensure that when the CA issued the certifica... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.3.1.7 Check time validity restriction in the chain | TP Id SECPKI_CA_CERTGEN_18_BV Summary Check that the validityPeriod of the subordinate certificate is inside the validityPeriod of the issuing certificate Reference IEEE Std 1609.2™ [3], clause 5.1.2.4 PICS Selection PICS_GN_SECURITY Expected behaviour with the CA is in 'operational' state and the CA is authorized with... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4 EA behaviour | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.0 Overview | All test purposes in the present clause may be included in the test sequence if the following PICS items is set: PICS_SECPKI_IUT_EA = TRUE |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.1 Enrolment request handling | TP Id SECPKI_EA_ENR_RCV_01_BV Summary The EnrollmentResponse message shall be sent by the EA to the ITS-S across the interface at reference point S3 in response to a received EnrollmentRequest message Reference ETSI TS 102 941 [1], clause 6.2.3.2.2 Configuration CFG_ENR_EA PICS Selection Expected behaviour with the EA ... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.2 Enrolment response | TP Id SECPKI_EA_ENR_01_BV Summary The EnrollmentResponse message shall be encrypted using an ETSI TS 103 097 [2] approved algorithm and the encryption shall be done with the same AES key as the one used by the ITS-S requestor for the encryption of the EnrollmentRequest message Reference ETSI TS 102 941 [1], clause 6.2.... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.3 Authorization validation request handling | TP Id SECPKI_EA_AUTHVAL_RCV_01_BV Summary The authorization validation response shall be sent by the EA to the AA across the interface at reference point S4 in response to a received AuthorizationValidationRequestMessage Reference ETSI TS 102 941 [1], clause 6.2.3.4.2 Configuration CFG_AVALID_EA PICS Selection Expected... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.4 Authorization validation response | TP Id SECPKI_EA_AUTHVAL_01_BV Summary The EtsiTs103097Data-Encrypted is built with the component recipients containing one instance of RecipientInfo of choice pskRecipInfo, which contains the HashedId8 of the symmetric key used by the ITS-S to encrypt the authorization request to which the response is built and the com... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.6 Authorization using butterfly key expansion mechanism | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.6.1 Butterfly authorization response | TP Id SECPKI_EA_BFK_AUTH_01_BV Summary Check that the EA sends the butterfly authorization respond message after receiving of the butterfly authorization request Check that this message is signed with EA certificate Reference ETSI TS 102 941 [1], clauses 6.2.3.5.1 and 6.2.3.5.3 Configuration CFG_BFK_AUTH_EA PICS Select... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.6.2 Butterfly certificate request | TP Id SECPKI_EA_BFK_AUTH _03_BV Summary Check that the EA sends butterfly certificate request message after receiving of the butterfly authorization request Check that this message is encrypted for the AA Check that this message is signed with the EA certificate Reference ETSI TS 102 941 [1], clause 6.2.3.5.4 Configura... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.4.6.3 Authorization certificate download | TP Id SECPKI_EA_BFK_AUTH_06_BV Summary Check that the butterfly certificate request message sent by EA to AA contains all required elements Reference ETSI TS 102 941 [1], clause 6.2.3.5.4 Configuration CFG_BFK_AUTH_EA PICS Selection Expected behaviour with the EA in 'operational' state authorized with CERT_EA certifica... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5 AA behaviour | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.0 Overview | All test purposes in the present clause may be included in the test sequence if the following PICS items is set: PICS_SECPKI_IUT_AA = TRUE ETSI ETSI TS 103 525-2 V2.1.1 (2024-09) 93 |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.1 Authorization request handling | TP Id SECPKI_AA_AUTH_RCV_01_BV Summary Check that the AA is able to decrypt the AuthorizationRequestMessage using the encryption private key corresponding to the recipient certificate Check that the AA is able to verify the inner signature Check that the AA is able to verify the request authenticity using the hmacKey v... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.2 Authorization validation request | TP Id SECPKI_AA_AUTHVAL_01_BV Summary Check that the AA sends authorization validation request after receiving of the authorization request Reference ETSI TS 102 941 [1], clause 6.2.3.4.1 Configuration CFG_AUTH_AA PICS Selection Expected behaviour with the EA in 'operational' state authorized with CERT_EA certificate e... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.3 Authorization validation response handling | TP Id SECPKI_AA_AUTHVAL_RCV_01_BV Summary Check that the AA sends the authorization response after receiving the AuthorizationRequestMessage Reference ETSI TS 102 941 [1], clause 6.2.3.3.2 Configuration CFG_AUTH_AA PICS Selection Expected behaviour with the ITS-S in 'enrolled' state the EA in 'operational' state and th... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.4 Authorization response | TP Id SECPKI_AA_AUTH_01_BV Summary Check that the AA sends encrypted authorization response Reference ETSI TS 102 941 [1], clause 6.2.3.3.2 Configuration CFG_AUTH_AA PICS Selection Expected behaviour with the ITS-S in 'enrolled' state has sent the AuthorizationRequestMessage containing encrypted enkKey containing AES s... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.5 CA Certificate Request | TP Id SECPKI_AA_CERTGEN_01_BV Summary SubCA certificate requests of the AA are transported to the RCA using CACertificateRequestMessage structures across the reference point S9 Reference ETSI TS 102 941 [1], clause 6.2.1 Configuration CFG_CAGEN_INIT PICS Selection Expected behaviour ensure that when the IUT is requeste... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.6 Authorization using butterfly key expansion mechanism | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.5.6.1 Butterfly certificate response | TP Id SECPKI_AA_BFK_AUTH_01_BV Summary Check that the AA sends the butterfly certificate response message after receiving of the butterfly certificate request Check that this message is encrypted using the same symmetric encryption key as the butterfly certificate request message Reference ETSI TS 102 941 [1], clauses ... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.6 RootCA behaviour | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.6.0 Overview | All test purposes in the present clause may be included in the test sequence if the following PICS items is set: PICS_SECPKI_IUT_RCA = TRUE |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.6.1 CTL generation | For the scope of test purposes of this clause, the EtsiTs103097Data and EtsiTs102941Data envelopes are already removed from the analysing messages if it is not explicitly specified in the test purpose. ETSI ETSI TS 103 525-2 V2.1.1 (2024-09) 121 TP Id SECPKI_RCA_CTLGEN_01_BV Summary Check that the RootCA generates the ... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.6.2 CRL generation | For the scope of test purposes of this clause, the EtsiTs103097Data and EtsiTs102941Data envelopes are already removed from the analysing messages if it is not explicitly specified in the test purpose. TP Id SECPKI_RCA_CRLGEN_01_BV Summary Check that the RootCA generates the CRL signed with appropriate certificate Refe... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.6.3 CA certificate generation | TP Id SECPKI_RCA_CAGEN_01_BV Summary Check that generated EA certificate contains only allowed permissions Reference ETSI TS 102 941 [1], clause B.5 Configuration CFG_CAGEN_RCA PICS Selection Expected behaviour ensure that when the IUT is requested to generate EA certificate then the IUT generates the certificate conta... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.7 DC behaviour | TP Id SECPKI_DC_LISTDIST_01_BV Summary Check that the RCA CRL is published and accessible when issued Reference ETSI TS 102 941 [1], clause 6.3.3 Configuration CFG_DC PICS Selection Expected behaviour with the TLM issued a new CRL ensure that when the ITS-S asks the IUT for the newly issued CRL then the IUT is answered... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.8 TLM behaviour | |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.8.1 CTL generation | For the scope of test purposes of this clause, the EtsiTs103097Data and EtsiTs102941Data envelopes are already removed from the analysing messages if it is not explicitly specified in the test purpose. TP Id SECPKI_TLM_ECTLGEN_01_BV Summary Check that the TLM generates the ECTL when new RootCA is about to be added Refe... |
ac386ea431aa38648d9c09cd5eb11aa1 | 103 525-2 | 5.9 CPOC behaviour | TP Id SECPKI_CPOC_LISTDIST_01_BV Summary Check that the TLM CTL is published and accessible when issued Reference ETSI TS 102 941 [1], clauses 6.3.2 and 6.3.3 Configuration CFG_CPOC PICS Selection Expected behaviour with the TLM issued a new CTL ensure that when the ITS-S asks the IUT for the newly issued CTL then the ... |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the test specifications for security algorithms as specified in ETSI TS 102 941 [1] and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2] and ETSI ETS 300 406 [i.3]. |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 2 References | |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 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... |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 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... |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 3 Definition of terms, symbols and abbreviations | |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 941 [1] and ISO/IEC 9646-1 [i.1] apply. |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 3.2 Symbols | Void. |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 097 [2] and the following apply: CRL Certificate Revocation List PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement |
722a803326d5e00f1fc77635aba1d6ae | 103 525-1 | 4 Conformance | A PICS pro forma which conforms to this PICS pro forma specification shall be technically equivalent to annex A of the present document and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to the present document shall: a) describe an implementation which claims to conform to ETS... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 1 Scope | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, whi... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 2 References | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 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... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 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... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 3 Definition of terms, symbols and abbreviations | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 3.1 Terms | Void. |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 3.2 Symbols | Void. |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARGB Alpha-Red-Green-Blue CCC Car Connectivity Consortium HSML High Speed Media Link IN INput PC Personal Computer RGB Red-Green-Blue RLE (Scan-line based) Run Length Encoding UI User Interface UPnP Universal Plug and Play USB Universal Serial... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 4 Introduction | High Speed Media Link (HSML) is a screen out technology. The main purpose is to let mobile users project their phones' screens to a larger one, like the display inside a car infotainment system or PC, and users can control their phones via an automotive head unit or PC. With bigger screens, users can have much better u... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5 HSML USB Architecture | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.1 General | HSML is a USB function that can transfer display data efficiently. The figure below shows the USB architecture of HSML. Two pipes are established. The control pipe is used to send HSML specific requests. The framebuffer pipe is established for transmitting the uncompressed or compressed display data. The device and hos... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2 Functional Characteristics | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2.1 General | The MirrorLink Server shall support at least two functions: one is HSML and the other is CDC/NCM which is compliant with HSML. The MirrorLink Server shall include the HSML USB interface into the same USB configuration as the CDC/NCM USB interface. The HSML function is used for video transmission and the CDC/NCM is used... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2.2 Interface | The HSML interface shall be one of several interfaces the MirrorLink Server has in order to conform to the present document. |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2.3 Endpoints | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2.3.1 General | The device shall contain two endpoints: Ctrl (Default) and Bulk In (Framebuffer). |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2.3.2 Default | The default endpoint uses the control transfers as defined in the USB specification [3]. All the standard and vendor- specific requests are transmitted through this endpoint. The endpoint number shall be zero (0). |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.2.3.3 Framebuffer | This endpoint is used to receive the framebuffer data from the device. This endpoint shall use bulk transfers and the direction shall be IN. The maximum packet size for USB 2.0 shall be 512 bytes and for USB 3.0 shall be 1 024 bytes. |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.3 Vendor-Specific Codes | Table 1 defines the interface class, subclass and protocol used in the HSML interface descriptor. Table 1: Vendor-Specific Codes Fields Code Description Class 0xFF Vendor specific class Subclass 0xCC CCC Protocol 0x01 HSML To comply with the present document, the device should not have another USB vendor-specific inter... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.4 Interface Descriptor | The HSML interface descriptor is just like a standard USB interface descriptor, except some fields are dedicated to HSML as follows. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 10 Table 2: HSML Interface Descriptor Offset Fields Size (Bytes) Value Description 0 bLength 1 Number Size of this descriptor. (9 bytes) 1 bDescri... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.5 Endpoint Descriptors | The HSML interface requires 2 endpoints: one is default Control endpoint (endpoint 0), another is BULK IN endpoint as follows. Table 3: HSML Bulk IN Endpoint Descriptor Offset Fields Size Value Description 0 bLength 1 Number Size of this descriptor. (7 bytes) 1 bDescriptorType 1 Constant Endpoint descriptor (0x05) 2 bE... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6 HSML Requests | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.1 General | 5. |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.1 General | Table 4 lists all of the HSML specific requests that are valid for the HSML interface. Requests marked as "Yes" in the mandatory field shall be implemented by any conforming HSML device. Table 4: HSML Request List Request Code Mandatory Description GetVersion 0x40 Yes Get and provide HSML versions of the HSML source an... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.2 GetVersion | This request retrieves the maximum version that the device can support and tells the device which version the host can support at the same time. Table 5: GetVersion Request bmRequestType bRequestCode wValue wIndex wLength Data 11000001B 0x40 HSML Sink version The interface number 2 First byte: Major version of HSML sou... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.3 GetParameters | This request is used by the host to get the capabilities and configuration of the device. Table 6: GetParameters Request bmRequestType bRequestCode wValue wIndex wLength Data 11000001B 0x41 0 The interface number 16 HSML Parameter structure (see Table 7) ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 12 Below is the HSML par... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.4 SetParameters | This request is used to tell the device which configuration that the host wants to use. Table 8: SetParameters Request bmRequestType bRequestCode wValue wIndex wLength Data 01000001B 0x42 0 The interface number 12 HSML Configuration structure (see Table 9) ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 13 Below is the HSML c... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.5 StartFramebufferTransmission | This request asks the device to start sending framebuffer via the Bulk IN endpoint. Table 10: StartFramebufferTransmission Request bmRequestType bRequestCode wValue wIndex wLength Data 01000001B 0x43 0x0000: Streaming Mode 0x0001: On-Demand Mode The interface number 0 None The device will send the framebuffer continuou... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.6 PauseFramebufferTransmission | This request asks the device to pause framebuffer transmission via the Bulk IN endpoint. Table 11: PauseFramebufferTransmission Request bmRequestType bRequestCode wValue wIndex wLength Data 01000001B 0x44 0 The interface number 0 None The device shall stop any pending framebuffer transmissions when receiving this reque... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.7 StopFramebufferTransmission | This request stops the device from sending framebuffer at the streaming mode. Table 12: StopFramebufferTransmission Request bmRequestType bRequestCode wValue wIndex wLength Data 01000001B 0x45 0 The interface number 0 None The device shall cease all activities on the Bulk IN endpoint and clean all remaining data in the... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.8 SetMaxFrameRate | This request sets the upper bound of the device's frame rate. Table 13: SetMaxFrameRate Request bmRequestType bRequestCode wValue wIndex wLength Data 01000001B 0x46 Maximum frames per second The interface number 0 None The frame rate is defined as 1 s divided by the number of framebuffer updates. The device should send... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 5.6.9 GetIdentifier | This request can be used to identify multiple HSML devices when they are all connected to the same host. Table 14: GetIdentifier bmRequestType bRequestCode wValue wIndex wLength Data 11000001B 0x47 0 The interface number 16 UUID version 4 The device shall return a Universally Unique IDentifier (UUID) version 4, as defi... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6 HSML Framebuffer Transmission Protocol | 6.1 General There are two phases of the HSML protocol: • Initialization Phase: To let HSML source and HSML sink to load proper drivers that can communicate with each other and exchange the configuration messages, as shown in Figure 3. • Transmission Phase: HSML source sends the display data and HSML sink sends the cont... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.2 Managing an HSML Connection | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.2.1 Identifying Remote Applications | HSML is identified as specific encoding within an existing VNC connection. Therefore, remote applications shall be listed and handled as VNC based applications with protocolID set to "VNC". During a VNC session the MirrorLink Client shall list HSML pseudo encoding (-527) within VNC SetEncodings message, to indicate the... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.2.2 Establishing the HSML Connection | A VNC connection shall be established from the MirrorLink Client prior the HSML connection as defined in [2]. The HSML connection shall be established after VNC initialization phase as defined in clause 6.3.1. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 16 |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.2.3 Intentionally Terminating the HSML Connection | The MirrorLink Client and Server can initiate terminating both connections anytime by sending a VNC ByeBye message as specified in [2]. The MirrorLink Client shall terminate the HSML connection by sending a StopFramebufferTransmission request, as specified in clause 5.6.7, when the MirrorLink Client is in streaming mod... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.2.4 Unintentionally Terminating the HSML Connection | The HSML connection may be disconnected unintentionally in case of any error conditions. The recognizing entity shall then terminate the VNC connection by sending a VNC ByeBye message as specified in [2]. The VNC connection may be disconnected unintentionally in case of any error conditions. The MirrorLink Client shall... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3 HSML Protocol Phases | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.1 Initialization Phase | Before establishing the HSML connection, a VNC connection shall be established, because HSML depends on it to configure display parameters, provide context information and handle user input events. Therefore, the whole initialization sequence shall be as shown in Figure 5. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 17 Fi... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2 Transmission Phase | |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.1 Handling Context Information | The VNC connection is used to exchange context information via framebuffer update request - response mechanism. Instead of any framebuffer pixel data a specific HSML pseudo encoding (-527) is used to identify the out-of-band transfer via HSML. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 18 Table 15: HSML Pseudo Encoding #... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.2 Handling Display Data | Once HSML source and HSML sink exchange the required information, HSML source can start to send the display data on USB layer. There are two ways to transmit the display data from HSML source to HSML sink: 1) Streaming Mode. 2) On-Demand Mode. HSML source shall support both Streaming Mode and On-Demand Mode. HSML sourc... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.3 Handling Pausing and Resuming Data Transfer | The HSML source can pause and later on resume the HSML streaming of framebuffer data at any point in time. The message sequence, the HSML source and sink shall follow for pausing and resuming the framebuffer stream in Streaming Mode, is shown in Figure 11. Figure 11: Message Sequence for Pausing and Resuming the Data T... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.4 Handling Framebuffer Resolution Change | The MirrorLink Client and Server can change framebuffer resolution as defined in [2]. The HSML source shall follow changed resolutions immediately and send HSML Framebuffer Data with updated resolution. The HSML sink shall render Framebuffer Data with updated resolution. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 22 The ... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.5 Handling Framebuffer Format Change | The HSML sink can change the pixel format and encoding of framebuffer during the transmission phase by sending the SetParameters request. It shall follow the procedure in Figure 16. Figure 16: Message Sequence for Framebuffer Format Change in Streaming Mode After changing the pixel format, the HSML sink shall ignore fr... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.6 Handling Framerate Adjustment | The HSML sink can limit the maximum frame rate that the HSML source can send by following the procedure in Figure 17. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 24 Figure 17: Message Sequence for Framerate Adjustment |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.7 Handling Framebuffer Blocking Notification | The HSML source shall be compliant with the Framebuffer Blocking Notification mechanism in [2], the FramebufferBlocking Notification is sent by VNC Client still and the example flow is shown in Figure 18 for the example situation, when the MirrorLink Client is blocking the framebuffer after receiving new Context Inform... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.