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

server	24i
serverId	de9265ec-7df1-3171-8c6c-74fc0056a720
key	BPLAT-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

Entitle user to "

Start

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

Image RemovedImage Added

Code Block

theme	Midnight
collapse	true

title Entitle user to "StartA" 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

Version	Old Version 8	New Version 9
Changes made by	Andy Beak	Andy Beak
Saved on	Sept 18, 2018	Sept 18, 2018

Versions Compared

Key

Introduction

Overview of BSS integration

Resources

Big picture

Use case diagrams

Create new user

Entitle user to "

A" OTT package

Entitle user to "Start" DVB package

Content Comparison

Versions Compared

Key

Introduction

Overview of BSS integration

Resources

Big picture

Use case diagrams

Create new user

Entitle user to "

A" OTT package

Entitle user to "Start" DVB package