8.5 Service Opt Out | UK Smart Metering Knowledge Project

Service details

Identifiers, rules, and applicability

Service reference: 8.5
Service Reference Variant: 8.5
DUIS section: 3.8.107
Command variants: 1
DUIS possible responses: AcknowledgementService Response from Device - GBCSPayload
Critical: No
Sensitive response: No
Protection against replay: Yes
On demand: No
Future dated: DSP
DSP scheduled: No
DCC only: No
SMETS1 applicability: No
SAPC requirement: Not stated
DUIS applicability: 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3

Specific Errors

Response codes and descriptions

Response Code	Response Code Description
`E080501`	The Device is associated to a Domestic MPxN
`E080502`	The Device Status is ‘Withdrawn’ (this particular check and Response Code is not expected to be reached in this DUIS version, as the generic Authorisation Check associated to Response Code E5 will fail prior to this check being carried out)
`E080503`	The Certificate Type is not applicable to the Device Type

Source: DUIS 3.8.107.3

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code

CS02b0x0104

DUIS Applicability

v3.0 – v5.3

GBCS Applicability

v1.0 – v4.3

GBCS Criticality

Critical

Sensitive Response

No

Future Dated

DSP

GBTWhat is GBT?

CommandESMENot always GBT

CommandGSMENot always GBT

CommandHCALCSNot always GBT

CommandPPMIDAlways GBT

SMETS1 Applicable

No

Eligible Roles

None stated

DUIS Service Definition

Data items and DCC processing

Request data items

Table 234: ServiceOptOut (sr:ServiceOptOut) data items

Data Item	Description / Values	Type	Mandatory	Default	Units
ExecutionDateTime	A 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, i.e. the date from which the Device is to be opted out from DCC services Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’	xs:dateTime	Yes	None`	UTC Date-Time
ABCFloorSeqNumber	Originator Counter (floor value) for the new ACB Remote Party. The value will be used to prevent replay of Update Security Credentials Commands, and other Commands, for the new controlling Remote Party Valid set: Value > 0 and <= Originator Counter of the first Command to the Device from the New ACB	sr:floorSequenceNumber (Restriction of xs:nonNegativeInteger minInclusive = 0, maxInclusive = 9223372036854775807)	Yes	None	N/A
ReplacementCertificates	This structure provides a list of the replacements. Each replacement contains a replacement Certificate	sr:ReplacementCertificatesACB	Yes	None	N/A
CertificationPathCertificates	This structure provides the Certificates needed to Confirm Validity of the new end entity Certificate against the root public key held on the Device. The number of these may be less than the number of replacement certificates (e.g. a Supplier may replace all of its certificates but may only need to supply one Certification Authority Certificate to link them all back to root.)	sr:CertificatePathCertificates (sr:Certificate xs:base64Binary minOccurs = “1”, maxOccurs = “3”)	Yes	None	N/A
ApplyTimeBasedCPVChecks	Device to apply (true) or not apply (false) time based checks as part of Confirm Validity check. It should only be set to false in exceptional circumstances (e.g. credentials on the Device have expired without replacement for unforeseen reasons)	xs:boolean	Yes	None	N/A

Table 235: ReplacementCertificates (sr:ReplacementCertificatesACB) data items

Data Item	Description / Values	Type	Mandatory	Default	Units
DigitalSigningCertificate	The Digital Signing credentials to be placed by the DCC in the DCC ‘Access Control Broker’ Remote Party Role, Key Usage digitalSignature on the Device so that communications via the DCC are no longer possible.	sr:Certificate (xs:base64Binary)	Device Type = PPMID: Yes Otherwise: N/A	None	N/A
KeyAgreementCertificate	The key agreement credentials to be placed by the DCCin the DCC ‘Access Control Broker’ Remote Party Role, Key Usage KeyAgreement on the Device so that communications via the DCC are no longer possible	sr:Certificate (xs:base64Binary)	Yes	None	N/A

Additional System Processing - DUIS

Upon successful execution of a ServiceOptOut Service Request, the DCC shall, for the specified DeviceID identified within the Service Request, perform the following actions.

Update the Smart Metering Inventory and set the SMI Status of the Device identified by DeviceId contained in the header to ‘Withdrawn’
For Device Types Electricity Smart Meter and Gas Smart Meter, Generate DCC Alerts N1, N2 to notifiy specified Users of the Device decomissioning as per DCC Alert definitions clause 3.6.3.4 DCC Alert Codes
For Device Types Electricity Smart Meter and Gas Smart Meter, update the Registration Systems to set the Service Status of the MPxN(s) associated to that Meter to “Opted Out
Delete all active DCC Schedules held within the DCC Systems and send a DCC Alert to the DCC Schedule owner.
Delete all Future Dated (DSP) requests with future dated execution dates that have not been sent to the Device and send a DCC Alert to the orginal sender of the request

For each certificate specified in a Response or Alert from the Device as being successfully updated by the Update Security Credentials command, the DCC Systems shall update the Smart Metering Inventory with the new certificate identifier as a record of the certificate held in the relevant Trust Anchor Cell on that Device.