-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
RICP_T4 Sprint B.D3
In the new version of the E2AP protocol the RIC has a Global RIC identifier that is defined in the spec.
Each response that the RIC sends to gNB node should contain this ID.
- Define parameter in the Configuration and map it in HelmChart.
- Remove the current Environment Variable from the Execution Command Docker.
- We need to make sure to return this ID in every message that requires it
Acceptance:
Deploy E2M in Dev-2-Dev environment with specific RIC ID. See it appears now in Configuration file.
Hila wants to see the Log.
Automation Tests passed successfully.
9.2.4 Global RIC ID
This IE is used to globally identify an Near-RT RIC.
IE/Group Name | Presence | Range | IE type and reference | Semantics description |
PLMN Identity | M | __ | 3GPP 38.423 clause 9.2.2.4 | |
Near-RT RIC ID | M | __ | BIT STRING (SIZE(20)) |
TP:
Given | When | Then |
---|---|---|
GLOBAL RIC ID is "whatever" | E2M is up | configuration is populated with this value |
GLOBAL RIC ID is "whatever" | E2M received an e2 setup request | e2 setup response is populated with this value |
1.
|
Add Global RIC Id parameter/s to configuration (remove value from docker run command) | Done | Unassigned | |
2.
|
Update helm chart and test value is retrieved successfully in D2D ENV | Done | Unassigned |