5G CHF

Questa guida funge da dichiarazione di conformità dell’implementazione del protocollo 5G CHF.

Categoria:

Sviluppo e integrazione

Argomenti in questo documento:

Introduzione
- Come interpretare lo stato nelle sezioni di conformità
Charging Function – Charging Service
- Conformità della sezione
- Codici di risposta
Charging Function – Spending Limit Control Service
- Conformità della sezione
- Codici di risposta
Charging Function – Interactions with Network Repository Function (NRF)
- Conformità della sezione
Formato CHF-CDR

Introduzione

The 5G CHF includes Nchf interfaces to enable converged charging and spending limit control for policy management. Interactions with the Network Repository Function are also outlined here.

Come interpretare lo stato nelle sezioni di conformità

La tabella seguente descrive the meaning of the status in section compliance sections.

Stato	Significato
Supportato	Application supports functionality. Application supports the attribute and is mapped to the charging function. The attribute is received in the request and used in the charging flows. This attribute is sent in the response as indicated by the specifications. Optionally, you can utilize this attribute for event storage and to inform charging decisions.
Supportato con estensioni	Application supports functionality with extension. The application supports the attribute and can be optionally utilized to select a price. The attribute is received in the request and is not used in the out-of-the-box charging flow. The attribute may or may not be sent in the response. You have an option to leverage available extensions in the charging flow to achieve the intended functionality. You can also prefer to use this attribute for storing in the event, and for making charging decisions.
Non supportato	Application does not support the functionality or the attribute.
Non applicabile	The section is not applicable for the implementation.
Informativo	This section serves solely for informational purposes.

Charging Function – Charging Service

Conformità della sezione

La tabella seguente contiene the description of the section compliance of the 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09):

Table 1-1: 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09) Conformità della sezione

Numero sezione	Sezione	Stato	Note
1	Scope	Informativo	-
2	References	Informativo	-
3	Definitions, symbols and abbreviations	Informativo	-
4	Overview	Supportato	-
5	Services offered by CHF	Supportato	-
5.1	Introduction	Supportato	-
5.2	Nchf_ConvergedCharging service	Supportato	-
5.2.1	Service description	Supportato	-
5.2.2	Service operations	Supportato	-
5.2.2.1	Introduction	Supportato	-
5.2.2.2	Nchf_ConvergedCharging_Create Operation	Supportato	-
5.2.2.3	Nchf_ConvergedCharging_Update Operation	Supportato	-
5.2.2.4	Nchf_ConvergedCharging_Release Operation	Supportato	-
5.2.2.5	Nchf_ConvergedCharging_Notify Operation	Supportato	-
5.3	Nchf_OfflineOnlyCharging service	Supportato	-
5.3.1	Service description	Supportato	-
5.3.2	Service operations	Supportato	-
5.3.2.1	Introduction	Supportato	-
5.3.2.2	Nchf_OfflineOnlyCharging_Create Operation	Supportato	-
5.3.2.3	Nchf_OfflineOnlyCharging_Update Operation	Supportato	-
5.3.2.4	Nchf_OfflineOnlyCharging_Release Operation	Supportato	-
6	API Definitions	Supportato	-
6.1	Nchf_ConvergedCharging Service API	Supportato	-
6.1.1	Introduction	Supportato	-
6.1.2	Usage of HTTP	Supportato	-
6.1.2.1	General	Supportato	-
6.1.2.2	HTTP standard headers	Supportato	-
6.1.2.2.1	General	Supportato	-
6.1.2.2.2	Content type	Supportato	-
6.1.2.3	HTTP custom headers	Supportato	Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers.
6.1.2.3.1	General	Supportato	-
6.1.3	Resources	Supportato	-
6.1.3.1	Overview	Supportato	-
6.1.3.2	Resource: Charging Data	Supportato	-
6.1.3.2.1	Description	Supportato	-
6.1.3.2.2	Resource Definition	Supportato	-
6.1.3.2.3	Resource Standard Methods	Supportato	-
6.1.3.2.3.1	POST	Supportato	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	Non applicabile	-
6.1.3.3	Resource: Individual Charging Data	Supportato	-
6.1.3.3.1	Description	Supportato	-
6.1.3.3.2	Resource Definition	Supportato	-
6.1.3.3.3	Resource Standard Methods	Non applicabile	-
6.1.3.3.4	Resource Custom Operations	Supportato	-
6.1.3.3.4.1	Overview	Supportato	-
6.1.3.3.4.2	Operation: update	Supportato	-
6.1.3.3.4.2.1	Description	Supportato	-
6.1.3.3.4.2.2	Operation Definition	Supportato	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	release	Supportato	-
6.1.3.3.4.3.1	Description	Supportato	-
6.1.3.3.4.3.2	Operation Definition	Supportato	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	Non applicabile	-
6.1.5	Notifications	Supportato	-
6.1.5.1	General	Supportato	-
6.1.5.2	Event Notification	Supportato	-
6.1.5.2.1	Description	Supportato	-
6.1.5.2.2	Target URI	Supportato	-
6.1.5.2.3	Standard Methods	Supportato	-
6.1.5.2.3.1	POST	Supportato	ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.1.6	Data Model	Supportato	-
6.1.6.1	General	Supportato	-
6.1.6.2	Structured data types	Supportato	-
6.1.6.2.1	Common Data Type	Supportato	-
6.1.6.2.1.1	Type ChargingDataRequest	Supportato
	subscriberIdentifier	Supportato con estensioni
	nfConsumerIdentification	Supportato con estensioni
	invocationTimeStamp	Supportato
	invocationSequenceNumber	Supportato
	retransmissionIndicator	Supportato con estensioni
	oneTimeEvent	Supportato con estensioni
	oneTimeEventType	Supportato con estensioni
	notifyUri	Supportato con estensioni
	supportedFeatures	Supportato
	serviceSpecificationInfo	Supportato con estensioni
	multipleUnitUsage	Supportato con estensioni
	triggers	Supportato
