aboutsummaryrefslogtreecommitdiffstats
path: root/docs/offeredapis/swagger/pms-api.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/offeredapis/swagger/pms-api.yaml')
-rw-r--r--docs/offeredapis/swagger/pms-api.yaml36
1 files changed, 29 insertions, 7 deletions
diff --git a/docs/offeredapis/swagger/pms-api.yaml b/docs/offeredapis/swagger/pms-api.yaml
index 3bf13a21..865eb770 100644
--- a/docs/offeredapis/swagger/pms-api.yaml
+++ b/docs/offeredapis/swagger/pms-api.yaml
@@ -1,7 +1,7 @@
---
openapi: 3.0.1
info:
- title: A1 Policy management service
+ title: A1 Policy Management Service
description: 'The O-RAN Non-RT RIC PolicyAgent provides a REST API for management
of policices. It provides support for: -Supervision of clients (R-APPs) to eliminate
stray policies in case of failure -Consistency monitoring of the SMO view of policies
@@ -16,13 +16,36 @@ servers:
- url: http://localhost:8081/
tags:
- name: A1 Policy Management
- description: Policy Controller
+ description: This is the north bound API of the A1 Policy Management Service ("Policy
+ Agent"). This API allows *services* to interact with the Policy Agent using REST.
+ By registering with the Policy Agent, the Policy Agent takes responsibility for
+ synchronizing the policies created by the service in the Near RT RICs. This means
+ that if a Near RT RIC restarts, the Policy Agent will try to recreate all the
+ policies residing in the Near RT RIC once it is started again. If this is not
+ possible, it will remove all policies belonging to the Near RT RIC. The Policy
+ Agent also keeps an updated view of the policy types available, and which Near
+ RT RICs that support which types. Also, the Policy Agent can tell if a Managed
+ Element is managed by a certain Near RT RIC.
- name: Health check
- description: Status Controller
+ description: The status of the A1 Policy Management Service
- name: RIC Repository
- description: Ric Repository Controller
+ description: The A1 Policy Management Service keeps an updated view of the Near
+ RT RICs that are available in the system. A service can find out which Near RT
+ RIC that manages a specific element in the network or which Near RT RICs that
+ support a specific policy type.
- name: Service registry and supervision
- description: Service Controller
+ description: A service can register itself in the A1 Policy Management Service.
+ By providing a callback URL the service can get notifications from the A1 Policy
+ Management Service. A service can also register a "*Keep Alive Interval*", in
+ seconds. By doing this the service promises to call the A1 Policy Management Service's
+ "*Keep Alive*" method, or else create or delete policies, more often than the
+ "*Keep Alive Interval*" measured in seconds. If the service, for some reason,
+ is not able to do this, the A1 Policy Management Service will consider that the
+ service has died or vanished and will then delete all its policies, both in the
+ internal repository and in the Near RT RICs where they were earlier created. **Note!**
+ If the service does not provide a value for "*Keep Alive Interval*", then the
+ service maintains full responsibility to delete all of its policies when they
+ are no longer needed.
paths:
"/policies":
get:
@@ -759,7 +782,7 @@ components:
description: callback for notifying of RIC synchronization
keepAliveIntervalSeconds:
type: integer
- description: keep alive interval for the service. This is a heartbeat supervision
+ description: Keep alive interval for the service. This is a heartbeat supervision
of the service, which in regular intevals must invoke a 'keepAlive' REST
call. When a service does not invoke this call within the given time,
it is considered unavailble. An unavailable service will be automatically
@@ -849,4 +872,3 @@ components:
ueId: '1'
statement:
priorityLevel: 1
-