5G CHF
Esta guía actúa como una declaración de conformidad de la implementación del protocolo para el protocolo 5G CHF.
Categoría:
Temas en este documento:
- Introducción
- Función de cobro – Servicio de cobro
- Función de cobro – Servicio de control de límite de gasto
- Función de cobro – Interacciones con la Función de Repositorio de Red (NRF)
- Formato CHF-CDR
Introducción
El 5G CHF (ang. Charging Function) incluye interfaces Nchf para habilitar el cobro convergente y el control de límite de gasto para la gestión de políticas. Las interacciones con la NRF (ang. Network Repository Function) también se detallan aquí.
Cómo interpretar el estado en las secciones de conformidad
La siguiente tabla describe el significado del estado en las secciones de conformidad de sección.
| Estado | Significado |
|---|---|
| Supported | La aplicación admite la funcionalidad. La aplicación admite el atributo y se mapea a la función de cobro. El atributo se recibe en la solicitud y se utiliza en los flujos de cobro. Este atributo se envía en la respuesta según lo indicado por las especificaciones. Opcionalmente, puede utilizar este atributo para el almacenamiento de eventos y para informar las decisiones de cobro. |
| Supported with Extensions | La aplicación admite la funcionalidad con extensión. La aplicación admite el atributo y puede utilizarse opcionalmente para seleccionar un precio. El atributo se recibe en la solicitud y no se utiliza en el flujo de cobro predeterminado. El atributo puede enviarse o no en la respuesta. Tiene la opción de aprovechar las extensiones disponibles en el flujo de cobro para lograr la funcionalidad prevista. También puede preferir utilizar este atributo para almacenarlo en el evento y para tomar decisiones de cobro. |
| Not Supported | La aplicación no admite la funcionalidad o el atributo. |
| Not Applicable | La sección no es aplicable para la implementación. |
| Informational | Esta sección sirve únicamente para fines informativos. |
Función de cobro – Servicio de cobro
Conformidad de la sección
La tabla siguiente contiene la descripción de la conformidad de la sección del Servicio de Cobro del Sistema 5G 3GPP TS 32.291 v16.5.1 (2020-09):
Tabla 1-1: Conformidad de la sección del Servicio de Cobro del Sistema 5G 3GPP TS 32.291 v16.5.1 (2020-09)
| Número de sección | Sección | Estado | 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 | Solo se admite el encabezado 3gpp-Sbi-Target-apiRoot entre los encabezados personalizados. |
| 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 y ChargingDataResponse. La respuesta incluye uno de los siguientes códigos: Para éxito 201 (creado). Para falla ProblemDetails incluyen - 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 y ChargingDataResponse. La respuesta incluye uno de los siguientes códigos: Para éxito 200 (OK). Para falla ProblemDetails incluyen - 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 y ChargingDataResponse. Para éxito, la respuesta será 204 (Sin contenido). Para falla, los ProblemDetails incluyen - 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 y ChargingDataResponse. Para éxito, la respuesta será 204 (Sin contenido). Para falla, los ProblemDetails incluyen - 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 | Consulte 6.1.6.3.6 para ver los tipos de Trigger admitidos. |
| 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 | El flujo de cobro predeterminado no procesa registros para roaming 5G. |
| 6.1.6.2.2.2 | ChargingDataResponse | Supported with Extensions | El flujo de cobro predeterminado no procesa registros para roaming 5G. |
| 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 se utiliza como la hora de la solicitud para el evento. |
| 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 | El flujo de cobro predeterminado no procesa registros para roaming 5G. |
| 6.1.6.2.2.16 | QFIContainerInformation | Supported with Extensions | Todos son compatibles solo en la solicitud, no admitidos en la respuesta |
| 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 | Se admiten FINAL, RAT_CHANGE y TARIFF_TIME_CHANGE. Otros tipos de disparadores se admiten con extensiones. |
| 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 y ChargingDataResponse. La respuesta incluye uno de los siguientes códigos: Para éxito 201 (creado). Para falla ProblemDetails incluyen - 400, 403 y 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 y ChargingDataResponse. La respuesta incluye uno de los siguientes códigos: Para éxito 200 (OK). Para falla ProblemDetails incluyen - 400, 403 y 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 y ChargingDataResponse. Para éxito, la respuesta será 204 (Sin contenido). Para falla, los ProblemDetails incluyen - 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 | Consulte 6.2.5.3.5 para ver los tipos de Trigger admitidos. | |
| 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 | - | Igual que 6.1.6.2.2.1 |
| 6.2.5.2.2.2 | Type ChargingDataResponse | - | Igual que 6.2.5.2.1.2 |
| 6.2.5.2.2.3 | Type MultipleUnitUsage | - | Igual que 6.2.5.2.1.3 |
| 6.2.5.2.2.4 | Type UsedUnitContainer | - | Igual que 6.2.5.2.1.4 |
| 6.2.5.2.2.5 | Type PDUSessionChargingInformation | - | Igual que 6.1.6.2.2.6 |
| 6.2.5.2.2.6 | Type UserInformation | - | Igual que 6.1.6.2.2.7 |
| 6.2.5.2.2.7 | Type PDUSessionInformation | - | Igual que 6.1.6.2.2.8 |
| 6.2.5.2.2.8 | Type PDUContainerInformation | - | Igual que 6.1.6.2.2.9 |
| 6.2.5.2.2.9 | Type NetworkSlicingInfo | - | Igual que 6.1.6.2.2.10 |
| 6.2.5.2.2.10 | Type PDUAddress | - | Igual que 6.1.6.2.2.11 |
| 6.2.5.2.2.11 | Type ServingNetworkFunctionID | - | Igual que 6.1.6.2.2.12 |
| 6.2.5.2.2.12 | Type RoamingQBCInformation | - | Igual que 6.1.6.2.2.13 |
| 6.2.5.2.2.13 | Type MultipleQFIcontainer | - | Igual que 6.1.6.2.2.14 |
| 6.2.5.2.2.14 | Type RoamingChargingProfile | - | Igual que 6.1.6.2.2.15 |
| 6.2.5.2.2.15 | Type QFIContainerInformation | - | Igual que 6.1.6.2.2.16 |
| 6.2.5.2.2.16 | Type RANSecondaryRATUsageReport | - | Igual que 6.1.6.2.2.17 |
| 6.2.5.2.2.17 | Type QosFlowsUsageReport | - | Igual que 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 | - | Igual que 6.1.6.3.2 |
| 6.2.5.3.3 | Enumeration: ChargingCharacteristicsSelectionMode | - | Igual que 6.1.6.3.5 |
| 6.2.5.3.4 | Enumeration: NodeFunctionality | Supported | |
| 6.2.5.3.5 | Enumeration: TriggerType | Supported | Se admiten FINAL, RAT_CHANGE y TARIFF_TIME_CHANGE. Otros tipos de disparadores se admiten con extensiones. |
| 6.2.5.3.6 | Enumeration: ResultCode | Supported | |
| 6.2.5.3.7 | Enumeration: 3GPPPSDataOffStatus | - | Igual que 6.1.6.3.13 |
| 6.2.5.3.8 | Enumeration: PartialRecordMethod | - | Igual que 6.1.6.3.15 |
| 6.2.5.3.9 | Enumeration: RoamerInOut | - | Igual que 6.1.6.3.16 |
| 6.2.5.3.10 | Enumeration: SubscriberIdentityType | - | Igual que 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 | No se admite OAuth2. |
Códigos de respuesta
Tabla 1-2: Códigos de respuesta
| Códigos de respuesta | Descripción |
|---|---|
| 201 Created (Create) | Se confirma la creación de un recurso de Charging Data y se devuelve una representación de dicho recurso. El recurso de Charging Data se crea y se devuelve con éxito. La representación del recurso creado se identifica a través del campo de encabezado Location en la respuesta 201. |
| 200 OK (Updates) | Se confirma la modificación de un recurso de Charging Data y se devuelve una representación de dicho recurso. El recurso de Charging Data que se modifica y se devuelve con éxito. |
| 204 No Content (Release) | El recurso de Charging Data que coincide con ChargingDataRef se modifica y luego se libera. |
| 400 Bad Request | CHARGING_FAILED: La solicitud HTTP se rechaza porque el conjunto de información de la sesión o del suscriptor necesaria por el CHF para el cobro o la creación del CDR (ang. Call Detail Record) está incompleto, es erróneo o no está disponible (por ejemplo, Rating Group, información del suscriptor). RE_AUTHORIZATION_FAILED: La solicitud HTTP se rechaza porque el conjunto de información necesaria por el Consumidor NF (ang. Network Function) (CTF) para informar el uso está incompleto, es erróneo o no está disponible. |
| 403 Forbidden | CHARGING_NOT_APPLICABLE: La solicitud HTTP es rechazada por el CHF ya que se ha determinado que el servicio puede ser otorgado al usuario final sin ningún cobro o creación de CDR. END_USER REQUEST_DENIED: La solicitud HTTP es denegada por el CHF debido a restricciones o limitaciones relacionadas con el usuario final. QUOTA_LIMIT_REACHED: La solicitud HTTP denegada por el CHF porque la cuenta del usuario final no pudo cubrir el servicio solicitado. Si la solicitud contenía unidades utilizadas, estas se deducen, si corresponde. END_USER_REQUEST_REJECTED: La solicitud HTTP rechazada por el CHF debido a restricciones o limitaciones del usuario final. |
| 404 Not Found | USER_UNKNOWN: La solicitud HTTP se rechaza porque el usuario final especificado en la solicitud no puede ser atendido por el CHF. |
| 500 Internal Server Error | Error de aplicación común |
Función de cobro – Servicio de control de límite de gasto
Conformidad de la sección
La tabla proporcionada a continuación describe la conformidad de las secciones dentro del Servicio de Cobro del Sistema 5G según 3GPP TS 29.594 v16.3.0 (2020-09).
Tabla 2-1: Conformidad de la sección del Servicio de Cobro del Sistema 5G 3GPP TS 29.594 v16.3.0 (2020-09)
| Número de sección | Sección | Estado | 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 | Solo se admite el encabezado 3gpp-Sbi-Target-apiRoot entre los encabezados personalizados. |
| 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 | Solicitud POST con SpendingLimitContext para crear una nueva suscripción individual de recuperación de límite de gasto. La respuesta POST debe contener SpendingLimitStatus como 201 (Created), ProblemDetails con 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 | Solicitud PUT con SpendingLimitContext para modificar la suscripción individual de recuperación de límite de gasto existente. La respuesta POST debe contener SpendingLimitStatus como 200 (OK), ProblemDetails con 400 (Bad Request). |
| 5.3.3.3.2 | DELETE | Supported | Solicitud DELETE. La respuesta DELETE debe contener 204 (No Content). Caso exitoso: Se eliminó la suscripción individual al límite de gasto que coincide con el subscriptionId. |
| 5.4 | Customer Operations without associated resources | Not Applicable | - |
| 5.5 | Notifications | Supported | - |
| 5.5.1 | General | Supported | Terminate no es compatible |
| 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 | Solicitud POST con SpendingLimitStatus para los contadores de políticas. La respuesta POST debe contener 204 (Sin contenido) y se acusa recibo de la notificación. |
| 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 | Solicitud POST con SubscriptionTerminationInfo para la eliminación de un recurso. La respuesta POST debe contener 204 (Sin contenido) y se acusa recibo de la notificación. |
| 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 | No se admite OAuth2. |
Códigos de respuesta
Tabla 2-2: Códigos de respuesta
| Códigos de respuesta | Descripción |
|---|---|
| 201 Created | SUCCESS: Se creó la suscripción al límite de gasto y se proporcionan informes de límite de gasto. |
| 200 OK | La suscripción individual al límite de gasto fue modificada y se proporcionan informes de límite de gasto. |
| 204 No Content | Consulte las operaciones individuales |
| 400 Bad Request | USER_UNKNOWN: El suscriptor especificado en la solicitud no es conocido en el CHF y la suscripción no se puede crear. NO_AVAILABLE_POLICY_COUNTERS: No hay contadores de política disponibles para el suscriptor en el CHF |
| 500 Internal Server Error | Error de aplicación común |
Función de cobro – Interacciones con la Función de Repositorio de Red (NRF)
Conformidad de la sección
La tabla siguiente proporciona una descripción de los servicios admitidos por el CHF como Consumidor NF para su interacción con la NRF, de acuerdo con los Servicios de Repositorio de Funciones de Red del Sistema 5G en 3GPP TS 29.510 v16.5.0 (2020-09).
Tabla 3-1: Servicios admitidos por el CHF como Consumidor NF
| Número de sección | Sección | Estado | Notas |
|---|---|---|---|
| 5 | Services Offered by the NRF | Supported | |
| 5.1 | Introduction | Supported | Solo se admite el Servicio NFManagement con las operaciones NFRegister, NFUpdate, NFDeregister y NFListRetrieval. |
| 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
La tabla siguiente describe el estado de conformidad de los campos dentro del Registro de Detalle de Llamada de la Función de Cobro de 3GPP (CHF-CDR) de la especificación 3GPP TS 32.298 versión 16.5.0.
Tabla 4-1: Formato CHF-CDR
| Campo | Estado |
|---|---|
| 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 |
