Policy counter operations
- Endpoint
-
/pcc/pcrf/policy-counter
API endpoints related to obtaining information about policy counters. This includes creating, retrieving, updating, and deleting counter.
Create policy counter
Creates a new policy counter.
post /pcc/pcrf/policy-counter
Request
Below is a request example. See the descriptions below for more details on the fields.
{
"id" : 4711,
"name" : "BaseProfileCounter",
"description" : "Counter for the base profile",
"status" : "active",
"deviceProfileId" : 111,
"locationProfileId" : 222,
"timeProfileId" : 333,
"networkProfileId" : 444,
"created" : "2020-06-07T13:10:00Z",
"updated" : "2020-06-08T14:20:00Z"
}
Get policy counter
Retrieves a policy counter. Specify an ID to retrieve a specific counter or retrieve all with no ID specified. Use query parameters to paginate the response when retrieving all. For example, /pcc/pcrf/policy-counter?page=0&size=100.
get /pcc/pcrf/policy-counter/id
Update policy counter
Updates an existing policy counter.
put /pcc/pcrf/policy-counter/id
Request
Below is a request example. See the descriptions below for more details on the fields.
{
"id" : 4711,
"name" : "BaseProfileCounter",
"description" : "Counter for the base profile",
"status" : "active",
"deviceProfileId" : 111,
"locationProfileId" : 222,
"timeProfileId" : 333,
"networkProfileId" : 444,
"created" : "2020-06-07T13:10:00Z",
"updated" : "2020-06-08T14:20:00Z"
}
PCRF API JSON descriptions
| Field | Description | ||
|---|---|---|---|
|
The ID of the Policy counter.
|
||
|
The name of the Policy counter.
|
||
|
A description of the Policy counter. |
||
|
The Policy counter’s status.
|
||
|
The service profile ID. |
||
|
The QoS profile ID. |
||
|
The charging profile profile ID. |
||
|
The device profile ID. |
||
|
The location profile ID. |
||
|
The time profile ID. |
||
|
The network profile ID. |
||
|
The time the Policy counter was created in ISO format. |
||
|
The time the Policy counter was updated in ISO format. |
PCRF API response codes
If you receive an HTTP status code of 400, your request does not confirm to the API specification. Check the endpoint is correct and your header information is set to use JSON.
If you receive an HTTP status code of 422, there is a processing error. More information is provided in the codes below.
| Code | Description |
|---|---|
|
The name is not unique.
|
|
Unknown service profile.
|
|
Unknown QoS profile.
|
|
Unknown charging profile.
|
|
Unknown status.
|
|
Unknown device profile. |
|
Unknown location profile. |
|
Unknown time profile. |
|
Unknown network profile. |