WO2013188682A1 - Partage d'informations avec d'autres utilisateurs - Google Patents

Partage d'informations avec d'autres utilisateurs Download PDF

Info

Publication number
WO2013188682A1
WO2013188682A1 PCT/US2013/045694 US2013045694W WO2013188682A1 WO 2013188682 A1 WO2013188682 A1 WO 2013188682A1 US 2013045694 W US2013045694 W US 2013045694W WO 2013188682 A1 WO2013188682 A1 WO 2013188682A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
users
subset
data items
information
Prior art date
Application number
PCT/US2013/045694
Other languages
English (en)
Inventor
Andrew G. Huibers
David F. Lieb
Kevin N. GABAYAN
Seth T. RAPHAEL
Original Assignee
Google Inc
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 Google Inc filed Critical Google Inc
Publication of WO2013188682A1 publication Critical patent/WO2013188682A1/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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • This disclosure relates to communication devices. Sharing information with other users (e.g., via a smartphone) is often time consuming and cumbersome. Therefore, what are needed are methods and systems for facilitating sharing information with other users.
  • An embodiment can receive a set of data items that is to be analyzed for sharing. Next, the embodiment can analyze the set of data items based on a first set of criteria to obtain a subset of the set of data items that are likely candidates for sharing. The embodiment can then present the subset of the set of data items to a first user.
  • the embodiment can receive a set of users that is to be analyzed for sharing information. Next, the embodiment can analyze the set of users based on a second set of criteria to obtain a subset of the set of users with whom the information is likely to be shared. The embodiment can then present the subset of the set of users to the first user.
  • the set of data items can include, but is not limited to, photos, videos, contact information, music, or any other information that a user may want to share with other users.
  • the first set of criteria can include a time window and a spatial region.
  • analyzing the set of data items can involve determining data items that were created during the time window at a location that is within the spatial region.
  • the second set of criteria can include a time window, a spatial region, and a distance threshold in a social network.
  • analyzing the set of users can involve determining users that are within the distance threshold from the first user in the social network and whose locations were within the spatial region during the time window.
  • the subset of the set of data items and the subset of the set of users are presented together to the first user. Additionally, these embodiments can present a first set of user interface elements to the first user to enable the first user to modify the subset of the set of data items, and present a second set of user interface elements to the first user to enable the first user to modify the subset of the set of users.
  • FIG. 1 illustrates a system in accordance with some embodiments described herein.
  • FIG. 2A presents a flowchart that illustrates a process for sharing data items in accordance with some embodiments described herein.
  • FIG. 2B-2E illustrates screenshots of a graphical user interface (GUI) of a device in accordance with some embodiments described herein.
  • GUI graphical user interface
  • FIG. 3A illustrates a process for identifying users with whom information is likely to be shared in accordance with some embodiments described herein.
  • FIG. 3B illustrates a screenshot of a GUI of a device in accordance with some embodiments described herein.
  • FIG. 4 illustrates a screenshot of a GUI of a device in accordance with some embodiments described herein.
  • FIG. 5 illustrates a computer in accordance with some embodiments described herein.
  • FIG. 6 illustrates an apparatus in accordance with some embodiments described herein.
  • non-transitory storage medium which may be any tangible device or medium that can store code and/or data for use by a computer system.
  • a non-transitory storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other tangible media, now known or later developed, that is capable of storing information.
  • the methods and processes described in this disclosure can be embodied as code and/or data, which can be stored in a non-transitory storage medium as described above.
  • a computer system reads and executes the code and/or data stored on the non-transitory storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the non-transitory storage medium.
  • the methods and processes described below can be included in hardware modules.
  • the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed.
  • ASIC application-specific integrated circuit
  • FPGAs field programmable gate arrays
  • the hardware modules When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.
  • Some embodiments help a user to automatically identify information and other users who may be interested in the information that the device user may want to share. For example, if a person goes on a hike with friends and family, then some embodiments
  • a software application executes on a computing platform and keeps track of information that is being created (e.g., photos that were taken and/or videos that were recorded since the last time the user shared information with other people), and creates a list of recipients with whom the user is likely to share the information. The software application can then present the user with the list of recipients, and allow the user to
  • the software application may take whatever action the user instructs the application to take.
  • the user may define rules that specify the action that the user wants the software application to take when the user identifies a particular list of recipients.
  • the software application registers with the operating system on the computing platform, and requests the operating system to activate the software application when certain conditions occur.
  • the software application may provide a set of conditions which, when they occur, indicate that the user may be interested in sharing information with other users.
  • the software application may request the operating system to activate the software application when the user moves more than a pre-determined distance from his/her previous location (e.g., 500 meters).
  • the software application can collect information (e.g., photos, videos, notes, etc.) that were generated since the last time the software application was activated. Next, the software application can determine whether there is anything in the collected information that the user may want to share with other users. If the software application determines that there is such information, the software application can present the user with the information and a list of recipients. The user can then decide whether and whom to send the information.
  • information e.g., photos, videos, notes, etc.
  • the list of recipients can be automatically determined by the software application based on data associated with the collected information.
  • Data associated with the collected information can include a geotag, a fingerprint (e.g., a fingerprint of an audio or video clip), a hash value, file metadata (e.g., author's name, file creation date, date when the file was last modified, title of the file, etc.), a face identifier (e.g., by using a face recognition process that associates one or more face identifiers with a photo), etc.
  • a geotag e.g., a fingerprint of an audio or video clip
  • file metadata e.g., author's name, file creation date, date when the file was last modified, title of the file, etc.
  • face identifier e.g., by using a face recognition process that associates one or more face identifiers with a photo
  • the software application may execute a set of rules to automatically generate a list of recipients based on the geotag.
  • historical information can be analyzed to identify a correspondence between content and recipients. For example, historical information can be analyzed to identify a correspondence between photos that were taken at an elementary school and a person (e.g., the user's mother) to whom these photos were sent. Based on such analysis, a set of rules can be determined. The software application may then use such rules to automatically create a list of recipients for the collected information.
  • the software application executes on a handheld device.
  • the software application may send only the metadata (e.g., location and time information or any other information that can be quickly generated based on the computing and bandwidth resources on the handheld device) associated with the photo/video to a server.
  • the server can then determine a list of recipients with whom the user is likely to share the information, and send the list to the handheld device.
  • the handheld device can then display the list of recipients to the user, and perform any actions that the user instructs the handheld to perform with regard to sharing the information.
  • the software application identifies content that was generated by the user based on metadata associated with the content.
  • a handheld device may contain a set of photos that include photos that were generated by the user, as well as photos that were received from other sources (e.g., downloaded from a website, received from a friend, etc.).
  • the handheld device i.e., a software application that is executing on the handheld device
  • may use the metadata e.g., the model of the camera that was used for taking the photo
  • the handheld device may then send metadata associated with only the identified photos to the server for further processing. Once the user approves the distribution of certain information (e.g., photos), only then is the information sent to the server so that the information can be distributed or shared between the identified users.
  • FIG. 1 illustrates a system in accordance with some embodiments described herein.
  • Devices 104-110 can communicate with each other and/or with server 102 via network 112.
  • a device e.g., devices 104-110) can generally be any hardware-based device, now known or later developed, that is capable of communicating with other devices. Examples of devices can include, but are not limited to, desktop computers, laptop computers, handheld computing devices, tablet computing devices, smartphones, automatic teller machines, point of sale systems, etc.
  • the device when the device detects information that the user may want to share with other users, the device can execute a series of processor instructions that cause the device to collect information that the user is likely to share with other users, and present the collected information to the user.
  • the device can also automatically determine a list of other users with whom to share the collected information and present the list to the user.
  • the device can use the time and location information to determine whether a user is likely to share a particular item of content with other users.
  • Network 112 can generally include any type of wired or wireless communication channel, now known or later developed, that enables two or more devices to communicate with one another.
  • Network 112 can include, but is not limited to, a local area network, a wide area network, or a combination of networks.
  • Server 102 can generally be any system that is capable of performing computations and that is capable of communicating with other devices.
  • Server 102 can be a computer system, a distributed system, a system based on cloud computing, or any other system, now known or later developed, that is capable of performing computations.
  • a device can send a message to a server.
  • device 106 can send message 114 to server 102 through network 112.
  • server 102 can send message 116 to device 106.
  • the reverse sequence of operations is also possible, i.e., the server first sends a message to a device and then the device responds with a message.
  • the message may be sent only one way (i.e., either from the device to the server or from the server to the device) without requiring that a corresponding message be sent in the reverse direction.
  • the term "message” generally refers to a group of bits that are used for conveying information.
  • a message can be a series of bits.
  • a message can include one or more units of data, e.g., one or more packets, cells, or frames.
  • FIG. 2A illustrates a process for identifying information that a user may want to share with other users in accordance with some embodiments described herein.
  • the process can begin with receiving a set of data items that is to be analyzed for sharing (operation 202).
  • the set of data items can be analyzed based on a set of criteria to obtain a subset of the set of data items that is a likely candidate for sharing (operation 204).
  • the process can then present the subset of the set of data items to a user (operation 206).
  • the set of criteria can include a time window and a spatial region.
  • analyzing the set of data items can involve determining data items that were created during the time window at a location that is within the spatial region.
  • the information that is considered for sharing may originate from a device, camera, application, or any other source that is capable of generating shareable information.
  • certain types of information e.g., based on the file extension
  • the information on the handheld device can be grouped into events (at a single level of granularity or at multiple hierarchical levels of granularity) based on the metadata associated with the information. For example, the time and location information associated with photos can be used to group photos into events. Once the information has been grouped into distinct events, a set of co-proximate users can be determined for each event. [0033] FIG.
  • 2B-2E illustrates screenshots of a GUI 250 of a device in accordance with some embodiments described herein.
  • the set of photos on a device has been selected as the set of data items that are to be analyzed for sharing, and the set of criteria that is used to determine a subset of the set of data items is a set of friends who use an application for sharing information and who were co-proximate with the user.
  • FIG. 2B illustrates a screenshot that shows an executing application for sharing information with other users, wherein the executing application is searching for friends of the user who also use the application.
  • FIG. 2C illustrates a screenshot after the executing application has determined that two friends also use the application.
  • FIG. 2C also illustrates that the executing application is now searching for the photos that are likely candidates to be shared with the two friends.
  • FIG. 2D illustrates that the application has found six photos so far that were taken while one or both friends were co-proximate with the user.
  • FIG. 2E illustrates the subset of the set of photos that was identified as a likely candidate for sharing. Determining a set of users with whom to share information
  • FIG. 3A illustrates a process for identifying users with whom information is likely to be shared in accordance with some embodiments described herein.
  • the process can begin with receiving a set of users that is to be analyzed for sharing information (operation 302).
  • the set of users can be analyzed based on a set of criteria to obtain a subset of the set of users with whom the information is likely to be shared (operation 304).
  • the process can then present the subset of the set of users (operation 306).
  • the set of criteria can include a time window, a spatial region, and a distance threshold in a social network.
  • analyzing the set of users can involve determining users that are within the distance threshold from the first user in the social network and who were within the spatial region during the time window.
  • two users are co-proximate to each other if the two users are within a given spatial region during a given time window.
  • a social network can be viewed as a network of vertices, wherein each vertex represents a social entity, e.g., a person, a company, etc.
  • An edge between two vertices can represent a direct relationship (e.g., a "friend" relationship) between the entities that correspond to the two vertices.
  • a distance between two vertices in a social network can be defined as the number of edges in a shortest path between the two vertices in the social network.
  • a distance threshold can specify the maximum distance that is allowed between a given user and another user in the social network.
  • a distance threshold can be used to specify a subset of the set of users in the social network. For example, if the distance threshold is equal to "1," then only a user's friends would be in the subset because only the user's friends are within a distance threshold of "1" from the user.
  • the distance threshold is equal to "2”
  • all of the user's friends, and also the friends of the user's friends would be in the subset because all of the user's friends, and also the friends of the user's friends are within a distance threshold of "2" from the user.
  • FIG. 3B illustrates a screenshot of a GUI 350 of a device in accordance with some embodiments described herein. Specifically, the screenshot illustrates a subset of a set of data items, namely, photos 352, and a subset of a set of users, namely attendees 354.
  • the application has determined that photos 352 are likely to be shared with attendees 354.
  • the device can then provide the user with user interface (UI) elements, e.g., UI elements 356 and 358, to change the subset of the set of photos and/or attendees.
  • UI user interface
  • the system determines a set of co-proximate users that a person is likely to share information with. For example, an embodiment can begin with the list of friends that user u ⁇ has on a social networking website. Next, the embodiment can filter out the friends that were not around the same place and time as user u ⁇ when user u ⁇ took a photo. The embodiment can then prompt user u ⁇ with the remaining list of friends. Once user u ⁇ identifies the friends with whom u ⁇ wants to share the information, the embodiment can share the information with the identified friends. This example was provided for illustration purposes only. In general, embodiments can use an arbitrarily complex filter to determine the set of users with whom to share information.
  • two users are co-proximate to one another if they are around the same location around the same time.
  • the location and time ranges that are used for determining co-proximity can depend on a number of factors, including, but not limited to, the accuracy of the location/time information, the probability that a given set of users are friends, etc.
  • any information that was generated by any of the people can become available to the other people present.
  • Each person can determine whether or not to share the information with other people, e.g., the permission can be granted by a user per photo, per event, and/or per co-proximate user.
  • Co-proximity can be determined from location information (longitude latitude) associated with the information that is being shared (e.g., the photo) and the timestamp associated with the information that is being shared, and/or any other metadata associated with the information.
  • location information longitude latitude
  • the co-proximity can be determined from location information (longitude latitude) contained in JPEG EXIF data.
  • the metadata is uploaded to a central server periodically without the user's explicit instructions.
  • metadata is uploaded every time information becomes available for sharing (e.g., when a photo is taken on the handheld device).
  • metadata is uploaded whenever the user changes location by more than a pre-determined distance.
  • co-proximity is determined from mobile device location data collected by an application running on the user's device.
  • co-proximity can be viewed as an arbitrarily complex filter that uses information from multiple sources to determine a set of co-proximate users.
  • co- location duration is used to determine actual co-proximity, i.e., co-proximity between two users is inferred if the two users spend more than a threshold amount of time in proximity to each other.
  • the device's velocity is used to determine actual co- proximity. For example, if the velocities of two different devices match over a given time period, then these two devices can be considered to be co-proximate. This can help prevent situations where a person is driving on a highway and the system determines that another person in another vehicle is co-proximate when actually the other person is not co-proximate to this user.
  • a hardware identifier e.g., a freeform alphanumeric field that corresponds to a device model and/or a hardware manufacturer
  • a software identifier e.g., a freeform alphanumeric field that corresponds to a software type, implementation, vendor, and/or version
  • a network address e.g., an IP or Ethernet address
  • a carrier identifier e.g., a field that indicates a communication company whose network the device is using
  • a network identifier e.g., an identifier (e.g., the SSID of a WiFi network) that corresponds to the communication network that the device is using
  • the hardware and/or software identifier can be used to signal the accuracy of the time/location information that is used in the co-proximate filter. If it is more likely that co-proximate users have the same type of hardware and/or software, then this information can be used in the co- proximate filter. Similarly, the carrier identifier or the network identifier can also be used in the co-proximate filter. Theses uses of the hardware identifiers, software identifiers, carrier identifiers, and network identifiers have been presented for illustration purposes only and are not intended to limit the scope of the embodiments described herein.
  • the metadata update may include a network address, e.g., an IP or Ethernet address.
  • Some address spaces are hierarchical, e.g., the IP address space is hierarchical.
  • the probability that two devices are co-proximate may be greater if the corresponding network addresses are closely related in the address space hierarchy (e.g., if the two network addresses belong to the same subnet). Therefore, the network address information can also be used as one of the parameters in the co-proximate filter.
  • a useful factor that can be used in the co-proximate filter is the relationship between two users in a social network.
  • Distance between two users is one of many metrics that can be used to determine the strength of the relationship between two users.
  • Another relationship metric can be based on the type and/or amount of communication between the two users. For example, the system may determine that the two users are closely related in the social network if the two users often exchange messages and/or posts on a social network website. Regardless of how the relationship strength between two users is determined, the co- proximate filter can use the relationship strength information to determine whether or not two users should be considered to be co-proximate.
  • the co-proximate filter may use a list of locations of the device over a given time period. If it is expected that users who have visited the same location(s) over a given time period are more likely to be co-proximate, then this information can be used by the filter.
  • the co-proximate filter may use an ambient temperature and/or sound recording that was recorded at a particular time.
  • the ambient temperature and/or sound recording may be used to complement or supplement the temporal and spatial information. For example, if the temporal and spatial information from two devices indicates that the two devices are coincident in time and space, the ambient temperature information and/or sound recording can be used to validate this conclusion.
  • the co-proximate filter may use one or more phone numbers (e.g., the device's phone number and/or phone numbers associated with the owner of the device) stored on the device. If it is expected that users who wish to exchange information with one another are likely to have each other's phone numbers stored on their devices and/or have common phone numbers stored on their devices, then this information can be used to determine the set of co-proximate users.
  • phone numbers e.g., the device's phone number and/or phone numbers associated with the owner of the device
  • the co-proximate filter can have a learning component.
  • the device can prompt user ul with the information and the list of co-proximate users.
  • the embodiment may modify the filter. For example, if a user removes certain users from the list, then the embodiment can modify the filter so that those users would be less likely to be selected as co-proximate users in the future.
  • the location information associated with a user or with a data item can be generated using a number of techniques.
  • a Global Positioning System (GPS) receiver can be used to determine the location.
  • Location can also be determined based on triangulating signals from multiple cell phone towers.
  • location information can also be received from a social networking application. For example, if a user posts a message or "checks in” at a store using an application, the location information associated with the message or with the "check in” operation can be used to determine the location of the user.
  • a user tagged in a photograph that has location and time information, then that can also be used to determine location and time information for the user.
  • the location information can be inferred based on the location information of another event that occurred recently. For example, the location of the handheld device is known a few minutes before the photo was taken or a few minutes after the photo was taken, then the location of the photo can be inferred based on the location of the device at a slightly different time. Modifications and variations
  • FIG. 4 illustrates a screenshot of a GUI 400 of a device in accordance with some embodiments described herein.
  • a set of photos that relate to an event that occurred on a particular night were shared between the device's owner and 23 other friends.
  • a discussion thread was then automatically created to enable the users to discuss the event.
  • two users named "Lindsey Sunden” and "Bernardo Nunez” have posted comments that related to the event.
  • a shared storage location can be created automatically for an event so that data items associated with the event can be uploaded to, and accessed from, the shared storage location by users who are associated with the event. For example, once the sharing software application determines that a group of friends were at an event (e.g., by using a co-proximate filter), the software application can create an album for that event, identify photos for each user in the group, and prompt each user in the group to upload their photos for the event to the album. The photos that a user uploads to the album can then be shared either with everyone present at the event, or with only the user's friends who were present at the event, or with a subset of the user's friends who were present at the event.
  • this sharing process is not limited to photos. Any type of information may be shared in this manner.
  • the sharing software application may automatically create a "contact album," and prompt each of the attendees to upload their contact information to the album to facilitate exchanging business contact information between the attendees.
  • the number of users with whom information is shared can be one or more, e.g., in the embodiments that automatically create an album, the album can have one or more users. For example, if only two people, e.g., users u ⁇ and u2, are present at an event, then the software application can prompt user u ⁇ to create an album, and share information with user u2 via the album.
  • Some embodiments can keep track of the sharing behavior and use the sharing behavior during co-proximity computations. For example, if user u ⁇ often shares information with user u2, then the software application can use this historical sharing pattern to determine whether or not information uploaded by user u ⁇ should be shared with user u2.
  • the software application can determine a composite sharing score for each user.
  • the composite sharing score can include multiple components, such as a temporal co-proximity component, spatial co-proximity component, social network distance component, historical sharing frequency component, etc.
  • the software application may select only those users whose composite sharing score is above a given threshold. If information was often shared with a particular user, then that user's historical sharing frequency component would have a high value, thereby increasing the probability that the user will be selected as one of the users with whom information will be shared.
  • the processing can be arbitrarily divided between the handheld device and the server. For example, in some embodiments the handset determines if a photo was taken by a user (and therefore may be a candidate for sharing), or whether the photo was taken by another user (and therefore may not be a candidate for sharing). The determination of the set of co-proximate users can then occur at the server.
  • the system shares photos that originated on the device.
  • Factors that can be used to determine whether or not a photo originated on the device include the size of the photo, EXIF data, filename counter increment, etc.
  • the handheld device may not embed time and/or location information in the photo.
  • the executing software application can add the time/location information as required.
  • the location information can be made accurate based on other information that is known about the user. For example, if the location information indicates that the person is in the vicinity of his/her home, and if the person does not appear to be moving, then the application can assume that the person is at his/her home. In this example, the accuracy of the location information was significantly improved based on other information (e.g., the home address of the person).
  • Other inputs that can be used in the co-proximate filter include calendar appointments, contents of emails, etc.
  • Information that a person may want to share could include information that the person was using during an event. For example, if a user was listening to a song or looking at a map during a hike, then this information can be tagged as something that the person may want to share with other co-proximate users.
  • locations can be clustered and ranked with distance, frequency, duration, time of day, and media generation (home/work, favorite places within multiple spatial/temporal scales, etc.).
  • Some embodiments can automatically create a timeline of the user's behavior based on information including: time, location, co-proximity, media generated (photos, video), etc.
  • the recorded information can then be used to create a personal log.
  • the recorded information can be segmented into trips based on the user's geo- temporal data. Trips can be ranked as a function of distance from special locations, visit frequency, duration, and other users in co-proximity. Media recorded during any trip may be shared with other users.
  • the recorded information can be analyzed and results can be generated based on the user's behavior and co-proximity.
  • the analytics can help a user determine his/her pattern of commute, work, and home activities. Friends within co-proximity can be ranked by proximity duration. The places that a person visits can be ranked by self-generated and other-labeled behavior metrics. Badges can be awarded based on improvement in a user's behavioral metrics and/or based on comparing the user's metrics with metrics of other users.
  • the type of content that selected for sharing and the set of co-proximate users can depend on a variety of factors including, the content of the information itself (e.g., is it a photo of a person, an animal, a building, etc.), the location (e.g., is was the photo taken at home, work, vacation, bar, etc.), the time of day (e.g., photos taken during work hours are more likely to be shared with colleagues), camera type, the list of co-proximate users (e.g., the person(s) whom you are with - e.g., family, friends, co-workers, etc.).
  • the location information can be inferred from events in your calendar, events in a social networking website, tagged photos, locations of credit card purchases.
  • Frequency of co-location can be used to determine friend strength and/or to generate new social network graph ("co-proximate buddies"). If we have raw access to handset MAC address (network interface unique ID) and signal strength of a WiFi or Bluetooth signal, we can potentially determine relative location/closeness (as opposed to absolute location which is what a GPS receiver determines). An unusual activity may trigger photo taking suggestion (unusual activity may include co-proximity to a new place and/or new people).
  • Some embodiments described herein can be used to determine user-oriented views of events. In these embodiments, there is no canonical album. Instead, everyone has their own “lens" into the event. The co-proximate information can be used to highlight the people who are important to you.
  • FIG. 5 illustrates a computer in accordance with some embodiments described herein.
  • a computer can generally refer to any hardware apparatus that is capable of performing computations.
  • devices 104-110 and server 102 shown in FIG. 1 can each be a computer.
  • computer 502 can include processor 504, memory 506, user interface 510, sensors 512, communication interfaces 514, storage 508, microphone 522, and speaker 524.
  • User interface 510 can generally include one or more input/output mechanisms for communicating with a user (e.g., a keypad, a touchscreen, a microphone, a speaker, a display, etc.).
  • Sensors 512 can include one or more inertial sensors (e.g., accelerometer, gyroscope, etc.) and/or other types of sensors (e.g., light meters, pressure gauges, thermometers, etc.).
  • Communication interfaces 514 can generally include one or more mechanisms for communicating with other computers (e.g., Universal Serial Bus interfaces, network interfaces, wireless interfaces, etc.).
  • Storage 508 may be a non-transitory storage medium, and may generally store instructions that, when loaded into memory 506 and executed by processor 504, cause computer 502 to perform one or more processes for facilitating communication with another computer.
  • storage 508 may include applications 516, operating system 518, and data 520.
  • Applications 516 may include software instructions that implement, either wholly or partly, one or more methods and/or processes that are implicitly and/or explicitly described in this disclosure.
  • Computer 502 has been presented for illustration purposes only. Many
  • computer 502 may include a different set of components than those shown in FIG. 5.
  • FIG. 6 illustrates an apparatus in accordance with some embodiments described herein.
  • Apparatus 602 can comprise a number of hardware mechanisms, which may
  • a hardware mechanism can generally be any piece of hardware that is designed to perform one or more actions.
  • a sending mechanism can refer to transmitter circuitry
  • a receiving mechanism can refer to receiver circuitry.
  • apparatus 602 can include content identifying mechanism 604, user identifying mechanism 606, receiving mechanism 608, sending mechanism 610, displaying mechanism 612, and user interface mechanism 614.
  • the apparatus shown in FIG. 6 is for illustration purposes only. Many modifications and variations will be apparent to practitioners having ordinary skill in the art. Specifically, apparatus 602 may include a different set of mechanisms than those shown in FIG. 6. Apparatus 602 can be capable of performing one or more methods and/or processes that are implicitly or explicitly described in this disclosure.
  • content identifying mechanism 604 is capable of identifying content that is likely to be shared with a set of users
  • user identifying mechanism 606 is capable of identifying a set of users with whom the identified content is likely to be shared
  • receiving mechanism 608 is capable of receiving information from other computers
  • sending mechanism 610 is capable of sending information to other computers
  • user interface mechanism 612 is capable of receiving input from a user and providing information to a user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne des systèmes et des techniques pour faciliter le partage des informations. Certains modes de réalisation peuvent recevoir un ensemble d'éléments de données qui doit être analysé pour le partage, analyser l'ensemble d'éléments de données en fonction d'un premier ensemble de critères pour obtenir un sous-ensemble de l'ensemble d'éléments de données qui est un candidat probable pour le partage, et présenter le sous-ensemble de l'ensemble d'éléments de données à un premier utilisateur. De plus, certains modes de réalisation peuvent recevoir un ensemble d'utilisateurs qui doit être analysé pour le partage des informations, analyser l'ensemble d'utilisateurs en fonction d'un second ensemble de critères pour obtenir un sous-ensemble de l'ensemble d'utilisateurs avec lequel les informations sont susceptibles d'être partagées, et présenter le sous-ensemble de l'ensemble d'utilisateurs au premier utilisateur.
PCT/US2013/045694 2012-06-13 2013-06-13 Partage d'informations avec d'autres utilisateurs WO2013188682A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201261659305P 2012-06-13 2012-06-13
US61/659,305 2012-06-13

Publications (1)

Publication Number Publication Date
WO2013188682A1 true WO2013188682A1 (fr) 2013-12-19

Family

ID=49758722

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/045694 WO2013188682A1 (fr) 2012-06-13 2013-06-13 Partage d'informations avec d'autres utilisateurs

Country Status (1)

Country Link
WO (1) WO2013188682A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3097704A4 (fr) * 2014-01-23 2017-03-22 Google, Inc. Détermination de données associées à des dispositifs informatiques proches
US10409858B2 (en) 2013-08-02 2019-09-10 Shoto, Inc. Discovery and sharing of photos between devices
WO2022160993A1 (fr) * 2021-01-28 2022-08-04 花瓣云科技有限公司 Procédé et dispositif de partage de données multimédias

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090234876A1 (en) * 2008-03-14 2009-09-17 Timothy Schigel Systems and methods for content sharing
US20100293198A1 (en) * 2009-05-12 2010-11-18 Marinucci Joseph L Mobile photo sharing
US20110211737A1 (en) * 2010-03-01 2011-09-01 Microsoft Corporation Event Matching in Social Networks
US8046411B2 (en) * 2006-04-28 2011-10-25 Yahoo! Inc. Multimedia sharing in social networks for mobile devices
US20120027256A1 (en) * 2010-07-27 2012-02-02 Google Inc. Automatic Media Sharing Via Shutter Click

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8046411B2 (en) * 2006-04-28 2011-10-25 Yahoo! Inc. Multimedia sharing in social networks for mobile devices
US20090234876A1 (en) * 2008-03-14 2009-09-17 Timothy Schigel Systems and methods for content sharing
US20100293198A1 (en) * 2009-05-12 2010-11-18 Marinucci Joseph L Mobile photo sharing
US20110211737A1 (en) * 2010-03-01 2011-09-01 Microsoft Corporation Event Matching in Social Networks
US20120027256A1 (en) * 2010-07-27 2012-02-02 Google Inc. Automatic Media Sharing Via Shutter Click

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10409858B2 (en) 2013-08-02 2019-09-10 Shoto, Inc. Discovery and sharing of photos between devices
EP3097704A4 (fr) * 2014-01-23 2017-03-22 Google, Inc. Détermination de données associées à des dispositifs informatiques proches
US9882996B2 (en) 2014-01-23 2018-01-30 Google Llc Determining data associated with proximate computing devices
WO2022160993A1 (fr) * 2021-01-28 2022-08-04 花瓣云科技有限公司 Procédé et dispositif de partage de données multimédias
EP4270970A4 (fr) * 2021-01-28 2024-05-29 Petal Cloud Technology Co., Ltd. Procédé et dispositif de partage de données multimédias

Similar Documents

Publication Publication Date Title
US9607024B2 (en) Sharing information with other users
US9996546B2 (en) Systems and methods for automatically disseminating content based on contextual information
CN103631851B (zh) 推荐好友的方法及其服务器和终端
US9020960B2 (en) System and method for modeling relationships between entities
US8515460B2 (en) Tagging data utilizing nearby device information
US20090150373A1 (en) System and method for synchronizing data on a network
US9413704B2 (en) Presenting messages associated with locations
US8745133B2 (en) System and method for optimizing the storage of data
US9600484B2 (en) System and method for reporting and analysis of media consumption data
KR102138184B1 (ko) 소셜 미디어 콘텐츠의 요약을 위한 메타데이터 사용
US9692812B1 (en) System and method for providing access to data objects based on proximity
US20160156628A1 (en) Automatic sharing of event content by linking devices
US20160034459A1 (en) Curating media from social connections
US20100063993A1 (en) System and method for socially aware identity manager
US20130046778A1 (en) System and method for automated service recommendations
US20110167357A1 (en) Scenario-Based Content Organization and Retrieval
US10609183B2 (en) Content sharing recommendations
US11429657B2 (en) Mobile device smart media filtering
US20140280152A1 (en) Computing system with relationship model mechanism and method of operation thereof
WO2016110203A1 (fr) Procédé et dispositif d'enregistrement de chemin de fichier et d'accès à un fichier local
US20170192965A1 (en) Method and apparatus for smart album generation
CN113544660A (zh) 用于对相关的内容标记进行识别和分组的系统和方法
CN112352233A (zh) 自动数字资产共享建议
CN109076069B (zh) 基于规则的身份广播
US20180267998A1 (en) Contextual and cognitive metadata for shared photographs

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: 13804062

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13804062

Country of ref document: EP

Kind code of ref document: A1