Service Reference Variant

7.11 · Read Boost Button Details

Service details

Identifiers, rules, and applicability

Service reference
7.11
Service Reference Variant
7.11
DUIS section
3.8.97
Command variants
1, 2, 3
DUIS possible responses
AcknowledgementService Response from Device - GBCSPayloadResponse to a Command for Local Delivery Request - LocalCommand Format
Critical
No
Sensitive response
No
Protection against replay
No
On demand
Yes
Future dated
DSP
DSP scheduled
No
DCC only
No
SMETS1 applicability
No
SAPC requirement
Optional
DUIS applicability
3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3

Cross-specification evidence

SMETS/CHTS to GBCS Mapping

This section shows the SMETS and CHTS attributes that can be read or written by the identified GBCS Use Case. Command requirements are shown separately from the mapped attributes.

ECS61c3 attributes0x005EESME
SpecificationItemReferenceDescription
SMETSBoost Function Availability5.26.1.1A data item to identify if ESME has a configured Boost Function.
SMETSBoost Function Control [n]5.26.2.1A data item to identify whether ALCS [n] or APC [n] is to be controlled by the Boost Function.
SMETSBoost Function Event Log5.26.3.1A single log capable of storing entries for the most recent 25 Boost Periods including the UTC date and time of the beginning and end of the Boost Period.

Specific Errors

Response codes and descriptions

No specific validation is defined for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS61c0x005E
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISOUESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 222: ReadBoostButtonDetails (sr:ReadLogFutureDatable) data items
Data ItemDescription / ValuesTypeMandatoryDefaultUnits
ExecutionDateTimeA User shall only add this Data Item to the Service Request where they require the Service Request to be executed at a future date and time. The UTC date and time the User requires the Command to be executed on the Device Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
ReadLogPeriodThe Start and/or End Date-Times for which the Boost Button Event Log data is requiredsr:ReadLogPeriod (see clause 3.10.1.14)YesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns →