Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.118  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   5…   5.2…   5.4…   5.10…   6…   7…   8…   9…

 

5.2  Location update for non-EPS services procedurep. 21

5.2.1  General descriptionp. 21

The location update for non-EPS services procedure is a general procedure used by UEs which are configured to use CS fallback and SMS over SGs, or SMS over SGs only. This procedure is not performed if:
  • the subscriber data indicates that the subscription is for packet only; or
  • the MME is registered for SMS for the UE (see TS 23.272).
This procedure allows UEs and the network to perform:
  • combined IMSI attach for EPS and non-EPS services or for SMS only;
  • IMSI attach for non-EPS services or for SMS only if the UE is already IMSI attached for EPS services;
  • normal location update procedure to the VLR if the UE is IMSI attached for both EPS and non-EPS services, or for SMS only; or
  • allocation of new TMSI to an UE.
The location update for non-EPS services procedure in the SGs interface is always started as a consequence of a direct action from the UE. The combined attach and tracking area update procedures are further specified in TS 23.272 and TS 24.301.
When a UE is IMSI attached for EPS and non-EPS services, the VLR shall stop any implicit detach timer. Instead the MME uses the "Paging Proceed Flag" to determine the likely availability of the UE to the network. Upon reception of the periodic Tracking Area Update message, the MME does not report to the VLR, and the MME shall not change the state of the SGs association. When the UE performs a detach only for EPS services or the MME performs an implicit detach for EPS services, and the VLR's implicit detach timer is not already running, the EPS detach indication to the VLR shall cause the VLR's implicit detach timer to be restarted from its initial value.
If the MME performs an implicit detach for both EPS and non-EPS services, then the MME shall send to the VLR an SGsAP-IMSI-DETACH-INDICATION message with cause "Implicit network initiated IMSI detach from EPS and non-EPS services", as further described in subclause 5.6 (the implicit IMSI detach message indicates that the UE is unavailable for both EPS and non-EPS services).
Up

5.2.2  Procedures in the MMEp. 22

5.2.2.1  Generalp. 22

The location update for non-EPS services procedure is initiated with a combined attach or a combined tracking area update procedure. On receipt of an ATTACH REQUEST message or a TRACKING AREA UPDATE REQUEST message from the UE, the MME handles the EPS related request as specified in TS 24.301.
When the MME receives the Update Location Answer message containing subscription data from the HSS, the MME determines whether it needs to perform location update for non-EPS services procedure. For the cases identified below, if the MME is configured with ability not to perform registrations with a VLR for the UE, the MME sends response message to the UE without starting the location update for non-EPS services procedure:
  • if the Network Access Mode (NAM) subscription data indicates that the subscription is for packet only (see TS 29.272); or
  • if the Network Access Mode (NAM) subscription data indicates that the subscription is for packet and circuit (see TS 29.272) and the MME is registered for SMS as specified in Annex C of TS 23.272 for this UE.
Otherwise, the MME shall start the location update for non-EPS services procedure and shall wait for the outcome of both location update procedures towards the VLR and the HSS before sending the response message to the UE.
Up

5.2.2.2  Location update initiationp. 22

5.2.2.2.1  Generalp. 22
If timer Ts6-1 is not running, the MME shall start the location update for non-EPS services procedure when it receives from the UE:
  • an attach request indicating combined EPS/IMSI attach;
  • a combined tracking area update request indicating Combined TA/LA updating with IMSI attach;
  • a combined tracking area update request and the MME detects that the LAI has changed;
  • a combined tracking area update request and the state of the SGs association is SGs-NULL; or
  • a combined tracking area update request and the MME serving the UE has changed.
If timer Ts6-1 is not running, the MME may start the location update for non-EPS services procedure when it receives from the UE:
  • a combined tracking area update request or a periodic tracking area update , if the MM context variable "VLR-Reliable" for the UE is set to "false" (see subclause 5.7.3).