6.1.6.2.1.2	Type ChargingDataResponse	Supportato
	invocationTimeStamp	Supportato
	invocationResult	Supportato con estensioni
	invocationSequenceNumber	Supportato
	sessionFailover	Supportato
	supportedFeatures	Supportato con estensioni
	multipleUnitInformation	Supportato con estensioni
	triggers	Supportato
6.1.6.2.1.3	Type ChargingNotifyRequest	Supportato con estensioni
	notificationType	Supportato con estensioni
	reauthorizatoinDetails	Supportato con estensioni
6.1.6.2.1.4	Type NFIdentification	Supportato con estensioni
	nodeFunctionality	Supportato con estensioni
	nFName	Supportato con estensioni
	nFIPv4Address	Supportato con estensioni
	nfIPv6Address	Supportato con estensioni
	nFFqdn	Supportato con estensioni
	nFPLMNID	Supportato con estensioni
6.1.6.2.1.5	Type MultipleUnitUsage	Supportato
	ratingGroup	Supportato
	requestedUnit	Supportato
	usedUnitContainer	Supportato
6.1.6.2.1.6	Type InvocationResult	Supportato con estensioni
	error (ProblemDetails)	Supportato con estensioni
	failureHandling	Supportato con estensioni
6.1.6.2.1.7	Type Trigger	Supportato	See 6.1.6.3.6 for supported Trigger types.
	triggerType	Supportato con estensioni
	triggerCategory	Supportato con estensioni
	timeLimit (DurationSec)	Supportato con estensioni
	volumeLimit	Supportato con estensioni
	volumeLimit64	Supportato con estensioni
	maxNumberOfccc	Supportato con estensioni
6.1.6.2.1.8	Type MultipleUnitInformation	Supportato
	resultCode	Supportato
	ratingGroup	Supportato
	grantedUnit	Supportato
	triggers	Supportato
	validityTime (DurationSec)	Supportato con estensioni
	quotaHandlingTime (DurationSec)	Supportato
	finalUnitIndication	Supportato
	timeQuotaThreshold	Supportato
	volumeQuotaThreshold	Supportato con estensioni
	unitQuotaThreshold	Supportato con estensioni
6.1.6.2.1.9	Type RequestedUnit	Supportato
	time	Supportato
	totalVolume	Supportato
	uplinkVolume	Supportato
	downLinkVolume	Supportato
	serviceSpecificUnits	Supportato
6.1.6.2.1.10	Type UsedUnitContainer	Supportato
	serviceId	Supportato
	quotaManagementIndicator	Supportato
	triggers	Supportato
	triggerTimeStamp	Supportato con estensioni
	time	Supportato con estensioni
	totalVolume	Supportato
	uplinkVolume	Supportato
	downlinkVolume	Supportato
	serviceSpecificUnits	Supportato
	eventTimeStamps	Supportato con estensioni
	localSequenceNumber	Supportato con estensioni
6.1.6.2.1.11	Type GrantedUnit	Supportato
	tariffTimeChange	Supportato
	time	Supportato
	totalVolume	Supportato
	uplinkVolume	Supportato
	downlinkVolume	Supportato
	serviceSpecificUnits	Supportato
6.1.6.2.1.12	Type FinalUnitIndication	Supportato
	finalUnitAction	Supportato
	restrictionFilterRule	Non supportato
	filterId	Non supportato
	redirectServer	Supportato
6.1.6.2.1.13	Type RedirectServer	Supportato
	redirectAddressType	Supportato
	redirectServerAddress	Supportato
6.1.6.2.1.14	Type ReauthorizationDetails	Supportato
	service (serviceId)	Supportato
	ratingGroup	Supportato
	quotaManagementIndicator	Supportato
6.1.6.2.1.15	Void	Non applicabile
6.1.6.2.1.16	Type ChargingNotifyResponse	Non supportato
	invocationResult	Non supportato
6.1.6.2.2	5G Data Connectivity Specified Data Type	Supportato	-
6.1.6.2.2.1	ChargingDataRequest	Supportato	The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.2	ChargingDataResponse	Supportato con estensioni	The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.3	MultipleUnitUsage	Supportato con estensioni	-
6.1.6.2.2.4	MultipleUnitInformation	Supportato con estensioni	-
6.1.6.2.2.5	UsedUnitContainer	Supportato con estensioni	-
6.1.6.2.2.6	PDUSessionChargingInformation	Supportato con estensioni	uetimeZone is used as the request time for the event.
6.1.6.2.2.7	UserInformation	Supportato con estensioni	-
6.1.6.2.2.8	PDUSessionInformation	Supportato con estensioni	-
6.1.6.2.2.9	PDUContainerInformation	Supportato con estensioni	-
6.1.6.2.2.10	NetworkSlicingInfo	Supportato con estensioni	-
6.1.6.2.2.11	PDUAddress	Supportato con estensioni	-
6.1.6.2.2.12	ServingNetworkFunctionID	Supportato con estensioni	-
6.1.6.2.2.13	RoamingQBCInformation	Supportato con estensioni	-
6.1.6.2.2.14	MultipleQFIcontainer	Supportato con estensioni	-
6.1.6.2.2.15	RoamingChargingProfile	Supportato con estensioni	The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.16	QFIContainerInformation	Supportato con estensioni	All are supported only in request, not supported in response
6.1.6.2.2.17	RANSecondaryRATUsageReport	Supportato con estensioni	-
6.1.6.2.2.18	QosFlowsUsageReport	Supportato con estensioni	-
6.1.6.2.2.19	MAPDUSessionInformation	Supportato con estensioni	-
6.1.6.2.3	SMS Specified Data Type	Supportato con estensioni	-
6.1.6.2.3.1	ChargingDataRequest	Supportato con estensioni	-
6.1.6.2.3.2	SMSChargingInformation	Supportato con estensioni	-
6.1.6.2.3.3	OriginatorInfo	Supportato con estensioni	-
6.1.6.2.3.4	RecipientInfo	Supportato con estensioni	-
6.1.6.2.3.5	SMAddressInfo	Supportato con estensioni	-
6.1.6.2.3.6	RecipientAddress	Supportato con estensioni	-
6.1.6.2.3.7	MessageClass	Supportato con estensioni	-
6.1.6.2.3.8	SMAddressDomain	Supportato con estensioni	-
6.1.6.2.3.9	SMInterface	Supportato con estensioni	-
6.1.6.2.4	5G connection and mobility Specified Data	Non supportato	-
6.1.6.2.4.1	ChargingDataRequest	Non supportato	-
6.1.6.2.4.2	ChargingDataResponse	Not Supportato con estensioni	-
6.1.6.2.4.3	Type RegistrationChargingInformation	Non supportato
	registrationMessagetype	Non supportato
	userInformation	Non supportato
	userLocationinfo	Non supportato
	uetimeZone	Non supportato
	rATType	Non supportato
	5gMMCapability	Non supportato
	mICOModeIndication	Non supportato
	smsIndication	Non supportato
	taiList	Non supportato
	serviceAreaRestriction	Non supportato
	requestedNSSAI	Non supportato
	allowedNssai	Non supportato
	rejectedNSSAI	Non supportato
	-	Non supportato
6.1.6.2.4.4	Type N2ConnectionChargingInformation	Non supportato
	n2ConnectionMessageType	Non supportato
	userInformation	Non supportato
	userLocationinfo	Non supportato
	uetimeZone	Non supportato
	rATType	Non supportato
	amfUeNgapId	Non supportato
	ranUeNgapId	Non supportato
	ranNodeId	Non supportato
	restrictedRatList	Non supportato
	forbiddenAreaList	Non supportato
	serviceAreaRestriction	Non supportato
	restrictedCnList	Non supportato
	allowedNssai	Non supportato
	rrcEstCause	Non supportato
	-	Non supportato
6.1.6.2.4.5	Type LocationReportingChargingInformation	Non supportato
	locationReportingMessageType	Non supportato
	userInformation	Non supportato
	userLocation	Non supportato
	infouetimeZone	Non supportato
	presenceReportingAreaInformation	Non supportato
	rATType	Non supportato
	-	Non supportato
6.1.6.2.5	Exposure Function Northbound API Specified	Non supportato
	-	Non supportato
6.1.6.2.5.1	Type ChargingDataRequest	Non supportato

6.1.6.2.5.1a	Type ChargingDataResponse	Non supportato

6.1.6.2.5.2	Type NEFChargingInformation	Non supportato
	groupIdentifier	Non supportato
	aPIDirection	Non supportato
	aPITargetNetworkFunction	Non supportato
	aPIResultCode	Non supportato
	aPIName	Non supportato
	aPIReference	Non supportato
	aPIContent	Non supportato

6.1.6.2.6	Network Slice Management (NSM) Specified Data Type	Non supportato

6.1.6.2.6.1	Type ChargingDataRequest	Non supportato
	tenantIdentifier	Non supportato
	mnSConsumerIdentifier	Non supportato
	nSMChargingInformation	Non supportato

6.1.6.2.6.2	Type ChargingDataResponse	Non supportato

6.1.6.2.6.3	Type NSMChargingInformation	Non supportato
	managementOperation	Non supportato
	idNetworkSliceInstance	Non supportato
	listOfServiceProfileChargingInformation	Non supportato
	managementOperationStatus	Non supportato
	operationalState	Non supportato
	administrativeState	Non supportato

6.1.6.2.6.4	Type ServiceProfileChargingInformation	Non supportato
	serviceProfileIdentifier	Non supportato
	sNSSAIList	Non supportato
	latency	Non supportato
	availability	Non supportato
	resourceSharingLevel	Non supportato
	jitter	Non supportato
	reliability	Non supportato
	maxNumberofUEs	Non supportato
	coverageArea	Non supportato
	uEMobilityLevel	Non supportato
	delayToleranceIndicator	Non supportato
	dLThptPerSlice	Non supportato
	dLThptPerUE	Non supportato
	uLThptPerSlice	Non supportato
	uLThptPerUE	Non supportato
	maxNumberofPDUsessions	Non supportato
	kPIMonitoringList	Non supportato
	supportedAccessTechnology	Non supportato
	v2XCommunicationModeIndicator	Non supportato
	addServiceProfileChargingInfo	Non supportato

6.1.6.2.6.5	Type Throughput	Non supportato
	guaranteedThpt	Non supportato
	maximumThpt	Non supportato

6.1.6.2.7	NS performance and analytics Specified Data Type	Non supportato
6.1.6.2.7.1	Type ChargingDataRequest	Non supportato
	tenantIdentifier	Non supportato
	nSPAChargingInformation	Non supportato
6.1.6.2.7.2	Type ChargingDataResponse	Non supportato
6.1.6.2.7.3	Type UsedUnitContainer	Non supportato
	nSPAContainerInformation	Non supportato
6.1.6.2.7.4	Type NSPAChargingInformation	Non supportato
	singleNSSAI	Non supportato
