Versions Compared

Version Old Version 9 New Version 10
Changes made by

Andy Beak (Unlicensed)

Andy Beak (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

We need a design confluence page for this KN BSS Integration.

1. Data flow diagrams for each of use cases.
2. Get it reviewed by leads
3. Get these flows accepted by customer and third-parties involved

Once these are done, development team can start working on the Epic

Ticket:

Jira Legacy
server24i
serverIdde9265ec-7df1-3171-8c6c-74fc0056a720
keyBPLAT-7116

Overview of BSS integration

Phase 1: No integration, users are provisioned through CMS

Phase 2: NetAdmin will provision users through an API as part of the vending process

Resources

KN ITV Channel configurations v1.5.xlsx

Table of Contents



Big picture



Use case diagrams

Create new user (phase 2 only)

Image Added

Code Block
themeMidnight
collapsetrue
title Create new user

note left of Amino factory
  At manufacture time
end note
Amino factory->Move API: List of STB serial numbers and keys
note right of NetAdmin:
  At sale time
end note
NetAdmin->Move API: User identity and their STB serial number

See /wiki/spaces/BPLAT/pages/38550375 to see the process of letting the user sign in.

Entitle user to "A" OTT package

(warning) TBC:  What Move API must be called by KN?  Do we need to provision a new endpoint like the one at Channel License

Code Block
themeMidnight
collapsetrue
title Entitle user to "A" OTT package

KN BSS->Move API: GET /api/user/<email>/product/<product_id>/buy/option/<option_id>
Move API->Irdeto: SOAP entitlement call
Irdeto->Move API: 200 OK
Move API->KN BSS: 200 OK

Entitle user to "Start" DVB package