| Dongho Kim | 287b75a | 2020-04-09 10:52:13 -0700 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 |
| 2 | International License. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| 4 | .. _docs_5g_a1_adaptor: |
| 5 | |
| mrichomme | e464389 | 2020-11-30 18:31:29 +0100 | [diff] [blame^] | 6 | :orphan: |
| 7 | |
| Dongho Kim | 287b75a | 2020-04-09 10:52:13 -0700 | [diff] [blame] | 8 | 5G - A1 Adaptor |
| 9 | --------------- |
| 10 | |
| 11 | Description |
| 12 | ~~~~~~~~~~~ |
| 13 | |
| 14 | A1 is an O-RAN defined interface between Non-Real Time RIC (Ran Intelligent Controller) in the management platform (ONAP) and RAN network element called Near-Real Time RIC. |
| 15 | A1 interface is used to communicate policy choices, AI/ML model updates, and other RAN functions that are not included in the traditional network configuration. |
| 16 | O-RAN defines architecture of RT RIC and relevant interfaces. |
| 17 | O-RAN WG2 has released the first version of A1 specifications September 2019. |
| 18 | ONAP needed to implement a module serving a communication channel between other ONAP components and RT RIC for A1 interface. |
| 19 | ONAP community has a harmonization project with mobility standard and A1 adaptor has been proposed in the project (https://wiki.onap.org/display/DW/MOBILITY+STANDARDS+HARMONIZATION+WITH+ONAP). |
| 20 | A1 adaptor has been implemented as a component in CCSDK. All implementation details are explained here: https://wiki.onap.org/display/DW/A1+Adapter+in+ONAP |
| 21 | |
| 22 | How to Use |
| 23 | ~~~~~~~~~~ |
| 24 | |
| 25 | Following steps describe a general procedure about how to use A1 adaptor. |
| 26 | |
| 27 | 1. ONAP Frankfurt includes A1 adaptor. |
| 28 | |
| 29 | 2. Edit A1 adaptor property file in sdnc container at dev-sdnc-x POD. (dev is an example of release name and x is replica number) |
| 30 | |
| 31 | a. A property file is located at /opt/onap/ccsdk/data/properties/a1-adapter-api-dg.properties. |
| 32 | |
| 33 | b. SSH into a rancher node (NFS/rancher). |
| 34 | |
| 35 | c. sudo su |
| 36 | |
| 37 | d. kubectl get pods -n onap -o wide | grep sdnc |
| 38 | |
| 39 | e. execute the following command to all sdnc PODs to update properties files. |
| 40 | |
| 41 | - kubectl exec -it dev-sdnc-x bash (x=0,1,2, depending on number of sdnc replicas in the setup) |
| 42 | |
| 43 | f. Once in the docker, edit the properties file. |
| 44 | |
| 45 | g. Make following configuration changes per setup |
| 46 | |
| 47 | - Update IP address and port number for Near-Real Time RIC as below |
| 48 | |
| 49 | - near-rt-ric-id=a.b.c.d:port |
| 50 | |
| 51 | A1 adaptor has been tested with A1 mediator as an example of Near-Real Time RIC. Detailed information can be found at its repo: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt%2Fric-dep.git;a=shortlog;h=refs%2Fheads%2Fmaster. |
| 52 | |
| 53 | Test Status and Plans |
| 54 | ~~~~~~~~~~~~~~~~~~~~~ |
| 55 | |
| 56 | For ONAP Frankfurt, A1 adaptor has not been involved in a full closed loop use case. A1 adaptor has gone through a unit test with A1 mediator in OSC as a underlying device. It has been tested for receiving A1 policy via DMaaP and publishing a response back to DMaaP as well as notification. More details are presented in https://wiki.onap.org/pages/viewpage.action?pageId=71837463. |