| Stavros Kanarakis | 596e7c0 | 2019-04-04 13:55:13 +0300 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| 4 | ===================================== |
| 5 | BBS-EP (BBS use case event processor) |
| 6 | ===================================== |
| 7 | |
| 8 | :Date: 2019-04-11 |
| 9 | |
| 10 | .. contents:: |
| 11 | :depth: 3 |
| 12 | .. |
| 13 | |
| 14 | Overview |
| 15 | ======== |
| 16 | |
| 17 | BBE-ep is responsible for handling two types of events for the BBS use case. |
| 18 | |
| 19 | First are PNF re-registration internal events published by PRH. BBS-ep must process these internal events to understand if they |
| 20 | actually constitute ONT(CPE) relocation events. In the relocation case, it publishes an event towards unauthenticated.DCAE_CL_OUTPUT |
| 21 | DMaaP topic to trigger further Policy actions related to BBS use case. |
| 22 | |
| 23 | Second type of events are CPE authentication events originally published by the Edge SDN M&C component of BBS use case architecture. |
| 24 | Through RestConf-Collector or VES-Collector, these events are consumed by BBS-ep and they are forwared towards unauthenticated.DCAE_CL_OUTPUT |
| 25 | DMaaP topic to trigger further Policy actions related to BBS use case. |
| 26 | |
| 27 | BBE-ep periodically polls for the two events. Polling interval is configurable and can be changed dynamically from Consul. Its implementation |
| 28 | is based on Reactive Streams (Reactor library), so it is fully asynchronous and non-blocking. |
| 29 | |
| 30 | |
| 31 | .. toctree:: |
| 32 | :maxdepth: 1 |
| 33 | |
| 34 | ./installation |
| 35 | ./functionality |
| 36 | ./development_info |