Av:Developer:Songcast:Ohz - Revision history

Simonc at 12:25, 6 November 2013

2013-11-06T12:25:13Z

← Older revision		Revision as of 12:25, 6 November 2013
Line 32:		Line 32:
	! Description		! Description
	\|- align="left" style="color:#ffffff; background-color:#008833;"		\|- align="left" style="color:#ffffff; background-color:#008833;"
-	~~! colspan="3"~~ \| Header	+	\| Header
		+	\|
		+	\|
	\|-		\|-
	\| 4		\| 4
Line 64:		Line 66:
	\| 2		\| 2
	\| Length		\| Length
-	\| The length in bytes of the whole message including this header	+	\| The length in bytes of the whole message including this header [8..5000]
-	\|-	+	\|- align="left" style="color:#ffffff; background-color:#008833;"
		+	\| Zone Query
		+	\|
	\|		\|
-	~~\| Minimum~~
-	~~\| 8~~
-	\|-
-	~~\| Maximum~~
-	~~\| 5000~~
-	~~\|- align="left" style="color:#ffffff; background-color:#008833;"~~
-	~~! colspan="3" \| Zone Query~~
	\|-		\|-
	\| 4		\| 4
Line 83:		Line 80:
	\| The queried Zone Id, where n = QueryZoneLength		\| The queried Zone Id, where n = QueryZoneLength
	\|- align="left" style="color:#ffffff; background-color:#008833;"		\|- align="left" style="color:#ffffff; background-color:#008833;"
-	~~! colspan="3"~~ \| Zone Uri	+	\| Zone Uri
		+	\|
		+	\|
	\|-		\|-
	\| 4		\| 4
Line 101:		Line 100:
	\| The URI, where q = UriLength		\| The URI, where q = UriLength
	\|- align="left" style="color:#ffffff; background-color:#008833;"		\|- align="left" style="color:#ffffff; background-color:#008833;"
-	~~! colspan="3"~~ \| Preset Query	+	\| Preset Query
		+	\|
		+	\|
	\|-		\|-
	\| 4		\| 4
Line 107:		Line 108:
	\| The queried preset number		\| The queried preset number
	\|- align="left" style="color:#ffffff; background-color:#008833;"		\|- align="left" style="color:#ffffff; background-color:#008833;"
-	~~! colspan="3"~~ \| Preset Info	+	\| Preset Info
		+	\|
		+	\|
	\|-		\|-
	\| 4		\| 4
Line 126:		Line 129:
	Each participating Sender must have a unique Zone Id. This Id is often derived from the Sender's MAC address, but any other network-unique Id is acceptable.		Each participating Sender must have a unique Zone Id. This Id is often derived from the Sender's MAC address, but any other network-unique Id is acceptable.

-	The OHZ URI for a Sender is: ohz://239.255.255.250:51972/ZoneId	+	The OHZ URI for a Sender is: <tt>ohz://239.255.255.250:51972/ZoneId</tt>

	=== From The Receiver's Perspective ===		=== From The Receiver's Perspective ===

-	In order to listen to ohz://239.255.255.250:51972/ZoneId, a Receiver should send a Zone Query message to the Multicast endpoint 239.255.255.250:51972 and listen for an equivalent Zone Uri message.	+	In order to listen to <tt>ohz://239.255.255.250:51972/ZoneId</tt>, a Receiver should send a Zone Query message to the Multicast endpoint <tt>239.255.255.250:51972</tt> and listen for an equivalent Zone Uri message.

	If no Zone Uri message is received within 100mS, then the process should be repeated.		If no Zone Uri message is received within 100mS, then the process should be repeated.
Line 140:		Line 143:
	=== From The Sender's Perspective ===		=== From The Sender's Perspective ===

-	A Sender should listen on the Multicast endpoint 239.255.255.250:51972 for Zone Query messages that match its Zone Id, and should respond with a single Zone Uri message.	+	A Sender should listen on the Multicast endpoint <tt>239.255.255.250:51972</tt> for Zone Query messages that match its Zone Id, and should respond with a single Zone Uri message.

	Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.		Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.

Grahamd: /* From The Sender's Perspective */

2011-05-12T12:52:21Z

From The Sender's Perspective

← Older revision		Revision as of 12:52, 12 May 2011
Line 140:		Line 140:
	=== From The Sender's Perspective ===		=== From The Sender's Perspective ===

-	A Sender ~~with~~ should listen on the Multicast endpoint 239.255.255.250:51972 for Zone Query messages that match its Zone Id, and should respond with a single Zone Uri message.	+	A Sender should listen on the Multicast endpoint 239.255.255.250:51972 for Zone Query messages that match its Zone Id, and should respond with a single Zone Uri message.

	Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.		Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.

Grahamd: /* Preset */

2011-05-10T10:52:47Z

Preset

← Older revision		Revision as of 10:52, 10 May 2011
Line 144:		Line 144:
	Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.		Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.

-	== ~~Preset~~ ==	+	== Presets ==

	A Sender can optionally participate in the OHZ Preset system. This allows for a Sender to be configured with a network-unique preset number that can be used by a primitive control points, such as an IR handset.		A Sender can optionally participate in the OHZ Preset system. This allows for a Sender to be configured with a network-unique preset number that can be used by a primitive control points, such as an IR handset.

Grahamd: /* From The Sender's Perspective */

2011-05-10T10:52:31Z

From The Sender's Perspective

