Professional Documents
Culture Documents
Volte E2E Use Cases - Exercises: Checklist
Volte E2E Use Cases - Exercises: Checklist
TABLE OF CONTENTS
DUTY A: Perform Trace Analysis ..................................................................................................................................................................... 2
TASK A-1: EPC VoLTE Registration .............................................................................................................................................................................................. 2
TASK A-2: IMS VoLTE Registration ............................................................................................................................................................................................... 6
TASK A-3: VoLTE Call Setup – EPC and IMS ............................................................................................................................................................................... 9
TASK A-4: SRVCC – EPC, MSS and IMS ................................................................................................................................................................................... 12
TASK A-5: IMS Centralized Services (ICS): O-SDS .................................................................................................................................................................... 15
TASK A-6: IMS Centralized Services (ICS): T-SDS ..................................................................................................................................................................... 18
TASK A-7: (OPTIONAL) VoLTE Call Setup with Pre-conditions .................................................................................................................................................. 20
Checklist
4. How many Authentication vectors are sent from HSS to MME? MME_REG.pcap
6. Which are allowed APNs for this UE? Which of them is the default one? MME_REG.pcap
7. Which QCI and ARP are configured for the default APN? Why are they defined in this way? MME_REG.pcap
8. Which IP address is allocated to the UE? In which message and field this information can be found? MME_REG.pcap
3. Which
3 kind of access to MMTel network is used by the user? IMS_REG.pcap
4 IMS user authentication performed? If yes – what kind of authentication mechanism is used?
4. Is IMS_REG.pcap
5. Which
5 parameters does SGC/ATCF add in the Path header? What are they used for? IMS_REG.pcap
rd
7. Identify the part of the trace that belongs to the 3 party registration. IMS_REG.pcap
8. There are 5 DIAMETER transactions between MTAS/SCCAS and HSS: 306 (User-DataRequest), 306, 306, IMS_REG.pcap
308 (Subscribe-NotificationsRequest) and 306. What is the purpose of the second 306 transaction? How is
the data sent from HSS to MTAS/SCCAS used?
9. What is the purpose of the third 306 transaction? How the data sent from HSS to MTAS/SCCAS is used? IMS_REG.pcap
11. Which node does MTAS/SCCAS send the MESSAGE message to? How is it routed? IMS_REG.pcap
12. What data is sent in MESSAGE? How are they used? IMS_REG.pcap
1. Open
2 IMS_CALL.pcap and MME_CALL.pcap trace files using WireShark.
2. Which
3 codec does UE want to use as a first choice? IMS_CALL.pcap
3. Is
4 the called user connected to the packet network (EPS) or CS network? IMS_CALL.pcap
4. Which
5 parameter indicates that the call is made from the UE connected via LTE PS, not CS? In which header IMS_CALL.pcap
it is located and which node adds it?
5. Explain the triggering of application servers on the originating side of the call? IMS_CALL.pcap
6. What makes P-CSCF to contact SAPC and for which purpose? IMS_CALL.pcap
7. Which media type is the dedicated EPS bearer required for? IMS_CALL.pcap¸ MME_CALL.pcap
8. Which will be the first point of contact for the RTP media flow for the UE (IP address)? IMS_CALL.pcap¸ MME_CALL.pcap
9. What is the QCI and ARP value for the new dedicated EPS bearer? MME_CALL.pcap
10. Which IP addresses identify E-UTRAN Access bearer (S1-U interface) on eNodeB respective SGw? MME_CALL.pcap
1. Open
2 MME_CALL.pcap, IMS_CALL.pcap and MSC_CALL.pcap trace files using WireShark.
2. In
3 the MME_CALL.pcap trace: which was the first message that showed that handover takes place? MME_CALL.pcap
3. Which
4 parameter(s) indicates that it is an SRVCC handover? MME_CALL.pcap
4. What
5 are the MSISDN and STN-SR values which are sent from MME to MCS-S via Sv interface? MME_CALL.pcap,
MSC_CALL.pcap,
IMS_CALL.pcap
5. What is the called number found in the Request-URI header of the INVITE message sent from MSC-S? MSC_CALL.pcap,
Compare it to one of the values found in step4.
6. Which number is inserted in the P-Asserted-Identity header of this INVITE message? MSC_CALL.pcap
8. Which contact information (IP address and port for the RTP media flow) is sent to MSC-S? Compare your IMS_CALL.pcap
answer to the one for Step8 (Exercise A-3).
9. What is the purpose of the INVITE message sent later from the ATCF? IMS_CALL.pcap
10. What is the called number found in the Request-URI? Compare with the result of Step 12 (Exercise A-2) IMS_CALL.pcap
11. What does Request-URI in the BYE (sent from SCCAS) refer to? IMS_CALL.pcap
1. Open
2 ICS_O-SDS.pcap trace file using WireShark.
2. Which
3 node does SPC=3-1018 belong to? ICS_O-SDS.pcap
3. What
4 were the calling and called parties numbers? ICS_O-SDS.pcap
4. Which
5 IMRN was chosen for this session setup? How is IMRN used? ICS_O-SDS.pcap
5. How
3 is INVITE from MGC routed to SCC-AS? ICS_O-SDS.pcap
6. How
4 does SCC-AS understand that it should treat incoming INVITE request (frame 11) as routed on PSI? ICS_O-SDS.pcap
7. Where
5 does the information inserted in PANI header come from (frame 23)? ICS_O-SDS.pcap
8. What
3 makes I-CSCF handle the call as originating one? ICS_O-SDS.pcap
9. What
4 is the current calling-user registration status in HSS? ICS_O-SDS.pcap
10. How
5 does SCC-AS understand that it should handle originating unregistered session, when triggered by S- ICS_O-SDS.pcap
CSCF?
11. Which
5 access information does SCC-AS caches for the calling user? ICS_O-SDS.pcap
12. Is
5 it possible to figure out which access type/domain is used by the called user? ICS_O-SDS.pcap
1. Open
2 ICS_T-SDS.pcap trace file using WireShark.
2. Which
3 node does SPC=3-1004 belong to? ICS_T-SDS.pcap
3. What
4 were the calling and called parties numbers? ICS_T-SDS.pcap
4. Which
5 IMRN was used for this session setup? How is IMRN built? ICS_T-SDS.pcap
5. What
3 is IMRN used for? ICS_T-SDS.pcap
6. Explain
4 the triggering sequence (communication between S-CSCF and SCC-AS/MTAS). ICS_T-SDS.pcap
7. Assuming
4 that the called user in this trace provided exactly the same access information as the calling user ICS_T-SDS.pcap
in the previous trace (exercise A-5) – which T-ADS decision is taken by SCC-AS?
8. Explain
5 the format of the called number in the Request-Line (Frame 85). ICS_T-SDS.pcap
1. Open
2 VoLTE PreCond.pcap trace file using WireShark.
2. Does
3 the caller client support preconditions and reliable provisional responses feature? VoLTE PreCond.pcap
3. What
4 is the current qos precondition status reported by the caller client at call initiation? VoLTE PreCond.pcap
4. What
5 is the desired precondition status on the caller side? VoLTE PreCond.pcap
5. Locate the first 183 response. What is the desired precondition status on the callee side? VoLTE PreCond.pcap
6. What is the current precondition status on the callee side? VoLTE PreCond.pcap
7. Which options the receiver of 183 Session Progress message should support? VoLTE PreCond.pcap
8. At what point P-CSCF on originating side initiates dedicated bearer establishment? VoLTE PreCond.pcap
9. How does PCRF find an IP-CAN session for the given user after receiving AAR message? VoLTE PreCond.pcap
10. What is the current qos precondition status reported by the caller client when UPDATE message is sent? VoLTE PreCond.pcap
11. What is the current qos precondition status reported by the callee client when UPDATE is confirmed with 200 VoLTE PreCond.pcap
OK?