Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 32.240  Word version:  17.3.0

Top   Top   Up   Prev   None
1…   3…   4…   4.3…   5…   5.3…   A…

 

A  BibliographyWord‑p. 52

This annex contains guidelines for the references in all the charging specifications.
  1. The 3GPP charging specifications
    [1]  - [99].
    One example:
    [20]  TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
  2. Common 3GPP specifications
    [100] - [199]
    One example:
    [101]  TS 22.115: "Service aspects; Charging and billing".
  3. other Domain and Service specific 3GPP / ETSI specifications
    [200] - [299]
    One example:
    [201]  TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
  4. Relevant ITU Recommendations
    [300] - [399]
    One example:
    [300]  ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)".
  5. Relevant IETF RFCs
    [400] - [499]
    One example:
    [402]  RFC 4006  (2005): "Diameter Credit-Control Application".
  6. Others
    [500] - [699]
    One example:
    [601]  Broadband Forum TR-134: "Broadband Policy Control Framework (BPCF)".
Up

B (Normative)  Single IMSI architecture for EU Roaming |R12|Word‑p. 53

B.0  GeneralWord‑p. 53

To enable the sale of regulated roaming services, an architecture based on 3GPP has been defined in the high-level technical specification EU Roaming regulation III; Structural Solutions; High Level Technical Specifications [298]. A real-time interface has been defined in EU Roaming regulation III; Interface & Protocol; Detailed Technical Specifications [299] for retailing billing of voice calls between a Domestic Service Provider and an Alternative Roaming Provider.
For the purposes of this annex, the following definitions apply:
Alternative Roaming Provider (ARP):
A roaming provider different from the domestic provider.
Domestic Service Provider (DSP):
An undertaking that provides a roaming customer with domestic mobile communications services, either a Mobile Network Operator or a Mobile Virtual Network Operator.
Up

B.1  Voice ControlWord‑p. 53

To enable charging of ARP subscribers for voice calls, an online charging interface between the DSP and ARP is established. The concept of voice call shall be interpreted as any Circuit-switched call, whatever the teleservice used (speech, 3.1 kHz audio, Fax, or CS data) except circuit-switched Video Telephony calls (BS 37, 64 kbit/s unrestricted digital info mode). The voice control architecture is shown in Figure B.1.1.
(not reproduced yet)
Figure B.1.1: Voice Control Architecture and Associated Functions
Up
The signaling between the Visited Network and the DSP utilizes CAP for the online CS domain charging as specified in TS 32.250. For the CAMEL option of IF#1, the signaling between the DSP and ARP also utilizes CAP for the online CS domain charging as specified in TS 32.250. For the Diameter option of IF#1, the signaling between the DSP and ARP utilizes Diameter Ro for the Voice Call Service online charging as specified in TS 32.276 and utilizes the Proxy Function for mapping between CAMEL and Diameter as specified in TS 32.293.
Up

C (Normative)  Fixed Broadband Access |R12|Word‑p. 54

C.1  GeneralWord‑p. 54

C.2  ReferencesWord‑p. 54

(Void)

C.3  Definitions, symbols and abbreviationsWord‑p. 54

(Void)

C.4  Common charging architecture and frameworkWord‑p. 54

C.4.1  Charging mechanismsWord‑p. 54

(Void)

C.4.2  High level common architectureWord‑p. 54

The logical ubiquitous charging architecture and the information flows for offline and online charging of Figure 4.2.2.1, applied to the convergent scenario (i.e. both the Fixed Broadband Access network and Evolved Packet Core (EPC) owned by a single operator) with PCEF located in Fixed Broadband Access is shown in the Figure C.4.2.1 below, based on Architecture defined in TS 23.203, clause S.4.1.
(not reproduced yet)
Figure C.4.2.1: Logical ubiquitous charging architecture and information flows PCEF located in IP-Edge
Up

C.4.3  Charging functionsWord‑p. 55

(Void)

C.4.4  Reference pointsWord‑p. 55

C.4.4.1  Offline charging reference pointsWord‑p. 55

C.4.4.1.1  GzWord‑p. 55
When applied to PCEF located in IP-Edge, the Gz reference point functionality relies on Rf or Ga Reference Points within the common charging architecture.
C.4.4.1.2  GznWord‑p. 55
The TDF when used for application based charging in a convergent scenario performs the same functionality as outlined in this document and in addition the Gzn reference point enables transport of offline charging information for both Non-seamless WLAN offloaded traffic from a 3GPP UE and for fixed devices.

