Message Flow

Diagram

O-RAN Configuration Management Radio Access Network SMO-O1-Controller(e.g. ONAP SDN-R) User space O-RAN Component O-RAN Component NetConf Client NetConf Client Abstration Layer Abstration Layer RestConf Server RestConf ServerSMO µService, rAppor OLDUX in browser SMO µService, rAppor OLDUX in browser [01]REST PUT or POST request for xNF [02]verification [03]forwarding as XML [04]<edit-config> [05]<rpc-reply> [06]verification [07]forwarding as XML or JSON based on HTTP Accept [08]HTTP RESPONSELicenseApache 2.0Thanks to plantUml!2020-12-03 | o-ran-sc.org


Description

  1. Any user (e.g humans, rApps, µServices) sends a set of configuration requests (here: just one) to the O1-Controller/Restconf-Provider/HTTP-Client.
  2. The request will be parsed, validated and in case of a json-body converted to xml.
  3. Finally the fowared conent ...
  4.  is send by the NetConf-Client of the O1-Controller as <edit-config/> operation to the O-RAN component.
  5. The NetConf server of the O-RAN component sends as response a NetConf <rpc-replay/> message the the O1-Controller
  6. The response will be parsed and validated...
  7. and based on the HTTP Accept header conterted to JSON or XML ...
  8. ... for sending a proper HTTP response


Verification Command

Please see Postman collection from SMO project: https://gerrit.o-ran-sc.org/r/gitweb?p=smo/o1.git;a=blob;f=scripts/postman/O-RAN+Collection.postman_collection.json

  • No labels