Null 7
Null 7
BY- sOLEX 1
2
Now UE Stablished A DRB With EnodeB, after that EnodeB send "initial Context setup
complete" response to MME,
Now MMW send " Modify Bearer Request " to SGW and SGW Response with "Modify
Bearer Response"
Now SGW Create Default Bearer with EnodeB, and SGW start sending Buffered
Downlink data to UW
Now LTE attach is completed.
UE send Invite Request to PCSC, Now PCSCF forward invite Request to SCSCF, now
SCSCF perform ENUM Query to obtain address of Terminating B party ICSCF, Once
SCSCF got the address of Terminating B party ICSCF, IT forward the Invite Request to
Terminating ICSCF.
Terminating end ICSCF is the entry point for MT call. Once it received the request
from Originating end SCSF it did LIR/LIA to HSS for obtain the address of terminating
end SCSF.
6. Which LTE Core and IMS Node involved when we making IMS call and how many
protocol protocols are involved?
a. In LTE-MME HSS PCRF and
b. IMS PCSCF ICSCF SCSCF DNS ENUM MNP-DB TAS OCS IMS-HSS.
c. Protocol used SIP and Diameter.
7. How you use to take trace and its analysis at message level, Tell me how ypu perform
BY- sOLEX 2
3
Test Cases?
Prerequisite.
First get the remote access through visor tool.
Reserve the particular imsi devise. Asked the lab team to rout the sim According the test
cases requirement.
TAC for the tac environment region Node trace.
Log in Credentials.
For Execution part-
First we click on batch file script, now we enter in RMTS mode. choose 2 for PP. It
connects us to lab devices remotely. Now we start a dry test. Flight mod on off to
check everything working fine at coverage level.
Log in to Wireshark server through putty.
Log in through ip and port no 22. Then give login credentials.
Now I am in Wireshark server. Used pwd command and cd command to work in my path
folder. Now start testing.
BY- sOLEX 3
4
For this first we switch as a root user for taking the trace.
Sudo su -
Root log in
Su - rtp99 User.
When I analysis on Wireshark if I find out a bug in a call flow, I raise it to defect
manager through JIRA tool. Then troubleshooting team fix it, once I get back it by
defect manager then I retest to verify and then close it.
• UE sends SIP “INVITE” msg to P-CSCF which contains A Party Number along
with SIP URI and B Party Number Tel URI.
• P-CSCF sends “INVITE” to S-CSCF along with SDP (Session Description Protocol)
offer A, which includes media capabilities and Codecs to be used.
• S-CSCF executes originating trigger IFC (initial Filter Criteria). IFC is list of
conditions upon which an Application Server (NTAS) shall be contacted. It can be
Registration, Originating INVITE, terminating INVITE (Registered), terminating INVITE
(De Registered). In this case, it is Originating INVITE. S-CSCF sends originating
“INVITE” to TAS.
• TAS does MNP dip query with STP to get LRN of B party. TAS also executes
originating A party services. TAS sends “INVITE” to S-CSCF along with B party number
with LRN.
• S-CSCF does iNUM query for B party (LRN+ 10-digit number) to check if B party
is VoLTE subscriber or not. Here, B party is in CS domain. So, iNUM sends response
that Number not found to S-CSCF.
• S-CSCF sends SIP “INVITE” to BGCF and BGCF will send to MGCF (MSS or GCS)
based on B party number routing table defined for break out calls. MGCF will
do further routing of B party in CS domain and sends 180 ringing to S-CSCF. Once, B
party answers, conversation will happen,
It is a set of signaling protocol. It is used for call setup, teardown a telephonic call (GSN
& PSTN).
BY- sOLEX 4
5
A Link- Access Link(SSP-STP)- It connect home network. SCP rout the message to home
network STP using A-Link.
B Link- Bridge Link(STP-STP)- Peer to Peer STP- It is used rout the call to one STP to
another STP.
C Link- It used for reliability. It is called Mated C-Link. If Some link is failures, then we
used mated link.
E Link- Home SSP to Visited STP.
F Link- It is used to connect one SSP to another SSP.
13. If any pod is not going to deploy then what you will do?
First I check on kubectl get pod then kubectl describe pod for configuration error and
then I check all occurred event through kubectl get event.
14. What kind of issue you are facing in deployment and how you have resolved it?
We have encounter configuration mismatch issue in deployment. For e.g. sometime
pods are not scheduled due to labels mismatch with cluster nodes.
Nodes selector and node affinity updated with incorrect labels in helm chart value.
yaml.
Secondly in recent deployments AUSF pod is not running fully due to Config error
UE-auth pod resource metrics release value is present as 2 instead of 1 for initial
deployment.
BY- sOLEX 5
6
18. 5G Architecture?
1. Kube Proxy
2. Kubelet
3. Pods
4. Container Engine
BY- sOLEX 6
7
BY- sOLEX 7
8
Note- we can register 1 IMPU at multiple end point (ie devices) so to register 1 user identity
at multiple end point we Required some identity which can differentiate multiple devices,
so here Contact header comes into pictures, contact header allows us to register multiple
end points with single user identity, and it also required for end to end communication (i.e.
device to device communication)
BY- sOLEX 8
9
to HSS to Retrieve SCSCF name stored in HSS during 1st attempt, now HSS response with
UAA (user Authorization answer) to ICSCF, now ICSCF forward registration request to
SCSCF, SCSCF checks IP Security association and Match RES value with XRes if Both Matches
then SCSCF Send SAR(Server Assignment Request) to HSS to download subscriber services
related profile, Now HSS send SAA ( server assignment answer) which carries user service
profile and IFC.
Now SCSCF send 200O OK Response to ICSCF and add " Service Rout “header which
contains address of SCSCF, now ICSCF forward 200 OK Response to PCSCF, PCSCF Save
service rout header and forward 200O OK response to UE, As of now IMS registration is
completed.
UE send Invite Request to PCSC, Now PCSCF forward invite Request to SCSCF, now
SCSCF perform ENUM Query to obtaine address of Terminating B party ICSCF, Once
SCSCF got the address of Terminating B party ICSCF, IT forward the Invite Request to
Terminating ICSCF,
Now ICSCF Query The SLF to Know Which HSS Required to Contact for user Location,
Now ICSCF send LIR (Location info Request) to HSS find the address of SCSCF, HSS
Response with LIA (Location Info Answer).
Now ICSCF forward INVITE Request to SCSCF, Now SCSCF Received Invite request and
forward to PCSCF and PCSCF Trigger PCRF to Reserve Resources and Creating
Dedicated Bearer for Termination user
After that PCSCF forward invite Request to B party,
Now B Party Response with " 183 session in progress" which also carrying SDP
Answer.
Now "183 session Progress Response “Received by A party, as of now Dedicated
Bearer is Created at both end but Precondition not met yet.
Now A Party Send " PRACK " upon Receiving "183 session Progress" Response.
Which Carry Final Select Codec.
Now B Party “Prack " and Agree with Final Selected Codec and Response "200OK "
for Prack.
As of now Codec Negotiation Done, but Precondition Not Meet Yet.
Now A Party Reserved Enough Network Resources and Send " Update " Request to B
party, B party Also Reserve Enough Network Resources and Response with "200OK "
for Update.
As of now Precondition meet, and Codec Negotiation is done.
Now B Party Ready to Ring
Now B Party Start Ringing and Send " 180 Ringing " to A party, A Party Received”
180R" and Send " PRACK" to make “180R " Reliable.
Now B Party Send 200OK for "PRACK".
BY- sOLEX 9
10
54. Tell me the name of networks services you created through LAN?
Ldap LAN/HTTP2 lan/LI lan/HSM lan/Trigger lan/etc.
55. *Have you done Netact Integration?
56. *Tell me about RTP error, Internal log, how you collect log?
57. How you check health?
Kubectl get pod
Kubectl get node
58. Which IP Addr. Used for login in keyclock.
We used ZTS ip addr & used 9090 port for login.
59. Why you do certificate provisioning & Netconf upload?
We do certificate provisioning to get access/permission for connectivity for udm
microservise, for that we upload secret in Vault Agent of ZTS and Netconf in CA-
server for all configuration and integration of microservises. We upload secret
through key file (key.pem, cert.pem, cacert.pem) authentication & used curl
command.
60. Difference between Pod and container?
A pod is a runtime specification of a container. A pod provides more declarative way
of defining through yaml file. We can run more than one container in a pod. They can
have taught each-other, can share resources & storage.
BY- sOLEX 11
12
BY- sOLEX 12
13
BY- sOLEX 13