Service Reference Variant

3.4 · Update Supplier Name

Service details

Identifiers, rules, and applicability

Service reference
3.4
Service Reference Variant
3.4
DUIS section
3.8.15
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.

ECS161 attribute0x0025ESME
SpecificationItemReferenceDescription
SMETSContact Details [INFO]5.7.4.8The name and contact telephone number of the Supplier.
GCS441 attribute0x0088GSME
SpecificationItemReferenceDescription
SMETSContact Details4.6.4.4The name and contact telephone number of the current gas Supplier.

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
ECS160x0025
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
GCS440x0088
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 125: UpdateSupplierName (sr:UpdateSupplierName) 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 Valid set: Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
SupplierNameDefined format Supplier name SupplierName 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 (maxLength = 15 pattern = “[ -~]+”)YesNoneN/A
SupplierTelephoneNumberDefined format Supplier Telephone Number SupplierTelephoneNumber is restricted by the XML Schema to only include numbers and spacesRestriction of xs:string (maxLength = 18 pattern = “[0-9 ]+”)YesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns →