Short message receiving control method and system, electronic equipment and storage medium

Abstract

The invention provides a short message receiving control method and system, electronic equipment and a storage medium, the control method is applied to an intelligent terminal, and a short message daemon is adopted to scan a first actual state of a short message receiving program in a first monitoring time period; and in response to the first actual state representing that the short message receiving program is in a non-survival state, adopting the short message daemon to generate a first awakening instruction to awaken the short message receiving program. According to the method and the device, the two-way supervision and wake-up mechanism is constructed, the background process is set to send the heartbeat request at regular time to monitor the survivability of the program, and meanwhile, the strategy of uploading failure retry and breakpoint resume is adopted, so that the problems of unstable running, service interruption and the like caused by system killing or self abnormality of the program are solved; according to the method, the short message receiving program can be ensured to run stably without missing the transmission of the short message, meanwhile, the quick discovery and notification of the service abnormality are realized, and the continuity, the reliability and the operation and maintenance of the short message receiving and uploading service are improved.

Description

Technical Field

[0001] This disclosure relates to the field of SMS processing technology, and in particular to a control method, system, electronic device and storage medium for receiving SMS messages. Background Technology

[0002] Traditional SMS receiving programs refer to applications that run on mobile terminals (such as mobile phones) to listen for, obtain and upload SMS information. However, they have problems such as poor running stability, easy termination by the system, loss of SMS messages during non-running periods after restarting, and difficulty in developers noticing abnormalities in the listening function.

[0003] Traditional SMS receiving programs lack effective process keep-alive mechanisms and comprehensive anomaly monitoring systems, making them easily identified as unnecessary programs by mobile phone systems and terminated, leading to SMS reception interruptions. Furthermore, the absence of an SMS retransmission mechanism means that SMS data lost during the non-running period cannot be retrieved after the program restarts, resulting in missed messages. In addition, the lack of timely alarm notifications when the monitoring function malfunctions makes it difficult for developers to promptly identify and resolve problems, impacting overall business continuity and data integrity. Summary of the Invention

[0004] The technical problem to be solved by this disclosure is to overcome the defects in the prior art where SMS receiving programs may be killed by the mobile phone system or fail to upload SMS messages, resulting in the inability to obtain SMS messages in a timely and comprehensive manner. This disclosure provides a control method, system, electronic device and storage medium for receiving SMS messages.

[0005] This disclosure solves the above-mentioned technical problems through the following technical solution:

[0006] In a first aspect, this disclosure provides a control method for receiving text messages. The control method is applied to a smart terminal, wherein the native operating system of the smart terminal is equipped with a plurality of text message receiving programs and a text message guardian program that is matched with the text message receiving programs.

[0007] The control method includes:

[0008] The SMS guardian program is used to scan the first actual state of the SMS receiving program during the first monitoring period.

[0009] In response to the first actual state indicating that the SMS receiving program is in a non-live state, the SMS daemon generates a first wake-up command to wake up the SMS receiving program.

[0010] Optionally, the control method further includes:

[0011] The SMS receiving program is used to scan the second actual state of the SMS guardian program during the second monitoring period;

[0012] In response to the second actual state indicating that the daemon is in a non-live state, the SMS receiving program generates a second wake-up command to wake up the SMS daemon.

[0013] Optionally, the step of using the SMS guardian to scan the actual status of the SMS receiving program during the first monitoring period includes:

[0014] Get the running status of a preset number of running applications;

[0015] The running status includes the associated information of the SMS receiving program in the application;

[0016] If the information is a preset status information, it is determined that the SMS receiving program is in a live state; otherwise, it is determined that the SMS receiving program is in a non-live state.

[0017] Optionally, the control method further includes:

[0018] Keep the background process of the SMS receiving program running continuously;

[0019] And / or,

[0020] The SMS receiving program sends a heartbeat request to the server every first preset time interval;

[0021] In response to the server not detecting the request to send a heartbeat within a second preset time, the server receives a first abnormality alert message.

[0022] And / or,

[0023] The SMS data uploaded to the server is stored in the server's preset storage space;

[0024] And / or,

[0025] In response to an anomaly in the total number of SMS data acquired by the server within a third preset time period, a second anomaly alert message is generated.

[0026] Optionally, the step of keeping the background process of the SMS receiving program running continuously includes:

[0027] In response to starting a background process, the service startup command is invoked;

[0028] The timed location service is invoked based on the service startup command.

[0029] According to the timed location service, the background process is restarted by timed broadcast to form the background process loop, so that the background process of the SMS receiving program remains active.

[0030] Optionally, the SMS messages uploaded to the server have a unique identifier;

[0031] And / or,

[0032] The control method further includes:

[0033] In response to the failure of the SMS upload, the upload operation of the SMS will be continuously retried until the upload is successful;

[0034] And / or,

[0035] The SMS receiving program runs in a native Android system after obtaining administrator account privileges; the SMS receiving program has permissions to read and write files and read SMS messages.

[0036] In a second aspect, this disclosure provides a control system for receiving text messages. The control system is applied to a smart terminal, wherein the native operating system of the smart terminal is equipped with a plurality of text message receiving programs and a text message guardian program that is matched with the text message receiving programs.

[0037] The control system includes:

[0038] The first state acquisition module is used to scan the first actual state of the SMS receiving program during the first monitoring period using the SMS guardian program.

[0039] The first program wake-up module is used to generate a first wake-up command to wake up the SMS receiving program in response to the first actual state indicating that the SMS receiving program is in a non-live state.

[0040] Optionally, the control system further includes:

[0041] The second state acquisition module is used to scan the second actual state of the SMS guardian program during the second monitoring period using the SMS receiving program.

[0042] The second program wake-up module is used to respond to the second actual state indicating that the guardian program is in an inactive state, and to generate a second wake-up command using the SMS receiving program to wake up the SMS guardian program.

[0043] Optionally, the first state acquisition module includes:

[0044] The status acquisition unit is used to acquire the running status of a preset number of running applications;

[0045] The running status includes the associated information of the SMS receiving program in the application;

[0046] The status determination unit is used to determine that the SMS receiving program is in a live state in response to the information being preset status information; otherwise, it determines that the SMS receiving program is in a non-live state.

[0047] Optionally, the control system further includes:

[0048] The control module is used to keep the background process of the SMS receiving program running continuously.

[0049] And / or,

[0050] The request sending module is used to send a heartbeat request to the server every first preset time interval using the SMS receiving program;

[0051] The first anomaly alarm module is used to receive the first anomaly reminder information sent by the server in response to the server not detecting the request to send a heartbeat within a second preset time.

[0052] And / or,

[0053] The SMS data uploaded to the server is stored in the server's preset storage space;

[0054] And / or,

[0055] The second anomaly alarm module is used to generate a second anomaly reminder message in response to the abnormal SMS data obtained by the server within a third preset time.

[0056] Optionally, the control module includes:

[0057] The background process startup response unit is used to respond to the startup of a background process by calling the service startup command;

[0058] A timed location service invocation unit is used to invoke the timed location service based on the service startup command;

[0059] The timed broadcast process restart unit is used to restart the background process by timed broadcast according to the timed location service, so as to form the background process loop and keep the background process of the SMS receiving program alive.

[0060] Optionally, the SMS messages uploaded to the server have a unique identifier;

[0061] And / or,

[0062] The control system further includes:

[0063] The SMS upload retry module is used to continuously retry the SMS upload operation in response to the SMS upload failure until the upload is successful.

[0064] And / or,

[0065] The system permission configuration module is used to ensure that the environment in which the SMS receiving program runs is the native Android system after obtaining administrator account permissions; wherein, the SMS receiving program has the permissions to read and write files and read SMS messages.

[0066] A third aspect of this disclosure provides an electronic device, including a memory, a processor, and a computer program stored in the memory and for running on the processor, wherein the processor executes the computer program to implement the control method for receiving SMS messages as described in the first aspect.

[0067] In a fourth aspect, this disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the control method for receiving SMS messages as described in the first aspect.

[0068] In a fifth aspect, this disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the SMS reception control method as described in the first aspect above.

[0069] Based on common knowledge in the field, the above-mentioned preferred conditions can be combined arbitrarily to obtain various preferred embodiments of this disclosure.

[0070] The positive and progressive effects of this disclosure are as follows:

[0071] In this disclosure, a daemon is deployed for the SMS receiving program to build a two-way monitoring and wake-up mechanism. A background process is set to send heartbeat requests periodically to monitor the survival of the SMS receiving program. At the same time, a strategy of retrying upload failures and resuming interrupted uploads is adopted. This solves the problems of instability and service interruption caused by system killing or its own abnormality, ensuring that the SMS receiving program can run stably and will not miss SMS messages. It also enables rapid detection and notification of service abnormalities without manual monitoring, timely detection and resolution of abnormal situations, and significantly improves the continuity, reliability and maintainability of SMS receiving and uploading services. Attached Figure Description

[0072] Figure 1 A flowchart of the control method for receiving text messages provided in Embodiment 1 of this disclosure;

[0073] Figure 2 This is an interface diagram of the SMS daemon program in the SMS receiving control method provided in Embodiment 1 of this disclosure;

[0074] Figure 3 This is an interface diagram of the SMS receiving program in the SMS receiving control method provided in Embodiment 1 of this disclosure;

[0075] Figure 4A flowchart of step S101 in the SMS receiving control method provided in Embodiment 2 of this disclosure;

[0076] Figure 5 This is a schematic diagram of the control system for receiving text messages provided in Embodiment 4 of this disclosure;

[0077] Figure 6 A schematic diagram of the control system for receiving text messages provided in Embodiment 5 of this disclosure;

[0078] Figure 7 This is a schematic diagram of the structure of the electronic device provided in Embodiment 6 of this disclosure. Detailed Implementation

[0079] The present disclosure is further illustrated below by way of embodiments, but the present disclosure is not limited to the scope of the embodiments described herein.

[0080] The prefixes such as "first" and "second" used in this disclosure are merely for distinguishing different descriptive objects and do not limit the position, order, priority, quantity, or content of the described objects. The use of ordinal numbers and other prefixes used to distinguish descriptive objects in this disclosure does not constitute a limitation on the described objects. The description of the described objects is given in the claims or the context of the embodiments, and should not be construed as an unnecessary limitation. Furthermore, in the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0081] Example 1

[0082] The present disclosure provides a method for controlling SMS reception, which is applied to a smart terminal. The native operating system of the smart terminal is equipped with several SMS receiving programs and an SMS guardian program that is matched with the SMS receiving programs.

[0083] like Figure 1 As shown, the control method in this embodiment includes:

[0084] S101. Use the SMS guardian program to scan the first actual status of the SMS receiving program during the first monitoring period.

[0085] The SMS daemon monitors the target SMS receiving application's liveness by continuously scanning the list of currently running processes in the system, running a persistent background process. It obtains a list of all active processes by calling Android system services. Each process entry in the list is then iterated through, and its corresponding class name is precisely compared with the preset core service component class names of the SMS receiving application to determine the actual status of the SMS daemon.

[0086] S102. In response to the first actual state characterization that the SMS receiving program is in a non-live state, the SMS daemon generates a first wake-up command to wake up the SMS receiving program.

[0087] When the SMS daemon determines that the SMS receiving program is not in a live state, the entire system immediately switches from monitoring mode to emergency wake-up. At this time, the SMS daemon generates a wake-up command to efficiently and reliably wake up the SMS receiving program, ensuring that it can consistently and continuously maintain the ability to receive SMS messages normally.

[0088] in, Figure 2 This embodiment shows the interface diagram of the SMS guardian program. Figure 3 The screenshot shows the interface of the SMS receiving program in this example.

[0089] This solution employs an SMS daemon to continuously monitor the status of the SMS application. When the application is detected to be inactive, an automatic wake-up command is immediately generated and executed. This overcomes the problems of unstable program operation, easy program termination by mobile phone applications, and SMS loss due to abnormal program termination. It significantly improves the continuity, reliability, and maintainability of SMS receiving and uploading services, ensuring the integrity of business data and the continuity of business operations.

[0090] Example 2

[0091] The file generation method in this embodiment is a further improvement on embodiment 1, specifically:

[0092] In a feasible solution, such as Figure 4 As shown, step S101 includes:

[0093] S1011. Obtain the running status of a preset number of running applications;

[0094] The running status includes the associated information of the SMS receiving program in the application;

