tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

3GPP Glossaries

|   Features_Services   |   Network_Entities   |   Reference_Points   |   SIM_UICC_Dir_Files   |   Identifiers   |

 

Interfaces / Reference Points

Y

 

 

 

Here          Top

|   S1‑MME   |   S1‑U   |   S2a   |   S2b   |   S2c   |   S3   |   S4   |   S5/S8   |   S6a   |   S6b   |   S6c   |   S6d   |   S6m   |   S6n   |   S6t   |   S7a   |   S7d   |   S8   |   S9   |   S9a   |   S10   |   S11   |   S11‑U   |   S12   |   S12   |   S13   |   S13'   |   S14   |   S15   |   S16   |   S101   |   S102   |   S103   |   S121   |   SBc   |   Sd   |   SGd   |   SGi   |   SGi‑mb   |   SGmb   |   SGs   |   Sh   |   Si   |   SLg   |   SLh   |   SLs   |   Sm   |   Sn   |   Sp   |   St   |   Sta   |   Sv   |   SWa   |   SWd   |   SWm   |   SWn   |   SWu   |   SWx   |   Sy   |

 


between  E-UTRAN  and  MME

specified from  Rel-8
in  TS 23.401, clause 5.1.1.2  and  TS 36.413 

S1-MME is the reference point for the control plane protocol between E-UTRAN and MME.

Up       Top


between  E-UTRAN  and  S-GW

specified from  Rel-8
in  TS 23.401, clause 5.1.2.2  and  TS 29.281 

S1-U is the reference point between E-UTRAN and S-GW for the per-bearer user plane tunnelling.

Up       Top


between  S-GW / P-GW  and  Trusted non-3GPP IP Access

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.10 

This interface provides the user plane with related control and mobility support. It is specified in TS 29.275 and TS 24.304 for PMIP and Client Mobile IPv4 FA mode respectively.

Up       Top


between  PDN-GW / S-GW  and  ePDG

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.11 

This interface provides the user plane with related control and mobility support. It is specified in TS 29.274 and in TS 29.275 for GTP and PMIP respectively.

Up       Top


between  PDN-GW  and  UE

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.12 

This interface provides the user plane with related control and mobility support. It is implemented over trusted and/or untrusted non-3GPP Access and/or 3GPP access. It is specified in TS 24.303.

Up       Top


between  MME  and  S4-SGSN

specified from  Rel-8
in  TS 23.401, clause 5.1.1.4  and  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

Up       Top


between  S-GW  and  S4-SGSN

specified from  Rel-8
in  TS 23.401, clause 5.1.1.5  and  TS 29.274  for Control Plane
in  TS 23.401, clauses 5.1.2.3, 5.1.2.5  and  TS 29.281  for User Plane 

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)

Up       Top


between  S-GW  and  PDN-GW

specified from  Rel-8
in  TS 23.401, clause 5.1.1.6  and  TS 29.274  or  TS 29.275  for Control Plane
in  TS 23.401, clause 5.1.2.1  and  TS 29.281  for User Plane 

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)

Up       Top


between  MME  and  HSS

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

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.

Up       Top


between  PDN-GW  and  3GPP AAA Server / Proxy

specified from  Rel-8
in  TS 23.402, clause 4.4  and  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.

Up       Top


between  HSS  and  SMS-GMSC / SMS-IWMSC

specified from  Rel-11
in  TS 23.040  and  TS 29.338 

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.

Up       Top


between  SGSN  and  HSS

specified from  Rel-8
in  TS 23.060  and  TS 29.272 

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.

Up       Top


between  MTC-IWF  and  HSS / HLR

specified from  Rel-11
in  TS 23.682  and  TS 29.336 

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


between  MTC-AAA  and  HSS / HLR

specified from  Rel-11
in  TS 23.682  and  TS 29.336 

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.

Up       Top


between  SCEF  and  HSS

specified from  Rel-13
in  TS 23.682  and  TS 29.336 

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.

Up       Top


between  CSS  and  MME

specified from  Rel-11
in  TS 23.401  and  TS 29.272 

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.

Up       Top


between  CSS  and  S4-SGSN

specified from  Rel-11
in  TS 23.060  and  TS 29.272 

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.

Up       Top


between  Visited S-GW  and  Home PDN-GW

 

See  S5/S8.

Up       Top


between  H-PCRF  and  H-PCRF

specified from  Rel-8
in  TS 23.203  and  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.

Up       Top


between  BPCF  and  PCRF / V-PCRF

specified from  Rel-11
Source:   TS 23.002, clause 6a.13.15 

This interface supports the transfer of (QoS) policy information from PCRF to BPCF of broadband access network. This interface is specified in TS 29.215.

