hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.6 Hash as UID | In SBP, hash value of object name or member variable name is used as a UID. Due to this, each service description should make sure that there is no conflict in hash value: • All object names shall have unique hash value inside the service. Hash conflict across different services does not matter. • Each member variable ... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7 Error handling | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.1 General | This clause describes how error should be handled. Error can be classified into irrecoverable error and recoverable error. Additionally, there are errors which should be just ignored. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.2 Irrecoverable error | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.2.1 Introduction | Irrecoverable error is an error when integrity of the other side cannot be trusted any more. Both SBP Sink and SBP Source, upon receiving this kind of error shall terminate the current session of the service in CDB level either by sending CDB StopService message or by sending CDB ServiceResponse message with error code... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.2.2 Unknown data type | Adding new data type breaks compatibility with old version of service framework as the size of data cannot be determined. This situation should have been avoided by checking version number in UPnP stage or CDB stage, but if this case happens due to other reason like lost synchronization, it shall be treated as an irrec... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.2.3 Wrong END: END check failure for form 4, 5 or command | STRUCTURE, STRUCTURE_ARRAY, or command does not terminate with END/END_C after receiving the expected number of elements. END and END_C are used to check the integrity of data payload, and when END/ENC_C are not discovered in the expected location, it shall be treated as critical error. This case is treated as irrecove... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.3 Recoverable error | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.3.1 Introduction | Recoverable error is an error which should be replied with error code if sending reply is possible in the command sequence. If command sequence does not allow sending reply, this error should be ignored. All error code not marked as irrecoverable can be considered as a recoverable error. Complete list of recoverable er... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.3.2 Unknown Object UID | This error happens when UID for the command sent from either side is unknown. SBP Source shall reply with error code, "unknown UID". When the SBP Sink receives unknown UID as part of response to a command, the SBP Sink should ignore it. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.3.3 Unknown command type | When SBP Sink sends an unknown command, SBP Source shall reply with a Response with the error code of "Unknown Command". When SBP Source sends a command with unknown type, the SBP Sink should ignore it. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.3.4 Unsupported feature | When any SBP endpoint sends a command of an unsupported feature, the other SBP endpoint shall reply with a Response with the error code of "Feature not supported". |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.4 Error to ignore | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.4.1 General | Some errors are to be ignored as ignoring such case allows future extension without breaking compatibility. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.4.2 Unknown UID for member variable | This situation can happen when a new member variable is added to a service. Even if one side does not support the latest version with the new member variable, the other side can still send the object data with new member variable. Upon receiving such member variable with unknown UID, either side shall just ignore the c... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.7.5 Error code definition | Table 16 gives the list of error code defined. Error code in the range of 0x1 to 0x0fffffff is allocated for irrecoverable error. Error code from 0x10000000 to 0x3fffffff is allocated for recoverable error. As new error code can be added in the future, range of the error code should be checked first rather than checkin... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.8 Authentication mechanism | The purpose of authentication is for SBP Source to verify if SBP Sink has valid permission to access the resource. MirrorLink CDB already has mechanism to restrict access to selected applications. But there may be service specific needs to have additional authentication. Also note that authentication does not protect t... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.9 Support of optional Objects | The current version of SBP does not have mechanism to list available Objects or to retrieve meta-data. It is up to each service to pass necessary meta-data information. SBP Sink can check if an optional Object is supported or not by trying to Get or Subscribe the Object. If the Object is not supported, SBP Source shall... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.10 Version listing and selection | This is supported in CDB level. Once CDB StartService message, which includes version selection, is received, the version is maintained while the session is maintained. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.11 Initialization Sequence | Figure 7: Example starting sequence of CDB/SBP The figure 3 shows initialization sequence of SBP with CDB. 1) CDB Endpoint in the SBP Sink side requests the list of supported services by sending ServicesRequest message. Before the step, SBP Source may register itself to CDB endpoint, but that step is not shown. 2) The ... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.12 Other topics | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.12.1 Extending a service | Adding a new data member to existing object is an easy way to extend existing service without breaking compatibility with already deployed counter-parts. Compatibility can break when the data type of an existing member variable is changed. In such case, there should be a change in major version number. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.12.2 Payload fragmentation | Each SBP command shall be delivered by one or more than one CDB ServicePayload messages. CDB layer can do the optimization of combining multiple ServicePayload into one TCP packet, but such concatenation should not happen in service framework level. If a command is too big to fit into single CDB Payload message, it sha... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.12.3 Inheritance | In the service description, inheritance can be used to avoid defining the same type again and again. Each service description using inheritance needs to make sure that the final data generated can be bounded. For example, a loop in inheritance relationship will create a data with infinite length which cannot be used. E... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.12.4 Shutdown clean-up and reconnection | When a SBP session is closed due to normal shut-down or shut-down caused by irrecoverable error, SBP Source should close all active commands by itself. If the service is still available in CDB service list, and the SBP Sink requests the service again, SBP Source shall guarantee that the previous shut-down does not prev... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 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... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 2 References | |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 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... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 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... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 3 Definition of terms, symbols and abbreviations | |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 3.1 Terms | Void. ETSI ETSI TS 103 544-20 V1.3.1 (2019-10) 6 |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 3.2 Symbols | Void. |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Access Point CCC Car Connectivity Consortium DHCP Dynamic Host Configuration Protocol DNS Domain Name System GC P2P Group Client GO P2P Group Owner IE Information Element IP Internet Protocol ML MirrorLink P2P Peer-to-peer WAN Wide Area Net... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 4 Internet Accessibility | |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 4.1 General | Both MirrorLink Server and Client can access the Internet, if all the following three conditions are true: 1) Either MirrorLink Server or Client shall have Internet connectivity with WAN interface. 2) The device that has Internet access shall be capable of sharing its connectivity to the other. 3) The device having Int... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 4.2 Wi-Fi P2P Connection | |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 4.2.1 General | If a MirrorLink Server and Client want Wi-Fi P2P connection, they shall proceed Wi-Fi connection setup as defined on the Wi-Fi P2P specification [1]. If a MirrorLink Client is setup to connect in this mode and the MirrorLink Server is set to operate in the same mode, the two devices find each other over Wi-Fi technolog... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 4.2.2 MirrorLink Internet Accessibility information Exchange | To inform the configuration information of internet accessibility of both sides, an Internet Accessibility sub-element shall be included into the CCC Information Element, as defined in [2] prior to a group formation. The Internet Accessibility entry provides the following information: • MirrorLink Type, i.e. whether th... |
88f8f972ea0badf53c29e02e126aa80c | 103 544-20 | 4.2.3 Managing Wi-Fi P2P connection using MirrorLink Service Discovery | MirrorLink Server or Client wants to become Group Owner when its configuration or service needs P2P Group Owner role to operate correctly. For example, MirrorLink Client shall become Group Owner to support more than one MirrorLink Servers, while MirrorLink Server shall play Group Owner role to offer Internet connectivi... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 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... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 2 References | |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 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... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 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... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 3 Definition of terms, symbols and abbreviations | |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 3.1 Terms | For the purposes of the present document, the following terms apply: pointer event: touch screen action in which the user touches the screen with one (virtual) finger only at a single location touch event: touch screen action in which the user touches the screen with two or more separate fingers at different locations ... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: PKA Public key of device A. PKCCC Public key of the CCC root CA. PKCTS Public key of the CTS root CA (for testing purpose). PKCTSD Public key of the CTS Device (for testing purpose). PKCTSM Public key of the CTS Manufacturer CA (for testing purpose)... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One CA Certification Authority CCC Car Connectivity Consortium CDB Common Data Bus CTS Conformance Test System DAP Device Attestation Protocol DER Distinguished Encoding Rules HSML High-Spead Media Link HTTP Hype... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4 Managing a DAP Session | |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.1 Bindings | |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.1.1 TCP Binding | |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.1.1.1 Identifying DAP Server | The identification of the DAP server is described in [8]. ETSI ETSI TS 103 544-4 V1.3.1 (2019-10) 8 |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.1.1.2 Device Attestation Launch | The DAP server start-up is facilitated via the UPnP TmApplicationServer:1 service LaunchApplication action, as defined in [8]. The LaunchApplication action shall return with a URL to the DAP server. If the returned URL is already used from any established DAP session, this session will continue without any change. Othe... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.1.2 Intentionally Terminating the DAP Session | The DAP server shall not intentionally terminate a DAP session. The DAP client shall intentionally terminate a DAP session, using the following steps: 1) UPnP Control Point uses TmApplicationServer:1 service's TerminateApplication SOAP action to send termination request. 2) DAP client shall disconnect the TCP connectio... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.1.3 Unintentionally Terminating the DAP Session | Unintentional termination of the DAP session may happen at any time due to error conditions. In the case of unintentional termination of the DAP session, the respective DAP server or client shall disconnect the TCP connection. The respective counterpart should disconnect as well. If the MirrorLink Client decides to re-... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.2 Other Bindings | Besides TCP/IP, it will be possible to run MirrorLink Device Attestation Protocol on top of other protocols like Bluetooth RFCOMM, but how to discover and establish connection for such configuration is outside the scope of the present document. |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 4.3 Testing Considerations | If the MirrorLink Client is in a dedicated testing state (as part of the MirrorLink Certification), it shall launch a new DAP session (either initiated automatically or manually from the user), whenever the DAP server has unintentionally terminated the DAP session. The MirrorLink Client shall have a mechanism to allow ... |
9640705d770ebd8a6dfaf82a1b63a15a | 103 544-4 | 5 Device Attestation Protocol | The prerequisite of successful Device Attestation Protocol run is that the MirrorLink server has a X.509 device certificate (with Extended Key Usage tcg-kp-AIKCertificate OID 2.23.133.8.3 as specified in clause 3.5 of [12]) for its device key pair from the server device manufacturer. The MirrorLink Client shall not exp... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 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... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 2 References | |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 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... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 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... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 3 Definition of terms, symbols and abbreviations | |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 3.1 Terms | Void. |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 3.2 Symbols | Void. |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CCC Car Connectivity Consortium IE Information Element IEEE Institute of Electrical and Electronics Engineers ML MirrorLink OUI Organizationally Unique Identifier UPnP Universal Plug and Play URL Universal Resource Locator |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 4 IEEE 802.11 Information Element | The IE (Information Element) is located at the end of management frames such as the beacon frame defined in 802.11 specification of IEEE [1]. Multiple IEs can be concatenated. Based on the usage of IE, IEEE defines the formats of different kinds of IEs identified by the Element ID. The IEEE 802.11 Information Element f... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 5 CCC Information Element | |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 5.1 General | The format of the CCC Information Element is given in Table 2. Table 2: MirrorLink Information Element Format Field Size (octet) Value Description Element ID 1 0xDD 802.11 Vendor specific usage Length 1 Variable The length of sum of following elements OUI (Organizationally Unique Identifier) 3 04-DF-69 CCC specific OUI... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 5.2 MirrorLink Subelements | |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 5.2.1 General | The MirrorLink Subelement format is given in Table 4. Table 4: MirrorLink Subelement Format Field Size (octet) Value Description Subelement ID 1 Identifier which represents the type of subelement (See Table 5). Length 1 Variable The length of sum of following elements Subelement body field variable The value of subelem... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 5.2.2 MirrorLink UPnP Device Information Subelement | The MirrorLink Device Information subelement is given in Table 6. The Subelement ID field shall have a value of 0x00. Table 6: MirrorLink UPnP Device Information Subelement Field Size (octet) Value Description Subelement ID 1 0x00 Identifier which indicates subelement type of UPnP device information of MirrorLink devic... |
c2d3ea6644bdb8fe004dc736e0a2471f | 103 544-18 | 5.2.3 Internet Accessibility Subelement | The Internet Accessibility subelement is given in Table 8. The Subelement ID field shall have a value of 0x01. Table 8: Internet Accessibility Subelement Field Size (octet) Value Description Subelement ID 1 0x01 Identifier which indicates subelement type of Internet Accessibility. Length 1 2 Length of sum of following ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 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... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 2 References | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 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... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 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... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 3 Definition of terms, symbols and abbreviations | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 3.1 Terms | For the purposes of the present document, the following terms apply: sink device: device that receives multimedia content from a WFD source over a Wi-Fi link and renders it source device: device that supports streaming multimedia content to a WFD sink(s) over a Wi-Fi link |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 3.2 Symbols | Void. |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Access Point AV Audio-Video BSS Basic Service Sets BT Bluetooth BVRA Bluetooth Voice Recognition Activation CCC Car Connectivity Consortium CDB Common Data Bus CRLF Carrige-Return, Line Feed DAP Device Attestation Protocol DHCP Dynamic Host... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 4 Introduction | Wi-Fi Display, also known as Miracast, is a peer-to-peer wireless screen replication standard created by the Wi-Fi Alliance. Its main purpose is to let the source device project its screen to the sink device screen, and to provide the sink device with the method to control the source device. Figure 1 shows the typical ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5 MirrorLink over WFD Procedure | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5.1 General | MirrorLink over Wi-Fi Display (WFD) connection between MirrorLink Server acting as WFD source device and MirrorLink Client acting as WFD sink device shall take place in the 4 following phases, as depicted in Figure 3. Figure 3: MirrorLink over Wi-Fi Display Diagram |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5.2 Phase 1: WFD Connection Setup | Phase 1 shall start when MirrorLink over Wi-Fi Display is switched on. In addition, if persistent WFD Group for MirrorLink exists, it is recommended that WFD Connection setup proceeds automatically without user interaction such as re-selection of WFD & CCC capable device. The following requirements apply to the phase 1... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5.3 Phase 2: UPnP Setup | Phase 1 shall be completed, before phase 2 can start. Figure 4: UPnP Setup Sequence Diagram UPnP Operation Start Based on the information within the CCC IE from the WFD device discovery and WFD connection setup stages, the MirrorLink device activates the respective UPnP components (i.e. TmServer Control Point or TmServ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5.4 Phase 3: WFD Session Setup | Phase 3 may start in parallel to the Phase 2, unless the WFD session has been setup outside the MirrorLink session. WFD TCP connection shall be established for the purpose of WFD RTSP procedures within the time limit specified in [5]. Similarly, the WFD session setup shall start after the establishment of TCP connectio... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5.5 Phase 4: WFD Operation | Phase 2 and 3 shall be completed, before phase 4 can start. During the WFD Operation phase, the WFD session is controlled from the MirrorLink Client, using RTSP commands and UIBC events. This allows the MirrorLink Client to start or pause the streaming of the MirrorLink Server's framebuffer. In case the MirrorLink Clie... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 5.6 Terminating a MirrorLink over WFD Session | MirrorLink Server and Client shall follow the procedures defined in the Core Specification [7] to disconnect a MirrorLink over WFD session. To avoid that graceful disconnection is leading to long response timeout, if the WFD peer is already disconnected or not responding anymore, the following behavior should be implem... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 6 WFD Audio | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 6.1 Audio Links | The selection of Audio links is specified in the respective Audio Specification [2]. ETSI ETSI TS 103 544-17 V1.3.1 (2019-10) 17 |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 6.2 WFD Audio Forward Channel | A MirrorLink Server shall use WFD's AV transport to provide media audio to the MirrorLink Client. The MirrorLink Client shall not launch the MirrorLink Server's RTP Server. BT A2DP shall not be used together with WFD. An existing BT A2DP connection to the MirrorLink Client shall be disconnected by the MirrorLink Client... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 6.3 WFD Audio Back Channel | WFD does not provide an Audio Back Channel. In case the MirrorLink Client intends to setup an Audio Back Channel, it shall follow the regular MirrorLink mechanism, as specified in the Audio Specification [2]. In case the MirrorLink Client intends to use RTP, it shall launch the MirrorLink Server's RTP Client. In case t... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 6.4 Telephony over WFD | BT HFP should be used to implemented telephony functionality over WFD. In this case, the MirrorLink Client shall launch the MirrorLink Server's BT HFP endpoint. The MirrorLink Client may use RTP based telephony audio, if supported from the MirrorLink Server. In this case, the MirrorLink Client shall launch the MirrorLi... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7 WFD User Input | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.1 General | MirrorLink Server and MirrorLink Client shall support User Input Back Channel as a mandatory feature of MirrorLink, through which the user input from user interface displayed at MirrorLink Client could be communicated back to MirrorLink Server. In addition, user interface related output and status events are exchanged ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2 UIBC Input Body Format for MirrorLink | |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.1 General | The payload structure for packetizing UIBC user inputs are specified in clause 4.11.1 (UIBC Data Encapsulation) of [5]. NOTE: The UIBC input body field should be padded up to an integer multiple of 16 bits to have an even integer number in the Length field as recommended in the WFD specification [5]. All MirrorLink spe... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.2 Key Event | The User Input Descriptor field of the MirrorLink UIBC Input message for the Key Event Input Type ID is shown in Table 3. Table 3: User Input Descriptor Field for Key Events Field Size (Octet) Notes Down Flag 1 Non-zero (true) if the key is now pressed, zero (false) if it is now released. Key Symbol Value 4 Key Symbol ... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.3 Pointer Event | The User Input Descriptor field of the MirrorLink UIBC Input message for the Pointer Event Input Type ID is shown in Table 4. The pointer event indicates either pointer movement or a pointer button press or release. Table 4: User Input Descriptor Field for Pointer Events Field Size (Octet) Notes Button Mask 1 Current s... |
844012584c35cdc9a9f41c91e3bc294e | 103 544-17 | 7.2.4 Touch Event | User Input Descriptor field of the MirrorLink UIBC Input message for the Touch Event Input Type ID is shown in Table 5. Touch events are used to describe touch screen action in which the user touches the screen with multiple individual fingers at different locations. The coordinate origin (0, 0) is defined to be the to... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.