Page History

...

current State / trigger	State = Active	State =To be Deleted
KA decide to kill E2T instance	Move to “To be deleted” State; Try to find POD in K8S and if found kill it; Even if fails - continue. Disassociate all RANs, Delete the E2T Address at all. Update RM, if fail – error but continue In order to distinguish between 2 sequences KA cycle, KA updates the Timestamp when it moves the RAN to this state, and sees it wasn't stayed in this state too long. It is called E2 Instance Deletion Timeout MS (Micro seconds)	(Transient State, should not occurs) Do all the steps Just like in Active (Previous Cell), except updating the state which is already “To be Deleted”.
E2 Initialize	Don’t update RM Disassociate all RANs and inform RM	Ignore: E2T will send another E2 Initialize if no KA Request after previous E2 Initialize for some times.
KA Response	Update Timestamp	Ignore. This Instance is about to deleted
E2M Restart	Update Timestamp	?????

...

E2M updates the RM in the following flows:
1. When a new E2T Instance Initialized.
2. When a a Setup Request arrived from the RAN and associated to existing E2T Instance
3. When KA kills existing E2T Instance - in this update it also disassociates list of RANs and also delete E2T Instance
4. When RAN lost connection
5. When a Red Button is requested - E2M dissociate all RANs
6. When existing E2T Instance initialized, it disassociates list of RANs served by this Instance
Also, when RM initialized, it queries E2M on the mapping between E2T and RANs and update the RIC with the new RMR. See E2 Manager R3 Interface DesignDesign#GetAllE2TRequest
There are 4 REST APIs Routing Manager published. U can read their Swagger at Routing Manager Swagger

...

Show all results