If multiple PLMNs are available for the CS domain, the MME shall select a PLMN for CS domain as specified in TS 23.272. If the MME cannot select any PLMN for CS domain for the UE, the MME informs the UE that the CS domain is not available.
The MME shall determine the new location area identification as follows:
  • if the MME received a combined attach request or combined tracking area update request from the UE with an indication for "SMS only", or the network only supports "SMS only" or the network only has a few VLRs that support SGs interface, the MME may allocate a default location area identification specifically configured for that case;
  • else the MME derives the location area identification from the current tracking area identity where the UE is located. For this the MME may take any access restrictions provided by the HSS into account, if the network is using separate location areas for GERAN and UTRAN cells.
The MME shall derive the VLR name from the location area identification which was determined. For networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes', the VLR name is derived as described in TS 23.236.The MME shall include the location area identification in the new location area identifier information element in the SGsAP-LOCATION-UPDATE-REQUEST message.
In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes' (TS 23.236), if the TMSI based NRI container is not received from the UE, and the MME determines that the serving VLR of the UE is changed, the MME shall include in the Old location area identifier a specific LAI value which is not broadcasted in the network and not associated with any VLR.
In networks supporting the feature "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" as defined in TS 23.236, the MME shall support load re-distribution of UEs to another VLR than the current one. When the MME receives a periodic tracking area update request or a combined tracking area update request, the MME shall check whether for this UE there is a SGs association to a VLR for which load re-distribution has been initiated in the MME by O&M. If this is the case and
  • if a combined tracking area update request is received, the MME shall derive the new VLR name as described in TS 23.236 and then send the SGsAP-LOCATION-UPDATE-REQUEST message to the new selected VLR; or
  • if a periodic tracking area update request is received, dependent on network configuration and operator policy, the MME shall take one of the following actions:
    • perform a network initiated detach with detach type "IMSI detach" immediately after the completion of the periodic tracking area update procedure; or
    • derive the new VLR name as described in TS 23.236 and then send the SGsAP-LOCATION-UPDATE-REQUEST message to the new selected VLR.
If the VLR is configured for gateway core network (GWCN), the MME shall select a CS domain operator as specified in TS 23.272 and proceed as follows:
  • If the preferred RAT of the selected CS domain operator is GERAN and the UE does not support GERAN network sharing (see subclause 10.5.5.12 of TS 24.008), the MME shall include the selected CS domain operator in the selected CS domain operator information element, and the common PLMN in the new location area identifier information element in the SGsAP-LOCATION-UPDATE-REQUEST message; or
  • If only common PLMN ID and no multiple PLMN IDs are provided in CS domain for selection by the UE (see subclause 4.2.3.1 of TS 23.251), the MME shall include the selected CS domain operator in the selected CS domain operator information element, and the common PLMN in the new location area identifier information element in the SGsAP-LOCATION-UPDATE-REQUEST message.
If multiple PLMN IDs are provided in CS domain for selection by the UE and the UE supports GERAN network sharing (see subclause 10.5.5.12 of TS 24.008), the MME shall include the selected PLMN for CS domain in the new location area identifier information element as specified in TS 23.251.
The SGsAP-LOCATION-UPDATE-REQUEST message includes the type of location update performed by the UE in the EPS location update type information element. If the UE has performed a combined attach or a combined tracking area update indicating "combined TA/LA updating with IMSI attach", the MME indicates "IMSI attach", otherwise the MME indicates "Normal location update".
The MME shall include the TMSI status in the SGsAP-LOCATION-UPDATE-REQUEST message if the UE indicates in the ATTACH REQUEST or the TRACKING AREA UPDATE REQUEST message that it has no valid TMSI available. The MME shall also include the old location area identifier in the SGsAP-LOCATION-UPDATE-REQUEST message if the UE included the old location area identification in the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message.
The MME shall include the TMSI based NRI container in the SGsAP-LOCATION-UPDATE-REQUEST message if received from the UE.
If the MME supports the "Automatic Device Detection" (see TS 22.101) or the "Trace for Management Based Activation/Deactivation" (see TS 32.422), the MME shall include the IMEISV in the SGsAP-LOCATION-UPDATE-REQUEST message.
The MME shall add the UE's current TAI and E-CGI to the SGsAP-LOCATION-UPDATE-REQUEST message.
When the MME sends the SGsAP-LOCATION-UPDATE-REQUEST, the MME shall start timer Ts6-1.
If timer Ts6-1 is running and the MME receives from the UE:
  • an attach request indicating combined EPS/IMSI attach; or
  • a combined tracking area update with or without IMSI attach.
