CN113641533A

CN113641533A - Terminal and short message processing method

Info

Publication number: CN113641533A
Application number: CN202010345771.XA
Authority: CN
Inventors: 张博; 林新茂; 赵云
Original assignee: Hisense Mobile Communications Technology Co Ltd
Current assignee: Hisense Mobile Communications Technology Co Ltd
Priority date: 2020-04-27
Filing date: 2020-04-27
Publication date: 2021-11-12
Anticipated expiration: 2040-04-27
Also published as: CN113641533B

Abstract

The application discloses a terminal and a short message processing method, relating to the technical field of intelligent terminals, wherein 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 list, acquiring a short message with the largest time mark of each contact in the plurality of short messages from the short message service list; the time mark is used for identifying the receiving time or the sending time of the short message; and writing the short message with the maximum time mark of each contact into an association table. The method saves the time for copying and backing up the short message, improves the efficiency for backing up the short message and achieves the aim of saving processing resources.

Description

Terminal and short message processing method

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 key switch function, and can realize the backup of terminal data to a new terminal, and in the backup process, communication applications such as short messages and the like in the new terminal need to be restored by inserting a database.

The inventors found that if the amount of data is large, there is a problem in that the backup of short messages takes a relatively large amount of time, and as the number of short messages is larger, the time consumption does not increase linearly with the number of short messages, but tends to increase almost exponentially. That is, as the number of short messages increases, the time for backing up each short message increases, 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 exemplary embodiments of the present application provide a terminal and a short message processing method, so as to save the time for short message backup and improve the efficiency of short message backup, thereby achieving the purpose of saving processing resources.

According to a first aspect of exemplary embodiments, there is provided a terminal including 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 list, acquiring a short message with the largest time mark of each contact in the plurality of short messages from the short message service list; the time mark is used for identifying the receiving time or the sending time of the short message;

writing the short message with the largest time mark of each contact into an association table;

the display screen is used for displaying a contact person conversation 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 list.

The inventor researches and discovers that in the related art, after a short message is written into a short message service table, the trigger function is caused to traverse the short message service table, so that the association table is updated, and the short message backup time is too 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 the backup or the copy of the short message 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 writing a plurality of short messages to be backed up into a short message service table in response to the short message backup instruction, closing a triggering function in a short message database, wherein the triggering function is used for triggering the updating of the association table once every time one short message is written into the short message service table.

In the related art, the short message database includes a trigger function, such as a trigger, for triggering 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 updating of the association table caused by the change of the short message every time is avoided, and the time for copying the short message is saved.

In a possible implementation manner, if the trigger function in the short message database is turned off, after the plurality of short messages are written in the short message service table, the processor is further configured to:

when receiving a broadcast notification message which is sent by the short message database and used for indicating that the plurality of short messages are written into the short message service table, re-starting the trigger function; alternatively, the first and second electrodes may be,

after receiving a query instruction for a designated Uniform Resource Identifier (URI), querying the designated URI, and re-starting the trigger function according to the resource indicated by the designated URI; the query instruction of the designated URI is sent by the short message database after the short messages are written into the short message service table.

By the implementation mode, 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 embodiment, the indicated resource is a restart instruction for re-enabling the trigger function; when the triggering function is re-enabled according to the resource indicated by the specified URI, the processor is used for:

searching the restart instruction indicated by the specified URI;

and executing the restart instruction to start a trigger function in the short message database for the association table.

The embodiment provides an implementation manner for restarting the trigger function in the short message database, and when the trigger function is restarted by querying the specified URI, the restart of the trigger function can be realized through the matching relationship between the specified URI and the restart instruction.

In a 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 the short message with the largest time stamp of each contact is written into the association table, the processor is configured to:

and writing the short message with the largest time mark of the contact person into a short message record corresponding to the unique identifier in an association table according to the unique identifier corresponding to the contact person.

The updating of the association table is realized through the unique identifier of the contact person, so that the short message with the maximum time mark of each contact person is accurately updated into the association table.

According to a second aspect of the exemplary embodiments, there is provided a short message processing 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;

and writing the short message with the maximum time mark of each contact into an association table.

In one possible embodiment, the method further comprises:

In a possible implementation manner, if the trigger function in the short message database is turned off, after the plurality of short messages are written in the short message service table, the method further includes:

