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

|   Pc   |   PC1   |   PC2   |   PC3   |   PC4a   |   PC4b   |   PC5   |   PC6   |   PC7   |   Pen   |   Pep   |   Pet   |   Peu   |   Pex   |   Pg   |   Ph   |   Pi   |   Pk   |   Pl   |   Pp   |   Pr   |   Pw   |   Pwp   |   Px   |

 


between  Presence Network Agent  and  MSC Server / VLR

specified from  Rel-6
Source:   TS 23.141, clause 4.3.10 

This reference point shall allow the MSC Server/VLR to report the mobility management related events to the Network Agent (such as attach/detach/location area update) and may allow the MSC Server/VLR to report call related events (such as call setup with the bearer information and call release).

This reference point may allow the MSC Server/ VLR to report Mobility States (such as Detached, Idle and Connected) and Call States (such as Busy with Bearer information and Idle).

This reference point is implemented using the existing mechanisms of CAMEL phase 4, 3GPP Release 5.

For 3GPP2 systems, the interface to this reference point is defined in 3GPP2 X.S0004.

Up       Top


between  ProSe AS  and  ProSe Application in UE 

specified from  Rel-12
Source:   TS 23.303, clause 4.3 

It is used to define application level signalling requirements. This reference point is not specified yet.

Up       Top


between  ProSe AS  and  ProSe Function

specified from  Rel-12
in  TS 23.303  and  TS 29.343 

The PC2 reference point is used to define the interaction between ProSe Application Server and ProSe functionality provided by the 3GPP EPS via ProSe Function (e.g. name translation) for EPC-level ProSe discovery.

Commands:
  • PXR/PXA:  ProXimity-Action-Request/Answer
  • XAR/XAA:  ProXimity-Application-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  ProSe Function

specified from  Rel-12
Source:   TS 23.303, clause 4.3 

PC3 relies on EPC user plane for transport (i.e. an "over IP" reference point). It is used to authorise ProSe Direct Discovery and EPC-level ProSe Discovery requests, and perform allocation of ProSe Application Codes corresponding to ProSe Application Identities used for ProSe Direct Discovery. It is used to define the authorisation policy per PLMN for ProSe Direct Discovery (for Public Safety and non-Public Safety) and communication (for Public Safety only) between UE and ProSe Function.

Up       Top


between  HSS  and  ProSe Function

specified from  Rel-12
in  TS 23.303  and  TS 29.344 

The PC4a reference point is used to provide subscription information in order to authorise access for ProSe Direct Discovery and ProSe Direct Communication on a per PLMN basis. It is also used by the ProSe Function (i.e. EPC-level ProSe Discovery Function) for retrieval of EPC-level ProSe Discovery related subscriber data.

Commands:
  • PIR/PIA:  ProSe-Subscriber-Information-Request/Answer
  • UPR/UPA:  Update-ProSe-Subscriber-Data-Request/Answer
  • PNR/PNA:  ProSe-Notify-Request/Answer
  • PSR/PSA:  ProSe-Initial-Location-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  SLP (OMA Secure User Plane Location Platform)  and  ProSe Function

specified from  Rel-12
Source:   TS 23.303, clause 4.3 

It is used by the ProSe Function (i.e. EPC-level ProSe Discovery Function) in the role of LCS client to query the SLP defined in OMA AD SUPL.

Up       Top

specified from  Rel-12
Source:   TS 23.303, clause 4.3 

It is used for control and user plane for ProSe Direct Discovery, ProSe Direct Communication and ProSe UE-to-Network Relay.

Up       Top

specified from  Rel-12
in  TS 23.303  and  TS 29.345 

The PC6 reference point is defined between a ProSe Function in the HPLMN and a ProSe Function in a local PLMN.

The PC7 reference point is defined between a ProSe Function in the HPLMN and a ProSe Function in a visited PLMN.

The PC6/PC7 reference points are used for:
  • HPLMN control of service authorization for ProSe;
  • Authorization of ProSe Direct Discovery requests;
  • Retrieval of Discovery Filter(s) corresponding ProSe Application ID name(s);
  • Translation of ProSe Application Code(s) to the associated ProSe Application Name.