Then:
  • if the LAI determined by the MME is the same as in the outstanding request, the MME shall not process this new request and shall wait for the VLR response to the ongoing procedure;
  • if the LAI determined by the MME is different but the VLR name is the same as for previous LAI, any response from the VLR to the outstanding request is ignored, the MME shall stop and reset timer Ts6-1 and the MME shall start the location update for non-EPS services procedure; or
  • if the LAI determined by the MME is different and the VLR name is different as for previous LAI, any response from the previously addressed VLR to the outstanding request is ignored, the MME shall stop and reset timer Ts6-1, and the MME shall start the location update for non-EPS services procedure.
When the MME receives from the UE a tracking area update request and the MME serving the UE has changed, the MME shall stop and reset timer Ts6-1.
Up
5.2.2.2.2  VLR fails without restartp. 24
If the MME supports restoration for CS services via an alternative VLR as defined in TS 23.007 and, upon reception of a combined tracking area update request or a periodic tracking area update request from the UE, the MME determines that the VLR serving the UE is no longer in service, the MME may:
  • if a combined tracking area update request is received, select an alternative VLR that is in service for the UE and immediately perform the location update for non-EPS services procedure towards the selected VLR as described in subclause 5.2; or
  • if a periodic tracking area update request is received, dependent on network configuration and operator policy,
    • perform a network initiated detach with detach type "IMSI detach" immediately after the completion of the periodic tracking area update procedure and then select an alternative VLR that is in service for the UE during the subsequent combined tracking area update procedure, before performing the location update for non-EPS services procedure towards the selected VLR as described in subclause 5.2; or
    • select an alternative VLR that is in service for the UE and immediately perform the location update for non-EPS services procedure towards the selected VLR as described in subclause 5.2.
If the MME supports restoration for CS services via an alternative VLR as defined in TS 23.007 and, upon reception of an UPLINK NAS TRANSPORT message (see TS 24.301) from the UE, the MME determines that the VLR serving the UE is no longer in service, the MME may:
  • request the UE to re-attach for non-EPS services as specified in TS 24.301 and then select an alternative VLR that is in service for the UE during the subsequent combined tracking area update procedure, before performing the location update for non-EPS services procedure towards the selected VLR as described in subclause 5.2.
Up

5.2.2.3  Location update responsep. 25

If the MME receives an SGsAP-LOCATION-UPDATE-ACCEPT message from the VLR, the MME shall stop timer Ts6-1 and:
  • move the state of the SGs association to SGs-ASSOCIATED;
  • set the MM context variable "VLR-Reliable" to "true"; and
  • indicate to the UE the acceptance of the VLR to the location update procedure. The message sent to the UE includes the Location Area Identity (see TS 24.301).
The MME shall wait for the outcome of the location update for non-EPS services procedure towards the VLR before sending a response to location update procedure to the UE. When the MME receives an SGsAP-LOCATION-UPDATE-REJECT message from the VLR, it will map the reject cause received to the appropriate reject cause as specified in TS 24.301, and report this reject cause to the UE.
If the VLR included the Mobile identity information element in the SGsAP-LOCATION-UPDATE-ACCEPT message, the MME shall relay the information received to the UE. If the Mobile identity information element contains a new TMSI, this will cause the UE to perform a TMSI reallocation procedure. In this case, the MME shall send to the VLR the SGsAP-TMSI-REALLOCATION-COMPLETE message when the MME receives the ATTACH COMPLETE or the TRACKING AREA UPDATE COMPLETE message from the UE. If the Mobile identity information element contains an IMSI, this will cause the UE to deallocate its TMSI.
Up

