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: BPLAT-7116 - Getting issue details... STATUS

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

Big picture

Use case diagrams

Create new user (phase 2 only)

Non-technical flow diagram

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

Which endpoint NetAdmin should use

NetAdmin will POST to https://boox.fi/api/management/stb/link_user

Parameter	Location	Description
service_token	Query	Token generated for a service. This param will be skipped if Service-Token HTTP Header exists
serial_no	Query	Serial Number of STB
email	Query	Email address of user who is provisioned for using the STB
public_keys	Query
chipset_id	Query
mac	Query

How the user will sign in

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

Entitle user to "A" OTT package

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

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

BPLAT-7116: Kabelnoord BSS integration