what is it: (Data management and exposure) Service that manages data subscriptions. It separates data consumers from data producers (for different vendor). Data consumer doesn't need to be aware of where the data source.
where is it: https://github.com/o-ran-sc/nonrtric-plt-informationcoordinatorservice mirror of https://gerrit.o-ran-sc.org/r/nonrtric/plt/informationcoordinatorservice
historical names? Information Coordinator Service (ICS); Enrichment Information Coordinator;
1. Building the docker image from source and run it on port 8083 http
git clone "https://gerrit.o-ran-sc.org/r/nonrtric/plt/informationcoordinatorservice"
cd informationcoordinatorservice
mvn clean install
docker run -d -p 8083:8083 o-ran-sc/nonrtric-plt-informationcoordinatorservice:latest
...
docker run -d -p 8083:8083 nexus3.o-ran-sc.org:10003/nonrtric-plt-informationcoordinatorservice:latest
2. Run docker image on port 8083 http
3. Import the swagger.json in Postman (informationcoordinatorservice/api/ics-api.json) as an OpenAPI3.0
43. Replace the baseUrl with http://localhost:8083 (in the Data management and exposure variables), and change accordingly {{infoTypeId}} from :infoTypeId
Other variables will be :{{infoJobId }}/{{infoProducerId}}/{{infoTypeId}}/{{subscriptionId}} etc
54. ICS flow:
a) Create a type (PUT /info-types)
b) Create a producer (PUT /info-producers) {supports type for filtering}
c) Create a job (PUT /info-jobs) {consumer subscription}
...
PUT {{baseUrl}}/data-producer/v1/info-types/{{infoTypeId}}
Body:
{
"info_job_data_schema": {
"topicName": "example_topic",
"key": "example_key",
"message": "example_message"
},
"info_type_information": {}
}
...
PUT {{baseUrl}}/data-producer/v1/info-producers/{{infoProducerId}}
Body:
{
"supported_info_types": ["example_info_type_id"],
"info_job_callback_url": "http://example.com/job_callback", //POST JobCallbackUrl() + "/" + infoJob.getId();
"info_producer_supervision_callback_url": "http://example.com/producer_supervision_callback"
}
...
PUT {{baseUrl}}/data-consumer/v1/info-jobs/{{infoJobId}}
Body:
{
"info_type_id": "example_info_type_id",
"job_owner": "example_owner",
"job_definition": {
"example_key1": "example_value1",
"example_key2": "example_value2"
},
"job_result_uri": "http://example.com/job_result",
"status_notification_uri": "http://example.com/status_notification"
}
1. Autorizarion Authorization check: POST to the Auth Authentication Agent (from the starting config config/application.yaml )
2. Validation: The URLs seem to be used only for URI validation (?)
3. Consumer starts a job on the Producer POST producerCallbacks.startInfoSubscriptionJob->restClient.post(producer.getJobCallbackUrl(), jobCallbackBody(infoJob))