C.4.4.2  Online charging reference pointsWord‑p. 55

C.4.4.2.1  GyWord‑p. 55
When applied to PCEF located in IP-Edge, the Gy reference point functionality relies on Ro Reference Point within the common charging architecture.
C.4.4.2.2  GynWord‑p. 55
The TDF when used for application based charging in a convergent scenario performs the same functionality as outlined in this document and in addition the Gyn reference point allows online credit control for TDF based charging for both Non-seamless WLAN offloaded traffic from a 3GPP UE and for fixed devices.

D (Normative)  Distributed Charging Trigger Function |R12|Word‑p. 56

D.1  GeneralWord‑p. 56

This annex specifies the enhancement to 3GPP charging architecture and framework in which, when required for a specific service, the Charging Trigger Function is split between the UE that supports that service and the network element or service element. As described in clause 4.3.1.1, the CTF consists of the Accounting Metrics Collection (AMC) function block and the Accounting Data Forwarding (ADF) function block. For select services, the CTF (AMC) is located in the UE and the CTF (ADF) is located in the network element or service element reachable by an application layer protocol. The applicability of this distributed CTF architecture is described in each specific middle tier charging TS that utilizes this construct.
In the present document the distributed CTF is only available for offline charging.
Up

D.2  Definitions, symbols and abbreviationsWord‑p. 56

D.2.1  DefinitionsWord‑p. 56

(Void)

D.2.2  SymbolsWord‑p. 56

For the purposes of this annex, the following symbols apply:
Xch
Offline charging reference point between a UE and the service NE for charging purposes

D.2.3  AbbreviationsWord‑p. 56

For the purposes of this annex, the following abbreviations apply:
CTF (AMC)
Charging Trigger Function (Accounting Metrics Collection)
CTF (ADF)
Charging Trigger Function (Accounting Data Forwarding)

D.3  Common charging architecture and frameworkWord‑p. 56

D.3.1  Charging mechanismsWord‑p. 56

(Void)

D.3.2  High level common architectureWord‑p. 56

The logical ubiquitous charging architecture and the reference points for offline charging of figure 4.2.1, extended with the distributed CTF architecture is shown in figure D.3.2.1.
(not reproduced yet)
Figure D.3.2.1: Logical ubiquitous charging architecture and reference points with distributed functional blocks of CTF for offline charging
Up

D.4.3  Charging functionsWord‑p. 57

D.4.3.1  Offline charging functionsWord‑p. 57

D.4.3.1.1  Charging Trigger FunctionWord‑p. 57
For a service utilizing the distributed CTF, the CTF is divided into two functional blocks as described in clause 4.3.1.1. The Accounting Metrics Collection (AMC) function block is in the UE that supports the specific service. The AMC sends usage information collected to the Accounting Data Forwarding (ADF) function block of the CTF in the service NE over the service-specific reference point, denoted as X. The subset of X specific to usage information collection for charging purposes is denoted as Xch in figure D.3.2.1.
Up

D.4.3.2  Online charging functionsWord‑p. 57

In this present specification, the distributed CTF is only available for offline charging.

D.4.4  Reference pointsWord‑p. 57

D.4.4.1  Offline charging reference pointsWord‑p. 57

D.4.4.1.1  XchWord‑p. 57
The subset of service-specific reference point X that is specific to usage information collection for charging purposes.

D.4.4.2  Online charging reference pointsWord‑p. 57

In this present specification, the distributed CTF is only available for offline charging.

E  High level overall charging architecture. |R15|Word‑p. 58

High level overall charging architecture.

E.1  GeneralWord‑p. 58

This annex presents a high level view of the overall charging architecture. It covers the charging reference points and interfaces from 3GPP Release 14 and 15 core networks and the IMS subsystem towards the charging functions of Release 14 and Release 15 charging systems.

E.2  Common charging architecture and frameworkWord‑p. 58

E.2.1  High level common architectureWord‑p. 58

The overall logical charging architecture is depicted below. The Rf and Ro reference points are applicable to GPRS, EPC or IMS NEs only, whereas the Nchf interface is applicable to 5GC NFs only.
(not reproduced yet)
Figure E.2.1.1: High level overall charging architecture and information flows
Up
When the target charging system (i.e. 5G CCS or EPC OCS/OFCS) needs to support termination of a reference point or interface from the opposite type of core network (i.e. Ro/Rf or Nchf) implementations will need to include interworking between the HTTP used by SBI and the Diameter protocol.

$  Change historyWord‑p. 59


Up   Top