Patent Application
20160087928
Embodiments of the present application relate generally to electrical and electronic hardware, computer software, application programming interfaces (API's), wired and wireless communications, Bluetooth systems, RF systems, wireless media devices, portable personal wireless devices, and consumer electronic (CE) devices.
As wireless media devices that may be used to playback content such as audio (e.g., music) and/or video (e.g., movies, YouTube, etc.) become more prevalent, an owner of such a media device may wish to share its playback capabilities with guests, friends or other persons. In some conventional applications, each wireless media device may require a pairing (e.g., Bluetooth pairing) or access credentials (e.g., a login, a user name/email address, a password) in order for a client device (e.g., a smartphone, a table, a pad, etc.) to gain access to the wireless media device (e.g., WiFi and/or Bluetooth enabled speaker boxes and the like). In some wireless media devices, there may be a limit to the number of client devices that may be paired with the media device (e.g., from 1 to 3 pairings). An owner may not wish to allow guests or others to have access credentials to a network (e.g., a WiFi network) that the media device is linked with and/or may not wish to allow guest to pair with the media device.
In a social environment, an owner may wish to provide guests or others with some utility of the media device (e.g., playback of guest content) without having to hassle with pairing each client device with the media device or having to provide access credentials to each client device user.
Accordingly, there is a need for systems, apparatus and methods that provide content handling.
Various embodiments or examples (“examples”) are disclosed in the following detailed description and the accompanying drawings:
Although the above-described drawings depict various examples of the invention, the invention is not limited by the depicted examples. It is to be understood that, in the drawings, like reference numerals designate like structural elements. Also, it is understood that the drawings are not necessarily to scale.
Various embodiments or examples may be implemented in numerous ways, including but not limited to implementation as a system, a process, a method, an apparatus, a user interface, or a series of executable program instructions included on a non-transitory computer readable medium. Such as a non-transitory computer readable medium or a computer network where the program instructions are sent over optical, electronic, or wireless communication links and stored or otherwise fixed in a non-transitory computer readable medium. In general, operations of disclosed processes may be performed in an arbitrary order, unless otherwise provided in the claims.
A detailed description of one or more examples is provided below along with accompanying figures. The detailed description is provided in connection with such examples, but is not limited to any particular example. The scope is limited only by the claims and numerous alternatives, modifications, and equivalents are encompassed. Numerous specific details are set forth in the following description in order to provide a thorough understanding. These details are provided for the purpose of example and the described techniques may be practiced according to the claims without some or all of these specific details. For clarity, technical material that is known in the technical fields related to the examples has not been described in detail to avoid unnecessarily obscuring the description.
Although the foregoing examples have been described in some detail for purposes of clarity of understanding, the above-described conceptual techniques are not limited to the details provided. There are many alternative ways of implementing the above-described conceptual techniques. The disclosed examples are illustrative and not restrictive.
Reference is now made to
If the host device is not in communication with the media device at the time the APP is executing, then the media device and/or host device may be activated or otherwise made to establish a wireless and/or wired communications link with each other, either directly as in the case of a Bluetooth (BT) pairing, for example, or indirectly, as in the case of using a wireless access point, such as a WiFi wireless router, for example. At a stage 104 content (e.g., from a playlist, file, directory, a data store, a library, etc.) may be selected for playback on the media device. The content may include without limitation, various forms of media or information that may be accessible by an electronic device, such as music, video, movies, text, electronic messages, data, audio, images (moving or still), digital files, compressed files, uncompressed files, encrypted files, just to name a few. In the discussion that follows, music (e.g., songs/music/voice/audio/soundtracks/performances in a digital format—MP3, FLAG, PCM, DSD, WAV, MPEG, ATRAC, AAC, AIFF, WMA, lossless compression formats, lossy compression formats, etc.) may be used as one non-limiting example of what may include content.
The content to be selected (e.g., using the APP) may be presented on an interface (e.g., display, touchscreen, GUI, menu, dashboard, etc.) of the host device and/or the media device. A cursor, finger, stylus, mouse, touchpad, voice command, bodily gesture recognition, eye movement tracking, keyboard, or other type of user interface may be used to select the content for playback on the media device. The content may reside in a data store (e.g., non-volatile memory) that is internal to the host device, external to the host device, internal to the media device, external to the media device, for example. The content may reside in one or more content sources 199, such as Cloud storage, the Cloud, the Internet, network attached storage (NAS), RAID storage, a content subscription service, a music subscription service, a streaming service, a music service, or the like (e.g., iTunes, Spotify, Rdio, Beats Music, YouTube, Amazon, Rhapsody, Xbox Music Pass, Deezer, Sony Music Unlimited, Google Play Music All Access, Pandora, Slacker Radio, SoundCloud, Napster, Grooveshark, etc.).
At a stage 106 playback of the content selected at the stage 104 may be initiated on the media device. Initiation of playback at the stage 106 may include playback upon selection of the content or may include queuing the selected content for later playback in a queue order (e.g., there may be other content in the queue that is ahead of the selected content). For purposes of explanation, assume the selected content may include music from a digital audio file. At the stage 106, initiating playback may include the media device accessing (internally or externally) the digital audio file and streaming or downloading the digital audio file for playback hardware and/or software systems of the media device.
At a stage 108 a communications network (e.g., wired and/or wireless) may be monitored for an electronic message from another device (e.g., a wireless client device, smartphone, cellular phone, tablet, pad, laptop, PC, smart watch, wearable device, etc.). The electronic message may be transmitted by a client device and received by the host device, the APP may act on data in the message (e.g., via an API with another application on the host device) to perform some task for the sender of the electronic message (e.g., a user of the client device). The communications network may include without limitation, a cellular network (e.g., 2G, 3G, 4G, etc.), a satellite network, a WiFi network (e.g., one or more varieties of IEEE 802.x), a Bluetooth network (e.g., BT, BT low energy), a NFC network, a WiMAX network, a low power radio network, a software defined radio network, a HackRF network, a LAN network, just to name a few, for example. Here, one or more radios in the host device and/or media device may monitor the communications network for the electronic message configured to Drop on the APP (e.g., data and/or data packets in a RF signal that may be read, interpreted, and acted on by the APP).
At as stage 110, the electronic message, received by the host device and/or media device (e.g., by a radio), may be parsed (e.g., by a processor executing the APP) to extract a host handle (e.g., an address that correctly identifies the host device upon which the APP is executing) and a Data Payload (e.g., a data payload included in the electronic message, such as a packet that includes a data payload). The electronic message may have a format determined by a protocol or communication standard, for example. The electronic message may include without limitation an email, a text message, a SMS, a Tweet, an instant message (IM), a SMTP message, a page, a one-to-one communication, a one-to-many communication, a social network communication (e.g., Facebook, Twitter, Flickr, Pinterest, Tumblr, Yelp, etc.), a professional/business network communication, an Internet communication, a blog communication (e.g., LinkedIn, HR.com, etc.), a bulletin board communication, a newsgroup communication, a Usenet communication, just to name a few, for example. In that there may be a variety of different types of electronic messages that may be received, the following examples describe a Tweet (e.g., from a Twitter account) as one non-limiting examples of types of electronic message that may be dropped on the APP. The electronic message may be formatted in packets or some other format, where for example, a header field may include the host handle and a data field may include a data payload (e.g., a DROP Payload). As is described below, the data payload that is dropped via the electronic message may include an identifier for content to be played back on the media device (e.g., a song title, an artist or band/group name, an album title, a genera of music or other form of performance, etc.), a command (e.g., volume up or down, bass up or down, or skip current track being played back, etc.), or both.
At a stage 112 a determination may be made as to whether or not the host handle is verified by the APP. For example, the received electronic message (e.g., a Tweet) may have been addressed to Twitter handle “@SpeakerBoxJoe”. If a Twitter account associated with the APP is for account “SpeakerBoxJoe@twitter.com”, then the APP may recognize that the host handle “@SpeakerBoxJoe” matches the account for “SpeakerBoxJoe@twitter.com”. Therefore, if the host handle in the electronic message is a match, then a YES branch may be taken from the stage 112 to a stage 114. On the other hand, if the host handle in the electronic message does not match (e.g., the handle in the electronic message is “@SpeakerBoxJill”), then a NO branch may be taken from the stage 112 to another stage in flow 100, such as back to the stage 108 where continued monitoring of the communications network may be used by the APP to wait to receive valid electronic messages (e.g., a Tweet that includes a correct Twitter handle “@SpeakerBoxJoe”).
At the stage 114 a determination may be made as to whether or not a syntax of the data payload is valid. A correct grammar for datum that may be included in the data payload may be application dependent; however, the following include non-limiting examples of valid syntax the APP may be configured to act on. As a first example, the data payload may include a song title that the sender of the electronic message would like to be played back on or queued for playback on the media device. To that end, the electronic message may include the host handle and the data payload for the title of the song, such as: (a) “@SpeakerBoxJoe play rumors”; (b) “@SpeakerBoxJoe rumors”; or (c) “@SpeakerBoxJoe #rumors”. In example (a), the data payload may include the word “play” and the title of the requested song “rumors”, with the host handle and the words play and rumors all separated by at least one blank space “ ”. In example (b), the data payload may include the title of the requested song “rumors” separated from the host handle by at least one black space “ ”. In example (c), the data payload may include a non-alphanumeric character (e.g., a special character from the ASCII character set) that may immediately proceed the text for the requested song, such as a “#” character (e.g., a hash tag) such that the correct syntax for a requested song is “(hash-tag)(song-title) with no blank spaces between. Therefore the correct syntax to request the song “rumors” is “#rumors” with at least one black space “ ” separating the host handle and the requested song. In the examples (a)-(c), the syntax for one or more of the host handle, the requested content, or the requested command, may or may not be case sensitive. For example, all lower case, all upper case, or mixed upper and lower case may be acceptable. Although non-limiting examples (a)-(c) had a song title as the data payload, other datum may be included in the data payload such as the aforementioned artist name, group name, band name, orchestra name, and commands.
As one example of a non-valid syntax for a data payload, if the hash tag “#” is required immediately prior to the song title, and the electronic message includes “@SpeakerBoxJoe $happy”, the “$” character before the song title “happy” would be an invalid syntax. As another example, “@SpeakerBoxJoe plays happy”, would be another invalid syntax because “play” and not “plays” must precede the song title. A host handle may be rejected as invalid due to improper syntax, such as “SpeakerBoxJoe $happy”, because the “@” symbol is missing in the host handle.
If a NO branch is taken from the stage 114, then flow 100 may transition to another stage, such as back to the stage 108 where continued monitoring of the communications network may be used by the APP to wait to receive valid electronic messages (e.g., electronic messages with valid syntax). If a YES branch is taken from the stage 114, then flow 100 may transition to a stage 116.
At the stage 116 a determination may be made as to whether or not data specified in the data payload is accessible. For example, the data specified in the data payload may include content (e.g., a digital audio file for the song “happy”). That content may reside in one or more data stores that may be internal or external to the host device, the media device or both. The data is accessible if it may be electronically accessed (e.g., using a communications network or link) from the location where it resides (e.g., the Cloud, a music/content streaming service, a subscription service, hard disc drive (HDD), solid state drive (SSD), Flash Memory, NAS, RAID, etc.). Data may not be accessible even though the data store(s) are electronically accessible because the requested content does not reside in the data store(s). For example, at the stage 116, the APP may perform a search of the data store(s) (e.g., using an API) for a song having the title “happy”. The search may return with a NULL result if no match is found for the song “happy”.
If the data in the data payload is not accessible (e.g., due to no match found or inability to access the data store(s)), then a NO branch may be taken from the stage 116 to another stage in flow 100, such as an optional stage 124 where a determination may be as to whether or not to transmit an electronic message (e.g., to the host device and/or the device that transmitted the request) that indicates that the Drop failed. If a YES branch is taken from the stage 124, then a failed Drop message may be transmitted at a stage 126. Stage 126 may transition to another stage of flow 100, such as back to stage 108 to monitor communications for other electronic messages, for example. If a NO branch is taken from the stage 124, then stage 124 may transition to another stage of flow 100, such as to stage 108 to monitor communications for other electronic messages.
If the data in the data payload is accessible, then a YES branch may be taken from the stage 116 to a stage 118 where the data in the data payload is accessed and may be executed on the media device. Execution on the media device may include playback of content such as audio, video, audio and video, or image files that include the data that was accessed. In some example, the data may include a command (e.g., #pause to pause playback, #bass-up to boost bass output, #bass-down to reduce bass output, etc.) and data for the command may be accessed from a data store in the host device, the media device or both (e.g., ROM, RAM, Flash Memory, HDD, SSD, or other).
In some examples, the data may be external to the host device, the media device, or both and may be accessed 198 from a content source 199 (e.g., the Cloud, Cloud storage, the Internet, a web site, a music service or subscription, a streaming service, a library, a store, etc.). Access 198 may include wired and/or wireless data communications as described above.
The stage 118 may transition to another stage in flow 100, such as optional stage 120 where a determination may be made as to whether or not to send a Drop confirmation message. If a NO branch is taken, then flow 100 may transition to another stage such as the stage 108 where communications may be monitored for other electronic messages. Conversely, if a YES branch is taken from the stage 120, then flow 100 may transition to a stage 122 where a successful drop message may be transmitted (e.g., to the host device and/or the device that transmitted the request). Stage 122 may transition to another stage in flow 100 such as the stage 108 where communications may be monitored for other electronic messages. A successful drop message may include an electronic message, for example “@SpeakerBoxJoe” just Dropped rumors”.
Successful electronic messages (e.g., at stage 122) may be transmitted to the host device, a client device that sent the initial electronic message or both. As one example, an electronic message transmitted in the form of a “Tweet” may be replied to as an electronic message in the form of another “Tweet” to the address (e.g., handle) of the sender. For example, if “@PartyGirlJane” tweeted electronic message “@SpeakerBoxJoe #seven nation army”, and that song was successfully dropped, then at the stage 122 an electronic message to the sender “@PartyGirlJane” may include “@SpeakerBoxJoe just Dropped seven nation army”. In some examples, failure of an electronic message may be communicated to a client device, a host device or both (e.g., at the stage 126). As one example, if at the stage 116 is it determined that the data for “seven nation army” is not accessible (e.g., the song is not available as a title/file in the content source(s) 198), then at the stage 126 an electronic message to the sender “@PartyGirlJane” may include “@SpeakerBoxJoe failed to Drop seven nation army”.
Different communications networks may be used at different stages of flow 100. For example, communications between the host device and the media device may be via a first communications network (e.g., BT), communication of the electronic message at the stage 108, the drop confirmation message at the stage 122, and or drop failed message as the stage 126 may be via a second communications network (e.g., a cellular network), and accessing the data at the stage 118 may be via third communications network (e.g., WiFi).
Turning now to
According to some examples, computer system 200 performs specific operations by processor 204 executing one or more sequences of one or more instructions stored in system memory 206. Such instructions may be read into system memory 206 from another non-transitory computer readable medium, such as storage device 208 or disk drive 210 (e.g., a HD or SSD). In some examples, circuitry may be used in place of or in combination with software instructions for implementation. The term “non-transitory computer readable medium” refers to any tangible medium that participates in providing instructions and/or data to processor 204 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, Flash Memory, optical, magnetic, or solid state disks, such as disk drive 210. Volatile media includes dynamic memory (e.g., DRAM), such as system memory 206. Common forms of non-transitory computer readable media includes, for example, floppy disk, flexible disk, hard disk, Flash Memory, SSD, magnetic tape, any other magnetic medium, CD-ROM, DVD-ROM, Blu-Ray ROM, USB thumb drive, SD Card, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer may read.
Instructions may further be transmitted or received using a transmission medium. The term “transmission medium” may include any tangible or intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Transmission media includes coaxial cables, copper wire, and fiber optics, wires that include bus 202 for transmitting a computer data signal. In some examples, execution of the sequences of instructions may be performed by a single computer system 200. According to some examples, two or more computer systems 200 coupled by communication link 220 (e.g., LAN, Ethernet, PSTN, wireless network, WiFi, WiMAX, Bluetooth (BT), NFC, Ad Hoc WiFi, HackRF, USB-powered software-defined radio (SDR), or other) may perform the sequence of instructions in coordination with one another. Computer system 200 may transmit and receive messages, data, and instructions, including programs, (e.g., application code), through communication link 220 and communication interface 212. Received program code may be executed by processor 204 as it is received, and/or stored in a drive unit 210 (e.g., a SSD or HD) or other non-volatile storage for later execution. Computer system 200 may optionally include one or more wireless systems 213 (e.g., one or more radios) in communication with the communication interface 212 and coupled (215, 223) with one or more antennas (217, 225) for receiving and/or transmitting RF signals (221, 227), such as from a WiFi network, BT radio, or other wireless network and/or wireless devices, for example. Examples of wireless devices include but are not limited to: a data capable strap band, wristband, wristwatch, digital watch, or wireless activity monitoring and reporting device; a smartphone; cellular phone; a tablet; a tablet computer; a pad device (e.g., an iPad); a touch screen device; a touch screen computer; a laptop computer; a personal computer; a server; a personal digital assistant (PDA); a portable gaming device; a mobile electronic device; and a wireless media device, just to name a few. Computer system 200 in part or whole may be used to implement one or more systems, devices, or methods that communicate with one or more external devices (e.g., external devices that transmit and/or receive electronic messages, such as Tweets). Wireless systems 213 may be coupled 231 with an external system, such as an external antenna or a router, for example. Computer system 200 in part or whole may be used to implement a remote server, a networked computer, a client device, a host device, a media device, or other compute engine in communication with other systems or devices as described herein. Computer system 200 in part or whole may be included in a portable device such as a smartphone, laptop, client device, host device, tablet, or pad.
Moving on to
Host device 310 may execute an application APP 312 operative to monitor a communications network (e.g., via one or more radios in a RF system of 310) for an electronic message 371 that may be transmitted 321 by one or more client devices 340 to an electronic messaging service 396 which may process the message 371 and may subsequently transmit or otherwise broadcast the message to the host device as denoted by 370. Broadcast of electronic message 370 may be received by the host device (e.g., via APP 394) and may also be received by other devices that may have access to messages to the handle in message 370 (e.g., followers of “@SpeakerBoxJoe). The electronic message (e.g., a Tweet) may include an address that matches an address 390 (e.g., handle “@SpeakerBoxJoe) associated with host device 310 (e.g., an account, such as a Twitter account, registered to a user of host device 310). As described above in reference to
Host device 310 and one or more client devices 340 (e.g., wireless devices of guests of a user of the host device 310) may both include an application APP 394 that may be used to compose electronic messages and to receive electronic messages that are properly addressed to the correct address for a recipient of the electronic message. Although several of the client devices 340 are depicted, there may be more or fewer client devices 340 as denoted by 342. An API or other algorithm in host device 310 may interface APP's 312 and 394 with each other such that the transmitted electronic message 370 is received by host device 310, passed or otherwise communicated to APP 394 which may communicate the electronic message 370 to APP 312 via the API. APP 312 may parse the electronic message 370 to determine if syntax of its various components (e.g., headers, packets, handle, data payload) are correct. Assuming for purposes of explanation the electronic message 370 is properly addressed and has valid syntax, the data payload may be acted on by APP 312 to perform an action indicated by the data payload. As one example, if the data payload includes “#happy”, APP 312 may pass (e.g., wirelessly communicate 321) the payload to content source(s) 199, Cloud 398, Internet 399 or some other entity where the data payload may be used as a search string to find content that matches “happy” (e.g., as a song title, an album title, movie title, etc.). As one example, communication 321 of a data equivalent of the text for “happy” to content source 199 (e.g., a music streaming service or music library) may cause the content source 199 to execute a search for content that matches “happy” in one or more data stores. A match or matches if found may be communicated 321 back to host device 310, media device 350 or both. In some examples, the data payload parsed by APP 312 may result in the data payload being communicated (321, 323) to the media device 350 and the media device 350 may pass the data equivalent of the text for “happy” to content source 199, where matches if found may be communicated 321 back to host device 310, media device 350 or both. In some examples, when a match is found for the search term (e.g., “happy”), media device 350 begins playback of the content (e.g., a digital audio file for “happy”) or queues the content for later playback using its various systems (e.g., DSP's, DAC's, amplifiers, etc.). In some examples, playback occurs by the media device 350 or the host device 310 streaming the content from content source(s) 199 or other sources (e.g., 398, 399), content that is queued for playback may be streamed when that content reaches the top of the queue. Each of the client devices 340 may compose (e.g., via APP 394) and communicate 321 an electronic message 371 addressed to handle “@SpeakerBoxJoe” with a content request “#content-title” and each request that is processed by APP 312 may be placed in a queue according to a queuing scheme (e.g., FIFO, LIFO, etc.).
In some examples, a search order for content to be acted on by media device 350 may include APP 312 searching for the content first in a data store of the host device 310 (e.g., in its internal data store such as Flash Memory or its removable data store such as a SD card or micro SD card), followed second in a data store of media device(s) 350 (e.g., in its internal data store such as Flash Memory or its removable data store such as a SD card or micro SD card), followed third by an external data store accessible by the host device 310, the media device 350 or both (e.g., NAS, a thumb drive, a SSD, a HDD, Cloud 398, Internet 399, etc.), and finally in content source(s) 199. In some examples, content that resides in an external source may be downloaded into a data store of the media device 350 or the host device 310 and subsequently played back on the media device 350. In other examples, the content may be streamed from the source it is located at.
Prior to receiving a first electronic message 317 requesting content to be played back, a user of host device 310 may activate the APP 312, may select an item of content for playback on media device 350, and may initiate playback of the selected content (e.g., MUSIC 311). Subsequent requests for playback of content via electronic messaging 370 may be acted on by host device 310 (e.g., via APP 312) by beginning playback of the content identified by the data payload or queuing it for later playback.
In
After initiation of playback on media device 350, song 411 may be a first song in a queue 450 as denoted by a now playing (NP) designation. Queue 450 may be displayed on a display system of host device 310, media device 350 or both. In some examples, queue 450 may be displayed on a display system of one or more client devices 340. In some examples, queue 450 may be displayed on a display system of one or more client devices 340 that have sent electronic messages 370 to host device 310.
Subsequently, a user of a client device 340 may compose an electronic message 371 that is received by electronic messaging service 396 and communicated to host device 310 as electronic message 370. A communication 421 for the song “happy” in the data payload of message 370 is transmitted 321 to content source 199 and accessed 427 for playback on media device 350. If song 411 is still being played back on media device 350, then the song “happy” may be placed in the queue 450 as the second song (e.g., the next song cued-up for playback) for media device 350 to playback after song 411 has ended or otherwise has its playback terminated. The song “rumors” may be placed third in queue 450 if it was the next request via electronic messaging after the request for “happy”, for example. The song “happy” may be the first song in the queue 450 (e.g., now playing) if the queue 450 was empty at the time “happy” was accessed 427 for playback on media device 350.
As additional user's compose messages addressed to “@SpeakerBoxJoe” on their respective client devices 340, song titles in their data payloads may be accessed from content source 199 and queued for playback on media device 350. As one or more songs are placed in queue 450, the queue may become a collaborative playlist used by the media device 350 to playback music or other content from friends, guests, associates, etc. of user 410, for example. The one or more songs or other content may be collaboratively queued starting from a first song (e.g., now playing NP:), a second song (e.g., “happy”), all the way to a last song in queue 450 denoted as last entry “LE:”.
In some examples, queue 450 may exhaust requests such that after the last entry “LE:” has been played back there are no more entries queued up. In order to prevent a lull in the playback of content (e.g., music at a party or social gathering), the last item of content in queue 450 may be operative as a seed for a playlist to be generated based on information that may be garnered from the user of host device 310, the media device 350, the host device 310 itself, one or more of the users of client devices 340, one or more of the client devices 340, or from data included in or associated with the content itself (e.g., metadata or the like).
In
Reference is now made to
Turning now to
Although the foregoing examples have been described in some detail for purposes of clarity of understanding, the above-described inventive techniques are not limited to the details provided. There are many alternative ways of implementing the above-described techniques or the present application. The disclosed examples are illustrative and not restrictive.
This application claims the benefit of U.S. Provisional Patent Application No. 62/019,327, filed on Jun. 30, 2014, which is herein incorporated by reference for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 62019327 | Jun 2014 | US |