[0095] The SMS daemon actively retrieves a list of all active processes in the system by calling the Android system's underlying ActivityManager service, specifically by executing the getRunningServices(50) method. The parameter 50 in parentheses is a carefully considered upper limit value designed to ensure coverage of all possible active processes in the background, thus providing a complete data foundation for status determination.

[0096] S1012. In response to the information being a preset status information, determine that the SMS receiving program is in a live state; otherwise, determine that the SMS receiving program is in a non-live state.

[0097] By iterating through each process entry in the list and precisely comparing its corresponding class name with the preset core service component class names of the SMS receiving program, the loop is broken if the target class name is matched in multiple scans within the monitoring period, at which point the process is determined to be in a "live" state. Conversely, if no trace of the process is found in several consecutive probes, it is determined to be in a "non-live" state. This periodic state assessment provides accurate and timely input for subsequent decision-making.

[0098] This solution obtains the running status of a preset number of running applications to ensure that almost all running processes are captured, thus providing a complete data foundation for status judgment. Then, by iterating through each process entry in the list and accurately comparing its corresponding class name with the preset class name of the SMS receiving program, the actual status of the SMS receiving program can be determined, solving the problems of unstable program operation and easy program being killed by the phone.

[0099] In one feasible implementation, the control method further includes:

[0100] The SMS receiving program is used to scan the SMS guardian's second actual status during the second monitoring period;

[0101] In response to the second actual state indicating that the daemon is in a non-live state, the SMS receiving program generates a second wake-up command to wake up the SMS daemon.

[0102] This solution incorporates a two-way detection and fault recovery mechanism. The core of this control method lies in the fact that not only does the SMS daemon perform a real-time status scan and monitoring of the SMS receiving program during the first preset monitoring period, but the SMS receiving program also proactively performs the same scan and status assessment on the SMS daemon during the second monitoring period.

[0103] When either program detects that another program is "not alive" through this mechanism, it will immediately and automatically generate and issue a program startup command to forcibly wake up or restart the other program. Through this interdependent and mutually monitoring closed loop, the two programs achieve self-repair and continuous availability of the SMS receiving system, fundamentally eliminating SMS upload interruptions caused by the unexpected termination of a single program, and significantly improving the success rate of SMS uploads to the server.

[0104] In one feasible implementation, the control method further includes:

[0105] Keep the background process of the SMS receiving program running continuously;

[0106] The steps to keep the SMS receiving program running in the background include:

[0107] In response to starting a background process, the service startup command is invoked;

[0108] The timed location service is invoked based on the service startup command;

[0109] Based on the timed location service, the background process is restarted via timed broadcast to form a background process loop, thus keeping the background process of the SMS receiving program alive for a long time.

[0110] In this solution, the Android background process calls the `onStart Command` method upon startup. This `onStart Command` method then calls the `invokeTimer POI Service` method, which wakes up the background process via a periodic broadcast. This creates a loop where the background process starts by calling the `onStart Command` method, which in turn calls the `invokeTimer POI Service` method, periodically waking up the background process again. The result is that the background process runs continuously, keeping the SMS receiving application's background process alive.

[0111] And / or,

[0112] The SMS receiving program sends a heartbeat request to the server every first preset time interval;

[0113] In response to the server not detecting a request to send a heartbeat within a second preset time, receive the first abnormal alert message sent by the server;

[0114] This solution includes a heartbeat detection function in the SMS receiving program. It sends a heartbeat request to the server every minute, allowing the server to monitor phones that haven't sent heartbeats recently. This enables the server to send alert emails to relevant personnel to check for any abnormalities in the program's operation. This helps personnel quickly identify and respond to problems when they arise. Furthermore, the program records detailed log files during operation, allowing relevant personnel to quickly locate the problem by referring to these log files. This allows for rapid repair and restoration of operation, ensuring that the SMS receiving and uploading program to the server does not experience prolonged shutdowns.

[0115] If the heartbeat detection is normal, it only means that the program is running. There may be other abnormal situations that cause the SMS to be uploaded to the server abnormally, such as the phone's network connection being unavailable or certain permissions of the SMS receiving program not being enabled.

[0116] And / or,

[0117] The SMS receiving program runs on a native Android system with administrator account privileges; it has permissions to read and write files and read SMS messages.

