USRE47400E1 - Systems and methods for providing dual-control functionality in a networked digital media device - Google Patents
Systems and methods for providing dual-control functionality in a networked digital media device Download PDFInfo
- Publication number
- USRE47400E1 USRE47400E1 US14/877,656 US200914877656A USRE47400E US RE47400 E1 USRE47400 E1 US RE47400E1 US 200914877656 A US200914877656 A US 200914877656A US RE47400 E USRE47400 E US RE47400E
- Authority
- US
- United States
- Prior art keywords
- standard
- media
- control
- control signal
- accordance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2807—Exchanging configuration information on appliance services in a home automation network
- H04L12/2809—Exchanging configuration information on appliance services in a home automation network indicating that an appliance service is present in a home automation network
-
- H04L29/06163—
-
- H04L29/08648—
-
- H04L67/16—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L2012/284—Home automation networks characterised by the type of medium used
- H04L2012/2841—Wireless
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L2012/2847—Home automation networks characterised by the type of home appliance used
- H04L2012/2849—Audio/video appliances
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R2227/00—Details of public address [PA] systems covered by H04R27/00 but not provided for in any of its subgroups
- H04R2227/005—Audio distribution systems for home, i.e. multi-room use
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R2420/00—Details of connection covered by H04R, not provided for in its groups
- H04R2420/07—Applications of wireless loudspeakers or wireless microphones
Definitions
- the present invention relates to systems and methods for providing dual-control functionality in a networked digital media device.
- Embodiments of the invention have been particularly developed to allow a wireless speaker subsystem to perform advanced, non-standard, functionalities under the control of an appropriately configured control device, yet still operate in a standard manner under the control of a standard control device. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts.
- a networked speaker subsystem unit typically includes a central processing unit coupled to a memory unit, a networking interface and audio output hardware (such as an amplifier and one or more speaker cones).
- the central processing unit provides a media rendering functionality whereby data indicative of audio received via the networking interface is processed to provide a corresponding audible output via the audio output hardware.
- the networking interface typically implements a wireless networking standard such as the IEEE 802.11 standard.
- Control of such a speaker subsystem unit is often achieved by way of a networked control device, which provides control signals directly or indirectly to the speaker subsystem unit over a network.
- the control device must first identify the speaker subsystem unit on the network, and subsequently be able to understand and implement the media control protocol used by that unit.
- a critical decision to be made is whether or not to aim for compliance with an existing standard, such as the UPnP AV standard. To do so typically involves sacrificing (or significantly limiting) the ability to provide various non-standard advanced functionalities. However, not doing so might lead to a poor consumer perception, or downstream consumer frustration when interoperability difficulties are experienced.
- Described herein are devices, systems and methods for providing dual control functionality in a digital media device, predominately for the purposes managing wireless audio systems.
- wireless audio systems are considered as a primary example, various embodiments are equally applicable to other audio systems, particularly other networked audio systems, and networked digital media playback systems generally.
- One embodiment provides a method performed by a networked digital media device for providing dual-control functionality, the method including the steps of:
- One embodiment provides a method wherein the standard and non-standard devices are embedded devices of a root device.
- One embodiment provides a method the standard digital media playback device and the non-standard digital media playback device are each advertised in accordance with a common open connectivity protocol.
- One embodiment provides a method wherein the common open connectivity protocol is UPnP.
- One embodiment provides a method wherein the standard media control protocol is compliant with the UPnP AV standard.
- One embodiment provides a method wherein the standard device is a MediaRenderer.
- One embodiment provides a method wherein the standard device is a MediaServer.
- One embodiment provides a method wherein the non-standard multimedia protocol provides control access to one or more advanced services.
- One embodiment provides a method wherein the one or more advanced services relate to group and/or zone interoperability.
- One embodiment provides a method wherein the one or more advanced services relate to surround sound functionality.
- One embodiment provides a method wherein the non-standard device is an embedded services device for encapsulating one or more non-standard UPnP services.
- One embodiment provides a method wherein the one or more non-standard UPnP services relate to group and/or zone interoperability.
- One embodiment provides a method wherein the one or more non-standard UPnP services relate to surround sound functionality.
- One embodiment provides a method wherein the networked digital media device is a virtual device representative of a networked media system including by a plurality of distributed hardware devices.
- One embodiment provides a method wherein a control signal received in accordance with the standard media control protocol is prioritised over a control signal received in accordance with the non-standard media control protocol.
- One embodiment provides a method wherein a control signal received in accordance with the standard media control protocol is temporarily prioritised over one or more control signals received in accordance with the non-standard media control protocol.
- One embodiment provides a method according to claim 1 including the steps of:
- One embodiment provides a method wherein the networked media device is a networked media playback device.
- One embodiment provides a method wherein the networked media playback device is a networked speaker subsystem unit.
- One embodiment provides a method wherein the networked media playback device is a wireless speaker subsystem unit.
- One embodiment provides a method wherein the networked media device is media server.
- One embodiment provides a computer-readable medium encoded with a set of instructions that when executed by one or more processors cause the one or more processors to carry out a method as described herein.
- One embodiment provides a networked digital media device for providing dual-control functionality, the device being configured to:
- One embodiment provides a playback unit wherein the networking interface includes a radio interface and wherein the computer network is a wireless network.
- Particular embodiments may provide all, some, or none of these aspects, features, or advantages. Particular embodiments may provide one or more other aspects, features, or advantages, one or more of which may be readily apparent to a person skilled in the art from the drawings, descriptions, and claims herein.
- FIG. 1 shows a networked media system according to one embodiment.
- FIG. 2 shows a method according to one embodiment.
- FIG. 3 shows a method according to one embodiment.
- FIG. 4 shows a method according to one embodiment.
- FIG. 5 shows a networked media system according to one embodiment.
- FIG. 6 shows a wireless speaker subsystem unit according to one embodiment.
- a networked digital media device advertises a standard digital media device, which is discoverable and controllable by a standard control device in accordance with a standard media control protocol (also referred to as a Device Control Protocol, or DCP).
- the networked digital media device also advertises a non-standard digital media playback device, the non-standard device being discoverable and controllable by a non-standard control device in accordance with a non-standard media control protocol.
- DCP Device Control Protocol
- the networked digital media device also advertises a non-standard digital media playback device, the non-standard device being discoverable and controllable by a non-standard control device in accordance with a non-standard media control protocol.
- a networked digital media device is, in some cases, a networked digital media playback device, which is capable of rendering digital media delivered to it via a computer network.
- a networked digital media playback device which is capable of rendering digital media delivered to it via a computer network.
- the UPnP AV standard describes such a device as a MediaRenderer.
- wireless speakers are used as an example of a networked digital media playback device.
- Those of ordinary skill in the art would readily be able to modify the description provided herein that is for wireless speakers and apply the methods and apparatuses to other discrete media devices. The description is provided in terms of wireless speakers in order to keep the description simple and not obscure various significant concepts.
- a networked digital media device includes a media server.
- a media server includes (or is coupled to) a storage device that maintains data indicative of media, such as digital audio files.
- a control device also referred to as a controller, Digital Media Controller, DMC, or control device
- DMC Digital Media Controller
- a networked digital media system is a system that allows one or more devices connected via a computer network to render digital media.
- a wireless audio system is used as an example of a networked digital media playback system.
- Those of ordinary skill in the art would readily be able to modify the description provided herein that is for a wireless audio system and apply the methods and apparatuses to other digital media playback systems.
- the description is provided in terms of a wireless audio system in order to keep the description simple and not obscure various significant concepts.
- FIG. 1 illustrates a basic digital media playback system 100 .
- System 100 includes wireless speakers 101 a and 101 b, a wireless access point 102 , a media server 103 , a standard control device 104 , and an advanced control device 105 .
- these components are connected to a common wireless network 106 , in the present circumstances being a wireless network in accordance with the IEEE 802.11 standard.
- Wireless speakers 101 a and 101 b are used to render and play back digital media provided by media server 103 , or provided at another location on network 106 .
- media is stored on one of the control devices, or a portable media device that is connected to a networked cradle device.
- Each wireless speaker 101 a and 101 b includes a network interface 112 for connecting to network 106 , in the present example via access point 102 . Data indicative of command signals is received via this network, along with data indicative of digital media for playback.
- a central processing unit (CPU) 113 operates in conjunction with memory 114 , and is responsible for rendering content, processing command signals, and the like.
- Memory 114 includes software instructions 115 , which, among other functions, allow wireless speakers 101 a and 101 b to perform various methods, including methods described herein. It is noted that not all instructions required for performing these methods need be in memory 104 at a given time.
- Wireless speakers 101 a and 101 b additionally include respective audio outputs 117 (which in some embodiments includes one or more speaker cones, or other analogue outputs such as audio jacks), for facilitating playback of rendered digital media as audio.
- Control devices 104 and 105 may include 802.11 type networked remote controls, or other networked devices.
- a control device might take the form of a portable electronic device having a 802.11 type network connection (such as a cellular phone, PDA, portable media player, or the like), purpose-built remote having a 802.11 type network connection, or a personal computer connected to network 106 and running appropriate software.
- standard control software such as UPnP control device software, is able to be downloaded to a device thereby to provide control device functionality.
- control device software is downloaded to an MP3 player, such that the MP3 player is able to coordinate playback of locally stored media via networked media playback devices.
- FIG. 2 illustrates a method 200 according to an embodiment of the present invention.
- method 200 is performed by wireless speaker 101 a (or, for that matter, speaker 101 b) based on software instructions 115 .
- Step 201 includes connecting to network 106 , which may occur substantially in the conventional manner.
- Step 202 includes advertising a standard digital media playback device, which in the present examples takes the form of a standard UPnP AV media device, more particularly a standard MediaRenderer. This standard UPnP media device is discoverable and controllable in accordance with the Universal Plug and Play Audio and Video (UPnP AV) standard.
- Step 203 includes advertising a non-standard digital media playback device, which in the present example takes the form of a proprietary UPnP Services Device.
- the Services Device is discoverable in accordance with the UPnP protocol, although the manner of control (and the services provided) goes beyond the scope of what is provided by way of the UPnP AV standard. That is, the Services Device is controllable in accordance with a non-standard protocol.
- the UPnP AV standard is provided by the Digital Living Network Alliance (DLNA). Details of this standard are available from www.dlna.org and www.upnp.org. Although the UPnP AV standard is used as a particular example throughout this specification, it will be appreciated that the general methodologies herein are applicable to other standards.
- DLNA Digital Living Network Alliance
- a media-specific UPnP device can adopt various roles on a given network, largely in line with the definitions described by DLNA in the roles of a Digital Media Renderer (also referred to as a DMR or MediaRenderer) and Digital Media Server (also referred to as a DMS or MediaServer).
- the present approach includes adopting a root UPnP device based on the UPnP Basic Device Template, such that the root device is conveniently discoverable via Simple Service Discovery Protocol (SSDP).
- SSDP Simple Service Discovery Protocol
- This root device is configured to advertise at least one standard UPnP media device (for example a MediaRenderer or MediaServer), thereby to fulfill the DLNA standard.
- a standard UPnP AV control device is able to discover, for the relevant device, a standard MediaRenderer and/or MediaServer device (a wireless speaker is, in some embodiments, able to adopt both roles, for example where media is stored in memory).
- a standard MediaRenderer and/or MediaServer device a wireless speaker is, in some embodiments, able to adopt both roles, for example where media is stored in memory.
- any instance of a MediaRenderer should provide services including RenderingControl, ConnectionManager and AVTransport, as well as other standard UPnP non-media services.
- any instance of MediaServer should provided services including ContentDirectory and ConnectionManager services, as well as other standard UPnP non-media services.
- Non-standard (e.g. advanced) services and devices can, by encapsulation in the Services Device, effectively be added to the root device without modification to the standard UPnP device or service descriptions.
- This approach is particularly advantageous in the sense that additional advanced functionalities may be implemented whilst, at the same time, avoiding the need for future compliance with respect to the standard UPnP AV standard control protocol (other than regression testing).
- Wireless speaker 101 a connects to network 106 at step 301 .
- Wireless speaker 101 a implements a Dynamic Host Configuration Protocol (DHCP) client, which searches for a DHCP server at step 302 .
- DHCP Dynamic Host Configuration Protocol
- Such a server is generally responsible for the assignment of IP addresses across a network, such as network 106 . If, at decision 303 , no DHCP server is available, wireless speaker subsystem 101 a self-assigns an IP address at step 304 . Otherwise, an available DHCP server assigns an IP address to wireless speaker 101 a at step 305 . In either case, the IP address assigned is used by wireless speaker 101 a in subsequent network operations.
- wireless speaker 101 a advertises itself across network 106 at step 306 (in the present circumstances, this includes steps 202 and 203 disclosed above).
- wireless speaker 101 a provides a discovery message that communicates to other devices on network 106 a relatively small data packet indicative of wireless speaker 101 a.
- the data packet includes the wireless speaker subsystem's MAC address.
- Step 307 includes conducting a discovery search across network 106 for devices of interest—such as other wireless speaker subsystems or groups representative of wireless audio systems (such as virtual devices allowing control of a plurality of physical wireless speaker subsystems that operate as a grouped speaker set).
- the discovery search includes the provision of a probe frame, and in response to this probe frame a similar discovery message to that mentioned above is provided by each complementarily discoverable device on network 106 to wireless speaker 101 a.
- step 306 is repeated at a later point in time.
- step 306 on a first occasion, includes advertising the Services Device, and on a second occasion includes advertising the standard MediaRenderer.
- the ordering of these varies between embodiments. However, it is permissible however to just advertise the Services Device where normal UPnP Services are unavailable—this might be during initial boot up of the speaker or where initial first-run configuration is required (e.g. to configure networking and group structure).
- media server 103 is configured to perform a method generally along the lines of method 300 . However, rather than advertising a standard MediaRenderer, it advertises a standard MediaServer.
- media server 103 includes a cradle for connecting a personal media player (such as an MP3 player) to network 205 , such that media stored on that player is made available for playback via speaker 101 a and 101 b.
- a personal media player such as an MP3 player
- media server 103 includes a cradle for connecting a personal media player (such as an MP3 player) to network 205 , such that media stored on that player is made available for playback via speaker 101 a and 101 b.
- Control devices 104 and 105 also implement a method along the lines of method 300 . It will be appreciated that this effectively results in a discovery protocol whereby each of control devices 104 and 105 discovers wireless speakers 101 a and 101 b (or, more specifically, none or more of the embedded devices advertised by those speakers), irrespective of the order by which the devices connect to network 106 .
- wireless speaker 101 a advertises both a standard UPnP MediaRenderer and the Services Device.
- the Services Device provides encapsulation for non-standard service extensions, and such embedded services and devices can be added to the Services Device without modification to the standard UPnP Device or Service descriptions.
- non-standard services provided by the Services Device might include:
- the Services Device provides advanced functionalities that allow speakers 101 a and 101 b to operate as a stereo pair. That is, a stereo audio file is able to be rendered by these speakers such that one plays a left-channel signal and the other synchronously plays a right-channel signal.
- This stereo pair is controlled (and optionally configured) in accordance with a non-standard media control protocol, allowing for control that goes beyond the UPnP standard (for example, left/right balance adjustment, stereo widening, and so on).
- This non-standard control protocol is implemented by advanced control device 105 . For example, this control device and the speakers might share a common manufacturer, or be otherwise designed to be specifically compatible one another.
- control device 105 is used to control playback of audio via the stereo pair defined by speakers 101 a and 101 b, and coordinate functions relating to the group relationship between these individual speakers in the context of the pair.
- control is not able to be achieved by way of standard control device 104 , which is only configured to implement the standard UPnP AV media control protocol.
- standard control device 104 is able to discover, in the expected and conventional manner, a standard MediaRenderer device corresponding to each of speakers 101 a and 101 b. In this manner, the standard control device is able to coordinate playback of media at either of these speakers.
- a virtual device may be defined for a stereo speaker pair, or other group/zone defined by a plurality of speakers.
- such a virtual device is defined in a similar manner to the individual speakers, such that a standard control device is able to discover a standard MediaRenderer (which is in fact representative of the two speakers, allowing the pair to be controlled as a single standard MediaRenderer).
- a virtual device (a group or a zone) does not have a conventional hardware manifestation in the sense that the wireless audio system includes several individual wireless speaker subsystems.
- the standard and non-standard devices advertised by such a virtual device do in effect share common hardware.
- Virtual devices are discoverable on a network in the same way as physical devices, and physical devices communicate with virtual devices as they would with other physical devices.
- a virtual device has its own IP address.
- a virtual device does not have IP addresses, for example as a result of a lower-level protocol running atop that virtual device.
- a virtual device includes one or more virtual devices, and the virtual device has an IP address whilst the virtual devices may or may not have respective IP addresses.
- a rudimentary control device i.e. the cellular telephone
- the cellular telephone may be used to achieve basic playback of audio via an advanced wireless audio system.
- FIG. 4 illustrates a method 400 for managing such a conflict according to one embodiment.
- a control signal received in accordance with the standard media control protocol is prioritized over a control signal received in accordance with the non-standard media control protocol. More particularly, a control signal received in accordance with the standard media control protocol is temporarily prioritized over one or more control signals received in accordance with the non-standard media control protocol.
- Method 400 commences at step 401 , where a wireless speaker receives a first control signal in accordance with the non-standard media control protocol.
- a wireless speaker receives a first control signal in accordance with the non-standard media control protocol.
- This is a relatively arbitrary starting point, and might, for example, include a speaker being under instruction to playback audio in the context of a group or zone, either as a master or a slave device.
- that speaker adopts a first state corresponding to the first control signal.
- that state might include rendering a stream of digital media from a particular source based on a particular synchronization protocol at a given volume.
- step 403 the speaker receives a second control signal in accordance with the standard UPnP AV media control protocol, and step 404 includes being responsive to the second control signal for adopting a second state corresponding to the second control signal.
- step 404 includes being responsive to the second control signal for adopting a second state corresponding to the second control signal.
- the wireless speaker ceases what it was doing, and commences playing back that audio track at a volume determined by the standard control device. If the speaker was operating as part of a group or zone, that ceases upon adopting this second state.
- Step 405 includes receiving, in accordance with the standard media control protocol, a third control signal indicative of an instruction to adopt a dormant state, or otherwise realizing a timeout condition.
- the crux of step 405 is an assumption or realization that standard control device 104 is no longer taking control of the relevant speaker.
- the speaker seeks to identify a fourth state related to the first state at 406 .
- a fourth state related to the first state at 406 .
- the relevant speaker was previously operating as part of a group or zone, it attempts to identify that group or zone, and re-join. This is in some embodiments achieved by analyzing UPnP commands provided to the speaker in accordance with the non-standard media control protocol during the period of time during which the standard control device was in control, which are optionally buffered in internal memory. If a relevant fourth state is able to be identified, and optionally subject to a final check of predefined exception conditions (i.e. whether it is reasonable to adopt the identified state), the speaker adopts the fourth state.
- a speaker initially operates under the control of a non-standard control point, for example playing back audio as part of a speaker set.
- a standard control point attempts to takes control of the speaker, which it is able to do. From that point, the speaker behaves as instructed by the standard control point. Once that control ends, the speaker re-instates itself under the influence of the non-standard control point, and behaves as it would have were it not for the impact standard control device (optionally be taking into account instructions from the non-standard device that were received, but not implemented due to prioritization of the standard control device).
- commands received in accordance with the non-standard protocol are not actioned. However, these may be stored and/or monitored to assist in identification of the fourth state at an appropriate time.
- FIG. 5 illustrates a residential house 501 having wireless speakers 502 to 513 . These are arranged in various groups (for example to provide stereo pairs and/or surround arrangements, as indicated by 520 and 530 ) and zones. In particular, all of the wireless speakers belong to a common “house zone”, which is used to effect playback of a common track synchronously across all of the wireless speakers in house 501 .
- an advanced control device is used to effect playback of media located on a networked media server across the house zone. This is used to create a continuous ambience throughout the house, with music playing on a substantially continuous basis.
- a visitor wishes to share with an audio track contained on a UPnP enabled cellular telephone (or other portable device). This visitor is able to discover a speaker on which to play back the relevant track on one of the speakers, due to the availability of standard UPnP MediaRenderer devices.
- a given MediaRenderer might be named “Kitchen Speaker” to assist the visitor in identifying it as a speaker in the kitchen.
- the visitor plays the relevant track through a selected one of the discovered standard MediaRenderers, during which time the concerned speaker or speakers leaves the house zone, and cease playing the ambient music being streamed across that zone.
- the visitor subsequently stops using the speaker (for example, this might be assumed to have occurred when the speaker adopts a dormant state for a predetermined period of time, such as one minute or thereabouts). At that point in time, the speaker rejoins the family zone, and continues to playback the ambient music synchronously with the other speakers.
- UPnP device To assist in understanding a manner by which dual control might be implemented on a UPnP device, provided below is an exemplary XML device description for a root device, according to one embodiment. This is intended to be indicative only.
- FIG. 6 shows a wireless speaker subsystem 601 , which is appropriate for use in the above embodiments.
- Wireless speaker subsystem 601 includes an input array 602 for receiving audio signals.
- Array 602 includes a SPDIF input, along with various other standard and proprietary digital audio inputs.
- array 602 includes one or more analogue audio inputs, in which case wireless speaker subsystem 601 includes an analogue to digital converter for converting analogue audio signals into digital form.
- a processing unit e.g., a central processing unit (CPU) 603 , which operates in conjunction with memory 604 .
- Memory 604 includes software instructions 605 which, among other functions, allow wireless speaker subsystem 601 to perform methods described herein. It is noted that not all instructions required for performing these methods need be in memory 604 at a given time.
- Wireless speaker subsystem 601 is, for the sake of example, configured to be a group leader, and presents a virtual interface for a wireless audio system, and in this manner also becomes responsible for fetching media from a server, or in the case of an SPDIF stream, partially recovering that stream from a digital input. Data indicative of this media or stream is then distributed to the other devices in the group.
- CPU 603 is responsible for administering playback of a received audio signal. In a broad sense, this includes two distinct tasks. Firstly, using a wireless network interface 606 , providing instructions to other wireless speaker subsystems to play respective components of the audio signal. Secondly, using an audio output 607 (which in some embodiments includes one or more speaker cones), playing back the intended center wireless speaker subsystem component of the audio signal.
- an audio output 607 which in some embodiments includes one or more speaker cones
- Wireless speaker subsystem 601 also includes an infrared port 610 .
- This infrared port receives infrared control signals from a compatible infrared remote controller 611 .
- the speaker and, in some cases, the group for which the speaker is leader
- wireless video units that receive over a wireless network data indicative of video and provide that video via a video output such as an LCD screen or an analogue or digital connection port.
- OFDM is one example of a multicarrier system in which the signal for transmission is split into a set of subcarriers.
- the invention may also be applicable to other wireless receivers that use multicarriers.
- base station access point
- AP access point
- client mobile device
- STA STA
- scope of the invention is not limited to devices that are labeled with those terms.
- the invention may be embodied in receivers and transceivers operating in other RF frequency ranges.
- a transceiver embodiment for operation conforming to the IEEE 802.11 OFDM standards has been described, the invention may be embodied in transceivers conforming to other standards and for other applications, including, for example other WLAN standards and other wireless standards.
- IEEE 802.11a COFDM wireless LANs and links wireless Ethernet, HIPERLAN 2, European Technical Standards Institute (ETSI) broadband radio access network (BRAN), and multimedia mobile access communication (MMAC) systems, wireless local area networks, local multipoint distribution service (LMDS) IF strips, wireless digital video, wireless USB links, wireless IEEE 1394 links, TDMA packet radios, low-cost point-to-point links, voice-over-IP portable “cell phones” (wireless Internet telephones), etc.
- ETSI European Technical Standards Institute
- MMAC multimedia mobile access communication
- wireless and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium.
- the term does not imply that the associated devices do not contain any wires, although in some embodiments they might not.
- processor may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory.
- a “computer” or a “computing machine” or a “computing platform” may include one or more processors.
- the methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein.
- Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included.
- a typical processing system that includes one or more processors.
- Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit.
- the processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM.
- a bus subsystem may be included for communicating between the components.
- the processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth.
- the processing system in some configurations may include a sound output device, and a network interface device.
- the memory subsystem thus includes a computer-readable medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein.
- computer-readable code e.g., software
- the software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system.
- the memory and the processor also constitute computer-readable medium encoded with computer-executable code.
- a computer-readable medium may form, or be includes in a computer program product.
- the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer or distributed network environment.
- the one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PC personal computer
- PDA Personal Digital Assistant
- each of the methods described herein is in the form of a computer-readable medium encoded with a set of instructions, e.g., a computer program that are for execution on one or more processors, e.g., one or more processors that are part of a wireless speaker subsystem unit or other wireless media rendering device.
- a computer-readable medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method.
- aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects.
- the present invention may take the form of computer-readable medium (e.g., a computer program product on a computer-readable storage medium) encoded with computer-readable program code embodied in the medium.
- the software may further be transmitted or received over a network via a network interface device.
- the computer-readable medium is shown in an exemplary embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
- the term “computer-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention.
- a computer-readable medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
- Non-volatile media includes, for example, optical, magnetic disks, and magnetooptical disks.
- Volatile media includes dynamic memory, such as main memory.
- Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.
- the term “computer-readable medium” shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media, a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that when executed implement a method, a carrier wave bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions a propagated signal and representing the set of instructions, and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.
- an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.
- Variants of the IEEE 802.11 standard as used herein means the variants and proposed variants of the IEEE 802.11 standard. Variants are versions defined in clauses of the standard and proposed amendments of the standard.
- the SPDIF enabled device becomes the leader.
- the group and the media source will not be implicitly linked together, so it may be possible for one device to have the SPDIF input and another to provide the streaming source from SPDIF.
- a networked digital media device may be connected through any form of computer network including networks with wired and wireless physical layers and networks consisting of multiple physical layers.
- the network through which the digital media device is connected does not affect the operation of the group other than to partially vary the extent to which synchronous playback is possible.
- a set of wireless speakers is used as an example of a networked digital media player, the invention is not limited to wireless speakers.
- the media devices include a radio interface and the network includes a wireless network
- the invention is applicable to media devices that can connect to a computer network.
- the description is provided in terms of wireless speakers in order to keep the description simple and not obscure the inventive concepts.
- a wireless audio system is used as an example of a networked digital media playback system—i.e., as an example of a system that allows one or more devices connected via a computer network to render digital media
- the invention is not limited to a wireless audio system.
- Those of ordinary skill in the art would readily be able to modify the description provided for wireless audio systems herein and apply the methods and apparatuses to other digital media playback systems.
- the description is provided in terms of wireless speakers and a wireless audio system in order to keep the description simple and not obscure the inventive concepts.
- any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others.
- the term comprising, when used in the claims should not be interpreted as being limitative to the means or elements or steps listed thereafter.
- the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B.
- Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.
- Coupled should not be interpreted as being limitative to direct connections only.
- the terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other.
- the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means.
- Coupled may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.
Landscapes
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
-
- (i) advertising a standard digital media playback device, the standard digital media playback device being discoverable and controllable by a standard control device in accordance with a standard media control protocol; and
- (ii) advertising a non-standard digital media playback device, the non-standard device being discoverable and controllable by a non-standard control device in accordance with a non-standard media control protocol;
- wherein the standard digital media playback device and the non-standard digital media playback device share common hardware.
-
- (iii) receiving, in accordance with the non-standard media control protocol, a first control signal;
- (iv) being responsive to the first control signal for adopting a first state corresponding to the first control signal;
- (v) receiving, in accordance with the standard media control protocol, a second control signal;
- (vi) being responsive to the second control signal for adopting a second state corresponding to the second control signal;
- (vii) receiving, in accordance with the standard media control protocol, a third control signal indicative of an instruction to adopt a dormant state;
- (viii) being responsive to the third control signal for identifying a fourth state related to the first state; and
- (ix) selectively adopting the fourth state.
-
- (iii) receiving, in accordance with the non-standard media control protocol, a first control signal;
- (iv) being responsive to the first control signal for adopting a first state corresponding to the first control signal;
- (v) receiving, in accordance with the standard media control protocol, a second control signal;
- (vi) being responsive to the second control signal for adopting a second state corresponding to the second control signal;
- (vii) being responsive to a timeout condition for identifying a fourth state related to the first state; and
- (viii) selectively adopting the fourth state.
-
- (i) advertising a standard digital media playback device, the standard digital media playback device being discoverable and controllable by a standard control device in accordance with a standard media control protocol; and
- (ii) advertising a non-standard digital media playback device, the non-standard device being discoverable and controllable by a non-standard control device in accordance with a non-standard media control protocol;
- wherein the standard digital media playback device and the non-standard digital media playback device share common hardware.
-
- a networking interface for connecting to a computer network;
- a first processor for carrying out a discovery process on the computer network for allowing mutual discovery of the device, the none or more complementary devices, and the none or more complimentary multimedia systems;
- a second processor for advertising a standard digital media playback device, the standard digital media playback device being discoverable and controllable by a standard control device in accordance with a standard media control protocol; and
- a third processor for advertising a non-standard digital media playback device, the non-standard device being discoverable and controllable by a non-standard control device in accordance with a non-standard media control protocol.
-
- Group Control. In broad terms, this allows multiple speakers to operate as a single set, for example as a 5.1 channel surround speaker set.
- Zone Control. In broad terms, this allows multiple groups of speakers to operate as a single zone. For example, existing speaker sets defined by groups are linked together, for example to allow synchronized playback across a plurality of groups.
- Basic Rendering. In broad terms, this governs a non-standard approach to rendering content. For example, in some cases this allows implementation of a proprietary or otherwise non-standard synchronization protocol.
- Surround Sound. This allows various surround sound control functionalities to be implemented within a group. For example, each speaker within a group takes on a role defined within a predetermined surround sound arrangement (such as a 5.1 channel arrangement). In this manner, by way of illustration, a “front left” speaker renders only a portion of a stream that is designated for the “front left” speaker.
<?xml version=“1.0” encoding=“utf-8”?> |
<root xmlns= “urn:schemas-upnp-org:device-1-0”> |
<specVersion> |
<major>1</major> | |
<minor>0</minor> |
<specVersion> | |
<URLBase>base URL for all relative URLs</URLBase> | |
<device> |
<deviceType>urn:schemas-avegasystems- | |
com:device:AiosDevice:1</deviceType> | |
<friendlyName>short user-friendly title</friendlyName> | |
<manufacturer>manufacturer name</manufacturer> | |
<manufacturerURL>URL to manufacturer | |
site</manufacturerURL> | |
<modelDescription>long user-friendly title</modelDescription> | |
<modelName>model name</modelName> | |
<modelNumber>model number</modelNumber> | |
<modelURL>URL to model site</modelURL> | |
<serialNumber>manufacturer's serial number</serialNumber> | |
<UDN>uuid:UUID</UDN> | |
<UPC>Universal Product Code</UPC> | |
<iconList> |
<icon> |
<mimetype>image/format</mimetype> | |
<width>horizontal pixels</width> | |
<height>vertical pixels</height> | |
<depth>color depth</depth> | |
<url>URL to icon</url> |
</icon> | |
XML to declare other icons, if any, goes here |
</iconList> | |
<serviceList> | |
</serviceList> | |
<deviceList> | |
</deviceList> |
<presentationURL>URL for presentation</presentationURL> | |
</device> |
</root> |
-
- xml: Required for all XML documents.
- root: Required. Includes um:schemas-upnp-org:device-1-0 as the value for the xmlns attribute; this references the UPnP Template Language (described below). Case sensitive and contains all other elements describing the root device as per the UPnP Basic Device Template. Note that URLBase is Optional and will not be included in the present template. Relative URLs are not presently used.
- device: Contains the following sub elements:
- deviceType: UPnP device type. The root device is a non-standard device and, for the sake of the present example, conforms to the following description: urn:schemas-avegasystems-com:device:AiosDevice:1 where 1 is the integer version number. Period characters in the domain name must be replaced with hyphens in accordance with RFC 2141. The device type suffix must be <=64 chars, not counting the version suffix and separating colon. Single URI.
- friendlyName: This aligns with the friendly name defined for any other devices (ie: the MediaRenderer) so presenting a uniform device name. A default friendly name shall be provided as part of the manufacturing configuration data however user changes to this element should be stored separately to the initial factory settings. String. Should be <64 characters.
- manufacturer: Manufacturer's name which can be device specific and will be part of the manufacturing configuration data. String. Should be <64 characters.
- manufacturerURL: Absolute URL for the manufacturer's web site. This can be device specific and where space on device permits this field shall be included as part of the manufacturing configuration data. Single URL<1024 characters
- modelDescription: Long description for end user. Where space on the device permits this field shall be included as part of the manufacturing configuration data. String. Should be <128 characters.
- modelName: Model name. Where space on the device permits this field shall be included as part of the manufacturing configuration data. String. Should be <32 characters.
- modelNumber: Model number. Where space on the device permits this field shall be included as part of the manufacturing configuration data. String. Should be <32 characters.
- modelURL: Absolute URL to the web site for model. Where space on the device permits this field shall be included as part of the manufacturing configuration data. Single URL <1024 characters.
- serialNumber: Serial number. Where space on the device permits this field shall be included as part of the manufacturing configuration data. String. Should be <64 characters.
- UDN: Unique Device Name. Universally-unique identifier for the device, generated internally in the same way as other UUIDs. Must be the same over time for a specific device instance (i.e., must survive reboots). Must match the value of the NT header in device discovery messages. Must match the prefix of the USN header in all discovery messages. See UPnPArchitecture Section 1 on device discovery which explains the standard NT and USN headers. Must begin with uuid: followed by a UUID suffix. Single URI, maximum length 68 bytes including “uuid:” portion. Note that UUID formatting hyphens are optional and for consistency shall not normally be included.
- UPC: Universal Product Code. Not included for root device.
- iconList: Used for managing icons, and sub-element descriptions follow the UPnP Basic Device Template.
- serviceList: In version 1.0 of the UPnP Device Architecture, the serviceList element was required, and it was required to contain at least one service element. These requirements were subsequently rescinded to accommodate the Gateway and Basic device types. If the device has no services, the serviceList element may be omitted entirely, or it may be present but contain no service elements. Appendix A of the UPnP Basic: Device Template suggests that older CPs may enforce the legacy requirement that a device must contain at least one service. Unless a concrete requirement can be determined to do this the root shall not have any associated services, state variables or the serviceList element.
- deviceList: The root shall have an embedded instantiation of at least one device defined by a UPnP Forum working committee in order to satisfy the role as a MediaRenderer or MediaServer, if and only if root device has embedded devices (such as the Services Device). Contains the following sub element:
- device: Repeat once for each embedded device defined by a UPnP Forum working committee. If UPnP vendor differentiates device by embedding additional UPnP devices, repeat once for each embedded device. In all cases will contain the same sub elements as defined above for root sub element device. Note that it is essential that all embedded devices have unique and persistent UUIDs, the UUIDs differentiate the individual devices not the physical product.
- presentation URL: This element provides an absolute URL to presentation for the device. Single URL<1024 characters.
<device> |
<deviceType>urn:schemas-avegasystems- | |
com:device:AiosDevice:1</deviceType> | |
<friendlyName>short user-friendly title</friendlyName> | |
<manufacturer>manufacturer name</manufacturer> | |
<manufacturerURL>URL to manufacturer site</manufacturerURL> | |
<modelDescription>long user-friendly title</modelDescription> | |
<modelName>model name</modelName> | |
<modelNumber>model number</modelNumber> | |
<modelURL>URL to model site</modelURL> | |
<serialNumber>manufacturer's serial number</serialNumber> | |
<UDN>uuid:UUID</UDN> | |
<UPC>Universal Product Code</UPC> | |
<iconList> |
<icon> |
<mimetype>image/format</mimetype> | |
<width>horizontal pixels</width> | |
<height>vertical pixels</height> | |
<depth>color depth</depth> | |
<url>URL to icon</url> |
</icon> | |
XML to declare other icons, if any, goes here |
</iconList> | |
<serviceList> | |
</serviceList> | |
<deviceList> | |
</deviceList> | |
<presentationURL>URL for presentation</presentationURL> |
</device> |
-
- device: Contains the following sub elements:
- deviceType: UPnP device type. The Services Device is a non-standard device, and conform to the following description: urn: schemas-avegasystems-com:device: AiosServices:1 where 1 is the integer version number. Period characters in the domain name should be replaced with hyphens in accordance with RFC 2141. The device type suffix must be <=64 chars, not counting the version suffix and separating colon. Single URI.
- friendlyName: This element must align with the friendly name defined in the corresponding root element so presenting a uniform device friendly name. String. Should be <64 characters.
- manufacturer: This element must align with the manufacturer's name defined in the corresponding root. String. Should be <64 characters.
- manufacturerURL: Where populated, this absolute URL for the manufacturer's web site must align with the corresponding Root element. Single URL <1024 characters
- modelDescription: Where populated, this long description for end user must align with the corresponding root element. String. Should be <128 characters.
- modelName: Model name. Where space on the device permits this field shall be included as part of the manufacturing configuration data. String. Should be <32 characters.
- modelNumber: Model number. Where space on the device permits this field shall be included as part of the manufacturing configuration data as used to populate the corresponding root element. String. Should be <32 characters.
- modelURL: Absolute URL to the web site for model. Where space on the device permits this field shall be included as part of the manufacturing configuration data as used to populate the corresponding root element. Single URL <1024 characters.
- serialNumber: Serial number. Where space on the device permits this field shall be included as part of the manufacturing configuration data as used to populate the corresponding root element. String. Should be <64 characters.
- UDN: Unique Device Name. Universally-unique identifier for the device, generated internally in the same way as other UUIDs. Must be the same over time for a specific device instance (i.e., must survive reboots). Must match the value of the NT header in device discovery messages. Must match the prefix of the USN header in all discovery messages. See UPnPArchitecture Section 1 on device discovery which explains the standard NT and USN headers). Must begin with uuid: followed by a UUID suffix. Single URI, maximum length 68 bytes including “uuid:” portion. Note that UUID formatting hyphens are optional and for consistency shall not normally be included.
- UPC: Universal Product Code. Not included for AiosServices.
- IconList: if and only if the device has one or more icons. Such icons only have meaning for Avega CP applications and as such this and the associated elements can be regarded as a place holder for future use. The existing icons available for MediaServer and MediaRenderer Devices should be sufficient to meet existing CP requirements. DLNA 7.2.28.1 requires two jpg 48×48 & 120×120 and two png 48×48 & 120×120 images. Sub element descriptions must follow the UPnP Basic: Device Template.
- serviceList: The Services Device shall exclusively contain non-standard UPriP services (such as Group Control, Zone Control, and others considered above). All standard UPnP Devices and services must only reside within the root <deviceList>. This restriction also applies for any embedded devices within the Services Device. The rationale behind this restriction is to ensure ease of compliance testing for standard UPnP devices. Note that normally there will be at least one non-standard service within the Services Device however an empty service list is permissible. In version 1.0 of the UPnP Device Architecture, the serviceList element was required, and it was required to contain at least one service element. These requirements were subsequently rescinded to accommodate the Gateway and Basic device types. If the device has no services, the serviceList element may be omitted entirely, or it may be present but contain no service elements. Appendix A of the UPnP Basic: Device Template suggests that older CPs may enforce the legacy requirement that a device must contain at least one service.
- deviceList: if and only if root device has embedded devices. Contains the following sub elements:
- device: Repeat once for each embedded device defined by a UPnP Forum working committee. If UPnP vendor differentiates device by embedding additional UPnP devices, repeat once for each embedded device. In all cases will contain the same sub elements as defined above for root sub element device. Note that it is essential that all embedded devices have unique and persistent UUIDs, the UUIDs differentiate the individual devices not the physical product.
- presentation URL: This element provides an absolute URL to presentation for the device. Single URL <1024 characters.
- device: Contains the following sub elements:
Claims (37)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/877,656 USRE47400E1 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2008900059 | 2008-01-07 | ||
AU2008900059A AU2008900059A0 (en) | 2008-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device | |
US14/877,656 USRE47400E1 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
US12/811,297 US8554895B2 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
PCT/AU2009/000018 WO2009086600A1 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
Publications (1)
Publication Number | Publication Date |
---|---|
USRE47400E1 true USRE47400E1 (en) | 2019-05-21 |
Family
ID=40852709
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/877,656 Active 2030-03-28 USRE47400E1 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
US12/811,297 Ceased US8554895B2 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/811,297 Ceased US8554895B2 (en) | 2008-01-07 | 2009-01-07 | Systems and methods for providing dual-control functionality in a networked digital media device |
Country Status (2)
Country | Link |
---|---|
US (2) | USRE47400E1 (en) |
WO (1) | WO2009086600A1 (en) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8423893B2 (en) * | 2008-01-07 | 2013-04-16 | Altec Lansing Australia Pty Limited | User interface for managing the operation of networked media playback devices |
JP2011530842A (en) * | 2008-07-11 | 2011-12-22 | マーベル ワールド トレード リミテッド | Service discovery method |
US20110029653A1 (en) * | 2009-08-03 | 2011-02-03 | General Instrument Corporation | Netmanager and netmodule general upnp extensions for ocap hnext |
WO2013039979A1 (en) * | 2011-09-16 | 2013-03-21 | Cisco Technology, Inc. | Modular headend architecture with downstream multicast |
TW201327370A (en) * | 2011-12-28 | 2013-07-01 | Amtran Technology Co Ltd | System and method for resource sharing and broadcasting device thereof |
US9131266B2 (en) * | 2012-08-10 | 2015-09-08 | Qualcomm Incorporated | Ad-hoc media presentation based upon dynamic discovery of media output devices that are proximate to one or more users |
US20140313103A1 (en) | 2013-04-19 | 2014-10-23 | Qualcomm Incorporated | Coordinating a display function between a plurality of proximate client devices |
US9438193B2 (en) * | 2013-06-05 | 2016-09-06 | Sonos, Inc. | Satellite volume control |
WO2016037155A1 (en) * | 2014-09-04 | 2016-03-10 | PWV Inc | Speaker discovery and assignment |
WO2016112048A1 (en) | 2015-01-05 | 2016-07-14 | PWV Inc | Discovery, control, and streaming of multi-channel audio playback with enhanced times synchronization |
US9794618B2 (en) | 2015-02-12 | 2017-10-17 | Harman International Industries, Incorporated | Media content playback system and method |
US9521496B2 (en) * | 2015-02-12 | 2016-12-13 | Harman International Industries, Inc. | Media content playback system and method |
JP6597248B2 (en) * | 2015-12-04 | 2019-10-30 | ヤマハ株式会社 | System and control method |
US11012780B2 (en) * | 2019-05-14 | 2021-05-18 | Bose Corporation | Speaker system with customized audio experiences |
US11637880B2 (en) * | 2021-05-06 | 2023-04-25 | Spotify Ab | Device discovery for social playback |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974237A (en) * | 1996-12-18 | 1999-10-26 | Northern Telecom Limited | Communications network monitoring |
US20030101294A1 (en) * | 2001-11-20 | 2003-05-29 | Ylian Saint-Hilaire | Method and architecture to support interaction between a host computer and remote devices |
US20050232602A1 (en) * | 2004-03-26 | 2005-10-20 | Kreifeldt Richard A | Audio related system link management |
US20060031459A1 (en) * | 2002-07-10 | 2006-02-09 | Sung-Joon Ahn | Remote control system of a home network |
US20060041655A1 (en) * | 2004-05-06 | 2006-02-23 | Marty Holloway | Bi-directional remote control for remotely controllable apparatus |
US7085814B1 (en) * | 1999-06-11 | 2006-08-01 | Microsoft Corporation | Data driven remote device control model with general programming interface-to-network messaging adapter |
WO2006090340A1 (en) | 2005-02-28 | 2006-08-31 | Koninklijke Philips Electronics, N.V. | System and method for providing 'universal 'follow-me' functionality in a upnp av network |
US20060281477A1 (en) * | 2005-06-08 | 2006-12-14 | Radial Labs, Inc., A Delaware Corporation | Dynamic detection and configuration of networked audio/video components |
US20080242222A1 (en) * | 2006-10-17 | 2008-10-02 | Stuart Bryce | Unification of multimedia devices |
US20090303926A1 (en) * | 2006-06-06 | 2009-12-10 | Frank Theodoor Henk Den Hartog | Proxy-bridge for connecting different types of devices |
US20100214948A1 (en) * | 2005-06-23 | 2010-08-26 | Koninklijke Philips Electronics, N.V. | Apparatus and method of configuring a device in a network |
-
2009
- 2009-01-07 US US14/877,656 patent/USRE47400E1/en active Active
- 2009-01-07 US US12/811,297 patent/US8554895B2/en not_active Ceased
- 2009-01-07 WO PCT/AU2009/000018 patent/WO2009086600A1/en active Application Filing
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974237A (en) * | 1996-12-18 | 1999-10-26 | Northern Telecom Limited | Communications network monitoring |
US7085814B1 (en) * | 1999-06-11 | 2006-08-01 | Microsoft Corporation | Data driven remote device control model with general programming interface-to-network messaging adapter |
US20030101294A1 (en) * | 2001-11-20 | 2003-05-29 | Ylian Saint-Hilaire | Method and architecture to support interaction between a host computer and remote devices |
US20060282514A1 (en) * | 2001-11-20 | 2006-12-14 | Ylian Saint-Hilaire | Method and architecture to support interaction between a host computer and remote devices |
US20060031459A1 (en) * | 2002-07-10 | 2006-02-09 | Sung-Joon Ahn | Remote control system of a home network |
US20050232602A1 (en) * | 2004-03-26 | 2005-10-20 | Kreifeldt Richard A | Audio related system link management |
US20060041655A1 (en) * | 2004-05-06 | 2006-02-23 | Marty Holloway | Bi-directional remote control for remotely controllable apparatus |
WO2006090340A1 (en) | 2005-02-28 | 2006-08-31 | Koninklijke Philips Electronics, N.V. | System and method for providing 'universal 'follow-me' functionality in a upnp av network |
US20060281477A1 (en) * | 2005-06-08 | 2006-12-14 | Radial Labs, Inc., A Delaware Corporation | Dynamic detection and configuration of networked audio/video components |
US20100214948A1 (en) * | 2005-06-23 | 2010-08-26 | Koninklijke Philips Electronics, N.V. | Apparatus and method of configuring a device in a network |
US20090303926A1 (en) * | 2006-06-06 | 2009-12-10 | Frank Theodoor Henk Den Hartog | Proxy-bridge for connecting different types of devices |
US20080242222A1 (en) * | 2006-10-17 | 2008-10-02 | Stuart Bryce | Unification of multimedia devices |
Non-Patent Citations (5)
Title |
---|
International Search Report-2 pgs., Feb. 27, 2009, Avega Systems PTY LTD. |
International Search Report—2 pgs., Feb. 27, 2009, Avega Systems PTY LTD. |
Publication: UPnP Device Architecture 1.1 (UPnP Forum), Oct. 15, 2008, 137 pgs. |
Xbox.com/Personalities-Windows Media Connect; http://web.archive.org/web/200612170245/www.xbox.com/en-US/community/personality/elle/20060203-pcmedial.ht m, OPI Dec. 17, 2006. |
Xbox.com/Personalities—Windows Media Connect; http://web.archive.org/web/200612170245/www.xbox.com/en-US/community/personality/elle/20060203-pcmedial.ht m, OPI Dec. 17, 2006. |
Also Published As
Publication number | Publication date |
---|---|
US20100293264A1 (en) | 2010-11-18 |
WO2009086600A1 (en) | 2009-07-16 |
US8554895B2 (en) | 2013-10-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
USRE47400E1 (en) | Systems and methods for providing dual-control functionality in a networked digital media device | |
US8724600B2 (en) | Systems and methods for providing a media playback in a networked environment | |
US9785399B2 (en) | Systems and methods for providing zone functionality in networked media systems | |
AU2022259837B2 (en) | Systems and methods for networked music playback | |
EP2080272B1 (en) | Unification of multimedia devices | |
KR101809544B1 (en) | Method for controlling home network device using universal web application and apparatus thereof | |
US8423893B2 (en) | User interface for managing the operation of networked media playback devices | |
KR100754431B1 (en) | Method for transferring a content according to the processing capability of dmr in dlna system | |
US10547993B2 (en) | Media content sharing method and apparatus | |
JP2010507295A (en) | Media wireless network setup and connection | |
US10680844B2 (en) | Apparatus and method for providing information for a wireless network connection using Wi-Fi | |
EP3240286B1 (en) | Apparatus and method for configuring high-definition video telephony between computer devices | |
CN105323628B (en) | Cross-screen playing method and system based on DLNA (digital Living network alliance), browser end device and playing device | |
JP5567144B2 (en) | Provision of media content information | |
US8176343B2 (en) | Method for providing information for power management of devices on a network | |
JP4789604B2 (en) | Content switching determination system, switching instruction terminal, and content switching determination method | |
CN103516566B (en) | Method and system for realizing server controlling by home network equipment, and apparatuses | |
JP6513770B2 (en) | Identify useful wired connections | |
KR101329668B1 (en) | Contents sharing system and method using push server | |
Bhalla et al. | Control Layer | |
Mukhtar et al. | Using Universal Plug-n-Play for Device Communication in Ad Hoc Pervasive Environments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SOUND UNITED, LLC, CALIFORNIA Free format text: GRANT OF SECURITY INTEREST;ASSIGNOR:D&M HOLDINGS INC.;REEL/FRAME:042622/0011 Effective date: 20170526 |
|
AS | Assignment |
Owner name: D&M HOLDINGS INC, JAPAN Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:SOUND UNITED, LLC;REEL/FRAME:054858/0361 Effective date: 20201224 |
|
AS | Assignment |
Owner name: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT, NEW YORK Free format text: NOTICE OF SECURITY INTEREST - - PATENTS;ASSIGNOR:D&M HOLDINGS INC.;REEL/FRAME:054874/0184 Effective date: 20201228 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:D&M HOLDINGS INC.;REEL/FRAME:057187/0713 Effective date: 20210730 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: ABL PATENT SECURITY AGREEMENT;ASSIGNOR:D&M HOLDINGS INC.;REEL/FRAME:057187/0736 Effective date: 20210730 |
|
AS | Assignment |
Owner name: D&M HOLDINGS INC., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: B & W LOUDSPEAKERS LTD, UNITED KINGDOM Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: SOUND UNITED, LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: B & W GROUP LTD, UNITED KINGDOM Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: D&M EUROPE B.V., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: BOSTON ACOUSTICS, INC., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: DEFINITIVE TECHNOLOGY, LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: DIRECTED, LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 Owner name: POLK AUDIO, LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS AGENT;REEL/FRAME:059127/0278 Effective date: 20210429 |
|
AS | Assignment |
Owner name: D&M HOLDINGS INC., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL (REEL/FRAME 057187/0713);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:059988/0537 Effective date: 20220404 Owner name: D&M HOLDINGS INC., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL (REEL/FRAME 057187/0736);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:059988/0585 Effective date: 20220404 |