MAPR993C0与GSM620协议比较

1、1 说明2g对应的协议是0902-620,r99对应的协议是2002年6月的29002 3c0以卜内容中先列举的是29002-3c0版本的描述，后列举的是0902-62()的描述。 红色字体是29002-3c0多出的部分，蓝色字体是两个协议不一致的部分。2 协议比较i. map_update_locationtable 8.1/2: map_update_location(29002-3co)parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)msc addressmm(=)vlr numbe

2、rmm(=)lmsiuc(=)supported camel phasescc(=)solsa support indicatorcc(=)1st support indicatorcc(=)super-charger supported in serving network entitycc(=)long ftn supportedcc(=)inform previous network entitycc(=)hlr numbercc(=)user errorcc(=)provider erroro分析：2g 与 3g 都使用 networklocupcontext v3目前代码实现中只多出

3、inform previous network entity 一个信元，其余多出的信元当前代码 没实现。infoim previous network entitythis parameter is used by the vlr to ask the hlr to inform the previous network entity about the update by sending the previous n etwork entity a can cel locati on message .it is used in case super-charger is supported

4、 in the network and the serving network entity has not been able to inform the previous network entity that ms has moved, that is if it has not sent send identification to the previous serving entity.因为该信元与super charger相关，目前一般都不支持该特也因此接口消息屮不会包括该信 元，即对于该消息，两个i办议的实现没有差界。8.1.2.2 service primitives(0902

5、-620)parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)msc addressmm(=)vlr numbermm(=)lmsiuc(=)supported camel phasescc(=)hlr numbercc(=)user errorcc(=)provider error02. map_cancel_location(same)table 8.1/3: map_cancel_locationparameter namerequestindicationresponseconfirm

6、invoke idmm(=)m(=)m(=)imsimm(=)lmsicc(=)cancellation typeccuser errorcc(=)provider error0分析：2g 厶/ 3g 都使用 locationcancellationcontext v3, 样。parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)lmsicc(=)cancellation typecc(=)user errorgc(=)provider error03. map_senddentificatio

7、ntable 8.1/4: map_senddentificationparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)tmsimm(=)number of requested vectorsmsegmentation prohibited indicatorcc(=)imsicc(=)authentication setuc(=)current security contextuc(=)user error0c(=)provider error0分析：3g协议111在req消息屮多出了必选信元number

8、of requested vectors和条件信元segmentation prohibited indicator。2g 时对应的 ac 版木为 intcrvlrlnforctricvalcontcxt v2 ； 3g 时对应intcrvlrlnforctricvalcontcxt v 3number of requested vectorsa number indicating how many authentication vectors the new vlr is prepared to receive the previous vlr shall not return more v

9、ectors than indicated by this paramete匚segmentation prohibited indicator4. map_purge_ms(same)this parameter indicates if the new vlr or sgsn allows message segmentation.parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)tmsimm(=)imsicc(=)authentication setuc(=)user errorcc(=)provide

10、r error0table 8.1/6: map_purge_msparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)vlr numbercc(=)freeze tmsicc(=)freeze p-tmsiccsgsn numbercc(=)user errorcc(=)provider error0分析：2g 与 3g 均使用 mspurgingcontext v3, 一样。parameter namerequestindicationresponseconfirminvoke idimsi

11、vlr numberfreeze tmsifreeze p-tmsisgsn number user error provider errormmccm(=)m(=)c(=)c(=)m(=)cccm(=)c(=)c(=)c(=) 05. map_update_gprs_location(no relation)table 8.1/7: map_update_gprs_locationparameter namerequestin dicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)sgsn numbermm(=)sgsn addressm

12、m(=)supported camel phasescc(=)solsa support indicatorcc(=)super-charger supported in serving network entitycc(=)gprs enhancements support indicatorcc(=)inform previous network entitycc(=)hlr numbercc(=)user errorcc(=)provider error0parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=

13、)imsimm(=)sgsn numbermm(=)sgsn addressmm(=)hlr numbercc(=)user errorcc(=)provider error06. map-n0te-mm-event(3g 独有)table 8.1/8: map_note_mm_event parametersparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)event metmm(=)service keymm(=)imsimm(=)basic msisdnmm(=)location information

14、cc(=)lsa identitycc(=)supported camel phasesmm(=)user errorcc(=)provider error0分析：山于该流程的触发需要在hlr签约m-cs1,而该信元是3g才有的，因此不会対2g 有影响，即在2g情况下不会触发该消息。7. map_prepare_handovertable 8.4/1: map_prepare_handoverparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)target cell idcc(=)target rnc idcc

15、(=)ho-numbernotrequiredcc(=)imsicc(=)integrity protection informationcc(=)encryption informationcc(=)radio resource informationcc(=)an-apducc(=)cc(=)allowed gsm algorithmscc(=)allowed umts algorithmscc(=)radio resource listcc(=)rab idcc(=)handover numbercc(=)relocation number listcc(=)multicall bear

