Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map

3GPP Glossaries:  Interfaces / Reference Points
for letter 'S' (2 of 6)

 

S3   (GTPv2-C)

Up       Top

between  MME
and  S4-SGSN

see it   here

specified from  Rel-8  in
TS 23.401, clause 5.1.1.4
TS 29.274 

This interface enables user and bearer information exchange for inter-3GPP access network mobility in idle and/or active state.
  • Mobility Management Messages (TS 29.274, clause 7.3)
    • Forward Relocation Request/Response
    • Forward Relocation Complete Notification/Acknowledge
    • Context Request/Response/Acknowledge
    • Identification Request/Response
    • Forward Access Context Notification/Acknowledge
    • Detach Notification/Acknowledge
    • Relocation Cancel Request/Response
    • Configuration Transfer Tunnel
    • RAN Information Relay
    • ISR Status Indication
    • UE Registration Query Request/Response
  • CS Fallback and SRVCC related messages (TS 29.274, clause 7.4)
    • Suspend Notification/Acknowledge (from SGSN to MME)
    • CS Paging Indication
    • Alert MME Notification/Acknowledge
    • UE Activity Notification/Acknowledge


S4   (GTPv2-C and GTPv1-U)

Up       Top

between  S-GW
and  S4-SGSN

see it   here

specified from  Rel-8  in
TS 23.401, clause 5.1.1.5
clause 5.1.2.3
clause 5.1.2.5
TS 29.274
.281 

This interface provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.
  • Tunnel Management Messages (TS 29.274, clause 7.2)
    • Create Session Request/Response (from SGSN to P-GW via S-GW)
    • Create Bearer Request/Response (from P-GW to SGSN via S-GW)
    • Bearer Resource Command (from SGSN to P-GW via S-GW)
    • Bearer Resource Failure Indication (from P-GW to SGSN via S-GW)
    • Modify Bearer Request/Response (from SGSN to P-GW via S-GW)
    • Delete Session Request/Response (from SGSN to P-GW via S-GW)
    • Delete Bearer Request/Response (from P-GW to SGSN via S-GW)
    • Downlink Data Notification/Notification-Acknowledge (from S-GW to SGSN)
    • Downlink Data Notification Failure Indication (from SGSN to S-GW)
    • Delete Indirect Data Forwarding Tunnel Request/Response (from SGSN to S-GW)
    • Modify Bearer Command (from SGSN to P-GW via S-GW)
    • Modify Bearer Failure Indication (from P-GW to SGSN via S-GW)
    • Update Bearer Request/Response (from P-GW to SGSN via S-GW)
    • Delete Bearer Command (from SGSN to P-GW via S-GW)
    • Delete Bearer Failure Indication (from P-GW to SGSN via S-GW)
    • Create Indirect Data Forwarding Tunnel Request/Response (from SGSN to S-GW)
    • Release Access Bearers Request/Response (from SGSN to S-GW)
    • Stop Paging Indication (from S-GW to SGSN)
  • Mobility Management Messages (TS 29.274, clause 7.3)
    • Change Notification Request/Response (from SGSN to P-GW via S-GW)
  • CS Fallback and SRVCC related messages (TS 29.274, clause 7.4)
    • Suspend Notification/Acknowledge (from SGSN to S-GW)
    • Resume Notification/Acknowledge (from SGSN to P-GW via S-GW)
  • Non-3GPP access related messages (TS 29.274, clause 7.5)
    • Create Forwarding Tunnel Request/Response (from SGSN to S-GW)
  • Restoration and Recovery (TS 29.274, clause 7.9)
    • PGW Restart Notification/Notification-Acknowledge (from S-GW to SGSN)
    • PGW Downlink Triggering Notification/Acknowledge (from P-GW to SGSN via S-GW)
  • Trace Management Messages (TS 29.274, clause 7.12)
    • Trace Session Activation (from SGSN to P-GW via S-GW)
    • Trace Session Deactivation (from SGSN to P-GW via S-GW)


S5/S8   (GTPv2-C or PMIPv6, GTPv1U)

Up       Top

between  S-GW
and  PDN-GW

see it   here

specified from  Rel-8  in
TS 23.401, clause 5.1.1.6
clause 5.1.2.1
TS 29.274
.275
.281 