In a possible embodiment, the indicated resource is a restart instruction for re-enabling the trigger function; the re-enabling of the trigger function according to the resource indicated by the specified URI comprises the following steps:

searching the restart instruction indicated by the specified URI;

In a possible implementation manner, before writing the plurality of short messages to be backed up into the short message service table, the method further includes:

writing the short message with the largest time stamp of each contact into an association table, wherein the writing of the short message with the largest time stamp comprises the following steps:

In a third aspect, the present application further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by the processing unit, implements the steps of the short message processing method according to the second aspect.

In addition, for technical effects brought by any one implementation manner of the second aspect and the third aspect, reference may be made to technical effects brought by different implementation manners of the first aspect, and details are not described here.

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 the common knowledge in the field, the above preferred conditions can be combined randomly to obtain the preferred embodiments of the application.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

fig. 2 is a schematic diagram illustrating a software architecture of a terminal according to an embodiment of the present application;

fig. 3 is a schematic flowchart illustrating a short message processing method according to an embodiment of the present application;

FIG. 4 is a diagram illustrating an operation interface of a key switch provided in an embodiment of the present application;

fig. 5 is a diagram illustrating a comparison of a short message processing method according to an embodiment of the present application;

fig. 6 is a diagram schematically illustrating a display interface comparison of a short message process in the related art;

fig. 7 is a comparative display interface diagram illustrating an exemplary short message processing method according to an embodiment of the present application;

fig. 8 schematically illustrates a terminal structure provided in an embodiment of the present application.

Detailed Description

The technical solution in the embodiments of the present application will be described in detail and removed with reference to the accompanying drawings. In the description of the embodiments of the present application, "a plurality" means two or more.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of embodiments of the application, unless stated otherwise, "plurality" means two or more.

First, fig. 1 shows a schematic structural diagram of a terminal 100.

The following describes an embodiment specifically by taking the terminal 100 as an example. It should be understood that the terminal 100 shown in fig. 1 is merely an 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 block diagram of a hardware configuration of the terminal 100 according to an exemplary embodiment is exemplarily shown in fig. 1. As shown in fig. 1, the terminal 100 includes: a Radio Frequency (RF) circuit 110, a memory 120, a display unit 130, a camera 140, a sensor 150, an audio circuit 160, a Wireless Fidelity (Wi-Fi) module 170, a processor 180, a bluetooth module 181, and a power supply 190.

The RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and may receive downlink data of a base station and then send the downlink data to the processor 180 for processing; the uplink data may be transmitted to the base station. Typically, the RF circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The 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 executing software programs or data stored in the memory 120. The 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 may store an operating system and various application programs, and may also store program codes for performing the methods described in the embodiments of the present application.

The display unit 130 may be used to receive input numeric or character information and generate signal input related to user settings and function control of the terminal 100, and particularly, the display unit 130 may include a touch screen 131 disposed on the front surface of the terminal 100 and may collect touch operations of a user thereon or nearby, such as clicking a button, dragging a scroll box, and the like.

The display unit 130 may also be used to display a Graphical User Interface (GUI) of information input by or provided to the user and various menus of the terminal 100. Specifically, the display unit 130 may include a display screen 132 disposed on the front surface of the terminal 100. The display screen 132 may be configured in the form of a liquid crystal display, a light emitting diode, or the like. The display unit 130 may be configured 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 the input and output functions of the terminal 100, and after the integration, the touch screen may be referred to as a touch display screen for short. In the present application, the display unit 130 may display the application programs and the 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 to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing elements convert the light signals into electrical signals which are then passed to the processor 180 for conversion into digital image signals.

The terminal 100 may further comprise 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 a gyroscope, barometer, hygrometer, thermometer, infrared sensor, light sensor, motion sensor, etc.

Audio circuitry 160, speaker 161, and microphone 162 may provide an audio interface between a user and terminal 100. 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. The terminal 100 may also be provided 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, converts the electrical signal into audio data after being received by the audio circuit 160, and outputs the audio data 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. In this application, the microphone 162 may capture the voice of the user.