[0118] In this solution, the program runs on the stock Android system. Since non-stock systems have various manufacturer-customized features, and our program needs to run continuously within the system, non-stock systems will consider it malware and kill the process after a period of time. By using the stock Android system of a Nexus phone, after obtaining super administrator privileges and granting the SMS receiving program read / write files and read SMS messages, if the SMS content is read, it is uploaded to the server. If not, it means that all SMS messages received on the phone have been successfully uploaded to the server, and the program can sleep for a period before continuing execution. This reduces the number of I / O operations (the number of read / write operations in a computer), reduces the program's runtime load, and ensures stable operation.

[0119] Example 3

[0120] In one feasible solution, the control method for receiving SMS messages also includes:

[0121] SMS data uploaded to the server is stored in the server's preset storage space;

[0122] And / or,

[0123] In response to an anomaly in the total number of SMS data acquired by the server within a third preset time period, a second anomaly alert message is generated.

[0124] This solution involves receiving SMS messages on a mobile device and uploading them to a server. Besides heartbeat detection to determine the SMS receiving program's viability, it also needs to monitor the volume of uploaded SMS messages. We store the SMS data uploaded to the server and then start a task that continuously scans for SMS volume. If a significant anomaly is detected in the SMS volume of a particular phone, an email notification is sent to relevant personnel to investigate the cause, resolve the issue, and restore normal upload speeds.

[0125] In this solution, to comprehensively improve the reliability and maintainability of the SMS receiving service, a process self-wake-up mechanism based on Android background services is designed. When the service starts, the `onStart Command` method is called to trigger the `invoke TimerPOI Service` timed location service. This method periodically wakes up the background process via timed broadcasts, thus forming a stable process self-recovery loop and ensuring the persistent operation of the SMS receiving program's background process. Based on this, a heartbeat detection mechanism is established. The SMS receiving program sends a heartbeat request to the server every minute. If the server does not detect a heartbeat within a preset time window, it immediately generates the first abnormal information and sends an email alert, enabling maintenance personnel to quickly detect abnormal states such as device offline or program freeze.

[0126] This solution also stores all SMS data uploaded to the server. Simultaneously, the server continuously scans, and when a significant anomaly is detected in the number of SMS messages sent to a device within a specific time window, a second anomaly message is automatically generated and relevant personnel are notified. This allows for accurate identification of service function failures caused by network fluctuations, permission changes, etc. Through these methods, this solution significantly improves the continuity and data reliability of the SMS receiving service.

[0127] In one feasible solution, the control method for receiving SMS messages also includes:

[0128] In response to a failed SMS upload, continuously retry the SMS upload operation until it is successfully uploaded;

[0129] In this solution, each SMS message uploaded to the server has a unique identifier: the smsID (SMS ID), which is the ID stored on the mobile phone. This ID increments as new SMS messages are received. The program stores the smsID field, allowing us to track which record the SMS upload process is currently running on. If the program reads a new SMS message but fails to upload it to the server, it will continuously retry. If the upload fails, the process will be blocked at that record. Alternatively, if the program terminates due to an exception, it will record the smsID at the time of termination, allowing it to resume execution from that ID upon recovery. This ensures that no SMS messages are missed during upload.

[0130] Example 4

[0131] This embodiment provides a control system for receiving text messages, applied to a smart terminal. The native operating system of the smart terminal is equipped with several text message receiving programs and a text message guardian program that is matched with the text message receiving programs.

[0132] like Figure 5 As shown, the control system for receiving text messages includes:

[0133] The first state acquisition module 1 is used to scan the actual state of the SMS receiving program during the first monitoring period using the SMS guardian program.

[0134] The first program wake-up module 2 is used to respond to the actual state indicating that the SMS receiving program is in a non-live state, and to generate a wake-up command using the SMS daemon to wake up the SMS receiving program.

[0135] This solution employs an SMS daemon to continuously monitor the status of the SMS application. When the application is detected to be inactive, an automatic wake-up command is immediately generated and executed. This overcomes the problems of unstable program operation, easy program termination by mobile phone applications, and SMS loss due to abnormal program termination. It significantly improves the continuity, reliability, and maintainability of SMS receiving and uploading services, ensuring the integrity of business data and the continuity of business operations.

