1. Field of the Invention
The present invention relates generally to network communications. More particularly, the present invention relates to network mediated delivery of rich media content.
2. Background Art
Photo albums have long been a popular format for commemorating special experiences, such as those arising from group travel or a group visit to a recreational venue. The photo albums assembled to memorialize these special events may sometimes include more than photos. For example, cutouts of map portions may be included to illustrate a travel route or highlight a destination, and dialogue bubbles may accompany personal photographs to convey the significance of a particular event or communicate significant episodes of group interaction.
The conventional approach to celebrating special events through production of a personal photo album devoted to the event includes several disadvantages, however. For example, the content from which the album is assembled is typically limited to content produced by the person assembling the album, or gathered by that individual from other members of the group sharing the common experience. Moreover, as a consequence of its often informal creation, a conventional photo album may convey a somewhat primitive aesthetic, resulting in a less than optimally pleasing artistic product for sharing with others.
In addition, a commemorative album assembled as previously described may actually be difficult to share. Because a physically assembled album is often a singular object, difficult to reproduce, members of the group celebrated by the album must typically be present at a common location to mutually enjoy its contents. Alternatively, the album may be circulated amongst the group members, or to outsiders to the group, eliminating the requirement that all be present in a common location. Unfortunately, circulation prevents the members temporarily dispossessed of the album from enjoying the reminiscences evoked by it, while depriving the outsiders not in possession of the album from appreciating its contents.
A more recent approach to commemorating a special event utilizes the advantages made available by modern communications technology to share digital images corresponding to the event. Widely available computer applications such as Shutterfly, and Kodak EasyShare, for example, enable ready sharing of electronic photos and photo albums among the members of a group, as well as their distribution to outsiders. Because an electronic photo album is much more easily reproduced than a physically assembled album, this approach overcomes the previous obstacles to mutual enjoyment of the commemorative content by all viewers concurrently, independent of their location.
Despite making commemorative digital content easier to share and enjoy, however, the conventional electronic solution to producing a digital photo album continues to place the burden of content production on one or more members of the group participating in the celebrated event. That is to say, the content contained by an electronic photo album is still typically limited to the content produced or gathered by group members. While that content, due to its likely personal significance to the group members, may be satisfactory for sharing among the group, as is true for the physical photo album produced according to the earlier conventional approach, the resulting collection of content may lack the richness and complexity of a professionally produced product, and be less desirable for viewing by outsiders to the group.
As a result of the various described disadvantages associated with conventional approaches to producing a collection of commemorative content, celebrating a special experience through creation of a commemorative album is unnecessarily difficult and inconvenient. Furthermore, because conventional approaches are likely to produce a less than optimally appealing artistic product, sharing enjoyment of the special experience with others may be less satisfying for all parties than if the commemorative album were more professionally produced.
Accordingly, there is a need to overcome the drawbacks and deficiencies in the art by offering a solution capable of providing a professional quality rich media commemorative record of a group event, to celebrate, memorialize, and enable sharing of the event.
There are provided systems and methods for providing a rich media visitor log, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.
The features and advantages of the present invention will become more readily apparent to those ordinarily skilled in the art after reviewing the following detailed description and accompanying drawings, wherein:
The present application is directed to a system and method for providing a rich media visitor log. The following description contains specific information pertaining to the implementation of the present invention. One skilled in the art will recognize that the present invention may be implemented in a manner different from that specifically discussed in the present application. Moreover, some of the specific details of the invention are not discussed in order not to obscure the invention. The specific details not described in the present application are within the knowledge of a person of ordinary skill in the art. The drawings in the present application and their accompanying detailed description are directed to merely exemplary embodiments of the invention. To maintain brevity, other embodiments of the invention, which use the principles of the present invention, are not specifically described in the present application and are not specifically illustrated by the present drawings. It should be borne in mind that, unless noted otherwise, like or corresponding elements among the figures may be indicated by like or corresponding reference numerals.
As shown in
According to the embodiment of
In a similar manner, visitors using mobile communication devices 130b and 130c may opt-in to the group session by identifying themselves as belonging to the group including the user of mobile communication device 130a. Subsequently, the users of mobile communication devices 130a, 130b, and 130c, can communicate with all other members of their group substantially simultaneously, in a number of different ways, as shall be described. For example, a user of mobile communication device 130a can send SMS text messages to communications server 110, for distribution by group management application 112 to mobile communication devices 130b and 130c. In addition, the members of the group can utilize group management application 112 to communicate with local services network 120 to, for example, obtain rich media content provided by visitor photo management application 122. Moreover, the members of the group may utilize group management application 112 to exchange communications including rich media content, such as photos, videos, and audio/video mashups produced by members of the group. In addition to providing management of group communications during the group session, group management application 112 may also be configured to expire activation of the group session, for example, after a predetermined time interval has elapsed since its activation.
Visitor log host application 118 is designed to generate a rich media visitor log commemorating the group visit to the recreational venue. Visitor log host application 118 may be configured to collect communications from the communications exchanged among mobile communication devices 130a, 130b, 130c, and local services network 120, and managed by group management application 112. Visitor log host application 118 may be further configured to identify exemplary communications for inclusion in a rich media visitor log from the collected communications, select rich media display assets corresponding to the identified exemplary communications from display asset database 117, and produce the rich media visitor log from the identified exemplary communications and the selected rich media display assets.
Although the present embodiment has been described by reference to SMS text messaging, in other embodiments, group messaging may occur via other communication formats. For example, in one embodiment, group communications, such as opt-in messaging and messaging amongst group members, for example, may include exchange of Multimedia Messaging Service (MMS) messages. In other embodiments, communications may occur through mobile Instant Messaging (IM) or other Transmission Control Protocol/Internet Protocol (TCP/IP) channels, enabled by Enhanced Data rates for Global System for Mobile communications (EDGE), Enhanced General Packet Radio Service (EGPRS), or International Mobile Telecommunications Single Carrier (IMT-SC) technologies, for example.
Turning to
As shown in
According to the present embodiment, group communication control software 219b is located in memory 234, having been received from communications server 210 via LAN 226. LAN 226 may comprise a wireless network such as a Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), or Bluetooth network, for example. Although in the present embodiment, transfer of group communication control software 219a is shown to result from data transfer over LAN 226, in another embodiment communication control software 219a may be downloaded over a packet network, such as the Internet, for example. In yet another embodiment, group communication control software 219a may be transferred via a wired or wireless connection to a client computer (not shown in
Controller 236 may be the central processing unit for mobile communication device 230, for example, in which role controller 236 runs mobile operating system 232, launches mobile browser 237, and facilitates execution of group communication control software 219b. Web browser 237, under the control of controller 236, may be used to enable a user of mobile communication device 230 to view communications content distributed by group management application 212 running on communications server 210.
As was the case for system 100 in
Similarly, as in
As previously noted, the systems shown in
Skipping ahead to
Turning to
Referring to step 410 of flowchart 400 in conjunction with
Upon entry into the Magic Kingdom, the group may be provided with documentation explaining the features and operation of the available services for managing group communications within the park. The documentation may include a group identification code that may be used in common by the users of mobile communication devices 130a, 130b, and 130c, for example, three members of the group including Kate, Billy, Mom, and Dad. The group identification code may take the form of a printed alphanumeric code, requiring manual entry into the respective mobile communication devices, or a radio frequency identification (RFID) tag readable by mobile communication device 130a, 130b, and 130, for example. In one embodiment, a protocol for assigning group identification codes assures that sequential codes are not assigned to successive visitors, or groups of visitors, entering the park, in order to prevent one visitor or group from successfully anticipating the group identification code assigned to another visitor or group, and intercepting or intruding into that other group's communications.
Step 410 is performed when a first message sent by any member of the group opts in to group management by providing communications server 110 with the group identification code issued to the group of Kate, Billy, Mom, and Dad. As in the embodiment of
The exemplary method of flowchart 400 continues with step 420, which comprises activating a group session corresponding to group identification code 342. Step 420 may be performed on communications server 110, for example, using group management application 112 and referring to a plurality of pre-authorized group identification codes available on communications server 110. Activating a group session in step 420 may comprise confirming that group identification code 342 is a valid code and initiating activation of the group session. As mentioned earlier, in some embodiments, a group session is associated with a predetermined activation period. In those embodiments, step 420 may additionally correspond to verification that the activation period for the group session has not been previously tolled. Although not represented in
Flowchart 400 continues with step 430, comprising collecting communications generated by and for members of the group during the group session. Having received a first message opting in to group management in step 410, and having activated a group session corresponding to group identification code 342 in step 420, the group may be enlarged by the receipt at communications server 110 of additional opt-in messages from Kate, Billy, and Mom. During a group session, messages generated by or for group members are collected for possible inclusion in a rich media visitor log commemorating the group session. Messages collected in step 430 may include opt-in messages from members of the group, communications among members of the group by means of group management application 112, exchange of rich media content among group members, retrieval and distribution of rich media content from local services network 120, and any communication containing information with regards to the location or activities of the group members. Collection of group communications on communications server 110 can continue as communications among group members occurs, during activation of the group session.
Continuing with step 440 of flowchart 400, step 440 comprises expiring activation of the group session. As previously remarked, in some embodiments, the group session for which activation is activated in step 420 is associated with a predetermined activation period. For example, a group session initiated as the result of entry into a theme park may be limited in time to an eighteen or twenty four hour window, at the end of which the group session is automatically terminated. A predetermined activation period may be determined to enable group communication in-park, but be of a duration making it unlikely that visitors will be able to continue group communication using the resources on communications server 110 after their group in-park experience has ended. In some embodiments the users of communication devices 130a, 130b, and 130c may be provided a means for ending their respective participation in the group session voluntarily, prior to the system imposed expiration of the activation period. In those embodiments, termination of the group session may occur when the participation of all group members has voluntarily ended.
Moving now to step 450 of flowchart 400, step 450 comprises identifying exemplary communications from the communications collected in step 430 for inclusion in the rich media visitor log. In one embodiment, identifying exemplary communications in step 450 may be an automated process, executed by visitor log host application 118. In other embodiments, identifying exemplary communications for inclusion in the rich media visitor log may include human input from, for example, one or more group members, or a human expert with editorial authority over the contents of the rich media visitor log. In some embodiments identifying exemplary communications for inclusion in the rich media visitor log may include filtering the collected communications in order to suppress or redact those communications containing inappropriate content, due to their subject matter or mode of expression, for example.
Continuing with step 460 of flowchart 400, step 460 comprises selecting rich media display assets corresponding to one or more of the identified exemplary communications from a plurality of display assets accessible to visitor log host application 118 on display asset database 117. The plurality of display assets may include rich media assets local to communications server 110, for example, maps or images corresponding to popular locations in-park, or imported display assets. Imported display assets may include rich media content exchanged between group members through use of group management application 112, as well as rich media content generated in-park through local services network 120. Where a communication from a group member comprises a message checking in at a specific park location, for example, a corresponding display asset may be text describing that action, and/or a graphical element depicting the locale. Alternatively, where a communication is provided for the members of the group comprising a notification message of the availability of rich media content retrieved from local services network 120, a corresponding display asset may be the rich media content retrieved.
In step 470 of flowchart 400, the exemplary communications identified in step 450 and the corresponding rich media display assets selected in step 460 are used to produce a rich media visitor log of the group session. As was the case in step 450, in some embodiments, producing the rich media visitor log in step 470 may be an automated process performed by visitor log host application 118. In other embodiments, however, producing the rich media guest log may include input, such as design input, for example, from a human producer.
Although not shown in flowchart 400 of
Referring to
From the above description it is manifest that various techniques can be used for implementing the present concepts without departing from their scope. Moreover, while the present application has provided a disclosure with specific reference to certain embodiments, a person of ordinary skills in the art would recognize that changes can be made in form and detail without departing from the spirit and the scope of the inventive concepts described. As such, the present embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that other embodiments are not limited to the particular implementational details described herein, but are capable of many rearrangements, modifications, and substitutions without departing from the disclosed inventive concepts.
This application claims priority to U.S. Provisional Application No. 61/069,116, filed on Mar. 11, 2008, which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6189783 | Motomiya et al. | Feb 2001 | B1 |
6671807 | Jaisimha | Dec 2003 | B1 |
7251495 | Keyani | Jul 2007 | B2 |
7409221 | Obradovich et al. | Aug 2008 | B2 |
7412042 | Henry | Aug 2008 | B2 |
7505779 | David | Mar 2009 | B1 |
7509124 | O'Neil | Mar 2009 | B2 |
7689510 | Lamkin | Mar 2010 | B2 |
7779097 | Lamkin | Aug 2010 | B2 |
7801537 | Matsumoto et al. | Sep 2010 | B2 |
8005460 | Chen | Aug 2011 | B2 |
8099109 | Altman et al. | Jan 2012 | B2 |
8332402 | Forstall et al. | Dec 2012 | B2 |
20010054101 | Wilson | Dec 2001 | A1 |
20020068573 | Raverdy | Jun 2002 | A1 |
20020069419 | Raverdy | Jun 2002 | A1 |
20020082897 | Menelly | Jun 2002 | A1 |
20020174003 | Redmann | Nov 2002 | A1 |
20020174248 | Morriss | Nov 2002 | A1 |
20030014749 | Simons et al. | Jan 2003 | A1 |
20030083889 | Macklin | May 2003 | A1 |
20030172090 | Asunmaa | Sep 2003 | A1 |
20030185232 | Moore | Oct 2003 | A1 |
20030191946 | Auer | Oct 2003 | A1 |
20040019513 | Colalancia | Jan 2004 | A1 |
20040019800 | Tatebayashi et al. | Jan 2004 | A1 |
20040022227 | Lynch | Feb 2004 | A1 |
20040078341 | Steichen | Apr 2004 | A1 |
20040116115 | Ertel | Jun 2004 | A1 |
20040158482 | Hale | Aug 2004 | A1 |
20040172315 | Hale | Sep 2004 | A1 |
20040172316 | Hale | Sep 2004 | A1 |
20040181424 | Hale | Sep 2004 | A1 |
20040184593 | Elsey | Sep 2004 | A1 |
20040214600 | Schechet | Oct 2004 | A1 |
20040266408 | Maes | Dec 2004 | A1 |
20050044224 | Jun | Feb 2005 | A1 |
20050060173 | Hale | Mar 2005 | A1 |
20050144642 | Ratterman | Jun 2005 | A1 |
20050202830 | Sudit | Sep 2005 | A1 |
20050240970 | Schwalb | Oct 2005 | A1 |
20050262530 | Ruetschi et al. | Nov 2005 | A1 |
20050266827 | Kim | Dec 2005 | A1 |
20060008256 | Khedouri | Jan 2006 | A1 |
20060159109 | Lamkin | Jul 2006 | A1 |
20060189337 | Farrill | Aug 2006 | A1 |
20060230061 | Sample et al. | Oct 2006 | A1 |
20070016584 | Grell | Jan 2007 | A1 |
20070032247 | Shaffer | Feb 2007 | A1 |
20070038476 | Sternlicht | Feb 2007 | A1 |
20070136573 | Steinberg | Jun 2007 | A1 |
20070157281 | Ellis et al. | Jul 2007 | A1 |
20070161402 | Ng | Jul 2007 | A1 |
20070203763 | Ackley | Aug 2007 | A1 |
20070208664 | Ortega | Sep 2007 | A1 |
20080014911 | Medved et al. | Jan 2008 | A1 |
20080045192 | Zhao et al. | Feb 2008 | A1 |
20080189293 | Strandel | Aug 2008 | A1 |
20080201158 | Johnson et al. | Aug 2008 | A1 |
20080248781 | Cedo Perpinya et al. | Oct 2008 | A1 |
20080319935 | Chandak | Dec 2008 | A1 |
20090061835 | Schmidt | Mar 2009 | A1 |
20090100480 | McQuaide | Apr 2009 | A1 |
20090156181 | Athsani | Jun 2009 | A1 |
20090163177 | Bearden | Jun 2009 | A1 |
20090204905 | Toghia | Aug 2009 | A1 |
20090215469 | Fisher et al. | Aug 2009 | A1 |
20090233543 | Watson | Sep 2009 | A1 |
20090233639 | Watson et al. | Sep 2009 | A1 |
20090234935 | Watson et al. | Sep 2009 | A1 |
20090313479 | Schroeter | Dec 2009 | A1 |
20100063866 | Kinoshita et al. | Mar 2010 | A1 |
20100080163 | Krishnamoorthi et al. | Apr 2010 | A1 |
20100093373 | Olsson et al. | Apr 2010 | A1 |
20100144328 | Keating et al. | Jun 2010 | A1 |
20100150120 | Schlicht et al. | Jun 2010 | A1 |
20110082639 | Jung et al. | Apr 2011 | A1 |
Entry |
---|
“Twitter: What are you doing?” 2008 Twitter. Jan. 6, 2009 <http://twitter.com/>. |
“Jaiku | Your Conversation.” 2008 Jaika. Jan. 6, 2009 <http://jaiku.com/>. |
Acohido, Byron, Google's GPhone strategy could keep user costs low, USATODAY.com., (Oct. 14, 2007). |
“3jam SuperTest::Your Free Text Messaging Inbox on the Web.” 2009 3jam, Inc.. Jan. 6, 2009 <http://www.3jam.com/>. |
“Your Social Compass.” 2009 Loopt, Inc. Jan. 6, 2009. <http://www.loopt.com/>. |
“dodgeball.com :: mobile social software.” 2009 Google Inc. Jan. 6, 2009. <http://www.dodgeball.com>. |
“Disney Files Patent for Wireless FastPasses.” NETCOT.com. posted Sep. 5, 2007<http://www.netcot.com/thesite/2007/09/05/disney-files-patent-for-wireless-fastpasses/>. |
U.S. Appl. No. 12/313,228 Non-Final OA dated Mar. 28, 2011. |
U.S. Appl. No. 12/313,228 Resp. to Non-Final OA (as Filed on May 25, 2011). |
U.S. Appl. No. 12/313,231 Non-Final OA dated Apr. 1, 2011. |
U.S. Appl. No. 12/313,231 Resp. to Non-Final OA (as Filed Jul. 1, 2011). |
U.S. Appl. No. 12/313,229 Non-Final OA dated Sep. 22, 2010. |
U.S. Appl. No. 12/313,229 Resp. to Non-Final OA (as Filed Dec. 22, 2010). |
U.S. Appl. No. 12/313,229 Final OA dated Mar. 14, 2011. |
U.S. Appl. No. 12/313,229 RCE and Resp. to Final OA (as Filed on Jun. 13, 2011). |
U.S. Appl. No. 12/313,229 Non-Final OA dated Aug. 4, 2011. |
U.S. Appl. No. 12/313,228 Non-Final OA dated May 24, 2012. |
Number | Date | Country | |
---|---|---|---|
20090233543 A1 | Sep 2009 | US |
Number | Date | Country | |
---|---|---|---|
61069116 | Mar 2008 | US |