Integrate the actual stream, so it could be picked up and processed by our components:

Parameter	Value	Description
* Input Mux	RTMP	CMAF is recommended (fMP4 containers) if encoder has been previously homologated with Akamai Ingest Point (Origin)
Input Video Codec	H.264
Input Audio Codec	AAC
Input Bitrate	750 Kbps
*Input Resolution	480x320	If another resolution is used, please notify it
GOP	60 or 120	60 is recommended
Fps	30	Frames per second
Profile	Baseline
* Lookahead	0-5	Setting it to low will improve latency, but since it reduces output quality for demanding scenes, it works well mainly if there are no or few scene changes.
* B Frames	0-5	The more B Frames used in a GOP, the higher the probability that encoding latency will be increased by a few frames for each B Frame added, as the encoding engine will look ahead to the next P Frames to construct the B frame. Using zero B Frames is possible to counteract this latency impact, but it will require raising the encoding bitrate to keep the same quality level as when using B Frames
Encoder Buffer Size	1x	The default value is twice the video bitrate in bits, which generates a 2-second delay on the decoder. If set to 1x bitrate, it generates a 1-second delay and slightly impacts the video quality.
Latency	2 sec	The max latency from capture device (example: camera) to origin server must be at most 2 sec

The parameters with (*) are recommendations.

For this test with XXX the next setting parameters will be used:

Note: This parameters will be sent via email.

Integrate your schedule in to our system, so that we would know what matches are going to be streamed

The feed can be either an XML/JSON (refers to condition 1) feed or a Pull API. The following data is needed to integrate the fixture feed:

IP range to be whitelisted: IP range - 185.107.196.0/22
Any implementation documentation
If feed requires AUTH key (if this is a temporal authentication key, which will have an expiry date 5 weeks prior to the change, we need to be notified and authentication key needs to be provided)
How the streams will be published – match or competition? Every match will have separate stream or you will provide us with one stream per competition (multiple matches?)
In order to match the streaming data to the schedule data, we expect when sending streaming data to AKAMAI to have unified ID, so we could match and link the stream to the fixture.

Any kind of integration distinct to XML/JSON is not accepted or needs to be included into the official agreement
The parameters