[0136] For the system embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this disclosure according to actual needs.

[0137] Example 5

[0138] like Figure 6 As shown, the SMS receiving control system in this embodiment is a further improvement on embodiment 6, specifically:

[0139] The SMS receiving control system in this embodiment also includes:

[0140] The second state acquisition module 3 is used to scan the second actual state of the SMS guardian during the second monitoring period using the SMS receiving program.

[0141] The second program wake-up module 4 is used to respond to the second actual state characterization that the guardian program is in an inactive state, and to generate a second wake-up command using the SMS receiving program to wake up the SMS guardian program.

[0142] Optionally, the first state acquisition module includes:

[0143] The status acquisition unit 11 is used to acquire the running status of a preset number of running applications;

[0144] The running status includes the associated information of the SMS receiving program in the application;

[0145] The status judgment unit 12 is used to determine that the SMS receiving program is alive in response to the preset status information; otherwise, it determines that the SMS receiving program is not alive.

[0146] Optionally, the control system also includes:

[0147] Control module 5 is used to keep the background process of the SMS receiving program running continuously.

[0148] And / or,

[0149] The request sending module 6 is used to send a heartbeat request to the server every first preset time interval using the SMS receiving program;

[0150] The first anomaly alarm module 7 is used to receive the first anomaly reminder information sent by the server in response to the server not detecting a request to send a heartbeat within a second preset time.

[0151] And / or,

[0152] SMS data uploaded to the server is stored in the server's preset storage space;

[0153] And / or,

[0154] The second anomaly alarm module 8 is used to generate a second anomaly reminder message in response to an anomaly in SMS data obtained by the server within a third preset time.

[0155] Optionally, the control module 5 includes:

[0156] Background process startup response unit 51 is used to respond to the startup of a background process by calling the service startup command;

[0157] The timed location service invocation unit 52 is used to invoke the timed location service based on the service startup command;

[0158] The timed broadcast process restart unit 53 is used to restart the background process by timed broadcast according to the timed location service, so as to form a background process loop and keep the background process of the SMS receiving program alive.

[0159] Optionally, the SMS messages uploaded to the server have a unique identifier;

[0160] And / or,

[0161] The control system also includes:

[0162] SMS upload retry module 9 is used to continuously retry the SMS upload operation in response to SMS upload failure until the upload is successful;

[0163] And / or,

[0164] The system permission configuration module 10 is used to ensure that the environment in which the SMS receiving program runs is the native Android system after obtaining administrator account permissions; among which, the SMS receiving program has the permissions to read and write files and read SMS messages.

[0165] This solution addresses issues such as instability and service interruption caused by system crashes or malfunctions by deploying a daemon to the SMS receiving program and setting a background process to periodically send heartbeat requests to monitor the program's viability. It also employs strategies for retrying upload failures and resuming interrupted uploads. This eliminates the risk of SMS data loss caused by system crashes or program malfunctions, enables rapid detection and notification of service anomalies, significantly improves the continuity, reliability, and maintainability of SMS receiving and uploading services, and ensures the integrity of business data and the continuity of business operations.

[0166] For the system embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this disclosure according to actual needs.

[0167] Example 6

[0168] Figure 7 This is a schematic diagram of the structure of an electronic device according to an example embodiment of the present disclosure. The electronic device includes a memory, a processor, and a computer program stored in the memory and used to run on the processor. When the processor executes the computer program, it implements the request processing method described in any of the above embodiments. Figure 7 The electronic device 90 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0169] like Figure 7 As shown, the electronic device 90 can be manifested as a general-purpose computing device, such as a server device. The components of the electronic device 90 may include, but are not limited to: at least one processor 91, at least one memory 92, and a bus 93 connecting different system components (including memory 92 and processor 91).

[0170] Bus 93 includes a data bus, an address bus, and a control bus.

[0171] The memory 92 may include volatile memory, such as random access memory (RAM) 921 and / or cache memory 922, and may further include read-only memory (ROM) 923.

[0172] The memory 92 may also include a program tool 925 (or utility) having a set (at least one) program module 924, such program module 924 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0173] The processor 91 executes various functional applications and data processing by running computer programs stored in the memory 92, such as the SMS receiving control method provided in any of the above embodiments.

