1 Charging Function – Charging Service

Caution:

Deploying charging for 5G with HTTP Gateway (5G CHF) requires a cloud native deployment of ECE and BRM components. The HTTP Gateway can be used only on an ECE cloud native system.

The following table describes the section compliance of 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09).

Section Compliance

Table 1-1 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09) Section Compliance

Section Number Section Status Notes
1 Scope Informational -
2 References Informational -
3 Definitions, symbols and abbreviations Informational -
4 Overview Supported -
5 Services offered by CHF Supported -
5.1 Introduction Supported -
5.2 Nchf_ConvergedCharging service Supported -
5.2.1 Service description Supported -
5.2.2 Service operations Supported -
5.2.2.1 Introduction Supported -
5.2.2.2 Nchf_ConvergedCharging_Create Operation Supported -
5.2.2.3 Nchf_ConvergedCharging_Update Operation Supported -
5.2.2.4 Nchf_ConvergedCharging_Release Operation Supported -
5.2.2.5 Nchf_ConvergedCharging_Notify Operation Supported -
5.3 Nchf_OfflineOnlyCharging service Supported -
5.3.1 Service description Supported -
5.3.2 Service operations Supported -
5.3.2.1 Introduction Supported -
5.3.2.2 Nchf_OfflineOnlyCharging_Create Operation Supported -
5.3.2.3 Nchf_OfflineOnlyCharging_Update Operation Supported -
5.3.2.4 Nchf_OfflineOnlyCharging_Release Operation Supported -
6 API Definitions Supported -
6.1 Nchf_ConvergedCharging Service API Supported -
6.1.1 Introduction Supported -
6.1.2 Usage of HTTP Supported -
6.1.2.1 General Supported -
6.1.2.2 HTTP standard headers Supported -
6.1.2.2.1 General Supported -
6.1.2.2.2 Content type Supported -
6.1.2.3 HTTP custom headers Supported -
6.1.2.3.1 General Supported Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers.
6.1.3 Resources Supported -
6.1.3.1 Overview Supported -
6.1.3.2 Resource: Charging Data Supported -
6.1.3.2.1 Description Supported -
6.1.3.2.2 Resource Definition Supported -
6.1.3.2.3 Resource Standard Methods Supported -
6.1.3.2.3.1 POST Supported ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 201 (created). For failure ProblemDetails include - 400, 403, 404.
6.1.3.2.4 Resource Custom Operations Not Applicable -
6.1.3.3 Resource: Individual Charging Data Supported -
6.1.3.3.1 Description Supported -
6.1.3.3.2 Resource Definition Supported -
6.1.3.3.3 Resource Standard Methods Not Applicable -
6.1.3.3.4 Resource Custom Operations Supported -
6.1.3.3.4.1 Overview Supported -
6.1.3.3.4.2 Operation: update Supported -
6.1.3.3.4.2.1 Description Supported -
6.1.3.3.4.2.2 Operation Definition Supported ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 200 (OK). For failure ProblemDetails include - 400, 403, 404.
6.1.3.3.4.3 Operation: release Supported -
6.1.3.3.4.3.1 Description Supported -
6.1.3.3.4.3.2 Operation Definition Supported ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.1.4 Custom Operations without associated resources Not Applicable -
6.1.5 Notifications Supported -
6.1.5.1 General Supported -
6.1.5.2 Event Notification Supported -
6.1.5.2.1 Description Supported -
6.1.5.2.2 Target URI Supported -
6.1.5.2.3 Standard Methods Supported -
6.1.5.2.3.1 POST Supported ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.1.6 Data Model Supported -
6.1.6.1 General Supported -
6.1.6.2 Structured data types Supported -
6.1.6.2.1 Common Data Type Supported -
6.1.6.2.1.1

Type ChargingDataRequest

subscriberIdentifier

nfConsumerIdentification

invocationTimeStamp

invocationSequenceNumber

retransmissionIndicator

