hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.5 Sink & Source Status Events | The User Input Descriptor field of the MirrorLink UIBC Input message for the Sink & Source Status Event Type ID is shown in Table 6. The Sink & Source Status event provides status information of specific device features and the ability to set them. Table 6: User Input Descriptor Field for Sink & Source Status Events Fi... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.6 UI Context Event | The User Input Descriptor field of the MirrorLink UIBC Input message for the UI Context Event Type ID is shown in Table 7. Table 7: User Input Descriptor Field for UI Context Events Field Size (Octet) Notes Reference 4 Context reference within the RTP UI stream. This Reference field shall be set to a non-zero value; th... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.7 UI Blocking Event | The User Input Descriptor field of the MirrorLink UIBC Input message for the UI Blocking Event Type ID is shown in Table 8. Table 8: User Input Descriptor Field for UI Blocking Events Field Size (Octet) Notes Reference 4 Context reference to the RTP UI stream. The UI blocking reference shall be equal to the UI context ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.8 Audio Context Event | The User Input Descriptor field of the MirrorLink UIBC Input message for the Audio Context Event Type ID is shown in Table 9. Table 9: User Input Descriptor Field for Audio Context Events Field Size (Octet) Notes Reference 4 Context reference to the RTP audio stream. This Reference field shall be set to a non-zero valu... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.9 Audio Blocking Event | The User Input Descriptor field of the MirrorLink UIBC Input message for the Audio Blocking Event Type ID is shown in Table 10. Table 10: User Input Descriptor Field for Audio Blocking Events Field Size (Octet) Notes Reference 4 Context reference within the RTP audio stream. The audio blocking reference shall be equal ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.10 Sink& Source Cut Text Events | The User Input Descriptor field of the MirrorLink UIBC Input message for the Sink & Source Cut Text Event Input Type ID is shown in Table 11. Ends of lines are represented by the linefeed / newline character (value 0x000A) alone. No carriage-return (value 0x000D) is needed. Table 11: User Input Descriptor Field for Sin... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.3 MirrorLink Specific RTSP Data Structures | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.3.1 General | The UIBC capability negotiation and update process are achieved using RTSP procedures. MirrorLink Client and Servers shall use UIBC (User Input Back Channel) to implement the User Input & Output Event mechanisms. During RTSP capability negotiation phase, wfd-uibc-capability parameter is used to describe what UIBC relat... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.3.2 wfd-uibc-capability parameter | When using WFD for MirrorLink, the wfd-uibc-capability parameter (as described in clause 6.1.15 of [5]) is used with input-cat field set to "VENDOR_SPECIFIC" and the vendor-specific-cap-info field set as specified (in the bold-face) as below. wfd-uibc-capability = "wfd_uibc_capability:" SP ("none" / (input-category- va... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.3.3 wfd-uibc-setting parameter | When using WFD for MirrorLink, the wfd-uibc-setting parameter (as described in clause 6.1.16 of [5]) SHALL be used during WFD capability negotiation or with the M15 RTSP message with uibc-setting field set to "enable" to start the UIBC session. |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 8 WFD Content Protection | Content protection using HDCP may be used by following the procedures described in [5]. Additional technical guidance and recommended best practices for MirrorLink devices implementing WFD with HDCP is provided in [i.2]. When using ML over WFD, the ML server shall not require HDCP content protection to start streaming ... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 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... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 2 References | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 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... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 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... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 3 Definition of terms, symbols and abbreviations | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 3.1 Terms | Void. |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 3.2 Symbols | Void. |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACMS Application Certification Management System AIA Authority Information Access CA Certificate Authority CN Common Name CTS Conformance Test System DAP Device Attestation Protocol DER Distinguished Encoding Rules HTTP HyperText Transfer Prot... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 4 Developer Application Concept | MirrorLink provides the ability to run certified applications on MirrorLink server devices that can be launched from the MirrorLink client device. In order to improve safety and ensure a quality user experience, an application certification program is implemented that will control which applications can be used with Mi... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5 Application Developer Certificate Structure | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.1 Application Development Certificate | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.1.1 General | MirrorLink Application Development Certificates shall be a public key X.509 version 3 certificate as specified in [1]. The certificate is a self-signed certificate. The signing authority shall not set an expiration date of longer than 1 month from the date of signing. Application Development Certificate shall use 2048-... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.1.2 Extension Header | The X.509 extension header shall have the following format: X509v3 extensions: CCC-MirrorLink-Developer-Id Extension: extnId: 1.3.6.1.4.1.41577.3.1 critical: no extnValue: DER:OCTET STRING CCC-MirrorLink Extension: extnId: 1.3.6.1.4.1.41577.2.1 critical: no extnValue: DER:<DER encoded XML, as specified below> |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.1.3 Extension Values | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.1.3.1 CCC-MirrorLink-Developer-Id | Developer Id, as provided from the Application Certification Management System (ACMS), shall be formatted as a character string of up to 40 alphanumeric characters (‘a’-‘z’, ‘0’-‘9’). |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.1.3.2 CCC-MirrorLink Extension Value | The DER encoded XML of the application information, as specified in [4]. The Signing Entity Name of application development certificates shall be "DEVELOPER". |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2 Developer Identification Certificate | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2.1 General | The MirrorLink Dev ID Certificate shall be a public key X.509 version 3 certificate as specified in [1]. The certificate shall be signed by the CCC's Root Certificate. A hierarchy of Certification Authorities (CAs) may be used for Dev ID certificates. In case intermediate CAs are used, the entire certificate chain up t... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2.2 Extension Header | The X.509 extension header shall have the following format: X509v3 extensions: CCC-MirrorLink-Developer-Id Extension: extnId: 1.3.6.1.4.1.41577.3.1 critical: no extnValue: DER:OCTET STRING CCC-MirrorLink-Developer-Server-Ids Extension: extnId: 1.3.6.1.4.1.41577.3.2 critical: no extnValue: DER:OCTET STRING CCC-MirrorLin... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2.3 Extension Values | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2.3.1 CCC-MirrorLink-Developer-Id | Developer Id, as provided from the Application Certification Management System (ACMS), shall be formatted as a character string of up to 40 alphanumeric characters (‘a’-‘z’, ‘0’-‘9’). |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2.3.2 CCC-MirrorLink-Developer-Server-Ids | A comma-delimited list of Server Ids, for which the Dev ID certificate is valid; each entry shall be formatted as a string (UTF-8). Server IDs are the IMEI/IMEISV number or version 5 UUID derived from an equivalent unique identifier of the MirrorLink Server devices on which development applications can be used, as defi... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.2.3.3 CCC-MirrorLink-Client-Manufacturer-Ids | Comma-separated list of MirrorLink Client manufacturer ids, for which the Dev ID certificate is not valid (black list). Each entry shall be formatted as a string (UTF-8). Each list entry represents a manufacturer name, and shall match the manufacturer name (as provided from the UPnP Client Profile service [5]) or the A... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 5.3 Root Certificate | The signing certification authority's Root Certificate, a hash of it or a hash of its public key shall be stored in the MirrorLink Server. Access to the certificate's public key shall be read-only. Expiration date of the root certificate shall be 20 years from the date of signing. Root certificate shall use 4 096-bit R... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6 Developer Identification Certificate Life Cycle | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.1 Certificate Retrieval and Validation | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.1.1 Certificate Retrieval | The MirrorLink Server shall use HTTP-GET to obtain the MirrorLink Dev ID certificate from the Application Certification Management System using the following URL: http://acms.carconnectivity.org:80 The following GET command shall be used to obtain the application certificate: GET /obtainDeveloperCertificate.html? certi... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.1.2 Certificate Validation | The validation of Dev ID certificates is following the steps below: 1) Validate the Dev ID certificate and trust chain. 2) Validate the MirrorLink Server identifier is in the list of Server IDs, as given in the CCC-MirrorLink- Developer-Server-Id X.509 extension. 3) Validate the MirrorLink Client's manufacturer identif... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.1.3 Testing Considerations | For Certification Validation testing purposes during MirrorLink device certification, the MirrorLink Server shall accept the CTS root certificate to validate application certificates distributed by the ACMS. This Test Mode shall not be accessible in production devices. |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.2 Certificate Revocation Checks | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.2.1 Revocation Protocol | The MirrorLink Server shall use the Online Certificate Status Protocol (OCSP) [2] to verify the status of Dev ID certificate. The URI, where the MirrorLink Server shall ask for the certificate status, shall be available from the AuthorityInfoAccess (AIA) field, as defined in [2], in the certificate. The MirrorLink Serv... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.2.2 Certificate Valid | The MirrorLink Server shall consider a developer ID certificate to be valid, if: • The OCSP certStatus is "good". ETSI ETSI TS 103 544-16 V1.3.1 (2019-10) 13 |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.2.3 Certificate Revoked | The MirrorLink Server shall consider the developer ID certificate to be revoked if: • The OCSP certStatus is "revoked"; and • The ACMS returns the HTTP-Get response with Error Code 500/900, when requesting a new certificate. The MirrorLink Server shall not send any further HTTP-Get and OCSP request for a revoked develo... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.2.4 Certificate Updated | A developer ID certificate shall be updated in the following cases: 1) Current Dev ID certificate expired. 2) Server or Client identifier fields in the certificate changed within the ACMS. The MirrorLink Server shall consider the developer ID certificate as to be updated if: • the OCSP certStatus is "revoked"; and • th... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.2.5 Testing Consideration | For OCSP testing purposes during MirrorLink device certification, the MirrorLink Server shall accept the CTS root certificate to validate responses from the ACMS. This Test Mode shall not be accessible in production devices. |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.3 Query and Grace Periods | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.3.1 Query Period | The MirrorLink Server shall verify from the ACMS, whether the developer ID certificate has been revoked. Validation shall happen within 50 % and 100 % of the query period, as defined in [4]. Developer ID certificates shall use the same query period as regular application certificates. If the query period is set to 0, t... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 6.3.2 Grace Period | The MirrorLink Server shall not allow for any Grace Period for Developer ID certificates. ETSI ETSI TS 103 544-16 V1.3.1 (2019-10) 14 |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 7 Application Development Certificate Life Cycle | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 7.1 Certificate Retrieval and Validation | |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 7.1.1 Certificate Retrieval | The MirrorLink Server manufacturer shall provide a mechanism to create and self-sign an application development certificate. The application development certificate shall include the developer identifier from the Dev ID Certificate. To facilitate rapid application development cycles, the application identifier should b... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 7.1.2 Certificate Validation | The validation of Application Development certificates is following the steps below: 1) Validate the application development certificate. 2) Validate the developer identifier is identical to the validated one in the Developer ID certificate. NOTE: The application identifier will not be validated, as it is expected to b... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 7.1.3 Certificate Update | An application development certificates shall be updated in the following cases: 1) Current application development certificate expired. 2) New developer identifier. The MirrorLink Server manufacturer shall provide a mechanism to update a self-signed application development certificate. On update of an application deve... |
772c63b7a5c13e42a1256d524ba3d1f6 | 103 544-16 | 7.2 Certificate Revocation Checks | Application development certificates are not subject to any Revocation Protocol. The MirrorLink Server shall not use OCSP requests to check with the ACMS the revocation status of any application development certificate. ETSI ETSI TS 103 544-16 V1.3.1 (2019-10) 16 Annex A (informative): OCSP Request & Response Example A... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 1 Scope | The scope of the present document is to provide technical guidelines for assessing device conformity to Pan-European eCall (according to CEN EN 16072:2015 [i.2]) and essential performance (CEN EN 16072 [i.3], ETSI TS 103 428 [i.4] and CEN EN 15722:2015 [i.6]). The present document compiles existing test cases / procedu... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 2 References | |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 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... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 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... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 3 Definitions and abbreviations | |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: category A: requirement category to ensure compliant functionality according to Regulation (EU) 2017/79 [i.5] category B: requirement category to ensure functional conformity regarding CEN specification represented by ETSI TS 103 412 [... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement AL Application Layer AL-ACK Application Layer ACKnowledgement AT ATtention CEN European Committee for Standardization ETSI ETSI TS 103 543 V1.1.1 (2018-02) 7 CTP Conformance Test Point EGNOS European Geographic Navigation O... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4 IVS conformance assessment | |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.0 General | This clause compiles conformance safety related requirements and test procedures relevant to Pan European eCall. It further includes category assignment to each test case. This information shall be used by device manufacturers and integrators for regulatory conformance indication (Category A), as well as for functional... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.1 Prerequisites | Devices used in the IVS conformance assessment procedure are CE certified. This implicitly indicates European conformity to health, safety, and environment protection throughout the EEA allowing devices to be traded in the EEA. |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.2 Commission Delegated Regulation (EU) 2017/79 | This clause is based on the Commission Delegated Regulation (EU) 2017/79 [i.5] |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.2.1 Sled tests - (EU) 2017/79 Annex I | Following test cases are specified in Commission Delegated Regulation (EU) 2017/79 [i.5] and more specifically "Annex I - Technical requirements and procedures for testing the resistance of eCall in-vehicle systems to severe crashes (high-severity deceleration test)". ETSI ETSI TS 103 543 V1.1.1 (2018-02) 8 Table 4.2.1... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.2.2 Coexistence tests - Regulation (EU) 2017/79 Annex IV | Following test cases are specified in Commission Delegated Regulation (EU) 2017/79 [i.5] and more specifically "Annex IV - Co-existence of third party services (TPS) with the 112-based eCall in-vehicle systems". Table 4.2.2-1: Coexistence tests TC Name Category 2.3. Deactivation of the 112-based system while the TPS sy... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.2.3 GNSS tests - Regulation (EU) 2017/79 Annex VI | Following test cases are specified in Commission Delegated Regulation (EU) 2017/79 [i.5] and more specifically "Annex VI - Technical requirements for compatibility of eCall in-vehicle systems with the positioning services provided by the Galileo and the EGNOS systems". Table 4.2.3-1: GNSS tests TC Name Category 2.2.1. ... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.2.4 In-vehicle system self-test - Regulation (EU) 2017/79 Annex VII | Following test cases are specified in Commission Delegated Regulation (EU) 2017/79 [i.5] and more specifically "Annex VII - In-vehicle system self-test". Table 4.2.4-1: Self-test TC Name Category 2.1 Self-test function verification test A 4.2.5 Privacy and data protection tests - Regulation (EU) 2017/79 Annex VIII Foll... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.3.1 Conformance tests for IVS eCall user equipment | Table 4.3.1-1: End to end tests Clause TC Name Catego ry 7.1.1.1 CTP 1.1.0.1 Conformance to ETSI TS 102 936-1 [i.8] and ETSI TS 102 936-2 [i.9] - PE eCall IVS B 7.1.1.2a CTP 1.1.0.2 Test for conformance to valid SIM/USIM - PE eCall capable IVS B 7.1.1.2b CTP 1.1.0.2 Test for conformance to valid SIM/USIM - PE eCall onl... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.4 eCall HLAP interoperability testing | Following test cases are specified in ETSI TS 103 428 [i.4] eCall HLAP Interoperability Testing specification. Table 4.4-1: Interoperability tests Clause TC Name Category 7.1.1 TD_MAN_1 MSD transmission / reception / acknowledgement with PSAP in Pull mode B 7.1.2 TD_MAN_2 MSD transmission / reception / acknowledgement ... |
9270a5ddc247610d11dfa387e9309b11 | 103 543 | 4.5 Additional restrictions and risks | CEN EN 15722:2015 [i.6] specifies that the last known real direction of the IVS should be included in the eCall MSD in 2 degree steps referenced to the magnetic north. Nevertheless, due to the use case of eCall IVS systems (on land maps) a fixed reference is needed which is the geodetic north for land navigation. There... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 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... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 2 References | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 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... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 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... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 3 Definition of terms, symbols and abbreviations | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 3.1 Terms | Void. |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 3.2 Symbols | Void. |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACMS Application Certification Management System AIA Authority Information Access API Application Programming Interface CA Certificate Authority CCC Car Connectivity Consortium CN Common Name CRL Certificate Revocation List CTS Conformance Tes... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 4 Application Certification Concept | MirrorLink distinguishes three main categories of applications: 1) A MirrorLink-Aware Application describes an application that implements software interfaces, which can be used via MirrorLink. A MirrorLink-Aware Application does not have MirrorLink or CCC Member certification, as described below. 2) A MirrorLink-Certi... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5 Application Certificate Structure | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.1 X.509 Certificate | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.1.1 Application Certificate | Application Certificates shall be a public key X.509 version 3 certificate as specified in [1]. MirrorLink uses long-lived Application Certificates. The signing Certification Authority should set an expiration date of 10 years from the date of signing, but it shall not be longer than the expiration date of the signing ... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.1.2 Intermediate Certificate | Hierarchy of certification authorities (CAs) may be used for application certification. In case intermediate CAs are used, the entire certificate chain up to the root CA shall be provided to the MirrorLink Server together with the application certificate. The Intermediate certificate, which signed by the CCC root CA, s... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.1.3 Root Certificate | The signing certification authority's Root Certificate, a hash of it or a hash of its public key shall be stored in the MirrorLink Server. Access to the certificate's public key shall be read-only. Expiration date of the root certificate shall be 20 years from the date of signing. Root Certificate shall use 4 096-bit R... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2 MirrorLink Extension | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.1 Extension Header | The X.509v3 [1] extension header shall have the following format. The CCC-MirrorLink Extension Id is provided from IANA. The identifier shall be provided without any "<>" delimiter. Its value is outside the scope of the present document: X509v3 extensions: CCC-MirrorLink Extension: extnId: 1.3.6.1.4.1.41577.2.1 critica... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.2 CCC-MirrorLink Extension Value | The DER encoded XML shall follow the format in Table 1. Detailed description of the elements can be found in the definitions of A_ARG_TYPE_AppList and A_ARG_TYPE_AppCertificateInfo in [4]. Table 1: MirrorLink Extension Header extnValue XML Element Description Parent Availability certificate MirrorLink Application Certi... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.3 Certificate Signing Entities | The following entity names are currently registered with CCC. The MirrorLink Client shall ignore any unknown entries. Table 2: Certificate Signing Entities Entity Name Description CCC Car Connectivity Consortium The application follows application guidelines, as specified from CCC, for the certified regions. DEVELOPER ... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.4 MirrorLink Server Platform Identifier | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.4.1 Registered MirrorLink Server Platform Identifier | MirrorLink Server devices, supporting 3rd party applications, shall support at least one of the listed platforms in Table 3. These platforms shall implement the MirrorLink API as defined in [5]. Additional platform specific requirements exist for Android [6]. Other registered platforms may have their own platform speci... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.4.2 Proprietary MirrorLink Server Platform Identifier | MirrorLink Server devices, supporting only a limited set of 1st party applications (MirrorLink Accessory devices), may support proprietary platforms, which do not implement the MirrorLink API or only a subset of it. The platform identifier of those proprietary platforms shall be formed as follows: Proprietary_<vendorNa... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.5 MirrorLink Server Runtime Identifier | The following runtime identifiers and their respective versions are currently registered with CCC. The runtime identifier shall be used case-sensitive. Table 4: MirrorLink Server Runtime Identifier Runtime Identifier Description Known Runtime Versions Native Native environment NOT USED |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.6 Application identifier | Each application shall have an application identifier, which identifies a particular version of an application executable within the given platform. The MirrorLink Server shall be able to detect any change to the application's executable after the application certificate has been signed. The application identifier shal... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 5.2.7 Mapping of Locales | CCC has defined a set of guidelines for CCC drive certification in the European Union, North America and Japan. Table 5 lists the locales (for the appropriate regions), which shall be included into the restricted element within the CCC signing entity, in case the application has passed the respective certification. Tab... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6 Application Certificate Life Cycle | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.1 General | The Application Certificate Life Cycle of applications, coming with a self-signed Application Certificate, containing an "entity" tag with a "name" tag value of "DEVELOPER", are specified in [3]. The high-level Application Certificate life-cycle is given below; the detailed specification is described in the following c... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.2 Certificate Retrieval and Validation |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.