Mobile Communications Systems Development. Rajib Taid. Читать онлайн. Newlib. NEWLIB.NET

Автор: Rajib Taid
Издательство: John Wiley & Sons Limited
Серия:
Жанр произведения: Техническая литература
Год издания: 0
isbn: 9781119778707
Скачать книгу
conversation purposes is intimated to the called UE through SIP:UPDATE method, following which it sends the SIP:RINGING status to the caller UE.

Schematic illustration of VoLTE call between IMS registered UEs.

      6.2.2 Interworking for VoLTE Call Through LTE/EPS: SRVCC

Schematic illustration of legacy and LTE network interworking for VoLTE call HO through SRVCC.

       MME and the MSC server and

       MME and SGSN, as shown above.

      In Figure 6.7, user A moved to a legacy 2G/3G coverage area. As the user moved away from the LTE coverage area and approaches a 2G/3G coverage area, the eNodeB detects a better signal level from the 2G/3G networks. UE sends the measurements reports to the eNodeB which in turn sends an SRVCC HO request to the MME. In Figure 6.7, the signaling and traffic paths are shown prior to and after the SRVCC HO. All the subsequent signaling and data communication takes place through the legacy network MSC server after the SRVCC HO is completed.

Schematic illustration of VoLTE call HO through SRVCC feature.

       How does SRVCC work?

       Indication of Feature Support

      An LTE UE indicates its SRVCC capability information through the class mark and network capability information sent along with the ATTACH Request message, refer to TS 24.301 [46], to the MME. MME indicates the SRVCC capability of a UE through the SRVCC operation possible IE in the INITIAL CONTEXT SETUP REQUEST MESSAGE, refer to TS 36.413 [97], to the eNodeB. MME may also request the SRVCC capability of a UE by sending the message UE Radio Capability Match Request (see Section 5.3.14 TS 23.401 [39]) to the UE through the eNodeB. Any subsequent changes in the SRVCC capability of a UE are also updated to the HSS by the MME.

       Initiation of Handover of LTE IMS Voice Call (VoLTE)

      SRVCC works by performing the handover of the ongoing VoLTE call as well as data session over IMS to the legacy GERAN/UTRAN network. Initiation of a handover operation works the same way as the normal handover procedure based on the signal‐level measurement reports reported from the UE to the E‐UTRAN. The source eNodeB sends the HANDOVER REQUIRED message, refer to TS 36.413 [97], to the MME with the SRVCC HO Indication IE for a handover of the existing VoLTE call. SRVCC HO Indication may be PS or PS and CS type. MME, in turn, initiates the SRVCC request to the MSC server. The MSC server prepares and executes the handover of the IMS voice call successfully. For further illustrations of the VoLTE call handover through the SRVCC method, refer to Figures 4.2.2‐1 and 4.2.3‐1, TS 23.216 [35].

       Handover of PS Call/Data Session

      The handover of an ongoing PS call during an SRVCC procedure is performed as usual as per the normal inter‐RAT handover procedures. For further illustrations of the inter‐RAT handover procedures, refer to Section 5.2.2 TS 23.401 [39].

      6.2.3 Interworking for Voice Call Through LTE/EPS: CSFB

Schematic illustration of legacy and LTE network interworking for CSFB.

       An MO or MT LTE UE that does not have the voice‐over IMS or VoLTE capability

       Other scenarios such as VoLTE‐capable UE that fails to register in the IMS.

      Unlike the interworking scenarios for VoLTE call as mentioned in Sections 6.2.1 and 6.2.2, no IMS is deployed and interworked as part of the LTE/EPS network with the CSFB arrangement. In this interworking scenario with CSFB arrangement, the LTE/EPS network provides only data services to subscribers.

      During a CSFB of a CS call, the ongoing PS session may be also transferred to the legacy network through PS HO procedure with reduced data rates. For the CSFB purpose, a new logical interface called SGs is configured between the MME and MSC/Visitor Location Register (VLR) to exchange signaling information only. The SGs logical interface also supports mobility management as well as MO/MT call establishment procedures. For more information on the CSFB, a protocol stack, and procedures supported over the SGs, refer to TS 23.272 [38] and TS 29.118 [68]. SGs interface uses the SCTP [17] layer and IP transport network. The SGs interface is similar to the GPRS/UMTS Gs interface that connects the SGSN and the MSC to provide CS domain services to MS engaged in a PS service.