-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
RICP_T4 Sprint B.D3
Verify user is able to get Node ID and Connection Status by using RNIB reader or by using E2M REST API (existing APIs).
TP:
Given | When | Then |
---|---|---|
A new E2 Setup completed successfully for RAN "test" | [Client -> E2M] HTTP GET v1/nodeb/test | AssociatedE2TInstanceAddress is populated with e2tAddress ConnectionStatus is CONNECTED RanName is test NodeType is GNB |
We don't have any test2 RAN on DB | [Client -> E2M] HTTP GET v1/nodeb/test2 | 404 NOT FOUND |
DB error | [Client -> E2M] HTTP GET v1/nodeb/test2 | 500 Internal server error |
- is cloned by
-
RIC-284 Setup D2D env. on new VM (to enable dev. testing)
- Done
1.
|
The exploration of the Gnbe simulator (v 3.2-32) | Done | Natalia Sheshukov | |
2.
|
Integration: Execute an E2 SETUP flow from RAN to RIC | Done | Unassigned | |
3.
|
Verify automation passes | Done | Unassigned | |
4.
|
Verify GetNodeb returns values of newly setup RAN | Done | Unassigned |