Document status
DRAFT
Document owner
Owner Details

+972-54-2891166,   ab600d@intl.att.com


RAN States

E2M supports the following state for each RAN:

StateDescription
Null

No RAN in DB

DisconnectedEither the connection failed, E2T dies or E2T initialized
ConnectedRemote RAN sends Setup Request  
Shutting-DownTemporary state during Red Button (From Dashboard)
Shut-DownPersistent state after Red Button (From Dashboard)

RAN Events

We have the following events which might change SM:

  1. Setup Request from RAN
  2. Connection failed from E2T
  3. E2T Initialized - E2T Restart (New E2T or existing)
  4. Red Button (From Dashboard)
  5. Keep Alive (KA) in E2M discover E2T isn't responding


RAN State Machine - States vs. Events

RM = Resource Management

States ==> 

Events

Null

Disconnected

Connected

Shutting-Down

Shut-Down

Setup Request from RAN

Connected;

Update RM;

Send Setup Response;

Update RM;

Disconnect-

Connected; (See note below)

Update RM;

Send Setup Response; 

Ignore

Connected;

Update RM;

Send Setup Response;

SCTP Failure (Lost Connection)

Error

Error

Disconnect;

Update RM;

Shut-down

Error

E2 Initialize


Ignore

Update RM;

Disconnect-



Red Button


Shut-down

Shutting-Down;

Tear down connection to E2T

Error


KA discover E2T dies


Ignore

Disconnect;

Update RM;



Note 

Flow of Setup -


In case Setup Request in Connected State - Update DB (it might be different), Update RM (it might be even different E2T in rare scenario), Return Setup Response.


Flow charts in the RAN State

State = Null (RAN doesn't exist in DB)

Null State

State = Connected

Connected State

State = Disconnected

Disconnected State


State = Shutting Down

Shutting Down State

State = Shut Down  

Shut Down State