Volte无法注网问题分析与IMS NV汇总

HW DIG项目Volte功能从3.17预测试至今已一个月了，因为个人之前没有volte调试经验，加之拉美是首个区域项目支持，无现网条件验证，所以不管从MBN制作还是NV汇总、功能DEBUG都把大家搞的焦头烂额、疲惫不堪，其中MBN的机制调整及制作就耗时近三周，这也给了我更多时间研究ims NV等配置。

高通平台ims NV相当多，据华为内部统计包含子项多达五百多项，包含功能开关控制、参数差异、拓展功能等，具体分类如下：

SMS、DAN、IMS Registration、Policy Manager、VOLTE、RCS、Presence、VT、UT、USSD、hVOLTE等，详情见附件。

Diego无法注网原因主要是NV及APN配置不对，如果要保证volte注网正常，可从以下几点检查。

1.保证NV正确，特别是

67218 Enable IMS (1 - enable, 0 - disable)、

66048 Voice Domain Preference (0 - CS, 1 - PS, 2 - CS Pref, 3 - PS Pref)等，否则不发起IMS注网。

2.保证MBN中APN正确，此APN数据保存在profile2中，用来建立IMS PDN的profile。

AT+CGDCONT?
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0",0,0,,0
AT$QCPDPIMSCFGE?
$QCPDPIMSCFGE: 2 , 1 , 0 , 0

AT+CGDCONT = 2,"IPV4V6","IMS"
AT$QCPDPIMSCFGE=2,1,0,0
预置方法:
把生成的/Data_Profiles/Profile2用efs explorer拖出来编译到Lab_Conf_Volte的MBN中

注：

参数1：2代表profile2

参数2：IP类型

参数3：apn  type

参数4：IP

IPV4-->"0.0.0.0"
IPV4V6-->"0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"

3.保证ap层APN正确，即EMUI globle/apn-conf.xml

eg.:

<apn carrier="001-01-ims"
      mcc="001"
      mnc="01"
      apn="ims"
      type="ims"
      protocol="IPV4V6"
      roaming_protocol="IPV4V6"
  />

// LTE Available:
[0051/0002] | MSG | 2017/03/02 10:16:50.029 | IMS/High | [qpDcm.c 8814] qpDplProcessDSSysEvent: Iterating DS Sys Info, pDSSysEvStruct->avail_sys[0].tech = 0 |
[0051/0002] | MSG | 2017/03/02 10:16:50.029 | IMS/High | [qpDcm.c 8815] qpDplProcessDSSysEvent: Iterating DS Sys Info, rat_value = 3, so_mask = 1000 |

// PDN Esatblihsment at Modem
[0051/0001] | MSG | 2017/03/02 10:16:50.042 | IMS/Medium | [qpDcm.c 7986] IMS_APP#>>#DPL_M#0#qpDcmEstablishPDPConnection |
[0051/0002] | MSG | 2017/03/02 10:16:50.042 | IMS/High | [qpDcm.c 8089] qpDcmEstablishPDPConnection | pDcmProfile=8a883980 dsAppID=28 |
[6052/0002] | MSG | 2017/03/02 10:16:50.042 | IMS DPL/High | [qpDcm.c 8112] qpDcmEstablishPDPConnection - APNName --> ims, Resolved APN --> |
[0051/0002] | MSG | 2017/03/02 10:16:50.042 | IMS/High | [qpDcm.c 8114] qpDcmEstablishPDPConnection - 3GPP ProfileNumber --> 2 | 3GPP2 ProfileNumber --> -1 | IPType --> 2 |

[0051/0001] | MSG | 2017/03/02 10:16:50.070 | IMS/Medium | [qpDcm.c 7986] IMS_APP#>>#DPL_M#0#qpDcmEstablishPDPConnection |
[0051/0002] | MSG | 2017/03/02 10:16:50.070 | IMS/High | [qpDcm.c 8089] qpDcmEstablishPDPConnection | pDcmProfile=8b085f00 dsAppID=29 |
[6052/0002] | MSG | 2017/03/02 10:16:50.070 | IMS DPL/High | [qpDcm.c 8112] qpDcmEstablishPDPConnection - APNName --> ims, Resolved APN --> |
[0051/0002] | MSG | 2017/03/02 10:16:50.070 | IMS/High | [qpDcm.c 8114] qpDcmEstablishPDPConnection - 3GPP ProfileNumber --> 2 | 3GPP2 ProfileNumber --> -1 | IPType --> 1 |

// MODEM PDN bringup Sucess
[0051/0002] | MSG | 2017/03/02 10:16:50.193 | IMS/High | [qpDcm.c 4290] qpDcmProcessNetEvent - [200] event occurred for AppId [29] iFaceid [0x43001d00] |

[0051/0002] | MSG | 2017/03/02 10:16:50.782 | IMS/High | [qpDcm.c 4290] qpDcmProcessNetEvent - [200] event occurred for AppId [28] iFaceid [0x42001c00] |

