...
- The heartbeats sent from the Spring libraries
- How to verify the accuracy of your implementation
- The Kantar Spring Testing Tool that provides logstream access for implementation validation
Heartbeats sent from the libraries
This section briefly explains what the heartbeats sent from the libraries should look like. A concrete example of a viewing session is used.
The content stream is started and the first request is transmitted:
...
Please use the record layout descriptions below for reference.
- counting domain: example.2cnt.net. Here, the “Sitename” is “example”.
- pl = player
- plv = player version
- sx = width of the stream window
- sy = height of the stream window
- stream = stream name
- cq = contentId
- uid = unique Id of the use process
- pst = play state (list of viewing intervals on the stream)
- dur = stream length in seconds (set up by the client)
- vt = view time in seconds (visual contact with the stream)
- First play state: 0+0+mbeswh :
The actual record output should look similar to below:
...
Note that the "uid" (uid=3f3tv5p) and stream name "stream=od" remained the same during the whole view sequence. This should always be the case when the implementation is correct.
...
Typically, this step is scheduled and completed for a single working day.
Final sign-off
Once all 3 steps are complete, Kantar Media will sign-off your implementation, confirming that all aspects are as expected.
...
Procedure Overview
Getting started
You will need the device ID of your test device and optionally the name of your app (<application>).
- For iOS, please use:
- iOS 5 or lower: the MAC address
- iOS 6 or 7: the Apple Advertising ID
- For Android, please use the Android-ID (AID) or Device-ID (DID).
You can read your device ID (MAC address, Advertising ID, AID, DID) with the help of free apps that can be downloaded from the respective app stores.
- iOS: App “my device info” at Apple App Store
- Android: App “ID” at Google Play,
- Windows Phone: Tool “device ID” at Windows Phone Marketplace
...
Your browser settings:
- Please use an html5-capable browser
- Please enable Java Script
- We recommend the use of a modern up-to-date browser such as Firefox, Chrome, ...
...
Illustration 1: Initial main screen
...
Now start the app to be tested on the test device or emulator identified in Field 2 above.
Begin your testing by starting the stream..
...
Illustration 2: Example main output screen
In the Events section of this page you will see:
...
- Red: Error
- Yellow: Warning
Once all parts of the request are correct, the app will return no error messages, indicating that your implementation is correct.
Important additional information about the on-screen interface
Below the main bars in the Events section of the page, the tool also contains 4 greyed out round ‘traffic lights’. These indicators are used to highlight the following standard mobile app actions:
...
You may see these traffic lights “go green” during your test as each action is positively verified. This is purely documentary and does not indicate whether your TV Player Report project implementation is correct.
‘Warning’ or ‘Error’ messages
Should you encounter ‘Warning’ or ‘Error’ messages then:
- Verify and check your implementation – you can view the log stream requests to help you further understand the error (see below for more information)
or - Contact the Spring technical group at support@spring.de. Please ensure that you copy our main UK TV Player support team at TVPlayerSupport@kantarmedia.com.
Viewing your log stream requests
Press the "View Request" button to view all the information in a JSON object which contains all messages from the Validator.
...
After clicking “Start test!” and a stream has been running
After starting the test tool and then starting the player, you will see the event counter counting through the number of requests as they are processed.
...
When clicking the “Viewrequests”
Part 1
In the above screen shot, we scrolled down through the list of all the heartbeats sent during the test.
...
- “uid” = the viewing session ID; generated at random by the library when it is started
- “stream” = stream identifier as defined by the broadcaster.
- “pst” = the playstates, i.e. the content playhead position(s). The position of the playhead at the time this heartbeat was sent, was at 1204 seconds.
- “vt” = viewtime.
- “cq” = The content ID, used to uniquely identify the content of the stream.
- “sy” = horizontal video resolution (as opposed to the same variable in the metadata)
- “sx” = vertical video resolution (as opposed to the same variable in the metadata)
- The other variables are additional and optional info that the broadcaster defined via the “desc”-variable.
Conclusion
...
This implementation is correct from a format point of view and the output can be correctly pro-cessed by the Kantar Spring systems.
...