Page History

Abbreviation

General

The RIC contains several E2T Instances, each one of them manages several RANs. E2M is the one which manages them. It means:

...

• Each Configurable time (100 Milliseconds) E2M sends broadcast KA Request to all living E2T Instances through the RMR.

• Every E2T Instance which gets it, responds with KA Response.

• If any E2T Instance doesn’t respond for a configurable time (400 Milliseconds) - E2M “kills” it:

  • E2M asks the K8S to kill the E2T Instance.

  • E2M divides disassociate the RANs associated with this “dying” instance to other living E2T Instances. If not found - they are treated as Orphans.E2M Updates the Routing Managers about the association of the RANs to other E2T Instances, about the Orphans (if any) , signs them as disconnected and Updates the RM about the disassociation of the RANs and about the deletion of the dead E2T Instance.

  • If success - E2M stores in its DB the new associations and sends Setup for this RANs through the updated RMR

• There is some logic how to sync between parallel flows - Killing an E2T Instance parallel to E2 Initialize arrives. See below.

...

• As described, when E2T Instance starts running and finished its Initialization, it sends RMR message (E2 Initialization) to E2M.

• If this is a new address (IP) then -

  • E2M updates the Routing Manager there is new E2T Instance

  • If success - E2M Registers it in the E2M DB. If fail - E2M does nothing. E2T will sends another time E2 Initialize to E2M if no KA Request arrives during the 500 Milliseconds after the previous E2 Initialize.

• If

  there are orphans - E2M will handle them here (See below)

  If this is an existing E2T Instance, then

  • E2M re-sends Setup for this RANs through the RMR. The RMR still contains the association of the RANs to this E2T Instancedisassociate the RANs associated with this "restart" instance, signs them as disconnected and Updates the RM about the disassociation of the RANs

• There is some logic how to sync between parallel flows - Killing an E2T Instance parallel to E2 Initialize arrives.

...

• Active (normal state). Selector mechanism can choose it.

• To be deleted - KA moves it to this state in DB the moment is understand it is dead. Selector mechanism can’t choose it. It is stay in this state until Routing manager success (in this case the entire entry is deleted) or failure, which is moved to the next step

  Routing Manager Failure

  In this state Selector mechanism can’t choose it.

In

...

In case E2T initialize arrives and this E2T is in “To be Deleted” state - Don’t do anything. E2T will send another E2T initialize in case no KA during 300 milliseconds after E2 Initialize.

Association RAN to Instance

...