oneTimeEvent

oneTimeEventType

notifyUri

supportedFeatures

serviceSpecificationInfo

multipleUnitUsage

triggers

Supported

Supported

Supported with Extensions

Supported

Supported

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported

Supported with Extensions

Supported with Extensions

Supported

Supported with Extensions

-
6.1.6.2.1.2

Type ChargingDataResponse

invocationTimeStamp

invocationResult

invocationSequenceNumber

sessionFailover

supportedFeatures

multipleUnitInformation

triggers

Supported

Supported

Supported

Supported

Supported with Extensions

Supported with Extensions

Supported

Supported with Extensions

-
6.1.6.2.1.3

Type ChargingNotifyRequest

notificationType

reauthorizatoinDetails

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.1.4

Type NFIdentification

nodeFunctionality

nFName

nFIPv4Address

nfIPv6Address

nFFqdn

nFPLMNID

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.1.5

Type MultipleUnitUsage

ratingGroup

requestedUnit

usedUnitContainer

Supported

Supported

Supported

Supported

-
6.1.6.2.1.6

Type InvocationResult

error (ProblemDetails)

failureHandling

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.1.7

Type Trigger

triggerType

triggerCategory

timeLimit (DurationSec)

volumeLimit

volumeLimit64

maxNumberOfccc

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

See 6.1.6.3.6 for supported Trigger types.
6.1.6.2.1.8

Type MultipleUnitInformation

resultCode

ratingGroup

grantedUnit

triggers

validityTime (DurationSec)

quotaHandlingTime (DurationSec)

finalUnitIndication

timeQuotaThreshold

volumeQuotaThreshold

unitQuotaThreshold

Supported

Supported

Supported

Supported

Supported with Extensions

Supported

Supported

Supported

Supported with Extensions

Supported

Supported

-
6.1.6.2.1.9

Type RequestedUnit

time

totalVolume

uplinkVolume

downLinkVolume

serviceSpecificUnits

Supported

Supported

Supported

Supported

Supported

Supported

-
6.1.6.2.1.10

Type UsedUnitContainer

serviceId

quotaManagementIndicator

triggers

triggerTimeStamp

time

totalVolume

uplinkVolume

downlinkVolume

serviceSpecificUnits

eventTimeStamps

localSequenceNumber

Supported

Supported

Supported

Supported with Extensions

Supported with Extensions

Supported

Supported

Supported

Supported

Supported

Supported with Extensions

Supported with Extensions

-
6.1.6.2.1.11

Type GrantedUnit

tariffTimeChange

time

totalVolume

uplinkVolume

downlinkVolume

serviceSpecificUnits

Supported

Supported

Supported

Supported

Supported

Supported

Supported

-
6.1.6.2.1.12

Type FinalUnitIndication

finalUnitAction

restrictionFilterRule

filterId

redirectServer

Supported

Supported

Not Supported

Not Supported

Supported

-
6.1.6.2.1.13

Type RedirectServer

redirectAddressType

redirectServerAddress

Supported

Supported

Supported

-
6.1.6.2.1.14

Type ReauthorizationDetails

service (serviceId)

ratingGroup

quotaManagementIndicator

Supported

Supported

Supported

Supported

-
6.1.6.2.1.15

Void

Not applicable

-
6.1.6.2.1.16

Type ChargingNotifyResponse

invocationResult

Not Supported

Not Supported

 
6.1.6.2.2 5G Data Connectivity Specified Data Type Supported -
6.1.6.2.2.1

Type ChargingDataRequest

pDUSessionChargingInformation

roamingQBCInformation

Supported

Supported with Extensions

Supported with Extensions

The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.2

Type ChargingDataResponse

pDUSessionChargingInformation

roamingQBCInformation

Supported

Supported with Extensions

Not Supported with Extensions

The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.3

Type MultipleUnitUsage

uPFID (NfInstanceId)

Supported

Supported with Extensions

-
6.1.6.2.2.4

