Self-driven and adaptable multi-vBNG management orchestration
摘要
說明書
Initially, every ‘n’ seconds, vBNG N 357 advertises subscriber counts (302). Said differently, for example, vBNG N 357 may periodically advertise subscriber information to NRM 341. In some instances, NRM 341 receives, from each vBNG instance of vBNG N 357 and vBNG N 361, a respective subscriber count. NRM 341 updates or modifies a database for vBNG N 357 (304). For instance, NRM 341 modify, for each vBNG instance of vBNG N 357 and vBNG N 361 a respective entry of NSDB 343 based on the respective subscriber count to generate modified subscriber count information. NRM 341 outputs an instruction to NLB 347 to recompute subscriber load balancer credits (306). Similarly, every ‘n’ seconds, vBNG M 361 advertises subscriber counts (308). In this example, NRM 341 updates NSDB 343 for vBNG M 361 (309). In this example, NRM 341 outputs an instruction to NLB 347 to recompute subscriber load balancer credits (310).
