5.7. (274) Abort-Session-Request / Answer (ASR and ASA):
§ A Diameter server may request that the access device stop providing service for a particular session by issuing an Abort-Session-Request (via ASR).
§ If the access device does stop the session upon receipt of an ASR, it (access device) issues an STR to the authorizing server (which may or may not be the agent issuing the ASR) just as it would if the session were terminated for any other reason.
§ The Abort-Session-Request (ASR) may be sent by any server to the access device that is providing session service, to request that the session identified by the Session-Id be stopped.
§ If the session identified by Session-Id in the ASR was successfully terminated, Result-Code is set to DIAMETER_SUCCESS.
§ The Abort-Session-Request (ASR) message may be sent by any server to the NAS providing session service, to request that the session identified by the Session-Id be stopped.
(For External PDN or other network)
1. Gi Between GGSN and Diameter Server for External PDN or other network
Server-Initiated PDP context termination (via ASR)
§ Diameter is used as the protocol between the GGSN and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to GPRS user session. However some IP applications could need to interwork with the GGSN to terminate a particular PDP context.
§ For this purpose, the Diameter server or proxy may send a Diameter ASR to the GGSN along with the NSAPI necessary to identify the particular PDP context to be terminated.
2. SGi Between EPS/P-GW and Diameter Server for External PDN or other network
Server-Initiated Bearer termination (via ASR)
§ For P-GW, the ASR command is sent by the Diameter server to the P-GW to request that the EPS bearer identified by the 3GPP-NSAPI AVP is to be terminated.
§ Diameter is used as the protocol between the P-GW and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to the user session.
§ For this purpose, the Diameter server or proxy may send a Diameter ASR along with the EPS bearer ID, if available, to identify the particular bearer to be terminated to the P-GW . The P-GW should react by deleting the corresponding bearer.
(In MBMS)
1. Gmb for Between BM-SC and GGSN or SGmb for Between eBM-SC and MBMS-GW
De-registration procedure (BM-SC initiated) (via ASR)
§ This MBMS de-registration procedure is initiated by BM-SC when the specific multicast MBMS bearer service is terminated.
§ The BM-SC sends a ASR message to all GGSNs contained in the
§ The GGSN returns a ASA message to the BM-SC.
BM-SC in the home PLMN initiated multicast service deactivation
§ The BM-SC in home PLMN sends an ASR Message to the BM-SC in visited PLMN, indicating that the UE shall be removed from a specific multicast service.
§ The session to be terminated is uniquely identified by the Diameter session-id.
(In PCC)
Bearer Release (thru either ASR/STR or RAR)
§ If the CRF (or PCRF) needs to notify the AF for (session abortion) all IP flows of an AF session, the CRF (or PCRF) shall send a Diameter AS-Request (ASR).
§ The AF will terminate the corresponding Diameter session at the Rx interface using a Diameter ST-Request (STR).
Further Description:
§ The CRF (or PCRF) indicates the session abortion to the AF by sending a Diameter ASR message to the AF. The ASR command is sent by the PCRF to inform the AF that bearer for the established session is no longer available.
§ The AF responds by sending a Diameter ASA message to the CRF.
§ The AF will terminate the corresponding Diameter session at the Rx interface using a Diameter ST-Request (STR). The AF sends a Diameter STR message to the CRF (or PCRF) to indicate that the session has been terminated.
§ The CRF (or PCRF) responds by sending a Diameter STA message to the AF.
(In WLAN)
1. Wa Between AAA-Server and WLAN AN
Immediate Purging of a User from WLAN access
§ This procedure is used to communicate between the WLAN AN and the 3GPP AAA Proxy that the 3GPP AAA Server has decided that a specific WLAN-UE shall be disconnected from accessing the WLAN interworking service.
§ The procedure is Diameter (ASR Message) or RADIUS (Disconnect Message specified in RFC 3576) based.
2. Wd Between AAA-Server and AAA-Proxy
Immediate Purging of a User from WLAN access
§ This procedure is used to communicate between the 3GPP AAA Proxy and the 3GPP AAA Server that the 3GPP AAA Server has decided that a specific WLAN-UE shall be disconnected from accessing the WLAN interworking service.
§ The procedure is Diameter (ASR message) or RADIUS (Disconnect-Request message) based.
3. Wm Between AAA-Server and PDG
3GPP AAA Server Initiated Tunnel Disconnect Procedure
§ The Wm reference point performs the disconnection of user tunnel initiated by the 3GPP AAA Server based on the use of the RFC 3588 (ASR/ASA) commands.
§ This procedure is used between the 3GPP AAA Server and the PDG.
§ It is invoked by the 3GPP AAA Server when the WLAN subscription for the user has been deleted/prohibited in the 3GPP AAA Server or if the particular session must be terminated for any reason and the PDG must be updated with respect to these changes.
4. Wg Between AAA-Server/-Proxy and WAG
Routing Policy Cancellation Procedure
§ This procedure is used between the 3GPP AAA Server and the WAG.
§ It is invoked by the 3GPP AAA Server when the session specific routing policy should be removed from the WAG.
§ The Wg reference point performs the routing policy cancellation procedure based on the use of RFC 3588 ASR/ASA commands.
§ In the roaming case where the PDG is in the VPLMN, the 3GPP AAA Proxy shall perform the functions described for the 3GPP AAA Server
5. Pr Between the 3GPP AAA Server and the PNA
W-APN De-Activation Indication
§ Pr reference point shall enable an indication of the W-APN Deactivation to the PNA.
§ This procedure is used between the 3GPP AAA Server and the PNA.
§ The procedure of W-APN Deactivation indication is invoked by the 3GPP AAA Server when a particular W-APN is deactivated via ASR message.
(In EPS/AAA)
1. SWa Between AAA Server/Proxy and Untrusted Non-3GPP IP Access
§ SWa for HSS/AAA Initiated Detach (via ASR/STR) is same as STa
2. STa Between AAA Server/Proxy and Trusted Non-3GPP IP Access
§ The Abort-Session-Request (ASR) command is sent from a 3GPP AAA Server/Proxy to a non-3GPP access network NAS.
STa for HSS/AAA Initiated Detach (via ASR/AAR)
§ This procedure is used to communicate between the 3GPP AAA/HSS and the the trusted non-3GPP access network to indicate that the 3GPP AAA/HSS has decided that a specific UE shall be detached from accessing the EPC (via ASR message).
3. SWd between 3GPP AAA Proxy and 3GPP AAA Server
§ SWd for HSS/AAA Initiated Detach for Trusted non-3GPP Access is same as STa (via ASR)
§ SWd for Commands used in connection with the SWm interface : (via DER/AAR, ASR/STR, RAR/RAA)
§ SWd for Commands used in connection with the S6b interface : (via DER/AAR, ASR/STR, RAR/RAA)
4. SWm between 3GPP AAA Server/Proxy and ePDG
3GPP AAA Server Initiated Session Termination Procedures (via ASR/STR)
§ The Abort-Session-Request (ASR) command shall be sent from a 3GPP AAA Server/Proxy to an ePDG.
§ The SWm reference point shall allow the 3GPP AAA Server to request the termination of an IKE_SA between UE and ePDG through 3GPP AAA Proxy via ASR, and therefore the termination of all mobility session established for all associated PDN connections.
§ If the user has several accesses (IKE_SA) active at an ePDG, a separate Session Termination procedure shall be initiated for each of them.
§ When the 3GPP AAA Proxy receives the ASR from the 3GPP AAA Server it shall route the request to the ePDG.
§ When the 3GPP AAA Proxy receives the STR from ePDG, it shall route the request to the 3GPP AAA Server. On receipt of the STA message, the 3GPP AAA Proxy shall route the response to the ePDG.
5. S6b between 3GPP AAA Server/Proxy and PDN GW
§ The S6b reference point allows the 3GPP AAA server to order a PDN GW to remove a PDN connection previously activated by the UE.
§ The Abort-Session-Request (ASR) command is sent from a 3GPP AAA Server/Proxy to a PDN GW
3GPP AAA Initiated Session Termination Procedures (via ASR/STR)
§ This procedure shall be initiated by the 3GPP AAA server.
§ This indicates to the PDN GW to remove the corresponding PDN connection (identified by Session-ID AVP and User-Name AVP).
§ On receipt of the Abort Session Answer (ASA) message from the PDN GW, the 3GPP AAA Proxy shall route the message to the 3GPP AAA Server, and it shall release any local resources.
§ When the 3GPP AAA Proxy receives the STR from PDN GW, it shall route the request to the 3GPP AAA Server.
§ On receipt of the STA message, the 3GPP AAA Proxy shall route the response to the PDN GW
(For 3GPP Charging)
1. (DCCA in 32.299) between IMS Nodes and OCS
§ The OCF may determine that a service requires termination.
§ If the OCF does not have a pending request (asynchronous), the OCF may trigger an ASR to terminate the Diameter session related to the service.
§ On reception of an ASR, the CTF shall close the associated Credit-Control session by sending a CCR [TERMINATE].
§ As an alternative to the ASR, the OCF may trigger a RAR to which the CTF behaves as described in RFC 4006 and the OCF shall return a CCA with Result-Code AVP with value DIAMETER-AUTHORIZATION-REJECTED for the resulting CCR.
5.8. (275) Session-Termination-Request / Answer (STR and STA):
§ The Session-Termination-Request (STR) is sent by the access device to inform the Diameter Server that an authenticated and/or authorized session is being terminated.
§ An STR MUST be issued when a user session terminates for any reason, including user logoff, expiration of Session-Timeout, administrative action, termination upon receipt of an Abort-Session-Request (see below), orderly shutdown of the access device, etc.
§ When a user session that required Diameter authorization terminates, the access device that provided the service MUST issue a Session-Termination-Request (STR) message to the Diameter server that authorized the service, to notify it that the session is no longer active.
§ A Diameter server that receives an STR message MUST clean up resources (e.g., session state) associated with the Session-Id specified in the STR, and returns a STA.
§ When a NAS receives an indication that a user's session is being disconnected by the client or an administrative command, the NAS MUST issue a Session-Termination-Request (STR) to its Diameter Server.
§ This will ensure that any resources maintained on the servers are freed appropriately.
§ The Session-Termination-Request (STR) message is sent by the NAS to inform the Diameter Server that an authenticated and/or authorized session is being terminated.
(For External PDN or other network)
1. Gi Between GGSN and Diameter Server for External PDN or other network
§ The STR command is sent by the GGSN to the Diameter server via Gi to terminate a DIAMETER session corresponding to an IP-CAN session of a certain user.
§ The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Answer ACA (STOP) message from the Diameter server.
§ If this was the last PDP context for that PDP address, the GGSN shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber.
2. SGi Between EPS/P-GW and Diameter Server for External PDN or other network
§ The STR command is sent by the P-GW to the Diameter server via SGi to terminate a DIAMETER session corresponding to an IP-CAN session of a certain user.
§ P-GW shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular bearer or user session.
§ The P-GW shall immediately send the corresponding response (e.g. Delete Bearer Request or Proxy Binding Ack with lifetime equal 0) to the peer node (e.g. S-GW) in the Packet Domain, without waiting for an Accounting-Answer ACA (STOP) message from the Diameter server.
§ If the last bearer of an IP-CAN session is deactivated, the P-GW shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IPv4 address and/or IPv6 prefix (if any) initially allocated to the subscriber.
(For MBMS)
1. Gmb Between BM-SC and GGSN or SGmb for Between eBM-SC and MBMS-GW
§ The STR command is sent by the GGSN to the BM-SC to terminate a DIAMETER session
§ A DIAMETER session for a multicast MBMS service is terminated when the last MBMS UE context for the MBMS bearer service is deleted. This informs the BM-SC that the GGSN would like to be deleted from the distribution tree of a particular MBMS bearer service (De-registration procedure).
§ A DIAMETER session for an individual UE’s multicast MBMS service authorization is terminated when the UE has requested to the GGSN to leave the MBMS bearer service.
§ A DIAMETER session for a broadcast MBMS service may be terminated by the GGSN in exceptional cases.
§ The STR command is also used to deactivate a Trace Session previously activated in the BM-SC and to terminate the associated Diameter Session initiated by the
De-registration procedure (GGSN initiated) (via STR)
§ The GGSN informs the BM-SC that it does not need to receive signalling, session attributes and data for a particular multicast MBMS bearer service anymore and therefore would like to be removed from the corresponding distribution tree.
§ When the
§ The BM-SC removes the identifier of the GGSN from the
Service deactivation (via STR)
§ The multicast service deactivation is a signalling procedure that will terminate the user registration to a particular MBMS multicast service. The multicast service deactivation can be initiated by the GGSN, when indicated so by the UE, or by the BM-SC, for service specific reasons.
§ The UE sends an IGMP (IPv4) or MLD (IPv6) Leave message over the default PDP context to leave a particular multicast service identified by an IP multicast address.
§ The GGSN sends a STR to the BM-SC, indicating that the UE is requesting to leave the multicast service. The session to be terminated is uniquely identified by the Diameter session-id.
§ Upon reception of the STR, the BM-SC verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends a STA to the GGSN that originated the Leave Indication. The APN shall be the same that was provided during service activation (see
§ Upon reception of the STA the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN.
Trace Session Deactivation procedure (via STR)
§ The Trace Session Deactivation procedure occurs when the GGSN indicates to the BM-SC that a Trace Session, previously activated, needs to be deactivated via STR message.
§ When the GGSN has received a Trace Deactivation message from the SGSN, in a Create MBMS Context Request/Update MBMS Context Request, that requires the deactivation of a Trace Session in the BM-SC, the GGSN sends a STR message (containing the Additional MBMS Trace Info AVP) to deactivate a trace session in the BM-SC and to tear down the corresponding Diameter Session previously established to activate the Trace Session
MBMS broadcast session termination (GGSN initiated)
§ In exceptional cases (e.g. resource pre-emption or timeout of the MBMS session), the GGSN may send an STR command to the BM-SC to initiate the termination of the Diameter session related to a broadcast MBMS bearer service. If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released.
§ The BM-SC removes the Diameter session and confirms the operation by sending an STA message to the GGSN.
Service deactivation - Service Provided by the BM-SC in home PLMN
§ Upon receiving the leave indication, the GGSN sends an STR to the BM-SC in visited PLMN, indicating that the roaming UE is requesting to leave the multicast service. The session to be terminated is uniquely identified by the Diameter session-id.
§ Upon reception of the STR, the BM-SC in visited PLMN finds the BM-SC in home PLMN which serves the roaming UE, and sends an STR to it for the roaming UE to deactivate a particular service.
§ The GGSN which is used to establish the MBMS bearer service deletes the MBMS UE Context and sends another STR to the BM-SC in home PLMN to confirm the successful deactivation of the MBMS UE Context.
§ The BM-SC in home PLMN then, deletes the MBMS UE Context and sends a confirmation to the GGSN in an STA message.
Service deactivation - Service Provided by the BM-SC in visited PLMN
§ Upon receiving the leave indication, the GGSN sends an STR to the BM-SC in visited PLMN, indicating that the roaming UE is requesting to leave the multicast service. The session to be terminated is uniquely identified by the Diameter session-id.
§ Upon reception of the STR, the BM-SC in visited PLMN verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends an STR to the BM-SC in home PLMN.
§ The BM-SC in home PLMN responds the BM-SC in visited PLMN with an ST-Answer.
§ Upon reception of the STA, the BM-SC in visited PLMN sends an STA to the GGSN that orignated the Leave Indication. The APN shall be the same that was provided during service activation.
§ The GGSN deletes the MBMS UE Context and sends an STR to the BM-SC in visited PLMN to confirm the successful deactivation of the MBMS UE Context.
(In PCC)
Bearer Release (thru either ASR/STR or RAR)
§ The ASR command is sent by the PCRF to inform the AF that bearer for the established session is no longer available.
§ If the CRF (or PCRF) needs to notify the AF for all IP flows of an AF session, the CRF (or PCRF) shall send a Diameter AS-Request (ASR). The AF will terminate the corresponding Diameter session at the Rx interface using a Diameter ST-Request (STR).
§ The CRF (or PCRF) indicates the session abort to the AF by sending a Diameter ASR message to the AF.
§ The AF responds by sending a Diameter ASA message to the CRF.
§ The AF sends a Diameter STR message to the CRF (or PCRF) to indicate that the session has been terminated.
§ The CRF (or PCRF) responds and acknowledges the termination of the session by sending an STA message to the AF.
AF Session Termination (via STR)
§ When an AF session is terminated, the AF shall send a Session-Termination-Request (STR) command to the PCRF.
§ When the PCRF receives a ST-Request from the AF, indicating an AF session termination, it shall acknowledge that request by sending a ST-Answer (STA) to the AF.
§ Afterwards, it shall free the resources allocated for the corresponding Service Data Flow(s). In order to do that, the PCRF shall initiate the request for the removal of any related PCC/QoS rules from the PCEF/BBERF and for the update of the Authorized QoS.
(In WLAN)
1. Wa Between AAA-Server/Proxy --- WLAN AN
Ending a Session (via STR)
§ Session termination is initiated when the WLAN-AN needs to inform the 3GPP AAA Server of the WLAN-UEs disconnection from the hot-spot via STR/STA messages.
2. Wd Between AAA-Server --- AAA-Proxy
Ending a Session (via STR)
§ Session termination occurs when a user de-registers from the 3GPP AAA Server in Wd (same as Wa).
3. Wm Between AAA-Server --- PDG
PDG Initiated Session Termination Procedure (via STR)
§ This procedure is used between the PDG and the 3GPP AAA Server.
§ It is invoked by the PDG when the user's tunnel associated with the W-APN has been disconnected.
§ Where the user has several active accesses (IKE_SA), a separate Session Termination procedure shall be initiated for each access.
§ In the roaming case, the 3GPP AAA Proxy shall forward the STR message to the 3GPP AAA Server.
4. Wg between AAA-Server/-Proxy and WAG
WAG Initiated Routing Policy Cancellation Procedure (via STR)
§ This procedure is used between the WAG and the 3GPP AAA Server.
§ It is invoked by the WAG in the case whereby the session specific routing policy has been removed from the WAG and this action has not been preceded by any
§ The Wg reference point performs the routing policy cancellation procedure based on the use of RFC 3588 Session Termination Request/ Answer (STR/STA) commands.
§ In the roaming case where the PDG is in the VPLMN, the 3GPP AAA Proxy shall perform the functions described below for the 3GPP AAA Server
(In EPS/AAA)
1. SWa Between AAA Server/Proxy and Untrusted Non-3GPP IP Access
§ SWa for Non-3GPP Access Network Initiated Detach is same as STa as next
2. STa Between AAA Server/Proxy and Trusted Non-3GPP IP Access
§ Non-3GPP IP Access Network Initiated Session Termination (via STR)
§ The STa reference point allows the non-3GPP access network to inform the 3GPP AAA server that the session resources of the non-3GPP access network assigned to a given user are being released.
§ The procedure shall be initiated by the non-3GPP access network and removes non-3GPP access information from the 3GPP AAA Server.
3. SWd between 3GPP AAA Proxy and 3GPP AAA Server
§ Same as STa HSS/AAA Initiated Detach for Trusted non-3GPP Access via ASR/STR
§ Same as STa Trusted non-3GPP IP Access network Initiated Session Termination via STR
4. SWm Between AAA-Server/Proxy and ePDG
ePDG Initiated Session Termination Procedures (via STR)
§ The SWm reference point allows the ePDG to inform the 3GPP AAA Server/Proxy about the termination of an IKE_SA between UE and ePDG, and that therefore the mobility session established on the ePDG for all associated PDN connections are to be removed.
§ The SWm Session Termination Request procedure shall be initiated by the ePDG to the 3GPP AAA Server which shall remove associated non-3GPP Access information.
3GPP AAA Server Initiated Session Termination Procedures (via ASR & STR) - N/A
5. S6b Between the 3GPP AAA Server and the PDN-GW
PDN GW Initiated Session Termination Procedures (via STR)
§ The S6b reference point allows the PDN GW to inform the 3GPP AAA server that the UE disconnected a PDN connection associated to an APN, and therefore the mobility session established for this PDN connection is to be removed.
§ The procedure shall be initiated by the PDN GW and removes PDN GW information from the 3GPP AAA server.
3GPP AAA Server Initiated Session Termination Procedures (via ASR & STR) - N/A
沒有留言:
張貼留言