-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
RICP_T4 Sprint B.D3
The RIC ID (See US 213) is taken from Configuration.
The list of supported Functions should be taken from SETUP Request message,
and the List of not Accepted Functions should be empty.
The format is XML (E2T decode it to ASN.1).
The RMR (Setup Response 12002) should contain the MEID that we received. Failure in the RMR - error.
| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
| Message Type | M | 9.2.3 | YES | reject | ||
| Global RIC ID | M | 9.2.4 | YES | reject | ||
| List of Accepted Functions | 0 .. <maxofRANfunctionID> | Complete list of Functions accepted by NEAR-RT RIC | YES | Reject | ||
| >RAN Function ID | M | __ | 9.2.8 | Id of the declared Function | YES | reject |
| List of not Accepted Functions | 0 .. <maxofRANfunctionID> | Complete list of Functions not accepted by NEAR-RT RIC | YES | reject | ||
| >RAN Function ID | M | __ | 9.2.8 | Id of the declared Function | YES | reject |
| >Cause | M | __ | 9.2.1 | Reason for not accepting function | YES | ignore |
Look on the E2M State Machine https://wiki.o-ran-sc.org/display/RICP/E2M+-+State+Machine, especially the text Note below the RAN State Machine - States vs. Events chapter:
- RMR Failure;
- RM Failure
- Setup in case Connected
DoD:
- Simulate Setup Request with full XML. See RMR Setup Response is sent to E2T and arrives there w/out error. See the RIC ID, List of functions is as expected
- Simulate the same but RMR Failure - see it behaves like we expected (Save in DB and Error Log)
- Simulate the same but RM Failure - see it behaves like we expected (Save in DB and Error Log)