Type MultipleUnitInformation

uPFID (NfInstanceId)

Supported

Supported with Extensions

-
6.1.6.2.2.5

Type UsedUnitContainer

pDUContainerInformation

Supported

Supported with Extensions

-
6.1.6.2.2.6

Type PDUSessionChargingInformation

chargingId

userInformation

userLocationinfo

userLocationTime

presenceReportingAreaInformation

uetimeZone

pduSessionInformation

unitCountInactivityTime (DurationSec)

rANSecondaryRATUsageReport

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

uetimeZone is used as the request time for the event.
6.1.6.2.2.7

Type UserInformation

servedGPSI

servedPEI

unauthenticatedFlag

roamerInOut

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.8

Type PDUSessionInformation

networkSlicingInfo

pduSessionID

pduType

sscMode

hPlmnId

servingNetworkFunctionID

servingCNPlmnId

ratType

mAPDUNon3GPPRATType

dnnId

dnnSelectionMode

chargingCharacteristics

chargingCharacteristicsSelectionMode

startTime

stopTime

3gppPSDataOffStatus

sessionStopIndicator

pduAddress

Diagnostics

authorizedQoSInformation

subscribedQoSInformation

authorizedSessionAMBR

subscribedSessionAMBR

mAPDUSessionInformation

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.9

Type PDUContainerInformation

timeofFirstUsage

timeofLastUsage

qoSInformation

qoSCharacteristics

afChargingIdentifier

afChargingString

userLocationInformation

uetimeZone

rATType

servingNodeID

presenceReportingAreaInformation

3gppPSDataOffStatus

sponsorIdentity

applicationserviceProviderIdentity

chargingRuleBaseName

mAPDUSteeringFunctionality

mAPDUSteeringMode

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.10

Type NetworkSlicingInfo

sNSSAI

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.11

Type PDUAddress

pduIPv4Address

pduIPv6AddresswithPrefix

pduAddressprefixlength

iPv4dynamicAddressFlag

iPv6dynamicPrefixFlag

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.12

Type ServingNetworkFunctionID

servingNetworkFunctionInformation

aMFId

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.13

Type RoamingQBCInformation

multipleQFIcontainer

uPFID

roamingChargingProfile

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.14

Type MultipleQFIcontainer

triggers

triggerTimestamp

time

totalVolume

uplinkVolume

downlinkVolume

localSequenceNumber

qFIContainerInformation

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.15

Type RoamingChargingProfile

triggers

partialRecordMethod

Supported with Extensions

Supported with Extensions

Supported with Extensions

The out of the box charging flow does not process records for 5G roaming

6.1.6.2.2.16

Type QFIContainerInformation

qFI

reportTime

timeofFirstUsage

timeofLastUsage

qoSInformation

qoSCharacteristics

userLocationInformation

uetimeZone

presenceReportingAreaInformation

rATType

3gppPSDataOffStatus

3gppChargingId

diagnostics

enhancedDiagnostics

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

All are supported only in request, not supported in response

6.1.6.2.2.17

Type RANSecondaryRATUsageReport

rANSecondaryRATType

qosFlowsUsage Reports

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.18

Type QosFlowsUsageReport

qFI

startTimestamp

endTimestamp

downlinkVolume

uplinkVolume

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.2.19

Type MAPDUSessionInformation

mAPDUSessionIndicator

aTSSSCapability

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3 SMS Specified Data Type

Supported with Extensions

-
6.1.6.2.3.1

Type ChargingDataRequest

sMSCharging Information

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.2

Type SMSChargingInformation

originatorInfo

recipientInfo

userEquipment Info

userLocationInfo

uetimeZone

rATType

sMSCAddress

sMDataCodingScheme

sMMessageType

sMReplyPathRequested

sMUserDataHeader

sMStatus

sMDischargeTime

numberofMessagesSent

sMServiceType

sMSequenceNumber

sMSresult

submissionTime

