Service Reference Variant

6.21 · Request Handover Of DCC Controlled Device

Service details

Identifiers, rules, and applicability

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

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E062101
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
E062102
The Certificate type is not applicable to the Device Type
E062103
The combination of User Role and Remote Party Role is invalid for the Device Type
E062105
The Certificate Type is not applicable to the Device Type & Remote Party Role combination or not all applicable Certificate Types are included in the Request.

Source: DUIS 3.8.74.3

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
CS02b0x0102
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
DSP
CommandESMEAlways GBT
CommandGSMEAlways GBT
CommandGPFAlways GBT
CommandHCALCSNot always GBT
SMETS1 Applicable
NoYes
Eligible Roles
EISESMEHCALCS
GISGSMEGPF
SMETS1 note

HCALCS is not a valid SMETS1 Device Type

Use Case / Message Code
CS02b0x0103
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
DSP
CommandESMEAlways GBT
CommandGPFAlways GBT
SMETS1 Applicable
Yes
Eligible Roles
EISESME
GISGPF

DUIS Service Definition

Data items and DCC processing

Request data items

Table 196: RequestHandoverOfDCCControlledDevice (sr:RequestHandoverOfDCCControlledDevice) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
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
RemotePartyRoleRemote Party Role for which the Credentials are being updated Valid Set in this context from the enumeration is; Supplier NetworkOperatorsr:RemotePartyRole Restriction base xs:token (Enumeration)YesNoneN/A
RemotePartyFloorSeqNumberOriginator Counter (floor value) for the new Remote Party. This value will be used to prevent replay of Update Security Credentials Commands, and other Commands, for the new controlling Remote Party. Used only where the Remote Party Role for which the Certificates are being updated is Supplier.sr:floorSequenceNumber (Restriction of xs:nonNegativeInteger minInclusive = 0, maxInclusive = 9223372036854775807NoNoneN/A
RemotePartyPrepaymentTopUpFloorSeqNumberOnly applicable when the Command changes Supplier Credentials and Counters on a Meter and the Counter for its Prepayment Top Ups is different to that used for other Commands. This value will be used to prevent replay of Prepayment Top Up Commandssr:floorSequenceNumber (Restriction of xs:nonNegativeInteger minInclusive = 0, maxInclusive = 9223372036854775807Remote Party Role = Supplier and Device Type = ESME or GSME: No Otherwise: N/ANoneN/A
ReplacementCertificatesThis structure provides a list of the replacements. Each replacement contains a replacement Certificate, its Key Usage and Cell Usage.sr:ReplacementCertificatesDCCHandoverYesNoneN/A
CertificationPathCertificatesThis 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:Certificate xs:base64Binary minOccurs = “1”, maxOccurs = “3”))YesNoneN/A
ApplyTimeBasedCPVChecksSpecify whether the time based Confirm Validity checkshould be appliedxs:booleanYesNoneN/A
Table 197: ReplacementCertificates (sr:ReplacementCertificatesDCCHandover) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
DigitalSigningCertificateThe new Digital Signing Certificate to be placed in the Remote Party Role Key Usage digitalSignature (Cell Usage management) on the Device.sr:Certificate (xs:base64Binary)YesNoneN/A
KeyAgreementCertificateThe new Key Agreement Certificate to be placed in the Remote Party Role Key Usage keyAgreement (Cell Usage management) on the Device.sr:Certificate (xs:base64Binary)HCALCS: N/A Otherwise: YesNoneN/A
KeyAgreementTopUpCertificateThe new Key Agreement Certificate to be placed in the Supplier Remote Party Role Key Usage keyAgreement (Cell Usage prePaymentTopUp) on the Device for those Suppliers that use different Originator Counters for Prepayment Top Up.sr:Certificate (xs:base64Binary)Remote Party Role = Supplier and Device Type = ESME or GSME: Yes Otherwise: N/ANoneN/A

Additional System Processing - DUIS

When the DCC receives a Response indicating Success from an Update Security Credentials command for all certificates and where the Remote Party whose certificate has been placed on the Device is not the sender of the Service Request, the DCC shall send a DCC Alert N42 to each of the relevant User(s) whose certificate has been placed on the Device.

Where the SMI Status of the associated Device is ‘Recovered’ and when all the Security Credentials from Access Control Broker Organisation Certificates that have been placed in the Supplier and Network Operator Trust Anchor Cells as part of the recovery process have been replaced with those from Organisation Certificates of the relevant Supplier and/or Network Operator, the DCC shall update the Device Status to the SMI Status it held immediately prior to the recovery process (SMI Status prior to the ‘Recovery’ SMI Status).

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.

Message Patterns & Examples

Pattern explorer

Open Message Patterns →

SMETS1 Supporting Requirements

Device-model variations and equivalent steps

Review the Section 18 requirements and their applicability across the documented manufacturer, Device Type, model, and firmware profiles.

Open S1SR Requirements →