These interfaces provide support for functions for packet data services towards end users during roaming and non-roaming cases (i.e. S8 is the inter PLMN variant of S5).
  • GTPv2-C Tunnel Management Messages (TS 29.274, clause 7.2)
    • Create Session Request/Response (from MME to P-GW via S-GW)
    • Create Bearer Request/Response (from P-GW to MME via S-GW)
    • Bearer Resource Command (from MME to P-GW via S-GW)
    • Bearer Resource Failure Indication (from P-GW to MME via S-GW)
    • Modify Bearer Request/Response (from MME to P-GW via S-GW)
    • Delete Session Request/Response (from MME to P-GW via S-GW)
    • Delete Bearer Request/Response (from P-GW to MME via S-GW)
    • Modify Bearer Command (from MME to P-GW via S-GW)
    • Modify Bearer Failure Indication (from P-GW to MME via S-GW)
    • Update Bearer Request/Response (from P-GW to MME via S-GW)
    • Delete Bearer Command (from MME to P-GW via S-GW)
    • Delete Bearer Failure Indication (from P-GW to MME via S-GW)
    • Remote UE Report Notification/Acknowledge (from MME to P-GW via S-GW)
  • GTPv2-C Mobility Management Messages (TS 29.274, clause 7.3)
    • Change Notification Request/Response (from MME to P-GW via S-GW)
  • GTPv2-C CS Fallback and SRVCC related messages (TS 29.274, clause 7.4)
    • Suspend Notification/Acknowledge (from S-GW to P-GW)
    • Resume Notification/Acknowledge (from MME to P-GW via S-GW)
  • GTPv2-C Restoration and Recovery (TS 29.274, clause 7.9)
    • Delete PDN Connection Set Request/Response (between MME and P-GW, via S-GW)
    • Update PDN Connection Set Request/Response (between S-GW and P-GW)
    • PGW Downlink Triggering Notification/Acknowledge (from P-GW to MME via S-GW)   for S5 only
  • GTPv2-C Trace Management Messages (TS 29.274, clause 7.12)
    • Trace Session Activation (from MME to P-GW via S-GW)
    • Trace Session Deactivation (from MME to P-GW via S-GW)


S6a   (Diameter)

Up       Top

between  MME
and  HSS

see it   here  and  here

specified from  Rel-8  in
TS 23.401, clause 5.1.1.9
TS 29.272, clause 5 

This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The MME informs the HSS of the location of a mobile station managed by the latter. The HSS sends to the MME all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.

Commands:
  • ULR/ULA:  Update-Location-Request/Answer
  • CLR/CLA:  Cancel-Location-Request/Answer
  • PUR/PUA:  Purge-UE-Request/Answer
  • IDR/IDA:  Insert-Subscriber-Data-Request/Answer
  • DSR/DSA:  Delete-Subscriber-Data-Request/Answer
  • AIR/AIA:  Authentication-Information-Request/Answer
  • RSR/RSA:  Reset-Request/Answer
  • NOR/NOA:  Notify-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S6b   (Diameter)

Up       Top

between  PDN-GW
and  3GPP AAA Server / Proxy

see it   here  and  here

specified from  Rel-8  in
TS 23.402, clause 4.4
TS 29.273, clause 9 

This reference point is used for mobility related authentication and authorization. It may also be used to retrieve and request storage of mobility parameters, such as the PDN GW Identity. It may also be used to retrieve static QoS profile for a UE for non-3GPP access in case dynamic PCC is not supported.

Commands:
  • DER/DEA:  Diameter-EAP-Request/Answer
  • AAR/AAA:  AA-Request/Answer
  • STR/STA:  Session-Termination-Request/Answer
  • ASR/ASA:  Abort-Session-Request/Answer
  • RAR/RAA:  Re-Auth-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S6c   (Diameter)

Up       Top

between  HSS
and  SMS-GMSC / SMS-IWMSC

specified from  Rel-11  in
TS 23.272, annex C
TS 29.338, clause 5 

S6c is used to interrogate the HSS of the required subscriber to obtain routing information for a short message directed to that subscriber.

Commands:
  • SRR/SRA:  Send-Routing-Info-for-SM-Request/Answer
  • ALR/ALA:  Alert-Service-Centre-Request/Answer
  • RDR/RDA:  Report-SM-Delivery-Status-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S6d   (Diameter)

Up       Top

between  SGSN
and  HSS

see it   here  and  here

specified from  Rel-8  in
TS 23.060, clause 5.6.3.9
TS 29.272, clause 5 

This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The SGSN informs the HSS of the location of a mobile station managed by the latter. The HSS sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.

Commands:
  • ULR/ULA:  Update-Location-Request/Answer
  • CLR/CLA:  Cancel-Location-Request/Answer
  • PUR/PUA:  Purge-UE-Request/Answer
  • IDR/IDA:  Insert-Subscriber-Data-Request/Answer
  • DSR/DSA:  Delete-Subscriber-Data-Request/Answer
  • AIR/AIA:  Authentication-Information-Request/Answer
  • RSR/RSA:  Reset-Request/Answer
  • NOR/NOA:  Notify-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S6m   (Diameter)

Up       Top

between  MTC-IWF
and  HSS / HLR

see it   here

specified from  Rel-11  in
TS 23.682, clause 4.3.3.4
TS 29.336, clause 5 

The S6m reference point is used between the MTC-IWF and the HSS/HLR to authorize a certain SCS to request a specific service (e.g. device triggering), and to retrieve subscription information and routing information (i.e. serving SGSN/MME/MSC identities) from the HSS/HLR.

Commands:
  • SIR/SIA:  Subscriber-Information-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.



Up       Top       Next