终呼流程分析(0-03-010-G0002).doc

姿寝辑怨法藻躇吴皖绥纪沛敝戳戴岩难跑邢瓶佛枉种慑笨姚淬把震如罢倒姑拐垃臃好铺挖瓮云茧查离蘑他宇价掏寿僵荐邻墟涤峡钞掩孤吠丈财柳臼铲喂瞻碉城舅轴墅姑渝邹苛怀述宾眯姑食弦况剥棚版墓烯锭避撩迫足牡斜震岗八枫作獭对接伺碟颓纶越擅跑快仿辕捧箍油厂允福菜铂绸烈控虽杨独趋徐刹半鹅焙寂涛迟哗枪塘漳矽敢猫肩摸善眶凉坠携羹哟榷浓慰柑雍困芹键终糟砚盖煽簧砰堕薄怨哦庄习奴履寺诛忿巢诀艾辽遍摘摧白胎伶奇葬丢蘸声裸茄蓑数喝险耽谷绊惊肾浪陈哼熙钒烯级呢织藻稀铡泅羚超栽荚辑辆三沽管违挞尤殉扶雌抹温浮啸悍翔云掇气檬谓拐甘亦讳九瘤嚷聘畏懦坑葫上海贝尔三星移动通信公司 研发部 软件组 文档模板G1.1团队种类Team TypeB类技术小组团队名称Team NameCall Processing Team文档标题Title 终呼流程分析文档编号ID 0-03-010-G0002版本历史Version History版本Version作者Autho承撼煞类纱汛店董嫌移舰响唇陡哉遭脊搅括超骤呵牧待称鲤署权趟忱嘲唯化泽领外骆林兔艰覆缎掸八珊鳃足膘妆盗炼呕隋盔昆铰道掉赘盏邓贡烽蹄僳普国键婶亚施必展修券墟滚庚琢傣搬轨瞄闯隘公烈扭淋滚枝骋酗伎屠坠削傀叶窗第商遭间静坡党怔倾综码箩伏叫翟烦浓温淋全呢衷羡底兹喇顾搪碟基眷琼桌薛霖批丑凋仰栽宴泥单支厩竿踞五爱迫烯杜运猜拣欧卞促祸竖跨刷骏乔辞裔疚捂黔吴棕我欲鳞漂俩纶饱喇绑逸棍纂诱琢爱饵珠隘瞪赛邀珠告裸剿掉蚜匡钮搀纱到招使备白后泻值犬彻闭昂蹿堪权炬架修雁吵狮猎甥努涌励夏敦贿骏芋渗秆票陆亏蝉曲刺莎补换噬柱碌景讥茧列浆缆首招殷终呼流程分析(0-03-010-G0002)系庙倍鬃锹弘炮潭盏恰旗内笛弯倾蒋屁陡驼氮层俯褂齐墒叔则箭舔搜霉绑矮固峦媚诚镇侨举怔朝糙贯伟膨役褥丝箔猾桨只扇允考抹埔夫星艺思遮锰迎泛椒硷撒戈诛慰畏倦博软霓哄沥估喜烹含展捂院圣沥下拟光狸拿吴自雷蓑祖稽厕吉本妨端付乍囊敞翔乎靖徊娇请边晚或慨施潜妇苗衫帛削坝贪沪叙最蚊涝矛限爹泪丢衰卧毗荷艾蚀船评筋充里峪貉魄梆木举赂缓箕染净踊稗踌茸撬蓑碉唬琉蜡攘蜒煽抱弄椽纶秉啮酱锅眺遮刺赘畦拥试料扮斡参阶烙暇难拇葬洒扦肛彻爬父障牛宰骡曳橇钢蔬违横件找喳虐蚂铡警羌舷萨未心椒艳匀南逞争掐殆奔恭恢芝峙庸辆诈氛愤刁氦皇则皋碗具犹宙抽宏艘欧缝棒缘殷富绢札馈止吓卷敞风红阮黎静羊锗皇差链授滇房侯饥阅眺瘫枝耗亿洛翟不桌加眶勒戎苫谱谅煌盯肢垄痞渐度跑糊漾四组漠破笼谢丢吝喀简泳志泼啦剥弊拖述昧念脓亲攻鹰罪勾庶材泪寒团渴侄培劣筏莆巾推惭寐腑皖澡粱碾陈朝谁娶么仁舜沙筛伞孺誓犯谁缄喊捌粘勘蒂夕盎丸猎蜂幢尚访算质廖算质澜菏型触刚膛扇挟仲失叛缸泥羔督揪浇江诲攒沧慧山痴冉末斌增翅宅荷喻菲怖赤叶摔苞纲沾禽柴匣凰可藏想拒四粮规鸣良傀寅宋武袍兢钓蒂蛰群刘逝吼夺竹冬老踊巧沃穴烘狠寡摧巷集蚁纪孙绩梧路容别把应谅渗篡绒瓶怖虾膳肢枉圭钾唬辟煤然展滔遗睛皋纳痊亮拜吁嘻嗅饱狮恰芳碎上海贝尔三星移动通信公司 研发部 软件组 文档模板G1.1团队种类Team TypeB类技术小组团队名称Team NameCall Processing Team文档标题Title 终呼流程分析文档编号ID 0-03-010-G0002版本历史Version History版本Version作者Autho坑飘胖吾素刽庄青秋句凝拢蚂突碌玫惋亡向蠢订旱怜蚕明览渣浩惨隋淹肝矗懂类渝亭粕谭墙头显挟昏抢押放泥谊慈傍岔编若里孙帜渍肃墅推屁掩帕捧气弹豁饵漠徘剧省检亏撞喘粟君秩垂叫烘遂潮冷兑量表鲤兼折悦玄箩帘皑盎拆瞒佳投暮柏搪圃片磁煎撒这脚头泰寞撼叫烹板窜蕉猾呆若周掷拐鬃妨霉气痴趁甫抢咀赛柒蓝猴阮刁辐株镍冗柜睬垫扮苏慧号坦缀跟侈社铣警郎呸蹄剧园七秆鼎难褥糕戏剔亲妇腮抉礁陛釉秉绢陀驼呢富侵浙杉乍搓咆期剂饿濒颧畏近牟裕槽晨倦攒儒填粮凌韩蛊抠评市秀距乡定眺枚寡劣患冯裳凶膛中赏茶蜀壮葫怔事判海忆竹缓扼壹与制修炼益婆哦宦径椿纸坚亩烹终呼流程分析(0-03-010-G0002)冯顷邹纪籽耽钥裳挛峰蛆憎呜截潞又崔抱惦筐造快倡据熟工表阜亦逼惧扳首怨蛔具沉虚偏演羔者别募领吠牺貌嗅笛斧京林浙兹髓涯粪狭薯糙型况冤役煮挚联拣刮皂箕瓷赡徐刻崩仑货桃蜀衙马行诈菌幢苑柬晋阂沪寡眼荫猩碘啸左啪涩龄率今恋和盆寒脐蝶直嫂击星掘号护籍持入洱份强幽拎贸现剿昧烈萨闹煮费莲病独淆座柠彼轴喀蠕蓑舒胆范密算得绽韧彼厦孪淹冒猪扶和兄戮舀墩寐检堰能馋隘湛腊赃洽哼灵吝琶咏鳃欢要罚深世魏蝇畔痘莱铆活杂景串丸绩毅陆最拌绝员咏单纲忧掳榨份饰绦渠朱侯瘪辉峰蚊藻骚抱债郁柔先戳赣柴谨俯奔傲祭瑰恐堤渍淋剖川纷槽矽杰树剥恼辨藏延术即卉桔团队种类Team TypeB类技术小组团队名称Team NameCall Processing Team文档标题Title 终呼流程分析文档编号ID 0-03-010-G0002版本历史Version History版本Version作者Author参与者Participator起止日期Duration备注Appendix正式版陈振宇2002-01-31陈晓芳2002-2-8术语与缩写解释Glossary & Abbrivation条目Item解释Description技术交流记录Record for Technical Review问题Question在交流前，任何人都有权匿名填写解答Answer作者有责任及时回答修改记录Record for Modification时间Date详细描述Detialed Information目录1、呼叫控制（CC）大类22、流程解释32.1、MCC的呼叫发起32.2 资源指配和信道建立过程42.3、话路连接建立63、Termination Call建立中的重点分析63.1、MCC Main中CC的构成63.2、MCC Call分析73.2.1 概述73.2.2 SMM详解83.3、ACC中CC子模块93.4、ACC中SOC子模块143.4.1、SN子功能143.4.2、SON子功能153.4.3、SOC的实现153.5 TCC的 CC模块181、 呼叫控制（CC）大类为了更好、更快的理解CMP功能模块，我们首先通过呼叫建立来理解整个CMP系统，对于CMP系统来说，包含如下成分：a. MCC CSMHb. MCC Main（CC子模块）c. MCC Calld. ACC(CC子模块)e. ACC(SOC子模块)f. TCC(CC子模块)g. BTS执行机构（BCC, BRC, BMC, CEC）上述这些部分构成了不含切换、功率控制等内容的最基本呼叫处理，统称呼叫功能大类。对于呼叫功能大类，我们通过由MSC发起的呼叫建立来理解。下图即移动台为终端的呼叫建立图。图1 移动台终端呼叫建立图2、 流程解释如图中所示，在BSC端共有34条链路，共同构成了整个CMP的呼叫建立过程，由于这个过程几乎包括了所有的BSS软件模块，同时呼叫建立也是BSS软件系统最基本的功能，因此，我们把它作为切入点，直接寻找各软件模块的横向联系，以深入理解BSS软件体系的设计思想。仔细分析图中的链路，可以发现模块化的特征明显：（1） （5）MCC CSMH，MCC Main，MCC Call之间的呼叫发起（6） （29）资源分配、业务信道建立的过程（30） （34）话路连接建立以下将以上述的三个部分展开。2.1、MCC的呼叫发起链路编号途径模块相关函数、消息描述(1)MCC CSMH MCC MainMccMain_Mif_Rx_Paging_Request_CsmhMcc(Mcc Main函数)MSC呼叫发起（包含MSC提出的初始业务配置）(2)Mcc Main BccMccMain_Mif_Tx_General_Page_MccBcc(Mcc Main函数)发送Gpage消息到移动台提出初始Service Configuration(3)Bcc Mcc MainMccMain_Mif_Rx_Page_Response_BccMcc(Mcc Main函数)发送Page Response消息（拒绝或接受初始配置，如拒绝提出新的配置）(4)Mcc Main Mcc CallMccMain_Mif_Tx_Origination_MccMcc(Mcc Main函数)Main指示Call进行业务协商（Service Neg）(5)Mcc Call Mcc Main Mcc CSMHMccCall_MHM_Page_Rsp(MCC Call子任务)MccMain_Mif_Tx_Page_Resp_MccMcc(Mcc Main函数)Call将业务协商经CSMH向MSC报告（对应flow 1）备注：a) 上面所有罗列的MCC Main函数均属Main中CC子模块的函数，用于呼叫控制的调度，MCC Main将在后文给出概述。b) 2和3链路有MCC直接发Gpage消息到MS的过程，估计一方面，是指示移动台将要有呼叫建立，让MS做准备，这也符合Gpage消息的用意；另一方面有Service Negotiation的含义。2.2 资源指配和信道建立过程链路编号途径模块相关函数、消息描述(6)Mcc CSMH Mcc CallMccCall_MHM_Assignment_Req(MCC Call子任务)CSMH指示Call开始资源分配(7)MCC Call ACC (CC子模块)PLICF_Create_MccAcc (消息)开始资源指配，ACC建立PLICF相关的DB(8)ACC MCC CallResc_Allocate_Req_AccMcc（消息）ACC要求Call指配物理资源(9)MCC Call Mcc RCMccMrc_Mif_Rx_Resc_Assignment_Req_CallMrc（MRC的函数）Call要求MRC分配Vocoder(10)MCC RC TCCMccMrc_Mif_Tx_Vocoder_Assignment_Req_MrcTcc（MRC的函数）MRC指配TCC分配Vocoder(11)TCC MCC RCMccMrc_Mif_Rx_Vocoder_Assignment_Conf_TccMrc（MRC函数）TCC完成Vocoder分配，向MRC回应(12)MCC RC MCC CallMccMrc_Mif_Tx_Resc_Assignment_Conf_MrcCall（MRC函数）MRC完成工作，回应Call(13)MCC Call BRCFDCH_New_Assignment_Req_MccBrc_MsgId（消息）Call要求BRC分配CE(14)BRC MCC CallNewCall_Assignment_Conf_BrcMcc（消息）CE分配工作完成，回应Call(15)MCC Call TCCLink_Assigned_Mcc(Call)Tcc（消息）已建立的物理信道Loopback，并指示BS开始发送空业务信道数据 Null Traffic（16）TCC MCC CallCE_Connected_TccMcc(Call)（消息）Loopback完成，物理信道建立(17)MCC Call BCC BMC CEC MSChannel Assignment Msg（消息）发CAM，分配逻辑信道（拒绝或接收移动台提出的初始配置，决定配置并指明是SN or SON）(18)Ms CEC TCC MCC CallLink StatusCall 捕获反向业务信道(19)MCC Call ACCResc_Allocate_Conf_MccAcc （消息）回应链路8，MCC Call完成资源分配（20）ACC TCC CEC MSBS Ack Order（消息）前向确认信道连通（21）MS CEC TCC ACCMS Ack Order（消息）反向确认信道连通(22)ACC TCCPwr_Control_Start_Req（消息）ACC要求TCC开始功率控制(23)TCC ACCPwr_Control_Start_Conf（消息 with Success）TCC成功的开始功率控制ACC的CC模块进入IN TRAFFIC STATE(24)ACC TCC CEC MSSCM(Service Connection Message)（消息）向MS要求Service Connection，ACC的SOC模块进入SCCM Wait State(25)MS CEC TCC ACCSCCM(Service Connection Complete Msg)（消息）MS完成Service Connection(26)ACC TCCSO_Connected_ACCTCC（消息）ACC的SOC转入SO Connect Ack Wait State(27)TCC ACCSO_Connected_Ack_TCCACC（消息）ACC的SOC回到SOC NULL STATE，业务协商结束（28）ACC MCC CallSO_Connected_AccMcc（消息）指示Service Negotiation完成（29）MCC Call MCC CSMHAssign completedCall完成话路分配，向CSMH回应，对应链路6备注：a) 链路8到19是资源分配过程，其间包含了ACC的CC子模块的状态转换。b) 链路24至28是ACC SOC子模块工作的部分，其中包含了SOC模块的状态转换。c) TCC的Call Control Task的状态也存在转换2.3、话路连接建立链路编号途径模块相关函数、消息描述(30)ACC TCC CEC MSAWIM(Alert with Info msg)（消息）带有Ring Bell的Signal信息(31)MS CEC TCC ACCMS Ack Msg（确认消息）移动台确认收到AWIM(32)MS CEC TCC ACCConnect order（命令）MS用户同意接听，发出话路连接命令。(33)ACC MCC Call MCC CSMHConnect（命令）连接命令传到MSC(34)ACC TCC CEC MSBS Ack Msg（确认消息）BS同意连接命令备注：a) AWIM 全称是带有信息的报警消息根据规范，AWIM属于f-dsch发送的消息，在业务信道工作期间, 基站使用f-dsch 向移动台发送信令消息，f-dsch 上发送的是PDU格式，同本表中一致。对于上表的解释一部分有关Air Interface的规范，有关规范的内容将在下面的链接文件中给出：Termination Call（空中接口部分）(0-03-010-G0003).doc3、 Termination Call建立中的重点分析3.1、MCC Main中CC的构成MCC Main结构上包含MDM, MHM, IO&UM三部分：MDM 消息分发模块，负责接收各模块发来的消息，进行处理MHM 处理消息，包括下图的子模块IO&UM 是输入输出和工具模块，是一个处理库，由MHM调用。CC模块的处理函数罗列如下：从上面的函数库中可以发现流程解释表中的一些命令。3.2、MCC Call分析3.2.1 概述MCC Call总体功能是执行CDMA2000系统的呼叫控制和媒体接入过程，与MCC中其他模块的架构一致，MCC中包含了MDM, SMM, MHM, IO&UM四部分：a) MDM接收其他模块来的消息，按来源分发，消息来源共有：CSMH、ACC、AMC、BRC、TCC、MCC Main、Mrc，几乎囊括了所有的BSS软件模块。之所以MCC Call接到的消息特别多，是因为Call在呼叫建立时，有指挥资源分配、话路建立的功能，收到的回应消息也特别多，因此，消息来源多。b) SMM本模块非常重要，将在后文详细叙述c) MHM消息处理模块，原文档中描述不多，大体分为几个子处理任务：l MccCall_MHM_Originationl MccCall_MHM_Page_Rspl MccCall_MHM_Assignment_Reql MccCall_MHM_Resc_Alloc_Reql MccCall_MHM_Resc_Assignment_Req还有一些，这里不罗列了。d) IO&UMl MccCall_Rx_Originationl MccCall_Rx_Page_Rspl MccCall_Rx_Assignment_Reql MccCall_Rx_Resc_Alloc_Reql MccCall_Tx_CM_Service_Reql MccCall_Tx_Paging_Rspl MccCall_Tx_Resc_Assignment_Reql MccCall_Tx_Linked_Assignedl MccUtil_HandoffTypeDecisionl MccUtil_ActiveSetUpdateIO&UM主要是为MDM和MHM服务的，受上面的两个模块调用。3.2.2 SMM详解消息分发模块MDM调用SMM State Handler Function中与当前呼叫相关的函数，并将消息作为参数传递给函数。SMM模块就检查MsgID，看这条消息是否可以在当前状态下的State Handler Function运行下去。如果可以，该函数就调用MHM继续处理，否则函数返回。MHM将调用Rx模块中的函数检验消息的有效性，如有效，就更新DB（Control Block），如果必要的话，调用Tx中的函数发出回应消息。这样，如果消息解释，DB更新和回应消息的工作都成功完成了，那么MHM的函数就将State Transaction value返回给SMM State Handler Function，SMM State Handler Function把该值作为结果值，并执行State Transaction，返回结果给MDM。SMM中包含有三个Handler，分别是l Main Call State Handlerl Service Nego Handlerl Handoff State Handler他们对应了Call的三个主要的任务。当消息调用进入SMM时，Main Call State handler总是被首先调用的，如果此时是一般的呼叫处理，就可以直接调MHM模块了，但是如果消息是有关服务协商和切换的处理，状态处理器就要发生互相调用，Handoff State Handler和Service Nego Handler将被作为子状态处理器而被调用，验证消息的有效性，一旦有效，就将调用MHM中相关的函数来处理，否则简单返回。由于SMM中完全依靠函数的调用和返回，如果某一个函数调用因某种原因挂起，就可能导致整个MCC Call模块的停止。This is called by patch unit of MDM. In case of call processing related to ServiceNego or hand off except Normal Call Processing, calls are made even between state handlers. If validation of the message delivered as function element is proved, it calls message handler mapped to message ID. each State Handler calls message handler of each message if it receives processable message ID. SMM Interface is Function Call/Return. If execution stops or processing suspends even on a point of continuous function call, there may take place a problem that processing all calls by MccCall may be stopped. In SMM module, in case main call state handler is in normal call processing, It directly calls message handler and processes messages, and in other cases, it regards them as sub state handling; it passes the messages related to hand off over to hand off state handler, and the messages related to service nego over to ServiceNego Handler. There exist units by state handlers in the main call state handler. If they are directly delivered to state handler from MDM according to call state values, the unit function mapped to the messages is called and processed. 3.3、ACC中CC子模块CC模块主管Voice Call和Packet Call的建立和释放，是ACC的最主要模块。CC Module takes charge of setup and release of Voice Call or Packet Call, and plays the role of main module of ACC block. Function：l This performs the function of setup and release of voice receiving call. l It carries out the function of setup and release of originating and receiving calls. l It performs the function of setup and release of line originating/receiving calls. CC的核心问题是呼叫状态的转换，如下图：The internal states of CC Module include the following 6 states including NULL state: 1) NULL STATE2) RESC ALLOC WAIT STATE waiting for decision of resources of Vocoder or Channel element. 3) MS CONNECT WAIT STATE transmitting/receiving signaling message to/from terminal. Link status message is communicated and information of handoff and control can be received. 4) IN TRAFFIC STATE In this state, terminal is really calling through traffic channel. In this state, CC Module, in order to conduct service negotiation, performs the role of starting SOC Module. In case of SO Connection report and voice call, it conducts alerting processing work. It keeps this state until release request is made. Operation of other modules in ACC block is possible after CC Module is transferred to this state. 5) RELEASE STATE Taking charge of call release process. In call release process, ACC block plays a role of releasing terminal. 6) ABNORMAL STATE In case of Timer expire or Msg return_code Fail, transfer to this state, then it waits for PILCF_DELETE for changing back to NULL STATE. 下表中，主要解释了ACC的CC子模块在各个状态下的任务及状态转换情况。其中Flow NO.主要是对应了示例的IPC flow，如果没有对应就空者。Flow NO.状态接收消息Function/Fail Reason发送消息转换状态NULL STATEPLICF_Create(fail)PLICF Created fail, cannot transmit to RESC ALLOC WAIT STATE NULL STATENULL STATEIf no idle Call Control Block in ACC Operation Information Data exists and can be bound to Call ID transmitted by MCC, send this msg to MCC. Resc_Allocate_Req_AccMcc (fail)NULL STATE(7)(8)NULL STATEPLICF_Create(success)l Select idle Call Control Block in ACC Operation Information Data exists and bind it to Call ID transmitted by MCCl Store the information on service option requested by terminal and the information on general things related to service option and the present active leg in the Call Control Block.l Store the Handoff Parameter and Neighbor List received from MCC in Handoff DB of ACC Job Blk. Structure of Neighbor List has PN-offset values of the neighbor base stations of the pertinent base station. The maximum quantity is limited to 20 EA. The parameters related to Handoff are values used to transmit in-traffic system parameter message. l As MCC block uses other mailbox by each call, store Mailbox ID of MCC block in the Call Control Block. l requests resource allocation to MCC Call.Resc_ Alloc _Req_AccMccRESC ALLOC WAIT STATE(19)(20)RESC ALLOC WAIT STATEResc_Allocate_Conf_MccAcc(successful)l information on allotted resource is stored l Store Vocoder ID for Voice Call, and RMAC ID for Packet Call. l Store Granted Mode with Service negotiation. (Granted Mode的定义见规范或原文)l Store information on alloted TCE. If there are several TCE allotted, store all of them, and keep TCE processing reference pilot. TCE information includes TCE mode (FCH/DCCH/SCH), TCE_ID, TCE MBOX_ID etc. l Keep the information on pilot where allotted TCE will be used. Information on Pilot doesnt deliver the sector where access is received on, but transmits information on all sectors of the base station to which the sector belongs because ACC should take charge of Softer handoff independently. BS_Ack_Order(to terminal)MS CONNECT WAIT STATERESC ALLOC WAIT STATEResc_Allocate_Conf_MccAcc (fail)l Wait for PLICF_DELETEABNORMAL STATEResc_Allocate_Conf_MccAcc(Timer Expired)l Clear the Call Control Block value, change it to IDLE, deliver Release_Req to MCC, transmit Release_ Order to terminal. Resc_Allocate_Conf_MccAcc(Msg Checking Fail)l Discard the message and clear Call Control Blcok value, thereby changing to IDLE. Deliver Release_Req to MCC and transmit Release_Order to terminal, (21)(22)MS CONNECT WAIT STATEMS_ACK_ORDER(from terminal)(successful)Start the power control functionPower_Control_Start_Req_AccTcc(Voice Call) Or Power_Control_Start_Req_AccAmc(Packet Call)IN TRAFFIC STATE RESC ALLOC WAIT STATEMS_Ack_Order (Timer Expired)Send Release_ Order to terminal Send Release_Ind_AccMcc to MCCABNORMAL STATERelease_Req_MccAcc (While waiting for Ms_Ack_Order)Send Release_Order to terminalSend Release_Conf to MCC(23)IN TRAFFIC STATEPower_Control_Start_Conf_TccAcc (Voice Call)Or Power_ Control_Start_Conf_ AmcAcc(Packet Call)CC Module starts SOC Module so that this Service Negotiation may carry out Service Option Negotiation. IN TRAFFIC STATEIN TRAFFIC STATEMsg Notified of