sMpriority

messageReference

messageSize

messageClass

deliveryReportRequested

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.3

Type OriginatorInfo

originatorSUPI

originatorGPSI

originatorOtherAddress

originatorReceivedAddress

originatorSCCPAddress

sMOriginatorInterface

sMOriginatorProtocolId

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.4

Type RecipientInfo

recipientSUPI

recipientGPSI

recipientOtherAddress

recipientReceivedAddress

recipientSCCPAddress

sMDestinationInterface

sMRecipientProtocolId

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.5

Type SMAddressInfo

sMaddressType

sMaddressData

sMaddressDomain

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.6

Type RecipientAddress

recipientAddressInfo

sMaddresseeType

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.7

Type MessageClass

classIdentifier

tokenText

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.8

Type SMAddressDomain

domainName

3GPPIMSIMCCMNC

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.3.9

Type SMInterface

interfaceId

interfaceText

interfacePort

interfaceType

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.2.4 5G connection and mobility Specified Data

Not Supported

-
6.1.6.2.4.1

Type ChargingDataRequest

ChargingDataRequest

ChargingDataRequest

ChargingDataRequest

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.4.2 Type ChargingDataResponse Not Supported -
6.1.6.2.4.3

Type RegistrationChargingInformation

registrationMessagetype

userInformation

userLocationinfo

uetimeZone

rATType

5gMMCapability

mICOModeIndication

smsIndication

taiList

serviceAreaRestriction

requestedNSSAI

allowedNssai

rejectedNSSAI

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.4.4

Type N2ConnectionChargingInformation

n2ConnectionMessageType

userInformation

userLocationinfo

uetimeZone

rATType

amfUeNgapId

ranUeNgapId

ranNodeId

restrictedRatList

forbiddenAreaList

serviceAreaRestriction

restrictedCnList

allowedNssai

rrcEstCause

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.4.5

Type LocationReportingChargingInformation

locationReportingMessageType

userInformation

userLocation

infouetimeZone

presenceReportingAreaInformation

rATType

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.5 Exposure Function Northbound API Specified Not Supported -
6.1.6.2.5.1 Type ChargingDataRequest Not Supported -
6.1.6.2.5.1a Type ChargingDataResponse Not Supported -
6.1.6.2.5.2

Type NEFChargingInformation

groupIdentifier

aPIDirection

aPITargetNetworkFunction

aPIResultCode

aPIName

aPIReference

aPIContent

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.6 Network Slice Management (NSM) Specified Data Type Not Supported -
6.1.6.2.6.1

Type ChargingDataRequest

tenantIdentifier

mnSConsumerIdentifier

nSMChargingInformation

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.6.2 Type ChargingDataResponse Not Supported -
6.1.6.2.6.3

Type NSMChargingInformation

managementOperation

idNetworkSliceInstance

listOfServiceProfileChargingInformation

managementOperationStatus

operationalState

administrativeState

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.6.4

Type ServiceProfileChargingInformation

serviceProfileIdentifier

sNSSAIList

latency

availability

resourceSharingLevel

jitter

reliability

maxNumberofUEs

coverageArea

uEMobilityLevel

delayToleranceIndicator

dLThptPerSlice

dLThptPerUE

uLThptPerSlice

uLThptPerUE

maxNumberofPDUsessions

kPIMonitoringList

supportedAccessTechnology

v2XCommunicationModeIndicator

addServiceProfileChargingInfo

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.2.6.5

Type Throughput

guaranteedThpt

maximumThpt

Not Supported

Not Supported

Not Supported

-
6.1.6.2.7 NS performance and analytics Specified Data Type

Not Supported

-
6.1.6.2.7.1

Type ChargingDataRequest

tenantIdentifier

nSPAChargingInformation

Not Supported

Not Supported

Not Supported

-
6.1.6.2.7.2 Type ChargingDataResponse

Not Supported

-
6.1.6.2.7.3

Type UsedUnitContainer

