ColinBrown at 00:57, 10 September 2020

2020-09-10T00:57:33Z

← Older revision		Revision as of 00:57, 10 September 2020
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|DCR & DTVR}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|US DCR & DTVR}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

Admin2: /* Unplugging of headphone */

2017-06-12T16:20:11Z

Unplugging of headphone

← Older revision		Revision as of 16:20, 12 June 2017
Line 66:		Line 66:
	*Call stop when the audio stops playback because of unplugging of headphone and withhold sending its playhead position.		*Call stop when the audio stops playback because of unplugging of headphone and withhold sending its playhead position.
	*Once the audio has resumed, call loadMetadata and playheadPosition in that order.		*Once the audio has resumed, call loadMetadata and playheadPosition in that order.
	<blockquote>''Note:'' Lock / Unlock device and app going Background / Foreground are not an interrupt scenario for radio / audio clients unless the audio stops.</blockquote>		<blockquote>'''Note:''' Lock / Unlock device and app going Background / Foreground are not an interrupt scenario for radio / audio clients unless the audio stops.</blockquote>

Admin at 05:48, 8 June 2017

2017-06-08T05:48:34Z

← Older revision		Revision as of 05:48, 8 June 2017
Line 1:		Line 1:
			{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|DCR & DTVR}} {{CurrentBreadcrumb}}
			[[Category:Digital]]

	Interrupt scenarios are use cases that lead to interruption in content (audio / video) playback. App developers should watch for these use cases and implement the Nielsen AppSDK in a way that AppSDK does accurate measurement. There are various interrupt scenarios which app dev should take care of		Interrupt scenarios are use cases that lead to interruption in content (audio / video) playback. App developers should watch for these use cases and implement the Nielsen AppSDK in a way that AppSDK does accurate measurement. There are various interrupt scenarios which app dev should take care of
	*Pause / Play		*Pause / Play

Admin: Created page with "Interrupt scenarios are use cases that lead to interruption in content (audio / video) playback. App developers should watch for these use cases and implement the Nielsen AppS..."

2017-06-07T02:20:45Z

Created page with "Interrupt scenarios are use cases that lead to interruption in content (audio / video) playback. App developers should watch for these use cases and implement the Nielsen AppS..."

New page

Interrupt scenarios are use cases that lead to interruption in content (audio / video) playback. App developers should watch for these use cases and implement the Nielsen AppSDK in a way that AppSDK does accurate measurement. There are various interrupt scenarios which app dev should take care of
*Pause / Play
*Network loss (Wi-Fi / Airplane / Cellular)
*Call Interrupt ( SIM or Third party Skype / Hangout call)
*Alarm Interrupt
*Content Buffering
*Lock / Unlock device (Video players only)
*App going Background / Foreground (Only video players without PIP mode support )
*Channel / Station Change Scenario
*Unplugging of headphone

== Interrupt scenarios for video ==
There are various interrupt scenarios which a video app dev should take care of
=== Pause / Play ===
*Call stop as soon as video is paused and withhold sending the playhead position.
*Once the video has resumed, call loadMetadata and sendID3 / playheadPosition in that order.
=== Network loss (Wi-Fi / Airplane / Cellular) ===
*Call stop as soon as network is lost and withhold sending the playhead position.
*Once the Wi-Fi is ON / Airplane is OFF / Cellular network is ON and the video has resumed, call loadMetadata and sendID3 / playheadPosition in that order.
=== Call Interrupt ( SIM or Third party Skype / Hangout call) ===
*Call stop as soon as a SIM or Skype / Hangout call is observed and withhold sending the playhead position.
*Once the SIM or Skype / Hangout call ends and the video has resumed, call loadMetadata and sendID3 / playheadPosition
=== Alarm Interrupt ===
*Call stop as soon as a device or an in-app alarm is observed and withhold sending the playhead position.
*Once the device or in-app alarm ends / is acknowledged and the video has resumed, call loadMetadata and sendID3 / playheadPosition in that order.
=== Content Buffering ===
*App dev should withhold sending the playhead position as soon as player starts content buffering
*Once the buffering ends and the audio has resumed, call sendID3 / playheadPosition.
=== Lock / Unlock device ===
*Call stop as soon as the device is locked and withhold sending the playhead position.
*Once the device is unlocked and the video has resumed, call loadMetadata and sendID3 / playheadPosition in that order.
=== App going Background / Foreground (when PIP mode is not supported / enabled) ===
*Call stop as soon as the app goes to background and withhold sending the playhead position.
*Once the app resumes to foreground and the video has resumed, call loadMetadata and sendID3 / playheadPosition in that order.
=== Channel / Station change from current channel / station to other ===
*Call stop for the current channel / station as soon as it is changed and withhold sending its playhead position.
*As soon as new channel / station starts, call loadMetadata and sendID3 / playheadPosition for the channel / station in that order.
=== Unplugging of headphone ===
*Call stop as soon as the video stops playback because of unplugging of headphone and withhold sending its playhead position.
*As soon as video resumes, call loadMetadata and sendID3 / playheadPosition

== Interrupt Scenarios for radio / audio ==
Radio / audio app dev must trigger / stop the API calls as mentioned below, in the respective interrupt scenario.
=== Pause / Play ===
*Call stop as soon as audio is paused and withhold sending the playhead position.
*Once the audio has resumed, call loadMetadata and playheadPosition in that order.
=== Network loss (Wi-Fi / Airplane / Cellular) ===
*Call stop as soon as network is lost and withhold sending the playhead position.
*Once the Wi-Fi is ON / Airplane is OFF / Cellular network is ON and the audio has resumed, call loadMetadata and playheadPosition in that order.
=== Call Interrupt ( SIM or Third party Skype / Hangout call) ===
*Call stop as soon as a SIM or Skype/Hangout call is observed and withhold sending the playhead position.
*Once the SIM or Skype/Hangout call ends and the audio has resumed, call loadMetadata and playheadPosition in that order.
=== Alarm Interrupt ===
*Call stop as soon as a device or an in-app alarm is observed and withhold sending the playhead position.
*Once the device or in-app alarm ends / is acknowledged and the audio has resumed, call loadMetadata and playheadPosition in that order.
=== Content Buffering ===
*Withhold sending the playhead position as soon as the player starts content buffering.
*Once the buffering ends and the audio has resumed, call playheadPosition.
=== Channel / Station Change Scenario ===
*Call stop for the current channel / station as soon as it is changed and withhold sending its playhead position.
*As soon as new channel / station starts, call loadMetadata and playheadPosition for the channel / station in that order.
=== Unplugging of headphone ===
*Call stop when the audio stops playback because of unplugging of headphone and withhold sending its playhead position.
*Once the audio has resumed, call loadMetadata and playheadPosition in that order.
<blockquote>''Note:'' Lock / Unlock device and app going Background / Foreground are not an interrupt scenario for radio / audio clients unless the audio stops.</blockquote>

Digital Measurement Interruption Scenarios - Revision history

ColinBrown at 00:57, 10 September 2020

Admin2: /* Unplugging of headphone */

Admin at 05:48, 8 June 2017

Admin: Created page with "Interrupt scenarios are use cases that lead to interruption in content (audio / video) playback. App developers should watch for these use cases and implement the Nielsen AppS..."