16、er informationcc(=)multiple bearer requestedcc(=)multiple bearer not supportedcc(=)selected umts algorithmscc(=)chosen radio resourceinformatio ncc(=)user errorcc(=)provider error0分析：3g 新增的信令单元imsl integrity protection information, encryption information, radio resource information, allowed gsm algo

17、rithms, allowed umts algorithms, radio resource list, rab id, multiple bearer requested； 3g 采用 an-apdu 代替了 2g 的 bss-apduc2g 对应的 ac 使用 handovercontrolcontext v2, 3g 对应的 ac 使用 handovercontrolcontextv3oparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)target cell idcc(=)ho-numbernotre

18、quiredcc(=)bss-apducc(=)cc(=)handover numbercc(=)user errorcc(=)provider error08. map_send_end_signaltable 8.4/2: map_send_end_signalparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)an-apdumm(=)provider error0分析：3g 采用 an-apdu 代替了 2g 的 bss-apduo2g 对应的 ac 使川 handovercontrolcontext v

19、2, 3g 对应的 ac 使川 handovercontrolcontextv3oparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)bss-apdumm(=)provider error09. map_process_access_signallingtable 8.4/3: map_process_access_signallingparameter namerequestindicati oninvoke idmm(=)an-apdumm(=)selected gsm algorithmcc(=)sele

20、cted umts algorithmscc(=)chosen radio resource informationcc(=)selected rab idcc(=)分析：3g采用an-apdu代替了 2g的bss-apduo红色部分是3g新增信元。2g 对应的 ac 使用 handovercontrolcontext v2, 3g 对应的 ac 使用 handovercontrolcontextv3oparameter namerequestindicationinvoke idmm(=)bss-apdumm(=)10. map_forward_access_signallingtable

21、8.4/4: map_forward_access_signallingparameter namerequestindicationinvoke idmm(=)integrity protection informationcc(=)encryption informationcc(=)key statuscc(=)an-apdumm(=)allowed gsm algorithmscc(=)allowed umts algorithmscc(=)radio resource informationcc(=)分析：3g 采用 an-apdu 代替了 2g 的 bss-apduo2g 对应的

22、ac 使用 handovercontrolcontext v2, 3g 对应的 ac 使用 handovercontrolcontextv3oparameter namerequestindicationinvoke idmm(=)bss-apdumm(=)11. map_prepare_subsequent_handovertable 8.4/5: map_prepare_subsequent_handoverparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)target cell idcc(=)targe

23、t rnc idcc(=)target msc numbermm(=)selected rab idcc(=)an-apdumm(=)cc(=)user errorcc(=)provider error0分析：3g采用an-apdu代替了 2g的bss-apduo红色部分是3g新增信元。2g 对应的 ac 使用 handovercontrolcontext v2, 3g 对应的 ac 使用 handovercontrolcontextv3oparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)target cel

24、l idmm(=)target msc numbermm(=)bss-apdumm(=)cc(=)user errorcc(=)provider error012. map_send_authenticationnfotable &5/2: map_send_authentication_info parametersparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsicc(=)number of requested vectorscc(=)re-synchronisation infocc(=

25、)segmentation prohibited indicatorcc(=)immediate response preferred indicatoruc(=)authenticationsetlistcc(=)user errorcc(=)provider error0分析：红色部分是3g新增信元。2g 对应的 ac 使用 inforetrievalcontext v2, 3g 对应的 ac 使用 inforetrievalcontext v3。table 8.5/2: map_send_authentication_parameters parametersparameter name

26、requestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)authe nticationsetlistcc(=)user errorcc(=)provider error013. map_authentication_failure_report (3g 独有)table 8.5/3: map_authentication_failure_report parametersparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)f

27、ailure causemm(=)user errorcc(=)provider error0分析:3g新增消息。14. map_check_imei (same)table 8.7/1: map checkmei parametersparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imeicc(=)cc(=)equipment statuscc(=)user errorcc(=)provider error0分析：2g 与 3g 均使用 equipmentmngtcontext v2,样。paramete

28、r namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imeicc(=)cc(=)equipment statusgc(=)user errorcc(=)provider error015. map-insert-subscriber-datatable 8.8/1: map-insert-subscriber-dataparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsicc(=)msisdncc(=)categorycc(=)subsc

29、riber statuscc(=)bearer service listcc(=)cc(=)teleservice listcc(=)cc(=)forward!ng information listcc(=)call barring information listcc(=)cug information listcc(=)ss-data listcc(=)emlpp subscription datacc(=)mc-subscription datacc(=)operator determined barring general datacc(=)cc(=)operator determin

30、ed barring hplmn datacc(=)roaming restriction due to un supportedcc(=)featureregional subscription datacc(=)vlr camel subscription infocc(=)voice broadcast datacc(=)voice group call datacc(=)network access modecc（=）gprs subscription datacc（=）roaming restricted in sgsn due tocc（=）unsupported featuren

