[go: up one dir, main page]

WO2018076840A1 - Procédé de partage de données, dispositif, support de stockage et serveur - Google Patents

Procédé de partage de données, dispositif, support de stockage et serveur Download PDF

Info

Publication number
WO2018076840A1
WO2018076840A1 PCT/CN2017/094815 CN2017094815W WO2018076840A1 WO 2018076840 A1 WO2018076840 A1 WO 2018076840A1 CN 2017094815 W CN2017094815 W CN 2017094815W WO 2018076840 A1 WO2018076840 A1 WO 2018076840A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
identity information
user data
information
sharing
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/CN2017/094815
Other languages
English (en)
Chinese (zh)
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of WO2018076840A1 publication Critical patent/WO2018076840A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-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/18—Commands or executable codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/212—Monitoring or handling of messages using filtering or selective blocking

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a data sharing method, apparatus, storage medium, and server.
  • the way of storing user data has gradually changed from hardware storage (such as mobile hard disk, U disk) to cloud server storage.
  • the user can store the user data in the cloud server anytime and anywhere through the client of the cloud server in the mobile terminal, and the user can also share the user data in the cloud server to other users.
  • the embodiment of the invention provides a data sharing method, device, storage medium and server, which can improve the convenience of data sharing.
  • an embodiment of the present invention provides a data sharing method, including:
  • an embodiment of the present invention provides a data sharing apparatus, including:
  • a first obtaining unit configured to acquire a request for sharing request sent by the first client, where the request for sharing includes the first client identity information and the second client identity information;
  • a reading unit configured to read an association list according to the second client identity information, where the association list includes a correspondence between the identifier information of the user data of the second client and the client identity information;
  • a second acquiring unit configured to acquire, according to the association list, identifier information of user data corresponding to the first client identity information
  • And generating a sending unit configured to generate a user data sharing link according to the identifier information, and send the user data sharing link to the first client.
  • an embodiment of the present invention provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are adapted to be loaded by a processor to execute the data sharing method.
  • an embodiment of the present invention provides a server, including a processor and a memory, the processor is electrically connected to the memory, the memory is used to store instructions and data, and the processor is configured to perform the foregoing data sharing. method.
  • the embodiment of the invention provides a data sharing method, device, storage medium and server, which can improve the convenience of data sharing.
  • FIG. 1 is a schematic diagram of a scenario of a data sharing system according to an embodiment of the present invention.
  • FIG. 2 is a flow chart of a data sharing method of the present invention.
  • FIG. 3 is still another flowchart of the data sharing method of the present invention.
  • FIG. 4 is a schematic structural diagram of a data sharing apparatus according to the present invention.
  • FIG. 5 is still another schematic structural diagram of a data sharing apparatus according to the present invention.
  • FIG. 6 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • first, second, and the like in the present invention may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another.
  • a first control may be referred to as a second control, and similarly, a second control may be referred to as a first control, without departing from the scope of the present invention.
  • Both the first control and the second control are controls, but they are not the same control.
  • the terms “comprises” and “comprising” and “comprising” are intended to cover a non-exclusive inclusion.
  • An embodiment of the present invention provides a data sharing method, including:
  • the method before the obtaining the request for sharing sent by the first client, the method further includes:
  • the step of reading the association list according to the second client identity information comprises:
  • the associated list is read from the storage area.
  • the step of acquiring the identification information of the user data to be shared corresponding to the first client identity information according to the association list comprises:
  • the identifier information corresponding to the found client identity information is determined as the identifier information of the user data to be shared corresponding to the first client identity information.
  • the method before the obtaining the identification information of the user data to be shared corresponding to the first client identity information according to the association list, the method further includes:
  • the identifier information of the user data to be shared corresponding to the first client identity information is obtained according to the association list.
  • the method further includes:
  • the second client If the second client is in the login state, generating sharing request prompt information according to the first client identity information, and sending the sharing request prompt information to the second client;
  • the method further includes:
  • the data sharing system mainly includes a cloud server and a terminal, and the cloud server and the terminal can be connected through a wired or wireless network.
  • FIG. 1 is a schematic diagram of a data sharing system according to an embodiment of the present invention.
  • the data sharing system includes a cloud server and a terminal, wherein the cloud server integrates the data sharing device provided by the present invention, and the cloud server stores the user.
  • the first client and the second client in the present invention are installed in the terminal, and the terminal in which the first client is built is shown in FIG. 1 , and the terminal in which the second client is built is not shown in FIG. 1 .
  • the terminal can be an electronic device such as a mobile phone or a tablet computer.
  • the first client user When the first client user needs to access the user data of the second client, the first client user sends a request for sharing to the cloud server through the first client.
  • the cloud server will obtain the request for sharing from the first client.
  • the request sharing request includes first client identity information and second client identity information.
  • the cloud server After obtaining the request for sharing, the cloud server obtains the first client identity information and the second client identity information in the request for sharing by parsing, and reads the second client according to the second client identity information.
  • the association list includes a correspondence between the identification information of the user data of the second client and the identity information of the client.
  • the first client can browse or download the corresponding user data of the second client by clicking the user data sharing link.
  • the embodiment provides a data sharing method, including: acquiring a request sharing request sent by a first client, where the requesting sharing request includes first client identity information and second client identity information; The client identity information reads the association list, where the association list includes a correspondence between the identification information of the user data of the second client and the client identity information; and the association list is obtained according to the identity information of the first client. And identifying information about the user data to be shared; and generating a user data sharing link according to the identification information, and sending the user data sharing link to the first client.
  • FIG. 2 is a flowchart of a data sharing method according to the present invention.
  • the data sharing method is applied to the cloud server.
  • the data sharing method can also be applied to other devices, and is not specifically limited herein.
  • step S101 the request sharing request sent by the first client is obtained, where the request sharing request includes the first client identity information and the second client identity information.
  • the first client When the first client user needs to request the user data of the second client user, according to the operation of the first client user, the first client generates a request for sharing and sends the request for sharing to the cloud server.
  • the cloud server will get the request for sharing.
  • the request for sharing includes the first client identity information and the second client identity information.
  • the client identity information includes the client username, the client user phone number, the registered mailbox, and the like, and the specific content of the client identity information is not limited herein.
  • the first client user when the first client user needs to request user data of the second client user, the first client user clicks on the request sharing portal in the first client page.
  • the first client will pop up a dialog box prompting the user to enter the second client identity information.
  • the first client user enters a second client user phone number at a corresponding location in the dialog box.
  • the OK button the first client automatically obtains the first client identity information, and generates a request for sharing according to the first client identity information and the second client user phone number, and requests the request
  • the sharing request is sent to the cloud server.
  • step S102 the association list is read according to the second client identity information, where the association list includes a correspondence between the identity information of the user data of the second client and the client identity information.
  • the cloud server After receiving the request for sharing by the first client, the cloud server obtains the first client identity information and the second client identity information by parsing the request sharing request. At the same time, the storage area of the cloud server corresponding to the second client corresponding to the second client is searched according to the second client identity information, and the association list set by the second client user is read from the storage area.
  • the association list includes a correspondence between the identifier information of the user data synchronized by the second client to the cloud server and the client identity information.
  • the second client user sets a sharing object for synchronizing the user data in the cloud server.
  • the second client user sets the sharing object of the 100 life photos as the mother's mobile phone number, that is, the second client user desires that the 100 life photos are associated with the mother's mobile phone number.
  • the second client user clicks the confirmation button the second client generates an association list according to the identification information of the 100 life photos and the mobile phone number of the mother, and sends the association list to the cloud server, and the cloud server stores the association. List.
  • the identification information of the user data may be a storage address of the user data in the cloud server, and may of course be other information that plays a role of identification, as long as the cloud server can find the corresponding user data according to the identification information. No specific restrictions are made here.
  • step S103 the identifier information of the user data to be shared corresponding to the first client identity information is acquired according to the association list.
  • the cloud server After the cloud server reads the association list preset by the second client user, the identifier information of the user data to be shared corresponding to the first client identity information is obtained according to the association list. Specifically, the cloud server searches for the client identity information that matches the first client identity information in the association list, and uses the identity information corresponding to the client identity information as the to-be-shared corresponding to the first client identity information. Identification information of user data.
  • the first client identity information is the mom's mobile phone number
  • the cloud server searches for the client matching the mom's mobile phone number in the read association list. End identity information to obtain identification information of the 100 life photos. It can be understood that the 100 life photos are user data to be shared.
  • step S104 a user data sharing link is generated according to the identification information, and the user data sharing link is sent to the first client.
  • the cloud server finds the identifier information corresponding to the first client identity information, the user data sharing link is generated according to the identifier information, and the user data sharing link is sent to the first client, so that the first client user passes Click the user data sharing link to get the user data stored in the cloud server by the second client.
  • the data sharing method in this embodiment is configured to obtain a request for sharing by the first client, where the request for sharing includes the first client identity information and the second client identity information; according to the second client identity
  • the information reading association list, wherein the association list includes a correspondence between the identification information of the user data of the second client and the client identity information; and the to-be-shared corresponding to the identity information of the first client is obtained according to the association list.
  • Identification information of the user data and generating a user data sharing link according to the identification information, and transmitting the user data sharing link to the first client.
  • the cloud server shares the corresponding user data with the first client user according to the association list set by the second client user in advance.
  • the second client user does not need to log in to the client to share and other operations, which brings convenience to data sharing and enhances user satisfaction in the data sharing process.
  • FIG. 3 is still another flowchart of the data sharing method of the present invention.
  • the data sharing method is applied to the cloud server.
  • the data sharing method can also be applied to other devices, and is not specifically limited herein.
  • the data sharing method comprises:
  • Step S201 Acquire user data of the second client.
  • Step S202 Acquire the identification information of the user data, and obtain an association list generated by the second client according to the correspondence between the identifier information and the client identity information.
  • Step S203 Acquire a request for sharing request sent by the first client, where the request for sharing includes the first client identity information and the second client identity information;
  • Step S204 The association list is read according to the second client identity information, where the association list includes a correspondence between the identifier information of the user data of the second client and the client identity information.
  • Step S205 determining whether the first client identity information exists in the association list; if the first client identity information exists, performing step S206; if the first client identity information is not present, executing Step S208;
  • Step S206 Acquire, according to the association list, identifier information of the user data to be shared corresponding to the first client identity information.
  • Step S207 Generate a user data sharing link according to the identifier information, and send the user data sharing link to the first client;
  • Step S208 determining whether the second client is in the login state; if the second client is in the login state, step S209 is performed; if the second client is not in the login state, executing step S212;
  • Step S210 Acquire an operation instruction that is feedback by the second client according to the sharing request prompt information
  • Step S211 determining whether there is identification information of the user data to be shared in the operation instruction; if there is identification information of the user data to be shared in the operation instruction, step S207 is performed; if the operation instruction does not exist After the identification information of the shared user data is described, step S212 is performed;
  • Step S212 Send prompt information that cannot access the second client user data to the first client.
  • step S201 and step S202 after the second client user logs in to the client of the cloud server, the user data in the terminal is uploaded to the cloud server through the upload button in the client.
  • the cloud server will obtain the user data sent by the second client, and store the user data at the corresponding location of the cloud server.
  • the cloud server obtains the identification information of the user data, and sends the identification information of the user data to the second client.
  • the identification information of the user data may be a storage address of the user data in the cloud server, and may of course be other information that plays a role of identification, as long as the cloud server can find the corresponding user data according to the identification information. No specific restrictions are made here.
  • the second client user After the second client user synchronizes the user data to the cloud server, the second client user sets a sharing object for the user data synchronized to the cloud server, wherein setting the sharing object refers to allocating other client identity information to the user data.
  • the second client After the second client user finishes setting the sharing object for the user data, the second client generates an association list according to the identification information of the user data acquired from the cloud server and the client identity information corresponding thereto, and sends the association list. To the cloud server.
  • the second client user sets the sharing object of 100 life photos as the mobile phone number of the mother, that is, the 100 life photos will be associated with the mother's mobile phone number.
  • the second client user clicks the confirmation button the second client generates an association list according to the identification information of the 100 life photos acquired from the cloud server and the mobile phone number of the mother, and sends the association list to the cloud server.
  • the cloud server obtains the association list and stores the association list, wherein the association list is used in a subsequent data sharing process.
  • the identification information of one user data may correspond to multiple client identity information.
  • the identification information of multiple user data may also correspond to a client identity information, where No specific restrictions are imposed.
  • the identity information of the client corresponding to the identification information of each user data is not limited to one type.
  • the identification information of each user data may correspond only to the user phone number in the client identity information, or each The identification information of the user data corresponds to multiple identity information such as the user name, the user's phone number, and the registered mailbox in the client identity information, and no specific restrictions are imposed herein.
  • step S203 when the first client user needs to request the user data of the second client user, according to the operation of the first client user, the first client generates a request for sharing and sends the request for sharing.
  • the cloud server will get the request for sharing.
  • the request for sharing includes the first client identity information and the second client identity information.
  • the client identity information includes the client username, the client user phone number, the registered mailbox, and the like, and the specific content of the client identity information is not limited herein.
  • the first client user when the first client user needs to request user data of the second client user, the first client user clicks on the request sharing portal in the first client page.
  • the first client will pop up a dialog box prompting the user to enter the second client identity information.
  • the first client user enters a second client user phone number at a corresponding location in the dialog box.
  • the OK button the first client automatically obtains the first client identity information, and generates a request for sharing according to the first client identity information and the second client user phone number, and requests the request
  • the sharing request is sent to the cloud server.
  • step S204 after receiving the request for sharing by the first client, the cloud server obtains the first client identity information and the second client identity information by parsing the request sharing request.
  • the storage area of the cloud server corresponding to the second client corresponding to the second client is searched according to the second client identity information, and the association list preset by the second client user is read from the storage area.
  • the association list includes a correspondence between the identifier information of the user data synchronized by the second client to the cloud server and the client identity information.
  • step S205 after the cloud server reads the association list stored in the server by the second client, it is determined whether the first client identity information exists in the association list. For example, when the first client identity information is a user phone number, the cloud server will determine whether the user phone number exists in the association list.
  • step S205 if the cloud server determines that the first client identity information exists in the association list, the identifier information of the user data to be shared corresponding to the first client identity information is obtained according to the association list, that is, Step S206 is performed.
  • step S206 after reading the association list preset by the second client user, the cloud server acquires the identifier information of the user data to be shared corresponding to the first client identity information according to the association list. Specifically, the cloud server searches for the client identity information that matches the first client identity information in the association list, and uses the identity information corresponding to the client identity information as the to-be-shared corresponding to the first client identity information. Identification information of user data.
  • the first client identity information is the mom's mobile phone number
  • the cloud server searches for the client matching the mom's mobile phone number in the read association list. End identity information to obtain identification information of the 100 life photos. It can be understood that the 100 life photos are user data to be shared.
  • step S207 after the cloud server finds the identifier information corresponding to the first client identity information, the user data sharing link is generated according to the identifier information, and the user data sharing link is sent to the first client, so that the first A client user can obtain user data stored in the cloud server by the second client by clicking the user data sharing link.
  • step S208 is a data sharing method in the case where the first client identity information exists in the association list. If the cloud server determines that the first client identity information does not exist in the association list, the cloud server further determines whether the second client is in the login state, that is, step S208 is performed.
  • step S208 if the cloud server determines that the second client is not in the login state, the cloud server sends a prompt message to the first client, where the prompt information is used to prompt the first client user to access the second client. End user data, that is, step S212 is performed.
  • the cloud server determines that the second client is in the login state, the cloud server generates the sharing request prompt information according to the first client identity information, and sends the sharing request prompt information to the second client, that is, step S209 is performed.
  • the sharing request prompt information includes the first client identity information, so that after the second client user views the sharing request prompt information, the second client user needs to access the user data. If the second client user wants the first client user to access the user data, after the second client user selects the user data to be shared, the second client obtains the identification information of the user data to be shared, and according to the to-be-shared The identification information of the user data generates an operation instruction containing the identification information, and sends the operation instruction containing the identification information to the cloud server.
  • the operation instruction containing the identification information may be composed only of the identification information of the user data to be shared, or may be the identification information of the user data to be shared and other
  • the instruction consists of.
  • an acceptance button is provided in the sharing request prompt information. If the second client user agrees to share the user data, the second client user clicks the accept button, and the second client will identify the user data according to the information to be shared. Click the operation information of the accept button to generate an operation instruction containing the identification information.
  • the second client If the second client user does not want the first client user to access the user data, the second client generates an operation instruction that does not include the identification information according to the operation of the second client user, and sends the operation that does not include the identification information.
  • Command to the cloud server For example, a rejection button is provided in the sharing request prompt information. If the second client user does not agree to share the user data, the second client user clicks the reject button, and the second client obtains the operation information of the click rejection button. , an empty operation instruction will be generated, and the empty operation instruction will be sent to the cloud server.
  • the cloud server obtains an operation instruction that is feedback from the second client according to the sharing request prompt information, and determines whether there is identification information of the user data to be shared in the operation instruction. If there is any identification information of the user data to be shared, that is, the operation instruction at this time is an operation instruction containing the identification information, the second client user wants to share the to-share user data corresponding to the identification information to the first client user.
  • the cloud server performs step S207, that is, generates a user data sharing link according to the identification information, and sends a user data sharing link to the first client, so that the first client user can browse or click the data sharing link.
  • the user data to be shared is downloaded, so that data sharing can still be realized if the first client identity information does not have an associated list.
  • step S212 If the cloud server determines that there is no identification information of the user data to be shared in the operation instruction, that is, the operation instruction is an empty operation instruction, indicating that the second client user does not want to share the data to the first client user. At this time, the cloud server sends a prompt message that the second client user data cannot be accessed to the first client, that is, step S212 is performed.
  • the first user logs in to the first client through the computer and uploads the training materials in the computer to the cloud server.
  • the first user's colleague ie, the second user
  • the second user will log in to the second client and click the request sharing button in the second client page.
  • the second client will pop up a dialog box.
  • the second user enters the first user's phone number in the dialog box and clicks the confirmation button.
  • the second client will automatically obtain the identity information of the second client, and generate a request for sharing according to the identity information of the second client and the phone number of the first user.
  • the second client will send the request for sharing to the cloud server.
  • the cloud server After receiving the request for sharing, the cloud server obtains the identity information of the second client and the phone number of the first user through parsing. Finding a corresponding first client according to the first user's phone number, and then searching for an area where the first client's user data is stored. The associated list is read from this storage area.
  • the first user does not set the sharing scope of the training data when the first user uploads the training data to the cloud server, that is, the identification information corresponding to the training data does not exist in the association list of the first user; or the first user pairs training
  • the identification information corresponding to the training data is not corresponding to the second client identity information, that is, the second client identity information does not exist in the association list.
  • the cloud server determines that the second client identity information does not exist in the association list. At this point, the cloud server will continue to determine whether the first client is in the login state. If the first user is using the client at this time, the cloud server generates a sharing request prompt message according to the second client identity information, and sends the message to the first client. The first client knows that the second user needs his training materials according to the sharing request prompt information.
  • the first user clicks the accept button in the sharing request prompt information field.
  • the first client pops up a selection dialog box for the first user to select the corresponding user data to be shared.
  • the first user clicks on the training profile folder and clicks the OK button.
  • the first client will obtain the identification information of the training material, and generate an operation instruction according to the identification information, and simultaneously send the operation instruction to the cloud server.
  • the cloud server obtains the operation instruction according to the operation instruction, and determines that the operation instruction includes the identification information of the user data to be shared.
  • the cloud server generates a user data sharing link according to the identification information, and sends a user data sharing link to the second client. In this way, the second user can browse or download the training materials by clicking on the data sharing link.
  • the data sharing method provided by the embodiment of the present invention may enable the first client user to share the corresponding user data to the first user according to the association list set by the second client user when the second client user data needs to be accessed.
  • the client user in the sharing process, the second client user does not need to log in to the client to share operations, etc., which brings convenience to data sharing and enhances user satisfaction in the data sharing process.
  • the cloud server sends the generated sharing request prompt information to the second client after determining that the second client is in the login state, so that the second client The user data can be shared to the first client in time according to the sharing request prompt information. In this way, even if the first client identity information does not exist in the association list, the first client user can obtain the desired user data by using the method, so that the entire sharing process is more rationalized.
  • the embodiment of the invention further provides a data sharing device, comprising:
  • a first obtaining unit configured to acquire a request for sharing request sent by the first client, where the request for sharing includes the first client identity information and the second client identity information;
  • a reading unit configured to read an association list according to the second client identity information, where the association list includes a correspondence between the identifier information of the user data of the second client and the client identity information;
  • a second acquiring unit configured to acquire, according to the association list, identifier information of the user data to be shared corresponding to the first client identity information
  • And generating a sending unit configured to generate a user data sharing link according to the identifier information, and send the user data sharing link to the first client.
  • the data sharing device further includes a third obtaining unit, where the third acquiring unit is configured to:
  • the reading unit is for:
  • the associated list is read from the storage area.
  • the second obtaining unit is configured to:
  • the identifier information corresponding to the found client identity information is determined as the identifier information of the user data to be shared corresponding to the first client identity information.
  • the data sharing device further includes a first determining unit
  • the first determining unit is configured to determine whether the first client identity information exists in the association list
  • the second acquiring unit is configured to: if the first client identity information exists in the association list, obtain, according to the association list, identifier information of user data corresponding to the first client identity information.
  • the data sharing apparatus further includes a second determining unit, wherein the second determining unit includes a first determining subunit, a generating transmitting subunit, an obtaining subunit, and a second judging subunit;
  • the first determining subunit is configured to determine whether the second client is in a login state if the first client identity information does not exist in the association list;
  • the generating and sending subunit is configured to generate sharing request prompt information according to the first client identity information, and send the sharing request prompt information to the second client, if the second client is in a login state ;
  • the obtaining subunit is configured to acquire an operation instruction that is sent by the second client according to the sharing request prompt information
  • the second determining subunit is configured to determine whether the identification information of the user data to be shared exists in the operation instruction
  • the generating and sending unit is specifically configured to: if the identification information of the user data to be shared exists in the operation instruction, generate a user data sharing link according to the identification information, and send the user data sharing link to the first Client.
  • the second determining unit further includes a prompting subunit; the prompting subunit is configured to send the inaccessible information if the identification information of the user data to be shared does not exist in the operation instruction Two prompt information of the client user data to the first client.
  • FIG. 4 is a schematic structural diagram of a data sharing apparatus according to the present invention.
  • the data sharing device 300 is applied to a cloud server.
  • the data sharing device 300 can also be applied to other devices, and is not specifically limited herein.
  • the data sharing device 300 includes a first obtaining unit 310, a reading unit 320, a second obtaining unit 330, and a generating transmitting unit 340.
  • the obtaining unit 310 is configured to obtain a request sharing request sent by the first client, where the request for sharing includes the first client identity information and the second client identity information
  • the reading unit 320 is configured to use the second
  • the client identity information reads the association list, where the association list includes the correspondence between the identification information of the user data of the second client and the client identity information
  • the second obtaining unit 330 is configured to obtain, according to the association list, the The identification information of the user data corresponding to the client identity information
  • the generation sending unit 340 is configured to generate a user data sharing link according to the identifier information, and send the user data sharing link to the first client.
  • the data sharing device 300 in the above embodiment will be described in detail below with reference to FIG.
  • the first client When the first client user needs to request the user data of the second client user, according to the operation of the first client user, the first client generates a data requesting the sharing request and sending the request for sharing to the cloud server. Sharing device 300.
  • the first obtaining unit 310 in the data sharing device 300 will acquire the request sharing request.
  • the request for sharing includes the first client identity information and the second client identity information.
  • the client identity information includes the client username, the client user phone number, the registered mailbox, and the like, and the specific content of the client identity information is not limited herein.
  • the first client user when the first client user needs to request user data of the second client user, the first client user clicks on the request sharing portal in the first client page.
  • the first client will pop up a dialog box prompting the user to enter the second client identity information.
  • the first client user enters a second client user phone number at a corresponding location in the dialog box.
  • the OK button the first client automatically obtains the first client identity information, and generates a request for sharing according to the first client identity information and the second client user phone number, and requests the request
  • the sharing request is sent to the data sharing device 300 of the cloud server.
  • the first client identity information and the second client identity information are obtained by parsing the request sharing request.
  • the first obtaining unit 310 transmits the first client identity information and the second client identity information to the reading unit 320.
  • the reading unit 320 searches the storage area of the cloud server corresponding to the second client corresponding to the second client identity information, and reads the association list set by the second client user from the storage area.
  • the association list includes a correspondence between the identifier information of the user data synchronized by the second client to the cloud server and the client identity information.
  • the second client user sets a sharing object for synchronizing the user data in the cloud server.
  • the second client user sets the sharing object of the 100 life photos as the mother's mobile phone number, that is, the second client user desires that the 100 life photos are associated with the mother's mobile phone number.
  • the second client user clicks the confirmation button the second client generates an association list according to the identification information of the 100 life photos and the mobile phone number of the mother, and sends the association list to the cloud server, and the cloud server stores the association. List.
  • the identification information of the user data may be a storage address of the user data in the cloud server, and may of course be other information that plays a role of identification, as long as the cloud server can find the corresponding user data according to the identification information. No specific restrictions are made here.
  • the reading unit 320 After reading the association list preset by the second client user, the reading unit 320 sends the association list and the first client identity information to the second obtaining unit 330.
  • the second obtaining unit 330 will acquire the identification information of the user data to be shared corresponding to the first client identity information according to the association list. Specifically, the second obtaining unit 330 searches for the client identity information that matches the first client identity information in the association list, and the identifier information corresponding to the client identity information is associated with the first client identity information. Identification information of the user data to be shared.
  • the first client identity information is the mom's mobile phone number
  • the second obtaining unit 330 searches for the client matching the mom's mobile phone number in the association list. End identity information to obtain identification information of the 100 life photos. It can be understood that the 100 life photos are user data to be shared.
  • the data sharing device 300 acquires the request sharing request sent by the first client by using the first obtaining unit 310, wherein the request sharing request includes the first client identity information and the second client identity information;
  • the unit 320 reads the association list according to the second client identity information, where the association list includes the correspondence between the identification information of the user data of the second client and the client identity information; and the second obtaining unit 330 is configured according to the association list.
  • the data sharing device 300 can share the corresponding user data with the first client user according to the association list set by the second client user when the first client user needs to access the second client user data, and share the corresponding user data.
  • the second client user does not need to log in to the client to share and other operations, which brings convenience to data sharing and enhances user satisfaction in the data sharing process.
  • FIG. 5 is still another schematic structural diagram of a data sharing apparatus according to the present invention.
  • the data sharing device 400 is applied to a cloud server.
  • the data sharing device 400 can also be applied to other devices, and is not specifically limited herein.
  • the data sharing apparatus 400 includes: a third obtaining unit 410, a first obtaining unit 420, a reading unit 430, a first determining unit 440, a second obtaining unit 450, a generating transmitting unit 460, and a second determining unit. 470.
  • the second determining unit 470 includes a first determining subunit 471, a generating transmitting subunit 472, an obtaining subunit 473, a second judging subunit 474, and a prompting subunit 475.
  • the data sharing device 400 in the above embodiment will be described in detail below with reference to FIG.
  • the user data in the terminal is uploaded to the cloud server through the upload button in the client.
  • the third obtaining unit 410 in the cloud server will acquire the user data sent by the second client, and store the user data at a corresponding location of the cloud server.
  • the third obtaining unit 410 will acquire the identification information of the user data, and send the identification information of the user data to the second client.
  • the identification information of the user data may be a storage address of the user data in the cloud server, and may of course be other information that plays a role of identification, as long as the cloud server can find the corresponding user data according to the identification information. No specific restrictions are made here.
  • the second client user After the second client user synchronizes the user data to the cloud server, the second client user sets a sharing object for the user data synchronized to the cloud server, wherein setting the sharing object refers to allocating other client identity information to the user data.
  • the second client After the second client user finishes setting the sharing object for the user data, the second client generates an association list according to the identification information of the user data acquired from the third obtaining unit 410 and the client identity information corresponding thereto, and the The associated list is sent to the cloud server.
  • the third obtaining unit 410 in the cloud server will acquire the association list.
  • the second client user sets the sharing object of 100 life photos as the mobile phone number of the mother, that is, the 100 life photos will be associated with the mother's mobile phone number.
  • the second client user clicks the confirmation button the second client generates an association list according to the identification information of the 100 life photos acquired from the cloud server and the mobile phone number of the mother, and sends the association list to the cloud server.
  • the third obtaining unit 410 acquires the association list and stores the association list, wherein the association list is used in a subsequent data sharing process.
  • the identification information of one user data may correspond to multiple client identity information.
  • the identification information of multiple user data may also correspond to a client identity information, where No specific restrictions are imposed.
  • the identity information of the client corresponding to the identification information of each user data is not limited to one type.
  • the identification information of each user data may correspond only to the user phone number in the client identity information, or each The identification information of the user data corresponds to multiple identity information such as the user name, the user's phone number, and the registered mailbox in the client identity information, and no specific restrictions are imposed herein.
  • the first client When the first client user needs to request the user data of the second client user, according to the operation of the first client user, the first client generates a data requesting the sharing request and sending the request for sharing to the cloud server. Sharing device 400.
  • the first obtaining unit 420 in the data sharing device 400 will acquire the request sharing request.
  • the request for sharing includes the first client identity information and the second client identity information.
  • the client identity information includes the client username, the client user phone number, the registered mailbox, and the like, and the specific content of the client identity information is not limited herein.
  • the first client user when the first client user needs to request user data of the second client user, the first client user clicks on the request sharing portal in the first client page.
  • the first client will pop up a dialog box prompting the user to enter the second client identity information.
  • the first client user enters a second client user phone number at a corresponding location in the dialog box.
  • the OK button the first client automatically obtains the first client identity information, and generates a request for sharing according to the first client identity information and the second client user phone number, and requests the request
  • the sharing request is sent to the data sharing device 400 of the cloud server.
  • the first client identity information and the second client identity information are obtained by parsing the request sharing request, and the obtained first client is obtained.
  • the identity information and the second client identity information are sent to the reading unit 430.
  • the reading unit 430 searches the storage area of the cloud server corresponding to the second client corresponding to the second client identity information, and reads the association list preset by the second client user from the storage area.
  • the association list includes a correspondence between the identifier information of the user data synchronized by the second client to the cloud server and the client identity information.
  • the reading unit 430 passes the read association list, the first client identity information, and the second client identity information to the first determining unit 440.
  • the first determining unit 440 will determine whether the first client identity information exists in the associated list. For example, when the first client identity information is the user phone number, the first determining unit 440 determines whether the user phone number exists in the association list.
  • the first determining unit 440 determines that the first client identity information exists in the association list, the first determining unit 440 passes the association list and the first client identity information to the second acquiring unit 450.
  • the second obtaining unit 450 acquires the identification information of the user data to be shared corresponding to the first client identity information according to the association list.
  • the second obtaining unit 450 searches for the client identity information that matches the first client identity information in the association list, and uses the identifier information corresponding to the client identity information as the first client identity information. Identification information of the user data to be shared.
  • the first client identity information is the mom's mobile phone number
  • the second obtaining unit 450 searches for the mobile phone number of the mom in the read association list. Matching client identity information to obtain identification information of the 100 life photos. It can be understood that the 100 life photos are user data to be shared.
  • the second obtaining unit 450 finds the identification information corresponding to the first client identity information
  • the second obtaining unit 450 passes the identification information and the first client identity information to the generation sending unit 460.
  • the generating and sending unit 460 generates a user data sharing link according to the identification information, and sends the user data sharing link to the first client, so that the first client user can obtain the second client by clicking the user data sharing link.
  • User data within the cloud server User data within the cloud server.
  • the foregoing step is a data sharing method in a case where the first determining unit 440 determines that the first client identity information exists in the associated list. If the first determining unit 440 determines that the first client identity information does not exist in the association list, the first determining unit 440 sends the first signal, the first client to the first determining subunit 471 in the second determining unit 470. The end identity information and the second client identity information are such that the first determining subunit 471 determines whether the second client is in the login state according to the first signal.
  • the first determining subunit 471 determines that the second client is not in the login state, the first determining subunit 471 sends the second signal and the first client identity information to the prompting subunit 475, so that the prompting subunit 475 is according to the first
  • the second signal sends the prompt information to the first client, where the prompt information is used to prompt the first client user to access the second client user data.
  • the first determining subunit 471 determines that the second client is in the login state, the first determining subunit 471 sends the third signal, the first client identity information, and the second client identity information to the generating and transmitting subunit 472, so that After receiving the third signal, the generating and sending subunit 472 generates the sharing request prompt information according to the first client identity information, and sends the sharing request prompt information to the second client.
  • the sharing request prompt information includes the first client identity information, so that after the second client user views the sharing request prompt information, the second client user needs to access the user data. If the second client user wants the first client user to access the user data, after the second client user selects the user data to be shared, the second client obtains the identification information of the user data to be shared, and according to the to-be-shared
  • the identification information of the user data generates an operation instruction including the identification information, and transmits the operation instruction including the identification information to the data sharing device 400.
  • the acquisition sub-unit 473 of the data sharing device 400 will acquire the operation instruction and deliver the acquired operation instruction to the second determination sub-unit 474.
  • the operation instruction containing the identification information may be composed only of the identification information of the user data to be shared, or may be the identification information of the user data to be shared and other
  • the instruction consists of.
  • an acceptance button is provided in the sharing request prompt information. If the second client user agrees to share the user data, the second client user clicks the accept button, and the second client will identify the user data according to the information to be shared. Click the operation information of the accept button to generate an operation instruction containing the identification information.
  • the second client If the second client user does not want the first client user to access the user data, the second client generates an operation instruction that does not include the identification information according to the operation of the second client user, and sends the operation that does not include the identification information. Command to the cloud server.
  • the acquisition subunit 473 will acquire the operation instruction. For example, a rejection button is provided in the sharing request prompt information. If the second client user does not agree to share the user data, the second client user clicks the reject button, and the second client obtains the operation information of the click rejection button. , an empty operation instruction will be generated, and the empty operation instruction will be sent to the cloud server.
  • the second determining sub-unit 474 determines whether there is identification information of the user data to be shared in the operation instruction. If there is any identification information of the user data to be shared, that is, the operation instruction at this time is an operation instruction containing the identification information, the second client user wants to share the to-share user data corresponding to the identification information to the first client user. At this time, the second determining sub-unit 474 will send the fourth signal, the identification information, and the first client identity information to the generation sending unit 460, so that the generation sending unit 460 generates the user data according to the identification information after acquiring the fourth signal.
  • the second determining sub-unit 474 determines that there is no identification information of the user data to be shared in the operation instruction, that is, the operation instruction is an empty operation instruction, indicating that the second client user does not want to share the data to the first client user. .
  • the second judging subunit 474 will send the fifth signal and the first client identity information to the prompting subunit 475, so that the prompting subunit 475 sends the prompt information that the second client user data cannot be accessed according to the fifth signal to The first client.
  • the data sharing device 400 provided by the embodiment of the present invention can enable the first client user to share the corresponding user data according to the association list set by the second client user when the second client user data needs to be accessed.
  • the second client user does not need to log in to the client to share and other operations, which brings convenience to data sharing and enhances user satisfaction in the data sharing process.
  • the first determining sub-unit 471 sends the generated sharing request prompt information to the second after determining that the second client is in the login state. The client, so that the second client can share the user data to the first client in time according to the sharing request prompt information. In this way, even if the first client identity information does not exist in the association list, the first client user can obtain the desired user data by using the method, so that the entire sharing process is more rationalized.
  • FIG. 6 is a schematic structural diagram of a server 500 according to an embodiment of the present invention. :
  • the server 500 can include one or more processors 501 of processing cores, a memory 502 of one or more computer readable storage media, a communication unit 503, a power source 504, an input unit 505, and a display unit 506.
  • server structure illustrated in FIG. 6 does not constitute a limitation to the server, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements. among them:
  • Processor 501 is the control center of the server, connecting various portions of the server with various interfaces and lines, by running or executing software programs and/or modules stored in memory 502, and recalling data stored in memory 502, Execute the server's various functions and process data to monitor the server as a whole.
  • processor 501 can include one or more processing cores; in some embodiments, processor 501 can integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system, a user Interfaces, applications, etc., the modem processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 501.
  • the memory 502 can be used to store software programs and modules, the software programs stored in the memory 502 include instructions executable in the processor, and the processor 501 executes various functional applications by running software programs and modules stored in the memory 502, and data processing.
  • the communication unit 503 can be used for receiving and transmitting signals during transceiving information.
  • the communication unit 503 receives signals transmitted by the terminal and hands the signals to one or more processors 501 for processing.
  • the communication unit 503 transmits the feedback signal sent by the processor 501 to the terminal.
  • the server 500 also includes a power source 504 (such as a battery) that powers the various components.
  • the power source can be logically coupled to the processor 501 through a power management system to manage charging, discharging, and power management through the power management system. And other functions.
  • the power supply 504 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
  • the server 500 can also include an input unit 505 that can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • an input unit 505 can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • the server 500 can also include a display unit 506 that can be used to display information entered by the user or information provided to the user and various graphical user interfaces of the server, which can be represented by graphics, text, icons, videos. And any combination of them to constitute.
  • Display unit 508 can include a display panel, and in some embodiments, a liquid crystal display can be employed (LCD, Liquid Crystal Display), Organic Light Emitting Diode (OLED, Organic Light-Emitting) Diode) and other forms to configure the display panel.
  • LCD Liquid Crystal Display
  • OLED Organic Light Emitting Diode
  • the processor 501 in the server 500 loads the executable file corresponding to the process of one or more applications into the memory 502 according to the following instructions, and is executed by the processor 501 to be stored in the memory.
  • the application in 502 thus implementing various functions, as follows:
  • the list includes the correspondence between the identification information of the user data of the second client and the client identity information, and the identifier information of the user data to be shared corresponding to the first client identity information is obtained according to the association list;
  • the identification information generates a user data sharing link and sends the user data sharing link to the first client.
  • the processor 501 also runs an application stored in the memory 502, as follows: acquiring user data of the second client; acquiring identification information of the user data, and acquiring the second client according to the identification information and the identity of the client An associative list generated by the correspondence between the information.
  • the processor 501 when reading the association list according to the second client identity information, is configured to: search for a storage area corresponding to the second client on the server according to the second client identity information; The storage area reads the associated list.
  • the processor 501 when acquiring the identification information of the user data to be shared corresponding to the first client identity information according to the association list, executing an application: searching from the association list with the first client
  • the identity information of the client identity information that matches the identity information is determined by the identifier information corresponding to the client identity information that is found as the identity information of the user data to be shared corresponding to the first client identity information.
  • the processor 501 before executing the identifier information application for acquiring the user data to be shared corresponding to the first client identity information according to the association list, further executing an application: determining whether the association list exists And the first client identity information; if the first client identity information exists in the association list, acquiring, according to the association list, an identifier of the user data to be shared corresponding to the first client identity information information.
  • the processor 501 After performing the determining whether the first client identity information application exists in the association list, the processor 501 further needs to execute an application, if the first client identity information does not exist in the association list, Determining whether the second client is in a login state; if the second client is in a login state, generating sharing request prompt information according to the first client identity information, and sending the sharing request prompt information to the a second client; obtaining an operation instruction that is sent by the second client according to the sharing request prompt information; determining whether there is identification information of the user data to be shared in the operation instruction; if the operation instruction exists in the operation instruction Sharing the identification information of the user data, generating a user data sharing link according to the identification information, and sending the user data sharing link to the first client; if the operation instruction does not have the user data to be shared Identifying information, sending prompt information that cannot access the second client user data to the first client
  • the processor 501 is further configured to: after the determining, by the operation instruction, the identifier information of the user data to be shared, if the identifier of the user data to be shared is not present in the operation instruction, Sending prompt information that cannot access the second client user data to the first client.
  • the data sharing device provided by the embodiment of the present invention is the same as the data sharing method in the foregoing embodiment, and any method provided in the data sharing method embodiment may be run on the data sharing device, and the specific For details, refer to the data sharing method embodiment, which is not described here.
  • the computer program may be stored in a computer readable storage medium, such as in a memory of the terminal, and executed by at least one processor in the terminal, and may include a method of data sharing as described in the execution process.
  • the storage medium may be a magnetic disk, an optical disk, a read only memory (ROM, Read) Only Memory), random access memory (RAM, Random Access Memory), etc.
  • each functional module may be integrated into one processing chip, or each module may exist physically separately, or two or more modules may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the integrated module if implemented in the form of a software functional module and sold or used as a standalone product, may also be stored in a computer readable storage medium, such as a read only memory, a magnetic disk or an optical disk, etc. .
  • the embodiment of the present invention further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are adapted to be loaded by a processor to execute the data sharing method described in any of the foregoing embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé de partage de données, un dispositif, un support de stockage et un serveur, le procédé de partage de données comprenant les étapes consistant : à obtenir une demande de partage envoyée par un premier client ; à lire une liste d'associations en fonction des informations d'identité d'un second client ; en fonction de la liste d'associations, à obtenir des informations d'identification de données d'utilisateur à partager correspondant à des informations d'identité du premier client ; à générer une liaison de partage de données d'utilisateur en fonction des informations d'identification et à envoyer la liaison de partage de données d'utilisateur au premier client.