S9a is only applicable to the interworking with Fixed Broadband Access network.

Up       Top


between  MME  and  MME

specified from  Rel-8
in  TS 23.401, clause 5.1.1.7  and  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

Up       Top


between  MME  and  S-GW

specified from  Rel-8
in  TS 23.401, clause 5.1.1.8  and  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)

Up       Top


between  MME  and  S-GW

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

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

Up       Top


between  S-GW  and  UTRAN

specified from  Rel-8
in  TS 23.401, clause 5.1.2.4  and  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


between  MME  and  EIR

specified from  Rel-8
in  TS 23.401  and  TS 29.272 

The S13 reference point is used by the MME to exchange data with the EIR, in order that the EIR can verify the status of the IMEI retrieved from the Mobile Station (e.g. to check that it has not been stolen, or, to verify that it does not have faults).

Commands:
  • ECR/ECA:  ME-Identity-Check-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  SGSN  and  EIR

specified from  Rel-8
in  TS 23.060  and  TS 29.272 

The S13' reference point is used by the SGSN to exchange data with the EIR, in order that the EIR can verify the status of the IMEI retrieved from the Mobile Station (e.g. to check that it has not been stolen, or, to verify that it does not have faults).

Commands:
  • ECR/ECA:  ME-Identity-Check-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  UE  and  ANDSF

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.21 

This interface is used for direct queries via pull mechanism. It enables dynamic provision of information to the UE for Network discovery and selection procedures related to non-3GPP accesses. Push and/or combination of Pull-Push may be supported as well. This interface is specified in TS 24.302.

Up       Top


between  HNB-GW  and  PCRF / V-PCRF

specified from  Rel-11
Source:   TS 23.002, clause 6a.13.14 

This reference point supports the initiation, modification and termination of sessions between the HNB GW and PCRF to support CS sessions. It triggers the PCRF to request allocation of resources in the Fixed Broadband access network for HNB CS calls. This interface is specified in TS 29.212.

S15 is only applicable to the interworking with Fixed Broadband Access network.

Up       Top


between  S4-SGSN  and  S4-SGSN

specified from  Rel-8
in  TS 23.060, clause 5.6.1.2  and  TS 29.274 

Interface between two SGSNs within the same or different PLMNs when those SGSNs support S4.
  • 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
  • CS Fallback and SRVCC related messages (TS 29.274, clause 7.4)
    • Suspend Notification/Acknowledge

Up       Top


between  HRPD AN  and  MME

specified from  Rel-8
in  TS 23.402, clause 9.1.2  and  TS 29.276 

The S101 interface supports procedures for Pre-Registration, Session Maintenance and Active handovers between E-UTRAN and HRPD networks. This is based on tunnelling over S101 signalling of one technology while the UE is in the other technology as specified in TS 23.402.

The HRPD air interface messages tunnelled over S101 in E-UTRAN to HRPD mobility are defined in 3GPP2 C.S0087 0.

Up       Top


between  3GPP2 1xCS IWS  and  MME

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.23 

The S102 reference point provides a tunnel between MME and 3GPP2 1xCS IWS to relay 3GPP2 1xCS signalling messages in order to support SRVCC as specified in TS 23.216 and CS Fallback as specified in TS 23.272. 1x CS signalling messages are those messages that are defined for A21 interface as described in 3GPP2 A.S0008-C.

In case of CS Fallback to 1x CS network as specified in TS 23.272, S102 Tunnel Redirection Procedure is used when the UE perform Tracking Area Update with MME change (as specified in TS 23.402 in case of S101 tunnel redirection) while the UE is registered with the 1xRTT CS domain and the S102 session exists between the MME and the 1xCS IWS.

Up       Top


between  HSGW  and  S-GW

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.24 

The S103 interface between the Serving GW and HRPD PDSN HSGW supports the forwarding of DL data during mobility from E-UTRAN to HRPD as specified in TS 23.402. Signalling procedures on the S101 interface are used to set up tunnels on the S103 interface.

Up       Top


between  HRPD AN  and  MME

specified from  Rel-12
in  TS 23.402, clause 17  and  TS 29.276 

The S121 interface supports RIM message transfer between eNodeB and HRPD A.

Up       Top


between  MME  and  CBC

specified from  Rel-8
Source:   TS 23.002, clause 6a.5.2 

Reference point between CBC and MME for warning message delivery and control functions. This interface is specified in TS 29.168.

Up       Top


between  TDF  and  PCRF / H-PCRF / V-PCRF

specified from  Rel-11
in  TS 23.203  and  TS 29.212 

The Sd Reference Point enables a PCRF to have dynamic control over the application detection and control behaviour at a TDF.

Commands:
  • TSR/TSA:  TDF-Session-Request/Answer
  • CCR/CCA:  CC-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.

