CN113641533B - Terminal and short message processing method - Google Patents
Terminal and short message processing method Download PDFInfo
- Publication number
- CN113641533B CN113641533B CN202010345771.XA CN202010345771A CN113641533B CN 113641533 B CN113641533 B CN 113641533B CN 202010345771 A CN202010345771 A CN 202010345771A CN 113641533 B CN113641533 B CN 113641533B
- Authority
- CN
- China
- Prior art keywords
- short message
- short
- contact
- messages
- writing
- 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
Links
- 238000003672 processing method Methods 0.000 title abstract description 14
- 238000000034 method Methods 0.000 claims abstract description 35
- 238000012545 processing Methods 0.000 claims abstract description 21
- 230000006870 function Effects 0.000 description 62
- 239000010410 layer Substances 0.000 description 25
- 238000010586 diagram Methods 0.000 description 14
- 230000008859 change Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 239000012792 core layer Substances 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000004807 localization Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 229910044991 metal oxide Inorganic materials 0.000 description 1
- 150000004706 metal oxides Chemical class 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
Abstract
The application discloses a terminal and a short message processing method, which relate to the technical field of intelligent terminals, and the method comprises the following steps: responding to a short message backup instruction, and writing a plurality of short messages to be backed up into a short message service table; after the plurality of short messages are written into the short message service table, acquiring one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for marking the receiving time or the sending time of the short message; and writing one short message with the maximum time mark of each contact into the association table. By the method, the time for copying and backing up the short message is saved, and the efficiency for backing up the short message is improved, so that the aim of saving processing resources is fulfilled.
Description
Technical Field
The application relates to the technical field of intelligent terminals, in particular to a terminal and a short message processing method.
Background
At present, basically all terminals have a one-key machine changing function, so that terminal data can be backed up to a new terminal, and communication applications such as short messages and the like in the new terminal need to be restored by inserting a database in the backup process.
The inventors found that if the data amount is large, there is a problem that the short message backup takes a relatively large amount of time, and as the number of short message pieces is larger, the time consumption does not linearly increase with the number of short message pieces, but almost exponentially increases. That is, as the number of short messages increases, more time is taken to backup each short message, which occupies more processing resources to complete the backup. Therefore, how to improve the efficiency of short message backup to save processing resources needs to be solved.
Disclosure of Invention
The embodiment of the application provides a terminal and a short message processing method, which are used for saving the time of short message backup and improving the efficiency of short message backup, thereby achieving the purpose of saving processing resources.
According to a first aspect in an exemplary embodiment, there is provided a terminal comprising an input unit, a processor and a display screen;
the input unit is used for receiving a short message backup instruction;
the processor is used for responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table;
after the plurality of short messages are written into the short message service table, acquiring one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for marking the receiving time or the sending time of the short message;
Writing one short message with the maximum time mark of each contact into an association table;
the display screen is used for displaying a contact person session interface corresponding to each contact person generated according to the short message service table; or displaying a short message list interface generated according to the association table.
The inventor researches and discovers that the triggering function is caused to traverse the short message service table after writing one short message into the short message service table in the related technology, so that the association table is updated, and the short message backup time is excessively long under the condition. According to the embodiment of the application, after the backup of the short message service table is finished, the short message content of the corresponding association table can be obtained by traversing the short message service table once, so that the time consumption required by short message backup or copying can be greatly saved, the short message backup efficiency is improved, and the purpose of saving processing resources is achieved.
In one possible implementation, the processor is further configured to:
after receiving the short message backup instruction and before responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table, closing a triggering function in a short message database, wherein the triggering function is used for triggering updating of the association table once when one short message is written into the short message service table.
In the related art, since the short message database includes a trigger function, for example, a trigger, the short message database is used to trigger the update of the association table once every time the short message service table is changed. According to the embodiment of the application, the triggering function in the short message database is closed, so that the update of the association table caused by the triggering of each time of short message change is avoided, and the time for backup and copying of the short message is saved.
In one possible implementation, if the trigger function in the short message database is turned off, after writing the plurality of short messages into a short message service table, the processor is further configured to:
when receiving a broadcast notification message sent by the short message database and used for indicating that the plurality of short messages are written in the short message service table, restarting the triggering function; or,
after receiving a query instruction for designating a Uniform Resource Identifier (URI), querying the designated URI, and restarting the trigger function according to the resource indicated by the designated URI; the query instruction of the appointed URI is sent by the short message database after the plurality of short messages are written into the short message service table.
According to the embodiment, after the short message service table is written, the triggering function in the short message database is recovered, so that the automatic updating operation of the association table based on the triggering function is recovered. The implementation mode provided by the application is realized through two possible implementation modes, and the normal function of the short message database after the backup is finished is ensured.
In a possible implementation, the indicated resource is a restart instruction for restarting the trigger function; when the triggering function is re-enabled according to the resource indicated by the specified URI, the processor is configured to:
searching the restart instruction indicated by the appointed URI;
executing the restarting instruction starts a triggering function in the short message database for the association table.
The embodiment provides an implementation way for restarting the triggering function in the short message database, and when restarting is performed by adopting the query of the appointed URI, the restarting of the triggering function can be realized through the matching relation between the appointed URI and the restarting instruction.
In one possible implementation manner, before writing the plurality of short messages to be backed up into the short message service table, the processor is further configured to:
analyzing the plurality of short messages to obtain each contact in the plurality of short messages;
generating a unique identifier of each contact in the association table, and creating a short message record for the contact in the association table according to the unique identifier;
when writing the short message with the maximum time mark of each contact into the association table, the processor is configured to:
And writing one short message with the maximum time mark of the contact into a short message record corresponding to the unique identifier in the association table according to the unique identifier corresponding to the contact.
The update of the association table is realized through the unique identification of the contact person, so that the short message with the maximum time mark of each contact person is ensured to be accurately updated into the association table.
According to a second aspect in an exemplary embodiment, there is provided a short message processing method, the method including:
responding to a short message backup instruction, and writing a plurality of short messages to be backed up into a short message service table;
after the plurality of short messages are written into the short message service table, acquiring one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for marking the receiving time or the sending time of the short message;
and writing one short message with the maximum time mark of each contact into the association table.
In one possible embodiment, the method further comprises:
after receiving the short message backup instruction and before responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table, closing a triggering function in a short message database, wherein the triggering function is used for triggering updating of the association table once when one short message is written into the short message service table.
In one possible implementation manner, if the trigger function in the short message database is closed, after writing the plurality of short messages into the short message service table, the method further includes:
when receiving a broadcast notification message sent by the short message database and used for indicating that the plurality of short messages are written in the short message service table, restarting the triggering function; or,
after receiving a query instruction for designating a Uniform Resource Identifier (URI), querying the designated URI, and restarting the trigger function according to the resource indicated by the designated URI; the query instruction of the appointed URI is sent by the short message database after the plurality of short messages are written into the short message service table.
In a possible implementation, the indicated resource is a restart instruction for restarting the trigger function; the re-enabling the trigger function according to the resource indicated by the specified URI includes:
searching the restart instruction indicated by the appointed URI;
executing the restarting instruction starts a triggering function in the short message database for the association table.
In one possible implementation manner, before writing the plurality of short messages to be backed up into the short message service table, the method further includes:
Analyzing the plurality of short messages to obtain each contact in the plurality of short messages;
generating a unique identifier of each contact in the association table, and creating a short message record for the contact in the association table according to the unique identifier;
writing the short message with the maximum time mark of each contact into an association table, wherein the writing comprises the following steps:
and writing one short message with the maximum time mark of the contact into a short message record corresponding to the unique identifier in the association table according to the unique identifier corresponding to the contact.
In a third aspect, the present application also provides a computer storage medium having stored thereon a computer program which, when executed by a processing unit, implements the steps of the short message processing method according to the second aspect.
In addition, the technical effects caused by any implementation manner of the second aspect and the third aspect may refer to the technical effects caused by different implementation manners of the first aspect, which are not described herein.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed. On the basis of conforming to the common knowledge in the field, the above preferred conditions can be arbitrarily combined to obtain the preferred embodiments of the application.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 2 schematically illustrates a software architecture of a terminal according to an embodiment of the present application;
fig. 3 is a schematic flow chart illustrating a short message processing method according to an embodiment of the present application;
fig. 4 exemplarily illustrates an operation interface of a push-to-talk machine provided in an embodiment of the present application;
fig. 5 is a schematic diagram illustrating a short message processing method according to an embodiment of the present application;
FIG. 6 is a diagram schematically showing a display interface contrast of a short message process in the related art;
fig. 7 is a schematic diagram illustrating a display interface contrast diagram of a short message processing method according to an embodiment of the present application;
fig. 8 illustrates a schematic structure of a terminal provided in an embodiment of the present application.
Detailed Description
The following description will be given in detail of the technical solutions in the embodiments of the present application with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, "a plurality" means two or more than two.
The terms "first," "second," and the like, are used below for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature, and in the description of embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.
First, fig. 1 shows a schematic configuration of a terminal 100.
The embodiment will be specifically described below with reference to the terminal 100 as an example. It should be understood that the terminal 100 shown in fig. 1 is only one example, and that the terminal 100 may have more or fewer components than shown in fig. 1, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
A hardware configuration block diagram of the terminal 100 according to an exemplary embodiment is exemplarily shown in fig. 1. As shown in fig. 1, the terminal 100 includes: radio Frequency (RF) circuitry 110, memory 120, display unit 130, camera 140, sensor 150, audio circuitry 160, wireless fidelity (Wireless Fidelity, wi-Fi) module 170, processor 180, bluetooth module 181, and power supply 190.
The RF circuit 110 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communication, and may receive downlink data of the base station and then transmit the downlink data to the processor 180 for processing; uplink data may be sent to the base station. Typically, RF circuitry includes, but is not limited to, antennas, at least one amplifier, transceivers, couplers, low noise amplifiers, diplexers, and the like.
Memory 120 may be used to store software programs and data. The processor 180 performs various functions of the terminal 100 and data processing by running software programs or data stored in the memory 120. Memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. The memory 120 stores an operating system that enables the terminal 100 to operate. The memory 120 in this application may store an operating system and various application programs, and may also store program codes for performing the methods described in embodiments of this application.
The display unit 130 may be used to receive input digital or character information, generate signal inputs related to user settings and function control of the terminal 100, and in particular, the display unit 130 may include a touch screen 131 provided at the front of the terminal 100, and may collect touch operations on or near the user, such as clicking buttons, dragging scroll boxes, and the like.
The display unit 130 may also be used to display information input by a user or information provided to the user and a graphical user interface (graphical user interface, GUI) of various menus of the terminal 100. In particular, the display unit 130 may include a display 132 disposed on the front of the terminal 100. The display 132 may be configured in the form of a liquid crystal display, light emitting diodes, or the like. The display unit 130 may be used to display a contact session interface or a short message list interface described in the present application.
The touch screen 131 may cover the display screen 132, or the touch screen 131 and the display screen 132 may be integrated to implement input and output functions of the terminal 100, and after integration, the touch screen may be simply referred to as a touch display screen. The display unit 130 may display an application program and corresponding operation steps.
The camera 140 may be used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the processor 180 for conversion into a digital image signal.
The terminal 100 may further include at least one sensor 150, such as an acceleration sensor 151, a distance sensor 152, a fingerprint sensor 153, a temperature sensor 154. The terminal 100 may also be configured with other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, light sensors, motion sensors, and the like.
Audio circuitry 160, speaker 161, microphone 162 can provide an audio interface between the user and terminal 100. The audio circuit 160 may transmit the received electrical signal converted from audio data to the speaker 161, and the speaker 161 converts the electrical signal into a sound signal and outputs the sound signal. The terminal 100 may also be configured with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, which is output to the RF circuit 110 for transmission to, for example, another terminal, or to the memory 120 for further processing. Microphone 162 may capture the voice of the user in this application.
Wi-Fi belongs to a short-range wireless transmission technology, and the terminal 100 can help a user to send and receive e-mail, browse web pages, access streaming media and the like through the Wi-Fi module 170, so that wireless broadband internet access is provided for the user.
The processor 180 is a control center of the terminal 100, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal 100 and processes data by running or executing software programs stored in the memory 120 and calling data stored in the memory 120. In some embodiments, the processor 180 may include one or more processing units; the processor 180 may also integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., and a baseband processor that primarily handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 180. The processor 180 may run an operating system, application programs, user interface displays and touch responses, and the processing methods described in the embodiments of the present application. In addition, the processor 180 is coupled with the display unit 130.
The bluetooth module 181 is configured to perform information interaction with other bluetooth devices having a bluetooth module through a bluetooth protocol. For example, the terminal 100 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) also provided with a bluetooth module through the bluetooth module 181, thereby performing data interaction.
The terminal 100 also includes a power supply 190 (e.g., a battery) that provides power to the various components. The power supply may be logically connected to the processor 180 through a power management system, so that functions of managing charge, discharge, power consumption, etc. are implemented through the power management system. The terminal 100 may also be configured with power buttons for powering on and off the terminal, and for locking the screen, etc.
Fig. 2 is a software configuration block diagram of the terminal 100 according to the embodiment of the present application.
The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system may be divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.
The application layer may include a series of application packages.
As shown in fig. 2, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.
As shown in FIG. 2, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.
The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.
The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, short messages, etc.
The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a short message notification icon may include a view displaying text and a view displaying a picture.
The telephony manager is used to provide the communication functions of the terminal 100. Such as the management of call status (including on, hung-up, etc.).
The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
The notification manager allows the application to display notification information (e.g., message digest of short message, message content) in a status bar, can be used to convey notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the terminal vibrates, and an indicator light blinks.
Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.
The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.
The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.
The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.
Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.
The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.
A 2D (one way of animation) graphics engine is a drawing engine for 2D drawing.
The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.
The workflow of the terminal 100 software and hardware is illustrated below in connection with capturing a photo scene.
When the touch screen 131 receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into the original input event (including information such as touch coordinates, time stamp of touch operation, etc.). The original input event is stored at the kernel layer. The application framework layer acquires an original input event from the kernel layer, and identifies a control corresponding to the input event. Taking the touch operation as a touch click operation, taking a control corresponding to the click operation as an example of a control of a camera application icon, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera driver by calling a kernel layer, and captures a still image or video through the camera 140.
The terminal 100 in the embodiment of the present application may be a mobile phone, a tablet computer, a wearable device, a notebook computer, a television, and the like.
Some terms appearing hereinafter are explained:
and (one) a short message service table: that is, sms (Short Message Service ) table, for storing the detailed content of each short message, refer to table 1, which is an example of sms table provided in the embodiment of the present application, and the specific content is as follows:
TABLE 1
| _id | threads_id | body | date | address |
Among them, the following points are described with respect to table 1:
(1) The "_id" in table 1 is a line number in the sms table, and is used for indicating the number of short messages in the sms table, for example, if 100 short messages are stored in the sms table, the "_id" in the sms table includes 100 short message records in total lines from 1 to 100;
(2) The "threads_id" is an identifier linked with a unique identifier "_id" of a contact in the threads table, and is used for identifying different contacts, for example, if the short message in the sms table comprises the short message interacted with 6 different contacts, the value of the threads_id is 1-6;
(3) "body" is used to denote the specific content of the piece of short message;
(4) "date" means a time stamp of the line short message record, that is, a receiving time or a transmitting time of the line short message;
(5) The address is used to represent the contact number for the short message interaction.
It should be noted that, only some of the contents in the sms table are shown in table 1, and these contents are not meant to be included, which is not limited in this application.
(II) association table: that is, the threads table is configured to store a short message with the largest time stamp in each contact session record, that is, a short message with the latest receiving time or sending time in each contact session, and refer to table 2, which is an example of the threads table provided in the embodiments of the present application, and specifically includes the following steps:
TABLE 2
| _id | date | snippet |
Among them, the following points are described with respect to table 2:
(1) The "_id" in table 2 is a row number in the threads table, and is used for representing the unique identifier of the contacts in the threads table, and the total row number of "_id" is the number of the contacts, for example, if 100 pieces of short messages in the sms table are respectively obtained by interacting with 6 contacts, the "_id" in the threads table includes 6 rows of short message records from 1 to 6, and is the latest short message record in the short message session records of the 6 contacts respectively;
(2) "date" also means a time stamp recorded for the line of short messages, i.e., a receiving time or a transmitting time of the short message;
(3) "snippet" indicates the specific content for this line of short messages.
It should be noted that, in table 2, only some of the contents in the threads table are given, and these contents are not meant to be included, which is not limited in the present application.
Aiming at the problem that the short message copying or backup takes more time at present, according to the research of the inventor, the problem of long time consumption in the related technology is mainly caused by the fact that the short message database and the contact database contain more triggers with triggering functions. When one piece of data is inserted, the operation of traversing the short message service table is triggered, so that the more the number of pieces is, the longer the time for traversing the operation of traversing the short message service table is, and the more the data quantity is, the more the time required for copying the data quantity is. For example, the sms table and the threads table are included in the sms database, and since the sms database has a trigger for updating the threads table in real time according to the sms table, the threads table is updated correspondingly and synchronously when the sms table changes each time.
The embodiment of the application is not only suitable for a one-key machine changing scene, but also suitable for applications such as cloud backup for copying, backing up or recovering short messages. For these applications, since sms table will insert many short messages, if sms table is traversed according to each short message inserted in sms table, the threads table is updated synchronously, i.e. each time sms table changes, the threads table is traversed and updated. However, in reality, the content in the threads table is the short message content with the largest time stamp of each contact in the sms table, so when the sms table is not completed for backup of the short message, the updates of threads are likely to be covered by the short message inserted into the sms table. In this case, the previous synchronous update of the threads table is meaningless, and the time consumed for copying or backing up the entire short message may become too long due to the update of the threads table.
In view of this, the embodiment of the present application provides a method for processing short messages, which reduces the time consumption of short message backup or duplication in a short message restoration scenario, and is described in detail below with reference to specific embodiments:
as shown in fig. 3, a flowchart of a short message processing method provided in an embodiment of the present application is shown, where the flowchart includes the following steps:
step 301, in response to the short message backup command, writing a plurality of short messages to be backed up into the short message service table.
In a possible embodiment, the short message backup instruction is a one-key machine change instruction, which can be understood that the one-key machine change instruction is used for backing up the short message stored in another terminal device; for example, if the short message of the terminal device a is backed up to the new terminal device B, when the short message backup instruction of the terminal device a is received, the terminal device B is ready to backup the short message to be backed up transmitted from the terminal device a received in the network, that is, the terminal B is ready to write the short message into the short message service table.
Referring to fig. 4, an operation interface of a push-to-talk device according to an embodiment of the present application is provided, where after being used to click "i are new mobile phones" on the interface, a plurality of short messages to be backed up are received; and then, responding to the clicking instruction, and writing the received short messages to be backed up into a short message service table, namely a sms table. If the interface of fig. 4 is displayed on the old terminal, after the user clicks "i am the old mobile phone" on the interface, in one possible implementation manner, the old terminal generates a two-dimensional code, waits for the new terminal to scan the two-dimensional code, and sends the contents of the short messages to be backed up of the old terminal to the new terminal after receiving a backup instruction sent by the new terminal based on the two-dimensional code. Of course, the two-dimensional code manner is only an example, and the old terminal and the new terminal can be associated in other manners during implementation, so as to realize the one-key exchange function.
In another possible embodiment, the short message backup instruction is a cloud backup instruction, which can be understood that the cloud backup instruction is used for backing up the plurality of short messages stored on the cloud server, and the implementation is similar to a one-key-change scenario and will not be repeated here.
Step S302, after the plurality of short messages are written into the short message service table, obtaining one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for identifying the receiving time or the sending time of the short message.
Step S303: and writing one short message with the maximum time mark of each contact into the association table.
The association table is used for storing a short message with the maximum time mark of each contact.
When the method is implemented, the short message service table and the association table are both contained in a short message database, the short message database contains a triggering function, and the triggering function is used for triggering updating of the association table once when one piece of short message is written in the short message service table; in one possible implementation, the triggering function may be implemented by a trigger.
In one possible embodiment, after updating the first short message in the plurality of short messages to be backed up to the short message service table, the triggering function in the short message database may be turned off; for example, the embodiment of closing the trigger in the sms database may be implemented by the following embodiment shown in table 3, as follows:
TABLE 3 Table 3
As shown in table 3, at least two types of triggers are included in the triggers included in the sms database, and one type is a trigger for updating, which is mainly used for implementing an operation of updating the contents in the threads table according to the sms change of the sms table; for example, when a time updated short message of an existing contact is received, specific content of the short message corresponding to the contact in the threads table is updated. The other is a trigger for insertion, which is mainly used for realizing the operation of inserting the thread table according to the short message change of the sms table; for example, if the sms table receives a short message of a new contact's session, the short message of the contact is inserted into the threads table.
After the trigger function is turned off, if the short message service table changes, the association table is not updated synchronously because the trigger function is not available.
In addition, after the plurality of short messages to be backed up are written in the short message service table, in a possible implementation manner, when a broadcast notification message sent by the short message database and used for indicating that the plurality of short messages are written in the short message service table is received, the triggering function is re-started.
In another possible implementation manner, after receiving a query instruction for a specified uniform resource identifier URI, querying the specified URI, and re-enabling the trigger function according to a resource indicated by the specified URI; the query instruction of the appointed URI is sent by the short message database after the plurality of short messages are written into the short message service table.
For example, if 100 pieces of short messages are to be backed up, after all 100 pieces of short message records are inserted into the sms table, it is indicated that writing of the sms table for the 100 pieces of short messages is completed, and the short message database will send a notification of completion of backup; the notification may be implemented by sending a broadcast notification message, or determined by querying a preset specified URI, and when a short message service component (for example, a ContentProvider component of one of the four components in Android) for updating the threads table receives the broadcast notification message or receives a query instruction for the specified URI, determining that the backup of the short message service table is completed, and then executing a trigger function for restarting the short message database.
When the operation of inquiring the appointed URI is implemented, the indicated resource is a restarting instruction for restarting the triggering function; when a query instruction for a specified URI is received, searching the restarting instruction indicated by the specified URI; and executing the restarting instruction to start the triggering function in the short message database for the association table.
The optional restart instruction is implemented by the following embodiment shown in table 4, where the trigger function is still exemplified by a trigger as follows:
TABLE 4 Table 4
In addition, before writing the plurality of short messages to be backed up into the short message service table, the method further comprises: analyzing the plurality of short messages to obtain each contact in the plurality of short messages; generating a unique identifier of each contact in the association table, and creating a short message record for the contact in the association table according to the unique identifier; firstly, determining that the short message to be backed up shares a plurality of contacts through analyzing the contact identification of the short message. For example, if 3 contacts are resolved, a session record of 3 rows of contacts is correspondingly generated in the threads table, and the "_id" includes 1, 2 and 3.
The created short message record is optional, and the short message which is firstly analyzed to correspond to the contact person can be recorded into the threads table to be used as an initial short message record for creating the threads table. In addition, after the sms table is backed up, each piece of short message in the sms table is analyzed, after one piece of short message with the largest time mark of each contact person is obtained, one piece of short message with the largest time mark of the contact person is written into a short message record corresponding to the unique mark in the association table according to the unique mark corresponding to the contact person. For example, if the short message with the largest time stamp of the contact person with the "threads_id" of 1 is obtained from the sms table as the short message 1, the short message 1 is written into the short message record of the row with the "_id" of 1 in the threads table.
When the analysis is performed on the plurality of short messages in the short message service table to obtain one short message with the largest time mark of each contact in the plurality of short messages, an optional implementation manner includes: for each contact, perform: extracting a time mark of at least one short message associated with the contact; comparing the time marks of the at least one short message associated with the contact; and acquiring a short message with the maximum time mark of the contact person according to the comparison result.
When the method is implemented, through the introduction of the specific contents of the sms table and the threads table, the fact that the 'threads_id' in the sms table is linked with the '_id' in the threads table can be determined, and after sms updating is completed, a plurality of contacts can be determined according to the 'threads_id' in the sms table; and then, searching and comparing one short message with the maximum time mark of each contact person according to the date in each contact person. For example, if the sms table contains 3 short messages of the contact a, and the receiving or transmitting time is respectively 4 months 9 days, 4 months 10 days, and 4 months 11 days, it can be determined that the short message received or transmitted on 4 months 11 days is the short message with the largest time stamp with the contact.
In the short message processing method provided in the embodiment of the present application, by closing the triggering function of the trigger, the efficiency of short message backup is improved, and for a clearer understanding of the technical solution of improving the efficiency by the application, referring to fig. 5, a comparison schematic diagram of the short message processing method provided in the implementation of the present application is provided, and from fig. 5, it can be determined that the total time T1 consumed for backup of short messages in the related art can be determined by the following formula (1):
wherein T1 represents total time required for backup of n pieces of short messages in the related art, n represents total n pieces of short messages to be backed up, sms i Representing the time required for inserting the ith short message into sms list, threads i Representing the time required to traverse sms tables for updating the ith short message to the threads table. Assuming that n is three short messages of the same contact person, the time required for inserting the sms table is 1 s/bar; the threads need 1s for traversing 1 short message, 2s for traversing 2 short messages, and 3s for traversing 3 short messages; the duration of T1 is 1s×3+1s+2s+3s=9s.
However, the total time T2 consumed for backup of short messages in the present application is determined by the following formula (2):
wherein m is<n; t2 represents the total time required by backup of n pieces of short messages in the application, n represents n pieces of short messages to be backed up, m represents m contacts in sms list, sms i Representing the time required for inserting the ith short message into sms list, threads j Representing the time required to traverse the short message in the sms table for the jth contact.
Continuing the assumption above, if the time required to insert the sms table is 1 s/bar; the threads table only needs to traverse the last 3 short messages for 3s; the duration of T2 is 1s×3+3s=6s, and compared with the prior art, the method and the device consume 9s, and can save the duration required for backing up the short message.
In addition, when the number of short messages to be backed up is larger, the time consumption of copying and backup of a large number of short messages can be saved through the method and the device.
Referring to fig. 6, a short message processing display interface in the related art is shown, in which the left column is a contact session interface generated according to sms table, and the right column is a short message list interface generated according to threads table. Wherein:
(1) Regarding the contact session interface:
and each time a short message is written in the sms table, adding a short message to the contact session interface and displaying the short message. For example, the number of the contact Zhang Mou is "138XXXX0000", three pieces of short messages are total, after the first piece of short message is received in the sms table, a contact session interface as "left-1" in fig. 6 is generated according to the sms table, and at this time, the contact session interface only contains one piece of short message; similarly, after the second short message is written in the sms table, generating a contact session interface of the left-2 in fig. 6 according to the sms table, wherein the contact session interface displays two short messages; the same principle as "left-3" in fig. 6 will be shown for 3 short messages, and will not be repeated here.
(2) Regarding the short message list interface:
due to the trigger function, whenever the sms table changes, the corresponding short message list interface as the right column in fig. 6 also changes. For example, continuing to take the foregoing Zhang Mou as an example, the "right-1" in fig. 6 is to insert the first short message into the sms table, and after synchronously updating the threads table, the short message list interface displays the first short message. Then, inserting a second short message into the sms table, and updating the short message with the maximum time mark of Zhang Mou in the short message list interface of 'right-2' in fig. 6 into the second short message, namely, the short message received by '12:00 in noon of 4.5'; in addition, the same thing as "right-3" in fig. 6, the latest short message of the contact is changed to the short message received by "4.8 afternoon 18:00".
Therefore, it is determined that in the related art, the display of the short message list interface may change with the update of the contact session interface. That is, the content of the display interface will change with the continuous update of the threads table, and the short message with the largest time stamp of the same contact (e.g. Zhang Mou) will change continuously. When a large number of short messages are backed up, the short message list interface is continuously refreshed and changed, but in practice, the content change process of the short message list interface based on the threads table is not needed, and after the backup is finished, the threads table can be ensured to store the short messages of one day with the largest time mark of each contact person. In contrast, in order to compare the difference between the present application and the related art, the state of the display interface of the terminal in the embodiment of the present application may be as shown in fig. 7.
Referring to fig. 7, the change from "left-1" to "left-3" of the contact session interface displayed in the left column of fig. 7 is the same as the implementation procedure in fig. 6, and will not be repeated here. However, the short message list interface in the right column is implemented by the method of the application, and after the last short message is written, the corresponding contact list interface is generated after the short message with the largest time mark is obtained. Continuing with the aforementioned Zhang Mou example, the "right-1" in fig. 7 is the short message with the largest time stamp of Zhang Mou, that is, the interfaces of "right-1" and "right-2" in fig. 6 are not required and will not be displayed in the present application. Therefore, in the embodiment of the application, the short message list interface based on the threads table has no middle change process, so that unnecessary refreshing of the interface can be avoided. In addition, through the display interface provided by the application, the time consumption of frequent change of the threads table due to triggering is reduced in the process of backing up a large number of short messages in a short time.
As shown in fig. 8, an embodiment of the present application provides a terminal, including an input unit 801, a processor 802, and a display 803;
the input unit 801 is configured to receive a short message backup instruction;
the processor 802 is configured to respond to the short message backup instruction, and write a plurality of short messages to be backed up into a short message service table;
after the plurality of short messages are written into the short message service table, acquiring one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for marking the receiving time or the sending time of the short message;
writing one short message with the maximum time mark of each contact into an association table;
the display 803 is configured to display a contact session interface corresponding to each contact generated according to the short message service table; or displaying a short message list interface generated according to the association table.
In one possible implementation, the processor 802 is further configured to:
after receiving the short message backup instruction and before responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table, closing a triggering function in a short message database, wherein the triggering function is used for triggering updating of the association table once when one short message is written into the short message service table.
In one possible implementation, if the trigger function in the short message database is turned off, after writing the plurality of short messages into a short message service table, the processor 802 is further configured to:
when receiving a broadcast notification message sent by the short message database and used for indicating that the plurality of short messages are written in the short message service table, restarting the triggering function; or,
after receiving a query instruction for designating a Uniform Resource Identifier (URI), querying the designated URI, and restarting the trigger function according to the resource indicated by the designated URI; the query instruction of the appointed URI is sent by the short message database after the plurality of short messages are written into the short message service table.
In a possible implementation, the indicated resource is a restart instruction for restarting the trigger function; when the triggering function is re-enabled according to the resource indicated by the specified URI, the processor 802 is configured to:
searching the restart instruction indicated by the appointed URI;
executing the restarting instruction starts a triggering function in the short message database for the association table.
In one possible implementation, before writing the plurality of short messages to be backed up into the short message service table, the processor 802 is further configured to:
analyzing the plurality of short messages to obtain each contact in the plurality of short messages;
generating a unique identifier of each contact in the association table, and creating a short message record for the contact in the association table according to the unique identifier;
when writing the short message with the maximum time stamp of each contact into the association table, the processor 802 is configured to:
and writing one short message with the maximum time mark of the contact into a short message record corresponding to the unique identifier in the association table according to the unique identifier corresponding to the contact.
Since the computer storage medium in the embodiments of the present application may be applied to the above-mentioned method, the technical effects that can be obtained by the computer storage medium may also refer to the above-mentioned method embodiments, and the embodiments of the present application are not described herein again.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.
Claims (6)
1. The terminal is characterized by comprising an input unit, a processor and a display screen;
the input unit is used for receiving a short message backup instruction;
the processor is used for responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table;
after the plurality of short messages are written into the short message service table, acquiring one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for marking the receiving time or the sending time of the short message;
Writing one short message with the maximum time mark of each contact into an association table;
the display screen is used for displaying a contact person session interface corresponding to each contact person generated according to the short message service table; or displaying a short message list interface generated according to the association table;
the processor is further configured to: after receiving the short message backup instruction and before responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table, closing a triggering function in a short message database, wherein the triggering function is used for triggering updating of the association table once when one short message is written into the short message service table;
if the triggering function in the short message database is closed, after the plurality of short messages are written into the short message service table, the processor is further configured to:
when receiving a broadcast notification message sent by the short message database and used for indicating that the plurality of short messages are written in the short message service table, restarting the triggering function; or,
after receiving a query instruction for designating a Uniform Resource Identifier (URI), querying the designated URI, and restarting the trigger function according to the resource indicated by the designated URI; the query instruction of the appointed URI is sent by the short message database after the plurality of short messages are written into the short message service table.
2. The terminal of claim 1, wherein the indicated resource is a restart instruction to re-enable the trigger function; when the triggering function is re-enabled according to the resource indicated by the specified URI, the processor is configured to:
searching the restart instruction indicated by the appointed URI;
executing the restarting instruction starts a triggering function in the short message database for the association table.
3. The terminal of claim 1, wherein prior to writing the plurality of short messages to be backed up in a short message service table, the processor is further configured to:
analyzing the plurality of short messages to obtain each contact in the plurality of short messages;
generating a unique identifier of each contact in the association table, and creating a short message record for the contact in the association table according to the unique identifier;
when writing the short message with the maximum time mark of each contact into the association table, the processor is configured to:
and writing one short message with the maximum time mark of the contact into a short message record corresponding to the unique identifier in the association table according to the unique identifier corresponding to the contact.
4. A method for processing short messages, the method comprising:
responding to a short message backup instruction, and writing a plurality of short messages to be backed up into a short message service table;
after the plurality of short messages are written into the short message service table, acquiring one short message with the largest time mark of each contact in the plurality of short messages from the short message service table; the time mark is used for marking the receiving time or the sending time of the short message;
writing one short message with the maximum time mark of each contact into an association table;
the method further comprises the steps of: after receiving the short message backup instruction and before responding to the short message backup instruction and writing a plurality of short messages to be backed up into a short message service table, closing a triggering function in a short message database, wherein the triggering function is used for triggering updating of the association table once when one short message is written into the short message service table;
if the triggering function in the short message database is closed, after the plurality of short messages are written into the short message service table, the method further comprises:
when receiving a broadcast notification message sent by the short message database and used for indicating that the plurality of short messages are written in the short message service table, restarting the triggering function; or,
After receiving a query instruction for designating a Uniform Resource Identifier (URI), querying the designated URI, and restarting the trigger function according to the resource indicated by the designated URI; the query instruction of the appointed URI is sent by the short message database after the plurality of short messages are written into the short message service table.
5. The method of claim 4, wherein the indicated resource is a restart instruction to re-enable the trigger function; the re-enabling the trigger function according to the resource indicated by the specified URI includes:
searching the restart instruction indicated by the appointed URI;
executing the restarting instruction starts a triggering function in the short message database for the association table.
6. The method of claim 4, wherein prior to writing the plurality of short messages to be backed up in the short message service table, the method further comprises:
analyzing the plurality of short messages to obtain each contact in the plurality of short messages;
generating a unique identifier of each contact in the association table, and creating a short message record for the contact in the association table according to the unique identifier;
Writing the short message with the maximum time mark of each contact into an association table, wherein the writing comprises the following steps:
and writing one short message with the maximum time mark of the contact into a short message record corresponding to the unique identifier in the association table according to the unique identifier corresponding to the contact.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010345771.XA CN113641533B (en) | 2020-04-27 | 2020-04-27 | Terminal and short message processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010345771.XA CN113641533B (en) | 2020-04-27 | 2020-04-27 | Terminal and short message processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113641533A CN113641533A (en) | 2021-11-12 |
| CN113641533B true CN113641533B (en) | 2024-03-12 |
Family
ID=78415199
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010345771.XA Active CN113641533B (en) | 2020-04-27 | 2020-04-27 | Terminal and short message processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113641533B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100577735B1 (en) * | 2005-09-06 | 2006-05-10 | 한 중 이 | Processing back-up service system which uses the mobile telecommunication terminal it perceives update information |
| CN103200233A (en) * | 2013-03-05 | 2013-07-10 | 广东欧珀移动通信有限公司 | Message back-up method based on increment and system thereof |
| CN103577280A (en) * | 2012-07-30 | 2014-02-12 | 北京网秦天下科技有限公司 | Method and system for duplicating data |
| FI20135761A (en) * | 2013-07-10 | 2015-01-11 | Elisa Oyj | Smart SMS service |
| CN106304028A (en) * | 2016-10-26 | 2017-01-04 | 广东小天才科技有限公司 | Address book backup and the method and device of recovery |
| CN106599071A (en) * | 2016-11-18 | 2017-04-26 | 青岛海信移动通信技术股份有限公司 | Short message display method and device |
| WO2018113151A1 (en) * | 2016-12-23 | 2018-06-28 | 华为技术有限公司 | Method and terminal for displaying information |
| EP3382994A1 (en) * | 2017-03-28 | 2018-10-03 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and apparatus for updating data |
| US10382420B1 (en) * | 2003-07-11 | 2019-08-13 | Shelton E. Harrison, Jr. | Website owner verification system, method, and device |
| CN110968574A (en) * | 2018-09-30 | 2020-04-07 | 青岛海信移动通信技术股份有限公司 | Data migration method and terminal |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8126848B2 (en) * | 2006-12-07 | 2012-02-28 | Robert Edward Wagner | Automated method for identifying and repairing logical data discrepancies between database replicas in a database cluster |
| CN102647702B (en) * | 2011-12-06 | 2017-11-24 | 中兴通讯股份有限公司 | A kind of information of mobile terminal copy backup device and method |
| US8806281B1 (en) * | 2012-01-23 | 2014-08-12 | Symantec Corporation | Systems and methods for displaying backup-status information for computing resources |
| CN103685406B (en) * | 2012-09-19 | 2018-09-25 | 腾讯科技（深圳）有限公司 | The method and device of mobile terminal contact person backup |
| WO2016081373A1 (en) * | 2014-11-18 | 2016-05-26 | Globally Tele-Connected, Llc | System, maethod and computer program product for contact information backup and recovery |
| CN106648986A (en) * | 2016-12-23 | 2017-05-10 | 宇龙计算机通信科技(深圳)有限公司 | Data backup method and data backup device |
-
2020
- 2020-04-27 CN CN202010345771.XA patent/CN113641533B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10382420B1 (en) * | 2003-07-11 | 2019-08-13 | Shelton E. Harrison, Jr. | Website owner verification system, method, and device |
| KR100577735B1 (en) * | 2005-09-06 | 2006-05-10 | 한 중 이 | Processing back-up service system which uses the mobile telecommunication terminal it perceives update information |
| CN103577280A (en) * | 2012-07-30 | 2014-02-12 | 北京网秦天下科技有限公司 | Method and system for duplicating data |
| CN103200233A (en) * | 2013-03-05 | 2013-07-10 | 广东欧珀移动通信有限公司 | Message back-up method based on increment and system thereof |
| FI20135761A (en) * | 2013-07-10 | 2015-01-11 | Elisa Oyj | Smart SMS service |
| CN106304028A (en) * | 2016-10-26 | 2017-01-04 | 广东小天才科技有限公司 | Address book backup and the method and device of recovery |
| CN106599071A (en) * | 2016-11-18 | 2017-04-26 | 青岛海信移动通信技术股份有限公司 | Short message display method and device |
| WO2018113151A1 (en) * | 2016-12-23 | 2018-06-28 | 华为技术有限公司 | Method and terminal for displaying information |
| EP3382994A1 (en) * | 2017-03-28 | 2018-10-03 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and apparatus for updating data |
| CN110968574A (en) * | 2018-09-30 | 2020-04-07 | 青岛海信移动通信技术股份有限公司 | Data migration method and terminal |
Non-Patent Citations (3)
| Title |
|---|
| Radio Frequency Identification (RFID) Based Attendance System with Short Message Service (SMS) Backup;Sarmad Hameed 等;《IOSR Journal of Computer Engineering (IOSR-JCE) 》;第21卷(第2期);全文 * |
| VC十十．Net 2003数据库访问技术要点及相关技巧;胡为民;《安庆师范学院学报（ 自然科学版）》;第11卷(第1期);第25页 * |
| 基于混合策略的低成本云存储方案;李松涛 等;《计算机应用》;第34卷(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113641533A (en) | 2021-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111597000B (en) | Small window management method and terminal | |
| CN110865837B (en) | Method and terminal for system upgrade | |
| CN111225108A (en) | Communication terminal and card display method of negative screen interface | |
| CN113656490B (en) | Data synchronization method, device, terminal and storage medium | |
| CN111597004B (en) | Terminal and user interface display method in application | |
| CN113835571A (en) | Terminal device, information display method and storage medium | |
| CN113709026B (en) | Method, device, storage medium and program product for processing instant communication message | |
| CN111176766A (en) | Communication terminal and component display method | |
| CN111506237A (en) | Terminal and method for starting operation function in application | |
| CN112099892B (en) | Communication terminal and method for rapidly scanning two-dimension code | |
| CN113055585B (en) | Thumbnail display method of shooting interface and mobile terminal | |
| CN112825072B (en) | Communication terminal and data sharing method | |
| CN114449171B (en) | Method for controlling camera, terminal device, storage medium and program product | |
| CN114371895B (en) | Terminal equipment, mail marking method and storage medium | |
| CN114546219B (en) | Picture list processing method and related device | |
| CN113641533B (en) | Terminal and short message processing method | |
| CN113157092B (en) | Visualization method, terminal device and storage medium | |
| CN111163220B (en) | Display method, communication terminal and computer storage medium | |
| CN111324255B (en) | Application processing method based on double-screen terminal and communication terminal | |
| CN111159734A (en) | Communication terminal and multi-application data inter-access processing method | |
| CN113642010B (en) | Method for acquiring data of extended storage device and mobile terminal | |
| CN114143456B (en) | Photographing method and device | |
| CN111142648B (en) | Data processing method and intelligent terminal | |
| CN113254132B (en) | Application display method and related device | |
| CN113253905B (en) | Touch method based on multi-finger operation and intelligent terminal |
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: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11 Applicant after: Qingdao Hisense Mobile Communication Technology Co.,Ltd. Address before: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11 Applicant before: HISENSE MOBILE COMMUNICATIONS TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |