Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.060  Word version:  16.0.0

Top   Top   Up   Prev   Next
1…   5…   5.3.8…   5.4…   5.4.2…   5.4.9…   5.6…   5.6.2   5.6.3…   5.6.3.7…   5.7…   6…   6.3…   6.5   6.6…   6.8…   6.9…   6.9.1.3   6.9.2…   6.9.2.2…   6.9.2.2.2   6.9.2.2.3…   6.9.2.2.5…   6.9.3…   6.10…   6.12…   6.13…   6.13.1.2…   6.13.2…   6.13.2.2   6.14…   8…   8.2…   9…   9.2.2…   9.2.2.2   9.2.2.3…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.4.2…   9.2.5…   12…   12.5   12.6   12.7…   12.8…   13…   14…   15…   15.3…   16…   16.2…   A…

 

6.9.3  Periodic RA and LA UpdatesWord‑p. 169
All GPRS-attached MSs, except A/Gb mode MSs in class B mode of operation engaged in CS communication, shall perform periodic RA updates. MSs that are IMSI-attached and not GPRS-attached shall perform periodic LA updates. Periodic RA updates are equivalent to intra SGSN routeing area updates as described in clause "Intra SGSN Routeing Area Update", with Update Type indicating periodic RA update. For MSs that are both IMSI-attached and GPRS-attached, the periodic updates depend on the mode of operation of the network:
  • If the network operates in mode I, periodic RA updates shall be performed, and periodic LA updates shall not be performed. In this case, the MSC/VLR shall disable implicit detach for GPRS-attached MSs and instead rely on the SGSN to receive periodic RA updates. If periodic RA updates are not received in the SGSN and the SGSN detaches the MS, the SGSN shall notify the MSC/VLR by sending an IMSI Detach Indication message.
  • If the network operates in mode II, both periodic RA updates and periodic LA updates shall be performed independently. RA updates are performed towards the SGSN, and LA updates are performed towards the MSC/VLR.
In A/Gb mode, the periodic RA update timer in the MS is stopped when an LLC PDU is sent since all sent LLC PDUs set the MM context state to READY. The periodic RA update timer is reset and started when the state returns to STANDBY.
In Iu mode, the periodic RA update timer in the MS is stopped when the MM context enters the PMM CONNECTED state. The periodic RA update timer is reset and started when the state returns to PMM IDLE state.
If the MS could not successfully complete the periodic RA update procedure after a retry scheme while the MS was in GERAN/UTRAN PS coverage, the MS shall wait a back-off time equal to the periodic LA update timer broadcast by the network before restarting the periodic RA update procedure.
Up

6.9.4  PS Handover Procedure |R6|

The PS Handover procedure is used to handover an MS with one or more packet flows from a source cell to a target cell, when at least one of the cells is a GERAN cell. The source and target cells can be located within either the same BSS (Intra BSS HO), different BSSs within the same SGSN (Intra SGSN HO) or belonging to different SGSNs (Inter SGSN HO), or systems with different radio access types (Inter RAT HO, Inter mode HO).
While the MS is still in the source cell:
  • Radio resources in the target cell are allocated and signalled to the MS.
  • System information of the target cell needed for access in the target cell is signalled to the MS.
After handover between GERAN and UTRAN is complete, the RAU procedure is performed even if the RAI has not changed.
As specified in clause 5.3.13.8, "Support for Non-IP data", with regard to CIoT EPS Optimisations, PDP Contexts of PDN Type "Non-IP" and PDN Connection to SCEF may need to be handled during the PS Handover Procedure. For an MS that is using a "Non-IP" connection to a GGSN/PGW, or a PDP Context to a SCEF, if these PDP Contexts cannot be supported by the target SGSN, the source SGSN does not attempt to handover those bearers and releases them upon successful completion of the handover. If the MS does not have any PDP Context other than Non-IP or SCEF ones that can be transferred, then the SGSN sends failure message to the source RAN node.
The complete PS Handover procedures are defined in TS 43.129.
The complete Inter RAT HO between E UTRAN and GERAN procedures are defined in TS 23.401.
Up

6.9.5  UE Radio Capability Match Request |R11|Word‑p. 170
If the SGSN requires more information on the UE capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.3.8), then the SGSN may send a UE Radio Capability Match Request to the RAN. This procedure is typically used during the Initial Attach procedure, during Routing Area Update procedure for the "first RAU following GERAN/E-UTRAN Attach" or for "UE Capability update" or when SGSN has not received the Voice Support Match Indicator (as part of the MM Context).
Reproduction of 3GPP TS 23.060, Figure 6.9.5-1: UE Radio Capability Match Request
Up
Step 1.
The SGSN indicates whether the SGSN wants to receive Voice support match indicator.
Step 2.
Upon receiving a UE Radio Capability Match Request from the SGSN, if the RAN has not already received the UE capabilities from the MS the RAN requests the MS to upload the UE Capability information by sending the RRC UE Capability Enquiry.
Step 3.
The MS provides the RAN with its UE capabilities sending the RRC UE Capability Information.
Step 4.
Upon receiving a UE Radio Capability Match Request from the SGSN, the RAN checks whether the UE capabilities are compatible with the network configuration. The RAN provides a Voice Support Match Indicator to the SGSN to indicate whether the UE capabilities and networks configuration are compatible.
For determining the appropriate UE Radio Capability Match Response, the RAN is configured by the operator to check whether the MS supports certain capabilities required for IMS PS Voice continuity. In a shared network, the RAN keeps a configuration separately per PLMN.
Up


Up   Top   ToC