2 Charging Function – Spending Limit Control Service
Caution:
Deploying the 5G Spending Limit Control Service with HTTP Gateway (5G CHF) requires a cloud native deployment of ECE and BRM components. The HTTP Gateway can be used only on an ECE cloud native system.
The following table describes the section compliance of 5G System Charging Service 3GPP TS 29.594 v16.3.0 (2020-09).
Section Compliance
Table 2-1 5G System Charging Service 3GPP TS 29.594 v16.3.0 (2020-09) Section Compliance
| Section Number | Section | Status | Notes |
|---|---|---|---|
| 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 | - |
| 5.2.3.1 | General | 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 DateTime Uri Supi Gpsi SupportedFeatures |
Supported Supported Supported Supported Supported Supported |
- |
| 5.6.2 | Structured data types | Supported | - |
| 5.6.2.1 | Introduction | Supported | - |
| 5.6.2.2 |
Type SpendingLimitContext supi gpsi policyCounterIds notifUri expiry supportedFeatures |
Supported Supported Supported Supported Supported Supported with Extensions Supported with Extensions |
- |
| 5.6.2.3 |
Type SpendingLimitStatus supi statusInfos expiry supportedFeatures |
Supported Supported Supported with Extensions Supported with Extensions Supported with Extensions |
- |
| 5.6.2.4 |
Type PolicyCounterInfo policyCounterId currentStatus penPolCounterStatuses |
Supported Supported Supported Supported |
- |
| 5.6.2.5 |
Type PendingPolicyCounterStatus policyCounterStatus activationTime |
Supported Supported Supported |
- |
| 5.6.2.6 |
Type SubscriptionTerminationInfo Supi termCause |
Not Supported Not Supported Not Supported |
- |
| 5.6.3 | Simple data types and enumerations | Supported | - |
| 5.6.3.1 | Introduction | Supported | - |
| 5.6.3.2 |
Simple data types PolicyCounterId |
Supported 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. |
Response Codes
Table 2-2 Response Codes
| Response codes | Description |
|---|---|
| 201 Created (Create) |
SUCCESS: The spending limit subscription was created, and spending limit reports are provided. |
| 200 OK (Updates) |
The individual spending limit subscription was modified, and spending limit reports are provided. |
| 204 No Content (Release) | 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 |