Commands:
  • PAR/PAA:  ProSe-Authorization-Request/Answer
  • PDR/PDA:  ProSe-Discovery-Request/Answer
  • PMR/PMA:  ProSe-Match-Request/Answer
  • PIR/PIA:  ProSe-Match-Report-Info-Request/Answer
  • PRR/PRA:  ProSe-Proximity-Request/Answer
  • PLR/PLA:  ProSe-Location-Update-Request/Answer
  • ALR/ALA:  ProSe-Alert-Request/Answer
  • RPR/RPA:  ProSe-Cancellation-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-6
Source:   TS 23.141, clause 4.3.2 

This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations to the size of the presence information.

Pen shall provide mechanisms for:
  • the Network Agent to manage subscription authorisation policies;
  • the Network Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server;
  • activating or deactivating the reporting of Presence Information for a given presentity from the network entities within the PLMN.
The Pen interface is an intra-operator interface. In order to provide the all the functionalities required on this reference point, a combination of multiple protocols may be used. In general the protocols used at the Pen reference point are not standardised. However, for 3GPP2 systems this reference point is defined in X.S0027-004.

At least, this interface shall support the transport of presence information under the PIDF format as specified in RFC 3863.

Up       Top

specified from  Rel-6
Source:   TS 23.141, clause 4.3.14 

This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations on the size of the presence information. This interface shall support the transport of presence information under the PIDF format as specified in RFC 3863.

Pep shall provide mechanisms for the Presence User Agent to obtain information on watcher subscriptions to the presentity's presence information.

Pep shall provide mechanisms for the Presence User Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server. It shall also be possible for the Presence User Agent to supply the complete presence document over Pep.

Pep shall support SIP-based communications for publishing presence information. IPv6 shall be supported for all functionalities required from a Presence User Agent that supports the Pep reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Pep. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 should be followed.

Up       Top

specified from  Rel-6
Source:   TS 23.141, clause 4.3.16 

This reference point shall allow a Watcher application to manage presence list information in the Presence List Server.

This reference point uses capabilities defined for the Ut reference point.

Up       Top

specified from  Rel-6
Source:   TS 23.141, clause 4.3.1 

This reference point shall allow the Presence User Agent to manage subscription authorization policies. IPv6 shall be supported for all functionalities required from a Presence User Agent that supports the Peu reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Peu.

However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 should be followed.

This reference point uses capabilities defined for the Ut reference point.

Up       Top


between  Presence External Agent  and  Presence Server

specified from  Rel-6
Source:   TS 23.141, clause 4.3.3 

This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations on the size of the presence information.

Pex shall provide mechanisms for the Presence External Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server.

In order to provide all the functionalities required on this reference point, a combination of multiple protocols may be used. Presence information obtained from an external network by the Presence External Agent is transferred across the Pex reference point to the Presence Server. This interface shall support the transport of presence information under the PIDF format as specified in RFC 3863.

Up       Top


between  Presence Network Agent  and  SGSN

specified from  Rel-6
Source:   TS 23.141, clause 4.3.9 

This reference point shall allow the SGSN to report mobility management related events (such as attach/not reachable for paging/detach/routing area update) to the Presence Network Agent.

This reference point may allow the SGSN to report Mobility States (such as Detached, Idle and Connected) and Session States (such as PDP context active and inactive).

This reference point is implemented using the existing mechanisms of CAMEL phase 4, 3GPP Release 5.

For 3GPP2 systems, this reference point is not supported

Up       Top


between  HSS / HLR  and  Presence Network Agent

specified from  Rel-6
Source:   TS 23.141, clause 4.3.5 

This reference point shall allow the Presence Network Agent to query HSS/HLR about the state and status of a subscriber (associated with a presentity) from the serving network (for 3GPP this is the CS domain or GPRS) and IMS perspective.

This reference point permits the Presence Network Agent to activate and deactivate the reporting of mobility management events from the serving network (for 3GPP this is the CS domain or GPRS) and/or the IMS-specific reports from the S-CSCF.

This reference point uses capabilities defined for the Sh reference point as well as the MAP interface.

Up       Top


between  S-CSCF  and  Presence Network Agent

specified from  Rel-6
Source:   TS 23.141, clause 4.3.6 

