Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.4.1 — Alerts Configuration Settings
6 technical records havebeen identified at this reference: 6 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
ESMESRV touchpoint
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS5.7.4.1 · item Alerts Configuration Settings - Supplier.maskAndActionsForHANDeviceSharing
Alerts Configuration Settings - Supplier - maskAndActionsForHANDeviceSharing
Both BIT STRINGS shall be 256 bits in length. The first bits string ('Mask') shall detail which events / alerts are to be changed. A value of 0b0 shall mean 'do not change' and 0b1 shall mean 'change'. The second bit string ('Actions') shall, for the events / alerts set by the Mask to be changed, specify the value each is to be changed to. In Actions, 0b0 shall mean 'turn off' and 0b1 shall mean 'turn on'. Both bit strings shall be numbered according to LSB = 0, the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Alert Code which is the concatenation 0x81 || n. The bit string in the corresponding read object shall be updated in line with Mask and Actions. The value set on the ESME shall be the concatenation Mask || Actions, so a 512 bit length bit string'.
- Object
Alerts Configuration Settings - Supplier- Attribute / method
maskAndActionsForHANDeviceSharing- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- Both BIT STRINGS shall be 256 bits in length. The first bits string ('Mask') shall detail which events / alerts are to be changed. A value of 0b0 shall mean 'do not change' and 0b1 shall mean 'change'. The second bit string ('Actions') shall, for the events / alerts set by the Mask to be changed, specify the value each is to be changed to. In Actions, 0b0 shall mean 'turn off' and 0b1 shall mean 'turn on'. Both bit strings shall be numbered according to LSB = 0, the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Alert Code which is the concatenation 0x81 || n. The bit string in the corresponding read object shall be updated in line with Mask and Actions. The value set on the ESME shall be the concatenation Mask || Actions, so a 512 bit length bit string'.
Documented touchpoints
- ConfiguresECS25a1
0x00EAESMESRV 6.22
SMETS5.7.4.1 · item Alerts Configuration Settings - Supplier.settingsForWANAlerting
Alerts Configuration Settings - Supplier - settingsForWANAlerting
The BIT STRING shall be 256 bits in length. The ESME shall have this BIT STRING set to reflect the current configuration according to the following: - 0b0 shall mean WAN Alerting 'turned off' and 0b1 shall mean 'turned on' - the BIT STRING shall be numbered according to LSB = 0 - the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Event / Alert Code which is the concatenation 0x81 || n.
- Object
Alerts Configuration Settings - Supplier- Attribute / method
settingsForWANAlerting- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- The BIT STRING shall be 256 bits in length. The ESME shall have this BIT STRING set to reflect the current configuration according to the following: - 0b0 shall mean WAN Alerting 'turned off' and 0b1 shall mean 'turned on' - the BIT STRING shall be numbered according to LSB = 0 - the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Event / Alert Code which is the concatenation 0x81 || n.
Documented touchpoints
- ReadsECS25r1
0x00EEESMESRV 6.2.10
SMETS5.7.4.1 · item Alerts Configuration Settings - Supplier.settingsForHANDeviceSharing
Alerts Configuration Settings - Supplier - settingsForHANDeviceSharing
The BIT STRING shall be 256 bits in length. The ESME shall have this BIT STRING set to reflect the current configuration according to the following: - 0b0 shall mean HAN Device sharing 'turned off' and 0b1 shall mean 'turned on' - the BIT STRING shall be numbered according to LSB = 0 - the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Event / Alert Code which is the concatenation 0x81 || n.
- Object
Alerts Configuration Settings - Supplier- Attribute / method
settingsForHANDeviceSharing- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- The BIT STRING shall be 256 bits in length. The ESME shall have this BIT STRING set to reflect the current configuration according to the following: - 0b0 shall mean HAN Device sharing 'turned off' and 0b1 shall mean 'turned on' - the BIT STRING shall be numbered according to LSB = 0 - the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Event / Alert Code which is the concatenation 0x81 || n.
Documented touchpoints
- ReadsECS25r1
0x00EEESMESRV 6.2.10
SMETS5.7.4.1 · item Alerts Configuration Settings - Network Operator.settingsForWANAlerting
Alerts Configuration Settings - Network Operator - settingsForWANAlerting
The BIT STRING shall be 256 bits in length. The ESME shall have this BIT STRING set to reflect the current configuration according to the following: - 0b0 shall mean WAN alerting 'turned off' and 0b1 shall mean 'turned on' - the BIT STRING shall be numbered according to LSB = 0 - the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Event / Alert Code which is the concatenation 0x80 || n.
- Object
Alerts Configuration Settings - Network Operator- Attribute / method
settingsForWANAlerting- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- The BIT STRING shall be 256 bits in length. The ESME shall have this BIT STRING set to reflect the current configuration according to the following: - 0b0 shall mean WAN alerting 'turned off' and 0b1 shall mean 'turned on' - the BIT STRING shall be numbered according to LSB = 0 - the mapping to Event / Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Event / Alert Code which is the concatenation 0x80 || n.
Documented touchpoints
- ReadsECS25r2
0x00EFESMESRV 6.2.10
SMETS5.7.4.1 · item Alerts Configuration Settings - Supplier.Bit string
Alerts Configuration Settings - Supplier - Bit string
Both BIT STRINGS shall be 256 bits in length. The first bit string ('Mask') shall detail which alerts are to be changed. A value of 0b0 shall mean 'do not change' and 0b1 shall mean 'change'. The second bit string ('Actions') shall, for the alerts set by the Mask as requiring change, specify the value each is to be changed to. In Actions, 0b0 shall mean 'turn off' and 0b1 shall mean 'turn on'. Both bit strings shall be numbered according to LSB = 0. The mapping to Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Alert Code which is the concatenation 0x81 || n. The value set on the ESME shall be the concatenation Mask || Actions, so a 512 bit length bit string
- Object
Alerts Configuration Settings - Supplier- Attribute / method
Bit string- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- Both BIT STRINGS shall be 256 bits in length. The first bit string ('Mask') shall detail which alerts are to be changed. A value of 0b0 shall mean 'do not change' and 0b1 shall mean 'change'. The second bit string ('Actions') shall, for the alerts set by the Mask as requiring change, specify the value each is to be changed to. In Actions, 0b0 shall mean 'turn off' and 0b1 shall mean 'turn on'. Both bit strings shall be numbered according to LSB = 0. The mapping to Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Alert Code which is the concatenation 0x81 || n. The value set on the ESME shall be the concatenation Mask || Actions, so a 512 bit length bit string
Documented touchpoints
- ConfiguresECS25a
0x00ACESMESRV 6.22
SMETS5.7.4.1 · item Alerts Configuration Settings - DNO.Bit string
Alerts Configuration Settings - DNO - Bit string
Both BIT STRINGS shall be 256 bits in length. The first bit string ('Mask') shall detail which alerts are to be changed. A value of 0b0 shall mean 'do not change' and 0b1 shall mean 'change'. The second bit string ('Actions') shall, for the alerts set by the Mask as requiring change, specify the value each is to be changed to. In Actions, 0b0 shall mean 'turn off' and 0b1 shall mean 'turn on'. Both bit strings shall be numbered according to LSB = 0. The mapping to Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Alert Code which is the concatenation 0x80 || n. The value set on the ESME shall be the concatenation Mask || Actions, so a 512 bit length bit string
- Object
Alerts Configuration Settings - DNO- Attribute / method
Bit string- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- Both BIT STRINGS shall be 256 bits in length. The first bit string ('Mask') shall detail which alerts are to be changed. A value of 0b0 shall mean 'do not change' and 0b1 shall mean 'change'. The second bit string ('Actions') shall, for the alerts set by the Mask as requiring change, specify the value each is to be changed to. In Actions, 0b0 shall mean 'turn off' and 0b1 shall mean 'turn on'. Both bit strings shall be numbered according to LSB = 0. The mapping to Alert Code of a particular bit in position n, where n is in hexadecimal, shall be to the Alert Code which is the concatenation 0x80 || n. The value set on the ESME shall be the concatenation Mask || Actions, so a 512 bit length bit string
Documented touchpoints
- ConfiguresECS25b
0x00B0ESMESRV 6.22
How to read this page
Evidence is kept at record level
A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.