5.2.2.4  Location update failurep. 25

If the MME receives an SGsAP-LOCATION-UPDATE-REJECT message from the VLR, the MME
  • shall stop timer Ts6-1;
  • shall move the state of the SGs association to SGs-NULL; and
  • indicates to the UE the rejection of the Location Update procedure by the VLR as specified in TS 24.301. The Reject cause value sent by the VLR shall be mapped to the appropriate reject cause as specified in TS 24.301, and the latter is forwarded to the UE.
Up

5.2.2.5  Abnormal casesp. 26

If timer Ts6-1 expires, the MME shall abort the Location Update for non-EPS service procedure and indicate this to the UE with the Reject cause value 'MSC temporarily not reachable'. The state of the SGs association to the VLR shall be SGs-NULL.
If the MME receives an SGsAP-LOCATION-UPDATE-ACCEPT message and timer Ts6-1 is not running then:
  • if timer Ts8 is running (see subclause 5.4), the message shall be ignored;
  • if timer Ts9 is running (see subclause 5.5), the message shall be ignored; or
  • if timers Ts8 and Ts9 are not running:
    • if the state of the SGs association to the VLR is SGs-ASSOCIATED, the message shall be ignored; or
    • if the state of the SGs association to the VLR is different than SGs-ASSOCIATED, the message shall be treated as a message incompatible with the protocol state of the MME (see subclause 7.3).
Up

5.2.2.6  Additional MME procedure for UE supporting NB-S1 mode onlyp. 26

This subclause applies when the UE supporting NB-S1 mode only requests SMS services via a normal attach request or tracking area update request.
If the UE supporting NB-S1 mode only requests SMS services using normal attach request or tracking area update request, the location update for non-EPS services procedure can be initiated by the MME when SMS over SGs is used.
If timer Ts6-1 is not running, the MME shall start the location update for non-EPS services procedure when it receives from the UE:
  • an attach request indicating EPS attach and "SMS only" in NB-S1 mode, SMS services via SMS in MME are not available and SMS over SGs is used for the UE;
  • a tracking area update request indicating TA updating and "SMS only" in NB-S1 mode, SMS services via SMS in MME are not available, SMS over SGs is used for the UE and the MME detects that the LAI has changed;
  • a tracking area update request indicating TA updating and "SMS only" in NB-S1 mode, SMS services via SMS in MME are not available, SMS over SGs is used for the UE and the state of the SGs association is SGs-NULL; or
  • a tracking area update request indicating TA updating and "SMS only" in NB-S1 mode, SMS services via SMS in MME are not available, SMS over SGs is used for the UE and the MME detects that the MME serving the UE has changed.
If the MME has a stored TMSI for the UE, the MME may include this TMSI in the TMSI based NRI container IE in the SGsAP-LOCATION-UPDATE-REQUEST message. Otherwise the MME shall indicate "no valid TMSI available" in the TMSI status IE in the SGsAP-LOCATION-UPDATE-REQUEST message.
If the MME received a normal attach request or normal tracking area update request from the UE with an indication for "SMS only", the MME may allocate a default location area identification specifically configured for that case.
If the MME receives an SGsAP-LOCATION-UPDATE-ACCEPT message from the VLR, the MME shall:
  • stop timer Ts6-1 and move the state of the SGs association to SGs-ASSOCIATED;
  • set the MM context variable "VLR-Reliable" to "true"; and
  • indicate to the UE the acceptance of SMS services as specified in TS 24.301.