nSPAContainerInformation

Not Supported

Not Supported

-
6.1.6.2.7.4

Type NSPAChargingInformation

singleNSSAI

Not Supported

Not Supported

-
6.1.6.2.7.5

Type NSPAContainerInformation

latency

throughput

maximumPacketLossRate

serviceExperienceStatisticsData

theNumberOfPDUSessions

theNumberOfRegisteredSubscribers

loadLevel

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

-
6.1.6.3 Simple data types and enumerations Supported -
6.1.6.3.1 Introduction Supported -
6.1.6.3.2

Simple data types

Diagnostics

IPFilterRule

N2ConnectionMessageType

LocationReportingMessageType

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

-
6.1.6.3.3 Enumeration: NotificationType Supported -
6.1.6.3.4 Enumeration: NodeFunctionality Supported -
6.1.6.3.5 Enumeration: ChargingCharacteristicsSelectionMode Supported -
6.1.6.3.6 Enumeration: TriggerType Supported FINAL, RAT_CHANGE, and TARIFF_TIME_CHANGE are supported. Other trigger types are supported with extensions.
6.1.6.3.7 Enumeration: FinalUnitAction Supported -
6.1.6.3.8 Enumeration: RedirectAddressType Supported -
6.1.6.3.9 Enumeration: TriggerCategory Supported -
6.1.6.3.10 Enumeration: QuotaManagementIndicator Supported -
6.1.6.3.11 Enumeration: FailureHandling Supported -
6.1.6.3.12 Enumeration: SessionFailover Supported -
6.1.6.3.13 Enumeration: 3GPPPSDataOffStatus Supported -
6.1.6.3.14 Enumeration: ResultCode Supported -
6.1.6.3.15 Enumeration: PartialRecordMethod Supported -
6.1.6.3.16 Enumeration: RoamerInOut Supported -
6.1.6.3.17 Void Supported -
6.1.6.3.18 Enumeration: SMMessageType Supported -
6.1.6.3.19 Enumeration: SMPriority Supported -
6.1.6.3.20 Enumeration: DeliveryReportRequested Supported -
6.1.6.3.21 Enumeration: InterfaceType Supported -
6.1.6.3.22 Enumeration: ClassIdentifier Supported -
6.1.6.3.23 Enumeration: SMAddressType Supported -
6.1.6.3.24 Enumeration: SMAddresseeType Supported -
6.1.6.3.25 Enumeration: SMServiceType Supported -
6.1.6.3.26 Enumeration: ReplyPathRequested Supported -
6.1.6.3.27 Enumeration: DnnSelectionMode Supported -
6.1.6.3.28 Enumeration: EventType Supported -
6.1.6.3.29 Enumeration: MICOModeIndication Supported -
6.1.6.3.30 Enumeration: RegistrationMessageType Supported -
6.1.6.3.31 Enumeration: SmsIndication Supported -
6.1.6.3.32 Enumeration: APIDirection Supported -
6.1.6.3.33 Enumeration: ManagementOperation Supported -
6.1.6.3.34 Enumeration: ManagementOperationStatus Supported -
6.1.6.4 Data types describing alternative data types or combinations of data types Not Applicable -
6.1.6.5 Binary data Not Applicable -
6.1.7 Error handling Supported -
6.1.7.1 General Supported -
6.1.7.2 Protocol Errors Not Applicable -
6.1.7.3 Application errors Supported -
6.1.8 Feature negotiation Not Supported -
6.2 Nchf_OfflineOnlyCharging Service API Supported -
6.2.1 Introduction Supported -
6.2.2 Usage of HTTP Supported -
6.2.3 Resources Supported -
6.2.3.1 Overview Supported -
6.2.3.2 Resource: Charging Data Supported -
6.2.3.2.1 Description Supported -
6.2.3.2.2 Resource Definition Supported -
6.2.3.2.3 Resource Standard Methods Supported -
6.2.3.2.3.1 POST Supported ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 201 (created). For failure ProblemDetails include - 400, 403, and 404.
6.2.3.2.4 Resource Custom Operations Not Applicable -
6.2.3.3 Resource: Individual Offline Only Charging Data Supported -
6.2.3.3.1 Description Supported -
6.2.3.3.2 Resource Definition Supported -
6.2.3.3.3 Resource Standard Methods Not Applicable -
6.2.3.3.4 Resource Custom Operations Supported -
6.2.3.3.4.1 Overview Supported -
6.2.3.3.4.2 Operation: update Supported -
6.2.3.3.4.2.1 Description Supported -
6.2.3.3.4.2.2 Operation Definition Supported ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 200 (OK). For failure ProblemDetails include - 400, 403, and 404.
6.2.3.3.4.3 Operation: release Supported -
6.2.3.3.4.3.1 Description Supported -
6.2.3.3.4.3.2 Operation Definition Supported ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.2.4 Custom Operations without associated resources Not Applicable -
6.2.5 Data Model Supported -
6.2.5.1 General Supported -
6.2.5.2 Structured data types Supported -
6.2.5.2.1 Common Data Type Supported -
6.2.5.2.1.1

