For most Mobile Internet Operators "I can't access internet with my phone" contributes the most number of calls into a call center. The reason for most of the complaints is usually simple - (Wrong Configuration in the Mobile Phone APN Settings).
In order to improve customer experience & at the same time improve on the data revenues for operators, 2 Functions are critical in the PS N/W.
The APN usually indicates the type of service a give customer wants to access eg, INTERENT, WAP,MMS etc, Usually the customer needs to configure the right APN to access the desired services.But Why work in this approach?, Customers dont want this stress.
There are 2 ways through which Operator can simplify the APN phone configuration issue and provide better user experience:
1). OTA (Over the Air) Normally realised by CS Core Network interworking with OTA server to realise the Function.( This is not my intrest for now)
2.) APN Correction Function: This Function is usually deployed in the SGSN and whenever a wrong APN is sent in Create PDP Context Activation request, the SGSN corrects it and then sends to DNS to obtain GGSN IP address hence PDP Context Activation Success Rate Improves & Users access service more smoothly.
The Core Principle of the APN Correction Feature is as shown below:
1). In the PDP Context Activation Procedure, the SGSN checks the Triplet carried in the PDP Context Activation Request against the Triplet Stored in the Home Location Register (HLR). This triplet includes: Access Point Name, PDP Type, PDP Address etc.
2). If these 2 Triplets are not consistent the SGSN rejects the PDP context Activation procedure.
3). This type of inconsistency is normally caused by wrong parameter settings in the MS/UE.
4.) The requested information correction procedure is used to minimize these failures. So SGSN would have a default Mapping say If APN-NI (I explained this on Day 1 under APN composition) requested by MS/UE is Not Matched, Use default APN as Internet and allow user to access as Long as this APN being corrected to is defined in the HLR for this Subscriber.
#PerfectionIsANorm
In order to improve customer experience & at the same time improve on the data revenues for operators, 2 Functions are critical in the PS N/W.
The APN usually indicates the type of service a give customer wants to access eg, INTERENT, WAP,MMS etc, Usually the customer needs to configure the right APN to access the desired services.But Why work in this approach?, Customers dont want this stress.
There are 2 ways through which Operator can simplify the APN phone configuration issue and provide better user experience:
1). OTA (Over the Air) Normally realised by CS Core Network interworking with OTA server to realise the Function.( This is not my intrest for now)
2.) APN Correction Function: This Function is usually deployed in the SGSN and whenever a wrong APN is sent in Create PDP Context Activation request, the SGSN corrects it and then sends to DNS to obtain GGSN IP address hence PDP Context Activation Success Rate Improves & Users access service more smoothly.
The Core Principle of the APN Correction Feature is as shown below:
1). In the PDP Context Activation Procedure, the SGSN checks the Triplet carried in the PDP Context Activation Request against the Triplet Stored in the Home Location Register (HLR). This triplet includes: Access Point Name, PDP Type, PDP Address etc.
2). If these 2 Triplets are not consistent the SGSN rejects the PDP context Activation procedure.
3). This type of inconsistency is normally caused by wrong parameter settings in the MS/UE.
4.) The requested information correction procedure is used to minimize these failures. So SGSN would have a default Mapping say If APN-NI (I explained this on Day 1 under APN composition) requested by MS/UE is Not Matched, Use default APN as Internet and allow user to access as Long as this APN being corrected to is defined in the HLR for this Subscriber.
#PerfectionIsANorm
Comments
Post a Comment