tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

3GPP Glossaries

 

 

Interfaces / Reference Points

Y

 

 

 

Here          Top

 Rc (Charging)     #  Rc (IMS)     #  Re     #  Rf     #  Rg     #  Ro     #  Rp     #  Rr     #  Rx    

 


between  OCF  and  ABMF

[Charging  R6]+

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.

Source:   TS 32.240, clause 4.4.2.5

Up       Top


between  AS  and  MRB

[IMS  R8]+

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).

Source:   TS 23.002, clause 6a.7.9a

Up       Top


between  OCF  and  RF

[Charging  R6]+

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.

Source:   TS 32.240, clause 4.4.2.4

Up       Top


between  CTF  and  CDF

[Charging  R6]+

The Rf reference point supports interaction between a CTF and a CDF. The following information may flow across this reference point in real-time:
  • Charging events for offline charging from the CTF to the CDF;
  • Acknowledgements for these events from the CDF to the CTF.
The protocol(s) crossing this reference point shall support the following capabilities:
  • Real-time transactions;
  • Stateless mode ("event based charging") and statefull mode ('session based charging') of operation;
  • Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport.
In addition, the protocol should support changeover to a secondary destination (alternate CDF(s)) in case of the primary CDF not being reachable. This interface application is defined in TS 32.299. 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.

Source:   TS 32.240, clause 4.4.1.1

Up       Top


between  GUP Server  and  Applications 

[R6]+

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.

Source:   TS 23.002, clause 6a.12.1

Up       Top


between  CTF  and  OCF

[Charging  R6]+

The Ro reference point supports interaction between a CTF and an OCF. The following information may flow across this reference point:
  • Charging events for online charging from the CTF to the OCF.
  • Receive Acknowledgements for these charging events from the OCF to the CTF. The acknowledgement grants or rejects the network resource usage requested in the charging event, according to the decision taken by the OCS.
The protocol(s) crossing this reference point shall support the following capabilities:
  • Real-time transactions;
  • Stateless mode ("event based charging") and statefull mode ("session based charging") of operation;
    NOTE:
    For "event based charging", the protocol may be stateless, however Internal implementation of the CTF and OCF may be stateful across the different charging events.
  • Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport.
In addition, the protocol should support changeover to a secondary destination (alternate OCF(s)) in case of the primary OCF not being reachable. This interface application is defined in TS 32.299. 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.

Source:   TS 32.240, clause 4.4.2.1

Up       Top


between  HSS  and  GUP Server

[R6]+

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.

Source:   TS 23.002, clause 6a.12.2

Up       Top


between  ABMF  and  Recharging Server 

[Charging  R6]+

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

Source:   TS 32.296, clause 5.1

Up       Top


between  AF  and  PCRF

[PCC  R7]+

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.

Source:   TS 23.203, clause 5.2.1

Up       Top