Wi-Fi belongs to a short-distance wireless transmission technology, and the terminal 100 can help a user to send and receive e-mails, browse webpages, access streaming media, and the like through the Wi-Fi module 170, and provides wireless broadband internet access 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, processor 180 may include one or more processing units; the processor 180 may also integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a baseband processor, which mainly handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 180. In the present application, the processor 180 may run an operating system, an application program, a user interface display, and a touch response, and the processing method described in the embodiments of the present application. Further, the processor 180 is coupled with the display unit 130.

And 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) having a bluetooth module via the bluetooth module 181, so as to perform data interaction.

The terminal 100 also includes a power supply 190 (e.g., a battery) to power the various components. The power supply may be logically connected to the processor 180 through a power management system to manage charging, discharging, power consumption, etc. through the power management system. The terminal 100 may also be configured with power buttons for powering the terminal on and off, and locking the screen.

Fig. 2 is a block diagram of a software configuration of the terminal 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system may be divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer, from top to bottom, respectively.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain 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 it accessible to applications. The data may include video, images, audio, dialed and answered calls, browsing history and bookmarks, phone books, 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, the display interface including the short message notification icon may include a view for displaying text and a view for displaying a picture.

The phone manager is used to provide a communication function of the terminal 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources, such as localized strings, icons, pictures, layout files, video files, etc., to the application.

The notification manager allows the application to display notification information (e.g., message digest of short message, message content) in the status bar, can be used to convey notification-type messages, and can automatically disappear after a short dwell without user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, 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, text information is prompted in the status bar, a prompt tone is given, the terminal vibrates, an indicator light flashes, and the like.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises 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. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

A 2D (an animation mode) 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 following describes exemplary workflow of the terminal 100 software and hardware 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 an original input event (including touch coordinates, a time stamp of the touch operation, and other information). The raw input events are stored at the kernel layer. And the application program framework layer acquires the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation, and taking a control corresponding to the click operation as a control of a camera application icon as an example, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera drive by calling a kernel layer, and captures a still image or a 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 herein are explained below:

short message service table: that is, a sms (Short Message Service) table, configured to store detailed contents of each Short Message, refer to table 1, which is an example of a sms table provided in an embodiment of the present application, and includes the following specific contents:

TABLE 1

_id

threads_id

body

date

address

Table 1 will now be described with reference to the following points:

