Step

Description

1

(See registration examples)

2

(See registration examples)

3

(See registration examples)

4

(See registration examples)

5

(See registration examples)

6

Server responds with the EndDevice resource without a FunctionSetAssignmentListLink. In this case, the resource of choice is a DemandResponseProgram which is not a direct member of EndDevice.

Server sends the following response:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<EndDevice href="/edev/3" subscribable="0" xmlns="urn:ieee:std:2030.5:ns">

<ConfigurationLink href="/edev/3/cfg"/>

<DeviceInformationLink href="/edev/3/di"/>

<DeviceStatusLink href="/edev/3/ds"/>

<FileStatusLink href="/edev/3/fs"/>

<PowerStatusLink href="/edev/3/ps"/>

<sFDI>987654321005</sFDI>

<changedTime>1379905200</changedTime>

<RegistrationLink href="/edev/3/reg"/>

<SubscriptionListLink all="0" href="/edev/3/subl"/>

</EndDevice>

7

(See registration examples)

8

(See registration examples)

9

(See registration examples)

10

Client GETs its DeviceCapabilities from the server as found in the DNS-SD TXT record. Client sends the following request:

GET /dcap HTTP/1.1 Host: {hostname}

Accept: application/sep+xml

11

Server responds with the DeviceCapabilities resource. Server sends the following response:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<DeviceCapability href="/dcap" xmlns="urn:ieee:std:2030.5:ns">

<DemandResponseProgramListLink all="1" href="/drp"/>

<MessagingProgramListLink all="2" href="/msg"/>

<EndDeviceListLink all="1" href="/edev"/>

<SelfDeviceLink href="/sdev"/>

</DeviceCapability>

12

Client GETs its desired resource from the server as found in the DeviceCapabilities resource. In this case, the resource of choice is a DemandResponseProgram.

(See DemandResponse examples)

13

(See DemandResponse examples)