ÎÊÌâÒÑ¿ªÆô
(ÆÕͨÎÊÌâ)
LA/RA Update Procedure
ÏëÎÊÏÂLA/RA Update ProcedureÍê³Éʲô×÷Ó㬴ËʱPDP¼¤»îÊÇÒ»Ö±±£´æ×ÅÂð£¬Æäºó¾Í¿ÉÒÔ½øÐÐÊý¾ÝÒµÎñÊÇ°É
ÌáÎÊÕß: dallas ÌáÎÊʱ¼ä: 2013-05-15
• CSFB¹Ò¶ÏÖ®ºóÎÞ·¨·µ»ØLTE£¬³öÏÖLTERRCSetupFail¼°LTETAUpDATeFailÊÇʲôÔÒò/ÈçºÎ½â¾ö 2018-11-01
• CSFBûÓÐTrackingareaupDATerequestÏÔʾCSFBʧ°Ü£¬¿ÉÒÔ½â¾öÂð£¬ÓÐʲôӰÏì 2018-05-08
• Tracking area upDATe reject--TAU¸üÐÂʧ°Ü£¬ ¶ÔÓ¦ÔÒòÊÇ£ºUE ident 2017-07-27
• 180ÕñÁåÖ®ºó±»½Ð·¢ËÍ486ÐÅÏ¢Òâ˼ÊDZ»½ÐÖ÷¶¯¹Ò»úÁËÂ𣿿´ÐÅÁîÉÏÖ÷½ÐÔÚÕñÁåÖ®Óз¢ÉúÁËÒ»´ÎUPDATEÊÇʲôÒâ˼°¡ÇóÖ¸µ¼¡£Í¾ÖлȦµÄÐÅÁî¡£ 2017-06-22
• VOLTEͨ»°£¬Ê²Ã´Çé¿öÏ»ط¢ÉúIMS_SIP_UPDATE 2016-09-02
• RRC_ConnEstabFail_RepeATEDATtemptRACH 2016-06-16
• RRCʧ°ÜÔÒòΪRRC_ConnEstabFail_RepeATEDATtemptRACH 2016-06-07
• imssipupDATe200ɶÒâ˼ÊÇ´íÎóÐÅÁîô 2016-04-26
• CSFBûÓÐTrackingareaupDATerequestÏÔʾCSFBʧ°Ü£¬¿ÉÒÔ½â¾öÂð£¬ÓÐʲôӰÏì 2018-05-08
• Tracking area upDATe reject--TAU¸üÐÂʧ°Ü£¬ ¶ÔÓ¦ÔÒòÊÇ£ºUE ident 2017-07-27
• 180ÕñÁåÖ®ºó±»½Ð·¢ËÍ486ÐÅÏ¢Òâ˼ÊDZ»½ÐÖ÷¶¯¹Ò»úÁËÂ𣿿´ÐÅÁîÉÏÖ÷½ÐÔÚÕñÁåÖ®Óз¢ÉúÁËÒ»´ÎUPDATEÊÇʲôÒâ˼°¡ÇóÖ¸µ¼¡£Í¾ÖлȦµÄÐÅÁî¡£ 2017-06-22
• VOLTEͨ»°£¬Ê²Ã´Çé¿öÏ»ط¢ÉúIMS_SIP_UPDATE 2016-09-02
• RRC_ConnEstabFail_RepeATEDATtemptRACH 2016-06-16
• RRCʧ°ÜÔÒòΪRRC_ConnEstabFail_RepeATEDATtemptRACH 2016-06-07
• imssipupDATe200ɶÒâ˼ÊÇ´íÎóÐÅÁîô 2016-04-26
ÎÊÌâ´ð°¸
( 3 )
¸ù¾Ý3GPP 24008The location updating procedure is a general procedure which is used for the following purposes:
- normal location updating (described in this subclause);
- periodic updating (see subclause 4.4.2);
- IMSI attach (see subclause 4.4.3).
- normal location updating (described in this subclause);
- periodic updating (see subclause 4.4.2);
- IMSI attach (see subclause 4.4.3).
»Ø´ðÕߣº
wwwmscbsccom
»Ø´ðʱ¼ä£º2013-05-15 13:53
34 33
Ò»¸öϵͳ¼ä¸Ä±äÊÇÔÚÒÔϳ¡¾°ÖвúÉú£¬MS·¢ÉúÁËIuģʽµ½A/Gbģʽ²Ù×÷µÄ¸Ä±ä£¬²¢ÇÒÊÇÓÉÒ»¸öRAUÁ÷³Ì»òPS handoverÁ÷³ÌËù´¥·¢µÄ¡£Ò»¸öϵͳ¼ä¸Ä±äµÄÇ°ÌáÌõ¼þÊÇMSÒѾGPRS¸½×ÅÁË¡£Òƶ¯ÐÔ¹ÜÀíµÄ״̬ת±äÓÉÏàÓ¦µÄÒƶ¯ÐÔ¹ÜÀíÁ÷³ÌÀ´Ö¸Ã÷¡£
ÔÚϵͳ¼ä¸Ä±äµÄÁ÷³ÌÖУ¬²»»á·¢Éú»á»°¹ÜÀí״̬µÄת±ä¡£
6.13.1 Intra SGSN Intersystem Change
An SGSN that supports both the Gb and Iu PS interfaces may support an intra-SGSN intersystem change if the radio access technology nodes serving the MS before and after the intersystem change are both served by this SGSN.
Ò»¸öͬʱ֧³ÖGbºÍIu PS½Ó¿ÚµÄSGSN¿ÉÒÔÖ§³ÖÒ»¸öintra-SGSNµÄϵͳ¼ä¸Ä±ä---µ±Ö®Ç°ºÍÖ®ºóΪMSÌṩ·þÎñµÄÎÞÏß½ÓÈë¼¼Êõ½ÚµãÓÉͬһ¸öSGSN·þÎñµÄʱºò¡£
6.13.1.1 Iu mode to A/Gb mode Intra SGSN Change
6.13.1.1.1 Iu mode to A/Gb mode Intra SGSN Change using Gn/Gp
The intersystem change from Iu mode to A/Gb mode takes place when an MS changes from UTRAN or GERAN Iu mode to A/Gb mode. Depending on the PMM state before the intersystem change and whether the RA is changed or not, one of the following procedures is initiated by the MS:
- When an MS in PMM IDLE state changes to the A/Gb mode without changing the RA, the MS shall follow the selective RA update procedures, see clause "Selective RA Update".
- When an MS in PMM IDLE state changes to the A/Gb mode and the RA changes, the MS shall initiate the GPRS RA update procedure, see clause "Intra SGSN Routeing Area Update".
- When an MS in PMM CONNECTED state changes to the A/Gb mode, the MS shall initiate the GPRS RA update procedure independent of whether the RA has changed or not. The RA update procedure is either combined RA / LA update or only RA update.
´ÓIuģʽµ½A/GbģʽµÄϵͳ¼ä¸Ä±ä£¬ÊÇÔÚMS·¢ÉúÁË´ÓUTRAN»òGERAN Iuģʽµ½A/GbģʽµÄ¸Ä±äʱ²úÉúµÄ¡£¸ù¾ÝÔÚϵͳ¼ä¸Ä±ä·¢Éú֮ǰµÄPMM״̬ÒÔ¼°RAÊÇ·ñ¸Ä±ä£¬ÒÔÏÂÁ÷³ÌÖ®Ò»½«ÓÉMS·¢Æð£º
- µ±MSÔÚPMM-IDLE״̬±ä¸üµ½A/Gbģʽ²¢ÇÒû¸Ä±äRA,MSÓ¦Ö´ÐÐÑ¡ÔñÐÔµÄRAUÁ÷³Ì£¬²Î¿¼Õ½ڡ°Ñ¡ÔñÐÔRA¸üС±¡£
- µ±MSÔÚPMM-IDLE״̬±ä¸üµ½A/Gbģʽ²¢ÇÒRA¸Ä±äÁË£¬MSÓ¦·¢ÆðGPRS RAUÁ÷³Ì£¬²Î¿¼Õ½ڡ°Intra SGSN RAU".
- µ±MSÔÚPMM-CONNECTED״̬±ä¸üµ½A/Gbģʽ,²»¹ÜÓÐûÓз¢ÉúRA±ä»¯,MS¶¼Ó¦·¢ÆðÒ»¸öGPRS RAUÁ÷³Ì.Õâ¸öRAUÁ÷³Ì»òÕßÊÇÒ»¸öÁªºÏµÄRA/LAU,»òÕßÖ»ÊÇÒ»¸öRAU.
A combined RA / LA update takes place in network operation mode I when the MS enters a new RA or when a GPRS-attached MS performs IMSI attach. The MS sends a Routeing Area Update Request message indicating that an LA update may also need to be performed, in which case the SGSN forwards the LA update to the VLR. This concerns only idle mode (see TS 23.122 [7b]), as no combined RA / LA updates are performed during a CS connection. In the context of this specification, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an MS in Iu mode.
Ò» ¸öÁªºÏµÄRA/LAU·¢ÉúÔÚÍøÂç²Ù×÷ģʽI---²¢ÇÒµ±MS½øÈëÁËÒ»¸öеÄRA»òµ±Ò»¸öGPRS¸½×ŵÄMSÖ´ÐÐÁËIMSI¸½×Å.MS·¢ËÍRAU RequestÏûϢָʾÕâÊÇÒ»¸öLAU¿ÉÄÜÒ²ÐèÒªÖ´ÐÐ,SGSNת·¢LAU¸øVLR.Õâ½öºÍidleģʽÓйØ(²Î¿¼TS23.122),ÒòΪÔÚÒ»¸öCSÁ¬ ½ÓÆÚ¼äûÓÐÁªºÏµÄRA/LAU±»Ö´ÐÐ.±¾¹æ·¶ÖÐÉÏÏÂÎĵÄÃèÊöÖÐ,RNS»òRNCµÄÊõÓïÒ²¿ÉÒÔÏàÓ¦²Î¿¼GERAN BSS»òBSC---µ±ÎªÒ»¸öIuģʽµÄMS·þÎñʱ.
Figure 52: Iu mode to A/Gb mode Intra SGSN Change
NOTE: All steps in figure 52 are common for architecture variants using Gn/Gp based interaction with a GGSN and using S4 based interactions with an S GW and P GW. For S4 based interaction with an S GW and P GW, procedure step (A) is defined in clause 6.13.1.1.2.
×¢ÊÍ£ºÔÚͼÀý52ÖеÄËùÓв½Öè¶ÔÓÚʹÓÃGn/Gp½Ó¿ÚºÍGGSN½»»¥£¬»¹ÊÇʹÓÃS4½Ó¿ÚºÍSGW/PGW½»»¥µÄ¼Ü¹¹µÄ¶¼Êǹ«¹²µÄ¡£»ùÓÚS4½Ó¿ÚºÍSGW/PGWµÄ½»»¥µÄ²½ÖèA£¬²Î¿¼Õ½Ú6.13.1.1.2¡£
1) The MS or RAN decides to perform an intersystem change which makes the MS switch to a new cell where A/Gb mode has to be used, and stops transmission to the network.
2) The MS sends a Routeing Area Update Request (old RAI, old P TMSI Signature, Update Type, Voice domain preference and UE's usage setting) message to the 2G+3G SGSN. Update Type shall indicate RA update or combined RA / LA-update or, if the MS wants to perform an IMSI attach, combined RA / LA update with IMSI attached requested. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the 2G+3G SGSN. The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 5.3.15.
If there is an ongoing emergency bearer service and a Routing Area Update Request is received the Routing Area Update shall be rejected with a cause code indicating that access to GERAN is not allowed.
1£©MS»òRAN¾ö¶¨Ö´ÐÐÒ»¸öϵͳ¼ä¸Ä±ä£¬Ê¹µÃMSÄÜÇл»µ½Ò»¸öеÄA/GbģʽϵÄСÇø£¬²¢ÇÒÍ£Ö¹´«µÝÊý¾Ýµ½ÍøÂç¡£
2£©MS ·¢ËÍRAUÇëÇó£¨old RAI¡¢old P-TMSIÇ©Ãû¡¢¸üÐÂÀàÐÍ¡¢ÓïÒôÓòÓÅÏȼ¶ºÍUEµÄʹÓÃÉèÖã©ÏûÏ¢¸ø2G+3G SGSN¡£¸üÐÂÀàÐÍÓ¦Ö¸Ã÷Õâ¸öÒ»¸öRAU»òÊÇÒ»¸öÁªºÏµÄRA/LAY»òÕߣ¬Èç¹ûMSÏëÖ´ÐÐÒ»¸öIMSIµÄ¸½×Å¡¢´øÓÐIMSI¸½×ÅÇëÇóµÄÁªºÏµÄRA /LAU¡£BSSÓ¦¼ÓÈëCGI£¨Ð¡ÇøÈ«Çò±êʶ£©²¢°üÀ¨Ð¡ÇøµÄRACºÍLACµ½Õâ¸ö½ÓÊÕµÄÏûÏ¢ÖУ¬È»ºóÔÙ´«µÝ¸ø2G+3G SGSN¡£UE¸ù¾ÝËü×Ô¼ºµÄÅäÖ㬰´ÕÕÕ½Ú5.3.15µÄÃèÊö£¬À´ÉèÖÃÓïÒôÓòÓÅÏȼ¶ºÍËüµÄʹÓÃÉèÖá£
3) If the MS is PMM CONNECTED state, the 2G+3G SGSN sends an SRNS Context Request (IMSI) message to the SRNS.
4) Upon reception of the SRNS Context Request message, the SRNS starts buffering and stops sending downlink PDUs to the MS. The SRNS responds with an SRNS Context Response (GTP SNDs, GTP SNUs, PDCP-SNDs, PDCP SNUs) message. The GTP sequence numbers are included for each PDP context indicating the next in-sequence downlink GTP-PDU to be sent to the MS and the next in-sequence GTP PDU to be tunnelled to the GGSN. For each active PDP context, which uses lossless PDCP, the SRNS also includes the uplink PDCP sequence number (PDCP SNU) and the downlink PDCP sequence number (PDCP-SND). PDCP SNU is the PDCP sequence number for the next expected in-sequence uplink packet to be received from the MS. PDCP-SND is the PDCP sequence number for the first downlink packet for which successful transmission has not been confirmed. The 2G+3G SGSN shall strip off the eight most significant bits of the passed PDCP sequence numbers, thus converting them to SNDCP N PDU numbers of the respective 2G GPRS PDP contexts.
3£©Èç¹ûMSÊÇÔÚPMM-CONNECTED״̬£¬2G+3G SGSN·¢ËÍSRNS Context Request(IMSI)ÏûÏ¢¸øSRNS¡£
4) Ò»µ©½ÓÊÕµ½SRNS Context RequestÏûÏ¢,SRNS¿ªÊ¼»º´æ²¢ÇÒÍ£Ö¹·¢ËÍÏÂÐÐPDU¸øMS¡£SRNSÏìÓ¦Ò»¸öSRNS Context Response(GTP SNDs¡¢GTP SNUs¡¢PDCP-SNDs¡¢PDCP SNUs£©ÏûÏ¢¡£Ã¿¸öPDPÉÏÏÂÎĶ¼°üº¬ÁËGTPÐòÁкÅÀ´Ö¸Ê¾ÐòÁÐÖн«Òª·¢Ë͸øMSµÄÏÂÒ»¸öÏÂÐÐGTP-PDU£¬ÒÔ¼°ÐòÁÐÖÐÏÂÒ»¸ö½«Òª·¢Ë͸øGGSN±»·â ×°½øËíµÀµÄGTP PDU¡£¶Ôÿһ¸öactiveµÄPDPÉÏÏÂÎÄ£¬ÈçʹÓÃÁËÎÞËðPDCP£¬SRNSÒ²Ó¦°üº¬ÉÏÐеÄPDCPÐòÁкÅ(PDCP SNU¼´Sequence Number Uplink)ÒÔ¼°ÏÂÐÐPDCPÐòÁкÅ(PDCP-SND¼´Sequence Number Downlink)¡£PDCP SNUÊÇÒ»¸öPDCPÐòÁкţ¬±íʾµÄÊÇÏÂÒ»¸öÆÚÍûµÄ´ÓMS½ÓÊÕµÄÓÐÐòµÄÉÏÐÐÊý¾Ý±¨ÎÄ¡£PDCP-SNDÊÇÒ»¸öPDCPÐòÁкţ¬±íʾµÄÊǵÚÒ»¸ö³É¹¦´«µÝµ«»¹ ûÓб»È·ÈϵÄÏÂÐÐÊý¾Ý°ü¡£2G+3G SGSNÓ¦ÌáÈ¡ÒѾ´«µÝµÄPDCPÐòÁкŵİËλ×î¸ßÓÐЧ룬½«Ö®×ª»»ÎªÔÚ2G GPRS PDPÉÏÏÂÎÄÖÐÏàÓ¦µÄSNDCP N PDUµÄÖµ¡£
5) Security functions may be executed.
5£©°²È«¹¦ÄÜ¿ÉÒÔ±»Ö´ÐС£
6) If the MS is PMM CONNECTED, the 2G+3G SGSN sends an SRNS Data Forward Command (RAB ID, Transport Layer Address, Iu Transport Association) message to the SRNS. This informs the SRNS that the 2G+3G SGSN is ready to receive data packets. Upon reception of SRNS Data Forward Command message from the 2G+3G SGSN the SRNS shall start the data-forwarding timer.
6a)If Direct Tunnel was established in Iu mode the SGSN sends Update PDP Context Request to the GGSN(s) concerned to establish the GTP tunnel between SGSN and GGSN. The GGSN(s) update the address for User Plane and downlink TEID for data and return an Update PDP Context Response. Otherwise, if there were changes of for example the RAT type that e.g. can be used for charging, the SGSN sends Update PDP Context Request (SGSN Address and TEID, QoS Negotiated, RAT type) message to the GGSN.
6)Èç¹ûMSÊÇPMM-CONNECTED×´ ̬£¬2G+3G SGSN·¢ËÍSRNS Data Forward Command(RAB ID,´«Êä²ãµØÖ·¡¢Iu´«Êä¹ØÁª£©ÏûÏ¢¸øSRNS¡£Õ⽫֪ͨSRNS£¬2G+3G SGSNÒѾ׼±¸ºÃ½ÓÊÕÊý¾Ý±¨ÎÄ¡£Ò»µ©´Ó2G+3G SGSN½ÓÊÕµ½Õâ¸öÏûÏ¢£¬SRNSÓ¦¿ªÊ¼Æô¶¯Êý¾Ýת·¢¼ÆʱÆ÷¡£
6a£© Èç¹ûÔÚIuģʽ½¨Á¢ÁËÖ±½ÓËíµÀ£¬SGSN·¢ËÍUpdate PDP Context Request¸ø¹ØÁªµÄGGSN£¬À´½¨Á¢ÔÚSGSNºÍGGSNÖ®¼äµÄGTPËíµÀ¡£GGSN¸üÐÂÓû§ÃæµØÖ·ºÍÏÂÐÐÊý¾ÝµÄTEID²¢·µ»ØUpdate PDP Context ResponseÏûÏ¢¡£³ý´ËÒÔÍ⣬Èç¹ûÓбðµÄ±ä»¯£¬ÈçRATÀàÐ͵ı仯ÐèÒªÓÃÓڼƷÑÄ¿µÄ£¬SGSN·¢ËÍUpdate PDP Context Request(SGSNµØÖ·ºÍTEID¡¢ÐÉ̵ÄQOS¡¢RATÀàÐÍ£©ÏûÏ¢¸øGGSN¡£
7) For each RAB indicated by the SRNS Data Forward Command the SRNS starts duplicating and tunnelling the buffered GTP-PDUs back to the 2G+3G SGSN. For each radio bearer which uses lossless PDCP the GTP-PDUs related to transmitted but not yet acknowledged PDCP PDUs are duplicated and tunnelled back to the 2G+3G SGSN together with their related downlink PDCP sequence numbers. The 2G+3G SGSN converts the PDCP sequence numbers to SNDCP sequence number (by stripping off the eight most significant bits of the PDCP sequence numbers).
7£© ÓÉSRNS Data Forward CommandÖ¸Ã÷µÄÿһ¸öRAB£¬SRNS¿ªÊ¼½«»º´æµÄGTP-PDU¸´ÖƲ¢ÇÒ·âÈëËíµÀ·¢¸ø2G+3G SGSN¡£¶ÔʹÓÃÁËÎÞËðPDCPѹËõµÄÿһ¸öÎÞÏß³ÐÔØ£¬Ïà¹ØµÄÒѾ´«Ê䵫»¹Ã»Óеõ½È·ÈϵÄGTP-PDU£¬PDCP PDU½«±»¸´ÖƲ¢ÇÒºÍËûÃÇÏà¹ØÁªµÄPDCPÐòÁкÅÒ»Æðͨ¹ýËíµÀ»Ø´«¸ø2G+3G SGSN¡£2G+3G SGSN½«°ÑPDCPÐòÁкÅת»»ÎªSNDCPÐòÁкÅ(ͨ¹ýÈ¥³ýPDCPÐòÁкŵÄ×î¸ß8룩¡£
8) The 2G+3G SGSN sends an Iu Release Command message to the SRNS. When the RNC data-forwarding timer has expired, the SRNS responds with an Iu Release Complete message.
8£©2G+3G SGSN·¢ËÍIu Release CommandÏûÏ¢¸øSRNS¡£µ±RNCת·¢Êý¾Ý¼ÆʱÆ÷³¬Ê±£¬SRNSÏìÓ¦Ò»¸öIu Release CompleteÏûÏ¢¡£
9) If the association has to be established i.e. if Update Type indicates combined RA / LA update with IMSI attach requested, or if the LA changed with the routeing area update, then the 2G+3G SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location Update Type) to the VLR. Location Update Type shall indicate IMSI attach if Update Type in step 1 indicated combined RA / LA update with IMSI attach requested. Otherwise, Location Update Type shall indicate normal location update. When the SGSN does not provide functionality for the Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the VLR number is derived from the RAI. When the SGSN provides functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the SGSN uses the RAI and a hash value from the IMSI to determine the VLR number. The VLR creates or updates the association with the 2G+3G SGSN by storing the SGSN Number.
9£©Èç¹û¹ØÁªÐèÒª½¨Á¢£¬Ò²¾ÍÊǸüÐÂÀàÐÍָʾ ÁË´øÓÐIMSI¸½×ŵÄÁªºÏµÄRA/LAUÇëÇ󣬻òÔÚRAUʱ·¢ÉúÁËLAµÄ±ä»¯£¬ÄÇô2G+3G SGSN·¢ËÍLocation Update Request(ÐÂLAI¡¢IMSI¡¢SGSN±àºÅ¡¢Location Update Type)¸øVLR¡£Location Update TypeӦָʾΪIMSI¸½×Å---Èç¹ûÔÚ²½Öè1µÄ¸üÐÂÀàÐÍָʾµÄÊÇ´øÓÐIMSI¸½×ÅÇëÇóµÄÁªºÏRA/LAU¡£³ý´ËÒÔÍ⣬Location Update TypeӦָʾΪһ¸öÕý³£µÄLocation Update¡£µ±SGSN²»Îª¶à¸öCN½ÚµãÌṩµ½RAN½ÚµãµÄÓòÄÚÁ¬½Ó¹¦ÄܵĻ°£¬VLR±àºÅ½«´ÓRAI»ñÈ¡¡£µ±SGSNÌṩÕâ¸ö¹¦ÄÜʱ£¬SGSNʹÓà RAIÒÔ¼°´ÓIMSIµÃµ½µÄÒ»¸ö¹þÏ£º¯ÊýÀ´¾ö¶¨VLR±àºÅ¡£VLRͨ¹ý´æ´¢SGSN±àºÅÀ´´´½¨»ò¸üÐÂÓë2G+3G SGSNµÄ¹ØÁª¡£
10) If the subscriber data in the VLR is marked as not confirmed by the HLR, the new VLR informs the HLR. The HLR cancels the data in the old VLR and inserts subscriber data in the new VLR:
a) The new VLR sends an Update Location (new VLR) to the HLR.
b) The HLR cancels the data in the old VLR by sending Cancel Location (IMSI) to the old VLR.
c) The old VLR acknowledges with Cancel Location Ack (IMSI).
d) The HLR sends Insert Subscriber Data (IMSI, subscriber data) to the new VLR.
e) The new VLR acknowledges with Insert Subscriber Data Ack (IMSI).
f) The HLR responds with Update Location Ack (IMSI) to the new VLR.
10)Èç¹ûVLRÉϵÄÇ©Ô¼Êý¾Ý±ê¼ÇΪδµÃµ½HLRµÄÈ·ÈÏ£¬Ôònew VLRҪ֪ͨHLR¡£HLRÈ¡ÏûÔÚold VLRÉϵÄÊý¾Ý²¢ÔÚnew VLR²åÈëеÄÓû§Ç©Ô¼Êý¾Ý£º
a£©new VLR·¢ËÍupdate location(new VLR)¸øHLR¡£
b) HLR·¢ËÍcancel location(IMSI)ÏûÏ¢¸øold VLRÀ´È¡ÏûÆäÉϵÄÊý¾Ý¡£
c£©old VLR·¢ËÍcancel location ack£¨IMSI)½øÐÐÈ·ÈÏ¡£
d£©HLR·¢ËͲåÈëÇ©Ô¼Óû§Êý¾Ý(IMSI,Ç©Ô¼Êý¾Ý£©¸ønew VLR¡£
e£©new VLR·¢ËÍinsert subscriber data ack(IMSI)½øÐÐÈ·ÈÏ¡£
f£©HLR·¢ËÍupdate location ack£¨IMSI£©¸ønew VLR½øÐÐÏìÓ¦¡£
11) The new VLR allocates a new VLR TMSI and responds with Location Update Accept (VLR TMSI) to the 2G+3G SGSN. VLR TMSI is optional if the VLR has not changed.
12) The 2G+3G SGSN validates the MS's presence in the new RA. If due to roaming restrictions or access restrictions the MS is not allowed to be attached in the RA, or if subscription checking fails, the 2G+3G SGSN rejects the routeing area update with an appropriate cause. If all checks are successful, the 2G+3G SGSN updates MM and PDP contexts for the MS. A new P TMSI may be allocated. A logical link is established between the new 2G+3G SGSN and the MS. 2G+3G-SGSN initiates the establishment procedure. A Routeing Area Update Accept (P TMSI, P TMSI Signature, Receive N PDU Number (= converted PDCP SNU), IMS voice over PS Session Supported Indication) message is returned to the MS. Receive N PDU Number contains the acknowledgements for each NSAPI which used lossless PDCP before the start of the update procedure, thereby confirming all mobile-originated N PDUs successfully transferred before the start of the update procedure. If Receive N PDU Number confirms the reception of N PDUs, these N PDUs shall be discarded by the MS. The IMS voice over PS Session Supported Indication is set as described in clause 5.3.8.
11£©new VLR·ÖÅäÒ»¸öеÄVLR TMSI²¢ÇÒÏìÓ¦location update accept(VLR TMSI)¸ø2G+3G SGSN¡£VLR TMSIÊÇ¿ÉÑ¡µÄ£¬Èç¹ûVLRûÓз¢Éú±ä»¯µÄ»°¡£
12£©2G+3G SGSNÑéÖ¤ÔÚÐÂRAÖÐMSµÄ´æÔÚÐÔ¡£Èç¹ûÒòΪÂþÓÎÏÞÖÆ»ò½ÓÈëÏÞÖÆ£¬MS²»ÔÊÐí¸½×ŵ½RA£¬»òÕßÈç¹ûÇ©Ô¼¼ì²éʧ°Ü£¬Ôò2G+3G SGSN¾Ü¾øRAU²¢¸ø³öÔÒòÖµ¡£Èç¹ûËùÓмì²é¶¼³É¹¦£¬2G+3G SGSN¸üÐÂMSµÄMMºÍPDPÉÏÏÂÎÄ¡£Ò»¸öеÄP-TMSI½«±»·ÖÅä¡£Ò»ÌõÂß¼Á´Â·½«ÔÚnew 2G+3G SGSNºÍMSÖ®¼ä½¨Á¢¡£2G+3G SGSN·¢Æð½¨Á¢Á÷³Ì¡£Ò»¸öRAU accept(P-TMSI¡¢P-TMSIÇ©Ãû¡¢Receive N-PDU Number£¨=ת»»µÄPDCP SNU)£¬IMS voice over PS»á»°Ö¸Ê¾Ö¸Ê¾£©ÏûÏ¢½«·µ»Ø¸øMS¡£Receive N-PDU Number°üº¬ÁËÔÚ¸üÐÂÁ÷³Ì¿ªÊ¼Ö®Ç°£¬Ê¹ÓÃÁËÎÞËðPDCPµÄ¶Ôÿ¸öNSAPIµÄÈ·ÈÏ£¬Òò´ËÈ·ÈÏÁËÔÚ¿ªÊ¼¸üÐÂÁ÷³Ì֮ǰËùÓÐMS·¢ÆðµÄ³É¹¦´«µÝµÄN- PDU¡£Èç¹ûReceive N-PDU NumberÈ·ÈÏÁ˶ÔN-PDUµÄ½ÓÊÕ£¬ÄÇЩN-PDUÓ¦±»MS¶ªÆú¡£IMS voice over PS»á»°Ö¸Ê¾Ö¸Ê¾¸ù¾Ý5.3.8Õ½ÚÃèÊöÉèÖá£
13) The MS acknowledges the new P TMSI by returning a Routeing Area Update Complete (Receive N PDU Number) message to the SGSN. Receive N PDU Number (= converted PDCP SND) contains the acknowledgements for each NSAPI which used lossless PDCP before the start of the update procedure, thereby confirming all mobile-terminated N PDUs successfully transferred before the start of the update procedure. If Receive N PDU Number confirms the reception of N PDUs, these N PDUs shall be discarded by the 2G+3G-SGSN.The MS deducts Receive N PDU Number from PDCP SND by stripping off the eight most significant bits. PDCP SND is the PDCP sequence number for the next expected in-sequence downlink packet to be received in the MS per radio bearer, which used lossless PDCP. The new 2G-SGSN negotiates with the MS for each NSAPI the use of acknowledged or unacknowledged SNDCP regardless whether the SRNS used lossless PDCP or not.
14) The 2G+3G SGSN sends a TMSI Reallocation Complete message to the VLR if the MS confirms the VLR TMSI.
15) The 2G+3G SGSN and the BSS may execute the BSS Packet Flow Context procedure.
13)MS ·µ»ØRAU Complete(Receive N-PDU Number£©ÏûÏ¢¸øSGSNÀ´È·È϶ÔÐÂP-TMSIµÄ·ÖÅä¡£Receive N-PDU Number£¨=ת»»µÄPDCP SND£©°üº¬Á˸üÐÂÁ÷³Ì¿ªÊ¼Ö®Ç°£¬Ê¹ÓÃÁËÎÞËðPDCPµÄ¶Ôÿ¸öNSAPIµÄÈ·ÈÏ£¬Òò´ËÈ·ÈÏÁËÔÚ¿ªÊ¼¸üÐÂÁ÷³Ì֮ǰËùÓÐMS½ÓÊյijɹ¦´«µÝµÄN-PDU¡£Èç¹û Receive N-PDU NumberÈ·ÈÏÁ˶ÔN-PDUµÄ½ÓÊÕ£¬ÄÇЩN-PDUÓ¦±»2G+3G SGSN¶ªÆú¡£MSͨ¹ý°þÀëPDCP SNDµÄ¸ß8λÓÐЧλÀ´µÃµ½Receive N-PDU Number¡£PDCP SNDÊÇÒ»¸öPDCPÐòÁкţ¬ÓÃÓÚ±êʶÔÚÿ¸öÎÞÏß³ÐÔØÉÏ£¬ÏÂÒ»¸öÆÚÍûÔÚMSÉÏÊÕµ½µÄʹÓÃÁËÎÞËðPDCPµÄÏÂÐÐÊý¾Ý±¨ÎÄ¡£New 2G-SGSNºÍMSΪÿ¸öNSAPIÐÉÌʹÓÃÈ·ÈÏ»ò·ÇÈ·ÈÏSNDCP£¬¶ø²»¹Ü֮ǰSRNSÊÇ·ñʹÓÃPDCP»òûÓÐʹÓá£
14£©2G+3G SGSN·¢ËÍTMSI Reallocation CompleteÏûÏ¢¸øVLR---Èç¹ûMSÈ·ÈÏÁËVLR TMSIµÄ»°¡£
15£©2G+3G SGSNÒÔ¼°BSS¿ÉÖ´ÐÐBSS Packet Flow ContextÁ÷³Ì¡£
6.13.1 Intra SGSN Intersystem Change
An SGSN that supports both the Gb and Iu PS interfaces may support an intra-SGSN intersystem change if the radio access technology nodes serving the MS before and after the intersystem change are both served by this SGSN.
Ò»¸öͬʱ֧³ÖGbºÍIu PS½Ó¿ÚµÄSGSN¿ÉÒÔÖ§³ÖÒ»¸öintra-SGSNµÄϵͳ¼ä¸Ä±ä---µ±Ö®Ç°ºÍÖ®ºóΪMSÌṩ·þÎñµÄÎÞÏß½ÓÈë¼¼Êõ½ÚµãÓÉͬһ¸öSGSN·þÎñµÄʱºò¡£
6.13.1.1 Iu mode to A/Gb mode Intra SGSN Change
6.13.1.1.1 Iu mode to A/Gb mode Intra SGSN Change using Gn/Gp
The intersystem change from Iu mode to A/Gb mode takes place when an MS changes from UTRAN or GERAN Iu mode to A/Gb mode. Depending on the PMM state before the intersystem change and whether the RA is changed or not, one of the following procedures is initiated by the MS:
- When an MS in PMM IDLE state changes to the A/Gb mode without changing the RA, the MS shall follow the selective RA update procedures, see clause "Selective RA Update".
- When an MS in PMM IDLE state changes to the A/Gb mode and the RA changes, the MS shall initiate the GPRS RA update procedure, see clause "Intra SGSN Routeing Area Update".
- When an MS in PMM CONNECTED state changes to the A/Gb mode, the MS shall initiate the GPRS RA update procedure independent of whether the RA has changed or not. The RA update procedure is either combined RA / LA update or only RA update.
´ÓIuģʽµ½A/GbģʽµÄϵͳ¼ä¸Ä±ä£¬ÊÇÔÚMS·¢ÉúÁË´ÓUTRAN»òGERAN Iuģʽµ½A/GbģʽµÄ¸Ä±äʱ²úÉúµÄ¡£¸ù¾ÝÔÚϵͳ¼ä¸Ä±ä·¢Éú֮ǰµÄPMM״̬ÒÔ¼°RAÊÇ·ñ¸Ä±ä£¬ÒÔÏÂÁ÷³ÌÖ®Ò»½«ÓÉMS·¢Æð£º
- µ±MSÔÚPMM-IDLE״̬±ä¸üµ½A/Gbģʽ²¢ÇÒû¸Ä±äRA,MSÓ¦Ö´ÐÐÑ¡ÔñÐÔµÄRAUÁ÷³Ì£¬²Î¿¼Õ½ڡ°Ñ¡ÔñÐÔRA¸üС±¡£
- µ±MSÔÚPMM-IDLE״̬±ä¸üµ½A/Gbģʽ²¢ÇÒRA¸Ä±äÁË£¬MSÓ¦·¢ÆðGPRS RAUÁ÷³Ì£¬²Î¿¼Õ½ڡ°Intra SGSN RAU".
- µ±MSÔÚPMM-CONNECTED״̬±ä¸üµ½A/Gbģʽ,²»¹ÜÓÐûÓз¢ÉúRA±ä»¯,MS¶¼Ó¦·¢ÆðÒ»¸öGPRS RAUÁ÷³Ì.Õâ¸öRAUÁ÷³Ì»òÕßÊÇÒ»¸öÁªºÏµÄRA/LAU,»òÕßÖ»ÊÇÒ»¸öRAU.
A combined RA / LA update takes place in network operation mode I when the MS enters a new RA or when a GPRS-attached MS performs IMSI attach. The MS sends a Routeing Area Update Request message indicating that an LA update may also need to be performed, in which case the SGSN forwards the LA update to the VLR. This concerns only idle mode (see TS 23.122 [7b]), as no combined RA / LA updates are performed during a CS connection. In the context of this specification, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an MS in Iu mode.
Ò» ¸öÁªºÏµÄRA/LAU·¢ÉúÔÚÍøÂç²Ù×÷ģʽI---²¢ÇÒµ±MS½øÈëÁËÒ»¸öеÄRA»òµ±Ò»¸öGPRS¸½×ŵÄMSÖ´ÐÐÁËIMSI¸½×Å.MS·¢ËÍRAU RequestÏûϢָʾÕâÊÇÒ»¸öLAU¿ÉÄÜÒ²ÐèÒªÖ´ÐÐ,SGSNת·¢LAU¸øVLR.Õâ½öºÍidleģʽÓйØ(²Î¿¼TS23.122),ÒòΪÔÚÒ»¸öCSÁ¬ ½ÓÆÚ¼äûÓÐÁªºÏµÄRA/LAU±»Ö´ÐÐ.±¾¹æ·¶ÖÐÉÏÏÂÎĵÄÃèÊöÖÐ,RNS»òRNCµÄÊõÓïÒ²¿ÉÒÔÏàÓ¦²Î¿¼GERAN BSS»òBSC---µ±ÎªÒ»¸öIuģʽµÄMS·þÎñʱ.
Figure 52: Iu mode to A/Gb mode Intra SGSN Change
NOTE: All steps in figure 52 are common for architecture variants using Gn/Gp based interaction with a GGSN and using S4 based interactions with an S GW and P GW. For S4 based interaction with an S GW and P GW, procedure step (A) is defined in clause 6.13.1.1.2.
×¢ÊÍ£ºÔÚͼÀý52ÖеÄËùÓв½Öè¶ÔÓÚʹÓÃGn/Gp½Ó¿ÚºÍGGSN½»»¥£¬»¹ÊÇʹÓÃS4½Ó¿ÚºÍSGW/PGW½»»¥µÄ¼Ü¹¹µÄ¶¼Êǹ«¹²µÄ¡£»ùÓÚS4½Ó¿ÚºÍSGW/PGWµÄ½»»¥µÄ²½ÖèA£¬²Î¿¼Õ½Ú6.13.1.1.2¡£
1) The MS or RAN decides to perform an intersystem change which makes the MS switch to a new cell where A/Gb mode has to be used, and stops transmission to the network.
2) The MS sends a Routeing Area Update Request (old RAI, old P TMSI Signature, Update Type, Voice domain preference and UE's usage setting) message to the 2G+3G SGSN. Update Type shall indicate RA update or combined RA / LA-update or, if the MS wants to perform an IMSI attach, combined RA / LA update with IMSI attached requested. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the 2G+3G SGSN. The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 5.3.15.
If there is an ongoing emergency bearer service and a Routing Area Update Request is received the Routing Area Update shall be rejected with a cause code indicating that access to GERAN is not allowed.
1£©MS»òRAN¾ö¶¨Ö´ÐÐÒ»¸öϵͳ¼ä¸Ä±ä£¬Ê¹µÃMSÄÜÇл»µ½Ò»¸öеÄA/GbģʽϵÄСÇø£¬²¢ÇÒÍ£Ö¹´«µÝÊý¾Ýµ½ÍøÂç¡£
2£©MS ·¢ËÍRAUÇëÇó£¨old RAI¡¢old P-TMSIÇ©Ãû¡¢¸üÐÂÀàÐÍ¡¢ÓïÒôÓòÓÅÏȼ¶ºÍUEµÄʹÓÃÉèÖã©ÏûÏ¢¸ø2G+3G SGSN¡£¸üÐÂÀàÐÍÓ¦Ö¸Ã÷Õâ¸öÒ»¸öRAU»òÊÇÒ»¸öÁªºÏµÄRA/LAY»òÕߣ¬Èç¹ûMSÏëÖ´ÐÐÒ»¸öIMSIµÄ¸½×Å¡¢´øÓÐIMSI¸½×ÅÇëÇóµÄÁªºÏµÄRA /LAU¡£BSSÓ¦¼ÓÈëCGI£¨Ð¡ÇøÈ«Çò±êʶ£©²¢°üÀ¨Ð¡ÇøµÄRACºÍLACµ½Õâ¸ö½ÓÊÕµÄÏûÏ¢ÖУ¬È»ºóÔÙ´«µÝ¸ø2G+3G SGSN¡£UE¸ù¾ÝËü×Ô¼ºµÄÅäÖ㬰´ÕÕÕ½Ú5.3.15µÄÃèÊö£¬À´ÉèÖÃÓïÒôÓòÓÅÏȼ¶ºÍËüµÄʹÓÃÉèÖá£
3) If the MS is PMM CONNECTED state, the 2G+3G SGSN sends an SRNS Context Request (IMSI) message to the SRNS.
4) Upon reception of the SRNS Context Request message, the SRNS starts buffering and stops sending downlink PDUs to the MS. The SRNS responds with an SRNS Context Response (GTP SNDs, GTP SNUs, PDCP-SNDs, PDCP SNUs) message. The GTP sequence numbers are included for each PDP context indicating the next in-sequence downlink GTP-PDU to be sent to the MS and the next in-sequence GTP PDU to be tunnelled to the GGSN. For each active PDP context, which uses lossless PDCP, the SRNS also includes the uplink PDCP sequence number (PDCP SNU) and the downlink PDCP sequence number (PDCP-SND). PDCP SNU is the PDCP sequence number for the next expected in-sequence uplink packet to be received from the MS. PDCP-SND is the PDCP sequence number for the first downlink packet for which successful transmission has not been confirmed. The 2G+3G SGSN shall strip off the eight most significant bits of the passed PDCP sequence numbers, thus converting them to SNDCP N PDU numbers of the respective 2G GPRS PDP contexts.
3£©Èç¹ûMSÊÇÔÚPMM-CONNECTED״̬£¬2G+3G SGSN·¢ËÍSRNS Context Request(IMSI)ÏûÏ¢¸øSRNS¡£
4) Ò»µ©½ÓÊÕµ½SRNS Context RequestÏûÏ¢,SRNS¿ªÊ¼»º´æ²¢ÇÒÍ£Ö¹·¢ËÍÏÂÐÐPDU¸øMS¡£SRNSÏìÓ¦Ò»¸öSRNS Context Response(GTP SNDs¡¢GTP SNUs¡¢PDCP-SNDs¡¢PDCP SNUs£©ÏûÏ¢¡£Ã¿¸öPDPÉÏÏÂÎĶ¼°üº¬ÁËGTPÐòÁкÅÀ´Ö¸Ê¾ÐòÁÐÖн«Òª·¢Ë͸øMSµÄÏÂÒ»¸öÏÂÐÐGTP-PDU£¬ÒÔ¼°ÐòÁÐÖÐÏÂÒ»¸ö½«Òª·¢Ë͸øGGSN±»·â ×°½øËíµÀµÄGTP PDU¡£¶Ôÿһ¸öactiveµÄPDPÉÏÏÂÎÄ£¬ÈçʹÓÃÁËÎÞËðPDCP£¬SRNSÒ²Ó¦°üº¬ÉÏÐеÄPDCPÐòÁкÅ(PDCP SNU¼´Sequence Number Uplink)ÒÔ¼°ÏÂÐÐPDCPÐòÁкÅ(PDCP-SND¼´Sequence Number Downlink)¡£PDCP SNUÊÇÒ»¸öPDCPÐòÁкţ¬±íʾµÄÊÇÏÂÒ»¸öÆÚÍûµÄ´ÓMS½ÓÊÕµÄÓÐÐòµÄÉÏÐÐÊý¾Ý±¨ÎÄ¡£PDCP-SNDÊÇÒ»¸öPDCPÐòÁкţ¬±íʾµÄÊǵÚÒ»¸ö³É¹¦´«µÝµ«»¹ ûÓб»È·ÈϵÄÏÂÐÐÊý¾Ý°ü¡£2G+3G SGSNÓ¦ÌáÈ¡ÒѾ´«µÝµÄPDCPÐòÁкŵİËλ×î¸ßÓÐЧ룬½«Ö®×ª»»ÎªÔÚ2G GPRS PDPÉÏÏÂÎÄÖÐÏàÓ¦µÄSNDCP N PDUµÄÖµ¡£
5) Security functions may be executed.
5£©°²È«¹¦ÄÜ¿ÉÒÔ±»Ö´ÐС£
6) If the MS is PMM CONNECTED, the 2G+3G SGSN sends an SRNS Data Forward Command (RAB ID, Transport Layer Address, Iu Transport Association) message to the SRNS. This informs the SRNS that the 2G+3G SGSN is ready to receive data packets. Upon reception of SRNS Data Forward Command message from the 2G+3G SGSN the SRNS shall start the data-forwarding timer.
6a)If Direct Tunnel was established in Iu mode the SGSN sends Update PDP Context Request to the GGSN(s) concerned to establish the GTP tunnel between SGSN and GGSN. The GGSN(s) update the address for User Plane and downlink TEID for data and return an Update PDP Context Response. Otherwise, if there were changes of for example the RAT type that e.g. can be used for charging, the SGSN sends Update PDP Context Request (SGSN Address and TEID, QoS Negotiated, RAT type) message to the GGSN.
6)Èç¹ûMSÊÇPMM-CONNECTED×´ ̬£¬2G+3G SGSN·¢ËÍSRNS Data Forward Command(RAB ID,´«Êä²ãµØÖ·¡¢Iu´«Êä¹ØÁª£©ÏûÏ¢¸øSRNS¡£Õ⽫֪ͨSRNS£¬2G+3G SGSNÒѾ׼±¸ºÃ½ÓÊÕÊý¾Ý±¨ÎÄ¡£Ò»µ©´Ó2G+3G SGSN½ÓÊÕµ½Õâ¸öÏûÏ¢£¬SRNSÓ¦¿ªÊ¼Æô¶¯Êý¾Ýת·¢¼ÆʱÆ÷¡£
6a£© Èç¹ûÔÚIuģʽ½¨Á¢ÁËÖ±½ÓËíµÀ£¬SGSN·¢ËÍUpdate PDP Context Request¸ø¹ØÁªµÄGGSN£¬À´½¨Á¢ÔÚSGSNºÍGGSNÖ®¼äµÄGTPËíµÀ¡£GGSN¸üÐÂÓû§ÃæµØÖ·ºÍÏÂÐÐÊý¾ÝµÄTEID²¢·µ»ØUpdate PDP Context ResponseÏûÏ¢¡£³ý´ËÒÔÍ⣬Èç¹ûÓбðµÄ±ä»¯£¬ÈçRATÀàÐ͵ı仯ÐèÒªÓÃÓڼƷÑÄ¿µÄ£¬SGSN·¢ËÍUpdate PDP Context Request(SGSNµØÖ·ºÍTEID¡¢ÐÉ̵ÄQOS¡¢RATÀàÐÍ£©ÏûÏ¢¸øGGSN¡£
7) For each RAB indicated by the SRNS Data Forward Command the SRNS starts duplicating and tunnelling the buffered GTP-PDUs back to the 2G+3G SGSN. For each radio bearer which uses lossless PDCP the GTP-PDUs related to transmitted but not yet acknowledged PDCP PDUs are duplicated and tunnelled back to the 2G+3G SGSN together with their related downlink PDCP sequence numbers. The 2G+3G SGSN converts the PDCP sequence numbers to SNDCP sequence number (by stripping off the eight most significant bits of the PDCP sequence numbers).
7£© ÓÉSRNS Data Forward CommandÖ¸Ã÷µÄÿһ¸öRAB£¬SRNS¿ªÊ¼½«»º´æµÄGTP-PDU¸´ÖƲ¢ÇÒ·âÈëËíµÀ·¢¸ø2G+3G SGSN¡£¶ÔʹÓÃÁËÎÞËðPDCPѹËõµÄÿһ¸öÎÞÏß³ÐÔØ£¬Ïà¹ØµÄÒѾ´«Ê䵫»¹Ã»Óеõ½È·ÈϵÄGTP-PDU£¬PDCP PDU½«±»¸´ÖƲ¢ÇÒºÍËûÃÇÏà¹ØÁªµÄPDCPÐòÁкÅÒ»Æðͨ¹ýËíµÀ»Ø´«¸ø2G+3G SGSN¡£2G+3G SGSN½«°ÑPDCPÐòÁкÅת»»ÎªSNDCPÐòÁкÅ(ͨ¹ýÈ¥³ýPDCPÐòÁкŵÄ×î¸ß8룩¡£
8) The 2G+3G SGSN sends an Iu Release Command message to the SRNS. When the RNC data-forwarding timer has expired, the SRNS responds with an Iu Release Complete message.
8£©2G+3G SGSN·¢ËÍIu Release CommandÏûÏ¢¸øSRNS¡£µ±RNCת·¢Êý¾Ý¼ÆʱÆ÷³¬Ê±£¬SRNSÏìÓ¦Ò»¸öIu Release CompleteÏûÏ¢¡£
9) If the association has to be established i.e. if Update Type indicates combined RA / LA update with IMSI attach requested, or if the LA changed with the routeing area update, then the 2G+3G SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location Update Type) to the VLR. Location Update Type shall indicate IMSI attach if Update Type in step 1 indicated combined RA / LA update with IMSI attach requested. Otherwise, Location Update Type shall indicate normal location update. When the SGSN does not provide functionality for the Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the VLR number is derived from the RAI. When the SGSN provides functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the SGSN uses the RAI and a hash value from the IMSI to determine the VLR number. The VLR creates or updates the association with the 2G+3G SGSN by storing the SGSN Number.
9£©Èç¹û¹ØÁªÐèÒª½¨Á¢£¬Ò²¾ÍÊǸüÐÂÀàÐÍָʾ ÁË´øÓÐIMSI¸½×ŵÄÁªºÏµÄRA/LAUÇëÇ󣬻òÔÚRAUʱ·¢ÉúÁËLAµÄ±ä»¯£¬ÄÇô2G+3G SGSN·¢ËÍLocation Update Request(ÐÂLAI¡¢IMSI¡¢SGSN±àºÅ¡¢Location Update Type)¸øVLR¡£Location Update TypeӦָʾΪIMSI¸½×Å---Èç¹ûÔÚ²½Öè1µÄ¸üÐÂÀàÐÍָʾµÄÊÇ´øÓÐIMSI¸½×ÅÇëÇóµÄÁªºÏRA/LAU¡£³ý´ËÒÔÍ⣬Location Update TypeӦָʾΪһ¸öÕý³£µÄLocation Update¡£µ±SGSN²»Îª¶à¸öCN½ÚµãÌṩµ½RAN½ÚµãµÄÓòÄÚÁ¬½Ó¹¦ÄܵĻ°£¬VLR±àºÅ½«´ÓRAI»ñÈ¡¡£µ±SGSNÌṩÕâ¸ö¹¦ÄÜʱ£¬SGSNʹÓà RAIÒÔ¼°´ÓIMSIµÃµ½µÄÒ»¸ö¹þÏ£º¯ÊýÀ´¾ö¶¨VLR±àºÅ¡£VLRͨ¹ý´æ´¢SGSN±àºÅÀ´´´½¨»ò¸üÐÂÓë2G+3G SGSNµÄ¹ØÁª¡£
10) If the subscriber data in the VLR is marked as not confirmed by the HLR, the new VLR informs the HLR. The HLR cancels the data in the old VLR and inserts subscriber data in the new VLR:
a) The new VLR sends an Update Location (new VLR) to the HLR.
b) The HLR cancels the data in the old VLR by sending Cancel Location (IMSI) to the old VLR.
c) The old VLR acknowledges with Cancel Location Ack (IMSI).
d) The HLR sends Insert Subscriber Data (IMSI, subscriber data) to the new VLR.
e) The new VLR acknowledges with Insert Subscriber Data Ack (IMSI).
f) The HLR responds with Update Location Ack (IMSI) to the new VLR.
10)Èç¹ûVLRÉϵÄÇ©Ô¼Êý¾Ý±ê¼ÇΪδµÃµ½HLRµÄÈ·ÈÏ£¬Ôònew VLRҪ֪ͨHLR¡£HLRÈ¡ÏûÔÚold VLRÉϵÄÊý¾Ý²¢ÔÚnew VLR²åÈëеÄÓû§Ç©Ô¼Êý¾Ý£º
a£©new VLR·¢ËÍupdate location(new VLR)¸øHLR¡£
b) HLR·¢ËÍcancel location(IMSI)ÏûÏ¢¸øold VLRÀ´È¡ÏûÆäÉϵÄÊý¾Ý¡£
c£©old VLR·¢ËÍcancel location ack£¨IMSI)½øÐÐÈ·ÈÏ¡£
d£©HLR·¢ËͲåÈëÇ©Ô¼Óû§Êý¾Ý(IMSI,Ç©Ô¼Êý¾Ý£©¸ønew VLR¡£
e£©new VLR·¢ËÍinsert subscriber data ack(IMSI)½øÐÐÈ·ÈÏ¡£
f£©HLR·¢ËÍupdate location ack£¨IMSI£©¸ønew VLR½øÐÐÏìÓ¦¡£
11) The new VLR allocates a new VLR TMSI and responds with Location Update Accept (VLR TMSI) to the 2G+3G SGSN. VLR TMSI is optional if the VLR has not changed.
12) The 2G+3G SGSN validates the MS's presence in the new RA. If due to roaming restrictions or access restrictions the MS is not allowed to be attached in the RA, or if subscription checking fails, the 2G+3G SGSN rejects the routeing area update with an appropriate cause. If all checks are successful, the 2G+3G SGSN updates MM and PDP contexts for the MS. A new P TMSI may be allocated. A logical link is established between the new 2G+3G SGSN and the MS. 2G+3G-SGSN initiates the establishment procedure. A Routeing Area Update Accept (P TMSI, P TMSI Signature, Receive N PDU Number (= converted PDCP SNU), IMS voice over PS Session Supported Indication) message is returned to the MS. Receive N PDU Number contains the acknowledgements for each NSAPI which used lossless PDCP before the start of the update procedure, thereby confirming all mobile-originated N PDUs successfully transferred before the start of the update procedure. If Receive N PDU Number confirms the reception of N PDUs, these N PDUs shall be discarded by the MS. The IMS voice over PS Session Supported Indication is set as described in clause 5.3.8.
11£©new VLR·ÖÅäÒ»¸öеÄVLR TMSI²¢ÇÒÏìÓ¦location update accept(VLR TMSI)¸ø2G+3G SGSN¡£VLR TMSIÊÇ¿ÉÑ¡µÄ£¬Èç¹ûVLRûÓз¢Éú±ä»¯µÄ»°¡£
12£©2G+3G SGSNÑéÖ¤ÔÚÐÂRAÖÐMSµÄ´æÔÚÐÔ¡£Èç¹ûÒòΪÂþÓÎÏÞÖÆ»ò½ÓÈëÏÞÖÆ£¬MS²»ÔÊÐí¸½×ŵ½RA£¬»òÕßÈç¹ûÇ©Ô¼¼ì²éʧ°Ü£¬Ôò2G+3G SGSN¾Ü¾øRAU²¢¸ø³öÔÒòÖµ¡£Èç¹ûËùÓмì²é¶¼³É¹¦£¬2G+3G SGSN¸üÐÂMSµÄMMºÍPDPÉÏÏÂÎÄ¡£Ò»¸öеÄP-TMSI½«±»·ÖÅä¡£Ò»ÌõÂß¼Á´Â·½«ÔÚnew 2G+3G SGSNºÍMSÖ®¼ä½¨Á¢¡£2G+3G SGSN·¢Æð½¨Á¢Á÷³Ì¡£Ò»¸öRAU accept(P-TMSI¡¢P-TMSIÇ©Ãû¡¢Receive N-PDU Number£¨=ת»»µÄPDCP SNU)£¬IMS voice over PS»á»°Ö¸Ê¾Ö¸Ê¾£©ÏûÏ¢½«·µ»Ø¸øMS¡£Receive N-PDU Number°üº¬ÁËÔÚ¸üÐÂÁ÷³Ì¿ªÊ¼Ö®Ç°£¬Ê¹ÓÃÁËÎÞËðPDCPµÄ¶Ôÿ¸öNSAPIµÄÈ·ÈÏ£¬Òò´ËÈ·ÈÏÁËÔÚ¿ªÊ¼¸üÐÂÁ÷³Ì֮ǰËùÓÐMS·¢ÆðµÄ³É¹¦´«µÝµÄN- PDU¡£Èç¹ûReceive N-PDU NumberÈ·ÈÏÁ˶ÔN-PDUµÄ½ÓÊÕ£¬ÄÇЩN-PDUÓ¦±»MS¶ªÆú¡£IMS voice over PS»á»°Ö¸Ê¾Ö¸Ê¾¸ù¾Ý5.3.8Õ½ÚÃèÊöÉèÖá£
13) The MS acknowledges the new P TMSI by returning a Routeing Area Update Complete (Receive N PDU Number) message to the SGSN. Receive N PDU Number (= converted PDCP SND) contains the acknowledgements for each NSAPI which used lossless PDCP before the start of the update procedure, thereby confirming all mobile-terminated N PDUs successfully transferred before the start of the update procedure. If Receive N PDU Number confirms the reception of N PDUs, these N PDUs shall be discarded by the 2G+3G-SGSN.The MS deducts Receive N PDU Number from PDCP SND by stripping off the eight most significant bits. PDCP SND is the PDCP sequence number for the next expected in-sequence downlink packet to be received in the MS per radio bearer, which used lossless PDCP. The new 2G-SGSN negotiates with the MS for each NSAPI the use of acknowledged or unacknowledged SNDCP regardless whether the SRNS used lossless PDCP or not.
14) The 2G+3G SGSN sends a TMSI Reallocation Complete message to the VLR if the MS confirms the VLR TMSI.
15) The 2G+3G SGSN and the BSS may execute the BSS Packet Flow Context procedure.
13)MS ·µ»ØRAU Complete(Receive N-PDU Number£©ÏûÏ¢¸øSGSNÀ´È·È϶ÔÐÂP-TMSIµÄ·ÖÅä¡£Receive N-PDU Number£¨=ת»»µÄPDCP SND£©°üº¬Á˸üÐÂÁ÷³Ì¿ªÊ¼Ö®Ç°£¬Ê¹ÓÃÁËÎÞËðPDCPµÄ¶Ôÿ¸öNSAPIµÄÈ·ÈÏ£¬Òò´ËÈ·ÈÏÁËÔÚ¿ªÊ¼¸üÐÂÁ÷³Ì֮ǰËùÓÐMS½ÓÊյijɹ¦´«µÝµÄN-PDU¡£Èç¹û Receive N-PDU NumberÈ·ÈÏÁ˶ÔN-PDUµÄ½ÓÊÕ£¬ÄÇЩN-PDUÓ¦±»2G+3G SGSN¶ªÆú¡£MSͨ¹ý°þÀëPDCP SNDµÄ¸ß8λÓÐЧλÀ´µÃµ½Receive N-PDU Number¡£PDCP SNDÊÇÒ»¸öPDCPÐòÁкţ¬ÓÃÓÚ±êʶÔÚÿ¸öÎÞÏß³ÐÔØÉÏ£¬ÏÂÒ»¸öÆÚÍûÔÚMSÉÏÊÕµ½µÄʹÓÃÁËÎÞËðPDCPµÄÏÂÐÐÊý¾Ý±¨ÎÄ¡£New 2G-SGSNºÍMSΪÿ¸öNSAPIÐÉÌʹÓÃÈ·ÈÏ»ò·ÇÈ·ÈÏSNDCP£¬¶ø²»¹Ü֮ǰSRNSÊÇ·ñʹÓÃPDCP»òûÓÐʹÓá£
14£©2G+3G SGSN·¢ËÍTMSI Reallocation CompleteÏûÏ¢¸øVLR---Èç¹ûMSÈ·ÈÏÁËVLR TMSIµÄ»°¡£
15£©2G+3G SGSNÒÔ¼°BSS¿ÉÖ´ÐÐBSS Packet Flow ContextÁ÷³Ì¡£
»Ø´ðÕߣº
OscarDon
»Ø´ðʱ¼ä£º2013-05-15 14:08
35 34
¼òµ¥À´ËµLAU»òÕßRAU¹ý³Ì¾ÍÏòCS»òPSÓòºËÐÄÍø˵Ã÷UEÔÚ¸ÃÓòÖУ¬²¢È¡µÃʹÓøÃÓò×ÊÔ´µÄȨÀû¡£
LAU¹ý³Ì·ÖΪ¿ª»úµÇ¼Ç×¢²á¡¢ÖÜÆÚÐÔλÖøüÐÂÒÔ¼°Õý³£Î»ÖøüУ¨Î»ÖÃÇø·¢Éú±ä¸ü£©£»
RAU¹ý³Ì·ÖΪÖÜÆÚÐԵĺÍÕý³£µÄ·ÓÉÇø¸üУ¨Â·ÓÉÇø·¢Éú±ä¸ü£©¡£
LAU¹ý³Ì·ÖΪ¿ª»úµÇ¼Ç×¢²á¡¢ÖÜÆÚÐÔλÖøüÐÂÒÔ¼°Õý³£Î»ÖøüУ¨Î»ÖÃÇø·¢Éú±ä¸ü£©£»
RAU¹ý³Ì·ÖΪÖÜÆÚÐԵĺÍÕý³£µÄ·ÓÉÇø¸üУ¨Â·ÓÉÇø·¢Éú±ä¸ü£©¡£
»Ø´ðÕߣº
marinelick
»Ø´ðʱ¼ä£º2013-05-24 13:37
36 27
ÈȵãÎÊÌâ
¸ü¶à¾«²Ê
ÁªÏµÎÒÃÇ - ÎÊͨÐÅר¼Ò | Powered by MSCBSC Òƶ¯Í¨ÐÅÍø © 2006 - |