← Older revision		Revision as of 10:52, 10 May 2011
Line 143:		Line 143:

	Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.		Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.
		+
		+	== Preset ==
		+
		+	A Sender can optionally participate in the OHZ Preset system. This allows for a Sender to be configured with a network-unique preset number that can be used by a primitive control points, such as an IR handset.
		+
		+	To participate in this system, a Sender must listen for Preset Query messages and send Preset Info messages accordingly.
		+
		+	The metadata for the Preset Info message is the same DIDL-Lite metadata that is published using the [[Av:Developer:SenderService\|Sender service]].

Grahamd: /* From The Sender's Perspective */

2011-05-10T10:47:29Z

From The Sender's Perspective

← Older revision		Revision as of 10:47, 10 May 2011
Line 139:		Line 139:

	=== From The Sender's Perspective ===		=== From The Sender's Perspective ===
		+
		+	A Sender with should listen on the Multicast endpoint 239.255.255.250:51972 for Zone Query messages that match its Zone Id, and should respond with a single Zone Uri message.
		+
		+	Whenever the Sender's OHM or OHU URI changes, it should send 3 consecutive Zone Uri messages with the new URI.

Grahamd: /* From The Receiver's Perspective */

2011-05-10T10:38:40Z

From The Receiver's Perspective

← Older revision		Revision as of 10:38, 10 May 2011
Line 134:		Line 134:
	If no Zone Uri message is received within 100mS, then the process should be repeated.		If no Zone Uri message is received within 100mS, then the process should be repeated.

-	Once a matching Zone Uri message has been received, the OHM or OHU URI is used to ~~establishe~~ an audio connection to the Sender.	+	Once a matching Zone Uri message has been received, the contained OHM or OHU URI is used to establish an audio connection to the Sender.

	The OHZ handler should continue listening for Zone Uri messages that match the Zone Id. If a different URI is published by the Sender, then audio playback should be terminated and a new audio connection established using the new OHM or OHU URI.		The OHZ handler should continue listening for Zone Uri messages that match the Zone Id. If a different URI is published by the Sender, then audio playback should be terminated and a new audio connection established using the new OHM or OHU URI.

	=== From The Sender's Perspective ===		=== From The Sender's Perspective ===

Grahamd: /* Zone Handling */

2011-05-10T10:37:43Z

Zone Handling

← Older revision		Revision as of 10:37, 10 May 2011
Line 126:		Line 126:
	Each participating Sender must have a unique Zone Id. This Id is often derived from the Sender's MAC address, but any other network-unique Id is acceptable.		Each participating Sender must have a unique Zone Id. This Id is often derived from the Sender's MAC address, but any other network-unique Id is acceptable.

-	The OHZ URI for a Sender is:	+	The OHZ URI for a Sender is: ohz://239.255.255.250:51972/ZoneId
-		+
-	ohz://239.255.255.250:51972/ZoneId	+

	=== From The Receiver's Perspective ===		=== From The Receiver's Perspective ===

Grahamd: /* Zone Id Handling */

2011-05-10T10:37:10Z

Zone Id Handling

← Older revision		Revision as of 10:37, 10 May 2011
Line 122:		Line 122:
	\|}		\|}

-	== Zone Id Handling ==	+	== Zone Handling ==

	Each participating Sender must have a unique Zone Id. This Id is often derived from the Sender's MAC address, but any other network-unique Id is acceptable.		Each participating Sender must have a unique Zone Id. This Id is often derived from the Sender's MAC address, but any other network-unique Id is acceptable.

Grahamd: /* Zone Id Handling */

2011-05-10T10:36:56Z

Zone Id Handling

← Older revision		Revision as of 10:36, 10 May 2011
Line 130:		Line 130:
	ohz://239.255.255.250:51972/ZoneId		ohz://239.255.255.250:51972/ZoneId

-	In ~~orderIf~~ a Receiver is	+	=== From The Receiver's Perspective ===
		+
		+	In order to listen to ohz://239.255.255.250:51972/ZoneId, a Receiver should send a Zone Query message to the Multicast endpoint 239.255.255.250:51972 and listen for an equivalent Zone Uri message.
		+
		+	If no Zone Uri message is received within 100mS, then the process should be repeated.
		+
		+	Once a matching Zone Uri message has been received, the OHM or OHU URI is used to establishe an audio connection to the Sender.
		+
		+	The OHZ handler should continue listening for Zone Uri messages that match the Zone Id. If a different URI is published by the Sender, then audio playback should be terminated and a new audio connection established using the new OHM or OHU URI.
		+
		+	=== From The Sender's Perspective ===

Grahamd: /* Message Format */

2011-05-10T10:20:39Z

Message Format

← Older revision		Revision as of 10:20, 10 May 2011
Line 81:		Line 81:
	\| n		\| n
	\| QueryZone		\| QueryZone
-	\| The queried ~~zone~~, where n = QueryZoneLength	+	\| The queried Zone Id, where n = QueryZoneLength
	\|- align="left" style="color:#ffffff; background-color:#008833;"		\|- align="left" style="color:#ffffff; background-color:#008833;"
	! colspan="3" \| Zone Uri		! colspan="3" \| Zone Uri
Line 87:		Line 87:
	\| 4		\| 4
	\| ZoneLength		\| ZoneLength
-	\| The length in bytes of the ~~zone~~	+	\| The length in bytes of the Zone Id
	\|-		\|-
	\| 4		\| 4
Line 95:		Line 95:
	\| p		\| p
	\| Zone		\| Zone
-	\| The ~~zone~~, where p = ZoneLength	+	\| The Zone Id, where p = ZoneLength
	\|-		\|-
	\| q		\| q