If the VLR included the Location area identifier or the Mobile identity information element in the SGsAP-LOCATION-UPDATE-ACCEPT message, the MME may store the received Location area identifier or the Mobile identity information element for the subsequent location update for non-EPS services procedure for the UE. If the Mobile identity information element contains a new TMSI, the MME may send to the VLR the SGsAP-TMSI-REALLOCATION-COMPLETE message when the MME indicates to the UE the acceptance of SMS services. If the Mobile identity information element contains an IMSI, the MME may delete any stored TMSI for the UE.
If the MME receives an SGsAP-LOCATION-UPDATE-REJECT message from the VLR, the MME shall:
  • stop timer Ts6-1 and move the state of the SGs association to SGs-NULL; and
  • indicate to the UE the rejection of SMS services as specified in TS 24.301. The MME maps the location update reject cause received from the VLR to an appropriate value as specified in TS 24.301 and forwards to the UE.
If timer Ts6-1 expires, the MME shall abort the Location Update for non-EPS service procedure. The MME indicates to the UE the rejection of SMS services by setting an appropriate value and shall as specified in TS 24.301 and forwards to the UE. The state of the SGs association to the VLR shall be SGs-NULL.
Up

5.2.3  Procedures in the VLRp. 27

5.2.3.1  Generalp. 27

When a VLR receives an SGsAP-LOCATION-UPDATE-REQUEST message, the VLR checks whether the IMSI is known. If the IMSI is not known, the VLR retrieves the MM context of the UE from the HSS.
In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes' (TS 23.236), if the TMSI based NRI container is received in the SGsAP-LOCATION-UPDATE-REQUEST message, the VLR derives the NRI value. If the NRI value is not allocated by the VLR, the VLR retrieves the MM context of the UE from the HSS.
When the VLR is configured for gateway core network (GWCN), the VLR shall select the serving CS domain operator as follows:
  • If the selected CS domain operator information element is received in the SGsAP-LOCATION-UPDATE-REQUEST message, the VLR shall select the serving CS domain operator as specified in the selected CS domain operator information element;
  • If the selected CS domain operator information element is not received in the SGsAP-LOCATION-UPDATE-REQUEST message and the PLMN ID included in the new location area identifier information element identifies a CS domain operator, the VLR shall select the serving CS domain operator as specified in the new location area identifier information element;
  • Otherwise, the VLR selects the serving CS domain operator based on local policies.
Up

5.2.3.2  Location update responsep. 27

If the location update is accepted by the VLR and, if necessary, by the HSS, the VLR shall:
  • move the SGs association to the SGs-ASSOCIATED state;
  • set the "Confirmed by Radio Contact" restoration indicator to "true";
  • update the SGs association by storing the MME address included in SGsAP-LOCATION-UPDATE-REQUEST message; and
  • send an SGsAP-LOCATION-UPDATE-ACCEPT message to the sending MME. This message includes the location area identifier received in the New location area identifier information element in the previous SGsAP-LOCATION-UPDATE-REQUEST message.
After the VLR has updated the SGs association, if Ts5 is still running for a MT service for this UE, the VLR shall repeat SGs Paging Request towards the updated SGs association.
Up

5.2.3.3  Location update failurep. 28

If the location update is rejected by the VLR, the VLR shall:
  • send an SGsAP-LOCATION-UPDATE-REJECT message to the MME with the appropriate reject cause as indicated in TS 24.008 and shall indicate to the MME the Location area identifier received in the corresponding SGsAP-LOCATION-UPDATE-REQUEST message; and
  • move the SGs association to SGs-NULL.

5.2.3.4  TMSI reallocation procedurep. 28