PCT/CN2017/094815 2016-10-25 2017-07-28 Procédé de partage de données, dispositif, support de stockage et serveur Ceased WO2018076840A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610938130.9 2016-10-25
CN201610938130.9A CN106357521A (zh) 2016-10-25 2016-10-25 数据分享方法及装置

Publications (1)

Publication Number Publication Date
WO2018076840A1 true WO2018076840A1 (fr) 2018-05-03

Family

ID=57864142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/094815 Ceased WO2018076840A1 (fr) 2016-10-25 2017-07-28 Procédé de partage de données, dispositif, support de stockage et serveur

Country Status (2)

Country Link
CN (1) CN106357521A (fr)
WO (1) WO2018076840A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112260929A (zh) * 2019-07-22 2021-01-22 腾讯科技（深圳）有限公司 内容分享方法、装置、终端及存储介质
CN114356231A (zh) * 2021-12-27 2022-04-15 阿里巴巴（中国）有限公司 数据处理方法、设备及计算机存储介质
WO2022252935A1 (fr) * 2021-06-01 2022-12-08 深圳传音控股股份有限公司 Procédé de traitement d'informations, dispositif et support de stockage

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106357521A (zh) * 2016-10-25 2017-01-25 广东欧珀移动通信有限公司 数据分享方法及装置
CN109697129A (zh) * 2017-10-23 2019-04-30 中兴通讯股份有限公司 一种信息分享方法、设备及计算机可读存储介质
CN109729049A (zh) * 2017-10-30 2019-05-07 北京国双科技有限公司 信息的分享方法及装置
CN110336810B (zh) * 2019-06-28 2022-06-14 华为云计算技术有限公司 信息分享方法、平台、计算设备及存储介质
CN112905295B (zh) * 2021-03-31 2021-10-15 掌阅科技股份有限公司 数据互通方法、计算设备及计算机存储介质
CN113783938A (zh) * 2021-08-18 2021-12-10 深圳市冠旭电子股份有限公司 基于可穿戴设备的数据分享方法、系统、设备及存储介质
CN114936254A (zh) * 2022-05-12 2022-08-23 清华大学 云链融合机制下的食品安全大数据共享管理方法及系统

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120227089A1 (en) * 2011-03-03 2012-09-06 Snu R&Db Foundation Apparatus and method for sharing contents of social network service in communication system
CN103002030A (zh) * 2012-11-26 2013-03-27 北京百度网讯科技有限公司 文件共享的方法和系统
CN103945009A (zh) * 2014-05-09 2014-07-23 张志强 软件分享方法及装置
CN104410615A (zh) * 2014-11-20 2015-03-11 北京奇虎科技有限公司 对共享数据进行访问的方法、客户端、服务器及系统
CN104601641A (zh) * 2014-05-23 2015-05-06 腾讯科技（深圳）有限公司 应用链接分享方法、装置及系统
CN104660678A (zh) * 2015-01-16 2015-05-27 深圳市深信服电子科技有限公司 应用数据分享方法和装置
CN104869143A (zh) * 2014-02-26 2015-08-26 腾讯科技（深圳）有限公司 资料分享方法、装置、客户端和服务器
CN104954398A (zh) * 2014-03-26 2015-09-30 腾讯科技（深圳）有限公司 一种获取内容的方法及装置
CN104980334A (zh) * 2014-04-23 2015-10-14 腾讯科技（深圳）有限公司 一种信息共享方法、装置及系统
CN105610949A (zh) * 2015-12-30 2016-05-25 腾讯科技（深圳）有限公司 资源数据使用权限的共享方法、装置及系统
CN106357521A (zh) * 2016-10-25 2017-01-25 广东欧珀移动通信有限公司 数据分享方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103227746B (zh) * 2012-01-31 2018-03-27 珠海德百祺科技有限公司 数据通信方法及系统
CN102740228A (zh) * 2012-06-21 2012-10-17 北京小米科技有限责任公司 一种位置信息共享方法、装置及系统
CN104079470B (zh) * 2013-03-27 2019-06-25 腾讯科技（深圳）有限公司 一种电子名片交换方法、系统及服务器
CN104079548B (zh) * 2013-04-27 2018-10-09 腾讯科技（深圳）有限公司 电子名片管理方法、装置、服务器及通信系统
CN105100223B (zh) * 2015-07-01 2019-10-15 北京奇虎科技有限公司 基于云端存储的文件分享方法、装置与系统

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120227089A1 (en) * 2011-03-03 2012-09-06 Snu R&Db Foundation Apparatus and method for sharing contents of social network service in communication system
CN103002030A (zh) * 2012-11-26 2013-03-27 北京百度网讯科技有限公司 文件共享的方法和系统
CN104869143A (zh) * 2014-02-26 2015-08-26 腾讯科技（深圳）有限公司 资料分享方法、装置、客户端和服务器
CN104954398A (zh) * 2014-03-26 2015-09-30 腾讯科技（深圳）有限公司 一种获取内容的方法及装置
CN104980334A (zh) * 2014-04-23 2015-10-14 腾讯科技（深圳）有限公司 一种信息共享方法、装置及系统
CN103945009A (zh) * 2014-05-09 2014-07-23 张志强 软件分享方法及装置
CN104601641A (zh) * 2014-05-23 2015-05-06 腾讯科技（深圳）有限公司 应用链接分享方法、装置及系统
CN104410615A (zh) * 2014-11-20 2015-03-11 北京奇虎科技有限公司 对共享数据进行访问的方法、客户端、服务器及系统
CN104660678A (zh) * 2015-01-16 2015-05-27 深圳市深信服电子科技有限公司 应用数据分享方法和装置
CN105610949A (zh) * 2015-12-30 2016-05-25 腾讯科技（深圳）有限公司 资源数据使用权限的共享方法、装置及系统
CN106357521A (zh) * 2016-10-25 2017-01-25 广东欧珀移动通信有限公司 数据分享方法及装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112260929A (zh) * 2019-07-22 2021-01-22 腾讯科技（深圳）有限公司 内容分享方法、装置、终端及存储介质
CN112260929B (zh) * 2019-07-22 2022-06-24 腾讯科技（深圳）有限公司 内容分享方法、装置、终端及存储介质
WO2022252935A1 (fr) * 2021-06-01 2022-12-08 深圳传音控股股份有限公司 Procédé de traitement d'informations, dispositif et support de stockage
CN114356231A (zh) * 2021-12-27 2022-04-15 阿里巴巴（中国）有限公司 数据处理方法、设备及计算机存储介质
CN114356231B (zh) * 2021-12-27 2023-10-20 阿里巴巴（中国）有限公司 数据处理方法、设备及计算机存储介质

Also Published As

Publication number Publication date
CN106357521A (zh) 2017-01-25

Similar Documents

Publication Publication Date Title
WO2018076840A1 (fr) Procédé de partage de données, dispositif, support de stockage et serveur
WO2018076812A1 (fr) Procédé et dispositif de réponse à une demande de données, support de stockage, serveur et système
WO2018076841A1 (fr) Procédé de partage de données, appareil, support de stockage, et serveur
WO2018076868A1 (fr) Procédé, dispositif et système de synchronisation de données, support de stockage et serveur
WO2018076889A1 (fr) Procédé de sauvegarde de données, dispositif, système, support de stockage et serveur
WO2018076829A1 (fr) Serveur, support d'informations, système, appareil et procédé de traitement de données de terminal
WO2014157886A1 (fr) Procédé et dispositif permettant d'exécuter une application
WO2017206883A1 (fr) Procédé et appareil de traitement d'applications, support de stockage, et dispositif électronique
WO2018076819A1 (fr) Procédé de téléchargement de données, appareil, support de stockage, dispositif électronique et système
WO2018120681A1 (fr) Procédé, dispositif et système de synchronisation de données, serveur de traitement de données et support de stockage
WO2019156506A1 (fr) Système et procédé de fourniture de contenus conversationnels
WO2018076866A1 (fr) Procédé de traitement de données, dispositif, support de stockage, dispositif électronique, et serveur
WO2012124985A2 (fr) Procédé et appareil de synchronisation d'informations personnelles
WO2014030889A1 (fr) Procédé et appareil de partage de contenu
WO2018090823A1 (fr) Procédé et système de protection de données de clé de partition de système et terminal
WO2018076873A1 (fr) Procédé de partage de données, appareil, support, dispositif électronique, et système
WO2018076867A1 (fr) Procédé, dispositif et système de suppression de sauvegarde de données, support de mémoire et serveur
WO2018076865A1 (fr) Procédé, dispositif, support d'informations et dispositif électronique de partage de données
WO2017206878A1 (fr) Procédé et appareil de traitement basé sur un verrou d'activation, support d'informations et dispositif électronique
WO2018076811A1 (fr) Dispositif électronique, support d'informations, système, dispositif et procédé de partage de données
WO2018076864A1 (fr) Procédé, appareil, support de stockage et dispositif électronique de synchronisation de données
WO2018076888A1 (fr) Procédé, dispositif et système de synchronisation de données d'un terminal mobile, support de mémoire et terminal mobile
WO2018076869A1 (fr) Procédé sauvegarde de données, appareil, support de stockage et dispositif électronique
WO2018117536A1 (fr) Appareil électronique, son procédé d'authentification d'autorité de commande et appareil de terminal utilisateur
WO2017028573A1 (fr) Procédé et système de traitement d'informations d'image sur la base d'un terminal mobile

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

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

Country of ref document: EP

Kind code of ref document: A1