Up       Top


between  MME  and  SMS-GMSC / SMS-IWMSC

specified from  Rel-11
in  TS 23.040  and  TS 29.338 

The SGd reference point is used to transfer short messages between the MME, the SMS-IWMSC, the SMS-GMSC and the SMS Router, and the alerting of the SMS-GMSC by the MME (possibly via an SMS Router),.

Commands:
  • OFR/OFA:  MO-Forward-Short-Message-Request/Answer
  • TFR/TFA:  MT-Forward-Short-Message-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  PDN-GW  and  PDN (Packet Data Network) 

specified from  Rel-8
Source:   TS 23.002, clause 7.2a 

This is the reference point between the PDN-GW and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. For more details see TS 29.061.

Up       Top


between  MBMS-GW  and  BM-SC

specified from  Rel-10
Source:   TS 23.002, clause 6a.11.2 

This reference point is used between MBMS-GW and BM-SC for MBMS data delivery. The details for this reference point are described in TS 23.246 and TS 29.061.

Up       Top


between  MBMS-GW  and  BM-SC

specified from  Rel-10
Source:   TS 23.002, clause 6a.11.1 

This reference point is used to exchange signalling between MBMS-GW and BM-SC. This represents the network side boundary of the MBMS Bearer Service from a control plane perspective. This includes MBMS bearer service specific signalling. The details for this reference point are described in TS 23.246 and TS 29.061.

Up       Top


between  MSC/VLR  and  MME

specified from  Rel-8
in  TS 23.272  and  TS 29.118 

This interface is used for the mobility management and paging procedures between EPS and CS domain, and it is based on the Gs interface procedures.

It is used to provide Fallback for Location Services (LCS) and Call Independent Supplementary Services (SS). It is also used for the delivery of both mobile originating and mobile terminating SMS over E-UTRAN in case SMSIP is not used.

Up       Top


between  HSS  and  SIP AS / OSA SCS

specified from  Rel-5
in  TS 23.228  and  TS 29.229 

The Application Server (SIP Application Server and/or the OSA Service Capability Server) may communicate to the HSS. The Sh interface is used for this purpose.

This reference point is also used to exchange signalling between IP-SM-GW and the HSS for SMSIP delivery.

Commands:
  • UDR/UDA:  User-Data-Request/Answer
  • PUR/PUA:  Profile-Update-Request/Answer
  • SNR/SNA:  Subscribe-Notifications-Request/Answer
  • PNR/PNA:  Push-Notification-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  HSS  and  CAMEL IM-SSF

specified from  Rel-5
Source:   TS 23.002, clause 6a.7.17 

The CAMEL Application Server (IM-SSF) may communicate to the HSS. The Si interface is used for this purpose. Details are described in TS 23.228, clause 4.2.4.

Up       Top


between  GMLC  and  MME

specified from  Rel-9
in  TS 23.271  and  TS 29.172 

The SLg interface is used by the GMLC to communicate with MMEs.

Commands:
  • PLR/PLA:  Provide-Location-Request/Answer
  • LRR/LRA:  Location-Report-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  GMLC  and  HSS

specified from  Rel-9
in  TS 23.271  and  TS 29.173 

The SLh interface is used by the GMLC to request the address of the visited MME for a particular target UE whose location has been requested.

Commands:
  • RIR/RIA:  LCS-Routing-Info-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  MME  and  E-SMLC

specified from  Rel-9
Source:   TS 23.002, clause 6a.3.13 

The SLs interface is used to convey LCS messages between the MME and E-SMLC. It is also used for tunnelling positioning protocol messages between the E-SMLC and either E-UTRAN or UE which are transparent to the MME as described in TS 36.305. The SLs interface is defined in TS 29.171.

Up       Top


between  MBMS-GW  and  MME

specified from  Rel-9
in  TS 23.246, clause 4.3.3  and  TS 29.274 

This reference point is used to exchange signalling between MBMS-GW and MME for MBMS Session Control.

MBMS Messages (TS 29.274, clause 7.13)
  • MBMS Session Start Request/Response
  • MBMS Session Update Request/Response
  • MBMS Session Stop Request/Response

Up       Top


between  MBMS-GW  and  S4-SGSN

specified from  Rel-9
in  TS 23.246, clause 4.3.3  and  TS 29.274 

This reference point is used to exchange signalling between MBMS-GW and S4-SGSN for MBMS Session Control and for MBMS data delivery in point-to-point mode.

MBMS Messages for Control (TS 29.274, clause 7.13)
  • MBMS Session Start Request/Response
  • MBMS Session Update Request/Response
  • MBMS Session Stop Request/Response

Up       Top


between  SPR  and  PCRF

