UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

8.7.1 · Join Service (Critical)

Service details

Identifiers, rules, and applicability

Service reference
8.7
Service Reference Variant
8.7.1
DUIS section
3.8.109
Command variants
4, 5, 6, 7
DUIS possible responses
AcknowledgementResponse to Transform Request - PreCommand FormatService Response from Device - GBCSPayloadResponse to a Command for Local Delivery Request - LocalCommand FormatCountersigned SMETS1 Response
Critical
Yes
Sensitive response
No
Protection against replay
Yes
On demand
Yes
Future dated
No
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

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.

CS03A12 commands1 attribute0x000DESME

Commands mapped to CS03A1

  • SMETSAdd Device Security Credentials5.6.3.4ESME
  • SMETSRemove Device Security Credentials5.6.3.19ESME
SpecificationItemReferenceDescription
SMETSDevice Log5.7.4.14The Security Credentials for each of the Type 1 Devices and Type 2 Devices with which ESME can establish Communications Links.

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E080702
The ‘Other Device’ Type is not valid for this Join Service

Source: DUIS 3.8.109.3

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
CS03A10x000D
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible RolesDevice to be Joined
EISESME
HCALCSPPMID
SMETS1 note

HCALCS is not a valid SMETS1 Device Type

Use Case / Message Code
CS03A20x00AB
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
No
Eligible RolesDevice to be Joined
EISHCALCS
ESME
Use Case / Message Code
CS03C0x00AF
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible RolesDevice to be Joined
GISGSME
PPMID

DUIS Service Definition

Data items and DCC processing

Request data items

Table 239: JoinServiceCritical (sr:JoinOrUnjoinDevice) data items
Data ItemDescription / ValuesTypeMandatoryDefaultUnits
OtherDeviceIDDevice ID of the Device to be joined to (paired with) the BusinessTargetID Devicesr:EUI (See clause 3.10.1.3)YesNoneN/A

Additional System Processing - DUIS

Where a GSME is to be joined to a PPMID then the DCC shall add the Key Agreement Certificate (currently in use by the PPMID specified within the Service Request) to the Pre-Command to be sent back to the User. The Key Agreement Certificate shall be retrieved by the DCC from the Public Key Repository where the “In Use” flag is set.

Upon successful execution of a JoinService(Critical) Service Request to join a HCALC or a PPMID Device, and where the associated Communication Hub Function and the associated Electricity Smart Meter or Gas Smart Meter SMI Status are ‘Commissioned’, the DCC shall update the Smart Metering Inventory and set the SMI Status of the HCALC or PPMID to ‘Commissioned’.

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 →