If the VLR decides to allocate a new TMSI to the UE, the VLR shall include the new TMSI in the SGsAP-LOCATION-UPDATE-ACCEPT message. After sending the SGsAP-LOCATION-UPDATE-ACCEPT message with a new TMSI the VLR shall start timer Ts6-2. If the VLR decides to deallocate the TMSI of the UE, the VLR shall include the IMSI of the UE in the SGsAP-LOCATION-UPDATE-ACCEPT message.
Upon receipt of the SGsAP-TMSI-REALLOCATION-COMPLETE message, the VLR shall stop the timer Ts6-2 and consider the new TMSI as valid.
If the IMSI was sent to the UE, the VLR considers the old TMSI if available, as deleted.
If no SGsAP-TMSI-REALLOCATION-COMPLETE message is received by the VLR before the timer Ts6-2 expires, the VLR shall abort the TMSI reallocation procedure. The VLR shall consider the old TMSI if available, occupied until the new TMSI is used in a subsequent A/Iu message, or for an implementation dependent time. The outcome of the TMSI reallocation procedure does not change the state of the SGs association. The VLR uses the IMSI or a TMSI, either the new TMSI or the old TMSI if available, for paging.
Up

5.2.3.5  Abnormal casesp. 28

The following abnormal cases can be identified:
  1. MM signalling via A or Iu interface
    If the VLR receives a Location Update request or an IMSI detach indication from the UE by the A or Iu interface when the state of the SGs association in the VLR is not SGs-NULL, the VLR shall move the state of the SGs association to SGs-NULL.
  2. Additional Location Update Request
    If the state of the SGs association in the VLR is LA-UPDATE PRESENT and an SGsAP-LOCATION-UPDATE-REQUEST message is received, then:
    • if the message is from the same MME and indicates the same New location area identifier information element as the outstanding location update request, then the VLR shall ignore this additional SGsAP-LOCATION-UPDATE-REQUEST message;
    • if the message is from the same MME but indicates a different New location area identifier information element to the outstanding location update request, then the VLR shall treat this additional SGsAP-LOCATION-UPDATE-REQUEST message and the VLR shall not send any response to the previous SGsAP-LOCATION-UPDATE-REQUEST message; or
    • if the message is from a different MME (indicating either the same or different New location area identifier information element) to the outstanding location update request, then the VLR shall treat this additional SGsAP-LOCATION-UPDATE-REQUEST message and the VLR shall not send any response to the previous SGsAP-LOCATION-UPDATE-REQUEST message.
  3. Detach signalling from the MME
    If the state of the SGs association in the VLR is LA-UPDATE PRESENT and either an SGsAP-EPS-DETACH-INDICATION or an SGsAP-IMSI-DETACH-INDICATION message is received, then the VLR shall abandon the Location Update for non-EPS services procedure (neither an SGsAP-LOCATION-UPDATE-ACCEPT nor an SGsAP-LOCATION-UPDATE-REJECT messages is sent) and the further actions described in subclause 5.4 or subclause 5.5 or subclause 5.6 are followed.
  4. Signalling via Gs interface
    If the VLR receives for a UE a BSSAP+-LOCATION-UPDATE-REQUEST message (as defined in TS 29.018) from an SGSN when the state of the SGs association for this UE in the VLR is not SGs-NULL, the VLR shall move the state of the SGs association to SGs-NULL.
  5. New Location Update Request during TMSI reallocation procedure
    If the VLR receives an SGsAP-LOCATION-UPDATE-REQUEST message while Ts6-2 is running, the VLR shall stop timer Ts6-2, abort the TMSI reallocation procedure and proceed with the new location update for non-EPS services procedure. If the VLR needs to page the MS during the new location update for non-EPS services procedure, the VLR uses the IMSI or a TMSI, either the new TMSI from the aborted TMSI reallocation procedure or the old TMSI if available, for paging.
  6. Reset signalling from the MME
    If the state of the SGs association in the VLR is LA-UPDATE PRESENT and an SGsAP-RESET-INDICATION message is received from the MME, then the VLR shall abandon the Location Update for non-EPS services procedure (neither an SGsAP-LOCATION-UPDATE-ACCEPT nor an SGsAP-LOCATION-UPDATE-REJECT messages is sent) and the further actions described in subclause 5.8 are followed.
  7. Collision between A or Iu paging and Location Update Request
    If the VLR receives Location Update Request when A or Iu paging is ongoing, then the VLR may abort paging procedure over A or Iu interface and may initiate paging procedure over SGs interface after location updating procedure has successfully completed.
