hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 3.2 Symbols | Void. |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: A2DP Bluetooth Advanced Audio Distribution Profile AP Access Point API Application Programming Interface BT Bluetooth CDB Common Data Bus CDC Communications Device Class NOTE: Specified from USB Device Working Group. DAP Device Attestation Pro... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 4 Introduction to MirrorLink | MirrorLink provides a concept for integrating the mobile device (hereinafter referred to as the "MirrorLink Server") and the vehicle head-unit (hereinafter referred to as the "MirrorLink Client"). In a MirrorLink context, the control and interaction of applications and services running on the mobile device will be repl... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 5 MirrorLink Architecture | The MirrorLink high-level architecture is shown in Figure 2. Figure 2: MirrorLink Architecture MirrorLink 1.1 Architecture consists of a set of protocols, providing the following features: 1) Connectivity, as specified in [1], providing: a) wired and wireless IP based connection-oriented and connection-less connectivit... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 6 MirrorLink Features | Table 1 specifies the requirements for the different MirrorLink features for the MirrorLink Server and Client and for which version the feature has been introduced. The version number given for a specific feature, highlights the MirrorLink version in which the feature has been introduced. The feature is available with ... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7 MirrorLink Session | |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.1 General | The high-level MirrorLink session diagram is shown in the following Figure 3. The MirrorLink flow starts with the user either actively connecting the MirrorLink Server device with a MirrorLink Client device, or by automatic connection, when coming into the vicinity of a MirrorLink Client device. Figure 3: High-level Mi... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.2 UPnP Operation Start | The sequence diagram of the UPnP operation start is given in the following Figure 4. The sequence shall follow UPnP device architecture specification as given in [29]. Figure 4: UPnP Operation Start Sequence Diagram In case the MirrorLink Server is connected via multiple interfaces (like Wi-Fi, USB), the UPnP Server De... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.3 MirrorLink Session Setup | |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.3.1 General | The sequence diagram of the MirrorLink session setup is given in Figure 5. The MirrorLink session shall start immediately after the UPnP Operation Start has been completed. ETSI ETSI TS 103 544-13 V1.3.1 (2019-10) 15 Figure 5: MirrorLink Session Setup Sequence Diagram The MirrorLink Client shall setup the MirrorLink se... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.3.2 Physical Interface Selection | The MirrorLink Client shall list all available alternative remote user interface mechanisms into the presentations list of A_ARG_TYPE_ClientProfile as defined in [10]. The list is independent of whether a particular mechanism is currently available due to the established physical connections. The MirrorLink Client shal... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.3.3 Setting the Client Profile | The MirrorLink Client shall set the respective Client Profile prior to using any other MirrorLink specific UPnP actions. The MirrorLink Client shall include all available remote user interface mechanisms into the presentations list within the UPnP A_ARG_TYPE_ClientProfile, as specified in [10]. The list is independent ... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.3.4 Executing Device Attestation Protocol | The MirrorLink Client shall retrieve the Application Listing from the MirrorLink Server to identify and to launch the Server's DAP endpoint. The MirrorLink Client shall execute the Device Attestation Protocol as specified in [4]. The MirrorLink Client shall immediately terminate any later established connection, if the... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.3.5 Establishing other Connections | The MirrorLink Client shall establish all necessary Audio (like RTP or Bluetooth) connections as well as the Common Data Bus connection, at the start of the MirrorLink session. The MirrorLink Server shall turn on Bluetooth and Bluetooth pairing shall be executed. The MirrorLink Server shall use the Bluetooth MAC addres... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.4 MirrorLink Operation | |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.4.1 Updating the Client Profile | Subsequent setting of the UPnP Client Profile by the MirrorLink Client shall overwrite any previous client profile setting for the same profile identifier, if the ClientID value in the Client Profile is identical to the original one. Subsequent setting of the UPnP Client Profile by the MirrorLink Client shall be denied... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.4.2 Changing the Physical Interface | In case the client profile is updated using another physical interface (e.g. Wi-Fi rather than USB), the MirrorLink Client shall immediately terminate any previously established connection, after receiving a successful response to the Set Client Profile action. NOTE: Updates to the physical transport may result in a di... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.4.3 Changing the Remote UI Mechanism | In case Remote UI Mechanisms become available or disappear during a MirrorLink session, after the initial interface has been selected, the MirrorLink Client should follow the state transition diagram shown in Figure 6. ETSI ETSI TS 103 544-13 V1.3.1 (2019-10) 18 Figure 6: Remote User Interface Transition Diagram The re... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.4.4 Disappearing Physical Interfaces | In case any of the physical connection suddenly disappear, e.g. as the user disconnects a wired connection, switches off a wireless radio, Figure 7 shows the resulting allowed transitions. Figure 7: Disappearing Physical Connection Transition Diagram An update to the selected remote user interface may result in a diffe... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.4.5 Legacy MirrorLink Mode | In case either the MirrorLink Client or the MirrorLink Server devices are MirrorLink 1.1 or MirrorLink 1.0 devices, HSML or WFD are not available for MirrorLink use. ETSI ETSI TS 103 544-13 V1.3.1 (2019-10) 19 In that case, the Remote User Interface Transition diagram simplifies to the diagram shown in Figure 8. Figure... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.5 MirrorLink Session Termination | The MirrorLink Server shall terminate an ongoing MirrorLink session, if the MirrorLink Client set the UPnP Client Profile to an empty String, i.e. ClientProfile equals "". Attempts to terminate the MirrorLink session shall be rejected from the MirrorLink Server, using "Error Code 701 - Operation Rejected", if the Mirro... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 7.6 Interoperability with other MirrorLink Versions | MirrorLink 1.3 devices shall interoperate with devices, implementing previous MirrorLink versions. NOTE: Limited or no interoperability is possible with MirrorLink 1.0 devices. MirrorLink 1.0 Client need not execute the DAP protocol and applications from MirrorLink 1.0 Servers are considered non-certified. The MirrorLi... |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 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... |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 2 References | |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 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... |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 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... |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 3 Definition of terms, symbols and abbreviations | |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 3.1 Terms | Void. |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 3.2 Symbols | Void. ETSI ETSI TS 103 544-27 V1.3.1 (2019-10) 6 |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CDB Common Data Bus SBP Service Binary Protocol UID Unique Identifier |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 4 Data Service Definition | |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 4.1 Basic Meta Data Service Version 1.0 | /** The present document defines a meta information umbrella service. * The present document is used as a basis for any Meta Information * Data service, improving on the low-level introspection mechanisms * offered by the CDB and SBP protocols. The service cannot be used * as a standalone service. * Any Meta Data Servi... |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 5 SBP Binding | The MetaInfoObjects object provides details on how the SBP Sink can access SBP objects from the SBP Source. An SBP Source shall allow access to each object, as defined within its MetaInfoObjects object. In case the SBP Sink attempts to access any of the SBP objects outside the allowed mechanism, the SBP Source shall se... |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 6 Theory of Operation | |
3140867072c4e62ff119a4da609b3831 | 103 544-27 | 6.1 Basic Operation | Figure 1 shows the basic operation of the Basic Meta Information data service. Figure 1: Sequence Diagram of Basic Service Operation It consists of the following steps: 1) CDB Client Endpoint sends a CDB ServicesRequest message, requesting the list of data services, provided from the CDB Server Endpoint. 2) CDB Server ... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 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... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 2 References | |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 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... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 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... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 3 Definition of terms, symbols and abbreviations | |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 3.1 Terms | Void. |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 3.2 Symbols | Void. |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface BT Bluetooth CCC Car Connectivity Consortium FB FrameBuffer FM Frequency Modulation HFP Bluetooth Hands-Free Profile HSML High Speed Media Link IOP InterOPerability ML MirrorLink RFB Remote Framebuffer RTP... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 4 Consumer Experience Principles | The MirrorLink consumer experience is guided by a set of principles. Those principles are not strictly enforceable, as they are described on a high-level. Therefore, no obligation language is used in their description. But devices failing those principles will typically violate one or more of the MirrorLink technical r... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5 Basic MirrorLink Features | |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.1 Introduction | This clause summarizes the consumer experience related requirements for the various MirrorLink features, which are available using the MirrorLink protocol. Requirements provided within this clause are complementary to requirements in the detailed MirrorLink protocol specifications. Nevertheless, in case of a contradict... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.2 First-Use Experience | The consumer installing MirrorLink on a supported mobile device is expecting an immediate first use experience, when connecting the device to a MirrorLink enabled in-vehicle infotainment system. ETSI ETSI TS 103 544-26 V1.3.1 (2019-10) 8 The following consumer experience requirements are defined: • If no MirrorLink cer... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.3 Download, Installation and Update of Applications | The consumer is able to download, install and update a suitable CCC or Member-certified application from any available application marketplace or via side-loading. In order to enable the consumer to use the application, e.g. while driving, the MirrorLink Server will need to evaluate the certification status prior first... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.4 Listing of MirrorLink Applications | The consumer is able to launch application via listings of MirrorLink applications. Application listings are provided from the MirrorLink Client, via native MirrorLink Client user-interfaces or from the MirrorLink Server, via dedicated Home Screen applications. Latter one is accessible only via a MirrorLink session. Th... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.5 Management of Certified Applications | In order to enable the consumer to use the application, e.g. while driving, the MirrorLink Server will need to continuously evaluate the certification status on a regular basis. This validation requires the consumer to have the device connected to the Internet: • The consumer shall have access to certified applications... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.6 Interacting with MirrorLink Applications | The consumer is able to interact with MirrorLink applications via Voice or Physical interaction with the Client devices user input controls, like the Client's touch screen, soft or hard buttons around the Client's screen or on the steering wheel. The following consumer experience requirements are defined: • All soft bu... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.7 Listening to Entertainment and Navigation Audio | The consumer has access to his/her favourite entertainment and navigation applications, either run remotely from the MirrorLink Server or locally from the MirrorLink Client. The MirrorLink Server is responsible for mixing all remote audio sources into a single audio stream, which is streamed to the MirrorLink Client. T... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.8 Transferring Audio to and from a MirrorLink Session | The consumer is using the mobile device with different audio accessories, like a Bluetooth or analogue audio connector. When connecting an audio accessory, entertainment audio is typically automatically transferred to the accessory and continues playing. When disconnecting the accessory, the entertainment audio is typi... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.9 MirrorLink Consistency, Robustness & Ease of Use | The consumer is using the mobile device within a MirrorLink session, it expects that whenever a connection is established, he/she has the same consistent experience as within the last session. The following consumer requirements are defined: • The application icons, presented to the consumer shall match the application... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.10 Phone Call Functionality | Consumers with MirrorLink enabled Server devices supporting phone call functionality, are expecting the same to be available via MirrorLink. Specifically, in coming phone calls, which may come in at any point in time during a MirrorLink session, need to be gracefully handled from the MirrorLink Server. The following co... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.11 MirrorLink Logo Use | Consumers with MirrorLink enabled devices, need to be aware that MirrorLink is available. The Car Connectivity Consortium has trademarked a MirrorLink logo and a MirrorLink Design-only icon for this purpose. The following consumer requirements are defined: • If the consumer is able to manually activate MirrorLink funct... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 5.12 Classic, Immersive and Legacy MirrorLink Mode | The consumer is expecting a seamless experience, when interacting with individual MirrorLink applications, switching between those and allowing to go back and forth to a native MirrorLink Client experience. MirrorLink aims to provide a user experience, where navigation mechanisms (e.g. buttons to switch between applica... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6 Minimum Baseline Performance | |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.1 General | All performance requirements are measured with no local applications running additionally on the target devices, unless those applications are needed for the correct operations of MirrorLink on those devices. |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.2 User Interface Performance | |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.2.1 VNC RAW/RLE Performance | In order to allow for a more optimized use of the available bandwidth for the VNC framebuffer transfer, the following requirements apply. The use case for these performance requirements is a map panning: • The MirrorLink Server shall be able to provide on average the full framebuffer update performance listed below, fo... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.2.2 HSML Performance | In order to allow for a more optimized use of the available bandwidth for the HSML framebuffer transfer, the following requirements HSML performance requirements apply: • The MirrorLink Server shall be able to provide on average the streaming performance listed below, for MirrorLink Client screen resolution of 800x480.... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.2.3 VNC VA H.264 Performance | In order to allow for a more optimized use of the available bandwidth for the VA H.264 framebuffer transfer, the following requirements VA H.264 performance requirements apply: • The MirrorLink Server shall be able to provide on average the streaming performance listed below, for MirrorLink Client screen resolution of ... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.3 Round Trip Latency | • The round-trip latency, i.e. the time from the consumer doing a touch or key event on the MirrorLink Client until a response from the MirrorLink applications is visible on the MirrorLink Client's display shall be less than 200 ms. NOTE: The round-trip latency is measured with a responsive test application. The Round ... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 6.4 Setting Up and Managing the MirrorLink Session | • The consumer shall be able to start MirrorLink from the MirrorLink Client not later than 2 000 ms after the MirrorLink Server has been connected to the MirrorLink Client, i.e. plugging in the USB cable, or after Wi-Fi P2P devices have been paired, or the consumer has executed a manual connection step on the MirrorLin... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 7 MirrorLink Application | |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 7.1 Introduction | The following clauses define the behavior and functionality for a set of MirrorLink applications, which can be relevant to achieve MirrorLink device certification. Dependent on the implemented MirrorLink Modes, a MirrorLink Server shall have all or some of them installed. ETSI ETSI TS 103 544-26 V1.3.1 (2019-10) 22 |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 7.2 Immersive & Classic Home Screen Application | A Home Screen application identifies a MirrorLink application, which provides a Home Screen experience, i.e. it allows the consumer to see a list of installed (certified) applications, and allows to launch them. Classic MirrorLink Mode A MirrorLink Server may provide a Classic Home Screen application (application categ... |
dc70dedd40dcb9cd1e8774a6e44ca321 | 103 544-26 | 7.3 Immersive & Classic Phone Call Application | A Phone Call application identifies a MirrorLink application, which provides a Phone Call experience, i.e. it allows the consumer place an outgoing call, accept/reject an incoming and/or manage an incoming call. Classic MirrorLink Mode A MirrorLink Server may provide a Classic Phone Call application (application catego... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 1 Scope | The present document specifies a limited set of baseline receiver requirements aiming to meet the essential requirements of Article 3.2 of the Radio Equipment Directive [i.4] by developing provisions for harmonised standards, see clauses 2.8.2 and 2.10.2 in Vademecum Part III [i.8] to support assessment of compliance o... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 2 References | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 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... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 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... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 3 Definition of terms, symbols and abbreviations | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 566 [i.2] apply. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TR 103 566 [i.2] and the following apply: dRBS reference distance for the definition of receiver sensitivity dRBR reference distance for the definition of receiver resilience dRBR_int reference distance for the interfering signal ETSI ETSI TS 103 567 V... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 103 566 [i.2] and the following apply: NZIF using Near-Zero Intermediate-Frequency technology RBR Receiver Baseline Resilience RBS Receiver Baseline Sensitivity RED Radio Equipment Directive RUT Receiver Under Test |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4 Existing RX requirements and Spectrum Efficiency | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.1 Introduction | Article 3.2 of the RED [i.4] calls of "effective and efficient use of radio spectrum" without providing guidance on the means or methods nor on the criteria to judge such use. Ideally, these criteria should be extractable from the relevant regulatory documents including ECC reports, decisions and recommendations. In or... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2 Classification of existing RX parameters [i.1] | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.1 Overview | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.1.1 Introduction | In general, two receiver properties contribute to the effectiveness and efficiency of spectrum utilization of a radio system: receiver sensitivity with regard to the wanted signal and receiver resilience with regard to unwanted signals. In this clause, a classification proposal for existing classical RX parameters is g... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.1.2 RX parameters related to sensitivity | Receiver sensitivity is determined by a number of factors, including receiver thermal noise, implementation margins, operating bandwidth, received signal modulation and the resistance to strong unwanted signals. Of these factors, operating bandwidth and signal modulation are fundamental determinants of receiver perform... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.1.3 RX parameters related to resilience | A receiver's performance in the presence of unwanted signals, its resilience, is affected by signals in different frequency bands: • In-band RX parameters: In this class, RX parameters related to in-band effects are summarized. In most cases no additional out-of-band interfering signals are considered in the test suite... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.2 Receiver Parameters proposed in ETSI EG 203 336 | ETSI EG 203 336 [i.1] lists a number of receiver parameters together with testing considerations. These RX parameters are listed in Table 1 below. ETSI ETSI TS 103 567 V1.1.1 (2019-09) 11 Table 1: RX parameters proposed in ETSI EG 203 336 [i.1] Performance criterion (PC): Objective testable BER, PER, FAR etc. at the ed... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.3 In-band RX parameters | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.3.1 Sensitivity | See ETSI EG 203 336 [i.1], clause 5.3.2. Receiver sensitivity is the ability to receive a wanted signal at a defined input signal level while providing a pre-determined level of performance. Receiver sensitivity should be included in Harmonised Standards because: • good sensitivity is generally valuable in minimizing i... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.3.2 Co-Channel rejection | See ETSI EG 203 336 [i.1], clause 5.3.3. Receiver co-channel rejection is a measure of the capability of a receiver to receive a wanted signal, without exceeding a given degradation, in the presence of an unwanted signal, both signals being at the nominal frequency of the receiver. When specifying tests for receiver co... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.3.3 Dynamic range | See ETSI EG 203 336 [i.1], clause 5.3.4.4.1. Receiver "dynamic range" is a generic term broadly defined as the range of input signal levels over which a receiver functions at a specified performance level. The "dynamic range" of a receiver may be specified in a Harmonised Standard by the selectivity parameters (see cla... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.3.4 Desensitization (In-band signals) | See ETSI EG 203 336 [i.1], clause 5.3.4.4.3. Desensitization is a degradation of receiver sensitivity caused by the presence of a large unwanted signal outside its operating channel or bandwidth. The term is most commonly applied when an unwanted signal is present in a receiver which is above the receiver's linear "dyn... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.4 Adjacent channel RX parameters | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.4.1 Adjacent signal selectivity (first and second adjacent channel) | See ETSI EG 203 336 [i.1], clause 5.3.4.3.3. Also named "Adjacent channel selectivity". Receiver adjacent signal selectivity (adjacent channel selectivity) can be part of multiple signal selectivity (more than one interfering signal) because attenuation of the interfering signal will require linear signal processing in... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.5 Remote band RX parameters | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.5.1 Blocking | See ETSI EG 203 336 [i.1], clause 5.3.4.3.1. Where relevant, Technical Bodies should also consider receiver blocking as a measure of the capability of a receiver to receive a wanted signal without exceeding a given degradation due to the presence of an unwanted input signal at any frequency other than those of the spur... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.5.2 Spurious response rejection | See ETSI EG 203 336 [i.1], clause 5.3.4.2.2. The spurious response rejection is a measure of the capability of the receiver to receive a wanted signal without exceeding a given degradation in to the presence of an unwanted signal at any frequency at which a response is obtained. The frequencies of the adjacent signals ... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.6 Combined band RX parameters | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.6.1 Reciprocal Mixing | See ETSI EG 203 336 [i.1], clause 5.3.4.4.2. Noise sidebands of the Local Oscillator (LO) mix with unwanted signals producing unwanted noise at the operational frequencies of the receiver which may result in degraded receiver sensitivity. In direct Digital Down Conversion receivers (DDC) a similar effect occurs caused ... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 4.2.6.2 Intermodulation | See ETSI EG 203 336 [i.1], clause 5.3.4.3.2. Radio-frequency intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal, without exceeding a given degradation in to the presence of at least two unwanted signals at frequencies F1 and F2 with a specific frequency relation... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5 Baseline Receiver parameters | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.1 Introduction | This clause provides models of clauses addressing Receiver Requirements which can be used as examples in the development process of new Harmonised Standards. The text“the present document” is included as reference to the Harmonised Standard using these models. The models of clauses are written in italics. The models of... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.