Document status | DRAFT |
---|---|
Document owner | |
Owner Details | +972-54-2891166, ab600d@intl.att.com |
E2M supports the following state for each RAN:
State | Description |
---|---|
Null | No RAN in DB |
Disconnected | Either the connection failed, E2T dies or E2T initialized |
Connected | Remote RAN sends Setup Request |
Shutting-Down | Temporary state during Red Button (From Dashboard) |
Shut-Down | Persistent state after Red Button (From Dashboard) |
We have the following events which might change SM:
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; |
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.