(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 from 1 to 100 lines;

(2) the 'threads _ id' is an identifier linked with a unique identifier 'id' of a contact person in a threads table and is used for identifying different contact persons, for example, if the short message in the sms table comprises short messages interacted with 6 different contact persons, the value of the threads _ id is 1-6;

(3) the body is used for representing the specific content of the short message;

(4) "date" represents the time stamp of the line of short message record, i.e. the receiving time or sending time of the line of short message;

(5) the address is used for indicating the number of the contact person interacting with the short message.

It should be noted that only a part of the contents of the sms table is shown in table 1, which does not mean that only these contents are included, and the present application is not limited thereto.

(II) association table: that is, the threads table is used to store a short message with the largest timestamp in each contact session record, that is, a short message with the latest receiving time or sending time in each contact session, referring to table 2, which is an example of a threads table provided in the embodiment of the present application, and the specific contents are as follows:

TABLE 2

_id

date

snippet

Table 2 will now be described with reference to the following points:

(1) "id" in table 2 is a line number in the threads table, and is used to indicate a unique identifier of a contact in the threads table, and the total number of lines of "id" is the number of the contact, for example, if 100 short messages in the sms table are obtained by interacting with 6 contacts respectively, the "id" in the threads table includes 6 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 indicates the time stamp recorded for the line of short messages, i.e. the time of receiving or sending the short message;

(3) "snippet" indicates the specific content for the line of short messages.

It should be noted that, in table 2, only a part of the contents in the reads table is also given, and the contents are not meant to include only these contents, which is not limited in the present application.

Aiming at the problem that the short message copying or backup consumes a lot of time at present, according to the research and discovery of the inventor, the problem of long time consumption in the related technology is mainly that the short message and the contact database both contain a lot of triggers with triggering functions. When each piece of data is inserted, the traversal query and update operations on the short message service table are triggered, so that the time consumption of the traversal query and update operations is longer as the number of the pieces is larger, and the problem that the time required for copying the data volume is longer under the condition of increasing the data volume is caused. For example, the short message database contains sms tables and threads tables, and because the short message database has a trigger for updating the threads tables in real time according to the sms tables, the threads tables are also updated correspondingly and synchronously when the sms tables change each time.

The embodiment of the application is not only suitable for a one-key-change scene, but also suitable for cloud backup and other applications for copying, backing up or recovering the short messages. For the applications, as a plurality of short messages are inserted into the sms table, if a short message is inserted into the sms table, the clocks table is synchronously updated after traversing the sms table, namely, the clocks table is updated in a traversing manner every time the sms table changes. But in fact, the content in the reads table is the content of the short message with the largest time stamp of each contact in the sms table, so when the backup of the short message by the sms table is not completed, the update of the reads is likely to be overwritten by the short message subsequently inserted into the sms table. In this case, the previous synchronous update of the reads table is meaningless, and the time consumption for copying or backing up the whole short message becomes too long due to the update of the reads table.

In view of this, the present application provides a short message processing method, which reduces the time consumption for short message backup or copying in a short message recovery 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 S301, responding to the short message backup command, writing a plurality of short messages to be backed up into a short message service list.

In one possible embodiment, the short message backup instruction is a key exchange instruction, which can be understood as the key exchange instruction 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 prepares to backup the short message to be backed up transmitted from the terminal device a received in the network, that is, the terminal B prepares to write the short message into the short message service table.

Referring to fig. 4, an operation interface of a key switch provided in the embodiment of the present application is shown, where after "i is a new mobile phone" on the interface is clicked, a plurality of short messages to be backed up are received; and then responding to the click command, and writing the received short messages to be backed up into a short message service table, namely an sms table. If the interface of fig. 4 is displayed on the old terminal, after the user clicks "i is the old mobile phone" on the interface, in a possible implementation manner, the old terminal generates a two-dimensional code, waits for the new terminal to scan the two-dimensional code, and after receiving a backup instruction sent by the new terminal based on the two-dimensional code, sends the contents of a plurality of short messages to be backed up of the old terminal to the new terminal. Of course, the two-dimensional code is only an example, and the old terminal and the new terminal may be associated in other ways during implementation, so as to implement the one-key-switch function.

In another possible embodiment, the short message backup instruction is a cloud backup instruction, which may be understood as that the cloud backup instruction is used to backup the plurality of short messages stored in the cloud server, and the implementation manner is similar to a one-key-change scenario, and is not described herein again.

Step S302, after writing the short messages into the short message service list, acquiring a short message with the largest time mark of each contact in the short messages from the short message service list; the time mark is used for identifying the receiving time or the sending time of the short message.

Step S303: and writing the short message with the maximum time mark of each contact into an association table.

The association table is used for storing a short message with the largest time mark of each contact person.

When the method is implemented, a short message service table and an 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 the updating of the association table once a short message is written in the short message service table; in one possible embodiment, the trigger function may be implemented by a trigger.

In a possible embodiment, after the first short message in the plurality of short messages to be backed up is updated to the short message service table, the triggering function in the short message database can be closed; for example, the embodiment of closing the trigger in the short message database can be implemented by the embodiment shown in table 3 below, as follows:

TABLE 3

As shown in table 3, the triggers included in the short message database at least include two types of triggers, one type is a trigger for updating, and the trigger is mainly used for updating the content in the reads table according to the short message change of the sms table; for example, when a short message with updated time of an existing contact is received, the specific content of the short message corresponding to the contact in the downloads table is updated. The other type is a trigger for insertion, which is mainly used for realizing the operation of inserting the bits table according to the short message change of the sms table; for example, when the sms table receives a short message of a new contact conversation, the short message of the contact is inserted into the downloads table.

After the triggering function is closed, if the short message service table changes, the association table will not be updated synchronously because the triggering 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 one possible implementation manner, when a broadcast notification message which is 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 restarted.

In another possible implementation manner, after a query instruction for a specified Uniform Resource Identifier (URI) is received, the specified URI is queried, and the trigger function is restarted according to the resource indicated by the specified URI; the query instruction of the designated URI is sent by the short message database after the short messages are written into the short message service table.

For example, if there are 100 short messages to be backed up, after 100 short message records are all inserted into the sms table, indicating that the writing of the sms table for the 100 short messages is completed, the short message database will send a notification of the completion of the backup; the notification may be implemented by a broadcast notification message sent or determined by querying a pre-agreed specific URI, and when a short message service component (for example, a ContentProvider component of one of four major components in an Android) for updating the broadcasts table receives the broadcast notification message or receives a query instruction for the specific URI, it is determined that the backup of the short message service table is completed, and then a trigger function in the short message database is re-enabled.

When the operation of inquiring the specified URI is implemented, the indicated resource is a restart instruction for re-enabling the trigger function; when a query instruction for a specified URI is received, searching the restart instruction indicated by the specified URI; and executing the restart instruction to start a trigger 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

In addition, before writing the plurality of short messages to be backed up into the short message service table, the method further comprises the following steps: 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, the method determines that the short message to be backed up has a plurality of contacts in total by analyzing the contact identification of the short message. For example, if the parsed content includes 3 contacts, session records of 3 rows of contacts are generated in the threads table, for example, "_ id" includes 1, 2, and 3.

The created short message record is optional, and the short message which is analyzed to correspond to the contact person at first can be recorded in the threads table to be used as the created initial short message record of the threads table. In addition, after the backup of the sms list is completed, analyzing each short message in the sms list, and after a short message with the largest time stamp of each contact is obtained, writing the short message with the largest time stamp of the contact into a short message record corresponding to the unique identifier in an association list according to the unique identifier corresponding to the contact. For example, if the short message with the largest timestamp of the contact with "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 corresponding to the "thread _ id" of 1 in the threads table.

When analyzing the short messages in the short message service table to obtain a short message with the largest time stamp of each contact in the short messages, an optional implementation manner includes: for each contact, respectively performing: extracting the 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 largest time mark of the contact according to the comparison result.

In implementation, through the introduction of the specific contents of the sms table and the reads table, it can be determined that the 'reads _ id' in the sms table is linked with the 'id' in the reads table, and after the sms update is completed, a total number of contacts can be determined according to the 'reads _ id' in the sms table; then, in each contact, searching and comparing a short message with the largest time mark of each contact according to the 'date'. For example, if there are 3 short messages of contact a in the sms list, and the receiving or sending time is 4 months and 9 days, 4 months and 10 days, and 4 months and 11 days, respectively, it is determined that the short message received or sent on 4 months and 11 days is the one with the largest timestamp with the contact.

In the short message processing method provided in the embodiment of the present application, the trigger function of the trigger is turned off, so that the efficiency of short message backup is improved, and in order to more clearly understand the technical scheme of improving the efficiency through the present application, referring to fig. 5, a comparison schematic diagram of a short message processing method provided for implementation of the present application, it may be determined from fig. 5 that the total time T1 consumed for the backup of a short message in the related art may be determined according to the following formula (1):

wherein, T1 represents the total time needed for the backup of n short messages in the related art, n represents n short messages to be backed up in total, sms_iIndicates the time required for inserting sms table into the ith short message, threads_iIndicating the time required to traverse the sms table for updating the ith short message to the reads table. Supposing that n is three short messages of the same contact person, and the time required for inserting the short messages into the sms list is 1 s/short message; 1s is needed for the threads to traverse 1 short message, 2s is needed for the threads to traverse 2 short messages, and 3s is needed for the threads to traverse 3 short messages; the duration of T1 is 1s × 3+1s +2s +3s — 9 s.

However, the total time T2 consumed for the backup of the short message in the present application is determined by the following formula (2):

wherein m is<n; t2 represents the total time needed by backup of n short messages in the application, n represents n short messages to be backed up in total, m represents m contacts in the sms list, and sms represents_iIndicates the time required for inserting sms table into the ith short message, threads_jIndicating the time required for traversing the short message of the jth contact in the sms table.

Continuing the above assumption, 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 3 s; the duration of T2 is 1s × 3+3s — 6s, which saves the duration required for backing up the short message compared to the prior art which consumes 9 s.

In addition, when the number of short messages to be backed up is larger, a large amount of time for copying and backing up the short messages can be saved by the method and the device.

Referring to fig. 6, a display interface for processing short messages in the related art is shown, in which the left column is a contact conversation interface generated according to an sms table, and the right column is a short message list interface generated according to a reads table. Wherein:

(1) regarding the contact session interface:

and adding a short message to the contact person conversation interface and displaying the short message every time when the short message is written into the sms list. For example, the number of a contact person is "138 XXXX 0000", three short messages are provided, and after the first short message is written in the sms table, a contact person conversation interface as shown in "left-1" in fig. 6 is generated according to the sms table, and at this time, the contact person conversation interface only contains one short message; similarly, after the second short message is written into the sms table, a contact person conversation interface like "left-2" in fig. 6 is generated according to the sms table, and at this time, the contact person conversation interface displays two short messages; the same as "left-3" in fig. 6, 3 short messages will be displayed, and will not be described herein.

(2) Regarding the short message list interface:

due to the trigger function, every time the sms table changes, the corresponding short message list interface in the right column of fig. 6 also changes. For example, continuing with the above-mentioned example, after the first short message is inserted into the sms table and the downloads table is synchronously updated as shown in "right-1" of fig. 6, the short message list interface displays the first short message. Then, inserting a second short message into the sms table, updating the short message list interface of the right-2 in fig. 6 with the largest time mark as the second short message, namely the short message received at 12:00 noon at 4.5; in addition, in the same manner as "right-3" in fig. 6, the latest short message of the contact on the short message list interface is changed to a short message received at "4.8 pm 18:00 pm".

It is determined that the display of the short message list interface on the display interface may vary with the update of the contact session interface in the related art. That is, the content of the display interface changes with the continuous update of the downloads table, and the short message with the largest timestamp of the same contact (e.g. zhang-a) changes continuously. When a large number of short messages are backed up, the short message list interface is continuously refreshed and changed, but actually, 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 is ensured to store the short messages of the day with the largest time mark of each contact person. In contrast, in order to compare the differences 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 displayed contact session interface in the left column of fig. 7 is the same as the implementation process in fig. 6, and is not described again here. However, the short message list interface on the right column is implemented by the method of the application to generate the corresponding contact list interface after the last short message is written and the short message with the largest time stamp is acquired. Continuing with the above example of zhangyi, right-1 in fig. 7 is a short message with the largest timestamp, i.e. the interfaces "right-1" and "right-2" in fig. 6 need not to 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 intermediate change process, and unnecessary interface refreshing can be avoided. Moreover, through the display interface provided by the application, the time consumption of frequent change of the triggered threads table 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, which includes an input unit 801, a processor 802, and a display 803;

the input unit 801 is used for receiving a short message backup instruction;

the processor 802 is configured to, in response to the short message backup instruction, write a plurality of short messages to be backed up into a short message service table;

the display screen 803 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 list.

In one possible implementation, the processor 802 is further configured to:

In a possible implementation manner, if the trigger function in the short message database is turned off, after the plurality of short messages are written in the short message service table, the processor 802 is further configured to:

In a possible embodiment, the indicated resource is a restart instruction for re-enabling the trigger function; when the trigger 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 specified URI;

In a possible implementation manner, before writing the plurality of short messages to be backed up into the short message service table, the processor 802 is further configured to:

when the short message with the largest timestamp of each contact is written into the association table, the processor 802 is configured to:

Since the computer storage medium in the embodiment of the present application can be applied to the method, the technical effect obtained by the method can also refer to the embodiment of the method, and the embodiment of the present application is not described herein again.

As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A 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;

2. The terminal of claim 1, wherein the processor is further configured to:

3. The terminal of claim 2, wherein if the trigger function in the short message database is turned off, after writing the plurality of short messages in a short message service table, the processor is further configured to:

4. The terminal of claim 3, wherein the indicated resource is a restart instruction for re-enabling the trigger function; when the triggering function is re-enabled according to the resource indicated by the specified URI, the processor is used for:

searching the restart instruction indicated by the specified URI;

5. The terminal of claim 1, wherein before writing the plurality of short messages to be backed up to the short message service list, the processor is further configured to:

6. A short message processing method is characterized by comprising the following steps:

7. The method of claim 6, wherein the method further comprises:

8. The method of claim 7, wherein if the trigger function in the short message database is turned off, after writing the plurality of short messages in a short message service table, the method further comprises:

9. The method of claim 8, wherein the indicated resource is a restart instruction for re-enabling the trigger function; the re-enabling of the trigger function according to the resource indicated by the specified URI comprises the following steps:

searching the restart instruction indicated by the specified URI;

10. The method of claim 6, wherein before writing the plurality of short messages to be backed up to the short message service list, the method further comprises: