WO2017020484A1 - 照片共享方法和装置 - Google Patents

照片共享方法和装置 Download PDF

Info

Publication number
WO2017020484A1
WO2017020484A1 PCT/CN2015/097801 CN2015097801W WO2017020484A1 WO 2017020484 A1 WO2017020484 A1 WO 2017020484A1 CN 2015097801 W CN2015097801 W CN 2015097801W WO 2017020484 A1 WO2017020484 A1 WO 2017020484A1
Authority
WO
WIPO (PCT)
Prior art keywords
party
contact
photo
party photo
face image
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2015/097801
Other languages
English (en)
French (fr)
Inventor
张涛
陈志军
龙飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xiaomi Inc
Original Assignee
Xiaomi 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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to JP2017531947A priority Critical patent/JP6305654B2/ja
Priority to KR1020167004020A priority patent/KR101759454B1/ko
Priority to RU2016131883A priority patent/RU2654168C2/ru
Priority to MX2016005074A priority patent/MX385157B/es
Publication of WO2017020484A1 publication Critical patent/WO2017020484A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G06F16/986Document structures and storage, e.g. HTML extensions
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/107Computer-aided management of electronic mailing [e-mailing]
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/43Querying
    • G06F16/432Query formulation
    • G06F16/434Query formulation using image data, e.g. images, photos, pictures taken by a user
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/951Indexing; Web crawling techniques
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/40Business processes related to social networking or social networking services
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06VIMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V10/00Arrangements for image or video recognition or understanding
    • G06V10/20Image preprocessing
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06VIMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V20/00Scenes; Scene-specific elements
    • G06V20/30Scenes; Scene-specific elements in albums, collections or shared content, e.g. social network photos or video
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06VIMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V20/00Scenes; Scene-specific elements
    • G06V20/35Categorising the entire scene, e.g. birthday party or wedding scene
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06VIMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V40/00Recognition of biometric, human-related or animal-related patterns in image or video data
    • G06V40/10Human or animal bodies, e.g. vehicle occupants or pedestrians; Body parts, e.g. hands
    • G06V40/16Human faces, e.g. facial parts, sketches or expressions
    • G06V40/172Classification, e.g. identification
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10Multimedia information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • H04L67/306User profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14Multichannel or multilink protocols

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a photo sharing method and apparatus.
  • Intelligent terminals have become an indispensable electronic device in people's lives. When going out to party, play, etc., you can use a terminal device such as a smart phone to take photos, making the smart terminal a major shooting device.
  • the present disclosure provides a photo sharing method and apparatus for overcoming the defect that the party photo sharing processing is inefficient due to the sharing manner manually transmitted.
  • a photo sharing method including:
  • each second party photo group identified by the party mark and each second party photo group respectively Contacts including:
  • each existing second party photo group is obtained, and the corresponding contact corresponding to each second party photo group is determined according to the first address book.
  • the method before receiving the party photo sharing request sent by the trigger terminal, the method further includes:
  • the to-be-stored party photo group is stored in a cloud photo album corresponding to the user account.
  • the party tag after receiving a party photo sharing request that is sent by the party participant as a trigger and carrying the user account and the party tag, on the one hand, obtaining the party tag from the cloud album corresponding to the trigger user account.
  • Corresponding first party photo group on the other hand, according to each contact included in the first address book corresponding to the trigger user account, obtaining a second party photo corresponding to the party mark in the cloud album of each contact Grouping, and determining corresponding contacts of each second party photo group according to the first address book.
  • the to-be-shared party photo collection including the first party photo group and each second party photo group is based on the contact information of the triggers recorded in the first address book and the contacts of the corresponding contact points of the second party photo group respectively.
  • the method is sent to the contact person corresponding to each of the second party photo group, thereby realizing the sharing of the party photos, and improving the sharing processing efficiency of the party photos.
  • the method further includes:
  • the determining, by the second face image set, whether there is a second face image set that is weakly related to the first face image set includes:
  • the correlation screening process of the face image set corresponding to the first party photo group, the weakly related second party photo group can be from the to-be-shared party photo collection Delete to further ensure the accuracy and reliability of the final shared party photos.
  • the photo collection of the to-be-shared party is sent according to the contact manner of the triggerer described in the first address book and the contact manner of the contact corresponding to each second party photo group respectively.
  • the method further includes:
  • the set of the to-be-shared party photo is sent to the target contact according to the contact manner corresponding to the target contact avatar.
  • the above solution by marking each contact and the trigger who has received the photo collection of the party to be shared, and by using the face image in each face image set corresponding to the party photo collection to be shared, and the above-mentioned contacts and triggers
  • the matching processing of the avatars of the unmarked contacts in the address book of the person can avoid missing the party participants, and further ensure the accurate and reliable sharing of the party photos.
  • a photo sharing apparatus including:
  • a first acquiring module configured to acquire, in a cloud photo album corresponding to the trigger user account, a first party photo group corresponding to the party mark;
  • a second acquiring module configured to acquire, according to each contact included in the first address book corresponding to the trigger user account, each second party photo group identified by the party mark and each second party photo Group corresponding contacts;
  • a third acquiring module configured to acquire a to-be-shared party photo collection including the first party photo group and each second party photo group;
  • the sending module is configured to send the to-be-shared party photo collection according to the contact information of the triggerer and the contact manner of the contact corresponding to each second party photo group described in the first address book A contact corresponding to the triggerer and each of the second party photo groups.
  • the second obtaining module includes:
  • a first determining submodule configured to respectively determine a contact user account corresponding to each contact included in the first address book
  • a second determining sub-module configured to determine, respectively, whether a second party photo group identified by the party mark exists in the cloud photo album corresponding to each contact user account;
  • Obtaining a sub-module configured to: when there is a second party photo group identified by the party mark, acquire each second party photo group that exists, and determine, according to the first address book, each second party photo group that exists Corresponding contact people.
  • the device further includes:
  • the second receiving module is configured to receive a storage request sent by each user terminal, where the storage request includes a party photo group to be stored and a user account identified by the party mark;
  • a storage module configured to store the to-be-stored party photo group in a cloud photo album corresponding to the user account.
  • the photo sharing device When the photo sharing device receives a party photo sharing request that is sent by the party participant as a trigger and carries the user account and the party tag, on the other hand, the cloud photo album corresponding to the trigger user account is obtained from the party photo tag.
  • the first party photo group of the first party according to each contact included in the first address book corresponding to the trigger user account, acquiring a second party photo group corresponding to the party mark in the cloud album of each contact And determining, according to the first address book, the contact corresponding to each second party photo group.
  • the to-be-shared party photo collection including the first party photo group and each second party photo group is based on the contact information of the triggers recorded in the first address book and the contacts of the corresponding contact points of the second party photo group respectively.
  • the method is sent to the contact person corresponding to each of the second party photo group, thereby realizing the sharing of the party photos, and improving the sharing processing efficiency of the party photos.
  • the device further includes:
  • a fourth acquiring module configured to obtain, by using face recognition, a first facial image set included in the first party photo group in the to-be-shared party photo collection, and the second party photo group a second set of face images respectively included;
  • a determining module configured to determine whether there is a second face image set that is weakly related to the first face image set in each second face image set;
  • a deleting module configured to delete a second facial image set that is weakly related to the first facial image set in each second facial image set, and delete the The second party photo group corresponding to the second face image set that is weakly related to the first face image set is described.
  • the determining module includes:
  • a third determining sub-module configured to determine, for each second facial image set, the number of identical facial images of the second facial image set and the first facial image set, respectively;
  • the fourth determining sub-module is configured to determine the second facial image set and when the number of the same facial image is less than a preset number threshold, and the number of occurrences of the same facial image is less than a preset number threshold
  • the first face image set is weakly correlated.
  • the correlation screening process of the face image set corresponding to the first party photo group by the face image set corresponding to each of the second party photo groups described above, and the weakly related second party photo group can be from the to-be-shared party photo collection Delete to further ensure the accuracy and reliability of the final shared party photos.
  • the device further includes:
  • the fifth obtaining module is configured to obtain a second address record corresponding to each contact user account respectively;
  • a marking module configured to mark each second party photo group correspondingly in the first address book and each second address book Contact and the trigger
  • a matching module configured to respectively map the first face image set and each face image included in each second face image set to the unmarked contact in the first address book and each second address book The avatar is matched to determine whether there is a matching target contact avatar;
  • the second sending module is configured to send the to-be-shared party photo collection to the target contact according to the contact manner corresponding to the target contact avatar when the target contact avatar is present.
  • the above solution by marking each contact and the trigger who has received the photo collection of the party to be shared, and by using the face image in each face image set corresponding to the party photo collection to be shared, and the above-mentioned contacts and triggers
  • the matching processing of the avatars of the unmarked contacts in the address book of the person can avoid missing the party participants, and further ensure the accurate and reliable sharing of the party photos.
  • a photo sharing apparatus including:
  • a memory configured to store processor executable instructions
  • the meeting receives a party photo sharing request sent by the trigger terminal, where the party photo sharing request includes a party mark and a trigger user account;
  • FIG. 1 is a flowchart of Embodiment 1 of a photo sharing method according to an exemplary embodiment
  • FIG. 2 is a flowchart of Embodiment 2 of a photo sharing method according to an exemplary embodiment
  • FIG. 3 is a flowchart of Embodiment 3 of a photo sharing method according to an exemplary embodiment
  • FIG. 4 is a flowchart of Embodiment 4 of a photo sharing method according to an exemplary embodiment
  • FIG. 5 is a block diagram of Embodiment 1 of a photo sharing apparatus according to an exemplary embodiment
  • FIG. 6 is a block diagram of a second embodiment of a photo sharing device according to an exemplary embodiment
  • FIG. 7 is a block diagram of a third embodiment of a photo sharing device according to an exemplary embodiment
  • FIG. 8 is a block diagram of a fourth embodiment of a photo sharing device according to an exemplary embodiment
  • FIG. 9 is a block diagram of a photo sharing device according to an exemplary embodiment.
  • FIG. 10 is a block diagram of another photo sharing device, according to an exemplary embodiment.
  • FIG. 1 is a flowchart of Embodiment 1 of a photo sharing method according to an exemplary embodiment.
  • the method may be performed by a photo sharing device, and the photo sharing device may be integrally disposed in a cloud server.
  • the photo sharing method includes the following steps:
  • step 101 a party photo sharing request sent by the trigger terminal is received, where the party photo sharing request includes a party token and a trigger user account.
  • each of the four people A, B, C, and D has taken some photos, which are called party photos.
  • each person marks or names the photograph of the party that was taken it is identified by a party mark.
  • the party mark includes information such as time, location, party scene, etc., wherein the time information can be automatically determined according to the clock of the user terminal, and the location can be determined according to the GPS location information of the user terminal, such as a certain park or a certain entertainment. The name of the specific meeting place such as the park. Since the above-mentioned time, place, and place information of the same party are the same, it is assumed that the four parties A, B, C, and D have the same party mark for each group of party photos taken.
  • each user can upload data content such as an address book, a photo, and the like stored in the user terminal to the cloud server for storage.
  • data content such as an address book, a photo, and the like stored in the user terminal
  • each user will be registered in the cloud server to obtain a user account, and the cloud server will allocate a certain storage space for each registered user to store the related data content of the user.
  • the trigger is one of A, B, C, and D, and is assumed to be A.
  • the trigger triggers the party photo sharing process, that is, the party photo group that each of the four people took in the same party is summarized. Together, they are sent to these four people.
  • the terminal can be loaded with a party photo sharing APP, so that the trigger can open the APP in its terminal, input its user account and the party mark of the party photo group to be shared, which triggers the terminal to the cloud server.
  • step 102 a first party photo group corresponding to the party mark is obtained in a cloud photo album corresponding to the trigger user account.
  • the first party photo group which is the party photo group identified by the party mark, is acquired from the cloud photo album corresponding to the trigger user account.
  • each second party photo group identified by the party mark and each second party photo group are respectively corresponding to each contact included in the first address book corresponding to the trigger user account. Contact.
  • the address book of the trigger corresponding to the trigger user account is obtained, that is, the first address book, and the information of each contact of the trigger is recorded in the first address book, including the name, contact information, and the like of each contact. .
  • the reason for obtaining the contacts in the first address book mentioned above is that the party participants who participate in the same party are often familiar friends, and each other will be a contact person.
  • the party photo of the same party captured by the other party participants is obtained from the cloud photo album corresponding to the user account of each contact, that is, the above Each second party photo group identified by the party mark.
  • step 103 can be implemented as follows:
  • the first relationship may be determined according to a pre-recorded correspondence between each contact name, contact information, and each contact user account.
  • the second photo group of the party photo group identified by the party mark in the party photo sharing request is present in the cloud photo album corresponding to each contact user account. If a second party photo group identified by the above party mark exists in a contact user account, the second party photo group and the contact corresponding to the contact user account are obtained, that is, the contact user account is in the first address book. The corresponding contact in .
  • step 104 a set of to-be-shared party photos including the first party photo group and each second party photo group is acquired.
  • step 105 the photo collection of the party to be shared is sent to the contact information of the trigger and the contact information of the contact corresponding to each of the second party photo groups in the first address book. a contact corresponding to the trigger and the second party photo group respectively.
  • the first party photo group corresponding to the triggerer A (indicated by the group 1) is finally obtained, and the second party photo group corresponding to the contact B (indicated by the group 2), the contact C Corresponding second party photo group (represented by group 3), contact D corresponding second party photo group (represented by group 4).
  • B, C, and D all exist in the address book of A, and group 1 - group 4 have the same party mark.
  • first party photo group (group 1) and each second party photo group (group 2, group 3, group 4) are grouped together to form a party photo collection to be shared, so as to separately share the party photo to be shared Send to A, B, C, D.
  • the contact form of A, B, C, and D is recorded in the address book of the trigger A, according to the contact mode, the set of party photos to be shared can be sent to A, B, C, and D.
  • the party participant-trigger after receiving a party photo sharing request sent by a party participant-trigger with the user account and the party mark, on the one hand, obtaining the party from the cloud album corresponding to the trigger user account. Marking the corresponding first party photo group, and, on the other hand, acquiring the second party corresponding to the party tag in the cloud album of each contact according to each contact included in the first address book corresponding to the trigger user account.
  • the photo group, and the contacts corresponding to the second party photo group are respectively determined according to the first address book.
  • the to-be-shared party photo collection including the first party photo group and each second party photo group is based on the contact information of the triggers recorded in the first address book and the contacts of the corresponding contact points of the second party photo group respectively.
  • the method is sent to the contact person corresponding to each of the second party photo group, thereby realizing the sharing of the party photos, and improving the sharing processing efficiency of the party photos.
  • FIG. 2 is a flowchart of a second embodiment of a photo sharing method according to an exemplary embodiment. As shown in FIG. 2, in the embodiment, after step 104 of the embodiment shown in FIG. step:
  • step 201 the first face image set included in the first party photo group in the to-be-shared party photo collection is obtained by face recognition, and the second party photo group included in each of the second party photo groups Second face image collection.
  • step 202 it is determined whether there is a second face image set that is weakly related to the first face image set in each second face image set, if the second face image set exists and the If the first face image set is weakly related to the second face image set, step 203 is performed; otherwise, step 105 is directly executed.
  • step 203 a second party photo group corresponding to the second face image set that is weakly related to the first face image set is deleted from the to-be-shared party photo set.
  • a face recognition process is performed on each party photo in the first party photo group by using a face recognition technology, and a first face image set composed of each face image included in the first party photo group is obtained, and a person is adopted.
  • the face recognition technology performs face recognition processing on each party photo in each second party photo group, and obtains a second face image set corresponding to each second party photo group.
  • each second face image set it is determined whether it is weakly related to the first face image set.
  • each second face image set is weakly related to the first face image set by:
  • the value determines that the second face image set is weakly related to the first face image set.
  • the triggerer A corresponds to the first face image set A1
  • the contact B corresponds to the second face image set B1
  • the contact C corresponds to the second face image set C
  • the contact D corresponds to The second face image set D1.
  • D1 is weakly related to A1, indicating that D and A participate in different parties.
  • the party photo group corresponding to the D is deleted in the to-be-shared party photo collection formed by each party photo group identified by the same party mark corresponding to A, B, C, and D, respectively. Then, according to the contact manners of A, B, and C recorded in the first address book of the trigger A, the set of party photos to be shared after the party photo group corresponding to the D is sent to A, B, and C.
  • the weakly related party photo group can be deleted from the to-shared party photo collection, and the final shared party photo is ensured to be accurate and reliable.
  • the address book based on the trigger A is The contact modes of A, B, and C described in the document can send the set of party photos to be shared to A, B, and C without being sent to E because there is no E contact in the address book of the trigger A.
  • the set of party photos to be shared cannot be sent to E under the above circumstances, in combination with the embodiment shown in FIG. 3, the following solution is provided.
  • FIG. 3 is a flowchart of a third embodiment of a photo sharing method according to an exemplary embodiment. As shown in FIG. 3, in the embodiment, on the basis of the embodiment shown in FIG. 2, after step 105. It also includes the following steps:
  • step 301 a second address book corresponding to each contact user account is obtained.
  • the contact corresponding to each contact user account refers to the contact in the cloud photo album in which the second party photo group exists.
  • the corresponding second address book is respectively obtained from the respective contact user accounts.
  • step 302 the contact corresponding to each second party photo group and the trigger are marked in the first address book and each second address book.
  • Each address book contains not only the contact's name, contact information, but also the contact's avatar, such as a photo sticker.
  • the first address book according to A is included.
  • the contact form of A, B, and C sends the collection of party photos to be shared to A, B, and C.
  • the users corresponding to each party photo group in the to-be-shared party photo collection are respectively marked, that is, A, B, and C are respectively marked. That is, A, B, and C are respectively marked in the first address book of the trigger A and the second address book of the contacts B and C, respectively.
  • the remaining unmarked contacts are respectively the contacts E in B and the contacts F in C.
  • step 303 the first face image set and each face image included in each second face image set are respectively associated with the unmarked contacts in the first address book and each second address book.
  • the avatar performs a matching process to determine whether there is a matching target contact avatar. If there is a target contact avatar, step 304 is performed, otherwise the process ends.
  • step 304 the to-be-shared party photo collection is sent to the target contact according to the contact manner corresponding to the target contact avatar.
  • the face recognition technology has been used to identify the face image set corresponding to each party photo group in the photo collection to be shared, that is, the first face image set and each second face image set.
  • E does not take a party photo in the above example, the image of E is captured in the party photo group taken by other party participants A, B, and C, and although E does not exist in the address book of the triggerer A, But it may exist in the address book of other contacts of A (contacts with the second party photo group).
  • each of the face images included in the first face image set and each second face image set is respectively associated with the first address book of the trigger A and the second of the contacts B and C.
  • the avatar of the unmarked contact in the address book is matched to determine whether there is a matching target contact avatar.
  • the face images are matched with the avatars of E and F, that is, the similarity measure of the face features is performed to determine whether each face image is in the image. There are face images that match E and F.
  • the matching face process can be used to determine that the face image containing the E matches the avatar of the contact E of the B, and the contact E is determined to be sent to the photo of the party to be shared.
  • the set of target contacts, so that the set of photos to be shared is sent to E according to the contact information of E recorded in B's address book.
  • the contact of the photo collection of the party to be shared is received. Marking of the person and the trigger, and by matching the set of face images corresponding to the set of party photos to be shared with the avatars of the unmarked contacts in the contacts of the above contacts and triggers, to avoid missing party participation People ensure the accuracy and reliability of party photo sharing.
  • FIG. 4 is a flowchart of a fourth embodiment of a photo sharing method according to an exemplary embodiment. As shown in FIG. 4, based on the foregoing embodiments, before step 101, the following steps may be further included:
  • step 401 a storage request sent by each user terminal is received, where the storage request includes a party photo group to be stored and a user account identified by the party tag.
  • step 402 the group of party photos to be stored is stored in a cloud album corresponding to the user account.
  • each user registers a user account in the cloud to store the data content such as address book, photo, audio and video stored in the terminal in the cloud.
  • the party photo group may be a folder in which each party photo taken by the user at the party is stored.
  • the folder may be named with a party tag, and the specific composition of the party tag has been described in the foregoing embodiment, and details are not described herein again.
  • the cloud storage process is triggered, the user terminal sends a storage request carrying the photo group to be stored and the user account to the cloud server, so that the cloud server can
  • the party photo group to be stored identified by the party tag is stored in the cloud photo album corresponding to the user account.
  • FIG. 5 is a block diagram of a first embodiment of a photo sharing device according to an exemplary embodiment.
  • the photo sharing device includes: a first receiving module 11, a first obtaining module 12, and a second acquiring module. 13.
  • the first receiving module 11 is configured to receive a party photo sharing request sent by the trigger terminal, where the party photo sharing request includes a party token and a trigger user account.
  • the first obtaining module 12 is configured to acquire a first party photo group corresponding to the party mark in the cloud photo album corresponding to the trigger user account.
  • the second obtaining module 13 is configured to acquire, according to each contact included in the first address book corresponding to the trigger user account, each second party photo group identified by the party mark and each second party The photo group corresponds to the contact.
  • the third obtaining module 14 is configured to acquire a to-be-shared party photo collection including the first party photo group and each second party photo group.
  • the first sending module 15 is configured to: according to the contact manner of the triggerer described in the first address book and the contact manner of the contact corresponding to each second party photo group, the to-be-shared party The photo collection is sent to the contact corresponding to the trigger and the respective second party photo group.
  • the second obtaining module 13 includes: a first determining submodule 131, a second determining submodule 132, and an obtaining submodule 133.
  • the first determining sub-module 131 is configured to respectively determine a contact user account corresponding to each contact included in the first address book.
  • the second determining sub-module 132 is configured to determine whether there is a second party photo group identified by the party mark in the cloud photo album corresponding to each contact user account.
  • the obtaining sub-module 133 is configured to: when there is a second party photo group identified by the party mark, acquire each second party photo group that exists, and determine, according to the first address book, each second party photo that exists Group corresponding contacts.
  • FIG. 6 is a block diagram of a second embodiment of a photo sharing device according to an exemplary embodiment. As shown in FIG. 6 , the photo sharing device further includes: fourth obtaining, based on the embodiment shown in FIG. 5 . Module 21, determination module 22 and deletion module 23.
  • the fourth obtaining module 21 is configured to obtain, by using face recognition, a first facial image set included in the first party photo group in the to-be-shared party photo collection, and the second party photo group A second set of face images included in each.
  • the determining module 22 is configured to determine whether there is a second face image set that is weakly related to the first face image set in each second face image set.
  • the deleting module 23 is configured to delete the second facial image set that is weakly related to the first facial image set in the second facial image set, and delete the photo from the to-shared party photo collection
  • the first face image set is a second party photo group corresponding to the weakly related second face image set.
  • the determining module 22 includes: a third determining submodule 221 and a fourth determining submodule 222.
  • the third determining sub-module 221 is configured to determine, for each second facial image set, the number of identical facial images of the second facial image set and the first facial image set, respectively.
  • the fourth determining sub-module 222 is configured to determine the second facial image set when the number of the same facial images is less than a preset number threshold, and the number of occurrences of the same facial image is less than a preset number of thresholds It is weakly related to the first face image set.
  • FIG. 7 is a block diagram of a third embodiment of a photo sharing device according to an exemplary embodiment. As shown in FIG. 7 , on the basis of the embodiment shown in FIG. 6 , the device further includes: a fifth acquiring module. 31. A tagging module 32, a matching module 33, and a second transmitting module 34.
  • the fifth obtaining module 31 is configured to obtain a second address record corresponding to each contact user account respectively;
  • the marking module 32 is configured to mark, in the first address book and each second address book, a contact and a trigger corresponding to each second party photo group;
  • the matching module 33 is configured to connect the first face image set and each face image included in each second face image set to the unmarked contact in the first address book and each second address book respectively
  • the person's avatar performs matching processing to determine whether there is a matching target contact avatar
  • the second sending module 34 is configured to send the to-be-shared party photo collection to the target contact according to the contact manner corresponding to the target contact avatar when the target contact avatar is present.
  • FIG. 8 is a block diagram of a fourth embodiment of a photo sharing device according to an exemplary embodiment, as shown in FIG. Based on the foregoing embodiment, the device further includes: a second receiving module 41 and a storage module 42.
  • the second receiving module 41 is configured to receive a storage request sent by each user terminal, where the storage request includes a party photo group to be stored and a user account identified by the party tag.
  • the storage module 42 is configured to store the to-be-stored party photo group in a cloud photo album corresponding to the user account.
  • the photo sharing device can be implemented as:
  • a memory configured to store processor executable instructions
  • processor is configured to:
  • the photo sharing device when the photo sharing device receives a party photo sharing request that is sent by the party participant as a trigger and carries the user account and the party tag, on the other hand, the photo sharing device obtains the cloud photo album corresponding to the trigger user account.
  • a first party photo group corresponding to the party tag and, on the other hand, obtaining, according to each contact included in the first address book corresponding to the trigger user account, a cloud photo album corresponding to the party tag in each contact
  • the second party photo group, and the contacts corresponding to the second party photo group are respectively determined according to the first address book.
  • the to-be-shared party photo collection including the first party photo group and each second party photo group is based on the contact information of the triggers recorded in the first address book and the contacts of the corresponding contact points of the second party photo group respectively.
  • the method is sent to the contact person corresponding to each of the second party photo group, thereby realizing the sharing of the party photos, and improving the sharing processing efficiency of the party photos.
  • FIG. 10 is a block diagram of another photo sharing device, according to an exemplary embodiment.
  • device 1900 can be provided as a server.
  • apparatus 1900 includes a processing component 1922 that further includes one or more processors, and memory resources represented by memory 1932 for storing instructions executable by processing component 1922, such as an application.
  • An application stored in memory 1932 can include one or more modules each corresponding to a set of instructions.
  • processing component 1922 is configured to execute instructions to perform the above method:
  • Apparatus 1900 can also include a power supply component 1926 configured to perform power management of apparatus 1900, a wired or wireless network interface 1950 configured to connect apparatus 1900 to the network, and an input/output (I/O) interface 1958.
  • Device 1900 can operate based on an operating system stored in memory 1932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • General Engineering & Computer Science (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Mathematical Physics (AREA)
  • Oral & Maxillofacial Surgery (AREA)
  • Human Computer Interaction (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephone Function (AREA)
  • Primary Health Care (AREA)
  • Software Systems (AREA)
  • Processing Or Creating Images (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种照片共享方法和装置,该方法包括:接收触发者终端发送的聚会照片共享请求,聚会照片共享请求中包括聚会标记和触发者用户账号(101);在触发者用户账号对应的云相册中获取与聚会标记对应的第一聚会照片组(102);根据与触发者用户账号对应的第一通信录中所包含的各联系人,获取以聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人(103);根据第一通信录中记载的触发者的联系方式以及各第二聚会照片组分别对应的联系人的联系方式,将包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合发送给触发者和各第二聚会照片组分别对应的联系人(104,105),从而实现聚会照片的共享,提高了聚会照片共享处理效率。

Description

照片共享方法和装置
本申请基于申请号为201510462784.4、申请日为2015年07月31日的中国专利申请提出,并要求该中国专利申请的优先权,该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及通信技术领域,尤其涉及一种照片共享方法和装置。
背景技术
智能终端已经成为人们生活中必不可少的一种电子设备,在外出聚会、游玩等时,可以使用智能手机等终端设备进行照片拍摄,使得智能终端已经成为一种主要的拍摄设备。
在与朋友一起聚会时,每个参与聚会的人可能都会拍得一些照片,为了实现此次聚会所拍得照片的共享,每个人会将自己拍得的照片共享给其他人。目前,往往采用相互间通过人工发送的方式来实现。举例来说,甲、乙、丙、丁四人一起聚会,分别拍摄了一些聚会照片,甲通过微信、短信等通信方式将自身拍得的照片分别发送给乙、丙、丁,同理,乙也将自己拍得的照片分别发送给甲、丙、丁,丙、丁亦然。
发明内容
本公开提供一种照片共享方法和装置,用以克服通过人工发送的共享方式导致聚会照片共享处理效率低的缺陷。
根据本公开实施例的第一方面,提供一种照片共享方法,包括:
接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
其中,所述根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人,包括:
分别确定与所述第一通信录中所包含的各联系人对应的联系人用户账号;
分别确定各联系人用户账号对应的云相册中是否存在以所述聚会标记标识的第二聚会照片组;
若存在以所述聚会标记标识的第二聚会照片组,则获取存在的各第二聚会照片组,并根据所述第一通信录确定存在的各第二聚会照片组分别对应的联系人。
进一步地,在接收触发者终端发送的聚会照片共享请求之前,所述方法还包括:
接收各用户终端发送的存储请求,所述存储请求中包括以聚会标记标识的待存储聚会照片组和用户账号;
将所述待存储聚会照片组存储在与所述用户账号对应的云相册中。
通过上述方案,当接收到某聚会参与人称为触发者发送的携带有自身用户账号和聚会标记的聚会照片共享请求后,一方面,从该触发者用户账号对应的云相册中获取与该聚会标记对应的第一聚会照片组,另一方面,根据该触发者用户账号对应的第一通信录中包含的各联系人,在各联系人的云相册中获取与该聚会标记对应的第二聚会照片组,并根据第一通信录分别确定各第二聚会照片组对应的联系人。最后,将包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合,根据第一通信录中记载的触发者的联系方式以及各第二聚会照片组分别对应的联系人的联系方式,发送给触发者和各第二聚会照片组分别对应的联系人,从而实现了聚会照片的共享,提高了聚会照片的共享处理效率。
进一步地,在获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合之后,还包括:
通过人脸识别,获得所述待共享聚会照片集合中的所述第一聚会照片组中包含的第一人脸图像集合,以及所述各第二聚会照片组中分别包含的第二人脸图像集合;
确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合;
若所述各第二人脸图像集合中存在与所述第一人脸图像集合弱相关的第二人脸图像集合,则从所述待共享聚会照片集合中删除与所述第一人脸图像集合弱相关的第二人脸图像集合所对应的第二聚会照片组。
其中,所述确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合,包括:
分别针对每个第二人脸图像集合,确定该第二人脸图像集合与所述第一人脸图像集合的相同人脸图像个数;
若所述相同人脸图像个数小于预设数量阈值,且所述相同人脸图像的出现次数小于预设次数阈值,则确定该第二人脸图像集合与所述第一人脸图像集合弱相关。
基于上述各第二聚会照片组对应的人脸图像集合,与第一聚会照片组对应的人脸图像集合的相关性筛选处理,能够将弱相关的第二聚会照片组从待共享聚会照片集合中删除,进一步保证最终共享的聚会照片的准确、可靠。
进一步地,所述根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人之后,还包括:
分别获得各联系人用户账号对应的第二通信录;
在所述第一通信录和各第二通信录中标记各第二聚会照片组对应的联系人和所述触发者;
将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与所述第一通信录和各第二通信录中未被标记的联系人的头像进行匹配处理,确定是否存在匹配的目标联系人头像;
若存在目标联系人头像,则根据所述目标联系人头像所对应的联系方式,将所述待共享聚会照片集合发送给所述目标联系人。
上述方案,通过对已接收待共享聚会照片集合的各联系人和触发者的标记,以及通过将待共享聚会照片集合对应的各人脸图像集合中的人脸图像,与上述各联系人和触发者的通信录中未被标记的联系人的头像的匹配处理,能够避免遗漏聚会参与人,进一步保证了聚会照片共享的准确、可靠。
根据本公开实施例的第二方面,提供一种照片共享装置,包括:
第一接收模块,被配置为接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
第一获取模块,被配置为在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
第二获取模块,被配置为根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
第三获取模块,被配置为获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
发送模块,被配置为根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
其中,所述第二获取模块包括:
第一确定子模块,被配置为分别确定与所述第一通信录中所包含的各联系人对应的联系人用户账号;
第二确定子模块,被配置为分别确定各联系人用户账号对应的云相册中是否存在以所述聚会标记标识的第二聚会照片组;
获取子模块,被配置为在存在以所述聚会标记标识的第二聚会照片组时,获取存在的各第二聚会照片组,并根据所述第一通信录确定存在的各第二聚会照片组分别对应的联系 人。
进一步地,所述装置还包括:
第二接收模块,被配置为接收各用户终端发送的存储请求,所述存储请求中包括以聚会标记标识的待存储聚会照片组和用户账号;
存储模块,被配置为将所述待存储聚会照片组存储在与所述用户账号对应的云相册中。
当照片共享装置接收到某聚会参与人称为触发者发送的携带有自身用户账号和聚会标记的聚会照片共享请求后,一方面,从该触发者用户账号对应的云相册中获取与该聚会标记对应的第一聚会照片组,另一方面,根据该触发者用户账号对应的第一通信录中包含的各联系人,在各联系人的云相册中获取与该聚会标记对应的第二聚会照片组,并根据第一通信录分别确定各第二聚会照片组对应的联系人。最后,将包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合,根据第一通信录中记载的触发者的联系方式以及各第二聚会照片组分别对应的联系人的联系方式,发送给触发者和各第二聚会照片组分别对应的联系人,从而实现了聚会照片的共享,提高了聚会照片的共享处理效率。
进一步地,所述装置还包括:
第四获取模块,被配置为通过人脸识别,获得所述待共享聚会照片集合中的所述第一聚会照片组中包含的第一人脸图像集合,以及所述各第二聚会照片组中分别包含的第二人脸图像集合;
确定模块,被配置为确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合;
删除模块,被配置为在所述各第二人脸图像集合中存在与所述第一人脸图像集合弱相关的第二人脸图像集合时,从所述待共享聚会照片集合中删除与所述第一人脸图像集合弱相关的第二人脸图像集合所对应的第二聚会照片组。
其中,所述确定模块包括:
第三确定子模块,被配置为分别针对每个第二人脸图像集合,确定该第二人脸图像集合与所述第一人脸图像集合的相同人脸图像个数;
第四确定子模块,被配置为在所述相同人脸图像个数小于预设数量阈值,且所述相同人脸图像的出现次数小于预设次数阈值时,确定该第二人脸图像集合与所述第一人脸图像集合弱相关。
通过上述各第二聚会照片组对应的人脸图像集合,与第一聚会照片组对应的人脸图像集合的相关性筛选处理,能够将弱相关的第二聚会照片组从待共享聚会照片集合中删除,进一步保证最终共享的聚会照片的准确、可靠。
进一步地,所述装置还包括:
第五获取模块,被配置为分别获得各联系人用户账号对应的第二通信录;
标记模块,被配置为在所述第一通信录和各第二通信录中标记各第二聚会照片组对应 的联系人和所述触发者;
匹配模块,被配置为将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与所述第一通信录和各第二通信录中未被标记的联系人的头像进行匹配处理,确定是否存在匹配的目标联系人头像;
第二发送模块,被配置为在存在目标联系人头像时,根据所述目标联系人头像所对应的联系方式,将所述待共享聚会照片集合发送给所述目标联系人。
上述方案,通过对已接收待共享聚会照片集合的各联系人和触发者的标记,以及通过将待共享聚会照片集合对应的各人脸图像集合中的人脸图像,与上述各联系人和触发者的通信录中未被标记的联系人的头像的匹配处理,能够避免遗漏聚会参与人,进一步保证了聚会照片共享的准确、可靠。
根据本公开实施例的第三方面,提供一种照片共享装置,包括:
处理器;
被配置为存储处理器可执行指令的存储器;
其中,所述处接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性和解释性的,并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分,示出了符合本公开的实施例,并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种照片共享方法实施例一的流程图;
图2是根据一示例性实施例示出的一种照片共享方法实施例二的流程图;
图3是根据一示例性实施例示出的一种照片共享方法实施例三的流程图;
图4是根据一示例性实施例示出的一种照片共享方法实施例四的流程图;
图5是根据一示例性实施例示出的一种照片共享装置实施例一的框图;
图6是根据一示例性实施例示出的一种照片共享装置实施例二的框图;
图7是根据一示例性实施例示出的一种照片共享装置实施例三的框图;
图8是根据一示例性实施例示出的一种照片共享装置实施例四的框图;
图9是根据一示例性实施例示出的一种照片共享装置的框图;
图10是根据一示例性实施例示出的另一种照片共享装置的框图。
通过上述附图,已示出本公开明确的实施例,后文中将有更详细的描述。这些附图和文字描述并不是为了通过任何方式限制本公开构思的范围,而是通过参考特定实施例为本领域技术人员说明本公开的概念。
具体实施方式
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
图1是根据一示例性实施例示出的一种照片共享方法实施例一的流程图,该方法可以由照片共享装置来执行,该照片共享装置可以集成设置在云服务器中。如图1所示,该照片共享方法包括以下步骤:
在步骤101中,接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号。
本实施例中,假设A、B、C和D四人的聚会中,各自拍得了一些照片,这些照片称为聚会照片。并且,在每个人对拍得的聚会照片进行标记或者说是命名时,会以聚会标记来标识。该聚会标记中比如包括时间、地点、聚会场景等信息,其中,时间信息可以根据用户终端的时钟自动确定,地点可以根据用户终端的GPS位置信息来确定,聚会场景比如某某公园、某某娱乐园等具体的聚会场所名。由于同一聚会的上述时间、地点、场所信息都相同,所以,假设A、B、C和D四人对各自拍得的一组聚会照片的聚会标记也相同。
另外,本公开实施例中假设每个用户可以将用户终端中存储的诸如通信录、照片等数据内容上传至云服务器中存储。为此,每个用户在云服务器中会注册获得一个用户账号,云服务器相应的会为每个注册用户分配一定的存储空间,用于存储该用户的相关数据内容。
本实施例中,上述触发者是A、B、C、D中的一人,假设为A,由该触发者触发聚会照片共享处理,即将这四人在同一聚会中各自拍得的聚会照片组汇总在一起,分别发送给这四人。
举例来说,终端中可以装载有聚会照片共享APP,从而,上述触发者可以在其终端中开启该APP,输入其用户账号以及待共享的聚会照片组的聚会标记,这样触发了终端向云服务器发送一条携带有该触发者用户账号和聚会标记的聚会照片共享请求。
在步骤102中,在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组。
在接收到上述聚会照片共享请求之后,从该触发者用户账号对应的云相册中,获取以上述聚会标记来标识的聚会照片组即上述第一聚会照片组。
在步骤103中,根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人。
进而,获取与触发者用户账号对应的触发者的通信录即上述第一通信录,该第一通信录中记载有该触发者的各联系人的信息,包括各联系人的名称、联系方式等。
之所以获得上述第一通信录中的各联系人,是因为参与同一聚会的各聚会参与人往往是相熟识的好友,彼此之间都会互为联系人。这样,可以根据触发者用户账号对应的第一通信录中包含的各联系人,从各联系人的用户账号对应的云相册中获得其他聚会参与人拍得的同一聚会的聚会照片,即以上述聚会标记标识的各第二聚会照片组。
具体来说,上述步骤103可以通过如下方式实现:
在获得了触发者用户账号下对应的第一通信录中包含的各联系人之后,可以根据预先记录的比如各联系人名称、联系方式与各联系人用户账号之间的对应关系,确定第一通信录中各联系人对应的联系人用户账号;
进而,分别确定各联系人用户账号对应的云相册中是否存在以上述聚会照片共享请求中的聚会标记来标识的聚会照片组即上述第二聚会照片组。如果某联系人用户账号下存在以上述聚会标记标识的第二聚会照片组,则获取该第二聚会照片组以及该联系人用户账号对应的联系人,即该联系人用户账号在第一通信录中对应的联系人。
在步骤104中,获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合。
在步骤105中,根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
通过上述处理方式,基于第一通信录中的各联系人和聚会标记,获得了以该聚会标记标识的其他聚会照片组以及每个聚会照片组对应的联系人。
也就是说,针对上述举例来说,最终获得了触发者A对应的第一聚会照片组(以组1表示),联系人B对应的第二聚会照片组(以组2表示),联系人C对应的第二聚会照片组(以组3表示),联系人D对应的第二聚会照片组(以组4表示)。其中,B、C、D均存在于A的通信录中,且组1-组4都具有相同的上述聚会标记。
从而,将上述第一聚会照片组(组1)和各第二聚会照片组(组2、组3、组4)汇总在一起,形成待共享聚会照片集合,以将该待共享聚会照片集合分别发送给A、B、C、D。
具体来说,由于触发者A的通信录中记载有A、B、C、D的联系方式,根据该联系方式,可以将待共享聚会照片集合发送给A、B、C、D。
本实施例中,当接收到某聚会参与人—触发者发送的携带有自身用户账号和聚会标记的聚会照片共享请求后,一方面,从该触发者用户账号对应的云相册中获取与该聚会标记对应的第一聚会照片组,另一方面,根据该触发者用户账号对应的第一通信录中包含的各联系人,在各联系人的云相册中获取与该聚会标记对应的第二聚会照片组,并根据第一通信录分别确定各第二聚会照片组对应的联系人。最后,将包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合,根据第一通信录中记载的触发者的联系方式以及各第二聚会照片组分别对应的联系人的联系方式,发送给触发者和各第二聚会照片组分别对应的联系人,从而实现了聚会照片的共享,提高了聚会照片的共享处理效率。
结合上述举例,在实际应用中,有可能会出现如下的特殊情况:虽然B、C、D的云相册中存在有以上述聚会标记来标识的聚会照片组,但是很可能只是一种巧合。比如,A、B、C参加了一个聚会,在相同的时间、地点,D与其他人(除A、B、C之外)也有另一个聚会,也就是说,A、B、C的聚会对应的待共享聚会照片集合中不应该不含D以相同聚会标记标识的聚会照片组。针对该特殊情况,本公开实施例中提供了如图2所示的解决方案。
图2是根据一示例性实施例示出的一种照片共享方法实施例二的流程图,如图2所示,本实施例中,在上述图1所示实施例的步骤104之后,还包括如下步骤:
在步骤201中,通过人脸识别,获得所述待共享聚会照片集合中的所述第一聚会照片组中包含的第一人脸图像集合,以及所述各第二聚会照片组中分别包含的第二人脸图像集合。
在步骤202中,确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合,若所述各第二人脸图像集合中存在与所述第一人脸图像集合弱相关的第二人脸图像集合,则执行步骤203,否则,直接执行步骤105。
在步骤203中,从所述待共享聚会照片集合中删除与所述第一人脸图像集合弱相关的第二人脸图像集合所对应的第二聚会照片组。
首先,采用人脸识别技术对第一聚会照片组中的各聚会照片进行人脸识别处理,得到由第一聚会照片组中包含的各人脸图像构成的第一人脸图像集合,以及采用人脸识别技术对各第二聚会照片组中的各聚会照片进行人脸识别处理,得到每个第二聚会照片组对应的第二人脸图像集合。
进而,针对每个第二人脸图像集合,确定其与第一人脸图像集合是否弱相关。
具体来说,可以通过如下方式确定每个第二人脸图像集合是否与第一人脸图像集合弱相关:
针对每个第二人脸图像集合,确定该第二人脸图像集合与第一人脸图像集合的相同人脸图像个数;
若相同人脸图像个数小于预设数量阈值,且相同人脸图像的出现次数小于预设次数阈 值,则确定该第二人脸图像集合与第一人脸图像集合弱相关。
针对上述特殊情况的举例来说,假设触发者A对应第一人脸图像集合A1,联系人B对应第二人脸图像集合B1,联系人C对应第二人脸图像集合C1,联系人D对应第二人脸图像集合D1。假设B1和C1中存储多个与A1中人脸图像相同的人脸图像,且相同的人脸图像的出现次数也大于预设次数阈值,则确定B1和C1与A1强相关,说明A、B、C参加的是同一个聚会。如果D1与A1中相同人脸图像个数小于预设数量阈值,且相同人脸图像的出现次数小于预设次数阈值,则确定D1与A1弱相关,说明D与A参加的是不同的聚会。
从而,在由A、B、C、D分别对应的以相同聚会标记标识的各聚会照片组构成的待共享聚会照片集合中删除上述D对应的聚会照片组。之后,根据触发者A的第一通信录中记载的A、B和C的联系方式,将去除D对应的聚会照片组之后的待共享聚会照片集合发送给A、B和C。
本实施例中,基于上述各聚会照片组对应的人脸图像集合的相关性筛选处理,能够将弱相关的聚会照片组从待共享聚会照片集合中删除,保证最终共享的聚会照片的准确、可靠。
在实际应用中,还有一种特殊情况:假设参与某个聚会的人有A、B、C、E,A作为触发者,E并没有拍得聚会照片,从而其云相册中没有以上述聚会标记标识的聚会照片组,并且,触发者A的通信录中有B和C,没有E。这样,基于上述各实施例的处理,假设待共享聚会照片集合中包含与A对应的第一聚会照片组,以及分别与B和C对应的第二聚会照片组,那么基于触发者A的通信录中记载的A、B和C的联系方式,能够将该待共享聚会照片集合发送给A、B和C,而不会发送给E,因为触发者A的通信录中没有E的联系方式。为了避免上述情况下不能将待共享聚会照片集合发送给E,结合图3所示实施例,提供了如下解决方案。
图3是根据一示例性实施例示出的一种照片共享方法实施例三的流程图,如图3所示,本实施例中,在上述图2所示实施例的基础上,在步骤105之后,还包括如下步骤:
在步骤301中,分别获得各联系人用户账号对应的第二通信录。
上述各联系人用户账号所对应的联系人是指云相册中存在上述第二聚会照片组的联系人。
在通过前述实施例中描述的方式,获得了存在各第二聚会照片组的联系人的用户账号后,从该各联系人用户账号下,分别获得对应的各第二通信录。
在步骤302中,在所述第一通信录和各第二通信录中标记各第二聚会照片组对应的联系人和所述触发者。
以上述举例来说,假设触发者A的第一通信录中包含A、B和C,联系人B的第二通信录中包含A、B、C、和E,联系人C的第二通信录中包含A、B、C和F。并且,上述 各通信录中不但包含联系人的名称、联系方式信息,还包含联系人的头像,比如大头贴。
在根据前述实施例中的描述,确定待共享聚会照片集合中包含了从A、B和C的云相册中获得的具有强相关关系的各聚会照片组之后,根据A的第一通信录中包含的A、B和C的联系方式,将该待共享聚会照片集合发送给A、B和C。之后,在A、B和C对应的通信录中分别标记该待共享聚会照片集合中每个聚会照片组对应的用户,即分别标记A、B和C。也就是说,在触发者A的第一通信录和联系人B和C的第二通信录中分别标记A、B和C。从而,剩余没有被标记的联系人分别是B中的联系人E和C中的联系人F。
在步骤303中,将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与所述第一通信录和各第二通信录中未被标记的联系人的头像进行匹配处理,确定是否存在匹配的目标联系人头像,若存在目标联系人头像,则执行步骤304,否则结束。
在步骤304中,根据所述目标联系人头像所对应的联系方式,将所述待共享聚会照片集合发送给所述目标联系人。
上述图2所示实施例中,已经采用人脸识别技术识别获得了待共享聚会照片集合中各个聚会照片组对应的人脸图像集合即上述第一人脸图像集合和各第二人脸图像集合。虽然上述举例中E没有拍得聚会照片,但是其他聚会参与人A、B和C拍得的聚会照片组中会拍到E的图像,而且,虽然E没有存在于触发者A的通信录中,但是其可能存在于A的其他联系人(具有第二聚会照片组的联系人)的通信录中。
因此,本实施例中,通过将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与触发者A的第一通信录和联系人B和C的第二通信录中未被标记的联系人的头像进行匹配处理,以确定是否存在匹配的目标联系人头像。
由于上述举例中未被标记的联系人只有E和F,所以是将上述各人脸图像与E和F的头像进行匹配,即进行人脸特征的相似度度量,以确定各人脸图像中是否存在与E和F匹配的人脸图像。
如果上述人脸图像中包含有E的图像,则通过匹配处理,能够确定包含有E的人脸图像与B的联系人E的头像相匹配,确定该联系人E也是需要被发送待共享聚会照片集合的目标联系人,从而根据B的通信录中记录的E的联系方式,将待共享聚会照片集合发送给E。
本实施例中,在根据触发者的通信录中所记载的各联系人的联系方式,将待共享聚会照片集合发送给对应的联系人之后,通过对已接收该待共享聚会照片集合的各联系人和触发者的标记,以及通过将该待共享聚会照片集合对应的人脸图像集合与上述各联系人和触发者的通信录中未被标记的联系人的头像的匹配处理,避免遗漏聚会参与人,保证了聚会照片共享的准确、可靠。
图4是根据一示例性实施例示出的一种照片共享方法实施例四的流程图,如图4所示,在上述各实施例的基础上,在步骤101之前还可以包括如下步骤:
在步骤401中,接收各用户终端发送的存储请求,所述存储请求中包括以聚会标记标识的待存储聚会照片组和用户账号。
在步骤402中,将所述待存储聚会照片组存储在与所述用户账号对应的云相册中。
本实施例中,假设各用户都会在云端注册有用户账号,以将自身终端中存储的诸如通信录、照片、音视频等数据内容进行云端存储。
当某个用户在参加完一个聚会,需要将拍得的聚会照片组即多张聚会照片发送到云端对应用户账号下的云相册中存储时,首先需要为该聚会照片组命名或者说为其打个标识。具体来说,该聚会照片组可以是一个文件夹,该文件夹中存储有该用户在本聚会时拍得的各张聚会照片。该文件夹可以以聚会标记来命名,该聚会标记的具体组成在前述实施例中已经描述,在此不再赘述。
从而,该用户通过选择待存储聚会照片组即上述文件夹,触发云存储处理后,用户终端向云服务器发送了携带有该待存储聚会照片组和用户账号的存储请求,以使云服务器将该以聚会标记标识的待存储聚会照片组存储到该用户账号对应的云相册中。
图5是根据一示例性实施例示出的一种照片共享装置实施例一的框图,如图5所示,该照片共享装置包括:第一接收模块11、第一获取模块12、第二获取模块13、第三获取模块14和第一发送模块15。
第一接收模块11,被配置为接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号。
第一获取模块12,被配置为在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组。
第二获取模块13,被配置为根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人。
第三获取模块14,被配置为获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合。
第一发送模块15,被配置为根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
其中,所述第二获取模块13包括:第一确定子模块131、第二确定子模块132和获取子模块133。
第一确定子模块131,被配置为分别确定与所述第一通信录中所包含的各联系人对应的联系人用户账号。
第二确定子模块132,被配置为分别确定各联系人用户账号对应的云相册中是否存在以所述聚会标记标识的第二聚会照片组。
获取子模块133,被配置为在存在以所述聚会标记标识的第二聚会照片组时,获取存在的各第二聚会照片组,并根据所述第一通信录确定存在的各第二聚会照片组分别对应的联系人。
图6是根据一示例性实施例示出的一种照片共享装置实施例二的框图,如图6所示,在图5所示实施例的基础上,所述照片共享装置还包括:第四获取模块21、确定模块22和删除模块23。
第四获取模块21,被配置为通过人脸识别,获得所述待共享聚会照片集合中的所述第一聚会照片组中包含的第一人脸图像集合,以及所述各第二聚会照片组中分别包含的第二人脸图像集合。
确定模块22,被配置为确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合。
删除模块23,被配置为在所述各第二人脸图像集合中存在与所述第一人脸图像集合弱相关的第二人脸图像集合时,从所述待共享聚会照片集合中删除与所述第一人脸图像集合弱相关的第二人脸图像集合所对应的第二聚会照片组。
其中,所述确定模块22包括:第三确定子模块221和第四确定子模块222。
第三确定子模块221,被配置为分别针对每个第二人脸图像集合,确定该第二人脸图像集合与所述第一人脸图像集合的相同人脸图像个数。
第四确定子模块222,被配置为在所述相同人脸图像个数小于预设数量阈值,且所述相同人脸图像的出现次数小于预设次数阈值时,确定该第二人脸图像集合与所述第一人脸图像集合弱相关。
图7是根据一示例性实施例示出的一种照片共享装置实施例三的框图,如图7所示,在上述图6所示实施例的基础上,所述装置还包括:第五获取模块31、标记模块32、匹配模块33和第二发送模块34。
第五获取模块31,被配置为分别获得各联系人用户账号对应的第二通信录;
标记模块32,被配置为在所述第一通信录和各第二通信录中标记各第二聚会照片组对应的联系人和所述触发者;
匹配模块33,被配置为将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与所述第一通信录和各第二通信录中未被标记的联系人的头像进行匹配处理,确定是否存在匹配的目标联系人头像;
第二发送模块34,被配置为在存在目标联系人头像时,根据所述目标联系人头像所对应的联系方式,将所述待共享聚会照片集合发送给所述目标联系人。
图8是根据一示例性实施例示出的一种照片共享装置实施例四的框图,如图8所示, 在上述实施例的基础上,所述装置还包括:第二接收模块41和存储模块42。
第二接收模块41,被配置为接收各用户终端发送的存储请求,所述存储请求中包括以聚会标记标识的待存储聚会照片组和用户账号。
存储模块42,被配置为将所述待存储聚会照片组存储在与所述用户账号对应的云相册中。
关于上述实施例中的照片共享装置,其中各个模块、子模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述,此处将不做详细阐述说明。
以上描述了照片共享装置的内部功能和结构,如图9所示,实际中,该照片共享装置可实现为:
处理器;
被配置为存储处理器可执行指令的存储器;
其中,所述处理器被配置为:
接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
以上实施例中,当照片共享装置接收到某聚会参与人称为触发者发送的携带有自身用户账号和聚会标记的聚会照片共享请求后,一方面,从该触发者用户账号对应的云相册中获取与该聚会标记对应的第一聚会照片组,另一方面,根据该触发者用户账号对应的第一通信录中包含的各联系人,在各联系人的云相册中获取与该聚会标记对应的第二聚会照片组,并根据第一通信录分别确定各第二聚会照片组对应的联系人。最后,将包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合,根据第一通信录中记载的触发者的联系方式以及各第二聚会照片组分别对应的联系人的联系方式,发送给触发者和各第二聚会照片组分别对应的联系人,从而实现了聚会照片的共享,提高了聚会照片的共享处理效率。
图10是根据一示例性实施例示出的另一种照片共享装置的框图。例如,装置1900可以被提供为一服务器。参照图10,装置1900包括处理组件1922,其进一步包括一个或多个处理器,以及由存储器1932所代表的存储器资源,用于存储可由处理组件1922的执行的指令,例如应用程序。存储器1932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外,处理组件1922被配置为执行指令,以执行上述方法:
接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
装置1900还可以包括一个电源组件1926被配置为执行装置1900的电源管理,一个有线或无线网络接口1950被配置为将装置1900连接到网络,和一个输入输出(I/O)接口1958。装置1900可以操作基于存储在存储器1932的操作系统,例如Windows ServerTM,Mac OS XTM,UnixTM,LinuxTM,FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后,将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本公开的真正范围和精神由下面的权利要求指出。
应当理解的是,本公开并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (13)

  1. 一种照片共享方法,其特征在于,所述方法包括:
    接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
    在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
    根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
    获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
    根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
  2. 根据权利要求1所述的方法,其特征在于,所述根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人,包括:
    分别确定与所述第一通信录中所包含的各联系人对应的联系人用户账号;
    分别确定各联系人用户账号对应的云相册中是否存在以所述聚会标记标识的第二聚会照片组;
    若存在以所述聚会标记标识的第二聚会照片组,则获取存在的各第二聚会照片组,并根据所述第一通信录确定存在的各第二聚会照片组分别对应的联系人。
  3. 根据权利要求2所述的方法,其特征在于,所述获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合之后,还包括:
    通过人脸识别,获得所述待共享聚会照片集合中的所述第一聚会照片组中包含的第一人脸图像集合,以及所述各第二聚会照片组中分别包含的第二人脸图像集合;
    确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合;
    若所述各第二人脸图像集合中存在与所述第一人脸图像集合弱相关的第二人脸图像集合,则从所述待共享聚会照片集合中删除与所述第一人脸图像集合弱相关的第二人脸图像集合所对应的第二聚会照片组。
  4. 根据权利要求3所述的方法,其特征在于,所述确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合,包括:
    分别针对每个第二人脸图像集合,确定该第二人脸图像集合与所述第一人脸图像集合 的相同人脸图像个数;
    若所述相同人脸图像个数小于预设数量阈值,且所述相同人脸图像的出现次数小于预设次数阈值,则确定该第二人脸图像集合与所述第一人脸图像集合弱相关。
  5. 根据权利要求3所述的方法,其特征在于,所述根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人之后,还包括:
    分别获得各联系人用户账号对应的第二通信录;
    在所述第一通信录和各第二通信录中标记各第二聚会照片组对应的联系人和所述触发者;
    将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与所述第一通信录和各第二通信录中未被标记的联系人的头像进行匹配处理,确定是否存在匹配的目标联系人头像;
    若存在目标联系人头像,则根据所述目标联系人头像所对应的联系方式,将所述待共享聚会照片集合发送给所述目标联系人。
  6. 根据权利要求1至5中任一项所述的方法,其特征在于,所述方法还包括:
    接收各用户终端发送的存储请求,所述存储请求中包括以聚会标记标识的待存储聚会照片组和用户账号;
    将所述待存储聚会照片组存储在与所述用户账号对应的云相册中。
  7. 一种照片共享装置,其特征在于,所述装置包括:
    第一接收模块,被配置为接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
    第一获取模块,被配置为在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
    第二获取模块,被配置为根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
    第三获取模块,被配置为获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
    第一发送模块,被配置为根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
  8. 根据权利要求7所述的装置,其特征在于,所述第二获取模块包括:
    第一确定子模块,被配置为分别确定与所述第一通信录中所包含的各联系人对应的联系人用户账号;
    第二确定子模块,被配置为分别确定各联系人用户账号对应的云相册中是否存在以所述聚会标记标识的第二聚会照片组;
    获取子模块,被配置为在存在以所述聚会标记标识的第二聚会照片组时,获取存在的各第二聚会照片组,并根据所述第一通信录确定存在的各第二聚会照片组分别对应的联系人。
  9. 根据权利要求8所述的装置,其特征在于,还包括:
    第四获取模块,被配置为通过人脸识别,获得所述待共享聚会照片集合中的所述第一聚会照片组中包含的第一人脸图像集合,以及所述各第二聚会照片组中分别包含的第二人脸图像集合;
    确定模块,被配置为确定各第二人脸图像集合中是否存在与所述第一人脸图像集合弱相关的第二人脸图像集合;
    删除模块,被配置为在所述各第二人脸图像集合中存在与所述第一人脸图像集合弱相关的第二人脸图像集合时,从所述待共享聚会照片集合中删除与所述第一人脸图像集合弱相关的第二人脸图像集合所对应的第二聚会照片组。
  10. 根据权利要求9所述的装置,其特征在于,所述确定模块包括:
    第三确定子模块,被配置为分别针对每个第二人脸图像集合,确定该第二人脸图像集合与所述第一人脸图像集合的相同人脸图像个数;
    第四确定子模块,被配置为在所述相同人脸图像个数小于预设数量阈值,且所述相同人脸图像的出现次数小于预设次数阈值时,确定该第二人脸图像集合与所述第一人脸图像集合弱相关。
  11. 根据权利要求9所述的装置,其特征在于,所述装置还包括:
    第五获取模块,被配置为分别获得各联系人用户账号对应的第二通信录;
    标记模块,被配置为在所述第一通信录和各第二通信录中标记各第二聚会照片组对应的联系人和所述触发者;
    匹配模块,被配置为将第一人脸图像集合和各第二人脸图像集合中包含的各人脸图像,分别与所述第一通信录和各第二通信录中未被标记的联系人的头像进行匹配处理,确定是否存在匹配的目标联系人头像;
    第二发送模块,被配置为在存在目标联系人头像时,根据所述目标联系人头像所对应 的联系方式,将所述待共享聚会照片集合发送给所述目标联系人。
  12. 根据权利要求7至11中任一项所述的装置,其特征在于,所述装置还包括:
    第二接收模块,被配置为接收各用户终端发送的存储请求,所述存储请求中包括以聚会标记标识的待存储聚会照片组和用户账号;
    存储模块,被配置为将所述待存储聚会照片组存储在与所述用户账号对应的云相册中。
  13. 一种照片共享装置,其特征在于,包括:
    处理器;
    被配置为存储处理器可执行指令的存储器;
    其中,所述处理器被配置为:
    接收触发者终端发送的聚会照片共享请求,所述聚会照片共享请求中包括聚会标记和触发者用户账号;
    在所述触发者用户账号对应的云相册中,获取与所述聚会标记对应的第一聚会照片组;
    根据与所述触发者用户账号对应的第一通信录中所包含的各联系人,获取以所述聚会标记标识的各第二聚会照片组以及各第二聚会照片组分别对应的联系人;
    获取包含第一聚会照片组和各第二聚会照片组的待共享聚会照片集合;
    根据所述第一通信录中记载的所述触发者的联系方式以及所述各第二聚会照片组分别对应的联系人的联系方式,将所述待共享聚会照片集合发送给所述触发者和所述各第二聚会照片组分别对应的联系人。
PCT/CN2015/097801 2015-07-31 2015-12-18 照片共享方法和装置 Ceased WO2017020484A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2017531947A JP6305654B2 (ja) 2015-07-31 2015-12-18 写真を共有する方法、装置、プログラム及び記録媒体
KR1020167004020A KR101759454B1 (ko) 2015-07-31 2015-12-18 사진을 공유하는 방법, 장치, 프로그램 및 기록매체
RU2016131883A RU2654168C2 (ru) 2015-07-31 2015-12-18 Способ и устройство для совместного использования фотографий
MX2016005074A MX385157B (es) 2015-07-31 2015-12-18 Método y dispositivo para compartir fotografías.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510462784.4A CN105069075B (zh) 2015-07-31 2015-07-31 照片共享方法和装置
CN201510462784.4 2015-07-31

Publications (1)

Publication Number Publication Date
WO2017020484A1 true WO2017020484A1 (zh) 2017-02-09

Family

ID=54498445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/097801 Ceased WO2017020484A1 (zh) 2015-07-31 2015-12-18 照片共享方法和装置

Country Status (8)

Country Link
US (1) US20170032188A1 (zh)
EP (1) EP3125179A1 (zh)
JP (1) JP6305654B2 (zh)
KR (1) KR101759454B1 (zh)
CN (1) CN105069075B (zh)
MX (1) MX385157B (zh)
RU (1) RU2654168C2 (zh)
WO (1) WO2017020484A1 (zh)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9118670B2 (en) * 2013-08-30 2015-08-25 U-Me Holdings LLC Making a user's data, settings, and licensed content available in the cloud
CN105069075B (zh) * 2015-07-31 2018-02-23 小米科技有限责任公司 照片共享方法和装置
CN105740426A (zh) * 2016-01-29 2016-07-06 宇龙计算机通信科技(深圳)有限公司 基于人脸识别的照片发送方法及装置
CN106096011A (zh) * 2016-06-23 2016-11-09 北京小米移动软件有限公司 照片分享方法及装置
CN107995157B (zh) * 2017-10-23 2020-11-03 北京春鸿科技有限公司 一种照片分发方法及系统
CN107948281A (zh) * 2017-11-24 2018-04-20 维沃移动通信有限公司 一种照片共享方法、移动终端及云服务器
KR102462793B1 (ko) 2018-05-21 2022-11-03 삼성전자 주식회사 계정 그룹 기반으로 콘텐츠를 공유하는 방법 및 이를 제공하는 전자 장치
CN108966020A (zh) * 2018-06-27 2018-12-07 Oppo广东移动通信有限公司 回忆视频创建方法及相关设备
US10880433B2 (en) * 2018-09-26 2020-12-29 Rovi Guides, Inc. Systems and methods for curation and delivery of content for use in electronic calls
US10855834B2 (en) * 2018-09-26 2020-12-01 Rovi Guides, Inc. Systems and methods for curation and delivery of content for use in electronic calls
US20200177531A1 (en) * 2018-12-03 2020-06-04 International Business Machines Corporation Photo sharing in a trusted auto-generated network
US11055361B2 (en) 2019-01-07 2021-07-06 Microsoft Technology Licensing, Llc Extensible framework for executable annotations in electronic content
CN109977081A (zh) * 2019-01-31 2019-07-05 维沃移动通信有限公司 一种内容共享方法及终端设备
CN111050077B (zh) * 2019-12-26 2021-08-10 维沃移动通信有限公司 拍摄方法及电子设备
KR20200047462A (ko) 2020-04-11 2020-05-07 주식회사 빈투게더 프라이버시가 보호되는 다자간 사진 및 동영상 공유 방법 및 시스템
CN114840279A (zh) * 2021-01-14 2022-08-02 腾讯科技(深圳)有限公司 信息共享方法、装置、终端及存储介质
CN115994051A (zh) * 2021-10-15 2023-04-21 花瓣云科技有限公司 一种图片备份系统、方法与设备
WO2023139616A1 (en) * 2022-01-20 2023-07-27 CAROSELLA, Daniele Method and system for sharing images of multimedia contents representative of spaces, places, scenarios
CN115665130A (zh) * 2022-10-19 2023-01-31 江苏开放大学(江苏城市职业学院) 智能终端影像管理方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080052349A1 (en) * 2006-08-27 2008-02-28 Michael Lin Methods and System for Aggregating Disparate Batches of Digital Media Files Captured During an Event for the Purpose of Inclusion into Public Collections for Sharing
CN103369031A (zh) * 2013-05-20 2013-10-23 华为技术有限公司 终端设备、电子相册服务器、照片分享系统及方法
CN103635892A (zh) * 2011-07-07 2014-03-12 索尼电脑娱乐美国公司 自动创建用于分享照片的群体
CN104317932A (zh) * 2014-10-31 2015-01-28 小米科技有限责任公司 照片分享方法及装置
CN105069075A (zh) * 2015-07-31 2015-11-18 小米科技有限责任公司 照片共享方法和装置

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3631225B2 (ja) * 2002-07-25 2005-03-23 キヤノン株式会社 画像処理装置、画像処理装置の制御方法、および画像処理装置の制御プログラム
JP2005267146A (ja) * 2004-03-18 2005-09-29 Nec Corp 画像認識機能を利用した電子メール作成方法および装置
US9143573B2 (en) * 2008-03-20 2015-09-22 Facebook, Inc. Tag suggestions for images on online social networks
US8224824B2 (en) * 2008-03-26 2012-07-17 Fujifilm Corporation Saving device for image sharing, image sharing system, and image sharing method
JP5268595B2 (ja) * 2008-11-28 2013-08-21 ソニー株式会社 画像処理装置、画像表示方法及び画像表示プログラム
JP5434569B2 (ja) * 2009-12-22 2014-03-05 ソニー株式会社 情報処理装置および方法、並びにプログラム
US8862663B2 (en) * 2009-12-27 2014-10-14 At&T Intellectual Property I, L.P. Method and system for providing a collaborative event-share service
US8527549B2 (en) * 2010-02-22 2013-09-03 Sookasa Inc. Cloud based operating and virtual file system
US8270684B2 (en) * 2010-07-27 2012-09-18 Google Inc. Automatic media sharing via shutter click
CN102694826B (zh) * 2011-03-22 2018-09-07 百度在线网络技术(北京)有限公司 一种用于获取与现实场景相关的共享对象的设备和方法
US8918463B2 (en) * 2011-04-29 2014-12-23 Facebook, Inc. Automated event tagging
US8606812B2 (en) * 2011-07-08 2013-12-10 Vanessa Paulisch Intelligent search
US10210586B2 (en) * 2011-09-09 2019-02-19 Facebook, Inc. Composited posting interface for social networking system
TWI534721B (zh) * 2011-10-19 2016-05-21 致伸科技股份有限公司 具有人臉辨識功能之相片分享系統
WO2013093186A2 (en) * 2011-12-22 2013-06-27 Nokia Corporation Method and apparatus for sharing media upon request via social networks
US9917892B2 (en) * 2012-03-31 2018-03-13 Intel Corporation Method, device, and system for AD-HOC resource selection
US20140019867A1 (en) * 2012-07-12 2014-01-16 Nokia Corporation Method and apparatus for sharing and recommending content
US20150116360A1 (en) * 2012-07-17 2015-04-30 Google Inc. Generating A Viewpoint On a Digital Map For a Point of Interest
US9069469B2 (en) * 2012-09-10 2015-06-30 Apple Inc. Sharing and synchronizing data across users of cloud computing systems
US20150199379A1 (en) * 2012-10-30 2015-07-16 Google Inc. Sorting and searching of related content based on underlying file metadata
JP5909801B2 (ja) * 2013-02-08 2016-04-27 株式会社Pfu 情報処理装置、情報処理システム、及びプログラム
US10133754B2 (en) * 2013-02-10 2018-11-20 Qualcomm Incorporated Peer-to-peer picture sharing using custom based rules for minimal power consumption and better user experience
CN104102656B (zh) * 2013-04-09 2016-08-03 腾讯科技(深圳)有限公司 好友推荐方法、装置、系统及服务器
JP2014219878A (ja) * 2013-05-09 2014-11-20 キヤノン株式会社 ユーザ端末、サーバ装置、情報共有方法及びプログラム
US9712577B2 (en) * 2013-06-09 2017-07-18 Apple Inc. Device, method, and graphical user interface for sharing content from a respective application
US9514331B2 (en) * 2013-07-03 2016-12-06 Facebook, Inc. Privacy model for shared collections of content on a social networking system
US10460151B2 (en) * 2013-09-17 2019-10-29 Cloudspotter Technologies, Inc. Private photo sharing system, method and network
JP5532180B1 (ja) * 2013-10-03 2014-06-25 富士ゼロックス株式会社 画像処理装置及びプログラム
US10466858B2 (en) * 2013-12-01 2019-11-05 Upskill, Inc. Systems and methods for interacting with a virtual menu
KR101488111B1 (ko) * 2013-12-02 2015-01-30 김홍석 사진공유 어플리케이션을 이용한 사진공유시스템
KR101534808B1 (ko) * 2013-12-30 2015-07-08 주식회사 시어스랩 얼굴 인식 기술을 이용한 전자 앨범 관리 방법 및 시스템
US8943140B1 (en) * 2014-03-26 2015-01-27 Ankit Dilip Kothari Assign photographers on an event invite and automate requesting, uploading, and sharing of photos and videos for an event
US9591039B2 (en) * 2014-06-01 2017-03-07 Apple Inc. Region based image sharing
US20160012738A1 (en) * 2014-07-10 2016-01-14 Neema Shafigh Interactive social learning network
US10389804B2 (en) * 2015-11-11 2019-08-20 Adobe Inc. Integration of content creation and sharing

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080052349A1 (en) * 2006-08-27 2008-02-28 Michael Lin Methods and System for Aggregating Disparate Batches of Digital Media Files Captured During an Event for the Purpose of Inclusion into Public Collections for Sharing
CN103635892A (zh) * 2011-07-07 2014-03-12 索尼电脑娱乐美国公司 自动创建用于分享照片的群体
CN103369031A (zh) * 2013-05-20 2013-10-23 华为技术有限公司 终端设备、电子相册服务器、照片分享系统及方法
CN104317932A (zh) * 2014-10-31 2015-01-28 小米科技有限责任公司 照片分享方法及装置
CN105069075A (zh) * 2015-07-31 2015-11-18 小米科技有限责任公司 照片共享方法和装置

Also Published As

Publication number Publication date
MX2016005074A (es) 2017-05-04
RU2016131883A (ru) 2018-02-06
EP3125179A1 (en) 2017-02-01
CN105069075B (zh) 2018-02-23
CN105069075A (zh) 2015-11-18
JP6305654B2 (ja) 2018-04-04
RU2654168C2 (ru) 2018-05-16
KR101759454B1 (ko) 2017-07-18
KR20170023747A (ko) 2017-03-06
MX385157B (es) 2025-03-14
JP2017529639A (ja) 2017-10-05
US20170032188A1 (en) 2017-02-02

Similar Documents

Publication Publication Date Title
WO2017020484A1 (zh) 照片共享方法和装置
US11651619B2 (en) Private photo sharing system, method and network
CN105095873B (zh) 照片共享方法、装置
US8810684B2 (en) Tagging images in a mobile communications device using a contacts list
KR101972504B1 (ko) 이미지 공유 방법 및 장치, 그리고 단말 장치
CN105429848A (zh) 通过拍照添加好友的方法、系统和社交服务器的社交系统
CN102819726A (zh) 用于移动终端的照片处理系统及方法
CN103369031A (zh) 终端设备、电子相册服务器、照片分享系统及方法
US20150006637A1 (en) Media Sharing
CN105005597A (zh) 一种照片分享方法及移动终端
US20160050704A1 (en) Image linking and sharing
WO2016146060A1 (zh) 照片的分享方法及装置
CN105635256B (zh) 多媒体同步方法、装置和系统
CN105989345A (zh) 图像匹配发现好友的方法和装置
WO2018133354A1 (zh) 一种信息获取方法及获取设备
CN112235181A (zh) 弱社交方法、客户端及系统
KR20180068054A (ko) 차량 탑승자 간 자료 공유 방법 및 그 시스템
CN105897570A (zh) 推送方法及装置
KR102618749B1 (ko) 명함 관리시스템
KR20120080379A (ko) 디지털 카메라의 이미지 어노테이션 처리 방법 및 장치
JP6646090B2 (ja) 携帯情報端末
JP2017118467A (ja) 撮影時刻認証システム及び撮影アプリケーション
KR20140077755A (ko) 영상 촬영 장치 및 영상 데이터의 자동 네이밍 방법
CN103297500B (zh) 通过软体跳转的联系人添加方法及系统
CN121334097A (zh) 资源包发送方法、装置、计算机设备

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2017531947

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20167004020

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/005074

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016131883

Country of ref document: RU

Kind code of ref document: A

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

Ref document number: 15900250

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

Country of ref document: EP

Kind code of ref document: A1