we need this earlier in 1H2022 (e.g., end of February) so we can start adapting xapps, simulators and otehr platfrom components.

(D)

if we now do not implement E2 node config and/or E2 connection update (whcih shoudl have been already an issues in E2APv1.1), let's make sure teh RIC reacts with proper error response to E2 node.

(A)

adapt the E2 node-side E2AP simulator to 2.0

also need to modify the (A1) bouncer-E2 simulator, (A2) DU implementation, and possibly proprietary implementations (e.g. CU, Viavi, ...)

(B)

note that RIC subscription failure has it's IE "RIC action not admitted list" removed

(c)

RIC Control request has one less value in its IE "RIC Control Ack Request" (ENUMERATED (NoAck, Ack, NAck…)). So xApps might have to change if they use that one.

–

See slide 7 from here https://static.sched.com/hosted_files/onesummit2021/62/ONeS_NA_2021_Thoralf_Czichy_Matti_Hiltunen_lessons_learned_near_rt_RIC_and_xApps.pdf

on what is mandatory to do.

copy and paste from the slideset. Item 3 is probably the most intrusive of all of them. (4) and (5) are also part of this JIRA item. Item (1) and (2) we handle as separate Jira items.

(1) RIC-851 E2APv2.0 “RIC Subscription Delete Required” procedure

• Enables E2 node to request deletion (E2 node overload, or subscription not relevant anymore)

(2)  (RIC-784, RIC-783) E2APv2.0 Clarified role of (optionally requested) RIC CONTROL ACKNOWLEDGE and (mandatory) RIC CONTROL FAILURE messages

• FAILURE to be sent if control timer on E2 expired, or if E2 node fails to execute RIC CONTROL request.

(3)  E2APv2.0 Adds transaction ID in various procedures

(4) E2APv2.0 E2 Node Component Configuration

IEs now contain additional component types by interface type (F1, X2, Xn, S1, …) and re-uses (by reference) the SETUP REQUEST/RESPONSE, CONFIGURATION UPDATE [ACKNOWLEDGE] of the underlying interface type.

(5) E2APv2.0 E2 SETUP REQUEST makes RAN function list and E2 node component configuration mandatory (at least one entry)