CN106790497B - Singing list synchronization method and mobile terminal - Google Patents

Singing list synchronization method and mobile terminal Download PDF

Info

Publication number
CN106790497B
CN106790497B CN201611159575.3A CN201611159575A CN106790497B CN 106790497 B CN106790497 B CN 106790497B CN 201611159575 A CN201611159575 A CN 201611159575A CN 106790497 B CN106790497 B CN 106790497B
Authority
CN
China
Prior art keywords
song list
cloud
local
list
mobile terminal
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.)
Active
Application number
CN201611159575.3A
Other languages
Chinese (zh)
Other versions
CN106790497A (en
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
Priority to CN201611159575.3A priority Critical patent/CN106790497B/en
Publication of CN106790497A publication Critical patent/CN106790497A/en
Application granted granted Critical
Publication of CN106790497B publication Critical patent/CN106790497B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/60Information retrieval; Database structures therefor; File system structures therefor of audio data
    • G06F16/68Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/686Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using information manually generated, e.g. tags, keywords, comments, title or artist information, time, location or usage information, user ratings

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The invention is suitable for the technical field of information, and provides a song list synchronization method and a mobile terminal, wherein the synchronization method comprises the following steps: when receiving a song list synchronization instruction, sending the name of a local song list to be synchronized to a cloud server to obtain a cloud song list with the same name returned by the server; comparing the local song list with the equipment identification corresponding to the cloud song list; and when the local song list and the cloud song list have the same corresponding equipment identification, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode. The invention solves the problem of cross synchronization of the homonymous singing lists of different mobile terminals in the prior art, enriches the synchronization modes of the singing lists and improves the efficiency of the singing list management.

Description

Singing list synchronization method and mobile terminal
Technical Field
The invention belongs to the technical field of information, and particularly relates to a song list synchronization method and a mobile terminal.
Background
When the synchronization of the cloud and the local song list is carried out, the prior art adopts a song list name comparison mode to realize, the condition of multiple devices is not considered, and the problem of chaotic synchronization among the same-name song lists of different mobile terminals easily occurs. For example, a user holds a mobile terminal a and a mobile terminal B, and after the user uploads a song list "recently played" on the mobile terminal a to a cloud server by using a cloud id, the song list "recently played" uploaded by the mobile terminal a can be synchronized to the mobile terminal B by the cloud id. Because the song list played recently only corresponds to the songs stored in the mobile terminal A, after the song list is synchronized on the mobile terminal B, the situation that playing files corresponding to some songs in the song list cannot be found exists, the problem of intersection exists in the synchronization of the song list, and the experience of a user is influenced.
Therefore, a new technical solution is needed to solve the above technical problems.
Disclosure of Invention
In view of this, the embodiment of the present invention provides a song list synchronization method and a mobile terminal, so as to solve the problem of cross synchronization of the same-name song lists of different mobile terminals in the prior art.
In a first aspect, a song list synchronization method is provided, where the synchronization method includes:
when a song list synchronization instruction is received, the name of a local song list to be synchronized is sent to a cloud server so as to obtain a cloud song list with the same name returned by the cloud server;
comparing the local song list with the equipment identification corresponding to the cloud song list;
and when the local song list and the cloud song list have the same corresponding equipment identification, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode.
Further, the acquiring a synchronization mode, synchronizing the local song list and the cloud song list according to the synchronization mode includes:
if a coverage instruction is received, performing coverage type synchronization on the local song list and the cloud song list;
and if a merging instruction is received, merging synchronization is carried out on the local song list and the cloud song list.
Further, if a coverage instruction is received, performing coverage synchronization on the local song list and the cloud song list comprises:
if a coverage instruction is received, comparing the time information of the local song list and the cloud song list;
if the time information of the cloud song list is earlier than that of a local song list, uploading the local song list to the cloud server to cover the cloud song list;
and if the time information of the local song list is earlier than that of the cloud song list, downloading the cloud song list to the mobile terminal and covering the local song list.
Further, if a merge instruction is received, performing merge-type synchronization on the local song list and the cloud song list includes:
if a merging instruction is received, adding the songs in the cloud-side song list to the local song list to obtain a merged song list;
cleaning the same song in the merged song list;
and after cleaning, updating the time information of the combined song list, and uploading the combined song list to a cloud server.
Further, the method further comprises:
and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
In a second aspect, a mobile terminal is provided, the mobile terminal comprising:
the sending module is used for sending the name of the local song list to be synchronized to the cloud server when receiving the song list synchronization instruction so as to obtain the cloud song list with the same name returned by the cloud server;
the comparison module is used for comparing the local song list with the equipment identification corresponding to the cloud song list;
and the synchronization module is used for acquiring a synchronization mode when the local song list is the same as the equipment identifier corresponding to the cloud song list, and synchronizing the local song list and the cloud song list according to the synchronization mode.
Further, the synchronization module includes:
the coverage submodule is used for performing coverage type synchronization on the local song list and the cloud song list if a coverage instruction is received;
and the merging submodule is used for performing merging type synchronization on the local song list and the cloud song list if a merging instruction is received.
Further, the overlay sub-module includes:
the comparison unit is used for comparing the time information of the local song list and the cloud song list when a coverage instruction is received;
the first uploading unit is used for uploading the local song list to the cloud server to cover the cloud song list if the time information of the cloud song list is earlier than that of the local song list;
and the downloading unit is used for downloading the cloud song list to the mobile terminal and covering the local song list if the time information of the local song list is earlier than that of the cloud song list.
Further, the merge sub-module includes:
the adding unit is used for adding the songs in the cloud song list to the local song list to obtain a combined song list if a combining instruction is received;
the cleaning unit is used for cleaning the same songs in the combined song list;
and the second uploading unit is used for updating the time information of the combined song list after the cleaning is finished and then uploading the combined song list to the cloud server.
Further, the mobile terminal further includes:
and the uploading module is used for uploading the local song list to a cloud server when the equipment identifications corresponding to the local song list and the cloud song list are different.
In a third aspect, a mobile terminal is provided, which includes:
the processor is used for sending the name of the local song list to be synchronized to the cloud server when receiving the song list synchronization instruction so as to obtain the cloud song list with the same name returned by the cloud server; comparing the local song list with the equipment identification corresponding to the cloud song list; and when the local song list and the cloud song list have the same corresponding equipment identification, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode.
Further, the processor is further configured to:
if a coverage instruction is received, performing coverage type synchronization on the local song list and the cloud song list;
and if a merging instruction is received, merging synchronization is carried out on the local song list and the cloud song list.
Further, the processor is further configured to:
if a coverage instruction is received, comparing the time information of the local song list and the cloud song list;
if the time information of the cloud song list is earlier than that of a local song list, uploading the local song list to the cloud server to cover the cloud song list;
and if the time information of the local song list is earlier than that of the cloud song list, downloading the cloud song list to the mobile terminal and covering the local song list.
Further, the processor is further configured to:
if a merging instruction is received, adding the songs in the cloud-side song list to the local song list to obtain a merged song list;
cleaning the same song in the merged song list;
and after cleaning, updating the time information of the combined song list, and uploading the combined song list to a cloud server.
Further, the processor is further configured to:
and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
Compared with the prior art, the embodiment of the invention sends the name of the local song list to be synchronized to the cloud server when receiving the song list synchronization instruction so as to obtain the cloud song list with the same name returned by the cloud server; then, comparing the local song list with the equipment identification corresponding to the cloud song list to judge whether the cloud song list corresponds to the mobile terminal or not through the equipment identification; further, work as local song list with the equipment identification that high in the clouds song list corresponds is the same, then acquires the synchronization mode, according to the synchronization mode is right local song list with the high in the clouds song list is synchronous to solved the different mobile terminal's of prior art problem of cross synchronization of the same name song list, and enriched the synchronization mode of song list, improved the efficiency of song list management.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of an implementation of a song list synchronization method according to a first embodiment of the present invention;
fig. 2 is a flowchart illustrating an implementation of overlay-type synchronization of the local song list and the cloud song list according to the first embodiment of the present invention;
fig. 3 is a flowchart illustrating a specific implementation of the merged synchronization of the local song list and the cloud song list according to the first embodiment of the present invention;
fig. 4 is a schematic block diagram of a mobile terminal provided in a second embodiment of the present invention;
fig. 5 is a schematic block diagram of a mobile terminal provided by a third embodiment of the present invention;
fig. 6 is a schematic block diagram of a mobile terminal provided by a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
When receiving a song list synchronization instruction, the embodiment of the invention sends the name of a local song list to be synchronized to a cloud server so as to obtain a cloud song list with the same name returned by the cloud server; then, comparing the local song list with the equipment identification corresponding to the cloud song list to judge whether the cloud song list corresponds to the mobile terminal or not through the equipment identification; further, work as local song list with the equipment identification that high in the clouds song list corresponds is the same, then acquires the synchronization mode, according to the synchronization mode is right local song list with the high in the clouds song list is synchronous to solved the different mobile terminal's of prior art problem of cross synchronization of the same name song list, and enriched the synchronization mode of song list, improved the efficiency of song list management. The embodiment of the invention also provides a corresponding mobile terminal, which is respectively explained in detail below.
Fig. 1 shows a flow of implementing the song list synchronization method according to the first embodiment of the present invention.
In the embodiment of the present invention, the method for synchronizing the song list is applied to a mobile terminal, including but not limited to a smart phone, a tablet computer, a learning machine, and a music player (such as MP3, MP 4).
Referring to fig. 1, the method of synchronizing the song list includes:
in step S101, when receiving the song list synchronization instruction, the name of the local song list to be synchronized is sent to the cloud server to obtain the cloud song list with the same name returned by the cloud server.
In the embodiment of the invention, when a song list synchronization instruction input by a user is acquired, the mobile terminal firstly sends the name of the local song list to the cloud server, so that after the cloud server receives the name, the name of the local song list is compared with the name of the cloud song list, a cloud song list with the same name as the local song list is screened out, and then the relevant information of the cloud song list is returned to the mobile terminal.
Here, the related information includes the name of the cloud-side song list, the song contained in the cloud-side song list, the device identifier, and time information. The device identification can be a serial number of the mobile terminal and is used for distinguishing the mobile terminal corresponding to the song list; the time information may be a creation/modification time of the song list on the mobile terminal. When a user creates a song list on a mobile terminal, the embodiment of the invention associates the name of the song list with the equipment identifier and the time information of the mobile terminal. When the song list is named, the device identification and time information are added to the end of the song list name. Optionally, in other embodiments, the device identifier and the time information may be hidden, and only the name of the song list is displayed, and the device identifier and the time information cannot be seen by the user.
In step S102, the device identifiers corresponding to the local song list and the cloud song list are compared.
Here, since the names of the cloud song tickets uploaded to the cloud server by different mobile terminals may be the same, the cloud song tickets obtained based on the names of the local song tickets may also be uploaded by other mobile terminals and do not correspond to the mobile terminals. Therefore, after the cloud-end song list with the same name is obtained, the embodiment of the invention compares the local song list with the device identifier corresponding to the cloud-end song list to determine whether the currently obtained cloud-end song list is the target song list, namely whether the currently obtained cloud-end song list corresponds to the mobile terminal.
In step S103, when the device identifiers corresponding to the local song list and the cloud song list are the same, a synchronization mode is obtained, and the local song list and the cloud song list are synchronized according to the synchronization mode.
Here, when the local song list and the cloud song list correspond to the same device identifier, it may be determined that the obtained cloud song list corresponds to the mobile terminal, and then prompt information may be output to prompt the user to confirm the synchronization mode of the local song list.
Optionally, in an embodiment of the present invention, the synchronization manner includes overlay synchronization and merge synchronization. Correspondingly, the prompt message comprises a covering identifier and a merging identifier. And when a coverage instruction generated by a coverage identifier in the user trigger prompt message is received, performing coverage synchronization on the local song list and the cloud song list. And when a merging instruction generated by a merging identifier in the user trigger prompt message is received, merging synchronization is carried out on the local song list and the cloud song list.
As a preferred example of the present invention, a specific implementation flow of performing overlay synchronization on the local song list and the cloud song list according to the first embodiment of the present invention is given below, and with reference to fig. 2, includes:
in step S201, if a coverage instruction is received, the time information of the local song list and the cloud song list is compared.
In step S202, if the time information of the cloud-side song list is earlier than the time information of the local song list, the local song list is uploaded to the cloud server to cover the cloud-side song list.
In step S203, if the time information of the local song list is earlier than the time information of the cloud song list, the cloud song list is downloaded to the mobile terminal, and the local song list is covered.
Here, after the cloud-end song list is obtained through device identifier comparison to correspond to the mobile terminal, the embodiment of the present invention compares the time information of the cloud-end song list and the local song list, and selects a song list with a closer time point for synchronization. For example, comparing the creation/modification time of the cloud-side song list with the local song list, uploading the local song list to a cloud server when the creation/modification time of the local song list is closer, and downloading the cloud-side song list to the mobile terminal when the creation/modification time of the cloud-side song list is closer; therefore, automatic coverage updating of the song list on the local and cloud terminals is realized.
As another preferred example of the present invention, a specific implementation flow of performing combined synchronization on the local song list and the cloud song list according to the first embodiment of the present invention is given below, and with reference to fig. 3, includes:
in step S301, if a merge instruction is received, adding the song in the cloud-end song list to the local song list to obtain a merged song list.
In step S302, the same song in the merged menu is cleaned.
In step S303, after the cleaning is completed, the time information of the merged song list is updated, and then the merged song list is uploaded to a cloud server.
Here, after the cloud song list is judged to correspond to the mobile terminal through the device identifier, the embodiment of the invention merges the cloud song list and the local song list. Specifically, after the songs in the cloud-side song list are added to the last song of the local song list, a merged song list is obtained. And then sequencing all songs in the combined song list according to a preset sequencing mode. Traversing the sorted combined song list, deleting the songs at the back position when the songs at the front position and the back position are the same song, and only keeping the first song at the front position to clear the same song in the combined song list. Updating the modification time of the combined song list until the whole song list is traversed, and uploading the combined song list serving as a local song list of the mobile terminal to a cloud server for storage; therefore, the local and cloud song lists are combined and updated, and the experience of the user is effectively improved.
Optionally, on the basis of the embodiment shown in fig. 1, the method for synchronizing the song list may further include:
and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
Here, when the equipment sign that local song list and high in the clouds song list correspond is inequality, then confirm the high in the clouds song list that obtains with mobile terminal does not correspond, is that other mobile terminal are stored song list on the high in the clouds server, promptly do not have stored on the cloud server mobile terminal's local song list, then will local song list uploads to the cloud server to the misjudgment that the cloud of the same name song list leads to has been avoided, has improved the synchronous validity of song list.
In summary, in the embodiment of the present invention, when receiving the song list synchronization instruction, the name of the local song list to be synchronized is sent to the cloud server, so as to obtain the cloud song list with the same name returned by the cloud server; then, comparing the local song list with the equipment identification corresponding to the cloud song list to judge whether the cloud song list corresponds to the mobile terminal or not through the equipment identification; further, work as local song list with the equipment identification that high in the clouds song list corresponds is the same, then acquires the synchronization mode, according to the synchronization mode is right local song list with the high in the clouds song list is synchronous to solved the different mobile terminal's of prior art problem of cross synchronization of the same name song list, and enriched the synchronization mode of song list, improved the efficiency of song list management.
Fig. 4 shows a schematic block diagram of a mobile terminal according to a second embodiment of the present invention, and only shows portions related to the embodiment of the present invention for convenience of explanation.
In an embodiment of the present invention, the mobile terminal is configured to implement the song list synchronization method described in the embodiments of fig. 1 to 3. The mobile terminal includes but is not limited to a smart phone, a tablet computer, and the like.
Referring to fig. 4, the mobile terminal includes:
the sending module 41 is configured to send the name of the local song list to be synchronized to the cloud server when receiving the song list synchronization instruction, so as to obtain the cloud song list with the same name returned by the cloud server;
a comparison module 42, configured to compare the device identifiers corresponding to the local song list and the cloud song list;
and the synchronization module 43 is configured to, when the device identifiers corresponding to the local song list and the cloud song list are the same, acquire a synchronization mode, and synchronize the local song list and the cloud song list according to the synchronization mode.
Further, the synchronization module 43 includes:
the coverage submodule 431 is used for performing coverage type synchronization on the local song list and the cloud song list if a coverage instruction is received;
and the merging submodule 432 is configured to perform merging synchronization on the local song list and the cloud song list if a merging instruction is received.
In the embodiment of the present invention, when a song synchronization instruction input by a user is acquired, a sending module 41 in the mobile terminal first sends the name of the local song list to the cloud server, so that after the cloud server receives the name, the name is compared with the name of the cloud song list, a cloud song list with the same name as the local song list is screened out, and then relevant information of the cloud song list is returned to the mobile terminal. Here, the related information includes the name of the cloud-side song list, the song contained in the cloud-side song list, the device identifier, and time information. The device identification can be a serial number of the mobile terminal and is used for distinguishing the mobile terminal corresponding to the song list; the time information may be a creation/modification time of the song list on the mobile terminal. When a user creates a song list on a mobile terminal, the embodiment of the invention associates the name of the song list with the equipment identifier and the time information of the mobile terminal. When the song list is named, the device identification and time information are added to the end of the song list name. Alternatively, in other embodiments, the device identifier and the time information may be hidden, that is, only the name of the song list is displayed, and the device identifier and the time information cannot be seen by the user.
Because the names of the cloud song lists uploaded to the cloud server by different mobile terminals are possibly the same, the cloud song lists acquired based on the names of the local song lists can also be uploaded by other mobile terminals and do not correspond to the mobile terminals. In contrast, after the cloud-end song list with the same name is obtained, the embodiment of the present invention compares, through the comparison module 42, the local song list with the device identifier corresponding to the cloud-end song list to determine whether the currently obtained song list is the target song list, that is, whether the currently obtained cloud-end song list is the song list stored on the cloud server corresponding to the mobile terminal.
When the local song list is the same as the device identifier corresponding to the cloud song list, the obtained cloud song list can be determined to be the song list stored on the cloud server corresponding to the mobile terminal, and then prompt information is output through the synchronization module 43 so as to prompt the user to confirm the synchronization mode of the local song list. Optionally, in an embodiment of the present invention, the synchronization manner includes overlay synchronization and merge synchronization. Correspondingly, the prompt message comprises a covering identifier and a merging identifier. The user may input an overlay instruction by triggering the overlay identifier, and the overlay submodule 431 performs overlay synchronization on the local song list and the cloud song list according to the overlay instruction. The overlay submodule 431 further includes:
a comparing unit 4311, configured to compare the time information of the local song list and the cloud song list if a coverage instruction is received;
a first uploading unit 4313, configured to upload the local song list to the cloud server to cover the cloud song list if the time information of the cloud song list is earlier than the time information of the local song list;
a downloading unit 4312, configured to download the cloud song list to the mobile terminal and cover the local song list if the time information of the local song list is earlier than the time information of the cloud song list.
Here, after the cloud-end song list is judged to correspond to the mobile terminal through the device identifier, the embodiment of the present invention selects a song list with a closer time point to synchronize through comparing the time information of the cloud-end song list and the local song list by the comparing unit 4311. For example, comparing the creation/modification time of the cloud-end song list with the local song list, uploading the local song list to a cloud server when the creation/modification time of the local song list is closer, and downloading the cloud-end song list to the local server when the creation/modification time of the cloud-end song list is closer; therefore, automatic coverage updating of the song list on the local and cloud terminals is realized.
Optionally, the user may also input a merge instruction by triggering the merge identifier, and the merge submodule 432 performs merge synchronization on the local song list and the cloud song list according to the merge instruction. The merge sub-module 432 further includes:
an adding unit 4321, configured to add the song in the cloud-end song list to the local song list to obtain a merged song list if a merging instruction is received;
a cleaning unit 4322, configured to clean the same song in the merged song list.
A second uploading unit 4323, configured to update the time information of the merged song list after the cleaning is completed, and then upload the merged song list to a cloud server.
Here, after the cloud song list is judged to correspond to the mobile terminal through the device identifier, the embodiment of the invention merges the cloud song list and the local song list. Specifically, the adding unit 4321 adds the song in the cloud-side song list to the last song of the local song list to obtain a merged song list. Then, the cleaning unit 4322 sorts all songs in the combined menu according to a preset sorting manner. Traversing the sorted combined song list, deleting the songs at the back position when the songs at the front position and the back position are the same song, and only keeping the first song at the front position to clear the same song in the combined song list. After the whole song list is traversed, the second uploading unit 4323 updates the modification time of the merged song list, and uploads the merged song list to a cloud server for storage as a local song list of the mobile terminal; therefore, the local and cloud song lists are combined and updated, and the experience of the user is improved.
Further, the mobile terminal further includes:
and the uploading module 44 is configured to upload the local song list to a cloud server when the device identifiers corresponding to the local song list and the cloud song list are different.
It should be noted that the mobile terminal in the embodiment of the present invention may be configured to implement all technical solutions in the foregoing method embodiments, and the functions of each functional module may be implemented according to the method in the foregoing method embodiments, and the specific implementation process may refer to the relevant description in the foregoing example, which is not described herein again.
In summary, in the embodiment of the present invention, when receiving the song list synchronization instruction, the name of the local song list to be synchronized is sent to the cloud server, so as to obtain the cloud song list with the same name returned by the cloud server; then, comparing the local song list with the equipment identification corresponding to the cloud song list to judge whether the cloud song list corresponds to the mobile terminal or not through the equipment identification; further, work as local song list with the equipment identification that high in the clouds song list corresponds is the same, then acquires the synchronization mode, according to the synchronization mode is right local song list with the high in the clouds song list is synchronous to solved the different mobile terminal's of prior art problem of cross synchronization of the same name song list, and enriched the synchronization mode of song list, improved the efficiency of song list management.
Referring to fig. 5, a schematic block diagram of a mobile terminal according to a third embodiment of the present invention is shown. The mobile terminal as shown in the figure may include: one or more processors 501 (only one shown); one or more input devices 502 (only one shown), one or more output devices 503 (only one shown), and a memory 504. The processor 501, the input device 502, the output device 503, and the memory 504 are connected by a bus 506. The memory 504 is used for storing instructions and the processor 501 is used for executing the instructions stored by the memory 504. Wherein:
optionally, the processor 501 is configured to:
the system comprises a cloud server, a server and a server, wherein the cloud server is used for sending a local song list name to be synchronized to the cloud server when receiving a song list synchronization instruction so as to obtain a cloud song list with the same name returned by the cloud server; comparing the local song list with the equipment identification corresponding to the cloud song list; and when the local song list and the cloud song list have the same corresponding equipment identification, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode.
Optionally, the processor 501 is further configured to:
if a coverage instruction is received, performing coverage type synchronization on the local song list and the cloud song list;
and if a merging instruction is received, merging synchronization is carried out on the local song list and the cloud song list.
Optionally, the processor 501 is further configured to:
if a coverage instruction is received, comparing the time information of the local song list and the cloud song list;
if the time information of the cloud song list is earlier than that of a local song list, uploading the local song list to the cloud server to cover the cloud song list;
and if the time information of the local song list is earlier than that of the cloud song list, downloading the cloud song list to the mobile terminal and covering the local song list.
Optionally, the processor 501 is further configured to:
if a merging instruction is received, adding the songs in the cloud-side song list to the local song list to obtain a merged song list;
cleaning the same song in the merged song list;
and after cleaning, updating the time information of the combined song list, and uploading the combined song list to a cloud server.
Optionally, the processor 501 is further configured to:
and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
It should be understood that, in the embodiment of the present invention, the Processor 501 may be a Central Processing Unit (CPU) and/or a Graphics Processing Unit (GPU), and may also be combined with other general purpose processors, Digital Signal Processors (DSP), Application Specific Integrated Circuits (ASIC), Field-Programmable Gate arrays (FPGA) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.
The input device 502 may include a touch pad, a fingerprint sensor (for collecting fingerprint information of a user and direction information of the fingerprint), a microphone, a communication module (such as a Wi-Fi module, a 2G/3G/4G network module), a physical button, and the like.
The output device 503 may include a display (LCD, etc.), speakers, etc. The display may be used, among other things, to display information entered by or provided to the user. The Display may include a Display panel, and optionally, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch screen may be overlaid on the display, and when the touch screen detects a touch operation thereon or nearby, the touch screen is transmitted to the processor 501 to determine the type of the touch event, and then the processor 501 provides a corresponding visual output on the display according to the type of the touch event.
In a specific implementation, the processor 501, the input device 502, the output device 503, and the memory 504 described in the embodiment of the present invention may execute the implementation manner described in the embodiment of the song list synchronization method provided in the embodiment of the present invention, and details are not described here again.
Fig. 6 is a schematic block diagram of a mobile terminal according to a fourth embodiment of the present invention, which can be used to implement the song list synchronization method provided in the above-mentioned embodiments.
As shown in fig. 6, the mobile terminal 1200 may include an RF (Radio Frequency) circuit 110, a memory 120 including one or more computer-readable storage media (only one shown), an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a transmission module 170, a processor 180 including one or more processing cores (only one shown), and a power supply 190. Those skilled in the art will appreciate that the mobile terminal 1200 configuration illustrated in fig. 6 is not intended to be limiting of the mobile terminal 1200 and may include more or less components than those illustrated, or some components in combination, or a different arrangement of components. Wherein:
the RF circuit 110 is used for receiving and transmitting electromagnetic waves, and performs interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. The RF circuitry 110 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF circuitry 110 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices over a wireless network. The wireless network may comprise a cellular telephone network, a wireless local area network, or a metropolitan area network. The Wireless network may use various Communication standards, protocols and technologies, including but not limited to Global System for Mobile Communication (GSM), Enhanced Mobile Communication (EDGE), wideband Code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wireless Fidelity (WiFi) (e.g., IEEE802.11 a, IEEE802.11 b, IEEE802.1 g and/or IEEE802.1 n), Voice over internet protocol (VoIP), world wide mail Access (Microwave for Wireless communications, Wi-Max), and other short message protocols, as well as any other suitable communication protocols, and may even include those that have not yet been developed.
The memory 120 may be configured to store software programs and modules, such as program instructions/modules corresponding to the method in the foregoing embodiment, and the processor 180 executes various functional applications and data processing by running the software programs and modules stored in the memory 120, that is, identifying a cloud-end song list corresponding to the mobile terminal according to the device identifier and synchronizing the local song list and the cloud-end song list. Memory 120 may include high speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 120 may further include memory located remotely from processor 180, which may be connected to mobile terminal 1200 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input unit 130 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, the input unit 130 may include a touch-sensitive surface 131 as well as other input devices 132. The touch-sensitive surface 131, also referred to as a touch display screen or a touch pad, may collect touch operations by a user on or near the touch-sensitive surface 131 (e.g., operations by a user on or near the touch-sensitive surface 131 using a finger, a stylus, or any other suitable object or attachment), and drive the corresponding connection device according to a predetermined program. Alternatively, the touch sensitive surface 131 may comprise two parts, a touch detection means and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 180, and can receive and execute commands sent by the processor 180. Additionally, the touch-sensitive surface 131 may be implemented using various types of resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch-sensitive surface 131, the input unit 130 may also include other input devices 132. In particular, other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 140 may be used to display information input by or provided to the user and various graphic user interfaces of the mobile terminal 1200, which may be configured by graphics, text, icons, video, and any combination thereof. The display unit 140 may include a display panel 141, and optionally, the display panel 141 may be configured in the form of an LCD (Liquid crystal display), an OLED (Organic Light-Emitting Diode), or the like. Further, the touch-sensitive surface 131 may cover the display panel 141, and when a touch operation is detected on or near the touch-sensitive surface 131, the touch operation is transmitted to the processor 180 to determine the type of the touch event, and then the processor 180 provides a corresponding visual output on the display panel 141 according to the type of the touch event. Although in FIG. 6, touch-sensitive surface 131 and display panel 141 are shown as two separate components to implement input and output functions, in some embodiments, touch-sensitive surface 131 may be integrated with display panel 141 to implement input and output functions.
The mobile terminal 1200 may also include at least one sensor 150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 141 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 141 and/or the backlight when the mobile terminal 1200 is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), detect the magnitude and direction of gravity when the mobile phone is stationary, and can be used for detecting an inclination angle, and identifying applications of the mobile phone gesture (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration identification related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which may be further configured in the mobile terminal 1200, detailed descriptions thereof are omitted.
Audio circuitry 160, speaker 161, and microphone 162 may provide an audio interface between a user and mobile terminal 1200. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electric signal, converts the electric signal into audio data after being received by the audio circuit 160, and then outputs the audio data to the processor 180 for processing, and then to the RF circuit 110 to be transmitted to, for example, another terminal, or outputs the audio data to the memory 120 for further processing. The audio circuitry 160 may also include an earbud jack to provide communication of peripheral headphones with the mobile terminal 1200.
The mobile terminal 1200, which can help a user send and receive e-mails, browse web pages, access streaming media, etc., through the transmission module 170 (e.g., WiFi module), provides the user with wireless broadband internet access. Although fig. 6 illustrates the transmission module 170, it is understood that it does not belong to the essential constitution of the mobile terminal 1200, and may be omitted entirely within the scope not changing the essence of the invention as needed.
The processor 180 is a control center of the mobile terminal 1200, connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions of the mobile terminal 1200 and processes data by operating or executing software programs and/or modules stored in the memory 120 and calling data stored in the memory 120, thereby integrally monitoring the mobile phone. Optionally, processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 180.
The mobile terminal 1200 also includes a power supply 190 (e.g., a battery) for powering the various components, which may be logically coupled to the processor 180 via a power management system that may be configured to manage charging, discharging, and power consumption. The power supply 190 may also include any component including 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.
Although not shown, the mobile terminal 1200 may further include a camera, a bluetooth module, and the like, which will not be described herein. Specifically, in this embodiment, the display unit of the mobile terminal is a touch screen display, the mobile terminal further includes a memory, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for:
when a song list synchronization instruction is received, the name of a local song list to be synchronized is sent to a cloud server so as to obtain a cloud song list with the same name returned by the cloud server;
comparing the local song list with the equipment identification corresponding to the cloud song list;
and when the local song list and the cloud song list have the same corresponding equipment identification, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode.
Assuming that the foregoing is the first possible implementation manner, in a second possible implementation manner provided on the basis of the first possible implementation manner, the memory of the mobile terminal further includes instructions for performing the following operations:
the acquiring the synchronization mode, synchronizing the local song list and the cloud song list according to the synchronization mode comprises:
if a coverage instruction is received, performing coverage type synchronization on the local song list and the cloud song list;
and if a merging instruction is received, merging synchronization is carried out on the local song list and the cloud song list.
In a third possible implementation manner provided as the basis of the second possible implementation manner, the memory of the mobile terminal further includes instructions for performing the following operations:
if a coverage instruction is received, performing coverage synchronization on the local song list and the cloud song list comprises the following steps:
if a coverage instruction is received, comparing the time information of the local song list and the cloud song list;
if the time information of the cloud song list is earlier than that of a local song list, uploading the local song list to the cloud server to cover the cloud song list;
and if the time information of the local song list is earlier than that of the cloud song list, downloading the cloud song list to the mobile terminal and covering the local song list.
In a fourth possible implementation manner provided as the basis of the second possible implementation manner, the memory of the mobile terminal further includes instructions for performing the following operations:
if a merging instruction is received, merging synchronization of the local song list and the cloud song list comprises the following steps:
if a merging instruction is received, adding the songs in the cloud-side song list to the local song list to obtain a merged song list;
cleaning the same song in the merged song list;
and after cleaning, updating the time information of the combined song list, and uploading the combined song list to a cloud server.
In a fifth possible implementation manner provided on the basis of the first to fourth possible implementation manners, the memory of the mobile terminal further includes instructions for performing the following operations:
and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
In summary, in the embodiment of the present invention, when receiving the song list synchronization instruction, the name of the local song list to be synchronized is sent to the cloud server, so as to obtain the cloud song list with the same name returned by the server; then, comparing the local song list with the equipment identification corresponding to the cloud song list to judge whether the cloud song list corresponds to the mobile terminal or not through the equipment identification; further, work as local song list with the equipment identification that high in the clouds song list corresponds is the same, then acquires the synchronization mode, according to the synchronization mode is right local song list with the high in the clouds song list is synchronous to solved the different mobile terminal's of prior art problem of cross synchronization of the same name song list, and enriched the synchronization mode of song list, improved the efficiency of song list management.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the modules and units described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed method and mobile terminal may be implemented in other manners. For example, the above-described embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of modules or units through some interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units and modules in the embodiments of the present invention may be integrated into one processing unit, or each unit and module may exist alone physically, or two or more units and modules may be integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (12)

1. A method for synchronizing a song list, the method comprising:
when a song list synchronization instruction is received, the name of a local song list to be synchronized is sent to a cloud server, the cloud server compares the name of the local song list with the name of a cloud song list after receiving the name of the local song list, a cloud song list which is the same as the local song list is screened out, and then relevant information of the screened cloud song list is returned, wherein the relevant information comprises the name of the cloud song list, songs contained in the cloud song list, equipment identification and time information, and when a user creates the song list on a mobile terminal and names the song list, the equipment identification and the time information are added to the tail of the song list name, the equipment identification and the time information are hidden, and only the name of the song list is displayed;
comparing the local song list with the equipment identification corresponding to the cloud song list;
when the device identifications corresponding to the local song list and the cloud song list are the same, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode;
and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
2. The method for synchronizing a song list according to claim 1, wherein the acquiring a synchronization mode, synchronizing the local song list and the cloud song list according to the synchronization mode comprises:
if a coverage instruction is received, performing coverage type synchronization on the local song list and the cloud song list;
and if a merging instruction is received, merging synchronization is carried out on the local song list and the cloud song list.
3. The method for synchronizing the song list according to claim 2, wherein the overlay-synchronizing the local song list and the cloud song list if the overlay command is received comprises:
if a coverage instruction is received, comparing the time information of the local song list and the cloud song list;
if the time information of the cloud song list is earlier than that of a local song list, uploading the local song list to the cloud server to cover the cloud song list;
and if the time information of the local song list is earlier than that of the cloud song list, downloading the cloud song list to the mobile terminal and covering the local song list.
4. The method for synchronizing the song list according to claim 2, wherein the step of performing a merged synchronization on the local song list and the cloud song list if a merge command is received comprises:
if a merging instruction is received, adding the songs in the cloud-side song list to the local song list to obtain a merged song list;
cleaning the same song in the merged song list;
and after cleaning, updating the time information of the combined song list, and uploading the combined song list to a cloud server.
5. A mobile terminal, characterized in that the mobile terminal comprises:
the system comprises a sending module, a cloud server and a control module, wherein the sending module is used for sending the name of a local song list to be synchronized to the cloud server when receiving a command of song list synchronization, the cloud server compares the name of the local song list with the name of a cloud song list after receiving the name of the local song list, screens out the cloud song list which is the same as the name of the local song list, and then returns relevant information of the screened cloud song list, wherein the relevant information comprises the name of the cloud song list, songs contained in the cloud song list, equipment identification and time information, and when a user creates the song list on a mobile terminal and names the song list, the equipment identification and the time information are added to the tail of the song list name, the equipment identification and the time information are hidden, and only the name of the song list is displayed;
the comparison module is used for comparing the local song list with the equipment identification corresponding to the cloud song list;
the synchronization module is used for acquiring a synchronization mode when the equipment identifiers corresponding to the local song list and the cloud song list are the same, and synchronizing the local song list and the cloud song list according to the synchronization mode;
and the uploading module is used for uploading the local song list to a cloud server when the equipment identifications corresponding to the local song list and the cloud song list are different.
6. The mobile terminal of claim 5, wherein the synchronization module comprises:
the coverage submodule is used for performing coverage type synchronization on the local song list and the cloud song list if a coverage instruction is received;
and the merging submodule is used for performing merging type synchronization on the local song list and the cloud song list if a merging instruction is received.
7. The mobile terminal of claim 6, wherein the overlay sub-module comprises:
the comparison unit is used for comparing the time information of the local song list and the cloud song list when a coverage instruction is received;
the first uploading unit is used for uploading the local song list to the cloud server to cover the cloud song list if the time information of the cloud song list is earlier than that of the local song list;
and the downloading unit is used for downloading the cloud song list to the mobile terminal and covering the local song list if the time information of the local song list is earlier than that of the cloud song list.
8. The mobile terminal of claim 6, wherein the merge sub-module comprises:
the adding unit is used for adding the songs in the cloud song list to the local song list to obtain a combined song list if a combining instruction is received;
the cleaning unit is used for cleaning the same songs in the combined song list;
and the second uploading unit is used for updating the time information of the combined song list after the cleaning is finished and then uploading the combined song list to the cloud server.
9. A mobile terminal, characterized in that the mobile terminal comprises:
a memory;
the system comprises a processor, a cloud server and a mobile terminal, wherein the processor is used for sending the name of a local song list to be synchronized to the cloud server when receiving a command of song list synchronization, the cloud server compares the name of the local song list with the name of a cloud song list after receiving the name of the local song list, screens out the cloud song list which is the same as the name of the local song list, and then returns relevant information of the screened cloud song list, wherein the relevant information comprises the name of the cloud song list, and songs, equipment identification and time information contained in the cloud song list; comparing the local song list with the equipment identification corresponding to the cloud song list; when the device identifications corresponding to the local song list and the cloud song list are the same, acquiring a synchronization mode, and synchronizing the local song list and the cloud song list according to the synchronization mode; and when the equipment identifications corresponding to the local song list and the cloud song list are different, uploading the local song list to a cloud server.
10. The mobile terminal of claim 9, wherein the processor is further configured to:
if a coverage instruction is received, performing coverage type synchronization on the local song list and the cloud song list;
and if a merging instruction is received, merging synchronization is carried out on the local song list and the cloud song list.
11. The mobile terminal of claim 10, wherein the processor is further configured to:
if a coverage instruction is received, comparing the time information of the local song list and the cloud song list;
if the time information of the cloud song list is earlier than that of a local song list, uploading the local song list to the cloud server to cover the cloud song list;
and if the time information of the local song list is earlier than that of the cloud song list, downloading the cloud song list to the mobile terminal and covering the local song list.
12. The mobile terminal of claim 10, wherein the processor is further configured to:
if a merging instruction is received, adding the songs in the cloud-side song list to the local song list to obtain a merged song list;
cleaning the same song in the merged song list;
and after cleaning, updating the time information of the combined song list, and uploading the combined song list to a cloud server.
CN201611159575.3A 2016-12-15 2016-12-15 Singing list synchronization method and mobile terminal Active CN106790497B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611159575.3A CN106790497B (en) 2016-12-15 2016-12-15 Singing list synchronization method and mobile terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611159575.3A CN106790497B (en) 2016-12-15 2016-12-15 Singing list synchronization method and mobile terminal

Publications (2)

Publication Number Publication Date
CN106790497A CN106790497A (en) 2017-05-31
CN106790497B true CN106790497B (en) 2020-01-24

Family

ID=58889152

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611159575.3A Active CN106790497B (en) 2016-12-15 2016-12-15 Singing list synchronization method and mobile terminal

Country Status (1)

Country Link
CN (1) CN106790497B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108471638B (en) * 2018-02-08 2021-04-06 深圳魔耳智能声学科技有限公司 Wireless earphone control method, device, control device and storage medium
CN111506740A (en) * 2020-04-14 2020-08-07 天津洪恩完美未来教育科技有限公司 Word list adding method and device, storage medium and electronic device

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060129330A (en) * 2004-01-27 2006-12-15 코닌클리케 필립스 일렉트로닉스 엔.브이. Audio/video content synchronization through playlists
US7937451B2 (en) * 2007-01-08 2011-05-03 Mspot, Inc. Method and apparatus for transferring digital content from a computer to a mobile handset
US10706096B2 (en) * 2011-08-18 2020-07-07 Apple Inc. Management of local and remote media items
CN103188321A (en) * 2011-12-30 2013-07-03 上海博泰悦臻电子设备制造有限公司 Information synchronizing method and system based on cloud server
CN103327037B (en) * 2012-03-20 2017-09-29 中兴通讯股份有限公司 Method of data synchronization and device
CN102821109B (en) * 2012-08-28 2015-06-03 腾讯科技(深圳)有限公司 Method, associated equipment and system for realizing data sharing in instant communication application

Also Published As

Publication number Publication date
CN106790497A (en) 2017-05-31

Similar Documents

Publication Publication Date Title
CN106055364B (en) Application starting method and terminal equipment
US9344838B2 (en) Data transmission method and apparatus, and terminal with touch screen
RU2632153C2 (en) Method, device and terminal for displaying virtual keyboard
CN108763316B (en) Audio list management method and mobile terminal
CN104778055B (en) Method and device for displaying progress bar
CN108834132B (en) Data transmission method and equipment and related medium product
CN108363524B (en) A kind of application icon display methods and mobile terminal
CN110673770B (en) Message display method and terminal equipment
CN103294442B (en) A kind of method of playing alert tones, device and terminal device
CN108052820B (en) Unlocking control method, terminal equipment and related product
CN109101327B (en) Switching of light application and mobile terminal
CN106452644B (en) Control method for playing back, device and terminal
CN106484563B (en) Data migration method and terminal equipment
CN109688611B (en) Frequency band parameter configuration method, device, terminal and storage medium
CN105550316A (en) Pushing method and device of audio list
CN107317828B (en) File downloading method and device
CN106790497B (en) Singing list synchronization method and mobile terminal
CN106302101B (en) Message reminding method, terminal and server
CN110958352B (en) Network signal display method, device, storage medium and mobile terminal
CN106682189B (en) File name display method and device
CN108683812B (en) Volume adjusting method and device and mobile terminal
CN107930126B (en) Game reservation data processing method and device and mobile terminal
CN112367425B (en) Volume adjusting method and device and terminal
CN106657278B (en) Data transmission method and device and computer equipment
CN106572163B (en) A kind of method and terminal of Data Migration

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information
CB02 Change of applicant information

Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18

Applicant after: OPPO Guangdong Mobile Communications Co., Ltd.

Address before: Changan town in Guangdong province Dongguan 523841 usha Beach Road No. 18

Applicant before: Guangdong Opel Mobile Communications Co., Ltd.

GR01 Patent grant
GR01 Patent grant