3.2.1 ALL-01 DISCOVERY (A, DR-A)
3.2.1.1 Purpose
This test is intended to validate the client’s ability to perform discovery against the utility server and to establish basic IEEE 2030.5-based communications.
3.2.1.2 Test procedure
The steps SHALL be performed as described in Table 5. The test results SHALL be compared against the Expected Result column in Table 5, except that steps 4, 5 and 6 can occur in any order. For example, time-synchronisation may be done prior to the client requesting the EndDeviceList from the utility server.
Table 5 – Test steps for Communications Client – Discovery
Step No. | Manual or utility server step | Expected comms client result |
1 | Client communications with the utility server are initialised as appropriate for the client (e.g. client is powered on). | Client performs HTTP discovery against the pre-configured utility server URI information. |
2 | Utility server sends the relevant function set resource links to the client. | Client receives the function set resource links and requests resource information from the utility server’s DeviceCapability endpoint. |
3 | Utility server sends the DeviceCapability resource including the TimeLink, EndDeviceListLink and MirrorUsagePointListLink resource links to the client. | Client receives DeviceCapability payload. Client requests resource information from the utility server’s EndDeviceList endpoint. |
4 | Utility server sends the EndDeviceList resource containing the relevant EndDeviceList information including the ConnectionPointLink and DERListLink resource link to the client. | Client receives the EndDeviceList payload with the required EndDevice information including the relevant resources. Client accesses the utility server’s Time endpoint. |
5 | Utility server sends the Time resource containing the relevant EndDeviceList information to the client. | Client receives the Time payload and is time- synchronised with the utility server to within 10 seconds (noting synchronisation may be done via GPS/NTP or other means as per |
CSIP-AUS). This will be verified through ongoing communications between the client and utility server. Client access the utility server’s DERList endpoint. | ||
6 | Utility server sends the DERList resource containing the DERCapabilityLink, DERStatusLink and DERSettingsLink resource links to the client. | Client receives the DERList payload with the required DER information including the relevant resources. |
3.2.1.3 Criteria
If during testing the client experiences one of the following events these are considered non- conformances with this requirement:
a) The client does not perform discovery against the utility server at the pre-configured address.
b) The client does not access the necessary function set or device capability resource links.
c) The client becomes unsynchronised with the utility server and does not flag an error.
Notes:
i) When test a communications client that does not claim conformance with the ConnectionPoint extension, the ConnectionPointLink resource is not reported by the utility server in step 4 of this test.
3.2.2 CON-01 SITE REGISTRATION (C)
3.2.2.1 Purpose
This test is intended to validate the client’s ability to register the ConnectionPoint of the site to the utility server when this method is used.
3.2.2.2 Test procedure
This test shall only be met by clients that intend to conform to the ConnectionPoint extension.
The steps SHALL be performed as described in Table 6. The test results SHALL be compared against the Expected Result column in Table 6.
Table 6 – Test steps for Communications Client – Site Registration
Step No. | Manual or utility server step | Expected comms client result |
1 | The client completes the discovery process as detailed in test 3.2.1, including receiving the EndDeviceListLink and ConnectionPointLink resource links from the utility server. | The client posts to the utility server’s EndDeviceListLink endpoint with an appropriate EndDevice payload. |
2 | The utility server responds to confirm the creation of the new EndDevice. | The client sends a valid connectionPointId to the ConnectionPoint endpoint and receives an appropriate validation from the utility server. |
3.2.2.3 Criteria
If during testing the client experiences one of the following events these are considered non- conformances with this requirement:
a) The client does not provide a valid connectionPointId to the utility server.