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

|   Rc (Charging)   |   Rc (IMS)   |   Re   |   REST-Rx   |   Rf   |   Rg   |   Ro   |   Rp   |   Rr   |   Rx   |

 


between  OCF  and  ABMF

specified from  Rel-6
Source:   TS 32.240, clause 4.4.2.5 

The Rc reference point allows the interaction between the OCF and an Account Balance Management Function (ABMF) in order to access the account of the subscriber on the OCS.

See 32.296 for further information.

Up       Top


between  AS  and  MRB

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

This reference point is used by the AS to request that media resources be assigned to a call when utilizing an MRB in both Query and In-Line modes (as described in TS 23.218).

Up       Top


between  OCF  and  RF

specified from  Rel-6
Source:   TS 32.240, clause 4.4.2.4 

The Re reference point supports interaction between the OCF and a Rating Function (RF) in order to determine the value of chargeable events in terms of monetary or non-monetary units.

This interface application is defined in 32.296.

Up       Top


between  AF  and  PC (Protocol Converter)

specified from  Rel-12  in  TS 29.201 

The Rx reference point, which is based on Diameter, is defined between the PCRF and the AF. If the AF supports RESTful HTTP and XML, a Protocol Converter (PC) is needed. The interface between the AF and the PC is named REST-Rx. The REST-Rx interface shall be used in non-IMS scenarios only.

The PC converts the information, received over the REST-Rx interface, into information that can be used on the Diameter-based Rx interface in order to get an access to the PCC architecture and vice versa. The PC manages RESTful resources, which are an integral part of the REST-Rx interface.

Up       Top


between  CTF  and  CDF

specified from  Rel-6
in  TS 32.240, clause 4.4.1.1  and  TS 32.299, clauses 6.1 and 6.2 

This interface essentially uses the Accounting-Request (ACR) and Accounting-Answer (ACA) commands defined in RFC 6733 (Diameter), section  9 (Accounting).

In the case of event-based offline charging, when the network element receives the indication that the service has been used/delivered, it sends (acting as a CTF) the charging parameters to the CDF via an EVENT_RECORD ACR.

Event-based offline charging

In the case of session-based offline charging, when the network element receives a service request, it sends (acting as a CTF) a START_RECORD ACR to the CDF, which will open a CDR. At regular interval times (Acct-Interim-Interval proposed by the CDF) the CTF will send an INTERIM_RECORD ACR and the CDF will update the CDR. When the service is terminated, the CTF will send a STOP_RECORD ACR and the CDF will close the CDR.

Session-based offline charging

The information contained in the charging events and the relevant chargeable events are specific to the domain / subsystem / service and are detailed in the respective middle tier TSs (see Charging).

Up       Top


between  GUP Server  and  Applications 

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

This reference point allows applications to create, read, modify and delete any user profile data using the harmonized access interface. The GUP Server locates the data repositories responsible of the storage of the requested profile component(s).

For more information see TS 23.240.

Up       Top


between  CTF  and  OCF

specified from  Rel-6
in  TS 32.240, clause 4.4.2.1  and  TS 32.299, clauses 6.3 and 6.4 

For online charging the Diameter Credit-Control Application (DCCA) defined in RFC 4006 is used. Three cases for online charging can be distinguished: Immediate Event Charging (IEC), Event Charging with Unit Reservation (ECUR) and Session Charging with Unit Reservation (SCUR).

Immediate Event Charging - Direct Debiting operation

Up       Top


between  HSS  and  GUP Server

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

This reference point enables the GUP Server and the Applications to access GUP Data Repositories. The HSS is one of the GUP Data Repositories. It stores the IM CN Subsystem user related data.

For more information see TS 23.240.

Up       Top


between  ABMF  and  Recharging Server 

specified from  Rel-6
in   TS 32.296, clause 5.1 

The Rr reference point allows the interaction between the ABMF and an external account recharging server.

Up       Top


between  AF  and  PCRF

specified for  Rel-6  in  TS 29.211 

specified from  Rel-7
in  TS 23.203, clause 5.2.1  and  TS 29.214 

This reference point enables transport of application level session information from AF to PCRF. Such information includes, but is not limited to:
  • IP filter information to identify the service data flow for policy control and/or differentiated charging;
  • Media/application bandwidth requirements for QoS control;
  • In addition, for sponsored data connectivity:
    • the sponsor's identification,
    • optionally, a usage threshold and whether the PCRF reports these events to the AF,
    • information identifying the application service provider and application (e.g. SDFs, application identifier, etc.).
The Rx reference point enables the AF subscription to notifications on IP-CAN bearer level events (e.g. signalling path status of AF session) in the IP-CAN.
Commands:
  • AAR/AAA:  AA-Request/Answer
  • RAR/RAA:  Re-Auth-Request/Answer
  • STR/STA:  Session-Termination-Request/Answer
  • ASR/ASA:  Abort-Session-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top