Service Reference Variant

5.2 ยท Read Schedule

Service details

Identifiers, rules, and applicability

Service reference
5.2
Service Reference Variant
5.2
DUIS section
3.8.44
Command variants
8
DUIS possible responses
Response to a Non-Device Service Request
Critical
No
Sensitive response
No
Protection against replay
No
On demand
No
Future dated
No
DSP scheduled
No
DCC only
Yes
SMETS1 applicability
Yes
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 CodeResponse Code Description
E050201
The DSPScheduleID does not exist or it is not owned by the User submitting the Service Request
E050202
The Device ID does not exist.
W050201
The User submitting the Service Request does not have any schedules created against the specified Device.

Source: DUIS 3.8.44.3

GBCS Use Case

Use cases, device coverage, and applicability

Instruction
ReadScheduleByDeviceIDReadScheduleByScheduleID
DUIS Applicability
v3.0 โ€“ v5.3
GBCS Applicability
DCC Only
GBCS Criticality
N/A
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISEESGISENOGNOMDROUDSP

DUIS Service Definition

Data items and DCC processing

Request data items

Table 159: ReadSchedule (sr:ReadSchedule) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
DSPScheduleIDSchedule ID generated by the DCC Systems when the schedule was created Valid Set: > 0sr:scheduleIDNo Either DSPScheduleID or DeviceID must be presentNoneN/A
DeviceIDThis is the Device ID for which schedules are to be readsr:EUI (See clause 3.10.1.3)No Either DSPScheduleID or DeviceID must be presentNoneN/A

Response data items

Table 160: DSPSchedulesRead (sr:DSPSchedulesRead) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
DSPSchedulesDetails of all the Schedules readsr:DSPSchedules maxOccurs = 99YesNoneN/A
Table 161: ReadSchedules (sr:ReadSchedules) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
DSPScheduleIDSchedule ID generated by the DCC Systems when the schedule was created Valid Set: > 0sr:scheduleIDYesNoneN/A
DSPScheduleDetailsSchedule details provided when the schedule was createdsr:DSPSchedule see 3.8.43.2YesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns โ†’