Service Reference Variant
Service details
Specific Errors
| Response Code | Response Code Description |
|---|---|
E050101 | The Schedule Start Date is not a future date |
E050102 | The Schedule End Date is mandatory for User Role “OU” |
E050103 | The Schedule End Date is earlier than the Schedule Start Date |
E050105 | The Service Request format does not match the Service Reference Variant in the DCC Schedule. The combination of DSPScheduledServiceReference and DSPScheduledServiceReferenceVariant is not valid |
E050107 | One of: • User’s Role is Unknown Remote Party to the Device and the DCC Scheduled Service Response contains Sensitive data and Request does not include the User’s Key Agreement Public Security Credentials Or • User’s Role is Known Remote Party to the Device and / or the DCC Scheduled Service Response doesn’t contain Sensitive data and Request includes the User’s Key Agreement Public Security Credentials |
E050108 | Unable to create Schedule, because the User already owns 99 active DSP Schedules for the Device |
E050109 | The DSP Service Request format doesn’t match the DSP Service Reference Variant in the Create Schedule message |
E050111 | The DSPScheduledServiceReferenceVariant is not applicable for a MDR user |
E050112 | The DSPScheduledServiceReferenceVariant is not applicable to SMETS2 Services |
Source: DUIS 3.8.43.3
Additional SMETS1 conditions are shown separately from the SRV-specific DUIS table.
Where DeviceID in the Service Request is a SMETS1 Device according to the Smart Metering Inventory, check that the DSPScheduledServiceReferenceVariant is supported for a SMETS1 Device according to clause 3.1.
Applies to: SMETS1 Devices only
Source: DUIS 1.4.6 Table 2
GBCS Use Case
DSPSCH-14.1-GSMEDSPSCH-4.10-ESMEDSPSCH-4.15-ESMEDSPSCH-4.16-ESMEDSPSCH-4.10-GSMEDSPSCH-4.12.1-ESMEDSPSCH-4.12.2-ESMEDSPSCH-4.14-ESMEDSPSCH-4.14-GPFDSPSCH-4.17-ESMEDSPSCH-4.17-GPFDSPSCH-4.6.1-ESMEDSPSCH-4.6.1-GPFDSPSCH-4.6.2-ESMEDSPSCH-4.8.1-ESMEDSPSCH-4.8.1-GPFDSPSCH-4.8.2-ESMEDSPSCH-4.8.3-ESMEDUIS Service Definition
| Data Item | Description / Valid Set | Type | Mandatory | Default | Units |
|---|---|---|---|---|---|
| ScheduleFrequency | The frequency of which the required service reference is executed Valid set Daily Weekly (The specified Service Request will be scheduled once a week, on the Schedule Start Date day of the week.) Monthly (The specified Service Request will be scheduled once a month, on the Schedule Start Date day of the month, where possible. For those months where the Schedule Start Date day of the month doesn’t exist, the Service Request will be scheduled on the last day of that month.) Quarterly (The specified Service Request will be scheduled once every three months, with Scheduled Start Date as for Monthly.) Half-Yearly (The specified Service Request will be scheduled once every six months, with Scheduled Start Date as for Monthly.) Yearly (The specified Service Request will be scheduled once every 12 months, with Scheduled Start Date as for Monthly.) | sr:ScheduleFrequency (Restriction of xs:string (Enumeration)) | Yes | None | N/A |
| ScheduleStartDate | The UTC date that the scheduled repeating request is required to commence from Valid date in the future | xs:date | Yes | None | UTC Date |
| ScheduleEndDate | The UTC date that the scheduled repeating request is required to cease, or if not present then the repeating schedule shall remain in force until deleted by the User or by the DCC Systems, e.g. because of Device Decommission Valid date in the future >= ScheduleStartDate | xs:date | User Role IS, GS, ES, ED, GT, MDR: No User Role OU: Yes | None | UTC Date |
| ScheduleExecutionStartTime | The UTC start time after which a scheduled Command (invoked by the schedule) may be run Valid Time | xs:time | No | 00:01:00 | UTC Time |
| KAPublicSecurityCredential | The Key Agreement Public Security Credentials, associated with the User submitting the Request that will be relied upon for Sensitive data Responses. Only applicable to those Scheduled Service Requests that can be submitted by User Roles for which the Device doesn’t hold Security Credentials. | sr:Certificate (xs:base64Binary) | User Role IS, ES, ED: N/A User Role GT (where Response includes sensitive data and Device Type = Gas Smart Meter): Yes User Role MDR, OU (where Response includes sensitive data): Yes | None | N/A |
| DSPScheduledServiceReference | Reference of the Service Request to be Scheduled. Valid Set: see clause 3.1 , where DCC Scheduled column in table is set to “Yes” | sr:DSPScheduledServiceReference (Restriction of xs:string (Enumeration)) | Yes | None | N/A |
| DSPScheduledServiceReferenceVariant | Reference Variant of the Service Request to be Scheduled. Valid Set: see clause 3.1 , where DCC Scheduled column in table is set to “Yes” | sr:DSPScheduledServiceReferenceVariant (Restriction of xs:string (Enumeration)) | Yes | None | N/A |
| DeviceID | This is the Device ID to which the DCC Schedule is targeted. | sr:EUI (See clause 3.10.1.3) | Yes | None | N/A |
| Choice of Service Request XML Element to be Scheduled | Name and Request Data Items corresponding to DSPScheduledServiceReferenceVariant to be Scheduled, choice of: | Yes | None | N/A | |
| DSPRetrieveImportDailyReadLog DSPRetrieveExportDailyReadLog DSPReadActiveImportProfileData DSPReadReactiveImportProfileData DSPReadExportProfileData DSPReadNetworkData DSPReadPrepaymentDailyReadLog DSPRetrieveDailyConsumptionLog | sr:ReadLogPeriodOffset | ||||
| DSPReadInstantaneousExportRegisters DSPReadMaximumDemandImportRegisters DSPReadMaximumDemandExportRegisters DSPReadLoadLimitData DSPReadActivePowerImport | sr:DSPReadData | ||||
| DSPRecordNetworkDataGAS | sr:RecordNetworkDataGAS |
| Data Item | Description / Valid Set | Type | Mandatory | Default | Units |
|---|---|---|---|---|---|
| DSPScheduleID | Schedule ID generated by the DCC Systems Valid Set: > 0 | sr:scheduleID | Yes | None | N/A |
Message Patterns & Examples