Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map

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

 

Up       Top

between  MBMS-GW
and  BM-SC

see it   here

specified from  Rel-10  in
TS 23.246, clause 4.3.3
TS 29.061, clause 13b 

This reference point is used between MBMS-GW and BM-SC for MBMS data delivery.


SGmb   (Diameter)

Up       Top

between  MBMS-GW
and  BM-SC

see it   here

specified from  Rel-9  in
TS 23.246, clause 4.3
TS 29.061, clause 20 

The SGmb reference point has similar functions with the Gmb interface in control plane except for the Multicast Mode related functions. Specifically, the BM-SC indicates session start, update and stop to the MBMS-GW including session attributes like QoS and MBMS service area, and some of attributes may be different from them in Gmb.


SGs   (IP/SCTP/SGsAP)

Up       Top

between  MSC/VLR
and  MME

see it   here

specified from  Rel-9  in
TS 23.272
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.


Sh   (Diameter)

Up       Top

between  HSS
and  SIP AS / OSA SCS

specified from  Rel-5  in
TS 23.218, clause 7.2.2
TS 23.228
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.


Si   (MAP)

Up       Top

between  HSS
and  CAMEL IM-SSF

specified from  Rel-5  in
TS 23.218, clause 7.2.4
TS 23.278
TS 29.002 

The CAMEL Application Server (IM-SSF) may communicate to the HSS. The Si interface is used for this purpose.


Up       Top

between  MC signalling user agent
and  MC SIP core

specified from  Rel-14  in
TS 23.280, clause 7.5.3.2 

The SIP-1 reference point, which exists between the signalling user agent and the SIP core for establishing a session in support of MC service, shall use the Gm reference point (with necessary enhancements to support MC service requirements and profiled to meet the minimum requirements for support of MC service). The SIP-1 reference point fulfils the requirements of the GC1 reference point. The SIP-1 reference point is used for:
  • SIP registration;
  • authentication and security to the service layer;
  • event subscription and event notification;
  • communication of the TMGI for multicast operation;
  • overload control;
  • session management; and
  • media negotiation.


Up       Top

between  MC SIP AS
and  MC SIP core

specified from  Rel-14  in
TS 23.280, clause 7.5.3.3 

The SIP-2 reference point, which exists between the SIP core and the SIP AS for establishing a session in support of MC service, shall use the ISC and Ma reference points. The SIP-2 reference point is used for:
  • notification to the MC service server(s) of SIP registration by the MC service UE;
  • authentication and security to the service layer;
  • event subscription and event notification;
  • communication of the TMGI for multicast operation;
  • session management; and
  • media negotiation.


Up       Top

between  MC SIP core
and  MC SIP core

specified from  Rel-14  in
TS 23.280, clause 7.5.3.4 

The SIP-3 reference point, which exists between one SIP core and another SIP core for establishing a session in support of MC service, shall use the Mm and Ici reference points. The SIP-3 reference point is used for:
  • event subscription and event notification;
  • session management; and
  • media negotiation.


SLg   (Diameter)

Up       Top

between  GMLC
and  MME

see it   here

specified from  Rel-9  in
TS 23.271, clause 7.7
TS 29.172 

SLg is the interface that is used by the GMLC to convey a location request to the MME currently serving a particular target UE whose location was requested. The interface is also used by the MME to return location results to the GMLC.

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.


SLh   (Diameter)

Up       Top

between  GMLC
and  HSS

see it   here

specified from  Rel-9  in
TS 23.271, clause 7.9
TS 29.173 

The SLh interface is used by the GMLC to request routing information from the HSS i.e. the address of the H-GMLC, and/or the address of the visited MSC/MSC server, SGSN, 3GPP AAA server or 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.


SLm   (SLmAP)

Up       Top

between  E-SMLC
and  LMU

see it   here

specified from  Rel-11  in
TS 23.271, clause 7.10
TS 36.305, clause 6.1.5
TS 36.456
457
458
459 

This interface allows the E-SMLC to exchange measurement information with the LMU for the purpose of UTDOA positioning as described in TS 36.305.


SLs   (LCS-AP)

Up       Top

between  MME
and  E-SMLC

see it   here

specified from  Rel-9  in
TS 23.271, clause 7.8
TS 29.171 

This interface is used to convey location requests from the MME to the E-SMLC and to convey corresponding location reports back from the E-SMLC to the MME. It is also used for tunnelling core network measurement requests from the E-SMLC to the RAN, using RAN specified protocols transparent to the MME as described in TS 36.305.


Sm   (GTPv2-C)

Up       Top

between  MBMS-GW
and  MME

see it   here

specified from  Rel-9  in
TS 23.246, clause 4.3.3
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


Sn   (GTPv2-C and GTPv1-U)

Up       Top

between  MBMS-GW
and  S4-SGSN

see it   here

specified from  Rel-9  in
TS 23.246, clause 4.3.3
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


Sp

Up       Top

between  SPR
and  PCRF

see it   here

defined from  Rel-8  in
TS 23.203, clause 5.2.3.1
but not specified 

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.

UDR replaces SPR when the UDC architecture is applied to store PCC related subscription data. In this deployment scenario Ud interface between PCRF and UDR is used to access subscription data in the UDR.


St   (Diameter)

Up       Top

between  TSSF
and  PCRF

see it   here

specified from  Rel-13  in
TS 23.203, clause 5.2.14
TS 29.212, clause 4c 

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.


STa   (Diameter)

Up       Top

see it   here

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