1: Why Volte?

2: Implementation (IMS Registration &

Architecture)
3: SIP Messages (IMS Signaling)
4: Overview of Bearers & Call Flow
5: Special Features in Volte

a) SRVCC (Single radio Voice Call Continuity)

b) ROHC (Robust Header Compression)
c) Optimized Segment
d) TTI Bundling
1: Why Volte?

Voice is carried in IP Packets (this approach called VoIP)

VOLTE: using overall approach that includes harder support of VOIP
approach, Specific feature of IMS and other entities of the EPS.
IMS : responsible of call control signaling such as Call origination and
termination , also route the call form 1 IMS network to other and 1
IMS network to other legacy network such as PSTN.

2: Implementation (IMS Registration &

Architecture)
Advantage:
In CSFB Data goes to 3G but lower rate. In Volte data rate is
same.
Call setup time get shorter.
3: SIP Messages (IMS Signaling)
3: Overview of Bearers & Call Flow

1: LTE uses the default EPS bearer to connectivity to a PDN.

2:Every UE assigned at least a one EPS bearer, the bearer
connects the UE to default Bearer Non guarantied Bit rates
3: Dedicated bearer is for non guarantied bit rate for Voice.

1: UE after powering up synchronizing with eNodeB &

establishing the signaling connection
2: UE sent attach request to MME
3: Along with the req to connect default PDN MME , MME
consults with the HSS for authentication.
4: After Successful authentication MME downloads the
subscription profile from the HSS.
5: Based on the Subscription profile and attach request MME
initiates the process to setup a default EPS bearer between the
UE and suitable PGW towards the default APN.
6: PGW after receive the request starts the creation of S5
portion (Approved QOS) of the EPS bearer and communicates
back to the SGW
7: MME then communicates with the UE .
8: Finally the S1-U Bearer is activated between UE & SGW.
9: PGW informs to MME for IP address allocates to the UE.
10 : After that UE starts to setup a QCI 5 & QCI 1 Bearer.
5: Special Features in Volte

a) SRVCC
b) ROHC (Robust Header Compression)

c) Optimized Segmentation
d) TTI Bundling
Input File for Craig palmer & Howard Tool
Process to Analyze B2 Trigger (SRVCC) in L3
Signature for TTI Bundling
SRS Over Estimation

LTE defines an optional sounding reference signal (SRS) in

the UL. UL channel quality, timing advance, and more. SRS
is transmitted by the UE using a known sequence, similar
to UL demodulation reference signal (DM RS), so the eNB
can use it to estimate the UL channel quality.
Power Drift (PUCCH)
Signatures to find out Accessibility Failures

->Check RF Condition
->Check SIP messages if there is any 500 level message (Core team support
required)
->In L1 & L3 find out what does happen during the process of call setup
->Check during the call setup time (time of QCI 1 bearer setup) if there is any
X2 or B2 event or any X2 & TAU collision .(we can see QCI 5,8 & 1 Bearer setup
& can conclude)
->

1: Core issues-
A:- Check in SIP messages if there is 500 level message

EXAMPLES:
1:-

2:
1: Special cases-
a: ) Known Issues (already in list of AR )
b: ) Message collision
c: ) During the call setup time B2& X2 do trigger

EXAMPLES:

1:-
2:-

3:-
In L1 messages check that UE transmits any packet or not this means UE is still in call
setup process.

In below mention example you can see that Activated bearer & X2 HO , during this UE
was not transmitting any packet
UE sent “CANCLE”
CBR : Constant BIT Rate
Activate
dedicated Bear

No
Packets
transmit

X2 HO

4:-
Parameters _ PHX Market
Drop Signatures:
1: UE declares RLF after failing to read SIBs following successful HO
2: UE declares RLF after failing to read SIBs following TTI-B enabling
3: UE declares RLF after Unanswered MR report : DL/UL Failures
4: UE declares RLF after OOS timeout
5: UE declares RLF after RACH MSG Failures
6: Triggered IRAT instead of SRVCC
7: UE1/UE2 Simultaneous SRVCC
8: SRVCC Collision with X2HO
9: Call dropped after SRVCC to 3G
10: Call dropped on 3G.
11: TA Drift AR 1-5067284
12: Incorrect DL PDCP SN on target after intra-eNB HO leads to
ROHC failures: AR- 1-5050344
13: Contention-free RACH 3 failure AR: 1-5056835
14: Unable to analyze - UE logs missing
15: Unable to analyze - Corrupted UE log files
16: Under Investigation
17: Early Termination
18: TAU and X2HO Collision
19: Incorrectly Pegged: Should be Accessibility Failure
20: UL Noise
21: PDCP 12bit-7bit border
22: Site Configuration Issue (Outside Polygon)

Signature 2: UE declares RLF after failing to read SIBs following

TTI-B enabling
Signature 3:UE declares RLF after Unanswered MR report : DL/UL
Failures
Signature 1: (JOT 4485): UE fails to reestablish on ATT
network after declaring RLF following with SRVCC
Signature 4: SRVCC Errors: Simultaneous SRVCC between
UE1 and UE2

Signature 5: SRVCC Errors: SRVCC Collision with X2 HO (HO

Cancellation)
Signature 10: Call dropped on 3G.
Signature13: Contention-free RACH 3 failure AR: 1-5056835
Case 1:
Case 2:
Signature 14 : 1-5050344 - Incorrect DL PDCP SN on target after intra-eNB
HO leads to ROHC failures.
L3 : You will get only Dedicated Bearer Activated , X2- Ho & after some time
deactivated.

L1 : You can see ROHC starts Failing & after HO & SN is non zero for the 1 st PDCP
packet.
Signature11: TA Drift AR 1-5067284
How to Start Analysis on QCAT& description about Key
Messages
1: Upload QXDM File
2: Filter out imp LTE messages