-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtcdd3_1.txt
143 lines (72 loc) · 3.6 KB
/
tcdd3_1.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
1.a
5.4.6.1
Commissioner and Commissionee discover each other and connect via the discovery mode applicable for the DUT.
Commissioner and Commissionee can discover each other and connect to each other.
Refer to Discovery test case 6.2.2 (DD-6.2.2) for validation steps.
1.b
5.4.6.1
Establish encryption keys with Password Authenticated Session Establishment on the commissioning channel
Refer to Secure Channel test case 6.2.1 (SC-6.2.1) for validation steps.
1.c
5.4.6.1
Commissioner arms Fail-safe timer on the Commissionee using ArmFailSafe command
Refer to General Commissioning Cluster test case TBD for validation steps (spec 8.11.7.3, 8.11.6.3)
1.d
5.4.6.1
Commissioner SHALL configure at the Commissionee UTC time, timezone, DST offset, and regulatory information at the Commissionee.
Refer to Time Synchronization Cluster test case TBD (spec 8.18) and General Cluster test case TBD (spec 8.11.7.1) for validation steps.
1.e
5.4.6.1
Commissioner establishes the authenticity of the Commissionee as a certified CHIP device.
Refer to Device Attestation test case TBD (spec 6.1.3) for validation steps.
1.f
5.4.6.1
Commissioner configures Fabric information using SetFabric command.
Refer to General Commissioning Cluster test case TBD for validation steps (spec 8.11.7.1)
1.g
5.4.6.1
Commissioner requests operational CSR from Commissionee with OperationalCSRRequest command
Refer to Operational Credential Cluster test case TBD for validation steps (spec 8.23.7.5)
1.h
5.4.6.1
Commissioner generates or otherwise obtains an Operational Certificate containing Operational ID in response OperationalCSRRequest command using ecosystem-specific means
Refer to Operational Credential Cluster test case TBD for validation steps (spec 8.23.7.5)
1.i
5.4.6.1
Commissioner configures operational credentials
Refer to Operational Credential Cluster test case TBD for validation steps (spec 8.23.7.5)
1.j
5.4.6.1
Commissioner configures ACL.
Refer to Access Control List Cluster test case TBD for validation steps (spec 7.4.9)
1.k
5.4.6.1
Commissioner configures the operational network at the Commissionee.
Refer to Network Commissioning Cluster test case TBD for validation steps (spec 8.10.8.*)
1.l
5.4.6.1
Commissioner triggers the Commissionee to connect to the operational network
Verify if the device is on the network by checking for the device on the network.
Refer to Network Commissioning Cluster test case TBD for further validation steps (spec 8.10.8.14)
1.m
5.4.6.1
Commissioner and Commissionee discover each other on the operational network using operational discovery
Refer to Secure Channel test case TBD for further validation steps (spec 4.2.2)
1.n
5.4.6.1
Commissioner and Commissionee establish encryption keys with CASE
Refer to Secure Channel test case TBD for further validation steps (spec 4.13.2)
1.o
5.4.6.1
Commissioner and Commissionee perform commissioning complete message exchange using CommissioningComplete command and CommissioningCompleteResponse command
Verify if both Commissioner and Commissionee can talk to each other on the network.
Verify that the commissioning connection is terminated.
Refer to General Commissioning Cluster test case TBD for validation steps (spec 8.11.7)
2.a
5.4.6.1
Same steps as 1.a-1.o. Force Fail any step between 1.a and 1.j.
The Commissioner and Commissionee terminate commissioning. Should go back to step 1a and start commissioning again.
3.a
5.4.6.1
Same steps as 1.a. Force Fail any step between 1.k and 1.o
Commissioner and Commissionee returning to 1.k (configuration of operational network information) and continue the commissioning flow again.