hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.2.1 Certificate Retrieval | An application, which is downloaded and installed from a market place or via other mechanism onto a MirrorLink certified server device shall come with a MirrorLink developer self-signed Application Certificate. In case that developer self-signed Application Certificate, does not contain an entity tag or a name tag with... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.2.2 Certificate Validation | If the MirrorLink Server detects a newly installed or reinstalled application, it shall follow the steps given below: • Validate the application certificate (i.e. check expiration dates, format, and signature). • Validate the certificate's trust chain. • Validate the application identifier (i.e. check the application i... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.2.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. |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3 Certificate Revocation Checks | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3.1 Revocation Protocol | Rather than downloading Certificate Revocation Lists (CRL), the Online Certificate Status Protocol (OCSP) [2] is used to verify the status of certificates. The URI, where the MirrorLink Server shall ask for the certificate status, shall be available from the AuthorityInfoAccess (AIA) field, as defined in [1], in the ce... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3.2 Certificate Valid | The MirrorLink Server shall consider an application certificate to be valid, if: • The OCSP certStatus is "good". The MirrorLink Server shall update the relevant entries (e.g. AppList and CertifiedApplicationList) through the UPnP Application Server Service, whenever an application's certificate is getting validated, a... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3.3 Certificate Revoked | The ACMS will need to revoke an application certificate in one of the following cases: 1) On request by the application developer; or ETSI ETSI TS 103 544-14 V1.3.1 (2019-10) 23 2) On request by the Application Certification Body, when a critical driver distraction issue has been detected within the application. The Mi... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3.4 Certificate Updated | The ACMS will need to update an application certificate in one of the following cases: 1) The current application certificate expired; or 2) Entries within the current application certificate have been added; or 3) Entries within the current application certificate have been removed. NOTE: An updated application certif... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3.5 Unchecked Certificates | An unchecked certificate is a certificate, whose revocation status has not been determined during either the restricted or non-restricted grace period. The MirrorLink Server shall continue checking for the revocation status for at least 6 months after the application certificate became unchecked. After 6 months, the Mi... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.3.6 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. For OCSP testing purposes during MirrorLink device certification, the MirrorLink Server shall p... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.4 Query and Grace Periods | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.4.1 Query Period | The MirrorLink Server shall verify from the ACMS, whether any application certificate has been revoked. Validation shall happen within 50 % to 100 % of the query period, if sufficient connectivity is available. It shall not be necessary for the MirrorLink Server device to be connected to a MirrorLink Client device in o... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.4.2 Grace Period | In case the MirrorLink Server cannot access the OCSP server within the query period, the query period can be extended. Definition: Restricted Grace Period - The number of hours without a successful query before a MirrorLink Server no longer allows an application, with an application certificate distributed by CCC, to b... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 6.4.3 Period Update | The ACMS shall provide an update to the revocation and grace period on every certificate revocation check. The ACMS shall use the responseExtension field of the following structure: Extensions ::= SEQUENCE { queryPeriod [0] EXPLICIT queryPeriod DEFAULT 168, driveGrace [1] EXPLICIT restrictedGrace DEFAULT 720, baseGrace... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.1 Application Installation | If the installation of an application fails, the MirrorLink Server device shall not install the Application's Certificate. The installation of an application can happen, while the MirrorLink Server device is not connected to a MirrorLink Client device. If the installation of an application succeeds, the MirrorLink Serv... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.2 Application Filtering | The basic underlying assumption is that any MirrorLink-Certified or Member-Certified Application, successfully installed on a MirrorLink certified Server device is going to show up on a MirrorLink certified Client device. Some level of filter may happen at the Server and/or Client side. Filtering shall be transparent t... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.3 Updating UPnP Application Server Services | |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.3.1 Eventing | The MirrorLink Server shall notify the MirrorLink Client, using the UPnP eventing mechanism for the AppListUpdate status variable defined in [4] for any of the following reasons: 1) An application has been added to the reported certified or non-certified application list; or 2) An application has been removed from the ... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.3.2 A_ARG_TYPE_AppList | The MirrorLink Server shall include all applications on the Reported Certified and Reported Non-Certified Application List, as defined in clause 7.2, into the response to the UPnP Application Server Service's GetApplicationList action, defined in [4], if the application matches the AppListingFilter filter criteria. Mir... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.3.3 A_ARG_TYPE_CertifiedAppList | The MirrorLink Server shall include all applications on the Reported Certified Application List, as defined in clause 7.2, into the response to the UPnP Application Server service's GetCertifiedApplicationsList action, defined in [4], if the application matches the AppCertFilter filtering criteria. The MirrorLink Serve... |
7a924131b36e5a21939d6240caab6b0a | 103 544-14 | 7.3.4 A_ARG_TYPE_AppCertificateInfo | The MirrorLink Server shall use all entries, unmodified, from the Application Certificate, matching the A_ARG_TYPE_AppCertificateInfo entries, defined in [4], for the given application. ETSI ETSI TS 103 544-14 V1.3.1 (2019-10) 31 Annex A (normative): XSD MirrorLink Extension Value The XSD scheme allows the XML structur... |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 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... |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 2 References | |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 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... |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 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... |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 3 Definition of terms, symbols and abbreviations | |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 3.1 Terms | Void. |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 3.2 Symbols | Void. ETSI ETSI TS 103 544-28 V1.3.1 (2019-10) 6 |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: SBP Service Binary Protocol UV Ultra Violet |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 4 Data Service Definition | |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 4.1 Weather Data Service Version 1.0 | /** The present document defines data objects for the weather data * service to be carried over by SBP. By receiving this data, the * weather data sink can provide weather information to the driver * through instrument cluster display panel. The Weather Source may * be implemented in a Mirrorlink Client or a Mirrorlink... |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 5 SBP Binding | The Weather Meta Data Services uses the following objects and their access capabilities, as defined in [1]. Table 1 Object Name Access Type Subscription Type Min Interval Time Max Interval Time City WRITABLE NONE N/A N/A Temperature READABLE ON_CHANGE N/A N/A Humidity READABLE ON_CHANGE N/A N/A Pressure READABLE ON_CHA... |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 6 Theory of Operations | |
1baea25398fc9e45dc242ea27d98bbfb | 103 544-28 | 6.1 Getting Weather updates | Figure 1 shows how a weather data sink retrieves metadata about the current weather condition from the weather data source. ETSI ETSI TS 103 544-28 V1.3.1 (2019-10) 9 SBP Server (Weather Source) SBP Client (Weather Sink) User ICD Execute Steps as defined in [2] SBP: Subscribe (Alert) SBP: Response (OK) SBP: Response (A... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 1 Scope | The present document provides parts of the Abstract Test Suite (ATS) for ITS PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The objective of the present document is to provide a basis for conformance tests for security communication over GeoNetwo... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 2 References | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 3 Definition of terms, symbols and abbreviations | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 940 [2], ETSI TS 102 941 [1], ETSI TS 103 097 [3], ETSI TS 103 525-1 [4], ETSI TS 103 525-2 [5], ETSI TS 102 871-3 [7], ISO/IEC 9646-6 [i.5] and ISO/IEC 9646-7 [i.6] apply. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 3.2 Symbols | Void. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AA Authorization Authority AID Application ID ASN Abstract Syntax Notation AT Authorization Ticket ETSI ETSI TS 103 525-3 V2.1.1 (2024-09) 8 ATM Abstract Test Method ATS Abstract Test Suite BV Valid Behaviour tests CAM Cooperative Awareness Me... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 4 Contents of the ITS Security Test Suite | The ITS Security test suite contains: • test implemented in TTCN-3 code; • certificate profiles and certificate generation tool. To execute the ITS Security Test Suite a Test Adapter implementation and a TTCN-3 compiler is required. The reference Test Adapter implementation can be found at https://forge.etsi.org/rep/IT... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5 Abstract Test Method | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.1 Introduction | This clause describes the ATM used to test the ITS-Pki framework. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.2 Abstract protocol tester | The abstract protocol tester used by the ITS-Pki test suite is described in figure 1. The Test System simulates valid and invalid protocol behaviour and analyses the reaction of the IUT. Figure 1: Abstract protocol tester - Pki |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3 Test Configuration | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.1 Introduction | This test suite shall use test configurations as defined in ETSI TS 103 525-2 [5], i.e. the tester simulates the AA implementing the ITS Pki framework over HTTP protocol. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2 PKI infrastructure | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.1 Overview | Before executing tests: • security certificates need to be generated, see clause 5.3.2.5; • security certificates need to be installed onto the IUT, see clause 5.3.2.6; and • some Test System settings need to be configured, see clause 5.3.2.3. ETSI ETSI TS 103 525-3 V2.1.1 (2024-09) 10 |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.2 PKI certificate hierarchy | The required PKI certificate hierarchy of the test infrastructure shall be as specified in ETSI TS 102 940 [2] and ETSI TS 102 941 [1]. The following certificates are required for the test execution: 1) The custom user-generated root certificate, referred as CERT_TEST_ROOT, is used to sign all CA certificates used by t... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.3 Test system settings | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.3.1 Test adapter settings | A reference test adapter has been developed and validated on the TTCN-3 runtime environments as listed in table 2 and can be downloaded at https://forge.etsi.org/rep/ITS/ttcn/ats_pki_ts103525-3.git. Table 2: TTCN-3 Tool Test Adapter Location TTCN-3 Tool Location TITAN AtsPki.cfg The relevant test adapter parameters for... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.3.2 Test Suite Parameters | The PKI test suite parameters defined in ETSI TS 103 525-2 [5] shall be applied. In addition the parameters defined in ETSI TS 102 871-3 [7] and in ETSI TS 103 096-2 [8] shall be applied as listed in tables 4 and 5. Table 4: PICS Parameters Parameter Reference Role Default value PICS_GN_SECURITY ETSI TS 102 871-2 [6], ... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.4 Certificate profiles | The ITS Security Test Suite contains certificate profiles describing content of certificates to be used by both TS and IUT. Then certificate profiles are used by the Certificate Generation Tool to generate all necessary certificates, see clause 5.3.2.5. ETSI ETSI TS 103 525-3 V2.1.1 (2024-09) 12 EXAMPLE: <certificate n... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.5 Certificate generation | Certificates can be generated based on certificate profiles using the certificate generation tool, provided as a part of the test suite. Certificate generation tool does not make any validation of the input profile, it just transforms the XML profile to the XER representation of the certificate, encode it to OER repres... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.3.2.6 Certificate installation | The ATS requires installing some certificates onto the IUT. The installation procedure is manual, customer dependent and out of scope of the present document. The list of certificates to be installed on the IUT is given in the certificate content definition, defined in ETSI TS 103 096-2 [8], clause 6.1.1 and ETSI TS 10... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.4 Test architecture | The ITS Pki Test Suite is based on the test architecture described in ETSI TS 102 871-3 [7]. The test system communicates with the PKI SUT over the pkiPort and over the utPorts as described in clause 5.5. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.5 Ports and ASPs | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.5.1 Introduction | Four ports are used by the ITS-Pki ATS: • The PKI Port, of type HTTP. • The geoNetworking Port, of type geoNetworkingPort. • The utPkiPort of type LibItsPki_TestSystem.UpperTesterPort. • The denmUtPort of type LibItsDenm_TestSystem.UpperTesterPort. • The camUtPort of type LibItsCam_TestSystem.UpperTesterPort. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.5.2 Primitives of the geoNetworkingPort | Two types of primitives are used in the securityPort: • The geoNetworkingInd primitive used to receive messages of type GeoNetworkingPacket. • The geoNetworkingReq primitive used to send messages of type GeoNetworkingPacket. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 5.5.3 Primitives of the utPort | The Upper Tester port uses these types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtCamTrigger primitive with the changeSpeed parameter is used to configure IUT to send CAM messages with high rate (greater than 1 Hz). • The UtDenmTrigger primitive used trigger the event in the IUT to send... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 6 External functions | The external functions, described in ETSI TS 103 096-3 [9] shall be applied. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7 ATS conventions | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain the testing conventions, described in c... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.2 Testing conventions | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.2.1 Testing states | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.2.1.1 Initial states | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back to operational state. As no specific actions are required for the idle state in the ETSI TS 103 097 [3], the function f_poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.3 Naming conventions | |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.3.1 Introduction | This test suite follows the naming convention guidelines provided in the ETSI EG 202 798 [i.1]. |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.3.2 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 6) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 8; • prefixes... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.3.3 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, table 7 shows specific naming conventions that apply to the ITS TTCN-3 test suite. ETSI ETSI TS 103 525-3 V2.1.1 (2024-09) 16 Table 7: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Three asterisks. EXAMPLE 1: log("*** TC_SEC_P... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.3.5 Test Case (TC) identifier | Table 8 shows the test case naming convention, which follows the same naming convention as the test purposes. ETSI ETSI TS 103 525-3 V2.1.1 (2024-09) 17 Table 8: TC naming convention Identifier TP_<root>_<tgt>_<gr>_<sub-gr> <sn>_<x> Sub-Group Category <root> = root SECPKI <tgt> = target ITSS ITS-Station AA Authorizatio... |
5e492524adbdb027889fafec833f5088 | 103 525-3 | 7.4 On line documentation | The T3D tool enables providing on-line documentation browser in HTML, by tagging TTCN-3 comments. These tags are defined in table 9. Table 9: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 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... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 2 References | |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 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... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 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... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 3 Definition of terms, symbols and abbreviations | |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 3.1 Terms | Void. |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 3.2 Symbols | Void. |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 3.3 Abbreviations | Void. |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4 Service Modeling Definition | |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.1 Service Type | The following service type identifies a service that is compliant with the present document: urn:schemas-upnp-org:service:TmNotificationServer:1 TmNotificationServer defined in the present document refers to the same service type. The TmNotificationServer service shall follow defined UPnP behaviour within the UPnP Devi... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.2 TmNotificationServer Service Architecture | This service provides the features for a MirrorLink UPnP Control Point to receive notifications from a MirrorLink UPnP Server Device. Based on information of the notification evented to the MirrorLink UPnP Control Point, the MirrorLink UPnP Control Point may launch the applications to bring it to foreground on the Mirr... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3 State Variables | |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.1 State Variable Overview | Table 4-1: Service State Variables Variable Name Req. or Opt. Data Type Allowed Value Default Value Eng. Units ActiveNotiEvent R string Undefined Empty string N/A NotiAppListUpdate R string Undefined Empty string N/A A_ARG_TYPE_Notification R string Undefined Empty string N/A A_ARG_TYPE_AppID R string Undefined Empty s... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.2 ActiveNotiEvent | ActiveNotiEvent is an evented state variable of type A_ARG_TYPE_NotiID, which contains the most urgent notification that needs to be handled from the MirrorLink UPnP Control Point. ActiveNotiEvent shall originate from an application (as given in appID), which has been set using the SetAllowedApplications actions. It is... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.3 NotiAppListUpdate | NotiAppListUpdate is an evented state variable of type A_ARG_TYPE_String, which contains a comma separated list of applications identifiers of applications, supporting notifications. Each application identifier is of type A_ARG_TYPE_AppID. The state variable is evented, implying that clients can subscribe to receive no... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.4 A_ARG_TYPE_Notification | The format of the A_ARG_TYPE_Notification state variable is an XML document. It includes detailed information about a notification. Table 4-2: Structure of the A_ARG_TYPE_Notification Element Description Parent Availability notification Notification element contains detailed information of an event occurred on a phone ... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.5 A_ARG_TYPE_AppID | A UTF-8 encoded string representing an unsigned 32-bit integer in hexadecimal format (with '0x' prefix) which denotes the unique application identifier. The MirrorLink Server shall use the unsigned integer value of a variable of this type within any action. I.e. comparing the values of two A_ARG_TYPE_AppID variables sh... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.6 A_ARG_TYPE_ProfileID | An unsigned 32-bit integer greater than or equal to 0, representing a unique profile identifier. Its value is set equal to 0 by default. |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.7 A_ARG_TYPE_ActionID | A UTF-8 encoded string representing an unsigned 32-bit integer in hexadecimal format (with '0x' prefix) which denotes the unique action identifier. The MirrorLink Server shall use the unsigned integer value of a variable of this type within any action. I.e. comparing the values of two A_ARG_TYPE_ActionID variables shal... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.8 A_ARG_TYPE_NotiID | A string formatted as UTF-8 representing a notification identifier, which has been provided by the given applications, identified by ApplicationID. The format is given as: NotifiationID@ApplicationID ETSI ETSI TS 103 544-11 V1.3.1 (2019-10) 12 NotificationID is an unsigned 32-bit integer in hexadecimal format (with '0x... |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.9 A_ARG_TYPE_String | A simple string type (UTF-8). |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.10 A_ARG_TYPE_URI | A string encoded as UTF-8 representing a URI. The URI shall be local to the MirrorLink Server. Access to external resources is not allowed. |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.11 A_ARG_TYPE_INT | A simple unsigned 32-bit integer represented in decimal (base 10) format. |
a8734cd2e670172d8d5e7f4f3b18bb02 | 103 544-11 | 4.3.12 A_ARG_TYPE_Bool | A simple Boolean string which can either have the value 'true' or 'false'. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.