Signalling connection setup
triggered by initial UE message
UE
Initial UE
message
RBS
pmS1SigConnEstabAtt +
pmS1SigConnEstabAttEm +
step for cause ”Emergency”
pmS1SigConnEstabAttHpa +
step for cause ”High Prio Access”
pmS1SigConnEstabAttMod +
step for cause ”Mobile Originating Data”
pmS1SigConnEstabAttMta +
step for cause ”Mobile Terminating Access”
pmS1SigConnEstabAttMos +
step for cause ”Mobile Originating Signalling”
pmS1SigConnEstabAttEm +
pmS1SigConnEstabAttHpa +
pmS1SigConnEstabAttMod +
pmS1SigConnEstabAttMta +
pmS1SigConnEstabAttMos +
Yes
RBS timeout
on initial context setup
request from MME?
No
B
MME sends initial context
setup request to RBS
Any message
received on the S1
logical connection ?
Stepped for any of the following
messages:
S1 downlink NAS transport
S1 UE context release command
S1 initial context setup request
S1 reset
RBS
Initial context
MME
setup request
(E-RABs, Sec keys)
No
Yes
pmS1SigConnEstabSucc +
pmS1SigConnEstabSuccEm +
pmS1SigConnEstabSuccHpa +
pmS1SigConnEstabSuccMod +
pmS1SigConnEstabSuccMta +
pmS1SigConnEstabSuccMos +
pmUeCtxtEstabAtt +
pmErabEstabAttInit +
pmErabEstabAttInitArp +
pmS1SigConnEstabSuccEm +
step for cause ”Emergency”
pmS1SigConnEstabSuccHpa +
step for cause ”High Prio Access”
pmS1SigConnEstabSuccMod +
step for cause ”Mobile Originating Data”
pmS1SigConnEstabSuccMta +
step for cause ”Mobile Terminating Access”
pmS1SigConnEstabSuccMos +
step for cause ”Mobile Originating Signalling”
Note: Corresponding
counter per QCI:
pmErabEstabAttInitQci
Stepped for each E-RAB that has
the given ARP Priority Level
A
L0000312G