hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 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 CDB session (either initiated automatically or manually from the user), whenever the CDB Server endpoint has intentionally terminated the CDB session. If the MirrorLink Client is in a dedicated test... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5 Message Types and Format | |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.1 Message Overview | The Common Data Bus (CDB) defines the following messages, which are specified in more detail in the following paragraphs: • ServicesRequest: Requests the list of supported services • ServicesSupported: Provide a list of supported data services • StartService: Request to start a specific service • StopService: Request t... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.2 ServicesRequest | The ServicesRequest message is used from the CDB Sink endpoint to request the list of supported services from the CDB Source endpoint. Table 1: ServicesRequest Message # bytes Type Value Description 2 U16 0xB101 Message-type 2 U16 2 Payload length 1 U8 1 CDB sink endpoint major version 1 U8 1 CDB sink endpoint minor ve... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.3 ServicesSupported | The ServicesSupported message shall be used from the CDB Source endpoint to notify the CDB Sink endpoint about the data services it can provide. Table 2: ServicesSupported Message # bytes Type Value Description 2 U16 0xB102 Message-type 2 U16 4+M Payload length 1 U8 1 CDB source endpoint major version 1 U8 1 CDB source... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.4 StartService | The StartService message is used from the CDB Sink endpoint to signal to the CDB Source endpoint to start a specific service and commence putting data packets related to that data service on to the common data bus. Table 4 specifies the format of the message. Table 4: StartService Message # bytes Type Value Description... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.5 StopService | The StopService message is used from the CDB Sink endpoint to signal to the CDB Source endpoint to stop a specific service and stop putting data packets related to that service on to the common data bus. Table 5 specifies the format of the message. Table 5: StopService Message # bytes Type Value Description 2 U16 0xB10... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.6 ServicePayload | The ServicePayload message delivers data from one CDB endpoint to the other one for any of the services, which have been started. The payload can have any data format of its own depending on the available services. The specification of the service payload is done within separate specifications and is out of the scope o... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.7 ServiceResponse | The ServiceResponse message shall be used from the CDB Source or Sink endpoint to respond to a message send from the CDB Sink or Source endpoint respectively (refer to Table 12 for details). Table 7 specifies the format of this message: Table 7: ServiceResponse Message # bytes Type Value Description 2 U16 0xB107 Messag... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.8 ByeBye | This message shall be used from either the CDB Source or Sink endpoint to terminate the Common Data Bus endpoint. Table 9 specifies the format of this message: Table 9: ByeBye Message # bytes Type Value Description 2 U16 0xB109 Message-type 2 U16 0 Payload length Sending and receiving a ByeBye message shall terminate t... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.9 Ping | The Ping message may be used from either side, to check if the other side is still alive. The endpoint, receiving a ping message, shall reply with a PingResponse message containing the sequence number. Table 10 specifies the format of the Ping message. Table 10: Ping Message # bytes Type Value Description 2 U16 0xB108 ... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 5.10 PingResponse | The PingResponse message shall be used from either side, to respond to a Ping messages. The receiving endpoint should send the PingResponse message, prior sending any other message. Table 11 specifies the format of the PingResponse message. Table 11: PingResponse Message # bytes Type Value Description 2 U16 0xB106 Mess... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 6 Message Flow | Table 12 summarizes the CDB Sink and Source Endpoint's message flow, it shall follow. The sending endpoint is given in brackets in the Message Received column. Table 12: CDB Message Flow Message Received (from) Message Responses Comment ServicesRequest (Sink) ServicesSupported - ServiceResponse (0x0209) Wrong CDB versi... |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 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... |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 2 References | |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 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... |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 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... |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 3 Definition of terms, symbols and abbreviations | |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 3.1 Terms | Void. |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 3.2 Symbols | Void. ETSI ETSI TS 103 544-19 V1.3.1 (2019-10) 6 |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Access Point SBP Service Binary Protocol |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 4 Data Service Definition | |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 4.1 Network Info Data Server Version 1.0 | /** The purpose of Network Information service is to provide network * capabilities and status of the Access Point to Client. * When MirrorLink Server and Client are connected though Wi-Fi * technology of Wi-Fi Alliance, both the ML Server and the Client * can be either an Access Point (AP) or Client. In-vehicle settin... |
76c23bf750b18e288f6d40341bdc099e | 103 544-19 | 5 SBP Binding | The Network Information Data Services uses the following objects and their access capabilities. Table 1 Object Name Access Type Subscription Type NetworkSupport READABLE NetworkStatus READABLE ON_CHANGE, AUTO DataBalanceStatus READABLE The data sink should first Get NetworkSupport Object, and then it should subscribe N... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 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... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 2 References | |
485e493b19ce8b72b583f4b758118b2f | 103 544-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... |
485e493b19ce8b72b583f4b758118b2f | 103 544-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... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 3 Definition of terms, symbols and abbreviations | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 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 ... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 3.2 Symbols | Void. |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: A2DP Bluetooth Advanced Audio Distribution Profile API Application Programming Interface BT Bluetooth BTA2DP Bluetooth Advanced Audio Distribution Profile BTHFP Bluetooth Hands Free Profile ETSI ETSI TS 103 544-3 V1.3.1 (2019-10) 8 BVRA Blueto... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 4 Introduction | The present document defines how the MirrorLink Client selects the transport media that the MirrorLink Server shall use to route audio streams. The MirrorLink Server distinguishes between two audio streams, namely phone and application audio. It advertises available transport options, using UPnP TmServerDevice:1 servic... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 5 Audio Link Options | MirrorLink allows the MirrorLink Client and Server to use the following audio features: • Media - Streaming of media audio from the MirrorLink Server to the MirrorLink Client; media audio feature includes navigation audio. • Phone - Bidirectional streaming of conversational audio, including in-band ringing. • VC - Stre... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 6 Audio Link Selection | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 6.1 General | The TmApplicationServer:1's service shall be used for controlling audio streams. Each type of audio source or sink on the MirrorLink Server is considered a remote application which can be remotely controlled by the MirrorLink Control Point using TmApplicationServer:1 service. The audio servers and clients can be starte... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 6.2 Identification of Available Audio Links | The identification of audio links is described in [8]. |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 6.3 LaunchApplication (AppID, ProfileID) | The LaunchApplication() action shall be used to start the audio streaming on the MirrorLink Server side and therefore select the underlying audio link. The response received will be an URI to the audio streaming sources/sinks using the audio streaming protocol identifier. The URI shall follow the A_ARG_TYPE_URI definit... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 6.4 TerminateApplication (AppID, ProfileID) | The TerminateApplication() action shall be used to stop the audio streaming (in either direction) on the MirrorLink Server side and follows the specification [8]. Invoking the TerminateApplication action causes the corresponding audio link to be closed. ETSI ETSI TS 103 544-3 V1.3.1 (2019-10) 15 Figure 3: Message Flow ... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 6.5 GetApplicationStatus (AppID, ProfileID) | The GetApplicationStatus() action provides the current status of an audio server or client running on the MirrorLink Server and is following [8]. The return values (of the type A_ARG_TYPE_AppStatus) specified for this SOAP action can be any of the following: • Foreground: Audio link is launched. • Background: Not used.... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7 RTP Audio Streaming | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.1 General | The audio RTP server and client on the MirrorLink Server listen on pre-specified ports, which are advertised using UPnP mechanisms. When the audio server captures audio data, it will encode the audio into RTP packets using the negotiated RTP Payload type and transmit the RTP packets over UDP/IP. The audio client is ful... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.2 RTP Packet Structure and Header Definition | RTP packets contain the standard RTP message header and the payload. Usually each RTP packet audio payload contains a predefined amount of audio data, but in a special case of end of stream (M=1), payload can be zero length. Therefore, the RTP client should not assume fixed payload length. Each RTP packet audio payload... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.3 RTP Audio Payload Definition | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.3.1 General | RTP payload length and sampling frequency shall be negotiated beforehand. This shall be done using UPnP mechanisms as defined in [8] and [9]. The following paragraphs define the audio payload format for 8 and 16 bit audio samples. The RTP server should support payload type 0 (8 bit, 8 kHz, mono). Audio stream is mu-law... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.3.2 48 kHz, 16 Bit Audio Payload (Mono) | This payload type denotes uncompressed audio data samples using 16-bit signed representation with 65 535 equally divided steps between minimum and maximum signal levels, ranging from -32 768 to 32 767. The value is represented in two's complement notation and transmitted in network byte order (most significant byte fir... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.3.3 48 kHz, 16 Bit Audio Payload (Stereo) | This payload type denotes uncompressed audio data samples using 16-bit signed representation with 65 535 equally divided steps between minimum and maximum signal level, ranging from -32 768 to 32 767. The value is represented in two's complement notation and transmitted in network byte order (most significant byte firs... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.3.4 16 kHz, 16 Bit Audio Payload (Mono) | This payload type denotes uncompressed audio data samples using 16-bit signed representation with 65 535 equally divided steps between minimum and maximum signal levels, ranging from -32 768 to 32 767. The value is represented in two's complement notation and transmitted in network byte order (most significant byte fir... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.4 Establishing the RTP Connection | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.4.1 General | RTP streaming in MirrorLink is based on UDP, which is connectionless. Some level of initial connection is REQUIRED for the MirrorLink RTP Server to know the MirrorLink RTP Client's IP address and port number. |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.4.2 RTP Server within MirrorLink Server | When the MirrorLink Server takes on the role of the MirrorLink RTP server, the MirrorLink Client shall send an UDP packet, containing 1 byte to the port number and IP address assigned for the MirrorLink Server's audio server. NOTE: The content of the byte can be any arbitrary value. On reception of that UDP packet, the... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.4.3 RTP Server within MirrorLink Client | When the MirrorLink Client takes the role of the MirrorLink RTP Server, the MirrorLink Client shall use the destination IP address and port number from the UPnP LaunchApplication action's response. Therefore, there is no need to wait for the 1 byte UDP packet. The MirrorLink Client's RTP server will start RTP streaming... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 7.5 Client and Server Implementation | For each audio stream, the audio client should do local buffering of the incoming RTP packets and should start playing the audio, if the buffer is filled with a reasonable number of packets. This will allow compensating for potential jittering. The audio client shall compensate potential frequency differences between t... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 8 Voice Command Handling | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 8.1 General | Voice Commands allow the User to interact and control a MirrorLink application using voice, while being in a MirrorLink session. The Voice Command use case require the MirrorLink Client to have access to a microphone, which is used to capture the user's voice and stream the voice samples to the MirrorLink Server, which... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 8.2 VC over RTP with an Established VNC Session | MirrorLink Servers and Clients, supporting Voice Commands, shall support it over an RTP back channel with an established VNC session. The RTP back channel shall be established with the establishment of the MirrorLink Session. Implementation Note: MirrorLink 1.1 or 1.2 Clients may establish the RTP back channel later, w... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 8.3 VC over RTP with an Established WFD Session | MirrorLink Servers and Clients, supporting Voice Commands, shall support it over an RTP back channel with an established WFD session. The described RTP behavior, as described in clause 8.2, shall apply to a MirrorLink over WFD session in the same way, using the respective UIBC messages instead the VNC messages. |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 8.4 VC over RTP without a VNC/WFD Session | Voice Commands over an RTP back channel, without an established VNC or WFD session is not possible. User may need to first launch an application, or bring an already running application into the foreground on the MirrorLink Client. Alternatively, applications may send a UPnP notification, to have the MirrorLink Client ... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 8.5 VC over Bluetooth HFP BVRA | MirrorLink Servers and Clients, supporting Voice Commands, may support it over Bluetooth HFP BVRA. In case Bluetooth HFP with BVRA support is established within MirrorLink, Voice Command capabilities shall provide the same capabilities as described in clause 8.2. In case Bluetooth HFP with BVRA support is established o... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 9 Interoperability with Bluetooth | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 9.1 General | Interoperability (IOP) of the MirrorLink RTP streaming audio framework with Bluetooth audio profiles shall be given. Bluetooth can be used to replace missing or existing RTP audio streaming functionality as defined in this MirrorLink specification. The MirrorLink Server shall at least distinguish between speech (phone ... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 9.2 Bluetooth Profiles relevant for MirrorLink | Bluetooth Headset Profile (BT HSP) [3] Bluetooth Headset profile (BT HSP) shall not be used in MirrorLink. Bluetooth Hands-Free Profile (BT HFP) [2] If Bluetooth Hands-free profile (BT HFP) is used for voice call together with RTP streaming for application audio, it is the responsibility of the MirrorLink Server to tak... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 9.3 Interoperability States - MirrorLink Server Perspective | Within the MirrorLink context, the following Interoperability (IOP) states with Bluetooth (BT) can be distinguished, as shown in Figure 13 from the CE MirrorLink Server, i.e. the CE device perspective: • MirrorLink Server has established neither any MirrorLink and nor any legacy Bluetooth connections (State: None) NOTE... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 9.4 Interoperability States - MirrorLink Client Perspective | Within the MirrorLink context, the following Interoperability (IOP) states with Bluetooth (BT) can be distinguished, as shown in Figure 14 from the MirrorLink Client, i.e. Head-Unit perspective: • MirrorLink Client has established neither any MirrorLink and nor any legacy Bluetooth connections (State: None) • MirrorLin... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 10 Audio Signal Processing Configuration | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 10.1 Conversational and Telephony-based Audio | In order to optimize perceived audio quality during conversational audio sessions in MirrorLink, clients and servers should conform to audio performance specifications and behaviours as defined in Recommendation ITU-T P.1100 [i.3]. To achieve this, the MirrorLink Server should disable all audio signal processing functi... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 10.2 Bluetooth HFP Noise Reduction/Echo Cancellation | In HFP specification, all audio signal processing in the MirrorLink Server should be disabled in correlation with the HFP requirements specifying AG Noise Reduction/Echo Cancellation. NOTE: It is assumed that a MirrorLink Server always perform the role of Hands-Free Profile Audio Gateway, as this is the primary way to ... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 10.3 RTP-based Conversational Audio | If a MirrorLink Client establishes an RTP connection for call or conversational audio usage, the MirrorLink Server should disable all local audio signal processing. The server should re-enable audio signal processing functions upon disconnection of RTP for conversational audio (i.e. call audio transfer to the MirrorLin... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 10.4 RTP-based Voice Command Audio | For Voice Command processing, over RTP the MirrorLink Client shall optimize its local audio signal processing for this use case. |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 11 Latency Switching Sources | |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 11.1 General | Latency Switching Sources (LSS) describe the problem that switching between different audio sources on a MirrorLink Client can take time. The audio switch has an unspecific latency. This clause describes how a MirrorLink application can be sure that it is audible via the MirrorLink Client, i.e. the switching has been d... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 11.2 Protocol Behaviour of Latency Switching Sources | An application, planning to send an audio stream, shall provide the intended Audio Context Information (MirrorLink API call 0x0803) to the MirrorLink Server. The MirrorLink Server shall send a silent audio stream, tagged with the provided audio context, in case no other MirrorLink audio source is playing; otherwise the... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 11.3 Timing Behaviour of Latency Switching Sources | Switching between a MirrorLink audio source and a local audio source on a MirrorLink Client will take time, time which is unknown in advance to the MirrorLink Client and Server, as it can dependent on the internal state of the audio system. For MirrorLink applications it is important though, to understand the time, a M... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 11.4 Use Cases for Latency Switched Sources | Based on above requirements, the following use cases are relevant: Blocking MirrorLink Server Audio with no presence of MirrorLink Client Local Audio The message sequence diagram in Figure 15 shows the application setting the audio context. The MirrorLink Server is sending a silent audio stream, which is responded by a... |
485e493b19ce8b72b583f4b758118b2f | 103 544-3 | 11.5 Backward Compatibility of Latency Switched Sources | Latency Switched Sources have been introduced in MirrorLink 1.3. Previous versions do not support this concept. Interoperability with MirrorLink 1.0 and 1.1 Servers MirrorLink 1.0 and 1.1 Servers do not support the specified concept Latency Switched Sources. Therefore, the MirrorLink Client shall not send an Audio Unbl... |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 1 Scope | The present document specifies Receiver Blocking for 5 GHz RLAN devices. |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 2 References | |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 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... |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 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... |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 3 Definitions, symbols and abbreviations | |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI EN 301 893 [1] apply. |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI EN 301 893 [1] apply. |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 301 893 [1] and the following apply: PER Packet Error Rate ETSI ETSI TS 103 521 V1.1.1 (2017-04) 6 |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4 Receiver Blocking for 5 GHz RLANs | |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.1 Receiver Blocking Specification | |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.1.1 Definition | Receiver blocking is a measure of the capability of the equipment to receive a wanted signal on its operating channel without exceeding a given degradation due to the presence of an unwanted input signal (blocking signal) on frequencies other than those of the operating bands provided in ETSI EN 301 893 [1], clause 1. |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.1.2 Performance Criteria | The minimum performance criterion shall be a PER of less than or equal to 10 %. The manufacturer may declare alternative performance criteria as long as that is appropriate for the intended use of the equipment. See clause 4.2.1. |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.1.3 Limits | While maintaining the minimum performance criteria as defined in clause 4.1.2, the blocking levels at specified frequency offsets shall be equal to or greater than the limits defined in table 1. Table 1: Receiver Blocking parameters Wanted signal mean power from companion device (dBm) Blocking signal frequency (MHz) Bl... |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.2 Receiver Blocking Test Method | |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.2.1 Test conditions | The UUT shall operate in its normal operational mode. This test shall be performed on one operating channel within each of the sub-bands defined in ETSI EN 301 893 [1]. Devices which can change their operating frequency automatically (adaptive channel allocation), this function shall be disabled. If the equipment can b... |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.2.2 Test Method | |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.2.2.1 Conducted measurements | For systems using multiple receive chains only one chain needs to be tested. All other receiver inputs shall be terminated. Figure 1 shows the test set-up which can be used for performing the receiver blocking test. The companion device may require appropriate shielding or may need to be put in a shielded room to preve... |
ad8e4aac65876491fd4b8d14e18be03f | 103 521 | 4.2.2.2 Radiated measurements | When performing radiated measurements on equipment with dedicated antennas, measurements shall be repeated for each alternative dedicated antenna. A test site as described in ETSI EN 301 893 [1], annex B and the measurement procedures as described in ETSI EN 301 893 [1], clause C.2 or clause C.3, shall be used. The tes... |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-1 | 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... |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-1 | 2 References | |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-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... |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-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... |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-1 | 3 Definition of terms, symbols and abbreviations | |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: pointer event: used to describe 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 dif... |
2036ee64178b23dc284cd6c6037dc9c3 | 103 544-1 | 3.2 Symbols | Void. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.