Digital Measurement SEI Audio Metadata: Difference between revisions
From Engineering Client Portal
No edit summary |
No edit summary |
||
| Line 206: | Line 206: | ||
'''Body - Example:''' | '''Body - Example:''' | ||
{"audiofilename":"aacFile1.aac","referencestart":"1489506887","referenceend":"1489506889"} | <code>{"audiofilename":"aacFile1.aac","referencestart":"1489506887","referenceend":"1489506889"}</code> | ||
Revision as of 15:55, 3 July 2024
The Nielsen “server-2-server” method of collecting DTVR data requires the distributor to make available to Nielsen audio file for each live-streaming channel and each VoD asset that is eligible to DTVR crediting. Please contact your Nielsen Technical contact for a full description of what content is eligible for DTVR crediting.
In addition, to the audio files themselves, the DTVR ingestion process needs to some additional metadata for each audio file; this document specifies the additional “out-of-band” metadata that need to be provided.
The specification is defined using a JSON schema.
File Naming Convention and Location
File should be named with following convention: FileType_MVPDId_AssetId_UTCStart_UTCEnd
File type: DTVRAssetMetaData
MVPDid: unique identifier provided by Nielsen for each MVPD
AssetId: in-house assetId
UTCStart (time in 32-bit unsigned int UTC in seconds from first second of audio captured)
UTCEnd (time in 32-bit unsigned int UTC in seconds from first second of audio captured)
Files should be placed in S3 buckets with the following folder structure:
[To be determined during design phase]
Nielsen will move files to another location as they are processed so processing status is apparent.
In the case of a stream that has one version with blackouts and one without, one with mobile and one non-mobile, each stream would have its own unique asset id.
Nielsen recommends for live-streams that the audio track associated with the live feed be segmented into 15min chunks for delivery to Nielsen.
For VoD, Nielsen recommends using a single audio file, unless the total duration is greater than 6 hours, in which case the file should be broken up into smaller chunks.
For live-streams, the audio file does not need to break on a show boundary. Nielsen recommends breaking on a convenient wall-clock time, such as on the hour, 15past, 30past, 45past etc
Please check with the Nielsen Technical support to confirm the proposed audio format is supported, and if any compression, encryption algorithms or frequency band filters are going to be used to transport the audio files to Nielsen.
SLA
The files must be delivered into the proper S3 bucket within 2 hours of the broadcast. For example, files from 1:00 AM to 1:15 AM must be delivered before 3:00 AM. The metadata file should be delivered to an S3 bucket after the audio files described in this reference file are delivered, and before any Viewing file that would use these audio files has been delivered. Please refer to the associated specifications for the SLA’s of these other files.
JSON Param Definition
Header Record
| Parameter | Description | Mandatory | Specified by | Format or Example |
|---|---|---|---|---|
| schemaversion | Json Schema Version | Yes | Nielsen | Example: S2SDTVRAssetMetaDataV2.0 |
| apid | Server App ID | Yes | Nielsen | Example: A487421B-XXXX-YYYY-8343-E3BBB66E44F2 |
| creationtime | File creation time | Yes | Client | Format: utc (time in 32-bit unsigned int UTC in seconds) |
| assetid | In-House Asset Id | Yes | Client | Format: alphanumeric,
Example: VID123456789 |
| assetname | In-House video asset name,
used for troubleshooting |
Yes | Client | Format: alphanumeric, Example: "A&E High Def East" or GraceNote channel mnemonic or call station letters |
| webpageurl | Website Identifier, used for diagnostics, can be turned off/on as needed | No | Client | Format: alphanumeric (max 2k)
Example:http://www.myapp.com/video.html |
| recordcount | # of records in body of file | Yes | Client | Format: numeric |
Header JSON Schema:
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"schemaversion": { "type": "string" },
"apid": { "type": "string" },
"creationtime": { "type": "string" },
"assetid": { "type": "string" },
"assetname": { "type": "string" },
"webpageurl": { "type": "string" },
"recordcount": { "type": "string" }
},
"required": [ "schemaversion", "apid", "creationtime", "assetid", "assetname", "recordcount" ]
}
Header Record - Example:
{
"schemaversion":"S2SDTVRAssetMetaDataV2.0",
"apid":"A487421B-XXXX-YYYY-8343-E3BBB66E44F2",
"creationtime":"1473781507",
"assetid":" VID123456789",
"assetname":"A&E High Def East",
"webpageurl":"http://www.myapp.com/video.html",
"recordcount":"100"
}
Body
| Parameter | Description | Mandatory | Specified by | Format or Example |
|---|---|---|---|---|
| audiofilename | Audio file name | Yes | Client | Example: aacFile1.aac
Audio files are assumed to be uploaded to the same directory/folder as the associated Asset Metadata file |
| referencestart | Starting in-house reference point for the audio file | Yes | Client | Format: utc (time in 32-bit unsigned int UTC in seconds)
For VoD, this will be an offset from the start of the asset For Live stream, this will be the in-house time |
| referenceend | End in-house reference point for the audio file | Yes | Client | Format: utc (time in 32-bit unsigned int UTC in seconds)
For VoD, this will be an offset from the start of the asset For Live stream, this will be the in-house time |
Note: All parameters are case sensitive.
Body Message Schema:
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"audiofilename": { "type": "string" },
"referencestart": { "type": "string" },
"referenceend": { "type": "string" }
},
"required": [ "audiofilename", "referencestart", "referenceend" ]
}
Body - Example:
{"audiofilename":"aacFile1.aac","referencestart":"1489506887","referenceend":"1489506889"}