6.1.6.2.7.5	Type NSPAContainerInformation	Non supportato
	latency	Non supportato
	throughput	Non supportato
	maximumPacketLossRate	Non supportato
	serviceExperienceStatisticsData	Non supportato
	theNumberOfPDUSessions	Non supportato
	theNumberOfRegisteredSubscribers	Non supportato
	loadLevel	Non supportato
6.1.6.3	Simple data types and enumerations	Supportato
6.1.6.3.1	Introduction	Supportato
6.1.6.3.2	Simple data types	Supportato con estensioni
	Diagnostics	Supportato con estensioni
	IPFilterRule	Supportato con estensioni
	N2ConnectionMessageType	Supportato con estensioni
	LocationReportingMessageType	Supportato con estensioni
6.1.6.3.3	Enumeration: NotificationType	Supportato
6.1.6.3.4	Enumeration: NodeFunctionality	Supportato
6.1.6.3.5	Enumeration: ChargingCharacteristicsSelectionMode	Supportato
6.1.6.3.6	Enumeration: TriggerType	Supportato	FINAL, RAT_CHANGE, and TARIFF_TIME_CHANGE are supported. Other trigger types are supported with extensions.
6.1.6.3.7	Enumeration: FinalUnitAction	Supportato
6.1.6.3.8	Enumeration: RedirectAddressType	Supportato
6.1.6.3.9	Enumeration: TriggerCategory	Supportato
6.1.6.3.10	Enumeration: QuotaManagementIndicator	Supportato
6.1.6.3.11	Enumeration: FailureHandling	Supportato
6.1.6.3.12	Enumeration: SessionFailover	Supportato
6.1.6.3.13	Enumeration: 3GPPPSDataOffStatus	Supportato
6.1.6.3.14	Enumeration: ResultCode	Supportato
6.1.6.3.15	Enumeration: PartialRecordMethod	Supportato
6.1.6.3.16	Enumeration: RoamerInOut	Supportato
6.1.6.3.17	Void	Supportato
6.1.6.3.18	Enumeration: SMMessageType	Supportato
6.1.6.3.19	Enumeration: SMPriority	Supportato
6.1.6.3.20	Enumeration: DeliveryReportRequested	Supportato
6.1.6.3.21	Enumeration: InterfaceType	Supportato
6.1.6.3.22	Enumeration: ClassIdentifier	Supportato
6.1.6.3.23	Enumeration: SMAddressType	Supportato
6.1.6.3.24	Enumeration: SMAddresseeType	Supportato
6.1.6.3.25	Enumeration: SMServiceType	Supportato
6.1.6.3.26	Enumeration: ReplyPathRequested	Supportato
6.1.6.3.27	Enumeration: DnnSelectionMode	Supportato
6.1.6.3.28	Enumeration: EventType	Supportato
6.1.6.3.29	Enumeration: MICOModeIndication	Supportato
6.1.6.3.30	Enumeration: RegistrationMessageType	Supportato
6.1.6.3.31	Enumeration: SmsIndication	Supportato
6.1.6.3.32	Enumeration: APIDirection	Supportato
6.1.6.3.33	Enumeration: ManagementOperation	Supportato
6.1.6.3.34	Enumeration: ManagementOperationStatus	Supportato
6.1.6.4	Data types describing alternative data types or combinations of data types	Non applicabile
6.1.6.5	Binary data	Non applicabile
6.1.7	Error handling	Supportato
6.1.7.1	General	Supportato
6.1.7.2	Protocol Errors	Non applicabile
6.1.7.3	Application errors	Supportato
6.1.8	Feature negotiation	Non supportato
6.2	Nchf_OfflineOnlyCharging Service API	Supportato
6.2.1	Introduction	Supportato
6.2.2	Usage of HTTP	Supportato
6.2.3	Resources	Supportato
6.2.3.1	Overview	Supportato
6.2.3.2	Resource: Charging Data	Supportato
6.2.3.2.1	Description	Supportato
6.2.3.2.2	Resource Definition	Supportato
6.2.3.2.3	Resource Standard Methods	Supportato
6.2.3.2.3.1	POST	Supportato	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	Non applicabile
6.2.3.3	Resource: Individual Offline Only Charging Data	Supportato
6.2.3.3.1	Description	Supportato
6.2.3.3.2	Resource Definition	Supportato
6.2.3.3.3	Resource Standard Methods	Non applicabile
6.2.3.3.4	Resource Custom Operations	Supportato
6.2.3.3.4.1	Overview	Supportato
6.2.3.3.4.2	Operation: update	Supportato
6.2.3.3.4.2.1	Description	Supportato
6.2.3.3.4.2.2	Operation Definition	Supportato	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	Supportato
6.2.3.3.4.3.1	Description	Supportato
6.2.3.3.4.3.2	Operation Definition	Supportato	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	Non applicabile
6.2.5	Data Model	Supportato
6.2.5.1	General	Supportato
6.2.5.2	Structured data types	Supportato
6.2.5.2.1	Common Data Type	Supportato
6.2.5.2.1.1	Type ChargingDataRequest	Supportato
	subscriberIdentifier	Supportato
	nfConsumerIdentification	Supportato
	invocationTimeStamp	Supportato con estensioni
	invocationSequenceNumber	Supportato
	serviceSpecificationInformation	Supportato
	multipleUnitUsage	Supportato con estensioni
	triggers	Supportato con estensioni	See 6.2.5.3.5 for supported Trigger types.
