5G CHF
Este guia atua como uma declaração de conformidade da implementação do protocolo para o protocolo 5G CHF.
Categoria:
Tópicos neste documento:
- Introdução
- Charging Function – Charging Service
- Charging Function – Spending Limit Control Service
- Charging Function – Interações com Network Repository Function (NRF)
- Formato CHF-CDR
Introdução
O 5G CHF inclui interfaces Nchf para permitir o carregamento convergente e o controle do limite de gastos para o gerenciamento de políticas. As interações com o Network Repository Function também são descritas aqui.
Como Interpretar o Status nas Seções de Conformidade
A tabela a seguir descreve o significado do status nas seções de conformidade de seção.
| Status | Significado |
|---|---|
| Supported | A aplicação suporta a funcionalidade. A aplicação suporta o atributo e este é mapeado para a função de carregamento. O atributo é recebido na requisição e utilizado nos fluxos de carregamento. Este atributo é enviado na resposta conforme indicado pelas especificações. Opcionalmente, você pode utilizar este atributo para armazenamento de eventos e para informar decisões de carregamento. |
| Supported with Extensions | A aplicação suporta a funcionalidade com extensão. A aplicação suporta o atributo e este pode ser opcionalmente utilizado para selecionar um preço. O atributo é recebido na requisição e não é utilizado no fluxo de carregamento padrão (out-of-the-box). O atributo pode ou não ser enviado na resposta. Você tem a opção de aproveitar as extensões disponíveis no fluxo de carregamento para alcançar a funcionalidade pretendida. Você também pode preferir usar este atributo para armazenamento no evento e para tomar decisões de carregamento. |
| Not Supported | A aplicação não suporta a funcionalidade ou o atributo. |
| Not Applicable | A seção não é aplicável para a implementação. |
| Informational | Esta seção serve apenas para fins informativos. |
Charging Function – Charging Service
Conformidade da Seção
A tabela abaixo contém a descrição da conformidade da seção do 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09):
Tabela 1-1: 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09) Section Compliance
| Número da Seção | Seção | Status | Notas |
|---|---|---|---|
| 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 | Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers. |
| 6.1.2.3.1 | General | Supported | - |
| 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 | 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 | Supported | |
| subscriberIdentifier | Supported with Extensions | ||
| nfConsumerIdentification | Supported with Extensions | ||
| invocationTimeStamp | Supported | ||
| invocationSequenceNumber | Supported | ||
| retransmissionIndicator | Supported with Extensions | ||
| oneTimeEvent | Supported with Extensions | ||
| oneTimeEventType | Supported with Extensions | ||
| notifyUri | Supported with Extensions | ||
| supportedFeatures | Supported | ||
| serviceSpecificationInfo | Supported with Extensions | ||
| multipleUnitUsage | Supported with Extensions | ||
| triggers | Supported | ||
| 6.1.6.2.1.2 | Type ChargingDataResponse | Supported | |
| invocationTimeStamp | Supported | ||
| invocationResult | Supported with Extensions | ||
| invocationSequenceNumber | Supported | ||
| sessionFailover | Supported | ||
| supportedFeatures | Supported with Extensions | ||
| multipleUnitInformation | Supported with Extensions | ||
| triggers | Supported | ||
| 6.1.6.2.1.3 | Type ChargingNotifyRequest | Supported with Extensions | |
| notificationType | Supported with Extensions | ||
| reauthorizatoinDetails | Supported with Extensions | ||
| 6.1.6.2.1.4 | Type NFIdentification | Supported with Extensions | |
| nodeFunctionality | Supported with Extensions | ||
| nFName | Supported with Extensions | ||
| nFIPv4Address | Supported with Extensions | ||
| nfIPv6Address | Supported with Extensions | ||
| nFFqdn | Supported with Extensions | ||
| nFPLMNID | Supported with Extensions | ||
| 6.1.6.2.1.5 | Type MultipleUnitUsage | Supported | |
| ratingGroup | Supported | ||
| requestedUnit | Supported | ||
| usedUnitContainer | Supported | ||
| 6.1.6.2.1.6 | Type InvocationResult | Supported with Extensions | |
| error (ProblemDetails) | Supported with Extensions | ||
| failureHandling | Supported with Extensions | ||
| 6.1.6.2.1.7 | Type Trigger | Supported | See 6.1.6.3.6 for supported Trigger types. |
| triggerType | Supported with Extensions | ||
| triggerCategory | Supported with Extensions | ||
| timeLimit (DurationSec) | Supported with Extensions | ||
| volumeLimit | Supported with Extensions | ||
| volumeLimit64 | Supported with Extensions | ||
| maxNumberOfccc | Supported with Extensions | ||
| 6.1.6.2.1.8 | Type MultipleUnitInformation | Supported | |
| resultCode | Supported | ||
| ratingGroup | Supported | ||
| grantedUnit | Supported | ||
| triggers | Supported | ||
| validityTime (DurationSec) | Supported with Extensions | ||
| quotaHandlingTime (DurationSec) | Supported | ||
| finalUnitIndication | Supported | ||
| timeQuotaThreshold | Supported | ||
| volumeQuotaThreshold | Supported with Extensions | ||
| unitQuotaThreshold | Supported with Extensions | ||
| 6.1.6.2.1.9 | Type RequestedUnit | Supported | |
| time | Supported | ||
| totalVolume | Supported | ||
| uplinkVolume | Supported | ||
| downLinkVolume | Supported | ||
| serviceSpecificUnits | Supported | ||
| 6.1.6.2.1.10 | Type UsedUnitContainer | Supported | |
| serviceId | Supported | ||
| quotaManagementIndicator | Supported | ||
| triggers | Supported | ||
| triggerTimeStamp | Supported with Extensions | ||
| time | Supported with Extensions | ||
| totalVolume | Supported | ||
| uplinkVolume | Supported | ||
| downlinkVolume | Supported | ||
| serviceSpecificUnits | Supported | ||
| eventTimeStamps | Supported with Extensions | ||
| localSequenceNumber | Supported with Extensions | ||
| 6.1.6.2.1.11 | Type GrantedUnit | Supported | |
| tariffTimeChange | Supported | ||
| time | Supported | ||
| totalVolume | Supported | ||
| uplinkVolume | Supported | ||
| downlinkVolume | Supported | ||
| serviceSpecificUnits | Supported | ||
| 6.1.6.2.1.12 | Type FinalUnitIndication | Supported | |
| finalUnitAction | Supported | ||
| restrictionFilterRule | Not Supported | ||
| filterId | Not Supported | ||
| redirectServer | Supported | ||
| 6.1.6.2.1.13 | Type RedirectServer | Supported | |
| redirectAddressType | Supported | ||
| redirectServerAddress | Supported | ||
| 6.1.6.2.1.14 | Type ReauthorizationDetails | Supported | |
| service (serviceId) | Supported | ||
| ratingGroup | Supported | ||
| quotaManagementIndicator | Supported | ||
| 6.1.6.2.1.15 | Void | Not applicable | |
| 6.1.6.2.1.16 | Type ChargingNotifyResponse | Not Supported | |
| invocationResult | Not Supported | ||
| 6.1.6.2.2 | 5G Data Connectivity Specified Data Type | Supported | - |
| 6.1.6.2.2.1 | ChargingDataRequest | Supported | The out of the box charging flow does not process records for 5G roaming. |
| 6.1.6.2.2.2 | ChargingDataResponse | Supported with Extensions | The out of the box charging flow does not process records for 5G roaming. |
| 6.1.6.2.2.3 | MultipleUnitUsage | Supported with Extensions | - |
| 6.1.6.2.2.4 | MultipleUnitInformation | Supported with Extensions | - |
| 6.1.6.2.2.5 | UsedUnitContainer | Supported with Extensions | - |
| 6.1.6.2.2.6 | PDUSessionChargingInformation | Supported with Extensions | uetimeZone is used as the request time for the event. |
| 6.1.6.2.2.7 | UserInformation | Supported with Extensions | - |
| 6.1.6.2.2.8 | PDUSessionInformation | Supported with Extensions | - |
| 6.1.6.2.2.9 | PDUContainerInformation | Supported with Extensions | - |
| 6.1.6.2.2.10 | NetworkSlicingInfo | Supported with Extensions | - |
| 6.1.6.2.2.11 | PDUAddress | Supported with Extensions | - |
| 6.1.6.2.2.12 | ServingNetworkFunctionID | Supported with Extensions | - |
| 6.1.6.2.2.13 | RoamingQBCInformation | Supported with Extensions | - |
| 6.1.6.2.2.14 | MultipleQFIcontainer | Supported with Extensions | - |
| 6.1.6.2.2.15 | RoamingChargingProfile | Supported with Extensions | The out of the box charging flow does not process records for 5G roaming. |
| 6.1.6.2.2.16 | QFIContainerInformation | Supported with Extensions | All are supported only in request, not supported in response |
| 6.1.6.2.2.17 | RANSecondaryRATUsageReport | Supported with Extensions | - |
| 6.1.6.2.2.18 | QosFlowsUsageReport | Supported with Extensions | - |
| 6.1.6.2.2.19 | MAPDUSessionInformation | Supported with Extensions | - |
| 6.1.6.2.3 | SMS Specified Data Type | Supported with Extensions | - |
| 6.1.6.2.3.1 | ChargingDataRequest | Supported with Extensions | - |
| 6.1.6.2.3.2 | SMSChargingInformation | Supported with Extensions | - |
| 6.1.6.2.3.3 | OriginatorInfo | Supported with Extensions | - |
| 6.1.6.2.3.4 | RecipientInfo | Supported with Extensions | - |
| 6.1.6.2.3.5 | SMAddressInfo | Supported with Extensions | - |
| 6.1.6.2.3.6 | RecipientAddress | Supported with Extensions | - |
| 6.1.6.2.3.7 | MessageClass | Supported with Extensions | - |
| 6.1.6.2.3.8 | SMAddressDomain | Supported with Extensions | - |
| 6.1.6.2.3.9 | SMInterface | Supported with Extensions | - |
| 6.1.6.2.4 | 5G connection and mobility Specified Data | Not Supported | - |
| 6.1.6.2.4.1 | ChargingDataRequest | Not Supported | - |
| 6.1.6.2.4.2 | ChargingDataResponse | Not Supported with Extensions | - |
| 6.1.6.2.4.3 | Type RegistrationChargingInformation | Not Supported | |
| registrationMessagetype | Not Supported | ||
| userInformation | Not Supported | ||
| userLocationinfo | Not Supported | ||
| uetimeZone | Not Supported | ||
| rATType | Not Supported | ||
| 5gMMCapability | Not Supported | ||
| mICOModeIndication | Not Supported | ||
| smsIndication | Not Supported | ||
| taiList | Not Supported | ||
| serviceAreaRestriction | Not Supported | ||
| requestedNSSAI | Not Supported | ||
| allowedNssai | Not Supported | ||
| rejectedNSSAI | Not Supported | ||
| - | Not Supported | ||
| 6.1.6.2.4.4 | Type N2ConnectionChargingInformation | Not Supported | |
| n2ConnectionMessageType | Not Supported | ||
| userInformation | Not Supported | ||
| userLocationinfo | Not Supported | ||
| uetimeZone | Not Supported | ||
| rATType | Not Supported | ||
| amfUeNgapId | Not Supported | ||
| ranUeNgapId | Not Supported | ||
| ranNodeId | Not Supported | ||
| restrictedRatList | Not Supported | ||
| forbiddenAreaList | Not Supported | ||
| serviceAreaRestriction | Not Supported | ||
| restrictedCnList | Not Supported | ||
| allowedNssai | Not Supported | ||
| rrcEstCause | Not Supported | ||
| - | Not Supported | ||
| 6.1.6.2.4.5 | Type LocationReportingChargingInformation | Not Supported | |
| locationReportingMessageType | Not Supported | ||
| userInformation | Not Supported | ||
| userLocation | Not Supported | ||
| infouetimeZone | Not Supported | ||
| presenceReportingAreaInformation | Not Supported | ||
| rATType | Not Supported | ||
| - | Not Supported | ||
| 6.1.6.2.5 | Exposure Function Northbound API Specified | Not Supported | |
| - | 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 | Not Supported | |
| groupIdentifier | Not Supported | ||
| aPIDirection | Not Supported | ||
| aPITargetNetworkFunction | Not Supported | ||
| aPIResultCode | Not Supported | ||
| aPIName | Not Supported | ||
| aPIReference | Not Supported | ||
| aPIContent | Not Supported | ||
| 6.1.6.2.6 | Network Slice Management (NSM) Specified Data Type | Not Supported | |
| 6.1.6.2.6.1 | Type ChargingDataRequest | Not Supported | |
| tenantIdentifier | Not Supported | ||
| mnSConsumerIdentifier | Not Supported | ||
| nSMChargingInformation | Not Supported | ||
| 6.1.6.2.6.2 | Type ChargingDataResponse | Not Supported | |
| 6.1.6.2.6.3 | Type NSMChargingInformation | Not Supported | |
| managementOperation | Not Supported | ||
| idNetworkSliceInstance | Not Supported | ||
| listOfServiceProfileChargingInformation | Not Supported | ||
| managementOperationStatus | Not Supported | ||
| operationalState | Not Supported | ||
| administrativeState | Not Supported | ||
| 6.1.6.2.6.4 | Type ServiceProfileChargingInformation | Not Supported | |
| serviceProfileIdentifier | Not Supported | ||
| sNSSAIList | Not Supported | ||
| latency | Not Supported | ||
| availability | Not Supported | ||
| resourceSharingLevel | Not Supported | ||
| jitter | Not Supported | ||
| reliability | Not Supported | ||
| maxNumberofUEs | Not Supported | ||
| coverageArea | Not Supported | ||
| uEMobilityLevel | Not Supported | ||
| delayToleranceIndicator | Not Supported | ||
| dLThptPerSlice | Not Supported | ||
| dLThptPerUE | Not Supported | ||
| uLThptPerSlice | Not Supported | ||
| uLThptPerUE | Not Supported | ||
| maxNumberofPDUsessions | Not Supported | ||
| kPIMonitoringList | Not Supported | ||
| supportedAccessTechnology | Not Supported | ||
| v2XCommunicationModeIndicator | Not Supported | ||
| addServiceProfileChargingInfo | Not Supported | ||
| 6.1.6.2.6.5 | Type Throughput | Not Supported | |
| guaranteedThpt | Not Supported | ||
| maximumThpt | Not Supported | ||
| 6.1.6.2.7 | NS performance and analytics Specified Data Type | Not Supported | |
| 6.1.6.2.7.1 | Type ChargingDataRequest | Not Supported | |
| tenantIdentifier | Not Supported | ||
| nSPAChargingInformation | Not Supported | ||
| 6.1.6.2.7.2 | Type ChargingDataResponse | Not Supported | |
| 6.1.6.2.7.3 | Type UsedUnitContainer | Not Supported | |
| nSPAContainerInformation | Not Supported | ||
| 6.1.6.2.7.4 | Type NSPAChargingInformation | Not Supported | |
| singleNSSAI | Not Supported | ||
| 6.1.6.2.7.5 | Type NSPAContainerInformation | Not Supported | |
| latency | Not Supported | ||
| throughput | Not Supported | ||
| maximumPacketLossRate | Not Supported | ||
| serviceExperienceStatisticsData | Not Supported | ||
| theNumberOfPDUSessions | Not Supported | ||
| theNumberOfRegisteredSubscribers | Not Supported | ||
| loadLevel | 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 | Supported with Extensions | |
| Diagnostics | Supported with Extensions | ||
| IPFilterRule | Supported with Extensions | ||
| N2ConnectionMessageType | Supported with Extensions | ||
| LocationReportingMessageType | 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 | Supported | |
| subscriberIdentifier | Supported | ||
| nfConsumerIdentification | Supported | ||
| invocationTimeStamp | Supported with Extensions | ||
| invocationSequenceNumber | Supported | ||
| serviceSpecificationInformation | Supported | ||
| multipleUnitUsage | Supported with Extensions | ||
| triggers | Supported with Extensions | See 6.2.5.3.5 for supported Trigger types. | |
| 6.2.5.2.1.2 | Type ChargingDataResponse | Supported | |
| invocationTimeStamp | Supported | ||
| invocationResult | Supported | ||
| invocationSequenceNumber | Supported | ||
| sessionFailover | Supported | ||
| triggers | Supported with Extensions | ||
| 6.2.5.2.1.3 | Type MultipleUnitUsage | Supported | |
| ratingGroup | Supported | ||
| usedUnitContainer | Supported | ||
| 6.2.5.2.1.4 | Type UsedUnitContainer | Supported | |
| serviceId | Supported | ||
| triggers | Supported | ||
| triggerTimeStamp | Supported | ||
| time | Supported | ||
| totalVolume | Supported with Extensions | ||
| uplinkVolume | Supported | ||
| downlinkVolume | Supported | ||
| serviceSpecificUnits | Supported | ||
| eventTimeStamps | Supported with Extensions | ||
| localSequenceNumber | Supported with Extensions | ||
| 6.2.5.2.1.5 | Type Trigger | Supported with Extensions | |
| triggerType | Supported with Extensions | ||
| triggerCategory | Supported with Extensions | ||
| timeLimit (DurationSec) | Supported with Extensions | ||
| volumeLimit64 | Supported with Extensions | ||
| eventLimit | Supported with Extensions | ||
| maxNumberOfccc | Supported with Extensions | ||
| 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. |
Códigos de Resposta
Tabela 1-2: Response Codes
| Códigos de resposta | Descrição |
|---|---|
| 201 Created (Create) | A criação de um recurso Charging Data é confirmada e uma representação desse recurso é retornada. O recurso Charging Data é criado e retornado com sucesso. A representação do recurso criado é identificada através do campo de cabeçalho Location na resposta 201. |
| 200 OK (Updates) | A modificação de um recurso Charging Data é confirmada e uma representação desse recurso é retornada. O recurso Charging Data que é modificado e retornado com sucesso. |
| 204 No Content (Release) | O recurso Charging Data correspondente ao ChargingDataRef é modificado e então liberado. |
| 400 Bad Request | CHARGING_FAILED: A requisição HTTP é rejeitada porque o conjunto de informações de sessão ou assinante necessário pelo CHF para carregamento ou criação de CDR está incompleto, incorreto ou indisponível (por exemplo, Rating Group, informações do assinante). RE_AUTHORIZATION_FAILED: A requisição HTTP é rejeitada porque o conjunto de informações necessário pelo NF Consumer (CTF) para reportar o uso está incompleto, incorreto ou indisponível. |
| 403 Forbidden | CHARGING_NOT_APPLICABLE: A requisição HTTP é rejeitada pelo CHF, pois foi determinado que o serviço pode ser concedido ao usuário final sem qualquer carregamento ou criação de CDR. END_USER REQUEST_DENIED: A requisição HTTP é negada pelo CHF devido a restrições ou limitações relacionadas ao usuário final. QUOTA_LIMIT_REACHED: A requisição HTTP negada pelo CHF porque a conta do usuário final não pôde cobrir o serviço solicitado. Se a requisição continha unidades utilizadas, elas são deduzidas, se aplicável. END_USER_REQUEST_REJECTED: A requisição HTTP rejeitada pelo CHF devido a restrições ou limitações do usuário final. |
| 404 Not Found | USER_UNKNOWN: A requisição HTTP é rejeitada porque o usuário final especificado na requisição não pode ser atendido pelo CHF. |
| 500 Internal Server Error | Erro Comum da Aplicação |
Charging Function – Spending Limit Control Service
Conformidade da Seção
A tabela fornecida abaixo descreve a conformidade das seções dentro do 5G System Charging Service de acordo com a 3GPP TS 29.594 v16.3.0 (2020-09).
Tabela 2-1: 5G System Charging Service 3GPP TS 29.594 v16.3.0 (2020-09) Section Compliance
| Número da Seção | Seção | Status | Notas |
|---|---|---|---|
| 1 | Scope | Informational | - |
| 2 | References | Informational | - |
| 3 | Definitions and abbreviations | Informational | - |
| 4 | Nchf_SpendingLimitControl Service | Supported | - |
| 4.1 | Service Description | Supported | - |
| 4.1.1 | Overview | Supported | - |
| 4.1.2 | Service Architecture | Supported | - |
| 4.1.3 | Network Functions | Supported | - |
| 4.1.3.1 | Charging Function (CHF) | Supported | - |
| 4.1.3.2 | NF Service Consumers | Supported | - |
| 4.2 | Service Operations | Supported | - |
| 4.2.1 | Introduction | Supported | - |
| 4.2.2 | Nchf_SpendingLimitControl_Subscribe service operation | Supported | - |
| 4.2.2.1 | General | Supported | - |
| 4.2.2.2 | Initial spending limit retrieval | Supported | - |
| 4.2.2.3 | Intermediate spending limit report retrieval | Supported | - |
| 4.2.3 | Nchf_SpendingLimitControl_Unsubscribe service operation | Supported | - |
| 4.2.3.1 | General | Supported | - |
| 4.2.3.2 | Unsubscribe from spending limit reporting | Supported | - |
| 4.2.4 | Nchf_SpendingLimitControl_Notify service operation | Supported | - |
| 4.2.4.1 | General | Supported | - |
| 4.2.4.2 | Spending limit report | Supported | - |
| 4.2.4.3 | Subscription termination request by CHF | Not Supported | - |
| 5 | Nchf_SpendingLimitControl Service API | Supported | - |
| 5.1 | Introduction | Supported | - |
| 5.2 | Usage of HTTP | Supported | - |
| 5.2.1 | General | Supported | - |
| 5.2.2 | HTTP standard headers | Supported | - |
| 5.2.2.1 | General | Supported | - |
| 5.2.2.2 | Content type | Supported | - |
| 5.2.3 | HTTP custom headers | Supported | Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers. |
| 5.3 | Resources | Supported | - |
| 5.3.1 | Resource Structure | Supported | - |
| 5.3.2 | Resource: Spending Limit Retrieval Subscriptions (Collection) | Supported | - |
| 5.3.2.1 | Description | Supported | - |
| 5.3.2.2 | Resource Definition | Supported | - |
| 5.3.2.3 | Resource Standard Methods | Supported | - |
| 5.3.2.3.1 | POST | Supported | 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 | Not Applicable | - |
| 5.3.3 | Resource: Individual Spending Limit Retrieval Subscription (Document) | Supported | - |
| 5.3.3.1 | Description | Supported | - |
| 5.3.3.2 | Resource definition | Supported | - |
| 5.3.3.3 | Resource Standard Methods | Supported | - |
| 5.3.3.3.1 | PUT | Supported | 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 | Supported | 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 | Not Applicable | - |
| 5.5 | Notifications | Supported | - |
| 5.5.1 | General | Supported | Terminate is not supported |
| 5.5.2 | Spending limit notification | Supported | - |
| 5.5.2.1 | Description | Supported | - |
| 5.5.2.2 | Target URI | Supported | - |
| 5.5.2.3 | Standard Methods | Supported | - |
| 5.5.2.3.1 | POST | Supported | 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 | Not Supported | - |
| 5.5.3.1 | Description | Supported | - |
| 5.5.3.2 | Target URI | Supported | - |
| 5.5.3.3 | Standard Methods | Supported | - |
| 5.5.3.3.1 | POST | Supported | 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 | Supported | - |
| 5.6.1 | General | Supported | - |
| 5.6.2 | Structured data types | Supported | - |
| 5.6.2.1 | Introduction | Supported | - |
| 5.6.2.2 | Type SpendingLimitContext | Supported | - |
| 5.6.2.3 | Type SpendingLimitStatus | Supported | - |
| 5.6.2.4 | Type PolicyCounterInfo | Supported | - |
| 5.6.2.5 | Type PendingPolicyCounterStatus | Supported | - |
| 5.6.2.6 | Type SubscriptionTerminationInfo | Not Supported | - |
| 5.6.3 | Simple data types and enumerations | Supported | - |
| 5.6.3.1 | Introduction | Supported | - |
| 5.6.3.2 | Simple data types | Supported | - |
| 5.6.3.3 | Enumeration: TerminationCause | Not Supported | - |
| 5.7 | Error handling | Supported | - |
| 5.7.1 | General | Supported | - |
| 5.7.2 | Protocol Errors | Not Applicable | - |
| 5.7.3 | Application Errors | Supported | - |
| 5.8 | Feature negotiation | Not Supported | - |
| 5.9 | Security | Not Supported | OAuth2 is not supported. |
Códigos de Resposta
Tabela 2-2: Response Codes
| Códigos de resposta | Descrição |
|---|---|
| 201 Created | SUCESSO: A assinatura do limite de gastos foi criada e os relatórios de limite de gastos são fornecidos. |
| 200 OK | A assinatura individual do limite de gastos foi modificada e os relatórios de limite de gastos são fornecidos. |
| 204 No Content | Consulte as operações individuais |
| 400 Bad Request | USER_UNKNOWN: O assinante especificado na requisição não é conhecido no CHF e a assinatura não pode ser criada. NO_AVAILABLE_POLICY_COUNTERS: Não há contadores de política disponíveis para o assinante no CHF |
| 500 Internal Server Error | Erro Comum da Aplicação |
Charging Function – Interações com Network Repository Function (NRF)
Conformidade da Seção
A tabela abaixo fornece uma descrição dos serviços suportados pelo CHF como uma Network Function consumidora para sua interação com o NRF, de acordo com os 5G System Network Function Repository Services em 3GPP TS 29.510 v16.5.0 (2020-09).
Tabela 3-1: Services Supported by CHF as a Consumer Network Function
| Número da Seção | Seção | Status | Notas |
|---|---|---|---|
| 5 | Services Offered by the NRF | Supported | |
| 5.1 | Introduction | Supported | Apenas o NFManagement Service com as operações NFRegister, NFUpdate, NFDeregister e NFListRetrieval são suportados. |
| 5.2 | Nnrf_NFManagement Service | Supported | |
| 5.2.1 | Service Description | Supported | |
| 5.2.2 | Service Operations | Supported | |
| 5.2.2.1 | Introduction | Supported | |
| 5.2.2.2 | NFRegister | Supported | |
| 5.2.2.2.1 | General | Supported | |
| 5.2.2.2.2 | NF (other than NRF) registration to NRF | Supported | |
| 5.2.2.3 | NFUpdate | Supported | |
| 5.2.2.3.1 | General | Supported | |
| 5.2.2.3.2 | NF Heart-Beat | Supported | |
| 5.2.2.4 | NFDeregister | Supported | |
| 5.2.2.4.1 | General | Supported | |
| 5.2.2.5 | NFStatusSubscribe | Not Supported | |
| 5.2.2.6 | NFStatusNotify | Not Supported | |
| 5.2.2.7 | NFStatusUnsubscribe | Not Supported | |
| 5.2.2.8 | NFListRetrieval | Supported | |
| 5.2.2.8.1 | General | Supported | |
| 5.2.2.9 | NFProfileRetrieval | Not Supported | |
| 5.2.2.9.1 | General | Not Supported |
Formato CHF-CDR
A tabela abaixo descreve o status de conformidade dos campos dentro do 3GPP Charging Function Call Detail Record (CHF-CDR) da especificação 3GPP TS 32.298 versão 16.5.0.
Tabela 4-1: CHF-CDR Format
| Campo | Status |
|---|---|
| Record Type | Supported |
| Recording Network Function ID | Not supported |
| Charging Session Identifier | Supported |
| Subscriber Identifier | Supported |
| NF Consumer Information | Supported |
| NF Functionality | Supported |
| NF Name | Supported |
| NF Address | Supported |
| NF PLMN ID | Supported |
| Triggers | Supported |
| SMF Triggers | Supported |
| List of Multiple Unit Usage | Supported |
| Rating Group | Supported |
| Used Unit Container | Supported |
| Service Identifier | Supported |
| Quota management Indicator | Supported |
| Local Sequence Number | Supported |
| Time | Supported |
| Uplink Volume | Supported |
| Downlink Volume | Supported |
| Total Volume | Supported |
| Service Specific Units | Supported |
| Event Time Stamp | Supported |
| Rating Indicator | Supported |
| Triggers | Supported |
| SMF Triggers | Supported |
| Trigger Time Stamp | Supported |
| PDU Container Information | Supported |
| UPF ID | Supported |
| Record Opening Time | Supported |
| Duration | Supported |
| Record Sequence Number | Supported |
| Cause for Record Closing | Supported |
| Local Record Sequence Number | Supported |
| Record Extensions | Not supported |
| Service Specification Information | Supported |
| PDU Session Charging Information | Supported |
| Roaming QBC Information | Supported |
| SMS Charging Information | Supported |
| Registration Charging Information | Not supported |
| N2 connection charging Information | Not supported |
| Location reporting charging Information | Not supported |
