Revision Description	Time	Swagger Ready
Adding new methods - Insert, Update and Delete ENB. Add new errors. Added Additional Cell Information for both eNB and gNB (in the Insert eNB Request, Update eNB) Changing the response of Get NodeB - adding more information to the Cell Object	TBD
Changing the end point of Update GNB. Adding more information to the Cell Object like Update eNB	TBD
Supporting E2M Set Parameter (New method) with Enable RIC parameter	May 2020	Ready
Get All NodeB States Request changed its End-Point URL Adding Connection Status in RAN object in Get All NodeB States Response	TBD
RAN Definition in the RAN List table turn to be Array of bytes (We don't decode the ASN.1)	June 2020	Ready
AD SDL Notification Description	June 2020	NA

API Request Overview

Info
In the URI of each method in this document we write “V#” instead of V1, since when moving from Version to Version sometimes we forgot to update it in the document. So to make our life easier, V# covers the Latest version.

...

Reset nodeb Request (Deprecated)

when a new NodeB (eNB or gNB) is added, Updated or deleted in RNIB, or when a state of NodeB is changed, the following SDL Notification generated.

E2M supports 2 types of SDL Notification, the client can subscribe to each of them:

In the following scenarios E2M generates SDL Notification:

Issue	NodeB State Change	NodeB Modification	Comments
Setup Request from RAN	+		Only in case the NodeB was previously Disconnected
Insert eNB API		+
Update eNB, Update gNB API		+
Lost Connection Red Button (Shut Down)	+		Only in case the NodeB was previously Connected
E2T Restart, Keep Alive decides this E2T Instance is dead		+	Only in case this NodeB was under the control of this E2T Instance and it was previously Connected
Delete eNB		+

Example of NodeB State Change

1592819435.658629 [0 ?:0] "PUBLISH" "{e2Manager},RAN_CONNECTION_STATUS_CHANGE" "gnb_208_092_303030_CONNECTED"