specified from  Rel-8
Source:   TS 23.203, clause 5.2.3.1 

The Sp reference point allows the PCRF to request subscription information related to the IP-CAN transport level policies from the SPR based on a subscriber ID, a PDN identifier and possible further IP-CAN session attributes. For example, the subscriber ID can be the IMSI.

The Sp reference point also allows the SPR to notify the PCRF when the subscription information has been changed if the PCRF has requested such notifications.

Up       Top


between  TSSF  and  PCRF

specified from  Rel-13
in  TS 23.203  and  TS 29.212 

The St reference point is used to provision the traffic steering control information from the PCRF to the TSSF.

Commands:
  • TNR/TNA:  TSSF-Notification-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top

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

This interface connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner.

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.

Up       Top


between  MSC  and  MME / SGSN

specified from  Rel-8
in  TS 23.216, clause 5.4.2  and  TS 29.280 

This interface is used to support Inter-RAT handover from IMS-based voice service over EPS to CS domain over 3GPP UTRAN/GERAN access or from UTRAN (HSPA) to 3GPP UTRAN/GERAN access and to support Inter-RAT handover from IMS based voice and video service over EPS to CS domain over 3GPP UTRAN access.

This interface is also used to support Inter-RAT handover from voice service in CS domain over 3GPP UTRAN/GERAN access to IMS based service over LTE or UTRAN (HSPA).

Sv Messages (TS 29.280, clause 5.2)
  • SRVCC PS to CS Request/Response
  • SRVCC PS to CS Complete Notification/Acknowledge
  • SRVCC PS to CS Cancel Notification/Acknowledge
  • SRVCC CS to PS Request/Response
  • SRVCC CS to PS Complete Notification/Acknowledge
  • SRVCC CS to PS Cancel Notification/Acknowledge

Up       Top

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

This interface enables support for the Untrusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization and charging-related information in a secure manner.

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.

Up       Top


between  3GPP AAA Server  and  3GPP AAA Proxy

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

This interface connects the 3GPP AAA Proxy, possibly via intermediate networks, to the 3GPP AAA Server.

Commands:
  • DER/DEA:  Diameter-EAP-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  ePDG  and  3GPP AAA Server / Proxy

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

This reference point is used for AAA signalling (transport of mobility parameters, tunnel authentication and authorization data). It also includes the MAG-AAA interface functionality, RFC 5779 and Mobile IPv6 NAS-AAA interface functionality, RFC 5447.

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.

Up       Top

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.18 

Traffic on this interface for a UE-initiated tunnel has to be forced towards ePDG.

Up       Top


between  ePDG  and  UE

specified from  Rel-8
Source:   TS 23.002, clause 6.4.4.19 

This interface supports handling of IPSec tunnels. The functionality of SWu includes UE-initiated tunnel establishment, user data packet transmission within the IPSec tunnel and tear down of the tunnel and support for fast update of IPSec tunnels during handover between two untrusted non-3GPP IP accesses.

This interface is specified in TS 24.302

Up       Top


between  HSS  and  3GPP AAA Server

specified from  Rel-8
in  TS 23.402, clause 12  and  TS 29.273, clause 8 

This reference point is used to authorize the UE and to transport NBM-related mobility parameters when NBM (Network-Based Mobility) is used to establish connectivity to the EPC. It is used to authenticate and authorize the UE when the S2a, S2b or S2c reference points are used to connect to EPC. It is also used to update the HSS with the PDN-GW address information. Additionally, it may be used to retrieve and update other mobility related parameters including static QoS profiles for non-3GPP accesses.

Commands:
  • MAR/MAA:  Multimedia-Authentication-Request/Answer
  • PPR/PPA:  Push-Profile-Request/Answer
  • SAR/SAA:  Server-Assignment-Request/Answer
  • RTR/RTA:  Registration-Termination-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  OCS  and  PCRF / H-PCRF

specified from  Rel-11
in  TS 23.203  and  TS 29.219 

The Sy reference point enables transfer of policy counter status information relating to subscriber spending from OCS to PCRF and supports the following functions:
  • Request for reporting of policy counter status information from PCRF to OCS and subscribe to or unsubscribe from spending limit reports (i.e. notifications of policy counter status changes).
  • Report of policy counter status information upon a PCRF request from OCS to PCRF.
  • Notification of spending limit reports from OCS to PCRF.
  • Cancellation of spending limit reporting from PCRF to OCS.
Since the Sy reference point resides between the PCRF and OCS in the HPLMN, roaming with home routed or visited access as well as non-roaming scenarios are supported in the same manner.

Commands:
  • SLR/SLA:  Spending-Limit-Request/Answer
  • SNR/SNA:  Spending-Status-Notification-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top