The invention pertains to digital media and more particularly, by way of example, to systems and methods for multimedia content sharing. The invention has application, by way of non-limiting example, in the sharing of images and other multimedia content between and among family, friends and other communities.
Digital cameras, both still and video, abound. One can hardly step into the streets of any modern city without witnessing multiple cameras in use. This has proven increasingly true since the advent of ultra-portable digital and video cameras, not to mention camera-equipped cell phones. The trend is likely to continue as manufacturers incorporate even better cameras into the ubiquitous cell phone.
The advances that have led to the upswing in picture-taking have not found parallel in picture sharing. Most users resort to printing their favorite pictures and hand-delivering, or mailing, them to friends and family. Those on the information superhighway may use e-mail to send photos but, as many will attest, e-mail client incompatibilies, image reader problems, firewall limitations, and lacking computer skills often frustrate recipients attempts to enjoy the fruits of these missives. While online photo sharing services, such as MySpace®, FaceBook®, help overcome some of these problems, they introduce new ones—not the least of which is necessitating would-be recipients to log on to their computers to see the latest uploads. So goes the art of passive viewing.
Video sharing technologies are even more wanting. The lack of e-mail support for all but the smallest of video files requires users to “burn” them into CDs or DVDs and hand-deliver or mail them to proposective recipients. Still, incompatibilies in storage formats and disk-reader capabilities often frustrate these efforts, as well. Those with sufficient skills may turn to online video sharing services, such as YouTube®, BlipTV®, to avoid these problems only to find, like users of their still photo sharing service counterparts, that they have introduced new ones.
In view of the foregoing, an object of the invention is to provide improved methods and apparatus for image sharing.
Related objects are to provide such methods and apparatus as can be used with still images, moving images (video), audio files, and other forms of multimedia content.
Further objects of the invention are to provide such methods and apparatus as reduce the potential that hardware, software and/or format incompatibilies will frustrate content sharing.
Yet other objects of the invention are to provide such methods and apparatus as can be easily used by young and old, those that are computer-savvy and not, alike.
Still yet further objects of the invention are to provide such methods and apparatus as bring together families, friends and other communities.
Yet still yet other objects of the invention are to provide such methods and apparatus as permit the sharing not only of multimedia content but, also, user feedback surrounding that content.
The foregoing are among the objects attained by the invention which provides, in some aspects, a multimedia content sharing system including a shared content server that stores items of content (e.g., still images, moving images and audio files) and a plurality of nodes, each in communications with the shared content server via cellular telephone and/or other data networks. Those other nodes can be, for example, mobile phones, personal digital assistants, network-enabled digital picture frames, personal computers, third-party servers, headless computing and/or communications devices (such as USB modems) and so forth.
The shared content server can transmit items of content to a first set of nodes “automatically,” e.g., without requests by users of those nodes for the items. At least one node in that first set (“first peer node”) displays the content of received items (e.g., on an LCD screen) and accepts user feedback in regard to them. That feedback is transmitted back to the shared content server for distribution to one or more other nodes (e.g., one or more “second peer nodes”), e.g., in the first set, which alter their own respective displays of the items accordingly.
Related aspects of the invention provide a system as described above in which the shared content server transmits the aforementioned feedback to one of the second peer nodes without the item of content with respect to which the feedback was accepted from the first peer node.
In still further related aspects, the invention provides a system as described above in which the feedback accepted by the first peer node with respect to an item of content includes commands for one or more of (i) copying the item to an album (or other collection), (ii) rotating the item on the display, (iii) requesting that another node (e.g., one or more of the second peer nodes) be blocked from presenting that item of content, (iv) requesting that a user or node responsible transmitting the item of content to the first peer node (via the shared content server) be blocked from transmitting further items of content to that and/or other nodes.
Other related aspects of the invention provide systems as described above in which the first peer node and/or other nodes in the first set store items of content received from the shared content server in respective local stores.
In other aspects, the invention provides systems as described above in which the first peer node alters its own presentation of items of content with respect to which the feedback was accepted, in addition to transmitting that feedback to the shared content server for distribution to other nodes. According to related aspects of the invention, the first peer node responds to selected interaction by a user of that node by (i) adding, deleting or otherwise changing information pertaining to an item presented by that node, and/or (ii) messaging and/or forwarding items of content to other nodes.
Further aspects of the invention provide systems as described above in which the shared content server transmits items of content to a second set of the nodes in the same manner as those transmitted to the first set of nodes, i.e., without requests by users of those nodes for the items. As with the first set, at least one node in the second set displays the content of received items, accepts user feedback in regard to those items, and transmits that feedback to the shared content server for distribution to other nodes in the second set of nodes.
According to further aspects of the invention, third-party server nodes in a system of the type above can include photo-sharing web sites, digital media companies, and/or other content repositories. Such node can, according to these aspects of the invention, provide items of content to the shared content server, for example, at the initiative of that third-party server, at the request of the shared-content server, and/or at a request of the user a node. Such third party server nodes can, instead or in addition, receive content from the shared content server, e.g., as in the case of a node used for a third-party photo printing service.
According to further related aspects of the invention, nodes that are headless computing and/or communications devices (such as USB modems) can be removeably coupled to host devices in order to display content received from the server(s). Such host devices can be digital picture frames, televisions, game consoles (with associated televisions) or other devices with displays.
Further aspects of the invention provide systems as described above in which the shared content server comprises one or more servers that are coupled for communication via one or more networks. Each of those servers can have a central store with records and/or other structures that store items of content and related information, e.g., thumbnails, versions, and supplementary information such as time of acquisition of an item of content and/or its transmittal to the one or more servers.
Still other aspects of the invention provide systems as described above in which the one or more of items of content on the shared content server are provided by the first peer node. That node can acquire the item, for example, using a camera that is coupled to the node, and can transmit it to the shared content server for transmittal to the other nodes. In related aspects of the invention, the first peer node can acquire the item of content from a web site, networked computer, hard drive, memory stick, DVD, CD or other device or system, prior to transmitting it to the shared content server for transmittal to the other nodes.
Other related aspects of the invention provide systems as described above in which the shared content server combines items of content, e.g., received from the first peer node, with supplementary information provided with that item of content and/or in connection with its transmission from that node. That supplementary information can include, for example, information contained in a header (e.g., of an e-mail) provided with the item of content and/or contained in metadata provided with the item of content, all by way of example. The shared content server can transmit the supplementary information to other nodes, along with the item of content to which it relates.
In related aspects of the invention, the shared content server processes items of content received, e.g., from the first peer node (or other nodes) and/or supplementary information for those items of content. This includes generating, for example, “thumbnails” of the items of content and versions of those items optimized for presentation on one or more the nodes. That optimization can include, for example, cropping images, performing red-eye reduction and/or adjusting any of resolution, color, and contrast.
Further related aspects of the invention provide systems as described above in which processing by the shared content server includes tagging an item of content received from a node to facilitate categorization of that item into one or more sets (e.g., “albums”), e.g., defined by users of the nodes. This can include tagging an item of content based on any of a user-supplied designation (e.g., album name), supplementary information provided with or for that item, and the content of the item itself.
Yet still other aspects of the invention provide systems as described above in which the shared content server transmits items of content to the first peer node and/or other nodes based on any of polling, scheduled transmission times, and/or sensed activity by a user of the respective node.
In other aspects, the invention provides systems as described above in which the shared content server transmits items of content to nodes based on the groups (e.g., albums) into which those items are formed and permissions by the nodes (or users of those nodes) in those groups. In related aspects, the shared content server forms those groups based on feedback received from the nodes in response to presentation of the items of transmitted content. Alternatively, or in addition, grouping can be based on user-defined rules, e.g., that are a function of tags or other information associated with the respective items of content.
In other aspects, the invention provides devices for multimedia content sharing having one or more features of the components of the systems described above. Thus for example, in one aspect, the invention provides a device for multimedia content sharing including a processor, a display that is coupled to the processor, where the processor (i) drives the display to present content of at least one item of content received from a shared content server, (ii) effects acceptance by the device of feedback with respect to that item of content from a user of the device, (iii) transmits that feedback to the shared content server for transmission to at least one other device to which that item of content was transmitted by the shared content server for altering that other device's presentation of that item of content.
In a related aspect, the invention provides a device as described above comprising a sensor that senses characteristics of any of (i) the device, (ii) an environment local to the device, and/or (ii) a user of the device. The sensor can be, by way of non-limiting example, a motion sensor, radio frequency identification (RFID) reader, bluetooth transceiver, photo-detector, network presence/characteristic sensor, microphone, touch sensor, proximity sensor, and/or camera.
According to further related aspects of the invention, the processor of a device as described above can respond to a sensed characteristic by (i) altering a state of the device, (ii) altering the presentation of an item of content by the device, (iii) generating and/or altering a user notification on the device, (iv) tagging an item of content, (v) generating a notification to the shared content server or to another device, (vi) sending an item of content to shared content server and/or another device, (vii) altering a prioritization of tasks by the device and/or the shared content server, and/or (viii) scheduling transmission of items of content.
In still other aspects, the invention provides methods of multimedia content sharing paralleling the operation of the systems and/or their components described above.
Other aspects of the invention provide a device, such as a computer-driven touch sensitive display, that facilitates operator selection of a function from among a plurality of functions. The device comprises a processor that is coupled to a display and that presents, utilizing a first format, (i) a limited subset of function-selection icons selected from a set of such icons, each of which is associated with one or more of the aforesaid functions and/or a differing display of options, (ii) one or more menu-index icons. The processor responds to user selection of one of the menu-index icons by repeating the display, albeit with a varied—but, again, limited subset of the function selection icons. Conversely, the processor responds to user selection of at least some function-selection icons for effecting a function associated therewith.
Related aspects of the invention provide a device as described above in which the processor responds to user selection of selected function-selection icons by driving the display to present function selection options in a format that differs from the first graphical format, described above.
Further related aspects of the invention provide a device as described above in which the set of function-selection icons is large compared with the available space on the display for presenting such icons; whereas the number of icons in each subset is small in comparison to that space. Thus, for example, the set of function-selection icons can be ten or larger and, more preferably, fifteen or larger and, still more preferably, twenty or larger, while the subsets of function-selection icons is five or smaller and, more preferably, three or smaller and, still more preferably, two or smaller.
Still other related aspects of the invention provide a device as described above in which the processor's response to user selection of menu-index icons effects a carousel-like indexing through the set of function selection icons—albeit in groupings of the subsets described above.
Still other aspects of the invention provide a device as described above in which the processor drives the display to present one or more specified screens.
In other aspects, the invention provides a user interface and methods of function selection paralleling the operation of the devices described above.
Still further aspects of the invention are evident in the drawings and in the discussion and claims that follow.
A more complete understanding of the invention may be attained by reference to the drawings, in which:
Architecture
Nodes 12-22 comprise one or more electronic devices or systems that (i) communicate with one another and/or with the servers 24a-24c and (ii) present, acquire and/or provide content. These include, by way of non-limiting example, mobile phones, personal digital assistants, network-enabled digital picture frames, personal computers, third-party servers or server systems, all of the type commercially available in the marketplace as adapted in accord with the teachings hereof. One or more of the nodes can also be content presentation devices (“CPDs”) of the type described more fully elsewhere herein. One or more of the nodes can also be headless computing devices (such as plug computers, by way of non-limiting example) and/or headless communication devices (such as USB modems, by way of non-limiting example), or other “headless” devices that do not have a dedicated display and that may not have a dedicated keyboard or other input device. It will be appreciated that while individual examples of such devices are shown in the illustrated embodiment, other embodiments may incorporate less or more of such devices.
Illustrated content sharing servers 24a-24c aggregate, processes and/or serve multimedia content from and/or to one or more of the nodes 12-22. The servers 24a-24c comprise personal computers, workstations, or other digital data processing devices of the type commercially available in the marketplace as adapted in accord with the teachings hereof. The servers 24a-24c, which may be coupled for communications with one another over the network 26, may be collocated, distributed or otherwise.
Network 26 provides communications coupling between the servers 24a-24c and/or nodes 12-22. The network 26 can include one or more cellular networks, one or more Internets, metropolitan area networks (MANs), wide area networks (WANs), local area networks, personal area networks (PANs) and other networks, wired, wireless, terrestrially-based, satellite-based, or otherwise, known in the art suitable for transport of digital content, data and commands in accord with the teachings hereof.
A further appreciation of the invention may be attained by reference to the embodiment shown in
The third-party server 16′ comprises a photo-sharing web site, a digital media company, and/or other repository of content. It may provide images and other multimedia content to the server 24a′ automatically (on action of the server 16′), at the request of the server 24a′, and/or at the request or behest of a user of server 16′ and/or one or more of the nodes 12′, 18′, 20′, 22′. In some embodiments, server 16′ may receive images and other multimedia content from the shared content server, e.g., as in the case of a printing service invoked at the behest of users of nodes 12′, 18′, 20′, 22′ to generate hardcopy of images.
The network 26′ comprises one or more cellular and/or other networks 32-36 providing communications coupling between server 24a′ and, respectively, mobile phone 12′ and CPD 20′, as shown. The network 26′ also comprises Internet backbone (not shown) providing communications coupling between server 24a′ and the cellular networks 32, 34. The network 26′ (and its constituent components) are operated and utilized in the conventional manner known in the art, as adapted in accord with the teachings hereof.
With continued reference to
Operation
Content Acquisition and Upload
With continued reference to
In the illustrated embodiment, interfaces are provided that facilitate the transmission of images (and other content) from the nodes 12′-22′ to the server 24a′. Those interfaces include “widgets,” “wizards,” applications and other special-purpose programs that can be executed by users of the nodes 12′-22′ to perform such transmission, e.g., on on-demand, scheduled or other bases. Such programs can be of the type conventionally used in the art to transfer images from client devices to server devices as adapted in accord with the teachings hereof. The interfaces also include general-purpose file transfer programs, such as (by way of non-limiting example) those suitable for ftp-, http-, e-mail-, or MMS-based transfers to server 24a′. Graphical user interfaces for use with the foregoing are described in further detail below. In the case of headless devices 21A′, such interfaces can be provided, e.g., by one or more host devices 21B′ to which the headless device 21A′ is associated. Thus, for example, a DPF 21B′ can serve as an interface for headless device 21A′. Devices 12′, 18′ and/or other devices capable of communicative coupling with the headless device 21A′ may serve that function, as well, instead or in addition to device 21A′.
Content Processing
The server 24a′ aggregates the received images with supplementary information provided, e.g., by the mobile phone 12′ and/or in the transmission process. This can include, by way of non-limiting example, “header” information contained in the e-mail or MMS transfer, such as, sender identification, time and date of transmission, subject line, message body, and so forth. This can also include metadata provided with the image itself, e.g., device identification, time and date of capture, aperture settings, and so forth.
The server 24a′ also processes the image and supplementary information, e.g., for transmission to the nodes 12′, 18′, 20′, 21A′, 22′. This can include generating thumbnails and/or optimized versions of the image for display or other presentation on the nodes. Those optimized versions can incorporate resolution reduction/enhancement, color reduction/enhancement, contrast reduction/enhancement, cropping, red-eye reduction, and other adjustments known in the art of image display.
Processing can further include tagging the images, for example, in accord with the supplementary information and/or in accord with designations made by a node user. In some embodiments, tagging can also be based on image content (as determined, for example, by facial or other recognition algorithms). In the embodiment illustrated in
Referring to
Referring back to
Content Distribution and Presentation
The server 24a′ transmits image information to the nodes. Preferably, this is done “automatically,” i.e., without need for request by the users of those nodes for those images. For example, in a preferred embodiment, once CPDs 20′, 22′ and headless devices 21A′ have been activated (e.g., powered-on and coupled to a cellular network), the server can download selected images to those devices 20′, 21A′, 22′ e.g., via networks 34, 36, without further action by the respective users of those devices. The “selected” images can be, for example, those contained in albums to which respective users of the devices 20′, 21A′, 22′ have permissions, as discussed below. Transmission of the images by server 24a′ to the devices 20′, 21A′, 22′ can be on polling, at scheduled transmission times (e.g., midnight every week day), when sensors in the respective devices 20′, 21A′, 22′ sense user activity (or lack thereof), and so forth. In some embodiments, transmission to devices 20′, 21A′, 22′ can also be on user request—e.g., where CPDs and/or headless devices are so configured and enabled. The server 24a′ can similarly transmit optimized images and, optionally, other information to the mobile phone 12′, computer 18′, e.g., upon user log-in or other request to the server 24a′ via a web browser, dedicated client or otherwise, on polling or other requests and/or at scheduled transmission times. The server 24a′ selects optimized images for transmission to each target node based on the characteristics of that node.
The nodes 12′, 18′, 20′, 21A′, 22′ present images individually and/or in groups, e.g., based on characteristics such as tags, sender, subject, time/date of image acquisition. The drawing depicts presentation of “albums” of images 66, 68, 70, here, shown by way of non-limiting example as image grids, on devices 12′, 18′, 20′, 22′, respectively (or, in the case of headless devices 21A′ via their respective host devices 21B′).
In addition to presenting the image information, one or more of the nodes can acquire and/or otherwise provide images. Thus, as shown in the drawing and discussed above, mobile phone 12′ can acquire an image that it, then, transmits to the server 24a′. This is likewise true of portable computer 18′, e.g., via a built-in or attached camera, as well as of headless device 21A′, e.g., via a camera to which it is attached, electromechanically, via cable or wire, wirelessly, or otherwise. These and other nodes can, instead or in addition, transmit to the server images acquired by other means (e.g., images downloaded from other devices/systems, generated images, and so forth). While, in some embodiments, CPDs 20′, 22′ and headless devices 21A; are equipped only for content presentation, in other embodiments, they may also acquire (e.g., via a built-in or attached camera) or otherwise provide images (e.g., downloaded or otherwise obtained from other devices/systems).
Albums & Communities of Users
As evident in the discussion above, images and other multimedia content can be transmitted to the nodes 12′-22′ based on groupings referred to, by way of non-limiting example, as “albums.” Membership of an image in an album may result in any of one or more ways, for example, (i) based on ad hoc assignment of individual or groups of images (or other content) by users to a pre-existing or new album, and/or (ii) based on rules that are defined by users, by default, or otherwise, that effect assignment of images (or other content) as a function of tags and/or other image information. In regard to the former, by way of non-limiting example, users of the nodes may utilize the user interface, e.g., of CPD 20′ (and, likewise, those of the other nodes) to copy images or other items of content to albums and, thereby, to effect system-wide assignment of those images (or other content) to those albums. In regard to the latter, by way of non-limiting example, the server 24a′ can assign newly acquired images to a default album, such as “ALL” or “NEW IMAGES”, etc.
However, in the illustrated embodiment, not all images that are members of an album are necessarily presented on all nodes 12′-22′. Instead image presentation is a function of permissions and preferences. Particularly, server 24a′ transmits to (or otherwise permits display on) the nodes 12′-22′ only those images to which the node has permission (e.g., by way of hardware and/or user authentication). Such permissions may be granted, for example, by default, as a consequence of payment of a service fee, activation of a user account, action of a node user, e.g., via a user interface of the type described below, action of an administrator, e.g., using a web site or other interface to the server 24a, and so forth. The obverse of such actions may, conversely, effect recision of such permissions.
In addition, in some embodiments, the server 24a′ will not transmit to (or permit display on) a node, images from which that node has been blocked or excluded (e.g., by act of the image creator/sender or otherwise)—even though those images may form part of an album to which the node has permission. Thus, for example, the user of a node that acquires or otherwise provides images (or other content) for a given album may block or exclude the user of another node from viewing those images—yet, not exclude users of other nodes from the same album. This may be effected, for example, by action of a node user, e.g., via a user interface of the type described below, action of an administrator, e.g., using a web site or other interface to the server 24a, and so forth.
Images received by the nodes 12′-22′ from server 24a′ may be presented to the respective users of those nodes, for example, depending display preferences set for those devices 12′-22′, e.g., by default, user action or otherwise. Thus, for example, one node may be configured to present all images transmitted to it by the server 24a′, while another node may be configured to present only newly received images, while yet another node may be configured to present only images that are members of selected albums, and, yet, while still another may be configured to block images from selected senders, nodes and/or selected albums. Still further, some of these nodes may be configured to present received images in groups or batches (e.g., album “grids” of the types shown, by way of non-limiting example in
In the illustrated embodiment, membership of an image in an album is reflected by tags 64 (see
The foregoing provides a mechanism for sharing of images between and among users of nodes 12′-22′ and, thereby, to form “communities.” This is illustrated, by way of example, in
Referring to the drawing, image 70 of the Eiffel Tower forms at least part of a first album to which all nodes have permission. Indeed, as shown in the drawing, the various nodes' preferences are set such that image (or one of its versions 44, 46) is displayed on each node. Image 72, of the Seattle Space Needle, and image 74, of the Statue of Liberty, form at least part of a second album to which only nodes 18′, 20′ have permission, as reflected by dashed lines in the drawing. Although the drawing shows both images on display in both nodes 18′, 20′, the preferences on one or both may be set so as to delay and/or prevent such display for either or both images. Image 76, of a tree at sunset, and image 78 of the Lincoln Memorial, form at least part of a third album to which nodes 20′ and 22′ have permission. Again, although the drawing shows both images on display in both nodes 20′, 22′, the preferences on one or both may be set so as to delay and/or prevent such display for either or both images.
User Interaction with Nodes
In addition to presenting content, nodes 12′, 18′, 20′, 22′ (and, in some embodiments, node 16′) accept user input for (i) manipulating or otherwise altering images and image information presentation, (ii) adding, deleting or otherwise changing image information, including image tags, (iii) replying to and/or otherwise messaging other users (e.g., an image sender) or other nodes (e.g., a third-party server), via the server 24a′, (iv) forwarding, via the server 24a,′ images and image information to other nodes, e.g., devices 12′, 18′, 20′, 22′ (for viewing by their respective users) or servers 16′ (including, for example, a server used by a printing service), all by way of non-limiting example. Nodes that are headless devices 21A′ can accept such user input for like purposes (e.g., manipulating/altering images or other content, replying to other users, forwarding content to other nodes, etc.) via associated host devices 21B′. A further appreciation of this may be attained, by way of non-limiting example, by reference to the discussion of the graphical user interface, below and elsewhere herein.
The user input can be reflected in presentation of images and information at the node in which the input was made. By way of scheduled, user-initiated or other synchronization operations, changes effected by the user input (or other feedback with respect to displayed images, or other content) may also be reflected in presentation of those same images (or other content) on the other nodes. For example, rotation of an image resulting from input by a user of node 22′ may be synchronized to the server 24a′ and, thereby, may be reflected in presentation of that image in corresponding albums 66, 68 on devices 18′, 20′, respectively. This is true, likewise, of assignment of an image to an album (e.g., via a “copy to album” operation utilizing the user interface), rotating or otherwise an image (e.g., via a “rotate” operation utilizing the user interface), tagging an image as a favorite (e.g., via a “tag as favorite” operation utilizing the user interface), changes to image information, including tags, made by the user of node 22′ vis-a-vis images depicted on the other nodes 18′, 20′, 21A′ (via host 21B′).
On the other hand, replies and/or other message sent by the user of node 22′ to mobile phone 12′ and identified as private (either by that user, by default, or otherwise) are presented on device 12′ (and not necessarily on the other nodes). Still other user input may be reflected solely on the device on which it is made.
The server 24a′ can aggregate, process, store, transmit other multimedia content—e.g., moving image sequences (such as video), text messages, audio data, notifications, events, and other information—in the same manner as that discussed above and shown in
Environmental Awareness
Characteristics of the nodes 12′-22′, environments local to those nodes, and/or users thereof, can be determined by direct communication/interaction with sensors on those nodes, by inference, e.g., based on time, date, and node location, and/or by a combination thereof. The nodes 12′-22′ and/or server 24a′ can use these characteristics to (i) alter the state of the node(s), (ii) alter the presentation of content, (iii) alter user notifications, (iv) tag content residing on the respective node and/or transmitted by it to the server 24a′, (v) generate notifications (or send content) to users of other nodes, (vi) alter prioritization of tasks by the respective node, and/or (vii) schedule transmission of images (or other content) from the server 24a′ to the nodes 12′-22′ (or vice versa).
Thus, one or more of the nodes 12′-22′ may include (but are not limited to) one or more of the following sensors:
In some embodiments, such sensors are used to identify the presence or absence of a (possibly specific) user, and/or provide date and/or time specific feedback or content to the user, e.g., as discussed (by way of non-limiting example), below:
(i) In some embodiments, for example, a photo-detector present on a node, e.g., 20′, can be used by logic on that node to determine ambient lighting and, thereby, to effect screen dimming (or brightening). Likewise, a motion sensor on that node can be used to detect the presence of a user at the node 20′ and, thereby, switch among display modes (e.g., image display mode, clock display mode, display-off mode).
(ii) In some embodiments, one or more of the nodes, again, for example, node 20′, includes one or more of the foregoing sensors that enable it to determine the identity of a user. That information can be used for, or in connection with, the tagging discussed above. Logic on the node can also use this information to alter the content and/or associated notifications that the node presents to a specific user. For example, a user can be presented with images and/or albums specific to him and/or can be notified and presented with newly arrived images (or other articles of content). Alternatively or in addition, the node can generate user-specific alerts (e.g., to take medications, walk the dog, see the doctor and so forth, based on information provided at set-up, by the server, by preconfiguration, or otherwise) and/or can generate notifications to the server 24a′ and/or the other nodes indicating that the user is present.
(iii) In some embodiments, logic on one or more of the nodes, for example, node 20′, determines node location, the local time of day, date, and so forth, via data available from servers on the network 26′, or otherwise. The node and/or server 24a′ can use this information for, or in connection with, the tagging noted and discussed in (iv) above. Logic on the node and/or server 24a′ can also use this information to alter (i) the state of the node, (ii) the presentation of images (or other content) thereon (e.g. only “new” or recent content), (iii) associated notifications that the node presents to users, such as, weather forecasts, birthday reminders, missing child (e.g., “Amber”) alerts, shopping or vendor-specific notifications (e.g., advertising), and so forth.
(iv) In some embodiments, one or more of the nodes, e.g., node 20′, includes a touch sensor, motion sensor and/or proximity sensor that is used, for example, to gauge user interest in a particular image (or other article of multimedia content) presented by that node and to tag that image (or other article of content) accordingly. For example, if the node 20′ detects a user's touch during display of a particular image (or other article of content) and/or album, that image or album can be tagged as a “favorite” or otherwise. This tag can be retained on the node to alter further presentation of that image or album (e.g., increasing frequency of presentation). The tag can also be transmitted to the server 24a′ for recording in store 38 for statistical purposes, archival purposes, and/or to alter presentation of that image or album on other nodes. In this latter regard, for example, user interest in an image detected in the foregoing manner can be conveyed to other nodes to which that image is transmitted and presented as part of an album (or otherwise), thereby, alerting other users to the level of interest in that image.
(v) In some embodiments, logic on a node, e.g., 20′, can detect user interaction (e.g., via one or more of the foregoing sensors) and can generate notifications (or send content) to users of other nodes, such as to reply to the sender of an article of content, forward content to a user at another node, place an order to purchase a hardcopy article of content, or “block” the sender of an article of content from sending any further content to a node.
(vi) In some embodiments, the server 24a′ and/or respective nodes can detect node and/or network activity and can adjust prioritization of tasks accordingly, e.g., suspending the download of images during user interaction with a node.
Content Presentation Devices (CPDs)
Processor 90
Internal Memory 92
I/O Ports
Touch Sensor Input 96
Other Sensors 98
Visual Output 99
Audio Out 100
Display (LCD) 102
RF Module 104
Antenna 106
Power Supply 108
Of course, it will be appreciated that the schematics shown in
Headless Devices
Headless devices 21A′ can be constructed (and operated) in a manner similar to that of CPDs 20′, 22′ discussed above, albeit without one or more of touch sensor input 96, other sensors 98, visual output 99, display 102, and/or power supply 108.
As used herein, removeably couple refers to communications coupling (electromechanically, via cable or wire, wirelessly, or otherwise) that is and/or can be effected temporarily in the normal course of the device's operational use. Examples include USB devices that are designed for insertion into and removal from USB ports and/or for connection to and disconnection from USB cables of host devices during normal use, WiFi and BlueTooth devices that are designed for transitory communications with paired hosts, all by way of non-limiting example, infrared and other optical communications devices that are designed for optical communications with nearby (and, typically, paired) hosts, all by way of non-limiting example.
User Interface
Like the other nodes, CPD 20′ (and 22′) can accept user input, e.g., for manipulating or otherwise altering images and image information presentation, addition, deletion or otherwise changing image information, including image tags, and so forth (see the discussion above under the heading “User Interaction”). To facilitate this, the CPD 20′ employs a user interface (“UI”) that provides, inter alia, for navigation of/interaction with images (and other multimedia content) and for setting device CPD 20′ characteristics/modes. Devices 21A′ that are headless nodes can likewise accept such user input for like purposes (e.g., manipulating/altering images or other multimedia content) via such a UI presented on associated host devices 21B′. Though the discussion below refers to the CPDs and their Ins for sake of brevity, it will be appreciated that those teachings are equally applicable to the headless devices 21A′ and their respective host devices 21B′.
That UI, which is implemented by CPU 90 operating in conjunction with display 102 and touch sensor 96 (among other components of the device 20′) in the conventional manner known as adapted in accord with the teachings hereof, is activated when the user initiates contact with the device 20′, e.g., via its touch screen 96′, though, in other embodiments, the UI can be activated in other ways (e.g., upon sensing motion in vicinity of the device, upon device start-up, periodically based on timing, or so forth). Such activation interrupts/pauses any slideshow or content presentation on an active device 20′ (or wakes an inactive device 20′) and opens a menu option with which the user can interact.
In some embodiments, CPU 90 (operating in conjunction with display 102, touch sensor 96, and other components of the device 20′) effects a UI that displays a hierarchical menu of user-selectable graphical or textual icons (hereinafter, “function-selection icons”), each of which is associated with one or more functions. The menu is referred to as “hierarchical” because, while user selection (e.g., via touch sensor 96) of some of those icons results in invocation of the respective associated function, user selection of others of those icons results in display (or activation) of plural additional icons, at least one of which must be selected by the user to invoke a function.
In practice, CPU 90 invokes a function selected by the user via the menu by calling a software routine and/or activating a hardware component (92-108) to execute the requisite operations. This is done in the conventional manner known as adapted in accord with the teachings hereof. Invokable functions in the illustrated embodiment include, though other embodiments may provide lesser, greater and/or other functions:
1.1.1. navigation/interaction
1.1.1. settings
Referring to
In the illustrated embodiment, the set of user-selectable function-selection icons from which the subsets are selected is ten or larger and, more particularly, 15 or larger and, still more particularly, twenty or larger, and yet still more particularly is approximately equal in number to the invocable functions listed above and, yet, still more particularly, is equal to the number of “leaves”—as opposed to “branches”—in the hierarchical listing of invocable functions above. (In other embodiments, function-selection icons may be provided corresponding to one or more of such branches, as well). In contrast, the display 102 of the illustrated embodiment is approximately 1″-10″ in width and 1″-10″ in height and, more preferably, 1″-7″ in width and 1″-5″ in height and, still more preferably, about 4″-7″ in width and about 4″-7″ in height. Moreover, the real estate on such display 102 in which the icons are displayed may range from 5%-100% of the display 102 depending on its size. For example, in a display 102 that is 6″×4″ or 5″×7″ inches, that real estate may comprise 20% of the display (thereby, leaving more of the display available for images), while in a display 102 that is 10″×8″, that real estate may comprise 10% of the display.
As above, user selection of selected function-selection icons results in invocation of the respective associated function, while user selection of other such function-selection icons results in a display which (i) presents options necessary to further specify function selection, and which may differ in format (for example, not including display of a carousel-like arrangement of user-selectable function-selection icons). Conversely, user selection of menu-index icons (which, themselves, may be textual or graphical) results in presentation of the subsequent or preceding small grouping of function-selection icons in the carousel.
In still other embodiments of the invention, the CPU 90 may implement a menu utilizing a combination of hierarchical and carousel-like graphical formats/structures. In yet still other embodiments, the CPU 90 may implement still other menu structures.
Regardless, the CPU 90 can implement a UI that presents additional textual and/or graphical information on the display 102, e.g., for user viewing and/or selection. This can include captions 124 containing, for example, image information (e.g., time/date of image acquisition, sender identification, and so forth, as discussed above). It can also include, for example, user-selectable navigational icons 126a, 126b that permit the user to “step through” a sequence of images (or other content) of the type transmitted by server 24a′ to device 20′.
For convenience, a UI effected by CPU 90 on display 102 is referred to as a “screen.” In
For sake of clarity, no actual images (e.g., of a small girl, or otherwise), are shown in the screens depicted in
Content Sharing Model
organization of server store, including representation of a user account, organization of other nodes into a community a.k.a. ‘group’, node synch (between server and CPD a.k.a. ‘frame’), organization of an ‘album’ of content, and including representation of an image and corresponding image information (as also shown in
(ii) input to server (e.g. from Sender1), content management (server store), distribution to nodes and/or groups of nodes (Frame1, Frame2, email3, mobile4), and examples of feedback (e.g. reply, block, undelete, forward, tag) to other nodes (e.g. Sender1 and Recipient1) via the server.
Described above are systems, devices and methods meeting the aforementioned objects, among others. It will be appreciated that the embodiments described and shown herein are merely examples of the invention and that other embodiments incorporating changes thereto may fall within the scope thereof. Thus, by way of non-limiting example, the permissions described above as attributable to nodes may, instead or in addition, be attributable to users of those nodes.
In view thereof, what we claim is pointed out in the section entitled “Claims.”
This application claims the benefit of priority of the following U.S. provisional applications: U.S. Ser. No. 61/429,898, filed Jan. 5, 2011, entitled “Systems and Methods For Multimedia Content Sharing With Removeably Coupled Headless Computing and/or Communications Nodes;” U.S. Ser. No. 61/313,488, filed Mar. 12, 2010, entitled “Systems and Methods For Multimedia Content Sharing With Removeably Coupled Headless Computing and/or Communications Nodes;” and U.S. Ser. No. 61/310,582, filed Mar. 4, 2010, entitled SYSTEMS AND METHODS FOR MULTIMEDIA CONTENT SHARING. This application is also a continuation-in-part and claims the benefit of priority of U.S. Ser. No. 12/221,789, filed Aug. 6, 2008, entitled SYSTEMS AND METHODS FOR MULTIMEDIA CONTENT SHARING, which is a continuation-in-part of same-titled U.S. Ser. No. 12/186,498, filed Aug. 5, 2008 (now abandoned). The teachings of all the aforementioned U.S. applications are incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
61429898 | Jan 2011 | US | |
61313488 | Mar 2010 | US | |
61310582 | Mar 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12221789 | Aug 2008 | US |
Child | 13040726 | US | |
Parent | 12186498 | Aug 2008 | US |
Child | 12221789 | US |