Quanteec Restricted document

Quanteec P2P · POC Scope of Work

Enter your credentials to open the document.

Quanteec P2P · POC Scope of Work

POC Scope of Work

To be completed and approved by both parties at the end of the workshop and before POC activation for free trial*.

*Free trial conditions:

  • 1 month + 1-month renewal subject to approval.
  • 10k concurrent viewers maximum in P2P. The 10k threshold will be set by Quanteec, viewers above this threshold will receive exclusively from CDN.
  • no limit in the number of video streams.
ℹ

This document defines the agreed scope for the Quanteec P2P proof of concept. Any item not listed here is considered out of scope. Changes after sign-off require a written amendment (see §11).

Mandatory before signing.

Customer
Versionv1.0 (draft)
Date
Prepared byQuanteec

1Streaming protocol & format

1.1 Protocols in scope

Select all that apply. Items not checked are explicitly out of scope for this POC.

1.2 Video codec(s) in use

1.3 Segment duration, buffer, and latency

All values are in seconds. A value of -1 for Buffer or Latency means the client applies nothing specific (provider default).

1.4 Content types in scope

Your usual peak, not the POC audience committed in §7.1. P2P impact starts at 300–400 concurrent viewers and scales linearly.

2Ad insertion

3CDN & delivery infrastructure

3.1 CDN service(s) currently in use

3.2 Multi-CDN strategy

3.3 Delivery geographies

3.4 Storage / origin

4Security & token authentication

4.1 DRM system(s) in use

ℹ

DRM architecture note: Quanteec does not touch the DRM licence flow. Peers only exchange already-fetched encrypted segments. No DRM configuration change is required.

4.2 Token authentication mechanism

5Players & devices

5.1 Player(s) in scope

Tick each player in use and note its version.

FieldValue
Number of active player versions in production
Player managed by a 3rd-party integrator?

5.2 Device(s) in scope

ℹ

Device minimum requirements

  • Samsung: Tizen 5.5 (2020) or newer
  • Android devices (box, stick, etc.): Android 9 or newer
  • Minimum RAM: 1 GB (128 MB for the app)
  • Minimum free disk: 8 MB for the SDK

SDK Web

SDK Android

SDK iOS

5.3 Stream segmentation by device category

If bitrate ladders or packaging differs substantially by device class, note it here.

6Integration

ℹ

The Quanteec SDK works by intercepting the player's segment requests. Wherever your application already customises that same layer, the two can interact. Answering this section accurately lets Quanteec anticipate conflicts before integration week rather than during it. A "yes" here is not a problem, it is information.

6.1 SDK delivery

How will the Quanteec SDK be added to your application? Select all that apply.

6.2 Application stack

Language and framework of the application that hosts the player. Note the major version where relevant.

6.3 Release path

How long it takes to get a build in front of real viewers is what actually sets the POC timeline agreed in §7.

QuestionAnswer
Typical time from merged code to production (days)
Staging or pre-production environment Quanteec can test against
Release requires app store review
Feature flag or remote config available to enable P2P without a release

6.4 Existing custom player behaviour

Tick anything your application already does itself and add a short note. None of it blocks P2P, it only changes how Quanteec integrates.

BehaviourCustom codeDetails, library or owner
Custom segment loader or HTTP request interceptor
Retry logic on request errors
Custom request timeouts
Buffer size or target latency changed at runtime
Player error handling and recovery (failover, reload)
Logging or telemetry hooked into media requests
Custom ABR or quality selection logic
Service worker or proxy intercepting media requests
Ad logic that rewrites the manifest at runtime

6.5 Content Security Policy and network

P2P delivery opens WebRTC connections and loads the SDK from an external origin. A strict policy blocks both, usually without an obvious error.

QuestionAnswer
Content Security Policy enforced on the pages or app
Quanteec origins can be added to script-src and connect-src
Known environments where WebRTC is blocked (corporate networks, ISPs)

7POC milestones & timeline

MilestoneDate / detail
POC start date
POC end date
Target event(s) / stream(s) for measurement
Minimum concurrent viewers expected

7.1 POC audience commitment

The measured audience determines whether the POC produces meaningful results. These figures are a commitment, not an estimate: the observed column is completed by Quanteec at the end of the POC.

MetricCommittedObserved (post-POC)
Minimum concurrent viewers during measured sessions
Expected peak concurrent viewers during the POC
Number of measured events or sessions

8Roles & responsibilities

RoleNameCompany
Customer, technical lead
Customer, business sponsor
Quanteec, integration contactQuanteec
Quanteec, account leadQuanteec
Player integrator (if 3rd party)

9Success criteria & exit conditions

All thresholds below must be agreed by both parties before POC activation. Items left blank are not measured in this POC.

9.1 CDN offload

MetricTarget (agreed)Result (post-POC)
CDN offload % at peak concurrent audience≥ 60%
Peak Gbps absorbed by P2P layer
Estimated CDN cost reduction≥ 25%

9.2 Quality of experience (QoE)

P2P must maintain or improve QoE vs CDN-only baseline. Results column to be completed post-POC.

QoE metricCDN baselineQuanteec P2PResult (post-POC)
Average rebuffering ratioSimilar or better than CDN
Top quality (highest bitrate available)Similar or better than CDN
Average bitrate delivered
Startup time (time to first frame)

9.3 Observability & analytics

The following metrics must be visible in the Quanteec dashboard and/or customer analytics during the POC.

Reporting access method

9.4 Go / no-go decision criteria

POC is declared successful and triggers a commercial proposal if ALL of the following are met:

ℹ

If any criterion is not met, both parties agree to a structured review before proceeding. Failure of a single metric does not automatically trigger a no-go: root cause analysis and a remediation window may be agreed in writing.

10Explicit out-of-scope items

⚠

The following are excluded from this POC unless separately agreed in writing before implementation.

11Change request process

Any change to the scope defined in this document requires written agreement from both parties before implementation. This includes:

Agreed change request method

Approval & responsible parties

ℹ

This scope is reviewed and agreed digitally and jointly by both parties, with no physical signature required. The people below are the responsible contacts for the POC; formal agreement is recorded with the confirmation checkbox at the end of this document.

Customer
Technical lead
Customer
Business sponsor
Quanteec
Integration lead
Quanteec
Account lead

Signing is final. Once signed, the document becomes read only and further changes require Quanteec to unlock it. Tip: in the print dialog, choose Save as PDF as the destination.