The LAC is very important for the mobility on basis MSC not UTRAN mobility.

Any way into RNC is written the LAC, and this LAC have to be the same LAC written in MSC. You can see the LAC into MSC as a puntator towards a specific RNC.So there is a misalignment between RNC and MSC you can have some problem for some proced ures and the calls ongoing. Let'us this problems for any case. IF the LAC is wrong in the MSC a certain area will not reveice the paging messag e from MSC, so nothing Termination CALL in this area you have. You can see this from RRC's indicators. IF the LAC is wrong in the MSC you cannot have the registration for the services CS, and so PS services too. This happened because the MSC receive from an RNC a message with a LAC different from the his LAC in database. So you have many fai lures for the services CS and RRC, see (RrcConnectionRelease_UnspecifiedSccpRele aseCause) as well. You can see it with the indicators RRC failure for registrati on or for the RAB after the RRC procedure with the indicators RRC Release for re gistration or the last for SS7 messagge with cause failure UnspecifiedSccpReleas eCause Finally you can see it with a call trace. The same you have if the LAC is wrong in the RNC and not in the MSC. Mind: if the LAC is wrong the calls already up not have problems, neither for HO or other. The problems there are only for UE's registration, for the paging and for the ne ws calls when the UE has in memory the old LAC (change of LAC for workorder). Tipically many operators does the choiche to give one LAC for one RNC, but it is a choice not a universal rule. So you can reduce the interference (3G networks) generated from the PCH channel. ciao