P2P · POC Scope of Work

POC Scope of Work

To be completed and approved by both parties before POC activation.

ℹ

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 §10).

Customer
Version	v1.0 (draft)
Date
Prepared by	Quanteec

1Streaming protocol & format

1.1 Protocols in scope

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

Target latency / packaging notes

1.2 Video codec(s) in use

H.264 / AVC H.265 / HEVC AV1 VP9

H.265 restrictions / fallback notes

1.3 Segment duration, buffer, and latency

Segment duration (s)

Buffer (s)

Latency (s)

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

Details (optional)

1.4 Content types in scope

Peak concurrent viewer estimate

Note: P2P impact starts at 300–400 concurrent viewers and scales linearly.

2Ad insertion

No ad insertion SSAI (server-side) SGAI (server-guided client-side) CSAI (client-side only)

Ad server / vendor

3CDN & delivery infrastructure

3.1 CDN service(s) currently in use

3.2 Multi-CDN strategy

Single CDN Multi-CDN: server-side steering Multi-CDN: client-side steering Multi-CDN: performance KPI-based routing

CDN load balancer / orchestration layer

3.3 Delivery geographies

Primary geography for POC measurement

3.4 Storage / origin

4Security & token authentication

4.1 DRM system(s) in use

DRM vendor / licence server

ℹ

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

Token TTL / rotation frequency

5Players & devices

5.1 Player(s) in scope

Tick each player in use and note its version.

Field	Value
Number of active player versions in production
Player managed by a 3rd-party integrator?	Yes, integrator contacts QuanteecNo, in-house

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

Computers (browser) Samsung Tizen LG webOS

Other:

SDK Android

Min SDK version

SDK iOS

iPhone iPad tvOS

Other:

5.3 Stream segmentation by device category

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

Same manifest for all devices Separate manifests by device category Device-specific ABR ladder, same packaging

Per-device stream notes

6POC milestones & timeline

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

Milestone plan

7Roles & responsibilities

Role	Name	Company
Customer, technical lead
Customer, business sponsor
Quanteec, integration contact		Quanteec
Quanteec, account lead		Quanteec
Player integrator (if 3rd party)

Agreed communication cadence

8Success criteria & exit conditions

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

8.1 CDN offload

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

8.2 Quality of experience (QoE)

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

QoE metric	CDN baseline	Quanteec P2P	Result (post-POC)
Average rebuffering ratio		Similar or better than CDN
Top quality (highest bitrate available)		Similar or better than CDN
Average bitrate delivered
Startup time (time to first frame)

8.3 Observability & analytics

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

Number of concurrent streams Rebuffering ratio (real-time) Time to First Byte (TTFB) Bandwidth consumption (CDN vs P2P split) Average bitrate delivered Video plays / session count P2P offload % over time (chart) Energy savings estimate (kWh / gCO₂)

Reporting access method

Quanteec real-time dashboard (Panel) Integration with customer analytics platform Post-event CSV / data export

8.4 Go / no-go decision criteria

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

CDN offload ≥ 60% at peak concurrent audience CDN cost reduction trajectory ≥ 25% annualised QoE metrics maintained or improved vs CDN baseline No user-facing complaints attributable to P2P during POC Integration completed within agreed timeline (§6)

ℹ

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.

9Explicit out-of-scope items

⚠

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

Changes to encoder or packager configuration Changes to CDN routing or CDN configuration Changes to DRM licence server VOD content (if live-only POC) Mobile SDK (if web-only POC) CTV SDK (if web-only POC) SLA / uptime guarantees during POC period Production traffic activation without staging sign-off

Additional out-of-scope items (customer-specific)

10Change request process

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

Adding protocols, device types, geographies, or streams not listed in §1–§5
Modifying success criteria or KPI thresholds (§8)
Extending the POC timeline beyond the agreed end date (§6)

Agreed change request method

Email confirmation from both technical leads Signed amendment to this document To be defined

Notes

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

Name

Title

Customer

Business sponsor

Name

Title

Quanteec

Integration lead

Name

Title

Quanteec

Account lead

Name

Title

I confirm the information entered above is accurate and complete, and agree to the scope, success criteria and exclusions defined in this document.

Confirmed by (name)

Date

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.

Quanteec P2P · POC Scope of Work

1Streaming protocol & format

1.1 Protocols in scope

1.2 Video codec(s) in use

1.3 Segment duration, buffer, and latency

1.4 Content types in scope

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

4.2 Token authentication mechanism

5Players & devices

5.1 Player(s) in scope

5.2 Device(s) in scope

5.3 Stream segmentation by device category

6POC milestones & timeline

7Roles & responsibilities

8Success criteria & exit conditions

8.1 CDN offload

8.2 Quality of experience (QoE)

8.3 Observability & analytics

8.4 Go / no-go decision criteria

9Explicit out-of-scope items

10Change request process

Approval & responsible parties