Up

5.3  Non-EPS alert procedurep. 29

5.3.1  General descriptionp. 29

This procedure is used by the VLR to request from an MME an indication when any signalling activity from the UE is detected. This procedure can be invoked at any time by the VLR. The MME shall acknowledge the SGsAP-ALERT-REQUEST message.

5.3.2  Procedures in the VLRp. 29

5.3.2.1  Alert Initiationp. 29

The VLR may start the Non-EPS alert procedure at any time. When the VLR wants to request from an MME that further activity from a UE is reported by the MME, the VLR shall send an SGsAP-ALERT-REQUEST message to that MME. The VLR starts timer Ts7 when the SGsAP-ALERT-REQUEST message is sent.

5.3.2.2  Alert Responsep. 29

When an SGsAP-ALERT-ACK message is received, the VLR shall stop the timer Ts7. The state of the SGs association is not changed.

5.3.2.3  Alert Failurep. 30

If an SGsAP-ALERT-REJECT message is received, the VLR shall stop the timer Ts7, move the state of the SGs association to SGs-NULL and within this state the SGs association is marked with the contents of the SGs cause information element.

5.3.2.4  Alert Indicationp. 30

The VLR shall not change the state of the SGs association upon reception of an SGsAP-UE-ACTIVITY-INDICATION message.
For Deployment Option 2 (see subclause 8.2.4a.1 of TS 23.272), if the SGsAP-UE-ACTIVITY-INDICATION message includes the Maximum UE Availability Time IE and the MNRF flag is set in the VLR, the VLR may forward the Maximum UE Availability Time IE to the HLR as defined in TS 29.002.
Up

5.3.2.5  Abnormal casesp. 30

If no SGsAP-ALERT-ACK message is received before the timer Ts7 expires, the VLR shall retransmit the SGsAP-ALERT-REQUEST message a maximum of Ns7 times.

5.3.3  Procedures in the MMEp. 30

5.3.3.1  Alert responsep. 30

The MME may receive an SGsAP-ALERT-REQUEST message in any state of the SGs association. Upon receipt of an SGsAP-ALERT-REQUEST message from the VLR and if the IMSI is known in the MME, the MME shall reply with an SGsAP-ALERT-ACK message and set the NEAF. If the MME has activated Idle mode Signaling Reduction for the UE, the MME shall send an Alert MME Notification message to the associated SGSN, as described in TS 29.274, except for the conditions specified in subclause 8.2.5c of TS 23.272.
Up

5.3.3.2  Alert failurep. 30

If an SGsAP-ALERT-REQUEST message is received for an IMSI that is unknown at the MME, the MME shall return an SGsAP-ALERT-REJECT message to the VLR indicating the SGs cause information element value "IMSI unknown".

5.3.3.3  Alert indicationp. 30

The MME shall report to the VLR upon detection of any activity in E-UTRAN (either signalling or, indirectly detected via S-GW, data transfer) from the UE if the NEAF is set. If the MME detects EPS signalling that leads to a procedure towards the VLR, the MME shall follow this procedure and reset the NEAF. If the MME detects activity that does not lead to any procedure towards the VLR, the MME shall send an SGsAP-UE-ACTIVITY-INDICATION message towards the VLR and reset the NEAF. Upon receipt of a UE Activity Notification message from the SGSN, the MME shall reply with a UE Activity Acknowledge message, send an SGsAP-UE-ACTIVITY-INDICATION message to the VLR and reset the NEAF flag.
For Deployment Option 2 (see subclause 8.2.4a.1 of TS 23.272), if the UE is using eDRX, the MME may include the Maximum UE Availability Time IE in the SGsAP-UE-ACTIVITY-INDICATION message.
Up

Up   Top   ToC