6.2.5.2.1.2	Type ChargingDataResponse	Supportato
	invocationTimeStamp	Supportato
	invocationResult	Supportato
	invocationSequenceNumber	Supportato
	sessionFailover	Supportato
	triggers	Supportato con estensioni
6.2.5.2.1.3	Type MultipleUnitUsage	Supportato
	ratingGroup	Supportato
	usedUnitContainer	Supportato
6.2.5.2.1.4	Type UsedUnitContainer	Supportato
	serviceId	Supportato
	triggers	Supportato
	triggerTimeStamp	Supportato
	time	Supportato
	totalVolume	Supportato con estensioni
	uplinkVolume	Supportato
	downlinkVolume	Supportato
	serviceSpecificUnits	Supportato
	eventTimeStamps	Supportato con estensioni
	localSequenceNumber	Supportato con estensioni
6.2.5.2.1.5	Type Trigger	Supportato con estensioni
	triggerType	Supportato con estensioni
	triggerCategory	Supportato con estensioni
	timeLimit (DurationSec)	Supportato con estensioni
	volumeLimit64	Supportato con estensioni
	eventLimit	Supportato con estensioni
	maxNumberOfccc	Supportato con estensioni
6.2.5.2.2	5G Data Connectivity Specified Data Type	Supportato
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	Supportato
6.2.5.3.1	Introduction	Supportato
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	Supportato
6.2.5.3.5	Enumeration: TriggerType	Supportato	FINAL, RAT_CHANGE and TARIFF_TIME_CHANGE are supported. Other trigger types are supported with extensions.
6.2.5.3.6	Enumeration: ResultCode	Supportato
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	Supportato
6.2.6.1	General	Supportato
6.2.6.2	Protocol Errors	Non applicabile
6.2.6.3	Application errors	Supportato
6.2.7	Feature negotiation	Non supportato
7	Bindings of CDR field, Information Element and Resource Attribute	Supportato
7.0	General	Supportato
7.1	Bindings of common CDR field, Information Element and Resource Attribute	Supportato
7.2	Bindings for 5G data connectivity	Supportato
7.3	Bindings for SMS charging	Non supportato
7.4	Bindings for 5G connection and mobility	Non supportato
7.5	Bindings for Exposure Function Northbound API charging	Non supportato
7.6	Bindings for NS performance and Analytics charging	Non supportato
8.0	Security	Non supportato	OAuth2 is not supported.

Codici di risposta

Table 1-2: Codici di risposta

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

Charging Function – Spending Limit Control Service

Conformità della sezione

The table provided below outlines the compliance of sections within the 5G System Charging Service as per 3GPP TS 29.594 v16.3.0 (2020-09).

Table 2-1: 5G System Charging Service 3GPP TS 29.594 v16.3.0 (2020-09) Conformità della sezione