[0174] Electronic device 90 can also communicate with one or more external devices 94 (e.g., keyboard, pointing device, etc.). This communication can be performed through input / output (I / O) interface 95. Furthermore, electronic device 90 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public network, such as the Internet) via network adapter 96. As shown, network adapter 96 communicates with other modules of electronic device 90 via bus 93. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 90, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems.

[0175] It should be noted that although several units / modules or sub-units / modules of the electronic device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0176] Example 7

[0177] This disclosure also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the SMS receiving control method provided in any of the above embodiments.

[0178] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.

[0179] Example 8

[0180] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the SMS reception control method described in any of the above embodiments.

[0181] The program code for executing the computer program product of this disclosure can be written in any combination of one or more programming languages, and the program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.

[0182] While specific embodiments of this disclosure have been described above, those skilled in the art should understand that these are merely illustrative examples, and the scope of protection of this disclosure is defined by the appended claims. Those skilled in the art can make various changes or modifications to these embodiments without departing from the principles and essence of this disclosure, but all such changes and modifications fall within the scope of protection of this disclosure.

Claims

1. A method for controlling SMS reception, characterized in that, The control method is applied to a smart terminal, in which a number of SMS receiving programs are set in the native operating system of the smart terminal, and an SMS guardian program is set to match the SMS receiving programs. The control method includes: The SMS guardian program is used to scan the first actual state of the SMS receiving program during the first monitoring period. In response to the first actual state indicating that the SMS receiving program is in a non-live state, the SMS daemon generates a first wake-up command to wake up the SMS receiving program.

2. The SMS receiving control method as described in claim 1, characterized in that, The control method further includes: The SMS receiving program is used to scan the second actual state of the SMS guardian program during the second monitoring period; In response to the second actual state indicating that the daemon is in a non-live state, the SMS receiving program generates a second wake-up command to wake up the SMS daemon.

3. The SMS receiving control method as described in claim 1, characterized in that, The step of using the SMS guardian program to scan the actual status of the SMS receiving program during the first monitoring period includes: Get the running status of a preset number of running applications; The running status includes the associated information of the SMS receiving program in the application; If the information is a preset status information, it is determined that the SMS receiving program is in a live state; otherwise, it is determined that the SMS receiving program is in a non-live state.

4. The control method for receiving SMS messages as described in claim 1, characterized in that, The control method further includes: Keep the background process of the SMS receiving program running continuously; And / or, The SMS receiving program sends a heartbeat request to the server every first preset time interval; In response to the server not detecting the request to send a heartbeat within a second preset time, the server receives a first abnormality alert message. And / or, The SMS data uploaded to the server is stored in the server's preset storage space; And / or, In response to an anomaly in the total number of SMS data acquired by the server within a third preset time period, a second anomaly alert message is generated.

5. The SMS receiving control method as described in claim 4, characterized in that, The steps for keeping the background process of the SMS receiving program running continuously include: In response to starting a background process, the service startup command is invoked; The timed location service is invoked based on the service startup command. According to the timed location service, the background process is restarted by timed broadcast to form the background process loop, so that the background process of the SMS receiving program remains active.

6. The control method for receiving SMS messages as described in any one of claims 1-5, characterized in that, Each SMS message uploaded to the server has a unique identifier; And / or, The control method further includes: In response to the failure of the SMS upload, the upload operation of the SMS will be continuously retried until the upload is successful; And / or, The SMS receiving program runs in a native Android system after obtaining administrator account privileges; the SMS receiving program has permissions to read and write files and read SMS messages.

7. A control system for receiving text messages, characterized in that, The control system is applied to a smart terminal, and the native operating system of the smart terminal is equipped with several SMS receiving programs and an SMS protection program that is matched with the SMS receiving programs. The control system includes: The first state acquisition module is used to scan the actual state of the SMS receiving program during the first monitoring period using the SMS guardian program. The first program wake-up module is used to generate a wake-up command using the SMS guardian program to wake up the SMS receiving program in response to the actual state indicating that the SMS receiving program is in an inactive state.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and for running on the processor, characterized in that, When the processor executes the computer program, it implements the control method for receiving SMS messages as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the control method for receiving SMS messages as described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the control method for receiving SMS messages as described in any one of claims 1 to 6.

Images