WO2015061696A1 - Système d'événement social - Google Patents

Système d'événement social Download PDF

Info

Publication number
WO2015061696A1
WO2015061696A1 PCT/US2014/062193 US2014062193W WO2015061696A1 WO 2015061696 A1 WO2015061696 A1 WO 2015061696A1 US 2014062193 W US2014062193 W US 2014062193W WO 2015061696 A1 WO2015061696 A1 WO 2015061696A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
users
social
mobile device
user
Prior art date
Application number
PCT/US2014/062193
Other languages
English (en)
Inventor
Scott Howard NORWALK
Original Assignee
Peep Mobile Digital
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Peep Mobile Digital filed Critical Peep Mobile Digital
Publication of WO2015061696A1 publication Critical patent/WO2015061696A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • Creators of photographic content often desire to distribute their photos to others. For example, if a person takes a photo at a birthday party, other people at the party may want the photographer to share the photograph.
  • One method used today to share photos is to take the camera home and upload the photos of the event to a shared repository. The photographer may then send a link to the repository to other people so that they may view the photos.
  • the upload action is performed after the party, and sometimes, long after the party, making the sharing of the photos non-contemporaneous with the party itself.
  • a social event system includes an event server configured to identify a group of users of the social event system that are socially connected to one another; and automatically provide a recommendation to the group of the users to be event participants to a social photo event, where the social photo event is defined according to one or more of a geographic proximity, a temporal proximity, and the group of users.
  • a mobile device is associated with a user of a social event system and configured to send location information to an event server of the social event system; and receive, from the event server responsive to identification of the user of the mobile device as being within a group of users of the social event system that are socially connected to one another, a recommendation to join a social photo event defined according to one or more of a geographic proximity, a temporal proximity, and the group of users.
  • a non-transitory computer-readable medium includes instructions that, when executed by at least one processor of a mobile device associated with a user of a social event system, cause the mobile device to be configured to send location information to an event server of the social event system; and receive, from the event server responsive to identification of the user of the mobile device as being within a group of users of the social event system that are socially connected to one another, a recommendation to join a social photo event defined according to one or more of a geographic proximity, a temporal proximity, and the group of users.
  • FIG. 1 is an example of a system diagram for a social event system
  • FIG. 2A is an example diagram of a geographic location including events and that are managed by the social event system
  • FIG. 2B is an example diagram of a global/local event managed by the social event system
  • FIG. 3 is an example diagram of content data for an event, as captured by mobile devices of multiple participants of the social event system
  • FIG. 4 is an example diagram of content data maintained by the data center of the social event system
  • FIG. 5 is an example of a workflow of an event having two users from a system perspective
  • FIG. 6 is an example of a workflow of an event having two users from a mobile device perspective
  • FIG. 7 is an example of a workflow for an entourage feature
  • FIGS. 8A and 8B are an example of a dataflow for an entourage feature
  • FIG. 9 is an example of a workflow for a take-back feature
  • FIG. 10 is an example of a dataflow for a take-back feature
  • FIG. 11 is an example of an activity diagram for a private messaging service for a social event system
  • FIG. 12 is an example of an activity diagram for a public messaging service for a social event system
  • FIG. 13 is an example of a global compilation and refinement of a verified global spatial directory
  • FIG. 14 is an example of an activity diagram for post-event processing related to a social event system
  • FIG. 15 is an example of front-row feature for a social event system.
  • a social group refers to a collection of users who may be connected by a shared activity, interest, affiliation or other characteristic.
  • Social photography refers to the concept of users of a social group sharing their photographs with other users of the social group.
  • a social event refers to a social occasion or activity including an association of a social group with a geographical location and an interval of time.
  • Social event photography refers to the sharing of photographs of a social event taken during the event by the participants with the other participants of the social group associated with the event.
  • a system may be configured to provide a digital platform for social event photography.
  • the platform may allow users of the system to define social events, invite participants to share photographs taken by the users at the socials events, and facilitate the management of the photographs of the social event during and after the event.
  • the platform may further include additional features in addition to performing as a data repository for the shared photos of the event.
  • the platform may include features such as invitations by location, post-event image upload (in an attempt to reduce data charges while away from a home Wi-Fi network), rating systems to rank photographs and photographers, instant messages between users based on selected photographs, processes to remove inappropriate user content, and other features for orchestrating a successful social event.
  • the system may include a server component configured to manage digital photographs taken by users of the system; manage event definitions including locations, times and participants; and maintain associations of users and client devices with events and social groups.
  • the system may also include a client component for use by participants of the event, such as a mobile application executable by client devices with image capture functionality.
  • the client component may be configured to allow users to access the server component to perform tasks such as receiving invitations to events, joining events, defining new events, inviting users to events, and providing digital photographs taken while attending events.
  • the client devices may be configured to utilize the mobile application to define events to which other users may be invited.
  • the platform may be configured to provide invitations to the other users to participate in the event.
  • the invitations may be provided to users through push notifications sent from the platform to the mobile applications of users entering the location and time for the event.
  • the invitations may be provided to the users in the form of text message invitations (e.g., short message service (SMS) messages, instant messages (IMs), etc.).
  • SMS short message service
  • IMs instant messages
  • the invitations may include information configured to facilitate invited users who do not have the mobile application to download the mobile application (e.g., a link from which to download the mobile application), such that the invited users may install the mobile application and participate in the social event. Once installed, the mobile application may in turn enable those new users to join the event as well as create their own social events.
  • the server component may be configured to track the current locations of the client devices (e.g., through use of global positioning system (GPS) geolocation, through use of Bluetooth technology such as the iBeacon Bluetooth Low Energy technology provided by Apple, Inc. of Cupertino, California, etc.). Based on the client device locations, the server component may be configured to notify the client devices that they may join an event to which they are invited. When users with the mobile application show up at the event location and time, they may be notified of the social photography event at that location. The users may then choose to join the event, and once joined may share and receive photos using the mobile application.
  • GPS global positioning system
  • Bluetooth technology such as the iBeacon Bluetooth Low Energy technology provided by Apple, Inc. of Cupertino, California, etc.
  • An active participant of a social event refers to a member of the social group who is in attendance at the social event
  • a passive participant of the social event refers to a member of the social group who is joined or otherwise associated with the event but is not in attendance at the event.
  • the client device may be configured to utilize a photo sharing tool of the mobile application to capture and share photos of the event with other users also associated with the event.
  • the client device may be configured to view the shared photos of the event, but may be excluded from sharing pictures.
  • Users that have the mobile application installed to their devices may be automatically notified of an event when they enter an event location and time. For example, the mobile application may be executed as a background process scanning for social events or notifications from a server component of social events. Potential users who do not have the mobile application may download the mobile application to their mobile device in order to be advised of events automatically.
  • Users may also be notified of events by invitation from other users.
  • users may send other users invitations via an email invitation, short message service (SMS) message, or a universal resource locator (URL) link on a social media site or a blog.
  • SMS short message service
  • URL universal resource locator
  • the electronic communications may be sent by either the event host or someone who is participating at the event.
  • the communications may include a URL link to a location from which the mobile application may be downloaded so that a potential user who is not yet a social event user may be invited to and may join the event quickly after receiving the invitation.
  • the user may be immediately informed of all events at or near their location (e.g., from one to thousands) by the mobile application signaling their presence via a notification (e.g., blinking, playing a sound effect).
  • a notification e.g., blinking, playing a sound effect
  • the sound effect may be a click similar to that of a distinct electronic camera shutter.
  • the number of notifications provided to the user may be based on how often the user sets the mobile device to provide notification (e.g., to play the sound).
  • the mobile device may be configurable with respect to how many times the mobile device will play the sound, for example, with a range of 1 to 100.
  • How often the interval between which the sound may be played may be configurable until a maximum configured number of attempts is reached.
  • a user may configure the mobile application to provide notifications an event 10 times every 5 seconds, 20 times every 5 seconds, 20 times every 30 seconds, etc.
  • a default notification setting may be to provide the notification 12 times every 5 seconds, for a time period totaling one minute.
  • the user may also have control to configure when and how the user is informed of an event (e.g., whether to notify audibly, visually, etc.).
  • the mobile application may be configured to display a listing of the total number of events at the current location.
  • the listing of events may be sortable by characteristics of the event, such as by when the event begins, when the event ends, how many participants are at the event, whether the event is public or private, alphabetically by event name, and by event ratings (e.g., using a rating system that follow the Motion Picture Association of America (MPAA) rating system such as G, PG, PG-13 and R).
  • MPAA Motion Picture Association of America
  • the mobile application interface for events may also include a search field to facilitate user search for particular events in case there are many events in a location and the user needs to find a specific name of an event or a person hosting a social event.
  • Each event may be associated with a cover photo, where the cover photo may be an image used to represent the event in the notifications and/or in the listing of events.
  • the host may select a photo recently taken by the host or another photo included in the event to be presented as the cover photo for the event.
  • the cover photo may be selected by the event host to illustrate the content included within the event, and may accordingly be utilized by other users browsing of the listing of events or receiving the notifications as a clue to the content included within the event.
  • the system may automatically assign a cover photo to the event at random (e.g., a random picture within the event, a random stock photo, etc.)
  • the user may utilize the user interface of the mobile application to join the event.
  • the user may select the event to join from a listing of available events, and may further select a "join event" control of the user interface.
  • the event is private, the request may be sent to the event host and the user may wait for electronic admittance to the event.
  • the request for admittance to the event may be referred to as a knock, and an event for which admittance requires a knock may be referred to as a knock event.
  • the event is public, the user may join immediately and begin the photo sharing experience. If the event is secret, then the event may be invisible to users who are not preregistered or otherwise invited to the event, and only users who are invited to the event may join the event.
  • the mobile application may be configured to allow the user to join multiple events at the same time, such that the photos taken by the user may be shared with the participants of each event to which the user is joined when the photo is taken.
  • photos taken by the user during the time window e.g., temporal proximity
  • the pictures the user receives back from the groups are not shared by the user across events and stay unique to each event. In other words, only users who are part of both groups may receive the photos from both groups.
  • social photography events may be bridged (e.g., joined together) by the hosts of the events to create a shared group event. When events are combined in this manner, then everyone in the groups may accordingly be granted access to the photos of both events.
  • a user travels outside the geographical limits of an event (e.g., if geographical limits for the event are configured) while the event is still in progress, then the user may still receive photos taken at the event, but the user may no longer share new photos with the event.
  • the user transitions from being an active event participant to being a passive event participant.
  • the photos that the user previously took while within the geographic bounds of the event are still shared with the group participants of the event and follow the sharing rules for the event as if the user was still part of the event.
  • the social photography event system may notifies them that they are about to leave the event (e.g., by playing its unique shutter sound). If the user decides to return at any time during the event, the user may manually and/or automatically rejoin the event and may then begin sharing photos again. Leaving an event may have no effect on receiving fully developed photos after the event; it just changes how the photos from the user may be shared to the event.
  • the mobile application may be configured to allow users to manage and otherwise control their own social events. Additionally or alternatively, a website component of the platform may be configured to allows users to log into their account and control features and functionality of their events to determine a level of service that best suits their needs (e.g., running multiple events, creation of templates for most used types of events, etc.).
  • a user who creates a social event may be referred to as an event host.
  • the user may log-in to their connected account via an online network and, as the event host, may specify a location and time for the social event, as well as whether the event is a public or private event.
  • the event host may specify other aspects of the event as well, such as whether event participants are allowed to invite outside participants.
  • the event host may accordingly be an administrator of the event who may have complete control over the interactions enabled for the event participants.
  • cloud-based storage services such as Apple's iCloud and/or DropBox, which only set up storage folders
  • social event photography lets the event host set up an event by date and time at a specific location.
  • the event host may access an event host control panel either on their mobile device or through a website portal.
  • This control panel may be configured to provide the event host with information regarding the social photography event, including, but not limited to, how many participants are at the event, the names of each participant, total photos taken by each participant, messages sent by the participant, the time and date that participants joined, if there is a charge for the event, the amount that the person paid for the event and payment type, invitations sent by participants to other participants, whether the participant is an active participant at the current location or a remote viewer, the current locations of the remote participants, and to what social networks the participants belong.
  • the event host may be able to send a private message to anyone at the event, send a public message to everyone at the event, remove a participant from the event, and/or remove any photos from the event.
  • the event host may utilize various functions of the event host control panel to change various parameters for an event.
  • a change event name function may allow the event host to change the event name at any time during the event. In an example, once the event ends, the event name cannot be changed and may be locked.
  • An end event function may allow the event host to end an event prior to the scheduled event end time.
  • An extend event time function may allow the event host to extend the total duration of the event at any time during the event.
  • a blast message to all participants at event location function may allow the event host to send a mass message simultaneously to all participants at the event location.
  • a blast message only to remote viewers function may allow the event host to send a message simultaneously to all participants that are viewing the event remotely.
  • a blast message to everyone function may allow the event host to send a message simultaneously to everyone at the event.
  • a view participants function may allow the event host to see the details of everyone who is attending the event. These details include the following variables by clicking on a name in the table the host can bring up an individual and conduct actions such as the following: (i) remove the participant from the event immediately or based on a countdown timer from 10 seconds to one hour; (ii) send a text message to that participant; (iii) limit the number of photos that the participant can share from their device; (iv) limit the number of messages the participant can send to other participants at the event; (v) limit the number of participants they can invite to the event; and (vi) limit the number of participants they can share with outside the event.
  • the event host may further enhance the experience for all the participants through a feature -rich digital platform that manages the social interactions surrounding the photographs.
  • Social event photography provides a user interface ("UI"), robust set of features, and the ability to share with social media (e.g., via the Facebook social network provided by Facebook, Inc. of Melno Park, California).
  • the social event photography system may provide a platform that puts users in control of social events. Whether there are two participants or thousands at an event, everyone at the location quickly becomes part of the photo sharing experience. Moreover, the photos may be shared with participants by location, date, and time.
  • the system may also support social interaction feature including; votes, quotes, chats. Users may quickly join a social photography event, and also remember where a photo is stored based on the social photography event they attended, versus looking for an electronic folder stored on a local computer or on a cloud-based storage service.
  • FIG. 1 is an example of a system diagram for a social event system 100.
  • the system 100 includes a network 110 over which mobile devices 120, terminals 120, merchants 140, datacenters 150, e-commerce systems 185, and third-party systems 190 may communicate.
  • the datacenter 150 may be configured to store user data 160, content data 170, content metadata 175, and event data 180.
  • An event server 155 may be in communication with the data center 150, and a social event application 125 may be installed to the mobile devices 120.
  • the social event system 100 may be used for social event photography, among other purposes.
  • the social event system 100 provides a platform for participants to set up social events, invite others to the social events, share information among users of the system 100, and otherwise provide for communication among the users of the system 100.
  • the platform provides various types of services to create and manage events, along with the content and communication that may occur related to the event.
  • the network 110 may be configured to provide for electronic communication of data among the various components of the system 100.
  • the network 110 may include one or more interconnected networks that provide communication between the system components.
  • network 110 may include the Internet, another wide area network, a local area network, a cellular phone network, a Bluetooth network, and/or USB-networked components.
  • the data center 150 may be in communication with the network 110, and may be configured to include one or more data storage devices configured to store and retrieve data for the social event system 100.
  • Databases, data repositories or other data stores described herein may include various kinds of mechanisms for storing, accessing, and retrieving various kinds of data, including a hierarchical database, a set of files in a file system, an application database in a proprietary format, a relational database management system (RDBMS), etc.
  • RDBMS relational database management system
  • Each such data store is generally included within a computing device employing a computer operating system, and is accessed via the network 110 in any one or more of a variety of manners.
  • a file system may be accessible from a computer operating system, and may include files stored in various formats.
  • the RDBMS may employ one or more of the structured query language (SQL) and a language for creating, storing, editing, and executing stored procedures, such as the PL/SQL language mentioned above.
  • SQL structured query language
  • the data center 150 is illustrated as being located at a single location on the network 110, the data center 150 it is not intended to describe a particular location or set of machines. Data center 150 should be understood to include cloud computing applications and/or other disparate, collaborative, or other means of processing. Moreover, the data center 150 may include one or more data center 150 computing devices located at different physical locations.
  • the user data 160 may include a data repository such as a database for storing information about the users of the system 100.
  • the user data 160 may include, for example, logon information for the user such as a username and a password.
  • logon information for the user such as a username and a password.
  • the user data 160 may also include other information, such as preferred templates and other user preferences that may be stored by the system 100.
  • the user data 160 may also include billing information or other information for use by the system 100.
  • the event data 180 may include information about social events for use by the system 100.
  • the event data 180 may include, for example, the location of the event, the time of the event, the participants to the event, the organizers of the event, etc.
  • the location may be defined by various information or a group of information.
  • One way to define a location may be by way of a physical geographic location, e.g., specified by GPS coordinates.
  • Another way to define the location may be using the GPS location in addition to a radius distance, such that the location is defined by an area surrounding the GPS location as defined by the radius. However, the radius is not the only way to define the location given GPS coordinates.
  • geometry or contours of the event location may be defined by the shape of structures surrounding the event location (e.g., within a building, within a park surrounded by other structures or roads, etc.).
  • a physical address such as a postal address.
  • the physical address may be determined by a reverse geocode process whereby the GPS location of the event is provided to the reverse geocode process and the physical address is thereby determined.
  • the time of the event may typically be defined by a start time, and end time and/or a duration of the event. In some cases, the time of the event may also include multiple times for an event.
  • An example of an event having multiple time periods may be a lecture at a University that spans across a lunch break. In this example, the event could be defined by two distinct periods around the lunch period (e.g., lOam-noon, and lpm-2pm).
  • the time of an event may simply include a start time. As example of this may be of an event that simply has no explicit end, but instead extends for an indefinite amount of time. As yet a further possibility, the time of an event may be inferred based on the data range of the photos included in the event.
  • the event start time is that of a time corresponding to when an earliest photo within the event was taken
  • the event end time is a time corresponding to when a most recently taken photo within the event was taken.
  • the time range of the event may change as photos are added to or removed from the event.
  • the participants to the events may include one or more users of the system 100 for which user data 160 is stored by the system 100.
  • the participants to the events may additionally or alternately include new users that may register with the service after the event has started.
  • the participants to the event may be considered a dynamic group that may be added to or subtracted to before, during, or after the event has occurred.
  • the content data 170 may include content associated with the events, such as digital photographs taken at the events.
  • the content data 170 may be embodied as a large data store that, in many examples, stores primarily photographs. It should be understood that content data 170 can be located or co-located globally across one or more data centers 150. This may accordingly allow for localized storage and providing of content data 170 near the users of the system 100 that create or request it.
  • the content data 170 may also include cloud -based storage and delivery.
  • the content metadata 175 may include metadata related to the content data 170 gathered at the events.
  • the content metadata 175 may accordingly include information about photographs, such as what user took the photograph, what time the photograph was taken, and at what location the photograph was taken (e.g., GPS coordinates, heading or direction, event, etc.).
  • the mobile devices 120A, 120B, and 120C may include various types of devices (e.g., tablets, smartphones, etc.) having photography and location-determining features and data network connectivity over the network 110.
  • devices e.g., tablets, smartphones, etc.
  • the mobile devices 120 may include hardware configured to determine the location of the mobile device 120.
  • the mobile devices 120 may include a global positioning system (GPS) receiver configured to access a GPS system to determine precise location information with respect to the location of the mobile device 120.
  • GPS global positioning system
  • other approaches to location determined may be used by the mobile device 120, such as by way of Wi-Fi location detection or mobile phone cell tower triangulation, among other possibilities.
  • the mobile device 120 may also include image capture hardware, such as a digital camera, that may be used to capture content data 170 such as pictures or photographs at various locations.
  • the image capture functionality of the mobile device 120 may be configured to include content metadata 175 along with the captured content data 170, including information such as the time at while the image was captured, the location at which the image was captured (e.g., utilizing the location determining features of the mobile device 120), and information regarding the image format and size itself.
  • the mobile devices 120 may be configured to execute application programs (sometimes referred to as "apps") on one or more processors of the mobile devices 120.
  • the application programs may be stored on one or more non-volatile media of the mobile devices 120 (e.g., as software, firmware, etc.), and may be loaded into volatile media for execution. These application programs may be able to utilize the hardware and software features of the mobile devices 120, such as the camera, location, and networking features discussed above.
  • the social event client application 125 may be one such application stored on a nonvolatile media of the mobile device 120. When executed by the mobile device 120, the social event client application 125 may be configured to cause the mobile device 120 to perform operations such as log into the data center 150 according to login information user data 160 provided by the social event client application 125, create, join and modify event data 180 for social events, create content data 170 to be added to the social events, and view content data 170 such as digital photographs taken by others at the social event.
  • the event server 155 may be a server device in communication with the data center 150, or in other examples may be an application stored on a non-volatile media of the data center 150.
  • the event server 155 may be configured to manage the event data 180, user data 160, content data 170, and content metadata 175 of the data store 150.
  • the event server 155 may be configured to receive, from the mobile devices 120, requests for creation of events, content captured by the mobile devices 120, and location information regarding the mobile devices 120.
  • the event server 155 may be further configured to provide notifications of events to mobile devices 120 invited to be participants to events, and content for the events to the mobile devices 120 (such as images of an event captured by other users of mobile devices 120). Further aspects of the operation of the social event client application 125 and event server 155 are discussed in further detail below.
  • the terminal 130 may be configured to allow a user to access the system 100 via a traditional computer such as a desktop or laptop that may not include the features necessary to operate as a mobile device 120 of the system 100. However, in some cases the mobile device 120 may be utilized by the user as a terminal 130.
  • the terminal 130 may be used to allow users of the system 100 to perform administrative tasks with regard to events, such as to adjust event properties as an event host.
  • the merchant 140 may include a third party that may access the system 100. As some possibilities, the merchant 140 may use a website, or an API to access the system 100.
  • the electronic commerce (“e-commerce") system 185 may be configured to enable the social event system 100 to monetize certain content data 170.
  • a professional photographer may use social event system 100 to photograph a wedding.
  • the professional photographer may let the wedding attendees know about the social event client application 125, which may be utilized by the wedding attendees to view or preview photographs taken at during wedding event.
  • the users may utilize the services of the e-commerce system 185 to purchase photographs of the wedding that they may choose.
  • the professional photographer may thereby utilize the social event system 100 to conduct business.
  • the third-party system 190 may be configured to provide access by third parties to the system.
  • the third parties may include, as some possibilities, social networking systems such as the Facebook social network service provided by Facebook, Inc. of Melno Park, California, the PInterest visual discovery tool, the Twitter social networking and micro-blogging service provided by Twitter, Inc. of San Francisco, California, or others.
  • the third-party system 190 may include search applications, advertising systems, or other systems that may desire access to the social event system 100.
  • FIG. 2A is an example diagram 200A of a geographic location including events 280, 281 and 282 that are managed by the social event system 100.
  • the geographic location may include a restaurant 210, a cafe 220, a restaurant 230, a bowling alley 240, a nightclub 250 and an arena 260.
  • the event 281 may be located at the cafe 220
  • the event 280 may be located at the bowling alley 280
  • the event 282 may be located at the arena 260.
  • the geographic location of the event 281 may be defined by event data 180 including a geographic point within the cafe 220 and a radius 221 within which the geographic location of the event 281 is included.
  • the event data 180 for the event 281 may be utilized by the system 100 to determine which mobile devices 120 are located within the location of the event 281.
  • the mobile device 120A of a user may be located within the radius 221 during the time of the event 281 and may accordingly become part of the event 281.
  • the mobile device 120B may also be located within the radius 221 during the event 281 and may also become part of the event 281.
  • the event data 180 for the event 281 as shown in addition to including information indicative of the geographic location of the Cafe 220, also includes a time for the event (e.g., a start time of noon), a date for the event (e.g., "tomorrow"), an organizer of the event 281 (e.g., the user of mobile device 120B), a type of the event (e.g., a private event for which participants must be invited by the organizer), and the invitees to the event 281 (e.g., the users of mobile devices 120A and 120C).
  • a time for the event e.g., a start time of noon
  • a date for the event e.g., "tomorrow”
  • an organizer of the event 281 e.g., the user of mobile device 120B
  • a type of the event e.g., a private event for which participants must be invited by the organizer
  • the invitees to the event 281 e.g., the users of mobile devices 120A and 120
  • the geographic location of the event 280 may be defined as the bowling alley 240 (e.g., once again according to a geographic location and radius).
  • a time for the event e.g., a start time of 8:00 PM
  • a date for the event e.g., "today”
  • an organizer of the event 280 e.g., the user of mobile device 120A
  • a type of the event
  • the event 282 may be defined by the event data 180 as the bounds of the arena 260, and during the time of a sporting event scheduled for the arena 260.
  • a professional photographer mobile device 262 may be the organizer of the event 282, and may take photographs during the event 282.
  • Participants to the event 282 may also include a spectator 263 that is at the physical location of the event 282, and another participant 264 who may be participating in the event 282, but is not at the arena 260 location of the event 282.
  • the user of the photographer mobile device 262 may utilize the e-commerce system 185 to charge for content data 170, such as photographs captured by the photographer 262 and received by participants 263, 264.
  • the e-commerce system 185 may be configured to provide promoters and/or organizations at the arena 260 with a royalty for content data 170 photographs sold via the e-commerce system 185.
  • FIG. 2B is an example diagram 200B of a global/local event 290 managed by the social event system 100.
  • a global/local event 290 may refer to an event that includes participants at both a local level (i.e., within the geographic area of the event) and at a global level (i.e., outside the geographic area of the event).
  • the global/local event 290 may be useful for events that have both local and remote viewers, such as for example, a televised soccer match.
  • the global/local event 290 may be attended by global participants (e.g., global participants 291, 292, 293), and local participants (e.g., local participant 294). While the local participant 294 may be physically located at the event 290, the global participants 291, 292, 293 may also be able to access content data 170 for the event 290 even though they are physically located away from the event 290. As shown, participant 291 may be located in California, participant 293 may be located in England, and participant 292 may be located in South Africa.
  • the social event system 100 enables participants from around the world to share in the photographs being taken at the global/local event 290.
  • the content data 170 images may be uploaded from mobile devices 120 of the users who are at the event 290 to the social event system 100 via network 110 and instantly, or nearly instantly, distributed to participants 291, 292, 293 around the world.
  • FIG. 3 is an example diagram 300 of content data 170 for an event, as captured by mobile devices 120 of multiple participants of the social event system 100.
  • the mobile device 120A includes an image store 302A that holds photos 120A1, 120A2, 120A3, 120A4.
  • mobile device 120B includes an image store 302B that holds photos 120B1, 120B2, 120B3, 120B4
  • phone 120C includes an image store 302C that holds photos 120C1, 120C2, 120C3, 120C4. As shown, these photos are stored physically on each user's mobile device 120.
  • FIG. 4 is an example diagram 400 of content data 170 maintained by the data center 150 of the social event system 100.
  • Event El includes a virtual data store 402 A for users 120 A, 120B for photos taken at the event El . These photos include 120A1, 120A2, 120A3, 120A4 and 120B1, 120B2, 120B3, 120B4.
  • Event E2 includes a virtual data store 402B for users 120B, 120C for photos taken at the event El . These photos include 120B1, 120B2, 120B3, 120B4 and 120C1, 120C2, 120C3, 120C4.
  • the diagram 400 further shows a physical data store 404 illustrating the physical storage of content data 170 in the data center 150.
  • the physical data store 404 includes a single copy of the images 120A1, 120A2, 120A3, 120A4, 120B1, 120B2, 120B3, 120B4, 120C1, 120C2, 120C3, 120C4. This provides that the images may be physically stored once, but event data 180 provides the affiliation for the events to images such that they may be shared by the users defined for the events El, E2.
  • FIG. 5 is an example workflow diagram 500 illustrating a data flow for a lifecycle of an event having two users from a system 100 perspective.
  • the data flow may be performed, for example, by the elements of the system 100 discussed in detail above.
  • the data flow may be initiated, for example, by the event organizer mobile device 120 A utilizing the social event client application 125 to input information describing a new event to be created, the event information specifying a time, place, and invitees or participants for the event.
  • the event organizer mobile device 120 A may send the created event request to the event server 155.
  • the event server 155 may receive the event request, and may communicate with a geocoding service 190.
  • the geocoding service 190 may be internal or external to the event server 155, and may be configured to apply a geocoding to the event, such as a GPS coordinate with a radius or other geometry surrounding the event location.
  • the geocoding service 190 may receive input indicative of a location, and may provide back geocoded information descriptive of the identified location.
  • the geocoded information may include a geographical coordinate and a radius surrounding that coordinate.
  • the event server 155 may further determine that the event has the necessary information to be created, and if the verification of the event by the event server 155 is successful the event may be stored in the user data store 160 or alternatively, in the event data store 180.
  • the event server 155 may push the event to the owner or organizer, as shown in the diagram 500 as mobile device 120 A.
  • the event server 155 may also push the event to the mobile devices 120 of the other invitees or participants identified by the event, e.g., to mobile device 120B as shown in the diagram 500.
  • the social event client applications 125 of the mobile devices 120 may be informed of the locations of the event to which they are invitees.
  • the mobile application 125 of the mobile device 120 A may utilize the pushed event information to become aware of the user arrival to the event.
  • the mobile application 125 may accordingly notify the event server 155 of the arrival of the mobile device 120 A at the event.
  • the event organizer mobile device 120 A may take a photo 120A1, and the photo 120A1 may be stored in the device image store 302 of the user's mobile device 120A.
  • the mobile application 125 may be informed that a picture is taken. As one possibility, the mobile application 125 may monitor the device image store 302 for new images. As another possibility, the mobile application 125 may provide image capture features, and may be notified of their creation due to use of the image capture features of the mobile application 125.
  • the mobile application 125 may reduce the image size of the captured image to create a preview image, and may send the preview image to the event server 155 for storage in the content data store 170.
  • the mobile application 125 of the mobile device 120B may utilize the pushed event information to become aware of the user arrival to the event.
  • the mobile application 125 may accordingly notify the event server 155 of the arrival of the mobile device 120B at the event.
  • the event server 155 may send the preview image 120A1 to event participant mobile device 120B.
  • the event organizer mobile device 120 A may take a photo 120A1, and the photo 120A1 may be stored in the device image store 302 of the user's mobile device 120A.
  • the mobile application 125 may be informed that a picture is taken. As one possibility, the mobile application 125 may monitor the device image store 302 for new images. As another possibility, the mobile application 125 may provide image capture features, and may be notified of their creation due to use of the image capture features of the mobile application 125.
  • the mobile application 125 may reduce the image size of the captured image to create a preview image, and may send the preview image to the event server 155 for storage in the content data store 170.
  • the event server 155 may send preview image 120B1 to the other event participants. In the illustrated example, the event server 155 may send the preview image 120B to the event organizer mobile device 120 A.
  • a participant to the event may exit the geographic bounds of the event before the event has completed. For example, the event participant mobile device 120B may moves outside of the radius of the event to go to another location. Once the mobile device 120 has moved outside of the event area, since the mobile device 120B is no longer a participant to the event the event server 155 may no longer allow photographs to be uploaded by the mobile device 120B.
  • the mobile device 120B may still be able to act as a passive participant to the event and receive photos taken by active participants to the event.
  • the event organizer mobile device 120 A the user of which is still at the event location, may take another photo 120A2.
  • a preview image 120A2 of that photo may be sent by the mobile device 120 A to the event server 155, which may store the preview to the content data store 170.
  • the mobile device 120B may then receive the preview image 120A2 from the event server 155, even though the mobile device 120B is no longer in attendance at the location of the event.
  • An event may expire when the time for the event has passed.
  • the event server 155 may determines that the event has expired.
  • each of the mobile applications 125 of the mobile devices 120 may determine that the event has expired (e.g., independently from the determination made by the event server 155, by being notified by the event server 155, etc.).
  • FIG. 6 is an example workflow diagram 600 of an event having two users from a mobile device 120 perspective.
  • the workflow may be performed, for example, by the elements of the system 100 discussed in detail above.
  • the workflow may be initiated, for example, by a user of the mobile application 125 logging into a web service 602 for the social event system 100 (e.g., provided by the event server 155).
  • the event server 155 may verify the credentials of the user, e.g., according to user account information stored in the user data store 160.
  • the mobile application 125 may retrieve events from the web service 602 related to the user or to the user's location (e.g., responsive to providing the location of the mobile device 120 to the event server 155). The events may be sent from the web service 602 to the mobile application 125 of the user and stored in secure storage 604 of the mobile device 120.
  • the mobile application 125 may wake up and check the location of the mobile device 120.
  • the location updates may be performed by periodically polling for the location of the mobile device 120, by using a GPS trigger or GPS alarm, or via a built-in feature of the mobile device 120 to notice an application (such as the mobile application 125) when a location has been achieved.
  • the mobile application 125 may update the location of the mobile device 120, e.g., using a GPS subsystem 606 of the mobile device 120 configured to provide a current location for mobile device 120.
  • the mobile application 125 may compare the current location of the mobile device 120 with the stored locations of the events for that user maintained in the secure storage 604 of the mobile device 120. Based on the comparison, the mobile application 125 may determine that the mobile device 120 is at the time and location for an event. Accordingly, the event may be triggered for the mobile device 120. When the event is triggered, the mobile application 125 may notify the web service 602 of the arrival of the user of the mobile device 120 to the event.
  • the event organizer mobile device 120 A may take a photo, and the photo may be stored in the device image store 302 of the user's mobile device 120 A.
  • the mobile device 120 may inform the mobile application 125 that a photo has been taken.
  • the mobile application 125 may access the image, create a preview image of the photo, and may send the preview image to the web service 602.
  • the web service 602 may then send that preview to other participants in the event. Those thumbnails may be stored in the secure photo phone storage 608 for each of the receiving mobile devices 120.
  • the mobile application 125 may also check the GPS location of the mobile device 120 again at regular intervals, if a polling system is used. In an example, the mobile application 125 determines that the user has left an event. Based on the determination of the mobile device 120 having left the event, the mobile application 125 may notify the web service 602 that the mobile device 120 has left the event.
  • the web service 602 may continue to send previews to the mobile device 120 after the mobile device 120 has left the event. These previews may be stored in photo secure storage 608 of the mobile device 120.
  • the mobile device 120 may notify the mobile application 125 that a picture has been taken. However, because there are no events associated with that user, the mobile application 125 may take no action with that photo.
  • FIG. 7 is an example of a workflow 700 for an entourage feature.
  • the entourage feature allows an event host, or the system 100 itself, to define criteria 702 for automatic creation of or inclusion of users in social photo events.
  • the entourage feature may facilitate the automatic creation of an event for a user when his or her friends are in the same location at any time (i.e., not necessarily at a predetermined time set up for the event).
  • the entourage feature may facilitate the automatic creation of an event for a group of users when the metadata of photos taken by the users indicate that the photos are taken of a common event and by friends.
  • These criteria may be referred to as a template, and may include, in an example, identifiers of a plurality of users of the mobile application 125.
  • the event host may utilize the system 100 to select friends to be invited as participants 704 to the entourage group.
  • the user may log-in to their connected account (e.g., via a web interface of the event server 155) via an online network 110 and may access an entourage group creation feature of the system 100.
  • the system 100 may then send invitations 706 to the selected friends.
  • the invitations may be provided to the users in the form of text message invitations (e.g., short message service (SMS) messages, instant messages (IMs), etc.).
  • SMS short message service
  • IMs instant messages
  • the system 100 may further receive accept or decline responses 708 from the invited friends, and may add those accepting users to the entourage group.
  • the event host may further set up a photo event template 710 related to the entourage group.
  • the template may include information with respect to the settings for the events that may be automatically created. These settings may include, as some non-limiting examples, relative geographic bounds within which participants are located to invoke an event; limits on the number of photos that the participant can share from their device; limits on the number of messages the participant can send to other participants at the event; limit on the number of participants other participants may invite to the event; and limit the number of participants that may be shared with outside the event.
  • the event host may then assign the entourage group to the template 712.
  • a template may only be associated with one entourage group at a time.
  • multiple templates can be created and associated with different entourage groups. This means that multiple templates for multiple entourages may be launched at the same location, as long as there is more than one individual from each entourage at that location for the associated template.
  • template number one can be associated with entourage number one
  • template number two can be associated with entourage number two.
  • the system 100 creates a new event 714, and the mobile applications 125 of the mobile devices 120 automatically join the new event.
  • the mobile application 125 automatically launches a social photo event for the defined template when the entourage feature is enabled for that template every time more than one person in the defined entourage group is in the same location.
  • the event may continue until less than two people from the defined Entourage group remain at such location 720. Thus, the event may continue even though one, more than one, or even all the original users who caused the event to be created initially have left the event.
  • the system 100 may automatically infer friends to be added as participants 704 to the entourage group using a concept of implied friendship to establish a recommendation.
  • the system 100 When a user performs certain actions that indicate friendship between users, such as: (i) a user of a mobile device 120 inviting another user to his or her event, (ii) a user a mobile device 120 accepting a request (e.g., a knock request) from another user to join an event, (iii) a user a mobile device 120 commenting on a photo of another user, (iv) a user of a mobile device 120 including another user in his or her contacts or address book, etc., the system 100 establishes a connection between the users. This connection (or social connection) may be referred to as an implied friendship. As additional actions that indicate friendship between users are identified by the system 100, the system 100 may increase the maintained strength of the implied friendship between the two users.
  • a connection or social connection
  • the system 100 may increase the maintained strength of the implied friendship between the two users.
  • the system 100 may be configured to cross-reference the photos of users stored in the user's image stores (e.g., content data store 170) to identify whether any photos appear to belong to a shared moment between the users.
  • a shared moment may occur, in an example, where two or more users who are connected according to the implied friendship "net" include photos in their image stores that were taken within geographic proximity and temporal proximity to one another.
  • the geographic proximity and temporal proximity may be determined from the photos according to similarity of the content metadata 175 of the photos stored in the content data store 170, for example. (As another possibility, it should be noted that geographic proximity and temporal proximity may also be used as inputs to infer an implied friendship between users.)
  • the system 100 may provide a recommendation or other notification to the users to trigger creation of a new event.
  • An example message for creation of such an event may be "Scott, you and your friends Dino and Justin have 30 photos from your trip to Las Vegas. Want to start an event?"
  • the system 100 may utilize the aggregated date, time, and location metadata of current photos of users as well as implied friendship information to establish a recommendation of photos that make sense to use to create an event.
  • the system 100 may also utilize the aggregated date, time, and location metadata and the friendship information to establish a recommendation of photos that make sense to add to an existing event. For instance, if an event for the geographical location and temporal location already exists for a subset of identified users determined to have photos from a particular place and time, the system 100 may provide a notification to the users not included in the event to trigger invitation to the existing event.
  • Metadata is collected including time, date, and location of the included photos. This information may be used to establish a temporal proximity (e.g., a date range) and one or more approximate locations (e.g., geographic proximity) defining where photos from this shared moment came from. This temporal proximity and geographic proximity may be associated by the system 100 with the event as pre-selection criteria to apply to photos to be added to the event.
  • a temporal proximity e.g., a date range
  • approximate locations e.g., geographic proximity
  • the user may be shown pre-selected photos from the user's personal photo library which meet the date range and approximate location(s) that are part of this event's pre-selection criteria (i.e., the photos of the user that are within the temporal proximity and geographic proximity as defined according to the other photos already included in the event).
  • the user may be prompted to add the recommended photos to the event, or may be further provided with the recommended photos as a default section that may be modified by the user (e.g., to facilitate de-selection of photos that the user does not wish to share with the event).
  • This matching of photos may be referred to as smart match.
  • the smart match functionality may not only apply to photos taken in the past but may also apply for current events.
  • an event e.g., at a concert
  • the invited users may be prompted to add any photos that they had just taken at the concert to the event if those photos fit within the geographic proximity and temporal proximity associated with the event.
  • the definition of the temporal proximity and geographic proximity of the event may adjust with the changing contents of the event.
  • the system 100 may support the addition of photos to the content data store 170 without a corresponding event.
  • a user may take photos without joining an event, such as by way of a camera application or the mobile application 125 installed to the mobile device 120 of the user.
  • the user may decide whether to include photos taken at that location and a time.
  • a user may take pictures whether joined to an event or not, and when the user is ready to include friends or other users, the user may participate in an event by either joining one or creating one and then include the photos that the user has been taking.
  • the camera user interface may include an indication (e.g., a menu on a side of the screen of the mobile device 120) that illustrates the people with which the user is currently sharing photos (whether the sharing is done automatically, e.g., for all photos that correspond to the event location, or by swiping the pic after taking it, e.g., to approve the photo for inclusion in the event).
  • an indication e.g., a menu on a side of the screen of the mobile device 120
  • the people with which the user is currently sharing photos whether the sharing is done automatically, e.g., for all photos that correspond to the event location, or by swiping the pic after taking it, e.g., to approve the photo for inclusion in the event.
  • a user may be associated with an Entourage including members of the family of the user. Accordingly, when the user takes pictures when the family members and the user are located within a geographic proximity, the user may utilize the mobile application 125 to automatically share photos taken with the mobile device 120 with the other members of the Entourage in an automatically created event.
  • the names of the users within the automatically created Entourage event may be illustrated on a menu of the mobile application 125 when the camera of the mobile application 125 is displayed.
  • the system 100 may invoke event post-processing. Further details of post-processing are discussed in more detail with respect to FIGS. 9-10 below.
  • the system 100 may again wait for the next automatic event to occur 724, and may automatically initiate another event 714 when multiple participants are again detected at a location.
  • the social event system 100 may automatically launch template number two. Likewise, when more individuals from Entourage Two show up at that given location, they are automatically added to event number two.
  • the entourage feature accordingly allows different groups of friends to share pictures automatically, based on defined templates when they show up at the same location.
  • the Entourage feature may be further configured to ensure that photos are unique and unduplicated between different Entourage groups.
  • photos are unique and unduplicated between different Entourage groups.
  • an individual is part of two Entourage groups for the same individual hosting those Entourage groups, then the photos for that user within both groups may only show up once across both groups.
  • the social event system 100 simplifies managing duplicate photos in complex social photo event situations.
  • FIGS. 8A and 8B are an example of a dataflow for an entourage feature.
  • an event host has created four Entourages, numbered one through four.
  • Mobile devices 120-1, 120-2, 120-3, 120-4, 120-5, 120-6, 120-7, 120-8 are participants to Entourage One.
  • Mobile devices 120-2, 120-3, 120-9, 120-10, 120-12, 120-13 are participants to Entourage Two.
  • Mobile devices 120-14, 120-15 are participants to Entourage Three.
  • Mobile devices 120-0 and 120-16 are participants to Entourage Four.
  • Mobile devices 120-0, 120-3, 120-9, 120-10, 120-16, 120-11, 120-2, 120-1, 120-6, 120-5 are located within the geographic area of the Entourages, and are participants that may share photos with the Entourages to which they are joined.
  • mobile devices 120-4, 120-7, 120-8, 120-12, 120-13, 120-14, 120-15 are outside the geographic area of the Entourages, and may receive photos from the Entourages to which they are joined but may not share photos.
  • an event stream of photos is created by the participants of the Entourages.
  • a photo P01 is taken by the mobile device 120-5 and shared with the Entourage One;
  • photo P02 is taken by the mobile device 120-10 and shared with the Entourage Two;
  • photo P03 is taken by the mobile device 120-9 and shared with the Entourage One;
  • photo P04 is taken by the mobile device 120-03 and shared with the Entourages One and Two;
  • photo P05 is taken by the mobile device 120-11 and shared with the Entourage Two;
  • photo P06 is taken by the mobile device 120-01 and shared with the Entourage One;
  • photo s P07 and P08 are taken by the mobile device 120-06 and shared with the Entourage One; and
  • photo s P09 and P10 are taken by the mobile device 120-16 and shared with the Entourage Four.
  • the Entourage Three as shown is not a started event and therefore no photos have been shared for that Entourage.
  • the content data store 170 may include only a single copy of each photo.
  • the photos taken by the mobile devices 120 may be stored by the system 100 in the content data store 170, and assigned unique identifiers. These unique identifiers may then be associated with the Entourages to which the mobile devices 120 are joined, thereby allowing the photos to be shared to the mobile devices 120 in the same Entourages as the taker of the photos.
  • FIG. 9 is an example of a workflow 900 for a take-back feature.
  • the photos may be stored on the mobile devices 120 on which they are taken. Additionally, the photos may be held on the mobile devices 120 for transfer to the data center 150 of the social event system 100 after the event ends.
  • the mobile application 125 may be configured to generate preview images of the photos, and provide the preview images to the event server 155 during the event. This provides that event participants may view the photos taken by other participants to the event in real time as they are taken.
  • the social event system 100 may use thumbnails (e.g., smaller than full resolution images) to enable the participants to view event photos in real time. These thumbnails may be sized to the mobile device 120 screen sufficient for viewing during the social event; however, the preview images may be of a lower quality that one may expect when printing the photograph.
  • the full resolution (or a higher resolution) image may be retrieved by the event server 155 (and/or provided by the mobile application 125) following the event, in a process whereby the mobile devices 120 of the event participants upload their photos to the data center 150 for post-event processing.
  • the mobile application 125 When an event participant takes a photo, the mobile application 125 generates a thumbnail image of the photo and transfers the thumbnail 902 to the data center 150 of the social event system 100.
  • the thumbnail is received 904 by the data center 150, organized according to the participants of the event 906 and the thumbnail image is made available 904 to the accounts of the other participants to the event.
  • the high resolution photographs are maintained by the mobile devices 102 of the event participants accounts and not necessarily transferred from the mobile devices 120 to the data center 150 or to the other participants. In this way, the thumbnail remains viewable on the mobile device 120, but the high-resolution printable image is accessible at the discretion of the user who took the image.
  • the high-resolution image may be downloaded for use on the mobile device 120 of the user on a social networking account of the user (e.g., a Facebook account or other social platform).
  • the thumbnails may be compressed files that can be transferred and managed while taking up a minimum of bandwidth and storage on the mobile devices 120 of the event participants.
  • one hundred thumbnail images may be equivalent to one full quality photo on a mobile device 120 of an event participant.
  • the participants may feel as though they are connected locally while the social event system 100 is uploading photos from the mobile devices 120 in real time using a compressed thumbnail and then transferring, or making available, those thumbnail images to the mobile devices 120 of the participants for use in the social event system 100.
  • Event participants may scroll through photos as fast as if the photos were local to their phone.
  • the participant also has all the built-in features and functionality made available by the social event system 100, including, but not limited to, real time sharing of photographs by location time and date, commenting and chatting about photos between participants, voting on photos, photo contests, facial recognition, e- commerce, etc.
  • participant may be given a warning by the host (e.g., a two-minute warning), such that the participants may take a "last great picture” or “last comment” or “last photo vote”.
  • a warning by the host e.g., a two-minute warning
  • the system 100 may begin a process to store the preview images and the corresponding high-resolution versions of the photos 910.
  • the event participants may be provided the ability to remove their photos from the event. This removal of photos from the event may be referred to as a "Take- Back.”
  • the event participants may utilize the take -back feature to remove photos 912 from the event that they are unhappy with or otherwise choose to remove for any reason.
  • the participant may utilize a user interface of the mobile application 125 to remove their own photos by going to the photo in the user interface, clicking on it, and selecting remove from the user interface.
  • the remove action performed in the post-event processing may remove the photo from being shared in the event. However, the remove action may not remove the photo from the individual's smartphone.
  • deleting from one's mobile device 120 may require a separate procedure (e.g., using an image maintenance application of the mobile device 120 apart from the mobile application 125) in order to protect deleting desired personal photos that an individual wants to keep, but does not want share with others from the event.
  • a separate procedure e.g., using an image maintenance application of the mobile device 120 apart from the mobile application 125
  • the mobile application 125 may automatically recognize the available network 914 and may begin transferring the photos taken from the Social Event to the Social Event System.
  • the social event system 100 may provide a predetermined, or configurable, time to ensure a minimum time (e.g., one hour) has elapsed between any event and when the photos begin to get transferred for post-party processing 916. This ensures all participants have time to "Take-Back" any photos that they do not want shared.
  • the images may be available for access 920 via the mobile application 125 or access 922 via a web interface to the social event system 100.
  • a participant to the event may download selected photos 924 to his mobile device 120, and/or continue to use the thumbnail versions of the photos as a convenient low-memory resource solution 906.
  • the user may perform actions such as printing the images 928, sharing of the images 930 with a social network, or viewing the images 932.
  • the mobile application 125 may automatically recognize the available network 914 when at a location where a high-speed connection is available, and transfer photos taken from the social event to the social event system without waiting for the event to conclude.
  • FIG. 10 is an example of a dataflow 1000 for a take-back feature.
  • participants #1, #2, and #3 each attend an event.
  • participant #1 takes photos #001, 002, 008, 009, 015
  • participant #2 takes photos #003, 006, 007, 012, 14, and participant #3 takes photos #004, 005, 010, 011, 013.
  • the mobile devices 120 of the participants may generate preview/thumbnail images, and may provide those images to the other participant mobile devices 120 via the services of the social event system 100. Copies of the preview images may also be maintained in the content data store 170 of the data store 150.
  • participant #1 uses the take -back feature to take back photos #001 and #015.
  • participant #2 does not take back any photos, but participant #3 uses the take -back feature to take back photo #005.
  • the post processing may be performed for a predetermined amount of time, such as 60 minutes. In an example, the amount of time for the post processing may be specified in the event properties or for an event template from which the event was automatically created.
  • the participant devices 120 may perform image upload of the high resolution/full quality versions of the photos.
  • the upload may be performed, for example, when the devices are at a home location (i.e., in communication with a home wireless network) or other location with a data connection predefined as being suitable for image upload.
  • the content data store 170 may remove the preview images for those images that were taken back by the participants during the post-event processing. In the illustrated example, the photos #001, 005, 015 are removed from the content data store 170.
  • the upload process is complete (which may vary by specific mobile device 120), the high-resolution photos and also the preview images for the photos of the event are ready and available for viewing and sharing by the users according to their individual requirements.
  • FIG. 11 is an example activity diagram 1100 for a private messaging service related to the social event system 100.
  • the data flow may be performed, for example, by the elements of the system 100 discussed in detail above. Similar to as discussed above with respect to Fig. 500, the data flow may be initiated, for example, by the event organizer mobile device 120A utilizing the social event client application 125 to input information describing a new event to be created, the event information specifying a time, place, and invitees or participants for the event.
  • the event organizer mobile device 120 A may send the created event request to the event server 155.
  • the event server 155 may receive the event request, and may apply a geocoding to the event, such as a GPS coordinate with a radius or other geometry surrounding the event location.
  • the geocoded information may include a geographical coordinate and a radius surrounding that coordinate.
  • the event server 155 may further determine that the event has the necessary information to be created, and if the verification of the event by the event server 155 is successful the event may be stored in the user data store 160 or alternatively, in the event data store 180.
  • the event server 155 may push the event to the owner or organizer, as shown in the diagram 500 as mobile device 120 A.
  • the event server 155 may also push the event to the mobile devices 120 of the other invitees or participants identified by the event, e.g., to mobile device 120B as shown in the diagram 500.
  • the social event client applications 125 of the mobile devices 120 may be informed of the locations of the event to which they are invitees.
  • the mobile application 125 of the mobile device 120 A may utilize the pushed event information to become aware of the user arrival to the event.
  • the mobile application 125 may accordingly notify the event server 155 of the arrival of the mobile device 120A at the event.
  • the event organizer mobile device 120A may take a photo 120A1, and the photo 120A1 may be stored in the device image store 302 of the user's mobile device 120A.
  • the mobile application 125 may be informed that a picture is taken. As one possibility, the mobile application 125 may monitor the device image store 302 for new images. As another possibility, the mobile application 125 may provide image capture features, and may be notified of their creation due to use of the image capture features of the mobile application 125.
  • the mobile application 125 may reduce the image size of the captured image to create a preview image, and may send the preview image to the event server 155 for storage in the content data store 170.
  • the mobile application 125 of the mobile device 120B may utilize the pushed event information to become aware of the user arrival to the event.
  • the mobile application 125 may accordingly notify the event server 155 of the arrival of the mobile device 120B at the event.
  • the event server 155 may send the preview image 120A1 to event participant mobile device 120B.
  • the event organizer mobile device 120A may take a photo 120A1, and the photo 120A1 may be stored in the device image store 302 of the user's mobile device 120A.
  • the mobile application 125 may be informed that a picture is taken. As one possibility, the mobile application 125 may monitor the device image store 302 for new images. As another possibility, the mobile application 125 may provide image capture features, and may be notified of their creation due to use of the image capture features of the mobile application 125.
  • the mobile application 125 may reduce the image size of the captured image to create a preview image, and may send the preview image to the event server 155 for storage in the content data store 170.
  • the event server 155 may send preview image 120B1 to the other event participants.
  • the event server 155 may send the preview image 120B to the event organizer mobile device 120 A.
  • a participant to the event may exit the geographic bounds of the event before the event has completed. For example, the event participant mobile device 120B may moves outside of the radius of the event to go to another location. Once the mobile device 120 has moved outside of the event area, since the mobile device 120B is no longer a participant to the event the event server 155 may no longer allow photographs to be uploaded by the mobile device 120B.
  • the mobile device 120B may still be able to act as a passive participant to the event and receive photos taken by active participants to the event.
  • the event organizer mobile device 120 A the user of which is still at the event location, may take another photo 120A2.
  • a preview image 120A2 of that photo may be sent by the mobile device 120 A to the event server 155, which may store the preview to the content data store 170.
  • the mobile device 120B may then receive the preview image 120A2 from the event server 155, even though the mobile device 120B is no longer in attendance at the location of the event.
  • An event may expire when the time for the event has passed.
  • the event server 155 may determines that the event has expired. Additionally or alternately, each of the mobile applications 125 of the mobile devices 120 may determine that the event has expired (e.g., independently from the determination made by the event server 155, by being notified by the event server 155, etc.).
  • the event server 155 may no longer accept new content preview images for the event.
  • the mobile application 125 of the mobile device 120 may begin the upload process for high-resolution images corresponding to the preview images sent to the event server 155 during the event.
  • the mobile application 125 may be configured to detect connection of the mobile device 120 to a network connection suitable for upload of full image data, such as a connection to a Wi-Fi network, to a mobile network, or another network.
  • the user of mobile device 120 A may comment on the image 120A1 to a specific event participant (e.g., the user of mobile device 120B). Although shown here as a comment to one event participant, private comments may also include a group of event participants. The private comment may pass through the event server 155 to a temporary message store 1110 (e.g., a message store of the data center 150).
  • a temporary message store 1110 e.g., a message store of the data center 150.
  • the event server 155 may then send the private comment to the event participant mobile device 120B (or participants) to which the private message is addressed. Once sent, the event server 155 may remove the private comment from the temporary message store. Accordingly, the event server 155 may be configured not to store private comments after they are received by the intended user/participant device.
  • Event participant 120B may then respond to the first private comment (without identifying the recipient because it is a response to event participant 120 A) with their own private comment on image 120A2, and that private comment is sent through the event server 155 to the temporary message store.
  • the event server 155 may then send a private comment from the event participant mobile device 120B to the event participant mobile device 120 A, using the private message information stored in the temporary message store. The event server 155 may then remove the private comment from the temporary message store.
  • FIG. 12 is an example activity diagram 1200 for a public messaging service related to the social event system 100.
  • the data flow of the activity diagram 1200 may be performed, for example, by the elements of the system 100 discussed in detail above.
  • the event participant mobile device 120A arrives at the geocoded location of the event, and notifies the event server 155 of its arrival. While at the event, the event participant mobile device 120 A takes a photo 120A1, and generates a preview image 120A1 corresponding to the photo 120A1. The event participant mobile device 120 A provides the preview image 120A1 to the content data store 170 of the system 100.
  • the event participant mobile device 120B arrives at the geocoded location of the event, and notifies the event server 155 of its arrival. While at the event, the event participant mobile device 120B takes a photo 120B1, and generates a preview image 120B1 corresponding to the photo 120B1. The event participant mobile device 120B provides the preview image 120B1 to the content data store 170 of the system 100. As the event participant mobile device 120 A is a participant to the event, the event server 155 sends the preview image 120B1 to the event participant 120A.
  • the user of mobile device 120 A may make a public comment on the image 120A1.
  • the mobile device 120 A may provide the public comment 120AC1 to the event server 155, to be added to the metadata content data store 180 for storage.
  • the event server 155 may send the public comment 120AC1 to the event participant 120B.
  • the user of mobile device 120B may also make a public comment on the image 120A1, possibly in response to the public comment 120AC1 posted by the mobile device 120A.
  • the mobile device 120B may provide the public comment 120BC1 to the event server 155, to be added to the metadata content data store 180 for storage.
  • the event server 155 may send the public comment 120BC1 to the event participant 120 A.
  • the event participant mobile device 120C may then arrive at the geocoded location of the event, and may notify the event server 155 of its arrival.
  • the event server 155 may accordingly provide the event participant mobile device 120C with the content of the event so far (e.g., preview images, public comments to the images, etc.).
  • the server application 125 may send the event participant mobile device 120C the preview image 120A1 and the preview image 120B1.
  • the event server 155 may also send the event participant mobile device 120C the public comments 120AC1 and 120BC1 related to image 120A1.
  • FIG. 13 is an example illustration 1300 of a global compilation and refinement of a verified global spatial directory.
  • the global spatial directory may be utilized by the social event system 100 to improve location recognition of locations specified by event hosts when creating events.
  • the social event system 100 may utilize the global spatial directory to create a verified global spatial directory. To accomplish this, the social event system 100 may provide the global spatial directory with the metadata of location coordinates (e.g., GPS and Bluetooth) specified by event hosts when creating or otherwise managing events. The social event system 100 may then match these location records against the databases for business and consumers (e.g., a Standard Industrial Classification "SIC" database, and/or other free or commercially available databases) to determine a name and other geographic information regarding the locations.
  • location coordinates e.g., GPS and Bluetooth
  • the social event system 100 may then match these location records against the databases for business and consumers (e.g., a Standard Industrial Classification "SIC" database, and/or other free or commercially available databases) to determine a name and other geographic information regarding the locations.
  • SIC Standard Industrial Classification
  • the system 100 may add a record to an unverified location database with the coordinates (e.g., from GPS and/or Bluetooth location information received from the event host specifying the location).
  • the social event system 100 may further watch for another event host to create an event at the same (or similar) coordinates using a similar name for that location.
  • the social event system 100 may update the record status of the unknown location to be a unique verified location.
  • the system 100 automatically updates the location to be a unique verified location record and is added to the verified location database. Variations on the system 100 are possible. In an example, the number of matches to become verified may be selectable based on criteria. As another possibility, a location may be revert to unverified status if numerous conflicting descriptions for the location are received by the system 100.
  • the system 100 may assign a unique ID to each event host (e.g., to each user having an account record in the user data store 160). This unique ID may be added to other otherwise associated with the record of a unique location when the unique location is added to the location database. Thus, when the system 100 identified that the same location name is matched at similar coordinates from a predetermined number of unique event hosts IDs (e.g., two, more than two, etc.), then the record of the unique location may be updated in status to that of a unique verified location.
  • a predetermined number of unique event hosts IDs e.g., two, more than two, etc.
  • the social event system 100 may also have different levels of unique verified location status, for example, based on the number of times the location name is identified at the coordinates, and by how many unique event host IDs the location name is used (e.g., according to processing of results from the location database queried according to the location name). Additionally or alternately, the recency of the last event that took place at that location name, will be included in the search methodology for increasing the levels of accuracy for any given solution in which the data is being applied.
  • the database containing the verified global spatial directory may accordingly be generated according to a compilation of data from sources such as the commercial business database, the commercial consumer database, and unique verified records compiled when events are created by event hosts. It should be noted that while the verified global spatial directory is discussed in relation to the social event system 100, the verified global spatial directory may be utilized by other systems as well. As a possibility, the system 100 may allow access to the verified global spatial directory through an online application programming interface, so that other applications or application developers may use the verified location content information for a myriad of different internet and software applications.
  • FIG. 14 is an example activity diagram 1400 for post-event processing related to the social event system 100.
  • the data flow of the activity diagram 1400 may be performed, for example, by the elements of the system 100 discussed in detail above.
  • the event participant mobile device 120A arrives at the geocoded location of the event, and notifies the event server 155 of its arrival. While at the event, the event participant mobile device 120 A takes a photo 120A1, and generates a preview image 120A1 corresponding to the photo 120A1. The event participant mobile device 120 A provides the preview image 120A1 to the content data store 170 of the system 100.
  • the event participant mobile device 120B arrives at the geocoded location of the event, and notifies the event server 155 of its arrival. While at the event, the event participant mobile device 120B takes a photo 120B1, and generates a preview image 120B1 corresponding to the photo 120B1. The event participant mobile device 120B provides the preview image 120B1 to the content data store 170 of the system 100. As the event participant mobile device 120 A is a participant to the event, the event server 155 sends the preview image 120B1 to the event participant 120A.
  • the event server 155 determines that the event ends, based on the time information for the event. Once the event has ended, the post-event processing may begin.
  • the post-event processing may occur for a predetermined duration. In many examples, the duration time for post-event processing begins when the event ends.
  • the duration may be configurable by the Event Host. Typically, the Event Host may configure the duration from one (1) hour to twenty four (24) hours. In another example, the event host may configure the post-processing time to be zero time, such that no post-processing time is allowed for that event.
  • the users of the event participant mobile devices 120A may review the photos that they took of the event. Based on the review, the users may indicate to the system 100 whether the photos that they took should be included in or removed from association with the event.
  • the event participant 120A may decide to remove image 120A1 from association with the event. Accordingly, the mobile device 120 A may send a message to the event server 155 to remove the image 120A1 from association with the event in the event content metadata store 175. Thus, the photo may no longer be related to the event in the system 100. Notably, however, the image 120A1 may not be removed from the content data store 170. This accordingly allows the user of the event participant mobile device 120 A to keep the image 120A1 in storage for private viewing and access, but without sharing the image with other participants to the event.
  • the event server 155 may be configured to direct the mobile devices 120 of the other participants to delete the preview image 120A1.
  • the preview image 120A1 may be removed from the event participant mobile device 120B. Thu, the post-processing removal of the image 120A1 removes the preview image 120A1 from the mobile device 120B, and removes access to the image 120A1 in any form from the mobile device 120B, or other access means.
  • the event participant mobile device 120B reviews the photos and decides not to remove any of the images taken by the mobile device 120B.
  • the image 120B1 is not removed from association with the event.
  • the post-processing period closes.
  • the mobile devices 120 may upload the full resolution images to the content data store 170. Once uploaded, the full resolution images associated with the event may be available to the event participant mobile devices 120A, 120B, etc.
  • FIG. 15 is an example of front-row feature for a social event system 100.
  • the front- row feature enables event participants to utilize their mobile devices 120 to select photographs that have been designated as "front row seats" at an event.
  • front row seats implies that the seats are in fact in the front row
  • the front-row feature may be used to gather the best photos, regardless of the location within the venue or event. However, it is expected that photograph locations closer to performers will be the best photos.
  • the front-row feature may utilize a database compilation technique that refines the best seats at the venue (e.g., the "best seats in the house") at a particular event. This can be done by collecting the participant's information and interactions with the social event system 100 along with the popularity of the photographs for that location that have been designated as front row seats.
  • a data field in the mobile application 125 may be provided for participants to self- designate themselves as front row photographers.
  • the social event system 100 utilizes location technology (e.g., geospatial GPS and Bluetooth) technology to determine and/or define the sections of the event that have been designated as front row seats by the event participants. Following an additional social event at the same location, the social event system 100 may utilize the front row data from both events to verify front row seats as "section verified" for those seats that are designated as front row seats in both events.
  • the social event system 100 may gather more data and provide a more refined front row designation with each event, as participants designate their front row seats and contribute photographs which are then shared by other participants. As an example, the more photographs that are downloaded for a designated front row seat, the more accurate the social event system 100 becomes to identify the best front row seats.
  • the social event system 100 may require a threshold of front row identified participants before designating the seat locations as a "section verified" front row seat.
  • the threshold may be set to a minimum of two events with designated front row participants for an event location to have "section verified" front row seats.
  • the social event system 100 may automatically assign participant mobile devices 120 to with front row seat designations if the mobile devices 120 are at "section verified” locations.
  • participant mobile devices 120 When automatic "section verified” is used, participants no longer need to self-designate as a front row photographer.
  • the social event system 100 automatically shares the participant's photographs as front row while they are at a "section verified” location.
  • the social event system 100 continues to track the number of photographs selected and downloaded in the front row section to refine the best seats at each particular event location.
  • the social event system 100 participant is advised on their mobile application 125 that they have a front row seat upon login and/or arrival to the event. Professional photographers may find this feature useful in that they will be sharing their photographs in this manner and can decide if such photographs are watermarked and being sold through an e-commerce solution (e.g., e-commerce system 185, etc.).
  • e-commerce solution e.g., e-commerce system 185, etc.
  • Photographs taken by event participant mobile devices 120 that are front row may be provided with preferential treatment.
  • the photographs taken by event participant mobile devices 120 that are front row may be the emphasized in the user interface of the mobile device 120.
  • front row photographs may be displayed first in a listing of event photos, or may be displayed in a highlighted manner in a list of event photos.
  • the social event system 100 may also make APIs available to allow access to the front row data for other purposes not having to do with event photography.
  • An API can provide immediate access to the geospatial data defining any mobile application 125 that is in a front row seat and integrate that with other software applications or systems (such as booking or ticket purchase systems).
  • three participants 38495, 47395, and 48393 to a first social event at the "Road House Concert Hall" venue use the mobile application 125 to self-designate that they are located within a section of front row seats.
  • the self-designations and associated locations are stored 1202 in the data center 150 in a repository including front row unverified locations when they are received by the event server 155.
  • the event server 155 may verify 1204 front row seats as "section verified” for those seats that are designated as front row seats in both the original event and in the further event or events. Additionally or optionally, the social event system 100 may utilize photograph download statistics for the users at the front row seats or other information such as front row self- designations at additional events to refine 1206 the designations of which sections of the "Road House Concert Hall” venue are front row. These designations of front row event locations may be stored 1208 in the data center 150 in a repository including front row verified locations.
  • the event server 155 may further utilize the services of a compiled event locations database 1210 to provide verified location information with respect to the names of the venues or other locations of the front row events.
  • the event server 155 may utilize a verified global spatial directory, such as the one discussed above with respect to the illustration 1300, in combination with information regarding current events and associated locations, as inputs to confirm which geographic locations (e.g., GPS coordinates, Bluetooth location data, etc.) of sections of a venue are verified as being front row.
  • the event server 155 may push a notification to the mobile devices 120 of the event participants that are located within the front row locations, to inform them that they are in section verified front row locations.
  • the notifications may be received by the participants 38495, 47395, and 48393.
  • These participants may accordingly be automatically identified by the system as front row, without requiring the participants to perform self-designation as front row. If any photos are taken by those front row participants, the social event system 100 may automatically shares those photographs as front row if they are taken while the participant devices are indicated as being at the front row locations.
  • the social event system 100 may be used for multiple other purposes.
  • the social event system 100 may be used as a notification service for when participants arrive.
  • the event host and other participants at the location may be notified as participants arrive.
  • participants that have not yet arrived may be configured to view who is at the event, and who is not.
  • the social event system 100 may be used for corporate document sharing. For example, where employees are at an event (e.g., a meeting), they may automatically be enabled to share documents by the social event system 100. In this way, the social event system 100 provides a platform for sharing information and documenting attendance.
  • the social event system 100 may be used to enhance finding like- minded people.
  • participants may have profiles that describe themselves and people they may want to meet. If profiles match, they may be notified of each other's presence at an event.
  • the social event system 100 provides a platform for communication and sharing. This may be in the form of digital documents (e.g., photos), include messaging between participants (and the messaging may be related to a document), and providing notification and scheduling services.
  • digital documents e.g., photos
  • the messaging may be related to a document
  • events described herein are shown in simplistic form as a single location. However, it is possible to have an event that includes multiple locations globally. Moreover, more than one event may be active at the same location.
  • Computing devices such as those discussed herein generally each include instructions executable by one or more computing devices such as those identified above, and for carrying out blocks or steps of processes described above.
  • process blocks discussed above may be embodied as computer-executable instructions.
  • Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, JavaTM, C, C++, Visual Basic, Java Script, Perl, HTML, etc.
  • a processor e.g., a microprocessor
  • receives instructions e.g., from a memory, a computer-readable medium, etc.
  • executes these instructions thereby performing one or more processes, including one or more of the processes described herein.
  • Such instructions and other data may be stored and transmitted using a variety of computer- readable media.
  • a file in a computing device is generally a collection of data stored on a computer readable medium, such as a storage medium, a random access memory, etc.
  • a computer-readable medium includes any medium that participates in providing data (e.g., instructions), which may be read by a computer. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media, etc.
  • Non-volatile media include, for example, optical or magnetic disks and other persistent memory.
  • Volatile media include dynamic random access memory (DRAM), which typically constitutes a main memory.
  • DRAM dynamic random access memory
  • Computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any other medium from which a computer can read.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un serveur d'événements qui peut identifier un groupe d'utilisateurs du système d'événement social qui sont socialement reliés les uns aux autres; et fournir automatiquement une recommandation au groupe des utilisateurs pour être des participants d'événement à un événement photo social, l'événement photo social étant défini en fonction d'un ou plusieurs critères choisis parmi une proximité géographique, une proximité temporelle et le groupe d'utilisateurs. Un dispositif mobile peut envoyer des informations de localisation à un serveur d'événements du système d'événement social; et recevoir, depuis le serveur d'événements en réponse à l'identification de l'utilisateur du dispositif mobile comme faisant partie d'un groupe d'utilisateurs du système d'événement social qui sont reliés socialement les uns aux autres, une recommandation pour adhérer à un événement photo social défini selon un ou plusieurs critères choisis parmi une proximité géographique, une proximité temporelle et le groupe d'utilisateurs.
PCT/US2014/062193 2013-10-25 2014-10-24 Système d'événement social WO2015061696A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201361896000P 2013-10-25 2013-10-25
US61/896,000 2013-10-25
US201461983457P 2014-04-24 2014-04-24
US61/983,457 2014-04-24

Publications (1)

Publication Number Publication Date
WO2015061696A1 true WO2015061696A1 (fr) 2015-04-30

Family

ID=52993624

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/062193 WO2015061696A1 (fr) 2013-10-25 2014-10-24 Système d'événement social

Country Status (1)

Country Link
WO (1) WO2015061696A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089379A1 (fr) * 2016-11-14 2018-05-17 Leyefe, Inc. Systèmes et procédés de gestion de données d'image sensibles au temps pour enrichir des événements sociaux
WO2019028531A1 (fr) * 2017-08-11 2019-02-14 Hooga Holdings Pty Ltd Gestion et archivage d'images et de messages pour événements
WO2020077573A1 (fr) * 2018-10-17 2020-04-23 Alibaba Group Holding Limited Partage de secret sans initialiseur de confiance
EP3603087A4 (fr) * 2017-03-31 2020-09-16 XO Group Inc. Procédés et appareil de diffusion multimédia dynamique sur la base d'une localisation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110064281A1 (en) * 2009-09-15 2011-03-17 Mediatek Inc. Picture sharing methods for a portable device
US20110251972A1 (en) * 2008-12-24 2011-10-13 Martin Francisco J Sporting event image capture, processing and publication
US20120250950A1 (en) * 2011-03-29 2012-10-04 Phaedra Papakipos Face Recognition Based on Spatial and Temporal Proximity
US20130013683A1 (en) * 2011-07-07 2013-01-10 Max Elliott Auto-creating groups for sharing photos

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110251972A1 (en) * 2008-12-24 2011-10-13 Martin Francisco J Sporting event image capture, processing and publication
US20110064281A1 (en) * 2009-09-15 2011-03-17 Mediatek Inc. Picture sharing methods for a portable device
US20120250950A1 (en) * 2011-03-29 2012-10-04 Phaedra Papakipos Face Recognition Based on Spatial and Temporal Proximity
US20130013683A1 (en) * 2011-07-07 2013-01-10 Max Elliott Auto-creating groups for sharing photos

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089379A1 (fr) * 2016-11-14 2018-05-17 Leyefe, Inc. Systèmes et procédés de gestion de données d'image sensibles au temps pour enrichir des événements sociaux
EP3603087A4 (fr) * 2017-03-31 2020-09-16 XO Group Inc. Procédés et appareil de diffusion multimédia dynamique sur la base d'une localisation
WO2019028531A1 (fr) * 2017-08-11 2019-02-14 Hooga Holdings Pty Ltd Gestion et archivage d'images et de messages pour événements
US11531776B2 (en) 2017-08-11 2022-12-20 Hooga Holdings Pty Ltd Image and message management and archiving for events
WO2020077573A1 (fr) * 2018-10-17 2020-04-23 Alibaba Group Holding Limited Partage de secret sans initialiseur de confiance
US11386212B2 (en) 2018-10-17 2022-07-12 Advanced New Technologies Co., Ltd. Secure multi-party computation with no trusted initializer

Similar Documents

Publication Publication Date Title
US11405348B2 (en) Managing an ephemeral post in a social networking system
KR101879619B1 (ko) 콘텐츠 항목의 저장
US9130763B2 (en) Automatic sharing of event content by linking devices
US20180351895A1 (en) In the event of selection of message, invoking camera to enabling to capture media and relating, attaching, integrating, overlay message with/on/in captured media and send to message sender
CN107710197B (zh) 在通信网络上共享图像和图像相册
US10582037B2 (en) Two-way permission-based directory of contacts
JP6311030B2 (ja) 共有仮想空間を生成するためのシステム及び方法
US9307047B2 (en) System and method for communication of an event through a call for media
JP4668200B2 (ja) 通信ネットワークを介してデジタル画像を自動的に共有する方法及びそのシステム
US20170127128A1 (en) Social Post Roll Up and Management System and Method of Use
US9342817B2 (en) Auto-creating groups for sharing photos
US20170118165A1 (en) System and method for controlled sharing and synchronizing information across a plurality of mobile client application computers
US20150356121A1 (en) Position location-enabled, event-based, photo sharing software and service
US9531823B1 (en) Processes for generating content sharing recommendations based on user feedback data
US20160050289A1 (en) Automatic sharing of digital content
US9405964B1 (en) Processes for generating content sharing recommendations based on image content analysis
US20150261813A1 (en) Method to form a social group for a real time event
US10397322B2 (en) Mobile and computer applications, systems and methods for large group travel and event management
US20150358390A1 (en) Method and system to share visual content across a plurality of mobile devices to generate interest, support and funding for philanthropic and for social causes
US20200104092A1 (en) Group Slideshow
WO2015061696A1 (fr) Système d'événement social
JP2016163236A (ja) 撮影装置、撮影方法および撮影プログラム
WO2020001648A1 (fr) Procédé et appareil de traitement d'image et dispositif terminal
US20190141488A1 (en) Systems and methods for ad-hoc trigger based data sharing group
JP5965504B1 (ja) 情報提供装置、情報提供方法および情報提供プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14856295

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23.09.2016)

122 Ep: pct application non-entry in european phase

Ref document number: 14856295

Country of ref document: EP

Kind code of ref document: A1