Numero sezione	Sezione	Stato	Note
1	Scope	Informativo	-
2	References	Informativo	-
3	Definitions and abbreviations	Informativo	-
4	Nchf_SpendingLimitControl Service	Supportato	-
4.1	Service Description	Supportato	-
4.1.1	Overview	Supportato	-
4.1.2	Service Architecture	Supportato	-
4.1.3	Network Functions	Supportato	-
4.1.3.1	Charging Function (CHF)	Supportato	-
4.1.3.2	NF Service Consumers	Supportato	-
4.2	Service Operations	Supportato	-
4.2.1	Introduction	Supportato	-
4.2.2	Nchf_SpendingLimitControl_Subscribe service operation	Supportato	-
4.2.2.1	General	Supportato	-
4.2.2.2	Initial spending limit retrieval	Supportato	-
4.2.2.3	Intermediate spending limit report retrieval	Supportato	-
4.2.3	Nchf_SpendingLimitControl_Unsubscribe service operation	Supportato	-
4.2.3.1	General	Supportato	-
4.2.3.2	Unsubscribe from spending limit reporting	Supportato	-
4.2.4	Nchf_SpendingLimitControl_Notify service operation	Supportato	-
4.2.4.1	General	Supportato	-
4.2.4.2	Spending limit report	Supportato	-
4.2.4.3	Subscription termination request by CHF	Non supportato	-
5	Nchf_SpendingLimitControl Service API	Supportato	-
5.1	Introduction	Supportato	-
5.2	Usage of HTTP	Supportato	-
5.2.1	General	Supportato	-
5.2.2	HTTP standard headers	Supportato	-
5.2.2.1	General	Supportato	-
5.2.2.2	Content type	Supportato	-
5.2.3	HTTP custom headers	Supportato	Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers.
5.3	Resources	Supportato	-
5.3.1	Resource Structure	Supportato	-
5.3.2	Resource: Spending Limit Retrieval Subscriptions (Collection)	Supportato	-
5.3.2.1	Description	Supportato	-
5.3.2.2	Resource Definition	Supportato	-
5.3.2.3	Resource Standard Methods	Supportato	-
5.3.2.3.1	POST	Supportato	POST request with SpendingLimitContext to create a new individual spending limit retrieval subscription. POST Response to contain SpendingLimitStatus as 201 (Created), ProblemDetails with 400 (Bad Request).
5.3.2.4	Resource Custom Operations	Non applicabile	-
5.3.3	Resource: Individual Spending Limit Retrieval Subscription (Document)	Supportato	-
5.3.3.1	Description	Supportato	-
5.3.3.2	Resource definition	Supportato	-
5.3.3.3	Resource Standard Methods	Supportato	-
5.3.3.3.1	PUT	Supportato	PUT request with SpendingLimitContext to modify the existing individual spending limit retrieval subscription. POST Response to contain SpendingLimitStatus as 200 (OK), ProblemDetails with 400 (Bad Request).
5.3.3.3.2	DELETE	Supportato	DELETE request. DELETE Response to contain 204 (No Content). Successful case: The individual spending limit subscription matching the subscriptionId was deleted.
5.4	Customer Operations without associated resources	Non applicabile	-
5.5	Notifications	Supportato	-
5.5.1	General	Supportato	Terminate is not supported
5.5.2	Spending limit notification	Supportato	-
5.5.2.1	Description	Supportato	-
5.5.2.2	Target URI	Supportato	-
5.5.2.3	Standard Methods	Supportato	-
5.5.2.3.1	POST	Supportato	POST request with SpendingLimitStatus for the policy counters. POST Response to contain 204 (no Content) and the receipt of the notification is acknowledged.
5.5.3	Subscription Termination	Non supportato	-
5.5.3.1	Description	Supportato	-
5.5.3.2	Target URI	Supportato	-
5.5.3.3	Standard Methods	Supportato	-
5.5.3.3.1	POST	Supportato	POST request with SubscriptionTerminationInfo for deletion of a resource. POST Response to contain 204 (no Content) and the receipt of the notification is acknowledged.
5.6	Data Model	Supportato	-
5.6.1	General	Supportato	-
5.6.2	Structured data types	Supportato	-
5.6.2.1	Introduction	Supportato	-
5.6.2.2	Type SpendingLimitContext	Supportato	-
5.6.2.3	Type SpendingLimitStatus	Supportato	-
5.6.2.4	Type PolicyCounterInfo	Supportato	-
5.6.2.5	Type PendingPolicyCounterStatus	Supportato	-
5.6.2.6	Type SubscriptionTerminationInfo	Non supportato	-
5.6.3	Simple data types and enumerations	Supportato	-
5.6.3.1	Introduction	Supportato	-
5.6.3.2	Simple data types	Supportato	-
5.6.3.3	Enumeration: TerminationCause	Non supportato	-
5.7	Error handling	Supportato	-
5.7.1	General	Supportato	-
5.7.2	Protocol Errors	Non applicabile	-
5.7.3	Application Errors	Supportato	-
5.8	Feature negotiation	Non supportato	-
5.9	Security	Non supportato	OAuth2 is not supported.