31、orth american equal access preferred carrieruc（=）id listsgsn camel subscription infocc（=）lsa informationcc（=）1st alert timercc（=）ss-code listcc（=）lmu identifiercc（=）lcs informationcc（=）cs allocation/retention prioritycc（=）super-charger supported in hlrcc（=）regional subscription responsecc（=）supporte

32、d camel phasescc（=）user erroruc（=）provider error0分析：2g与3g均使用subscriberdatamngtcontext v3,而且不样的信元对消息处理没有 影响parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsicc(=)msisdncc(=)categorycc(=)subscriber statuscc(=)bearer service listcc(=)cc(=)teleservice listcc(=)cc(=)forwarding infor

33、mation listcc(=)call barring information listcc(=)cug information listcc(=)ss-data listcc(=)emlpp subscription datacc(=)operator determined barring general datacc(=)cc(=)operator determined barring hplmn datacc(=)roaming restriction due to unsupportedcc(=)featureregional subscription datacc(=)vlr ca

34、mel subscription infocc(=)voice broadcast datacc(=)voice group call datacc(=)network access modecc(=)gprs subscription datacc(=)roaming restricted in sgsn due tocc(=)unsupported featurenorth american equal access preferred carrieruc(=)idss-code listcc(=)regional subscription responsecc(=)supported c

35、amel phasescc(=)user erroruc(=)provider error016. map-delete-subscriber-datatable 8.8/2: map-delete-subscriber-dataparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)basic service listcc(=)ss-code listcc(=)roaming restriction due tounsupported featurecc(=)camel subscription

36、 info withdrawcc(=)specific csi withdrawcc(=)regional subscription datacc(=)vbs group indicationc0(=)vgcs group indicationcc(=)gprs subscription data withdrawcc(=)roaming restricted in sgsn due tounsupported featurecc(=)lsa information withdrawc0(=)1st information withdrawcc(=)regional subscription

37、responsecc(=)gmlc list withdrawcc(=)user errorcc(=)provider error0分析：2g与3g均使用subscriberdatamngtcontext v3,而.不一样的信元对消息处理没有 影响parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)basic service listcc(=)ss-code listcc(=)roaming restriction due toun supported featurecc(=)camel su

38、bscription info withdrawcc(=)regional subscription datacc(=)vbs group indicationcc(=)vgcs group indicationcc(=)gprs subscription data withdrawcc(=)roaming restricted in sgsn due tocc(=)un supported featureregional subscription responsecc(=)user errorcc(=)provider error017. map_reset (same)table 8.10

39、/1: map_resetparameter namerequestindicationinvoke idmm(=)hlr numbermm(=)hlr id listuc(=)分析：2g 与 3g 均使用 resetcontext v2,样。parameter namerequestindicationinvoke idmm(=)hlr numbermm(=)hlr id listuc(=)1 & map_forward_check_ss_indicationtable 8.10/2: map_forward_check_ss_indicationparameter namerequ

40、estindicationinvoke idmm(=)分析：2g 与 3g 均使用 networklocupcontext v3, 一样。parameter namerequestindicationinvoke idmm(=)19. map_restore_datatable 8.10/3: map_restore_dataparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsimm(=)lmsiuc(=)supported camel phasescc(=)solsa support indicator

41、cc(=)1st support indicatorcc(=)super-charger supported inserving network entitycc(=)long ftn supportedcc(=)hlr numbercc(=)ms not reachable flagcc(=)user errorcc(=)provider error0分析：2g与3g均使丿ij networklocupcontext v3,新增信元对该消息没冇影响parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)imsim

42、m(=)lmsiuc(=)supported camel phasescc(=)hlr numbercc(=)ms not reachable flagcc(=)user errorcc(=)provider error020. map-provide-subscriber-info (same)table 8.11/2: provide_subscriber_lnformationparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)requested infomm(=)imsimm(=)lmsiu0locat

43、ion informationcc(=)subscriber statecc(=)user errorcc(=)provider error0分析：2g 与 3g 均使用 subscriberlnfoenquirycontext v3, 样。parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)requested infomm(=)imsimm(=)lmsiu0location informationcc(=)subscriber statecc(=)user errorcc(=)provider error02

44、1. map-send-imsi (same)table 9.2/1: map-send-imsiparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)msisdnmm(=)imsicc(=)user errorcc(=)provider error0分析：2g 与 3g 均使用 imsiretrievalcontext v2, 样。parameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)msisdnmm(=)imsicc(=)use

45、r errorcc(=)provider error022. map_send_routing_informationtable 10.1/1: map_send_routingjnformation parametersparameter namerequestindicationresponseconfirminvoke idmm(=)m(=)m(=)interrogation typemm(=)gmsc addressmm(=)msisdnmm(=)cc(=)or interrogationcc(=)or capabilitycc(=)cug interlockcc(=)cc(=)cug outgoing accesscc(=)cc(=)number of forwardingcc(=)network signal infocc(=)supported camel phasescc(=)suppress t-csicc(=)suppression of announcementcc(=)call