hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.2 Receiver Baseline Sensitivity (RBS) | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.2.1 Definition | Receiver baseline sensitivity is the capability to receive a wanted signal at application or use case related defined input signal levels while providing a pre-determined minimum acceptable level of performance. Applications notes: • The purpose of the sensitivity requirement is to assure a basic measure of efficient u... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.2.2 Applicability | The receiver baseline sensitivity requirement is applicable to all devices addressed by the present document. Application notes: • Excluded from applicability of this requirement are transmit-only devices. • The TB addressing the excluded requirement will have to devise appropriate text. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.2.3 Limits | Receiver baseline sensitivity shall be better than <xx> dBm (or <yy> dBm/MHz) under the following operating conditions: Application notes: • The operating conditions include the signal levels, bandwidth, antenna parameters and pass/fail criteria. The specified operating conditions may need to be translated into measure... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.2.4 Conformance | The corresponding measurement description is in the RBS conformance test clause <x.y>. Application notes: • In the present document, model of conformance test clause is given in clause 6.2. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.3 Receiver Baseline Resilience (RBR) | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.3.1 Definition | Receiver Baseline Resilience (RBR) is defined as the capability to maintain a pre-determined minimum acceptable level of performance in the presence of unwanted signals over the frequency band of operation, applicable adjacent and remote frequency bands. Application notes: • The purpose of the RBS requirement is to ass... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.3.2 Applicability | The RBR requirement is applicable to all devices addressed by the present document. Application note: • Excluded from applicability of this requirement are transmit-only devices. For such devices other criteria apply, e.g. as documented by ECC sharing studies and reports or EU regulation. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.3.3 Limits | Receiver baseline resilience shall be better than the pass/fail criteria given below under the operating conditions in Table <X>. The pass/fail criteria for the RBR requirement are: • No loss of connection with any of the unwanted signals applied. • No loss of transmitted data with any of the unwanted signals applied. ... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 5.3.4 Conformance/Testing for compliance with technical requirements | The corresponding measurement description is in the RBR conformance test clause <x.y>. Application notes: • In the present document, model of conformance test clause is given in clause 6.3. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6 RX conformance tests | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.1 Introduction | In this clause, considerations regarding conformance tests are presented that cover the RBS and RBR measurements. These considerations need to be adapted and extended by the responsible TB during the development of the Harmonised Standard to the actual needs of the devices under test based on their intended use. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.2 Conformance test for RBS | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.2.1 General | The basic test setup of a RBS test is depicted in following clauses. The RBS conformance test is in main part equivalent to the sensitivity test given in ETSI EG 203 336 [i.1]. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.2.2 Test setup | The test can be performed based on radiated and conducted measurements. In Figure 1, a test setup for a radiated measurement of receiver baseline sensitivity is depicted. ETSI ETSI TS 103 567 V1.1.1 (2019-09) 20 Figure 1: Radiated test setup receiver baseline sensitivity with distance as parameter for a communication d... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.2.3 Test procedure | The tests should define the minimum requirement for efficient spectrum use. To avoid having to measure the actual signal level at the receiver, which may be impractical or even impossible depending on the application, the tests require a certain quality of reception for a given separation distance dRBS between transmit... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.3 Conformance test for RBR | |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.3.1 General | The basic test setup of a RBR test is depicted in following clauses. Depending on the specified frequency ranges, used signal formats and number of signals the RBR conformance test is equivalent to receiver parameter given in ETSI EG 203 336 [i.1]. |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.3.2 Test setup | Receiver baseline resilience tests the robustness of the receiver in the presence of interfering signals. For communication devices, the RUT and the companion transmitter shall be placed at a separation distance dRBR of each other. If the manufacturers documentation indicates that the RUT and/or companion transmitter h... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 6.3.3 Test procedure | The test procedure for both communication and radio determination devices is split into two sections. Section 1: Test without the interfering signal. Section 2: The interfering signal defined in the conformance section will be switched on. Receiver under Test (RUT) Equipment under Test Companion transmitter dRBR Interf... |
addbe6955c41c1dff477fce82e183929 | 103 567 | 7 Summary and conclusion | The present document provides a limited set of baseline receiver requirements to address the spectrum efficiency requirements of the RED and provides a sound basis to justify the use of this set in Harmonised Standards to claim presumption of conformity. It addresses the Assessment of Compliance of Documents drafted by... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 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... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 2 References | |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 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... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 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... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 3 Definition of terms, symbols and abbreviations | |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 3.1 Terms | Void. |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 3.2 Symbols | Void. |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: HUD Head Up Display ICD Instrument Cluster Display RTP Real-Time Protocol SBP Service Binary Protocol UIBC User Interface Back Channel VNC Virtual Networking Computing WFD Wi-Fi Display |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 4 Data Service Definition | |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 4.1 Media Meta Data Service Version 1.0 | /** The present document defines data objects for the Media Meta * data service to be carried over the SBP. By receiving * this data, the Media Data Sink (e.g. a car) can provide variety * media information to the driver and passenger through instrument * cluster display panel, HUD etc. * The Media Meta Source may be i... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 5 SBP Binding | |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 5.1 Service Registry | The Media 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 MediaPlayerStatus READABLE ON_CHANGE N/A N/A CurrentMediaItem READABLE ON_CHANGE N/A N/A NextMediaItem READABLE ON_CHANGE N/A N/... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 5.2 Service Specific Error Codes | |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 5.2.1 General | The Media Meta data service defines the following service specific error codes, used within an SBP::Response. The Media Meta data service shall not terminate in response to any service-specific error. The Media Meta data service source shall send the respective error response, but shall otherwise ignore the command. |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 5.2.2 Access to ControlMediaItem Object | The following error codes are defined, accessing the ControlMediaItem object: 0x40000 0000: command not known. This error code is sent, when the sink selects a media item not defined in the enumeration. 0x40000 0001: command not supported. This error code is sent, when the sink is sending a command not supported from t... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 6 Theory of Operation | |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 6.1 Subscribing to Current and Next Media Items | Figure 1 shows how a media data sink retrieves meta data about the currently played media from the media data source and displays it e.g. on the Instrument Cluster Display (ICD). ETSI ETSI TS 103 544-24 V1.3.1 (2019-10) 10 Figure 1: Message Sequence Diagram - Retrieve Media Meta Data of currently played Media It consis... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 6.2 Subscribing to Playback Position | Figure 2 shows how a media data sink retrieves meta data about the current playback position, for the current media playback, from the media data source and displays it e.g. on the Instrument Cluster Display (ICD). Figure 2: Message Sequence Diagram - Retrieve Media Meta Data of currently played Media It consists of th... |
030ba88e7f252f498ddd56076c8e8d2a | 103 544-24 | 6.3 Remote Control the Media Source | Figure 3 shows how a media data sink can remote control the media data source. To support the remote-control mechanisms, the Media Data Source is required to support the ControlMediaItem object. An example message sequence diagram is shown in Figure 3. SBP Server (Media Source) SBP Server (Media Source) SBP Client (Med... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 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... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 2 References | |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 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... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 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... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 3 Definition of terms, symbols and abbreviations | |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 3.1 Terms | Void. |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 3.2 Symbols | Void. |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CDB Common Data Bus EIR Extended Inquiry Response IVI In-Vehicle Infotainment system MAC Medium Access Control NFC Near Field Communication OOB Out of Band SBP Service Binary Protocol SSP Secure Simple Pairing USB Universal Serial Bus |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 4 Data Service Definition | |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 4.1 Bluetooth Out-of-Band Pairing over MirrorLink Version 1.0 | /** The present document defines data objects for the Bluetooth out-of- * band pairing using SBP is modelled after the Bluetooth out-of-band * pairing using NFC as described in [1]. Objects and data structures * are similar to the ones defined in that document. * @version 1.0 */ SERVICE com.mirrorlink.ml_bt_oob_pairing... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 5 SBP Binding | |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 5.1 Service Registry | The Bluetooth Out-of-Band Data Services uses the following objects and their access capabilities. Table 1 Object Name Access Type Subscription Type StaticClientConfig READABLE NONE StaticServerConfig CONFIGURABLE NONE DynamicClientConfig READABLE ON_CHANGE DynamicServerConfig CONFIGURABLE NONE Bluetooth_Handover_Reques... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6 Theory of Operation | |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.1 General | The obligation for this feature is CONDITIONAL. A MirrorLink Client and Server, supporting Bluetooth within a MirrorLink session, shall support this feature. The user may disable/enable the automatic pairing feature. MirrorLink Clients and Servers shall both support sending OOB information to enable OOB authentication ... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2 SBP Protocol | |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.1 General | The MirrorLink Client shall include the ml_bt_oob_pairing Service into the CDB service listing, prior to launching any Bluetooth module via an UPnP launch application action, unless the MirrorLink Client is already paired with the MirrorLink Server. The MirrorLink Client shall include the ml_bt_oob_pairing Service into... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.2 Bluetooth Radio Status Monitoring | Once the CDB Service has been launched, the following steps shall be executed: 1) The MirrorLink Server shall do a SET operation for the StaticServerConfig object. 2) The MirrorLink Server shall do a GET operation for the StaticClientConfig object. 3) The MirrorLink Server shall do a SET operation for the DynamicServer... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.3 Out-of-Band Pairing Configuration | If the Bluetooth radio of both devices is switched on, i.e. DynamicServerConfig::DynamicConfig.radioStatus and DynamicClientConfig::DynamicConfig.radioStatus are set to TRUE, the following steps shall be executed: 1) The MirrorLink Server shall evaluate its paring status with the MirrorLink Client's Bluetooth device an... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.4 Handover Request & Selection | If the MirrorLink Server and Client support Bluetooth OOB pairing over SBP and if at least one of both devices are not paired, i.e. either DynamicClientConfig::StaticConfig::pairingStatus or DynamicServerConfig::StaticConfig::pairingStatus is FALSE, the following steps shall be executed: 1) The MirrorLink Server may de... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.5 SSP Commencement | The MirrorLink Server shall then commence the Bluetooth SSP OOB pairing per the sequence described in [2] [Vol 2] Part F, clause 4.2.16 and depicted in Figure 4.20. |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.6 Post-Pairing Connection | The Bluetooth pairing, after the Bluetooth Handover Request and Select messages have been exchanged shall follow Bluetooth Secure Simple Pairing ([2] [Vol 2] Part F, clause 4.2, Figure 4.3): 1) The MirrorLink Client shall initiate the pairing, if the MirrorLink Client has set StaticClientConfig::StaticConfig.startConne... |
5a3a8b3612011c354d039f7ac8c33cf7 | 103 544-23 | 6.2.7 Timeout Considerations | In case the MirrorLink Server fails to receive a response from the MirrorLink Client to a GET operation within 10 s, it should stop the CDB service and start it again. If the MirrorLink Server fails to succeed, it shall give up latest after the 3rd re-start and shall fallback to manual Bluetooth pairing. In case the Mi... |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 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... |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 2 References | |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 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... |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 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... |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 3 Definition of terms, symbols and abbreviations | |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 3.1 Terms | Void. |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 3.2 Symbols | Void. ETSI ETSI TS 103 544-7 V1.3.1 (2019-10) 6 |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: GPS Global Positioning System NMEA National Marine Electronics Association SBP Service Binary Protocol |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 4 Data Service Definition | |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 4.1 GPS Data Service Version 1.0 | /** The purpose of GPS service is to provide better GPS data in car * environments. The specification relies on NMEA as bearer of GPS * data. * @version 1.0 */ SERVICE com.mirrorlink.GPS { /** SUPPORTED_SENTENCES */ ENUM<INT> SUPPORTED_SENTENCES { /** SUPPORT_GGA */ SUPPORT_GGA = 0x01, /** SUPPORT_GLL */ SUPPORT_GLL = ... |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 4.2 GPS Data Service Version 2.0 | SERVICE com.mirrorlink.GPS : @version 1.0 { ENUM<INT> definedCoordinateSystem { /** WGS-84 coordinate system * @mandatory */ CS_WGS84 = 0x00000001; /** GCJ-02 coordinate system * @optional */ CS_GCJ02 = 0x00000002; /** GCJ-02 coordinate system * @optional */ CS_Proprietary = 0x80000000; }; /** This object returns bit f... |
9aa01ef631e15187811700467bccd6e1 | 103 544-7 | 5 SBP Binding | The GPS Data Services uses the following objects and their access capabilities: Object Name Access Type Subscription Type NMEA READABLE ON_CHANGE, REGULAR, or AUTO NMEA_description READABLE NONE availableCoordinateSystems READABLE NONE currentCoordinateSystem CONFIGURABLE NONE If the SBP Source endpoint's geolocation s... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 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... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 2 References | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 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... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 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... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 3 Definition of terms, symbols and abbreviations | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 3.1 Terms | Void. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 3.2 Symbols | Void. |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface BOM Byte Order Mark CDB Common Data Bus EBNF Extended Backus-Naur Form INT INTeger IP Internet Protocol LSB Least Significant Bit MSB Most Significant Bit SBP Service Binary Protocol TCP Transmission Contr... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 4 MirrorLink® Data Service Architecture | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 4.1 Overall Architecture | MirrorLink Data service is composed of CDB, service framework and service provider/subscriber. CDB is the underlying multiplexing layer which also provides service discovery feature. On top of it, service framework layer allows implementing a new service in easier way by providing common abstraction for service provide... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 4.2 Version convention | CDB and service framework layers are bound under the same version number provided from CDB. In other words, the service framework layer does not have separate version number. CDB version number will be updated when there is an update in CDB or service framework layer. This present document, goes together with the CDB v... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 4.3 Starting Data Service | MirrorLink data service requires CDB as underlying layer. And to use data service, CDB should be launched by via UPnP application launch mechanism [3]. Note that there is no separate application for data service, and launching CDB is enough. More details on discovering CDB services can be found from clause 5.3 of CDB s... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 4.4 Data Service Security with Device Attestation Protocol | CDB can support payload encryption by using a pre-arranged session key. In the current MirrorLink architecture, the session key can be acquired after attestation of CDB in MirrorLink Server side by utilizing Device Attestation Protocol [4]. The application public key generated from the attestation of CDB is the session... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5 Service Framework: Service BINARY Protocol (SBP) | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.1 Introduction | As a basic data representation mechanism in the service framework layer, we have preferred binary version compared to XML mainly for performance reason. Due to that, a new binary protocol for service framework, SBP (Service Binary Protocol) was defined. Even if the service framework is based on binary protocol, it is i... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.2 Service Description Example | Service description can be done by defining data objects including member variables. Mechanism for subscribing the data objects will be explained later. Let's assume an example service with the name of "com.mirrorlink.sensor_example". The name is used to uniquely identify the service in CDB layer. Figure 2 shows data o... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.3 Data representation | Data in SBP is represented as in Table 1 using Extended Backus-Naur Form (EBNF). Table 1: Binary representation of data in EBNF EBNF Form No Matching data_type data = data_type, value | 1 BOOLEAN, BYTE, SHORT, INT, LONG, FLOAT, DOUBLE data_type, no_elements, {value} | 2 BYTES, STRING data_type, element_data_type, no_el... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.4 Command representation | Compared to data representation, there is only one type of EBNF for command as shown in Table 5. Table 5: Binary representation of command in EBNF command = command_type, payload_length, UID, packet_id, value, no_elements, {data_with_UID}, END_C; Table 6 describes symbols used in EBNF of command. Table 6: Description o... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5 Command Sequences | |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.1 General | This clause shows how commands are related with each other by showing sequences and examples. Note that each command sequence shall share the same packet_id. Any AuthenticationChallenge-AuthenticationResponse phase, which is actually a sequence, following a Get/Set/Subscribe command, shall have the same packet_id as th... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.2 Get, [{Response-Continue}], Response | Get is used to fetch an Object data once. For protected object, optionally, authentication can be requested in the middle. When the authentication stage is included, service SBP Source will send AuthenticationChallenge message and SBP Sink shall respond with AuthenticationResponse. After the OPTIONAL authentication, Re... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.3 Set, [{Response-Continue}], Response | Set is used to set an object to the desired state. Set operation is similar to writing to hardware registers which will trigger some action. As it is the case with hardware register, successful write does not necessarily mean that the object, when read back, will have the same value as requested via Set. The example be... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.4 Subscribe, {Response-OK/NOK}, [{Response}] | Subscribe command is used to request asynchronous notification for the object. Notification can be requested either in regular interval or on change of data. Depending on the service, sending data in regular interval or on change need not make sense, and in that case, only one mechanism will be supported. SBP Source sh... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.5 Cancel, Response | Cancel command stops the currently active Get, Set, or Subscribe command. Upon receiving this command, SBP Source should cancel the processing for the requested command. The example in Table 12 shows how the thermometer object, subscribed before, can be cancelled. ETSI ETSI TS 103 544-6 V1.3.1 (2019-10) 22 Table 12: Ex... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.6 AuthenticationChallenge, AuthenticationResponse | SBP Source can send AuthenticationChallenge after receiving Get/Set/Subscribe command for an object which requires authentication. The current specification does not define any authentication mechanism, and version 1.0 service SBP Source should not use this command unless service specific authentication is defined. But... |
d382d432cbe5f12db5f2f201512a616c | 103 544-6 | 5.5.7 AliveRequest, AliveResponse | AliveRequest is used by SBP Sink to check if the SBP Source is alive or not. As it is the case with other commands, upon receiving this command, SBP Source should reply with AliveResponse within 5 seconds. Failure to do that shall be interpreted as an irrecoverable error by SBP Sink. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.