// PDN Esatblihsment Request to AP
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 1010] | 1086 |qpDsiNetCtrlCB : dsi event is DSI_EVT_NET_IS_CONN for dsi_net_handle [0x557f278e00] |
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 1107] | 1086 |qpDsiNetCtrlCB :Send to LB sock success pConnServDB:5bf0a148
|
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] imsdatad.c 5390] | 835 |ims-dcm-daemon calling qpDsiNetCtrlProc with pConnServDb:5bf0a148 |
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 647] | 835 |qpDsiNetCtrlThreadProc : waiting for signal on mutex |
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 676] | 835 |qpDsiNetCtrlThreadProc : calling qpdplSetupCNERoute |
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 281] | 835 |qpdplSetupCNERoute...creating observer |
[6052/0003] | MSG | 2017/03/02 10:16:50.240 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 292] | 835 |qpdplSetupCNERoute...calling CreateCneNetworkRequest, using network [4] and Slot ID [1] |
[6052/0003] | MSG | 2017/03/02 10:16:50.245 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 305] | 835 |qpdplSetupCNERoute: ptr - pConnServDb [0x555bf0a148], pNetworkReqHandl [0x557f279fd0], pDplCneNetworkObrvr [0x557f279fb0] |
[6052/0003] | MSG | 2017/03/02 10:16:50.576 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 318] | 835 |qpdplSetupCNERoute...calling bringup for apn type 0 |
[6052/0003] | MSG | 2017/03/02 10:16:50.576 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 320] | 835 |qpdplSetupCNERoute..bringup returned 0 |


[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 1010] | 1086 |qpDsiNetCtrlCB : dsi event is DSI_EVT_NET_IS_CONN for dsi_net_handle [0x557f27a7a0] |
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 1107] | 1086 |qpDsiNetCtrlCB :Send to LB sock success pConnServDB:5bf0a258
|
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] imsdatad.c 5390] | 835 |ims-dcm-daemon calling qpDsiNetCtrlProc with pConnServDb:5bf0a258 |
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 647] | 835 |qpDsiNetCtrlThreadProc : waiting for signal on mutex |
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpDplConnectionManager.cpp 676] | 835 |qpDsiNetCtrlThreadProc : calling qpdplSetupCNERoute |
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 281] | 835 |qpdplSetupCNERoute...creating observer |
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 292] | 835 |qpdplSetupCNERoute...calling CreateCneNetworkRequest, using network [4] and Slot ID [1] |
[6052/0003] | MSG | 2017/03/02 10:16:50.790 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 305] | 835 |qpdplSetupCNERoute: ptr - pConnServDb [0x555bf0a258], pNetworkReqHandl [0x557f27a1c0], pDplCneNetworkObrvr [0x557f27b0e0] |
[6052/0003] | MSG | 2017/03/02 10:16:51.120 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 318] | 835 |qpdplSetupCNERoute...calling bringup for apn type 0 |
[6052/0003] | MSG | 2017/03/02 10:16:51.120 | IMS DPL/Error | [[IMS_DataD] qpdplCnERoutingNotifier.cpp 320] | 835 |qpdplSetupCNERoute..bringup returned 0 |


如果APN未配置:
15:46:50.581 2779 2902 I QCNEJ : |CORE| CNE_REQUEST_BRING_RAT_UP received
15:46:50.581 2779 2902 I QCNEJ : |CORE| CNE_REQUEST_BRING_RAT_UP received
15:46:50.584 2779 2902 I QCNEJ : |CORE| handleRatRequest net Type: 4 slotidx: 0
15:46:50.587 2779 2902 I QCNEJ : |CORE| handleRatRequest: subId = 0
15:46:50.587 2779 2902 I QCNEJ : |CORE| Bring up network: 4
15:46:50.619 2829 3019 D HwDctController: [HwTNF 0]Found pending request in ddsRequest list = NetworkRequest [ id=8, legacyType=11, [ Transports: CELLULAR Capabilities: IMS&TRUSTED&NOT_VPN] ]
15:46:51.638 2829 2829 D GsmDCT : [0]trySetupData for type:ims due to dataAttached apnContext={mApnType=ims mState=IDLE mWaitingApns={null} mWaitingApnsPermanentFailureCountDown=0 mApnSetting={null} mReason=dataAttached mDataEnabled=true mDependencyMet=true}
15:46:51.641 2829 2829 D GsmDCT : [0]buildWaitingApns: E requestedApnType=ims
15:46:51.649 2829 2829 D GsmDCT : [0]buildWaitingApns: couldn't handle requesedApnType=ims
15:46:51.649 2829 2829 D GsmDCT : [0]buildWaitingApns: X apnList=[]
15:46:51.649 2829 2829 D GsmDCT : [0]notifyNoData: type=ims