Type ChargingDataRequest

subscriberIdentifier

nfConsumerIdentification

invocationTimeStamp

invocationSequenceNumber

serviceSpecificationInformation

multipleUnitUsage

triggers

Supported

Supported

Supported with Extensions

Supported

Supported

Supported with Extensions

Supported

Supported with Extensions

-
6.2.5.2.1.2

Type ChargingDataResponse

invocationTimeStamp

invocationResult

invocationSequenceNumber

sessionFailover

triggers

Supported

Supported

Supported

Supported

Supported with Extensions

Supported with Extensions

-
6.2.5.2.1.3

Type MultipleUnitUsage

ratingGroup

usedUnitContainer

Supported

Supported

Supported

-
6.2.5.2.1.4

Type UsedUnitContainer

serviceId

triggers

triggerTimeStamp

time

totalVolume

uplinkVolume

downlinkVolume

serviceSpecificUnits

eventTimeStamps

localSequenceNumber

Supported

Supported

Supported

Supported with Extensions

Supported

Supported

Supported

Supported

Supported

Supported with Extensions

Supported with Extensions

-
6.2.5.2.1.5

Type Trigger

triggerType

triggerCategory

timeLimit (DurationSec)

volumeLimit64

eventLimit

maxNumberOfccc

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

Supported with Extensions

