| Document status | DRAFT |
|---|---|
| Document owner | |
| Owner Details | +972-54-2891166, ab600d@intl.att.com |
RAN States
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) |
RAN Events
We have the following events which might change SM:
- Setup Request from RAN
- Connection failed from E2T
- E2T Initialized - E2T Restart (New E2T or existing)
- Red Button (From Dashboard)
- Keep Alive (KA) in E2M discover E2T isn't responding
RAN State Machine - States vs. Events
States ==> Events | Null | Disconnected | Connected | Shutting-Down | Shut-Down |
|---|---|---|---|---|---|
Setup Request from RAN | Send Setup Response; Update RM; Connected | Update RM; Disconnect- | Send Setup Response; | Ignore | Send Setup Response; Update RM; Connected |
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; |
RM = Resource Management
Flow charts in the RAN State
State = Null (RAN doesn't exist in DB)
State = Connected
State = Disconnected
State = Shutting Down
State = Shut Down
