Revision Summary Date Revision History Revision Comments 10/22/2006 0.01 New Version 0.01 release 1/19/2007 1.0 Major Version 1.0 release 3/2/2007 1.1 Minor Version 1.1 release 4/3/2007 1.2 Minor Version 1.2 release 5/11/2007 1.3 Minor Version 1.3 release 6/1/2007 1.4 Minor TDI Bug Fixes 7/3/2007 1.4.1 Editorial Changed language and formatting in the technical content. 7/20/2007 1.4.2 Editorial Changed language and formatting in the technical content. 8/10/2007 1.5 Minor Clarified the meaning of the technical content. 9/28/2007 1.5.1 Editorial Changed language and formatting in the technical content. 10/23/2007 1.5.2 Editorial Changed language and formatting in the technical content. 11/30/2007 1.5.3 Editorial Changed language
12/5/2008 2.0 Updated and revised the technical content. 1/16/2009 2.0.1 Editorial Changed language and formatting in the technical content. 2/27/2009 2.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 2.0.3 Editorial Changed language and formatting in the technical content. 5/22/2009 3.0 Major Updated and revised the technical content. 7/2/2009 3.0.1 Editorial Changed language and formatting in the technical content. 8/14/2009 3.0.2 Editorial Changed language and formatting in the technical content. 9/25/2009 4.0 Major Updated and revised the technical content. 11/6/2009 4.0.1 Editorial Changed language and formatting
in the technical content. 12/18/2009 4.0.2 Editorial Changed language and formatting in the technical content. 1/29/2010 4.1 Minor Clarified the meaning of the technical content. 3/12/2010 4.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 4.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 4.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 4.1.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 4.1.3 None No changes to the meaning, language, or formatting of the technical content.
the technical content. 9/23/2011 4.2 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 5.0 Major Updated and revised the technical content. 3/30/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 6.0 Major Updated and revised
Protocol Details Server Details Abstract Data Model Not applicable for this protocol specification. Timers Beacon: This timer controls how often are sent. The time-out interval for this timer MUST be in the range of 1 to 10 seconds, inclusive. Initialization Creating an NSC File The server MUST create an at once. The file MUST specify the IP multicast group and UDP port number to which the are addressed. It also MUST specify all headers that are needed by the client to parse the ASF packets, and assign a Format ID to each ASF header. All ASF headers in the .nsc file MUST have a different Format ID.<4><5> A previously created .nsc file can be used instead of creating a new .nsc file, if the contents of the existing file are equivalent to the new .nsc file that would otherwise be created. Transmitting Beacon Packets If the server does not have any to send (for example, if a live event has not yet started), but clients have already received an , the server SHOULD start the Beacon timer. Starting the Beacon timer when there are no MSB packets to send allows clients to remain ready to receive MSB packets. The server MAY start the Beacon timer if it is going to immediately begin transmitting MSB packets.<6> The Beacon timer MUST be configured to expire in 10 seconds or less, but not more often than once every second. Higher-Layer Triggered Events Not applicable for this protocol specification. Processing Events and Sequencing Rules Transmitting the First MSB Packet in a Stream When the server is about to transmit the first for a stream, it MUST ensure that the value of the wStreamID field in MSB packet is different from the wStreamID value that is used in the previous stream, if any. In this context, the term "stream" refers to an file, or an entry, in a server-side playlist. If the new stream uses the same ASF header as the previous stream, the most significant bit in the wStreamID field MUST be set to the opposite value of that bit in the wStreamID field that is used for the previous stream.
Index A 10 Abstract data 17 16 9 9 ASF packet ( 18, 18) 13 13 B Beacon packet ( 14, 18) 14 16 17 11 C 9 28 Client 17 18 17 19 18 18 19 17 D Data - abstract 17 16 Data – abstract 17 16 12 E 11 11 19 13 Examples ( 20, 20) F 9 9 G 7 H Higher-layer triggered events 18 16 I 25 25 25 8 Initialization 17 16 7 L Local events 19 17 18 M Message processing 18 16 Messages 13 14 15 10 10 10 10 MSB packet ( 15, 18) 15 20 15 N 8 NSC file 16 10 22 10 O 19 Other local events 17 8 P 25