See 6.2.5.3.5 for supported Trigger types.
6.2.5.2.2 5G Data Connectivity Specified Data Type Supported -
6.2.5.2.2.1 Type ChargingDataRequest - Same as 6.1.6.2.2.1
6.2.5.2.2.2 Type ChargingDataResponse - Same as 6.2.5.2.1.2
6.2.5.2.2.3 Type MultipleUnitUsage - Same as 6.2.5.2.1.3
6.2.5.2.2.4 Type UsedUnitContainer - Same as 6.2.5.2.1.4
6.2.5.2.2.5 Type PDUSessionChargingInformation - Same as 6.1.6.2.2.6
6.2.5.2.2.6 Type UserInformation - Same as 6.1.6.2.2.7
6.2.5.2.2.7 Type PDUSessionInformation - Same as 6.1.6.2.2.8
6.2.5.2.2.8 Type PDUContainerInformation - Same as 6.1.6.2.2.9
6.2.5.2.2.9 Type NetworkSlicingInfo - Same as 6.1.6.2.2.10
6.2.5.2.2.10 Type PDUAddress - Same as 6.1.6.2.2.11
6.2.5.2.2.11 Type ServingNetworkFunctionID - Same as 6.1.6.2.2.12
6.2.5.2.2.12 Type RoamingQBCInformation - Same as 6.1.6.2.2.13
6.2.5.2.2.13 Type MultipleQFIcontainer - Same as 6.1.6.2.2.14
6.2.5.2.2.14 Type RoamingChargingProfile - Same as 6.1.6.2.2.15
6.2.5.2.2.15 Type QFIContainerInformation - Same as 6.1.6.2.2.16
6.2.5.2.2.16 Type RANSecondaryRATUsageReport - Same as 6.1.6.2.2.17
6.2.5.2.2.17 Type QosFlowsUsageReport - Same as 6.1.6.2.2.18
6.2.5.3 Simple data types and enumerations Supported -
6.2.5.3.1 Introduction Supported -
6.2.5.3.2 Simple data types - Same as 6.1.6.3.2
6.2.5.3.3 Enumeration: ChargingCharacteristicsSelectionMode - Same as 6.1.6.3.5
6.2.5.3.4 Enumeration: NodeFunctionality Supported -
6.2.5.3.5 Enumeration: TriggerType Supported FINAL, RAT_CHANGE and TARIFF_TIME_CHANGE are supported. Other trigger types are supported with extensions.
6.2.5.3.6 Enumeration: ResultCode Supported -
6.2.5.3.7 Enumeration: 3GPPPSDataOffStatus - Same as 6.1.6.3.13
6.2.5.3.8 Enumeration: PartialRecordMethod - Same as 6.1.6.3.15
6.2.5.3.9 Enumeration: RoamerInOut - Same as 6.1.6.3.16
6.2.5.3.10 Enumeration: SubscriberIdentityType - Same as 6.1.6.3.17
6.2.6 Error handling Supported -
6.2.6.1 General Supported -
6.2.6.2 Protocol Errors Not Applicable -
6.2.6.3 Application errors Supported -
6.2.7 Feature negotiation Not Supported -
7 Bindings of CDR field, Information Element and Resource Attribute Supported -
7.0 General Supported -
7.1 Bindings of common CDR field, Information Element and Resource Attribute Supported -
7.2 Bindings for 5G data connectivity Supported -
7.3 Bindings for SMS charging Not Supported -
7.4 Bindings for 5G connection and mobility Not Supported -
7.5 Bindings for Exposure Function Northbound API charging Not Supported -
7.6 Bindings for NS performance and Analytics charging Not Supported -
8.0 Security Not Supported OAuth2 is not supported.

Response Codes

Table 1-2 Response Codes

Response codes Description
201 Created (Create)

The creation of a Charging Data resource is confirmed, and a representation of that resource is returned.

The Charging Data resource is created and returned successfully.

The representation of created resource is identified via Location header field in the 201 response.

200 OK (Updates)

The modification of a Charging Data resource is confirmed, and a representation of that resource is returned.

The Charging Data resource which is modified and returned successfully.

204 No Content (Release) The Charging Data resource matching the ChargingDataRef is modified and then released.
400 Bad Request

CHARGING_FAILED: The HTTP request is rejected because the set of session or subscriber information needed by the CHF for charging or CDR creation is incomplete or erroneous or not available (for example, Rating Group, subscriber information).

RE_AUTHORIZATION_FAILED: The HTTP request is rejected because the set of information needed by the NF Consumer (CTF) to report the usage is incomplete or erroneous or not available.

403 Forbidden

CHARGING_NOT_APPLICABLE: The HTTP request is rejected by the CHF since it has been determined that the service can be granted to the end user without any charging or CDR creation.

END_USER REQUEST_DENIED: The HTTP request is denied by the CHF due to restrictions or limitations related to the end-user.

QUOTA_LIMIT_REACHED: The HTTP request denied by the CHF because the end user's account could not cover the requested service. If the request contained used units they are deducted, if applicable.

END_USER_REQUEST_REJECTED: The HTTP request rejected by the CHF due to end-user restrictions or limitations.

404 Not Found USER_UNKNOWN: The HTTP request is rejected because the end user specified in the request cannot be served by the CHF.

500 Internal Server Error

Common Application Error