Codici di risposta

Table 2-2: Codici di risposta

Response codes	Description
201 Created	SUCCESS: The spending limit subscription was created, and spending limit reports are provided.
200 OK	The individual spending limit subscription was modified, and spending limit reports are provided.
204 No Content	Please see individual operations
400 Bad Request	USER_UNKNOWN: The subscriber specified in the request is not known at the CHF and the subscription cannot be created. NO_AVAILABLE_POLICY_COUNTERS: There are no policy counters available for the subscriber at the CHF
500 Internal Server Error	Common Application Error

Charging Function – Interactions with Network Repository Function (NRF)

Conformità della sezione

The table below provides a description of the services supported by CHF as a consumer Network Function for its interaction with NRF, in accordance with the 5G System Network Function Repository Services in 3GPP TS 29.510 v16.5.0 (2020-09).

Table 3-1: Services Supportato by CHF as a Consumer Network Function

Numero sezione	Sezione	Stato	Note
5	Services Offered by the NRF	Supportato
5.1	Introduction	Supportato	Only NFManagement Service with operations NFRegister, NFUpdate, NFDeregister, and NFListRetrieval are supported.
5.2	Nnrf_NFManagement Service	Supportato
5.2.1	Service Description	Supportato
5.2.2	Service Operations	Supportato
5.2.2.1	Introduction	Supportato
5.2.2.2	NFRegister	Supportato
5.2.2.2.1	General	Supportato
5.2.2.2.2	NF (other than NRF) registration to NRF	Supportato
5.2.2.3	NFUpdate	Supportato
5.2.2.3.1	General	Supportato
5.2.2.3.2	NF Heart-Beat	Supportato
5.2.2.4	NFDeregister	Supportato
5.2.2.4.1	General	Supportato
5.2.2.5	NFStatusSubscribe	Non supportato
5.2.2.6	NFStatusNotify	Non supportato
5.2.2.7	NFStatusUnsubscribe	Non supportato
5.2.2.8	NFListRetrieval	Supportato
5.2.2.8.1	General	Supportato
5.2.2.9	NFProfileRetrieval	Non supportato
5.2.2.9.1	General	Non supportato

Formato CHF-CDR

The table below outlines the compliance status of the fields within the 3GPP Charging Function Call Detail Record (CHF-CDR) dal 3GPP TS 32.298 version 16.5.0 specification.

Table 4-1: CHF-CDR Format

Field	Stato
Record Type	Supportato
Recording Network Function ID	Non supportato
Charging Session Identifier	Supportato
Subscriber Identifier	Supportato
NF Consumer Information	Supportato
NF Functionality	Supportato
NF Name	Supportato
NF Address	Supportato
NF PLMN ID	Supportato
Triggers	Supportato
SMF Triggers	Supportato
List of Multiple Unit Usage	Supportato
Rating Group	Supportato
Used Unit Container	Supportato
Service Identifier	Supportato
Quota management Indicator	Supportato
Local Sequence Number	Supportato
Time	Supportato
Uplink Volume	Supportato
Downlink Volume	Supportato
Total Volume	Supportato
Service Specific Units	Supportato
Event Time Stamp	Supportato
Rating Indicator	Supportato
Triggers	Supportato
SMF Triggers	Supportato
Trigger Time Stamp	Supportato
PDU Container Information	Supportato
UPF ID	Supportato
Record Opening Time	Supportato
Duration	Supportato
Record Sequence Number	Supportato
Cause for Record Closing	Supportato
Local Record Sequence Number	Supportato
Record Extensions	Non supportato
Service Specification Information	Supportato
PDU Session Charging Information	Supportato
Roaming QBC Information	Supportato
SMS Charging Information	Supportato
Registration Charging Information	Non supportato
N2 connection charging Information	Non supportato
Location reporting charging Information	Non supportato

Diameter

Radius