Content for TS 32.291 Word version: 18.0.0

3.1 Definitions 3.2 Symbols 3.3 Abbreviations 4.1 Service architecture 4.2 Network functions
...

1 Scope p. 10

The present document specifies the protocol that is used for service based interface. The API definitions and data type definitions are aligned with the common charging architecture specified in TS 32.240. The present document is related to other 3GPP charging TSs as follows:

The common 3GPP charging architecture is specified in TS 32.240.
The 5G data connectivity charging is specified in TS 32.255.
The 5G connection and mobility charging is specified in TS 32.256.
The service, operations and procedures of 5G charging for service based interface is specified in TS 32.290.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in TS 29.500 and TS 29.501.

2 References p. 10

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".

[2] - [13] Void.

[14]

TS 32.254: "Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging".

[15] - [28] Void.

[29]

TS 32.274: "Telecommunication management; Charging management;Short Message Service (SMS) charging".

[30]

TS 32.255: "Telecommunication management; Charging management; 5G Data connectivity domain charging; stage 2".

[31]

TS 32.256: "Telecommunication management; Charging management; 5G connection and mobility domain charging; stage 2".

[32]

TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".

[33]

TS 32.275: "Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging".

[34]

TS 32.281: "Telecommunication management; Charging management; Announcement"

[35]

TS 32.277: "Telecommunication management; Charging management; Proximity-based Services (ProSe) charging".

[36]

TS 32.257: "Telecommunication management; Charging management; Edge computing domain charging; stage 2".

[37]

TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging".

[38] - [49] Void.

[50] - [57] Void.

[58]

TS 32.290: "Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI).

[59] - [69]

Void.

[70]

TS 28.201: "Charging management; Network slice performance and analytics charging in the 5G System (5GS); Stage 2".

[71]

TS 28.202: "Charging management; Network slice management charging in the 5G System (5GS); Stage 2".

[72] - [99] Void.

[100]

TR 21.905: "Vocabulary for 3GPP Specifications".

[101]

TR 21.900: "Technical Specification Group working methods".

[102]

TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[103] - [199] Void

[200] - [252] Void

[253]

TS 28.532: "Management and orchestration; Management services".

[254]

TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".

[255]

TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".

[256]

TS 28.554: "Management and orchestration;5G end to end Key Performance Indicators (KPI)".

[257]

TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".

[258]

TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3".

[259]

TS 29.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification".".

[260]

TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interface; signalling flows and message contents".

[261]

TS 29.002: "Mobile Application Part (MAP) specification".

[262]

TS 28.550: "Management and orchestration; Performance assurance".

[263]

TS 28.552: "Management and orchestration; 5G performance measurements".

[264] - [298] Void

[299]

TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".

[300]

TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".

[301]

TS 29.594: "5G System; Spending Limit Control Service; Stage 3".

[302]

TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".

[303]

TS 24.501: "Non-Access-Stratum (NAS) Protocol for 5G System (5GS); Stage 3".

[304]

TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".

[305]

TS 29.510: "Network Function Repository Services; Stage 3".

[306]

TS 29.520: "5G System; Network Data Analytics Services;Stage 3".

[307]

TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".

[308]

TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".

[309]

TS 29.558: "Enabling Edge Applications; Application Programming Interface (API) specification; stage 3".

[310]

TS 28.538: "Management and orchestration; Edge Computing Management".

[311]

TS 24.558: "Enabling Edge Applications; Protocol specification".

[312] - [370] Void

[371]

TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".

[372] - [389] Void

[390]

TS 33.501: "Security architecture and procedures for 5G System".

[391] - [399] Void

[400] Void.

[401]

RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".

[402]

RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format ".

[403]

RFC 6749: "The OAuth 2.0 Authorization Framework".

[404]

RFC 3986: "Uniform Resource Identifiers (URI): Generic Syntax".

[405]

RFC 7315: "Private Extensions to the Session Initiation Protocol (SIP) for the 3rd Generation Partnership Projects (3GPP)".

[406]

RFC 3261: "SIP: Session Initiation Protocol".

[407]

RFC 8866: "SDP: Session Description Protocol".

[408]

RFC 5646: "Tags for Identifying Languages".

[409]

OMA "Multimedia Messaging Service; Encapsulation Protocol".

[410] - [499] Void.

[500]

OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md.

[501] - [599] Void.

3 Definitions, symbols and abbreviations p. 13

3.1 Definitions p. 13

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2 Symbols p. 13

For the purposes of the present document, the following symbols apply:

Nchf

Service based interface exhibited by CHF.

3.3 Abbreviations p. 13

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

Application Function

AMF

Access and Mobility Management Function

ATSSS

Access Traffic Steering, Switching, Splitting

CHF

Charging Function

CEF

Charging Enablement Function

CTF

Charging Trigger Function

GPSI

Generic Public Subscription Identifier

GUAMI

Globally Unique AMF Identifier

I-SMF

Intermediate SMF

MnS

Management Service

Network Function

PEI

Permanent Equipment Identifier

QBC

QoS flow Based Charging

QFI

QoS Flow Identifier

SMSF

Short Message Service Function

SMF

Session Management Function

SSC

Session and Service Continuity

SUPI

Subscription Permanent Identifier

4 Overview p. 13

4.1 Service architecture p. 13

The Converged Charging Service or Offline Only Charging Service is provided by the CHF to the consumer and shown in the SBI representation model in Figure 4.1.1.

The ConvergedCharging Service (Nchf_ ConvergedCharging) or Offline Only Charging Service (Nchf_OfflineOnlyCharging) is part of the Nchf service-based interface exhibited by the Charging Function (CHF). The list of NF Service Consumer(s) is provided in Table 5.1-1.

Copy of original 3GPP image for 3GPP TS 32.291, Fig. 4.1.1: Reference Architecture for the Nchf_ConvergedCharging Service; SBI representation

Figure 4.1.1: Reference Architecture for the Nchf_ConvergedCharging Service; SBI representation
(⇒ copy of original 3GPP image)

4.2 Network functions p. 14

4.2.1 Charging Function (CHF) p. 14

The CHF is responsible for converged online charging and offline charging functionalities. The CHF provides the following:

Quota;
Re-authorisation triggers;
Notification when Charging Domain determines rating conditions is affected or when CHF determines to terminate the charging service;
Receiving service usage reports from NF Service Consumer; and
CDRs generation.

4.2.2 NF Service Consumers p. 14

The NF Service Consumers shall support:

Requesting and receiving the quota(s);
Sending service usage reports; and
Handling quota re-authorisation or abort notifications.