Service Reference Variant

3.1 · Display Message

Service details

Identifiers, rules, and applicability

Service reference
3.1
Service Reference Variant
3.1
DUIS section
3.8.12
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.

ECS101 attribute0x0021ESME
SpecificationItemReferenceDescription
SMETSSupplier Message [INFO]5.7.4.43A message issued to, and held on, ESME for provision to the Consumer.
GCS071 attribute0x0071GSME
SpecificationItemReferenceDescription
SMETSSupplier Message4.6.4.24A message issued to, and held on, GSME for provision to the Consumer.

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
ECS100x0021
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
EISESME
Use Case / Message Code
GCS070x0071
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
GISGSME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 122: DisplayMessage (sr:DisplayMessage) 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 ID Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
SupplierMessageText content of message to be displayed to customer SupplierMessage is restricted by the XML Schema to only include displayable characters Valid set: • All printable characters, i.e. characters with ASCII values of 32 (space) to 126 (tilde) inclusiveRestriction of xs:string (minLength = 1, maxLength = 116, pattern = “[ -~]+”)YesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns →