Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map

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

 

S6n   (Diameter)

Up       Top

between  MTC-AAA
and  HSS / HLR

see it   here

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

This reference point is used between the MTC-AAA and the HSS/HLR to translate an IMSI to external identifier(s) of the user.

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.


S6t   (Diameter)

Up       Top

between  SCEF
and  HSS

see it   here

specified from  Rel-13  in
TS 23.682, clause 4.3.3.7
TS 29.336, clause 7 

The S6t reference point connects the SCEF with the HSS to perform configuration and reporting of Monitoring events, and configuration of AESE Communication Pattern. The S6t reference point shall shall allow the SCEF to:
  • configure UE related Monitoring events;
  • receive reporting of the configured Monitoring events from the HSS;
  • configure UE related AESE Communication Pattern;
  • Authorize the UE for NIDD.
Commands:
  • CIR/CIA:  Configuration-Information-Request/Answer
  • RIR/RIA:  Reporting-Information-Request/Answer
  • NIR/NIA:  NIDD-Information-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S7a   (Diameter)

Up       Top

between  CSS
and  MME

see it   here

specified from  Rel-11  in
TS 23.401, clause 5.1.1.12
TS 29.272, clause 5A 

This reference point is used to transfer to the MME the CSG subscription information stored in the VPLMN for roaming UEs.

Commands:
  • UVR/UVA:  Update-VCSG-Location-Request/Answer
  • CVR/CVA:  Cancel-VCSG-Location-Request/Answer
  • IDR/IDA:  Insert-Subscription-Data-Request/Answer
  • DSR/DSA:  Delete-Subscriber-Data-Request/Answer
  • RSR/RSA:  Reset-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S7d   (Diameter)

Up       Top

between  CSS
and  S4-SGSN

see it   here

specified from  Rel-11  in
TS 23.060, clause 5.6.3.11
TS 29.272, clause 5A 

This reference point is used to transfer to the S4-SGSN the CSG subscription information stored in the VPLMN for roaming UEs.

Commands:
  • UVR/UVA:  Update-VCSG-Location-Request/Answer
  • CVR/CVA:  Cancel-VCSG-Location-Request/Answer
  • IDR/IDA:  Insert-Subscription-Data-Request/Answer
  • DSR/DSA:  Delete-Subscriber-Data-Request/Answer
  • RSR/RSA:  Reset-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S8

Up       Top

between  Visited S-GW
and  Home PDN-GW

 

See  S5/S8.


S9   (Diameter)

Up       Top

between  H-PCRF
and  H-PCRF

specified from  Rel-8  in
TS 23.203, clause 5.2.6
TS 29.215 

For roaming with a visited access (PCEF and, if applicable, BBERF in the visited network), the S9 reference point enables the H-PCRF to (via the V-PCRF):
  • have dynamic PCC control, including the PCEF and, if applicable, BBERF, and, if applicable, TDF, in the VPLMN;
  • deliver or receive IP-CAN-specific parameters from both the PCEF and, if applicable, BBERF, in the VPLMN;
  • serve Rx authorizations and event subscriptions from an AF in the VPLMN;
  • receive application identifier, service data flow descriptions, if available, application instance identifiers, if available, and application detection start/stop event triggers report.
For roaming with a home routed access, the S9 enables the H-PCRF to provide dynamic QoS control policies from the HPLMN, via a V-PCRF, to a BBERF in the VPLMN.

Commands:
  • TER/TEA:  Trigger-Establishment-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


S9a   (Diameter)

Up       Top

between  BPCF
and  PCRF / V-PCRF

specified from  Rel-11  in
TS 23.203, annex P.4
TS 29.215, annex A 

This interface supports the transfer of (QoS) policy information from PCRF to BPCF of broadband access network. S9a is only applicable to the interworking with Fixed Broadband Access network.


S10   (GTPv2-C)

Up       Top

between  MME
and  MME

see it   here

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

This interface is used to support user information transfer and MME relocation support between the MMEs.
  • 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
    • Relocation Cancel Request/Response
    • Configuration Transfer Tunnel
    • RAN Information Relay


S11   (GTPv2-C)

Up       Top

between  MME
and  S-GW

see it   here

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

This interface is used to support mobility and bearer management between the MME and S-GW.
  • 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)
    • Downlink Data Notification/Notification-Acknowledge (from S-GW to MME)
    • Downlink Data Notification Failure Indication (from MME to S-GW)
    • Delete Indirect Data Forwarding Tunnel Request/Response (from MME to 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)
    • Create Indirect Data Forwarding Tunnel Request/Response (from MME to S-GW)
    • Release Access Bearers Request/Response (from MME to S-GW)
    • Stop Paging Indication (from S-GW to MME)
    • Modify Access Bearers Request/Response (from MME to S-GW)
    • Remote UE Report Notification/Acknowledge (from MME to P-GW via S-GW)
  • Mobility Management Messages (TS 29.274, clause 7.3)
    • Change Notification Request/Response (from MME to P-GW via S-GW)
  • CS Fallback and SRVCC related messages (TS 29.274, clause 7.4)
    • Suspend Notification/Acknowledge (from MME to S-GW)
    • Resume Notification/Acknowledge (from MME to P-GW via S-GW)
  • Non-3GPP access related messages (TS 29.274, clause 7.5)
    • Create Forwarding Tunnel Request/Response (from MME to S-GW)
  • Restoration and Recovery (TS 29.274, clause 7.9)
    • Delete PDN Connection Set Request/Response (between MME and P-GW, via S-GW)
    • PGW Restart Notification/Notification Acknowledge (from S-GW to MME)
    • PGW Downlink Triggering Notification/Acknowledge (from P-GW to MME via S-GW)
  • 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)


S11-U   (GTPv1-U)

Up       Top

between  MME
and  S-GW

specified from  Rel-13  in
TS 23.401, clause 5.1.2.6
clause 5.3.4B
TS 29.281 

This is used when Control Plane CIoT (Cellular Internet of Things) EPS Optimisation applies.


S12   (GTPv1-U)

Up       Top

between  S-GW
and  UTRAN

see it   here

specified from  Rel-8  in
TS 23.401, clause 5.1.2.4
TS 29.281 

It is used for user plane tunnelling when Direct Tunnel is established. It is based on the Iu-u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN or respectively between SGSN and GGSN. Usage of S12 is an operator configuration option.



Up       Top       Next