The S-CSCF may provide IMS-specific presence information (e.g. about IMS registration state). This reference point shall use mechanisms defined for the ISC reference point.

Up       Top


between  Presence Network Agent  and  GGSN

specified from  Rel-6
Source:   TS 23.141, clause 4.3.11 

This reference point shall allow the GGSN to report presence relevant events to the Presence Network Agent (such as PDP context activation/de-activation). This reference point is implemented using the mechanisms of the RADIUS interface for reporting of access requests on Gi reference point.

For 3GPP2 systems, this reference point is not supported.

Up       Top


between  Presence Network Agent  and  GMLC

specified from  Rel-6
Source:   TS 23.141, clause 4.3.8 

This reference point shall be used by the Presence Network Agent to retrieve location information related to a subscriber (associated with the presentity). This reference point is the interface to GMLC and it is an instance of the Le reference point.

In the case of Presence the LCS client is the Presence Network Agent and so the protocol implementing Pl needs to be defined. Though normally a stage 3 responsibility in this case the protocol to be used is defined here since it is a reference to an existing protocol. Thus, Pl shall conform to OMA LIF-MLP specification.

For 3GPP2 systems, the interface for this reference point is to the 3GPP2 Position Server and is not supported in the current release of the specification.

Up       Top


between  Presence Network Agent  and  PDG

specified from  Rel-6
Source:   TS 23.141, clause 4.3.13 

This reference point shall allow the PDG to report presence relevant events to the Presence Network Agent (such as tunnel establishment/removal, allocation of the remote IP address for the WLAN UE). This reference point is based on reusing of the Wi reference point.

For 3GPP2 systems, this reference point is not supported.

Up       Top

specified from  Rel-6
Source:   TS 23.141, clause 4.3.12 

This reference point shall allow the 3GPP AAA Server to report IP-connectivity related events to the Presence Network Agent (such as WLAN UE attaching/detaching and tunnel establishment/removal). The Pr reference point shall be as much as possible based on mechanisms of existing interfaces.

For 3GPP2 systems, the interface for this reference point is to the AAA server and is defined in X.S0027-004.

Up       Top

specified from  Rel-6
Source:   TS 23.141, clause 4.3.4 

This reference point shall allow a Watcher application to request and obtain presence information. This interface shall support the transport of presence information under the PIDF format as specified in RFC 3863.

The transport shall not impose any limitations to the size of the presence information. In order to provide all the functionalities required on this interface, a combination of multiple protocols may be used. This reference point shall support both presence monitoring and fetching modes.

In the fetching mode, it shall be possible for the watcher to once request all or only a subset of a presentity's presence information (e.g. one or more tuples). The subset of the presence information is defined by the filter that is carried in the presence information subscription.

In the monitoring mode, it shall be possible for the watcher to request monitoring of all or a subset of a presentity's presence information (i.e. one or more tuples) . Watcher shall be able to explicitly indicate the capability to process partial updates. The subset of the presence information is defined by the filter that is carried in the presence information subscription. It shall be possible for the watcher to request the presence server to filter out information when the watcher is equal to the publishing Presence User Agent. It shall be possible for the notifications containing the presentity's presence information to contain only information as defined by filters. It shall be possible for the notifications containing the presentity's presence information to contain only the modified tuples, i.e. only those tuples which have changed since the last notification.

This reference point may allow a Watcher application to use presence lists in presence information subscriptions, and the Watcher Presence Proxy to interface to a server that provides the functionality of Presence List Server. IPv6 shall be supported for all functionalities required from a Watcher application that supports the Pw reference point.

An IPv6 capable 3GPP UE shall use IPv6 when accessing Pw. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 should be followed.

Up       Top

specified from  Rel-6
Source:   TS 23.141, clause 4.3.15 

The Pwp interface is an intra-operator interface. This reference point shall allow all the functionalities provided by the Pw and Pep reference points.

Up       Top


between  Presentity Presence Proxy  and  HSS

specified from  Rel-6
Source:   TS 23.141, clause 4.3.7 

The Px interface is an intra-operator interface. This interface shall assist locating the Presence Server of the presentity. This interface is implemented using the mechanisms defined for the Cx and Dx reference points.

Up       Top