hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.2 mvmDataControlField (optional container) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.2.1 Introduction | The mvmDataControlField container is portrayed in Figure 34. It consists of a series of data elements that serve mainly for the purpose of control the bidirectional communication between the vehicles and the RO. This is equally available in the MVM structure. Contained data elements are: 1) mvmGenerationTime 2) rolling... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.2.2 mvmGenerationTime data element | The mvmGenerationTime data element is optionally. It is used for check on the data freshness on the receive side from message generation time included as part of the message transmission from the transmitter side. The format of the data element complies with CDD definition of TimeStampIts (ETSI ITS). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.2.3 rollingCounterFromMIM (sequence) | The data element rollingCounterFromMIM serves as a mirror of the rolling counters that were received with the latest, up to 10 MIM messages from the RO. It enables the RO to recognize whether the vehicle system has received fresh data from the vehicle or if there are lost messages in the radio transmission. ETSI ETSI T... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.2.4 proprietaryExtensionField (optional element) | This data element defines optionally 2 bytes are used to carry specific information or request from a specific SV to the RO, e.g. an information that the vehicle has entered a car wash station or opened the charging flap at an electric charging station. The bytes are unformatted, i.e. the format is only defined between... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.3 systemManagementData (optional container) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.3.1 Introduction | The systemManagementData container is portrayed in Figure 35. It consists of a series of optional data elements that serve for the purpose to exchange the identification labels of the bidirectional communication between the SVs and the RO. This is equally available in the MIM structure. Contained data elements are: 1) ... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.3.2 sessionID data element | The vehicle confirms the according sessionID of a MIM with this data element. The RO identifies herewith the response from the associated vehicle. Clause 7.4.3.2 explains that the sessionID is negotiated between the RO and vehicle systems outside the driving protocol. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.3.3 missionID data element | The missionID data element identifies a task that is negotiated and agreed upfront on both sides, the RO and the vehicle subordinated to an according sessionID date element. In MVM it has to comply with the current missionID data element of MIM. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 51 |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.3.4 vehicleID data element | The vehicleID data element is an optional identifier. The vehicle needs to know its own vehicleID, and this will be independent from sessionID values. The use of this data field corresponds to clause 7.4.3.4 in the MIM description and will be a mirror of the according vehicleID data element in MVM. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.3.5 facilityID data element | The data element provides the option for the identification of the infrastructure facility, e.g. a parking structure or a logistics depot, depending on the use case. It serves for documentation purposes and should be identical in the corresponding MIMs and MVMs. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4 vehicleState (optional container: VehicleState) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.1 Introduction | The vehicleState container carries signals about the actual status of the vehicle's condition with reference to the driving task. This return signals from the vehicle is usable in the RO subsystem for correction and refinement of the vehicle motion control VMC. The structure of the vehicleState container within the MVM... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.2 vehicleStateGenerationTime data element (optional) | This data element will be used for checks on the Data Freshness on receive side from Vehicle State Message generation from transmission point of View as Vehicle State Generation Time could originate from different module than radio transmitter module. The format of the data element complies with CDD definition of TimeS... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.3 operationMode data element | The data element operationMode comprises the modes described in Table 13 in response to the data element driveCommandAction within the MIM message. Table 13: operationMode values State Description unknown default value initializing The vehicle is preparing for the mission but has not entered automated mode yet. prepare... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.4 gearState data element | The data element gearSelected reports in analogy to the gear request in clause 7.4.7.4 the states described in Table 14. Table 14: gearState values State Description park P: Vehicle shall engage P. backwards R: Vehicle shall drive backwards. neutral N: Vehicle shall engage neutral gear. forwards D: Vehicle shall drive ... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.5 directionIndicatorState data element | The data element directionIndicatorState reports in analogy to the indicator request in clause 7.4.7.5 the states described in Table 15. Table 15: gearSelected states State Description off The vehicle does not flash indicator lights at this stage. right Right indicator lights flashing. left Left Indicator lights flashi... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.6 parkingBrakeState data element | The data element parkingBrakeState reports in analogy to the parking brake request in clause 7.4.7.6 the states described in Table 16. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 53 Table 16: parkingBrakeState values State Description unknown The status of the electric parking brake is unknown. engaging The parking brake is ... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.7 motorSystemState data element | The data element motorSystemState reports in analogy to the motor system request in clause 7.4.7.7 the states described in Table 17. Table 17: motorSystemState values State Description off Propulsion Motor off. on Propulsion Motor on. unknown The propulsion motor status is unknown (not used as a command). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.8 currentVelocity data element | The DE reports the current speed of the vehicle at the related local time stamp. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.9 currentCurvature data element | The DE reports the current curvature of the vehicle at the related local time stamp. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.10 secureStandstill data element | This is a Boolean data element reports a secured vehicle standstill, also on inclined roads. A secure standstill of the vehicle needs individually to be defined by the two partners of RO and VO subsystems and possibly includes the engagement of an electronic parking brake. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.11 idxLastWayPoint data element | The optional DE is a 2-byte value. It is referenced to the path snippet concept in clauses 7.6 and 7.6.3. The vehicle herewith reports to the RO subsystem index of the current wayPoint that has been passed in the array of consecutive wayPoints. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.12 localizedPose (container: Pose) | The AVM system permanently senses the vehicle's position in a relative two-dimensional coordinate system (X and Y). In this optional container the vehicle reports its x, y position and heading psi with regards to the latest RO position and the delta movement calculated by vehicle odometry data. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.13 x data element | This data element is 20 bit for the x position of the way point. Resolution is 1 cm. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.14 y data element | This data element is 20 bit for the y position of the way point. Resolution is 1 cm. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 54 |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.4.15 psi data element | This data element is 16 bit for the desired heading position of the vehicle in that specific way point. A heading (psi) value of 0 represents a drive in x-direction. The unit is in 0,0001 radian and counted counter-clockwise. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.5 vidResponse (optional container: VidResponse) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.5.1 Introduction | With reference to clause 7.4.4.2, a seed can be negotiated using a Diffie-Hellman key exchange. This key exchange process allows the two participants to agree on a secret seed, even if everyone can read the communication. NOTE: It is assumed that the communication between the participants is authenticated (payloads are... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.5.2 vidVehicleState data element | The data element vidVehiclestate describes the current state in the vehicle identification process and complies with the enumerated values shown in Table 18. Table 18: vidVehicleState values State Description undefined Default value. ready Vehicle is ready to get flashing code. lightFlashingInProgress For the infrastru... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.5.3 VidVehiclePublicKey | The data element contains a 4-byte value for a public key from the vehicle to derive the vehicle identification secret. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 55 8.3.6 safetyTimeSyncResponse (optional container: SafetyTimeSyncResponse) |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.6.1 Introduction | To calculate the ITS timestamp given in the expirationTime data element from the drivingPermission container in the MIM message, the RO subsystem needs to be able to continuously determine the current time in which the VO subsystem in an SV operates. This means that the RO determines the offset between the RO clock and... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.6.2 challenge data element | The data element reflects the challenge as received in the safetyTimeSyncRequest container within the MIM message. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.6.3 vehicleSafetyClockReceiveTimestamp data element | This clock data reflects the time of the RO subsystem when the safetyTimeSyncRequest (clause 7.4.6) was sent. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.6.4 vehicleSafetyClockTransmitTimestamp data element | This clock data reflects the time in which the VO subsystem in an SV operates, adequately to currentVehicleSafetyClockTime, see clause 8.3.9.3. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.6.5 checksum data element | This safety time synchronization shall be protected by a dedicated safety checksum. An example how to calculate data element checksum is provided in clause D.4.2. 8.3.7 safeVehicleTypeConfirmation (container: SafeVehicleTypeConfirmation) |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.7.1 Introduction | This safety-relevant container, which structure is shown in Figure 39, describes the vehicle type identifier. Though the vehicle type identifier was already sent to the RO by the backends, this is a safe confirmation by the SV. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 56 The SV shall send the safeVehicleTypeConfirmation c... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.7.2 vehicleType data element | The Vehicle Type Identifier is a string, agreed upon between OEM and the Remote Vehicle Operation provider. From the Vehicle Type Identifier, the vehicle-specific properties e.g. wheelbase, front and rear overhangs, etc., can be inferred. Operator Backend (OB) and RO subsystem already received the Vehicle Type Identifi... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.7.3 safetyProfile data element | This data element carries a string information that is exchanged beyond the VMC protocol. The safety profile is optionally negotiated via an OB and a VB. For confirmation of the backend exchange this element supports safety mechanism of the safeVehicleTypeConfirmation container. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.7.4 checksum data element | This safety time synchronization needs to be protected by a dedicated safety checksum. An example how to calculate data element checksum is provided in clause D.4.3. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.8 vehicleError (container: VehicleError) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.8.1 Overview of the vehicleError container | This container is an optional data carrier and is added to the MVM message in case an error appears during VMC of the vehicle. Figure 40 illustrates the data elements in the vehicleError container. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 57 Figure 40: Structure of the vehicleError container within the MVM message |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.8.2 time data element | The data element shows the timestamp when the error occurred. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.8.3 vehCode data element | Depending on the given error by the vehicle code data element vehCode, the infrastructure either tries to resolve the issue or aborts the mission. It saves this state for logging purposes and forwards its content to the backend. A list of mapped errors is presented in Table 19. Table 19: vehCode error codes State Descr... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.8.4 customCode data element | It contains a data element for a customer specific error code. The infrastructure will not further interpret this value. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.8.5 description data element (optional) | This data element contains up to 200 characters. It carries a description (verbal or coded) with further details about the error. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9 vehicleSafetyFeedback (optional sequence) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.1 Overview | This defines optionally a sequence of up to up to 20 VehicleSafetyFeedback containers within one MVM message. It helps to identify the safety feedback information of several sub-loops that can happen during one MVM information cycle. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 58 Figure 41: Structure of the vehicleSafetyFeed... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.2 VehicleSafetyFeedbackContainer (container) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.2.1 Introduction | This container hosts the safety feedback information of a specific safety cycle. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.2.2 remainingTimeToStartBraking data element | The time which the vehicle is allowed to keep driving until brakes shall be engaged. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.2.3 safetyViolations: SEQUENCE OF SafetyViolationsEnum | This reports a sequence of up to 5 safety violations from the DE safetyViolationsEnum due to the specific safety cycle which as a result leads to stopping the vehicle. This structure covers the fact that during one safety cycle more than one stopping reason can occur. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.2.4 safetyViolationsEnum data element | Table 20 presents a list of enumerators available to support reporting a safety violation as described in clause 8.3.9.2.3. Table 20: List of safetyViolationsEnum enumerators State Description noViolation No violation noDrivingPermissionReceived No driving permission received lastDrivingPermissionTooOld Last driving pe... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.9.3 currentVehicleSafetyClockTime data element | The DE contains the time stamp of the specific safety loop in the vehicle as described in detail with the specific vehicleSafetyFeedback container. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10 vehicleProperties (container: VehicleProperties) | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.1 Introduction | This container is an optional data carrier and is added to the MVM message mainly as a surrogate for missing static vehicle data that AVM system will possibly need. In specific use cases the static vehicle data will be transferred upfront to a VMC protocol e.g. via backend communication. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.2 Overview of the vehicleProperties container | The data elements structure of the vehicleProperties container is shown in Figure 42. Figure 42: Structure of the vehicleProperties container within the MVM message |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.3 basicVehicleClass data element | This data element specifies a list of generic vehicle classes that the AVM system will cope with. The list of defined vehicle classes as enumerators is shown in Table 21. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 60 Table 21: List of basicVehicleClass enumerators State Description none Not equipped, not known or unavailabl... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.4 vehicleLength data element | This data element vehicleLength contains the overall vehicle length in (cm). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.5 vehicleWheelbase data element | The data element vehicleWheelbase contains the wheelbase value (cm). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.6 vehicleRearOverhang data element | This data element contains the rear overhang value (cm). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.7 vehicleWidth data element | The data element vehicleWidth contains the overall vehicle width value (cm). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.8 vehicleTireWitdth data element | The data element vehicleTireWidth contains the specified width of tires value. It is applied for precise control if the vehicle drives over wheel chocks and ramps. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.9 vehicleMass data element | The vehicleMass data element represents a rough vehicle mass value, it is taken from the CDD. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.10 vehicleTrackWidth data element | This data element contains the vehicle track width value (cm) which is applicable for precise control if the vehicle drives over wheel chocks and ramps. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.11 vehicleSpeedLimit data element | The data element vehicleSpeedLimit contains the limit value of the vehicle speed according to the use case, unit in (cm/s). |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.12 vehicleCurvatureLimit data element | The data element vehicleCurvatureLimit contains the limit value of the vehicle curvature according to the use case, symmetrically applicable for left and right turns. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 61 |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 8.3.10.13 vehicleMaxAngularSteeringRate data element | This data element reports the static value of a maximum steering rate for the according use case, with reference to the wheel angle, not steering wheel angle. Unit is specified as rad/s with a resolution of 0,0001. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 62 Annex A (normative): ASN.1 modules This clause provides the norm... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 1 Scope | The present document defines security provisions for Smart Voice-controlled Device extending from the provisions for consumer IoT devices defined in ETSI TS 103 645 [1]. In terms of security concerns, SVD has a different focus than other generic IoT devices (e.g. distributed sensors, smart appliances, etc.). For exampl... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 2 References | |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 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... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 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... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 3 Definition of terms, symbols and abbreviations | |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 645 [1] and the following apply: pairing: act of authentication, authorization and exchange of specific information between devices/machines and/or applications running on a device/machine resulting in a long-term trust relationship ETSI ETSI TS 1... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 3.2 Symbols | Void. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 645 [1] and the following apply: NVD National Vulnerability Database OTA Over-The-Air SVD Smart Voice-controlled Device SSL Secure Sockets Layer TLS Transport Layer Security |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 4 Methodology and general requirements | |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 4.1 Introduction | Like many Internet of Things (IoT) devices, Smart Voice-controlled Device rely on internet connectivity and may be connected to other devices within a Local Area Network (LAN), which makes them susceptible to various security risks and attacks. The voice commands processed by SVD often entail the use of personal data, ... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 4.2 Handling of provisions | The present document adopts the provisions of ETSI TS 103 645 [1] as a baseline for the Smart Voice-controlled Device. The methodology used for the adoption is described in the present clause, which includes different operations to modify provisions from ETSI TS 103 645 [1] and add new provisions specific to Smart Voic... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 4.3 Naming conventions | The provisions in the present document are named following the naming conventions described in the present clause. Each provision contains an acronym representing the Smart Voice-controlled Device. The acronym for the Smart Voice-controlled Device is set to SVD. Names for provisions that are specific to the present doc... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.0 Reporting implementation | Provision SVD 5.0-1 (extended): A justification shall be recorded for each recommendation in the present document that is considered to be not applicable for or not fulfilled by the device. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.1 No universal default passwords | Existing provisions from ETSI TS 103 645 [1], clause 5.1 are modified as follows. Provision SVD 5.1-1, Provision SVD 5.1-2 (information): NOTE: Credentials that are commonly used by SVD for initial pairing, such as pairing codes and QR codes, are also be considered as "passwords" in these provisions. Best practice is t... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.2 Implement a means to manage reports of vulnerabilities | No modifications to the provisions from ETSI TS 103 645 [1], clause 5.2 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.3 Keep software updated | Existing provisions from ETSI TS 103 645 [1], clause 5.3 are modified as follows: Provision SVD 5.3-2 (refined): The SVD shall have an update mechanism for the secure installation of updates. Provision SVD 5.3-4A (promoted): One secure update mechanism shall be configurable to be automated. Provision SVD 5.3-7 (extende... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.4 Securely store sensitive security parameter | Provision SVD 5.4-1 (information): NOTE 1: Possible sensitive security parameters in SVD include but are not limited to: cryptographic parameters used for initialization or pairing, such as pre-installed certificates in the device or immutable unique identity of the device or unique symmetric/asymmetric root keys of th... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.5 Communicate securely | Provision SVD 5.5-4 (promoted): Access to device functionality via a network interface in the initialized state shall only be possible after authentication on that interface. Provision SVD 5.5-5 (information): NOTE: The pairing of new devices or apps is such a security-relevant change. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.6 Minimize exposed attack surfaces | Provision SVD 5.6-1 (information): NOTE: Some SVDs provide network and/or logical interfaces to transport voice commands e.g. via external microphones. Provision SVD 5.6-4B (refined): Debug interfaces that are physical ports shall be physically disabled. Provision SVD 5.6-5 (promoted): The manufacturer shall only enabl... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.7 Ensure software integrity | No modifications to the provisions from ETSI TS 103 645 [1], clause 5.7 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.8 Ensure that personal data is secure | No modifications to the provisions from ETSI TS 103 645 [1], clause 5.8 are defined in the present document. ETSI ETSI TS 103 927 V1.1.1 (2024-01) 11 |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.9 Make systems resilient to outages | No modifications to the provisions from ETSI TS 103 645 [1], clause 5.9 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.10 Examine system telemetry data | No modifications to the provisions from ETSI TS 103 645 [1], clause 5.10 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.11 Make it easy for users to delete user data | Provision SVD 5.11-1 (information): EXAMPLE: The SVD asks the user for permission to request the removal of user data including user account data from connected devices or associated services when unpairing or logging out is initiated. Provision SVD 5.11-2 (extended): The user shall be provided with a functionality suc... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.12 Make installation and maintenance of devices easy | Provision SVD 5.12-1(information): NOTE: For SVDs, methods such as scanning QR codes, scanning dynamic graphics, inputting device identities, and NFC transactions can be provided to allow users to complete initialization with a minimum of steps. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 5.13 Validate input data | No modifications to the provisions from ETSI TS 103 645 [1], clause 5.13 are defined in the present document. 6 Adapted data protection provisions for Smart Voice-controlled Device Existing provisions from ETSI TS 103 645 [1], clause 6 are modified as follows: Provision SVD 6-1 (information): NOTE: It should be noted t... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.1 No universal default passwords | Provision SVD 7.1-1 (added): SVDs shall not use passwords or simple pairing codes for initial pairing. ETSI ETSI TS 103 927 V1.1.1 (2024-01) 12 |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.2 Implement a means to manage reports of vulnerabilities | No additions to the provisions from ETSI TS 103 645 [1], clause 5.2 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.3 Keep software updated | Provision SVD 7.3-1 (added): Manufacturers of SVDs should package and release functional updates and security updates separately. NOTE 1: This recommendation supports consumers in choosing specific feature versions according to their preferences while still enjoy the latest security fixes. Provision SVD 7.3-2 (added): ... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.4 Securely store sensitive security parameters | No additions to the provisions from ETSI TS 103 645 [1], clause 5.4 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.5 Communicate securely | Provision SVD 7.5-1 (added): The SVD should close unused communication sessions in a timely manner. NOTE: Keep alive signals indicate that communication sessions are still used. Provision SVD 7.5-2 (added): SVD should keep the number of connected devices to a minimum necessary for the intended operation. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.6 Minimize exposed attack surfaces | Provision SVD 7.6-1 (added): In the initialized state, the SVD should use packet filtering to discard and potentially log inappropriate packages on network layer. NOTE: Typically, inappropriate network packages make use of unused or inappropriate network addresses such as unused ports or unsuitable IP addresses. Provis... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.