Uati has changed




Yüklə 12.13 Kb.
tarix30.04.2016
ölçüsü12.13 Kb.

1097.

ALU

4-12

01

4.1.1.4

T

The Cause Value=08H “UATI has changed” was never mentioned in section 3 when to use this value. Should it be removed?

QC to verify if should have been used.


        1. IAS-Session Information Update Response


The IAS-Session Information Update Response message is sent by the SRNC in response to the ANRI that sent an IAS-Session Information Update Request message to the SRNC. Refer to section Error: Reference source not found, IAS-Session Information Update Response, for the format and content of this message.
1.1.1.1.1Successful Operation

If the IAS-Session Information Update Request message is received from an ANRI in the route set by the SRNC, then the SRNC shall respond with an IAS-Session Information Update Response message with the fields in the message set as follows:

  • The AT Identity IE of the message shall be set to be the same as the AT Identity IE in the IAS-Session Information Update Request message;

  • The sender NW ID shall be set to the ANID of the SRNC and the receiver NW ID shall be set to the value of the sender NW ID field in the IAS-Session Information Update Request message;

  • If the Session Signature IE of the IAS-Session Information Update Request message contains the current session signature at the SRNC and the session is not locked, then the Cause IE of the IAS-Session Information Update Response message shall be set to ‘Successful event’ and the Session Signature IE of the IAS-Session Information Update Response shall be set to a new session signature for the AT. The SRNC shall store session information for the new session signature and await the confirmation from the AT either through the Session Updated message or the IAS-Session Information Request/IAS-SRNC Transfer Request message containing the new session signature. If the new session signature is never confirmed, the connection is lost and the subsequent access from the AT uses the old session signature, then the SRNC shall discard the new session signature and session information associated with the new session signature;

  • If the Session Signature IE of the IAS-Session Information Update Request message contains the current session signature at the SRNC but the session is locked, then the Cause IE of the IAS-Session Information Update Response message shall be set to ‘Requested session locked’ and the Session Signature IE of the IAS-Session Information Update Response shall be set to the current session signature for the AT.

  • If the Session Signature IE of the IAS-Session Information Update Request message does not contain the current session signature at the SRNC, then the Cause IE of the IAS-Session Information Update Response message shall be set to ‘Invalid session signature’ and the Session Signature IE of the IAS-Session Information Update Response shall be set to the current session signature for the AT at the SRNC.

Upon receipt of the IAS-Session Information Update Response message with ‘Successful event’ Cause IE, the receiving ANRI shall complete session configuration with the AT, i.e., by sending the new session signature included in the Session Signature IE in the IAS-Session Information Update Response message to the AT. The receiving ANRI also stops timer Tsur-ias corresponding to this message.

Upon receipt of the IAS-Session Information Update Response message with ‘Requested session locked’ Cause IE, the receiving ANRI stops timer Tsur-ias corresponding to this message and should wait until the new UATI for the AT is received before resending the IAS-Session Information Update Request message to the SRNC identified by the new UATI.



Upon receipt of the IAS-Session Information Update Response message with ‘Invalid session signature’ Cause IE, the ANRI shall abort session configuration with the AT. The receiving ANRI also stops timer Tsur-ias corresponding to this message. The receiving ANRI may send an IAS-Session Information Request message to the SRNC to retrieve session information using the updated session signature from the SRNC.
1.1.1.1.2Failure Operation

If an IAS-Session Information Update Request message is received with any of the following conditions

  • The AT Identity IE is invalid, i.e.g., the AT identity is not recognized;

  • tThe ANRI is not the session anchor ANRI for the AT identified in the message;

  • The sending ANRI is not in the Route Set of the AT or is not the DAP for the AT and Route Open Request IE is not included;

then the ANRI responds with an IAS-Session Information Update Response message with the fields in the message set as follows:

  • The AT Identity IE of the message shall be set to the AT Identity IE in the IAS-Session Information Request message;

  • The sender NW ID shall be set to the ANID of the SRNC and the receiver NW ID shall be set to the value of the sender NW ID field in the IAS-Session Information Update Request message;

  • The Cause IE shall be set to ‘Requested session not found’ if the AT Identity IE is invalid, to ‘UATI has changed’ if the ANRI is no longer the session anchor ANRI for the AT, or to ‘Requesting ANRI not in Route Set’ if the sending ANRI is not in the Route Set;

  • All of the other IEs shall be omitted.

Upon receipt of the IAS-Session Information Update Response message with ‘Requested session not found’ or ‘Requesting ANRI not in Route Set’ Cause IE, the ANRI shall close the route with the AT. The receiving ANRI also stops timer Tsur-ias corresponding to this message.

If the IAS-Session Information Update Request message is received by an ANRI that is not the Session Anchor ANRI for the AT, then it may silently discard the message.


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©azrefs.org 2016
rəhbərliyinə müraciət

    Ana səhifə