CN108966159B - Short message withdrawing method, system, computer equipment and storage medium - Google Patents
Short message withdrawing method, system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN108966159B CN108966159B CN201811023099.1A CN201811023099A CN108966159B CN 108966159 B CN108966159 B CN 108966159B CN 201811023099 A CN201811023099 A CN 201811023099A CN 108966159 B CN108966159 B CN 108966159B
- Authority
- CN
- China
- Prior art keywords
- short message
- server
- identifier
- withdrawal
- platform server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application relates to cloud services and provides a short message withdrawing method, a system, computer equipment and a storage medium. The method comprises the following steps: the platform server receives a short message sending instruction sent by the sender terminal, generates a task identifier corresponding to the short message according to the short message sending instruction, and returns the task identifier to the sender terminal. And the platform server writes the task identifier into a short message sending queue and starts a sending process. The platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries a task identifier, and the task identifier is searched in a short message sending queue. And when the task identifier exists in the short message sending queue, the platform server finishes the sending process of the task identifier, deletes the task identifier from the short message sending queue and returns a withdrawal success prompt to the sender terminal. By adopting the method, the short message can be withdrawn, and the waste of short message resources is reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a system, a computer device, and a storage medium for withdrawing a short message.
Background
Short message: short Message Service, SMS for Short, is a text or digital Message that a user directly sends or receives through a mobile phone or other telecommunication terminals, and the number of characters that the user can receive and send a Short Message at a time is 160 english or digital characters, or 70 chinese characters. Short messages are now widely used as one of the important means of communication with the spread of these devices. At present, most devices cannot withdraw the short message after sending the short message, and if the short message has errors or other conditions, the short message needs to be sent again, which wastes a large amount of short message resources.
Disclosure of Invention
In view of the foregoing, there is a need to provide a short message recall method, a system, a computer device and a storage medium that can reduce the waste of short message resources.
A short message withdrawal method comprises the following steps:
the platform server receives a short message sending instruction sent by a sender terminal, generates a task identifier corresponding to a short message according to the short message sending instruction, and returns the task identifier to the sender terminal;
the platform server writes the task identifier into a short message sending queue and starts a sending process;
the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries the task identifier, and the task identifier is searched in the short message sending queue;
and when the platform server finds the task identifier in the short message sending queue, the platform server finishes the sending process of the task identifier, deletes the task identifier from the short message sending queue, and returns a withdrawal success prompt to the sender terminal.
In one embodiment, after the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, where the short message withdrawal instruction carries a task identifier, and searches for the task identifier in the short message sending queue, the method further includes:
when the task identifier is not found in the short message sending queue, the platform server sends a short message withdrawing request to an operator server, wherein the short message withdrawing request carries a short message identifier and a platform identifier;
the operator server receives a short message recall request and verifies the platform identification according to the short message recall request;
when the operator server verifies that the platform identification passes, detecting whether the short message corresponding to the short message identification is sent to a receiver terminal according to the short message withdrawal request;
and the operator server intercepts the short message when the short message is not sent to the receiver terminal, and returns a withdrawal success prompt to the sender terminal through the platform server.
In one embodiment, after detecting whether the short message has been sent to the receiver terminal according to the short message recall request, the method further includes:
the operator server sends a short message deleting request to a manufacturer server when the short message is sent to the receiver terminal, wherein the short message deleting request carries a receiver identifier, a short message identifier and an operator identifier;
the manufacturer server verifies the operator identification according to the short message deleting request, and when the operator identification passes the verification, a corresponding receiver terminal is searched according to the receiver identification;
when the manufacturer server finds the receiver terminal, calling a target kernel interface to send a short message deleting instruction to the receiver terminal, so that the receiver terminal deletes the short message corresponding to the short message identification according to the short message deleting instruction;
and the manufacturer server returns a withdrawal success prompt to the sender terminal through the operator server and the platform server.
In one embodiment, before the operator server sends the short message deletion request to the vendor server, the method further includes:
and the operator server receives the equipment identifier sent by the platform server and determines the manufacturer server according to the equipment identifier.
In one embodiment, before the operator server receives the device identifier sent by the platform server and determines the vendor server according to the device identifier, the method further includes:
the platform server sends a query request to a manufacturer server cluster corresponding to different operating systems, wherein the query request carries a receiver identifier;
the manufacturer server cluster inquires an equipment identifier corresponding to a receiver identifier according to the inquiry request, and when the equipment identifier can be found in the manufacturer server cluster, the equipment identifier is sent to a platform server;
and the platform server receives the equipment identification and correspondingly stores the equipment identification and the receiver identification.
In one embodiment, after the platform server writes the task identifier into a short message sending queue and starts a sending process, the method further includes:
the platform server sends the short message to the operator server by using the sending process according to the short message sending queue;
and the operator server receives the short message and sends the short message to a receiver terminal.
In one embodiment, the method further comprises:
when the short message is withdrawn, the platform server generates a withdrawal log according to the task identifier and stores the withdrawal log;
and the platform server receives a log withdrawal inquiry command sent by the sender terminal, and returns the log withdrawal to the sender terminal according to the log withdrawal inquiry command, so that the sender terminal displays the log withdrawal.
A short message recall system, the system comprising:
the platform server is used for receiving a short message sending instruction sent by a sender terminal, generating a task identifier corresponding to a short message according to the short message sending instruction, and returning the task identifier to the sender terminal;
the platform server is used for writing the task identifier into a short message sending queue and starting a sending process;
the platform server is used for receiving a short message withdrawal instruction sent by a sender terminal within a preset time period, wherein the short message withdrawal instruction carries the task identifier, and the task identifier is searched in the short message sending queue;
and the platform server is used for finishing the sending process of the task identifier when the task identifier is found in the short message sending queue, deleting the task identifier from the short message sending queue, and returning a withdrawal success prompt to the sender terminal.
A computer device comprising a memory storing a computer program and a processor implementing the steps of any of the methods described above when the processor executes the computer program.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
the platform server receives a short message sending instruction sent by a sender terminal, generates a task identifier corresponding to a short message according to the short message sending instruction, and returns the task identifier to the sender terminal;
the platform server writes the task identifier into a short message sending queue and starts a sending process;
the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries the task identifier, and the task identifier is searched in the short message sending queue;
and when the task identifier exists in the short message sending queue, the platform server finishes the sending process of the task identifier, deletes the task identifier from the short message sending queue, and returns a withdrawal success prompt to the sender terminal.
The short message withdrawing method, the system, the computer equipment and the storage medium receive a short message sending instruction sent by a sender terminal through the platform server, generate a task identifier corresponding to the short message according to the short message sending instruction, and return the task identifier to the sender terminal; the platform server writes the task identifier into a short message sending queue and starts a sending process; the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries the task identifier, and the task identifier is searched in the short message sending queue; when the task identifier exists in the short message sending queue, the platform server finishes the sending process of the task identifier, deletes the task identifier from the short message sending queue, and returns a withdrawal success prompt to the sender terminal.
Drawings
Fig. 1 is an application scenario diagram of a short message revocation method in an embodiment;
fig. 2 is a schematic flow chart illustrating a method for withdrawing a short message according to an embodiment;
FIG. 3 is a flow chart illustrating an embodiment of an operator server for message recall;
FIG. 4 is a schematic flow chart illustrating an embodiment of a vendor server withdrawing a short message;
FIG. 5 is a flow diagram that illustrates the storage of an identifier by a platform server in one embodiment;
FIG. 6 is a flow chart illustrating SMS transmission according to an embodiment;
fig. 7 is a schematic flow chart illustrating generation of a short message revocation log according to an embodiment;
FIG. 8 is a timing diagram illustrating the withdrawal of short messages in an exemplary embodiment;
FIG. 9 is a block diagram of a SMS message recall system in accordance with an embodiment;
FIG. 10 is a diagram showing an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The short message withdrawing method provided by the application can be applied to the application environment shown in fig. 1. Wherein the sender terminal 102 communicates with the platform server 104 through a network. The platform server 104 receives a short message sending instruction sent by the sender terminal 102, generates a task identifier corresponding to the short message according to the short message sending instruction, and returns the task identifier to the sender terminal 102; the platform server 104 writes the task identifier into a short message sending queue and starts a sending process; the platform server 104 receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries a task identifier, and the task identifier is searched in a short message sending queue; when the platform server 104 finds the task identifier in the short message sending queue, the sending process of the task identifier is ended, the task identifier is deleted from the short message sending queue, and a withdrawal success prompt is returned to the sender terminal 102. The sender terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the platform server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, as shown in fig. 2, a method for withdrawing a short message is provided, which is described by taking the application of the method to the platform server in fig. 1 as an example, and includes the following steps:
s202, the platform server receives a short message sending instruction sent by the sender terminal, generates a task identifier corresponding to the short message according to the short message sending instruction, and returns the task identifier to the sender terminal.
The task identification is used for identifying sending tasks of the short messages, each short message has a corresponding sending task, and each sending task has a corresponding task identification. The platform server refers to a server of a message cloud platform, and the message cloud platform is used for sending short messages.
Specifically, a sender terminal sends a short message through a message cloud platform, a platform server receives a short message sending instruction, obtains the short message to be sent according to the sending instruction and generates a task identifier corresponding to the short message, then the task identifier is returned to the sender terminal, and the sender terminal receives the task identifier and displays the task identifier in the message cloud platform.
S204, the platform server writes the task identifier into a short message sending queue and starts a sending process.
Specifically, the platform server writes the generated task identifier into a short message sending queue and starts a sending process of the short message to wait for sending.
S206, the platform server receives a short message withdrawal instruction sent by the sender terminal within a preset time period, the short message withdrawal instruction carries a task identifier, and the task identifier is searched in a short message sending queue.
Specifically, within a preset time period, for example within 2 minutes, when a user finds that a short message has an error or other situations requiring the withdrawal of the short message, the sending party terminal receives a withdrawal instruction sent by the user through the message cloud platform, the withdrawal instruction carries a task identifier selected by the user, that is, the short message corresponding to the task identifier is the short message requiring the withdrawal, then the sending party terminal sends the short message withdrawal instruction to the platform server, the platform server receives the short message withdrawal instruction, the short message withdrawal instruction carries the task identifier corresponding to the short message requiring the withdrawal, and the platform server searches the task identifier in the short message sending queue according to the short message withdrawal instruction. And when the task identifier can be found, the short message is not sent to the operator server. And when the task identifier cannot be found, the short message is sent to the operator server.
And S208, when the platform server finds the task identifier in the short message sending queue, ending the sending process of the task identifier, deleting the task identifier from the short message sending queue, and returning a withdrawal success prompt to the sender terminal.
Specifically, when the platform server finds the task identifier in the short message sending queue, it indicates that the short message corresponding to the task identifier has not been sent to the operator server, at this time, the platform server ends the sending process of the short message corresponding to the task identifier, deletes the task identifier in the short message sending queue of the platform server, and then the platform server returns a withdrawal success prompt to the sender terminal.
In the short message withdrawing method, the short messages waiting to be sent in the short message sending queue in the platform server are withdrawn through the technical characteristics, so that the waste of short message resources can be reduced, the loss of customers and the problems caused by wrong short messages can be reduced, and the user experience is improved.
In an embodiment, as shown in fig. 3, after step S206, that is, after the platform server receives a short message withdrawal instruction sent by the sender terminal within a preset time period, where the short message withdrawal instruction carries a task identifier, and after the task identifier is searched in the short message sending queue, the method further includes the steps of:
s302, when the task identifier is not found in the short message sending queue, the platform server sends a short message withdrawal request to the operator server, wherein the short message withdrawal request carries the short message identifier and the platform identifier.
The short message identification is used for identifying a sender of the short message, and can be a platform account of the sender or a mobile phone number of the sender, the platform identification is used for identifying a sending platform of the short message, and the operator server refers to a server of a provider providing network service, such as a china unicom server, a china telecommunication server, a china mobile server, and the like.
Specifically, when the platform server does not find the task identifier in the short message sending queue, it indicates that the platform server has sent the short message to the operator server. At this time, the platform server sends a short message withdrawal request to the operator server, wherein the short message withdrawal request carries the short message identifier and the platform identifier.
S304, the operator server receives the short message recall request and verifies the platform identification according to the short message recall request.
Specifically, when the operator server receives the short message recall request, the operator server first performs the short message recall according to the verification of whether the platform identifier has the authority, which may be that the platform and the operator subscribe the platform identifier in advance. And the operation server stores the agreed platform identification into the platform identification data table, and matches the received platform identification with the platform identification stored in the operation server when receiving the withdrawal request.
S306, when the identification of the platform passes through the verification of the operator server, the operator server detects whether the short message corresponding to the short message identification is sent to the terminal of the receiving party according to the short message withdrawing request.
Specifically, when the operator server can match the platform identifier from all the stored platform identifiers, that is, when the same platform identifier is stored in the operation server, the platform identifier passes verification, at this time, it is detected whether the short message corresponding to the short message identifier has been sent to the receiver terminal according to the short message withdrawal request, when the platform identifier stored in the operation server is different from the received platform identifier, the platform identifier fails verification, and the operation server returns a prompt without withdrawal permission to the platform server.
And S308, the operator server intercepts the short message when the short message is not sent to the receiver terminal, and returns a withdrawal success prompt to the sender terminal through the platform server.
Specifically, when detecting that the short message is not sent to the receiving party terminal, the operation server intercepts the short message being sent, sends a short message success prompt for intercepting the short message identifier to the platform server after the interception is successful, and the platform server returns a withdrawal success prompt to the sending party terminal.
In the embodiment, through the technical characteristics, when the platform server sends the short message to the operator server, the platform server sends a withdrawal request to the operator server, when the right verification passes, the operator server intercepts the short message which is not sent to the receiver terminal, an interception success prompt is returned to the platform server after the interception is successful, and the platform server returns a withdrawal success prompt to the sender terminal after receiving the prompt.
In one embodiment, as shown in fig. 4, after step S306, that is, after detecting whether the short message has been sent to the receiver terminal according to the short message withdrawal request, the method further includes the steps of:
s402, when the short message is sent to the terminal of the receiving party, the operator server sends a short message deleting request to the manufacturer server, wherein the short message deleting request carries the identification of the receiving party, the identification of the short message and the identification of the operator.
The receiving party identification user identification receiving party can be a mobile phone number of the receiving party or an account number of a message cloud platform of the receiving party. The carrier identity is used to identify the carrier. The manufacturer server refers to a manufacturer of the terminal device of the receiving party, for example, if the terminal of the receiving party is a mobile phone, the manufacturer server is a server.
Specifically, when the operator server detects that the short message to be withdrawn is sent to the terminal of the receiving party, at the moment, the operator server sends a short message deleting request to all the manufacturer servers, wherein the short message deleting request carries the identification of the receiving party, the identification of the short message and the identification of the operator.
S404, the manufacturer server verifies the operator identification according to the short message deleting request, and when the operator identification passes the verification, the corresponding receiver terminal is searched according to the receiver identification.
Specifically, when the manufacturer server receives the short message deletion request, the operator identifier is verified, that is, the operator and the manufacturer agree the operator identifier in advance, the manufacturer server stores the agreed operator identifier, when the operator identifier is received, the operator identifier is matched with the stored operator identifier, when the same operator identifier exists, the operator identifier passes verification, then the manufacturer server searches a corresponding receiver terminal according to the receiver identifier, wherein the receiver identifier corresponds to the receiver terminal one to one, for example, one mobile phone number corresponds to one mobile phone, and the manufacturer server can search whether the mobile phone number uses the mobile phone equipment produced by the manufacturer according to the mobile phone number. And when the manufacturer server does not find the receiver terminal corresponding to the receiver identifier, the short message deleting request is not processed.
S406, the manufacturer server can call the target kernel interface to send a short message deleting instruction to the receiver terminal when finding the receiver terminal, so that the receiver terminal deletes the short message corresponding to the short message identifier according to the short message deleting instruction.
And S408, the manufacturer server returns a withdrawal success prompt to the sender terminal through the operator server and the platform server.
Specifically, when the manufacturer server can find the receiver terminal, it indicates that the receiver terminal is a terminal device produced by the manufacturer. At the moment, the manufacturer server calls a specified kernel interface to send a short message deleting instruction to the receiver terminal, when the receiver terminal equipment receives the short message deleting instruction through the specified kernel interface, the short message is deleted in the receiver terminal, then the manufacturer server returns a deleting success instruction to the operator server, the operator server returns a deleting success prompt to the platform server, and finally the platform server returns a withdrawing success prompt to the sender terminal.
In the embodiment, through the technical characteristics, when the short message needing to be withdrawn is sent to the receiving party terminal, the receiving party terminal corresponding to the receiving party identifier is found through the manufacturer server, so that the receiving party terminal deletes the short message in the receiving party terminal through the kernel interface, the short message sent to the receiving party terminal can be withdrawn, the loss of a customer and the problem caused by error information are further reduced, and the fault tolerance rate of the customer is improved.
In one embodiment, before step S402, that is, before the operator server sends the short message deletion request to the vendor server, the method further includes the steps of:
and the operator server receives the equipment identifier sent by the platform server and determines the manufacturer server according to the equipment identifier.
The device identifier is used for identifying the terminal device of the receiving party, is a unique identification code of the device, and is given to the device identifier when the manufacturer produces the device. For example, the device Identity of the Mobile device may be an IMEI (International Mobile Equipment Identity).
Specifically, the platform server may pre-store a device identifier of the receiver terminal, and when the operator server sends the short message deletion request to the vendor server, the operator server may obtain the device identifier of the receiver terminal from the platform server, and then determine the vendor server according to the device identifier. Therefore, when the operator server sends the short message deleting request to the manufacturer server, the operator server can send the short message deleting request to the determined manufacturer server without sending the request to all the manufacturer servers, the short message withdrawing efficiency is improved, and the server resources are saved.
In one embodiment, as shown in fig. 5, before the operator server receives the device identifier sent by the platform server and determines the vendor server according to the device identifier, the method further includes the steps of:
s502, the platform server sends a query request to the manufacturer server clusters corresponding to different operating systems, wherein the query request carries the identification of a receiver.
The operating system is a computer program for managing and controlling computer hardware and software resources, is the most basic system software directly running on a bare computer, and any other software can run only under the support of the operating system, wherein the operating system comprises an android system, an apple system, a blackberry system and the like.
Specifically, when a sender sends a short message through a message cloud platform, a receiver identifier needs to be set on the message cloud platform in advance, when a platform server obtains the receiver identifier, the platform server can send a query request to a manufacturer server cluster corresponding to different operating systems, for example, the platform server can send the query request to a manufacturer server cluster corresponding to an android system, the manufacturer server cluster includes a Huacheng server, a millet server, a samsung server and the like, and the query request needs to query an equipment identifier corresponding to the receiver identifier.
S504, the manufacturer server cluster inquires the equipment identification corresponding to the receiver identification according to the inquiry request, and when the equipment identification can be found in the manufacturer server cluster, the equipment identification is sent to the platform server.
Specifically, when the manufacturer server cluster receives the query request, the equipment identifier corresponding to the receiver identifier is queried, and when the equipment identifier can be found in the manufacturer server cluster, the found equipment identifier is sent to the platform server.
S506, the platform server receives the equipment identification and correspondingly stores the equipment identification and the receiver identification.
Specifically, when the platform server receives the device identifier, the device identifier and the receiver identifier are correspondingly stored in the database.
In the embodiment, by the technical characteristics, the device identifier corresponding to the receiver identifier can be obtained from the manufacturer server in advance, and the device identifier is stored in the platform server, and when the operator server needs to use the device identifier, the platform server sends the device identifier to the operator server, so that the short message withdrawal efficiency is further improved.
In an embodiment, as shown in fig. 6, after step S204, that is, after the platform server writes the task identifier into the short message sending queue and starts the sending process, the method further includes the steps of:
s602, the platform server sends the short message to the operator server by using the sending process according to the short message sending queue.
S604, the operator server receives the short message and sends the short message to the terminal of the receiving party.
Specifically, the platform server uses a sending process to send the short messages of the task identifiers to the operator server in sequence according to the sequence of the task identifiers in the short message sending queue, the sent content further comprises the corresponding short message identifiers of the receiver terminal, the short message identifiers are received by the sender terminal through the message cloud platform, and the sender terminal sends the short message identifiers and the short messages to the platform server together. After the operator server receives the short message and the short message identification, the short message is sent to the receiver terminal according to the short message identification, and the short message is sent by the method.
In one embodiment, as shown in fig. 7, the method for withdrawing a short message further includes the steps of:
and S702, the platform server generates a withdrawal log according to the task identifier when the short message is withdrawn, and stores the withdrawal log.
Specifically, when the platform server withdraws the short message, a withdrawal log is generated according to the task identifier, and the withdrawal log comprises the short message identifier, the withdrawal time, the withdrawal place, whether the withdrawal is successful, and the like of the withdrawn short message. Wherein. The revocation location refers to a revocation at a platform server or a revocation at an operator server or a revocation from a recipient terminal. The platform server saves the withdrawn log in a pre-established log database.
And S704, the platform server receives a log withdrawal inquiry command sent by the sender terminal, and returns the withdrawn log to the sender terminal according to the log withdrawal inquiry command, so that the sender terminal displays the withdrawn log.
Specifically, the sender terminal sends a withdrawal query instruction to the server through the message cloud platform, the platform server reads a withdrawal log from the log database after receiving the instruction, the read withdrawal log is sent to the sender terminal, the withdrawal log is displayed through the message cloud platform when the sender terminal receives the withdrawal log, the sender can check the withdrawn short message through the displayed withdrawal log, and the withdrawn short message can be edited again and sent again.
In a specific embodiment, as shown in fig. 8, the platform server 804 receives a short message withdrawal instruction sent by the sender mobile phone 802, where the instruction carries a task ID, the platform server 804 searches for the task ID in a short message sending queue, and when the task ID is found, ends the sending process and deletes the task ID in the short message sending queue, and then returns a withdrawal success prompt to the receiver mobile phone. When the task ID is not found, the platform server 804 sends a withdrawal request to the operator server 806, where the withdrawal request carries a receiver mobile phone number and a message cloud platform identifier corresponding to the short message. The operator server 806 first verifies the message cloud platform identifier, and when the message cloud platform identifier passes the verification, detects whether the short message is sent to the mobile phone of the receiver according to the mobile phone number of the receiver. When the short message is not sent completely, the operator server 806 intercepts the short message being sent, and sends a prompt of successful interception to the platform server 804 after successful interception, and the platform server 804 notifies the sender mobile phone 802 that the withdrawal is successful. When the short message is sent completely, that is, the short message reaches the terminal of the receiving party, the operator server 806 determines the vendor server 808 corresponding to the mobile phone of the receiving party, and sends a short message deletion request to the vendor server 808, where the request carries the mobile phone number of the receiving party and the operator identifier. When the manufacturer server 808 receives the short message deleting request, the manufacturer server 808 verifies the operator identification, when the verification is passed, the manufacturer server 808 calls the appointed kernel interface to send a short message deleting instruction to the mobile phone of the receiving party, and when the mobile phone 810 of the receiving party receives the short message deleting instruction, the received short message is deleted, and a prompt of successful deletion is returned to the manufacturer server 808. After receiving the prompt of successful deletion, the vendor server 808 returns a prompt of successful revocation to the sender mobile phone through the operator server 806 and the platform server 804, and the sender can resend the message through the sender mobile phone 802.
It should be understood that although the various steps in the flow charts of fig. 2-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-7 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 9, there is provided a short message recall system 900, including: platform server 902, wherein:
the platform server 902 is configured to receive a short message sending instruction sent by the sender terminal, generate a task identifier corresponding to the short message according to the short message sending instruction, and return the task identifier to the sender terminal.
The platform server 902 is configured to write the task identifier into the short message sending queue and start a sending process.
The platform server 902 is configured to receive a short message withdrawal instruction sent by a sender terminal within a preset time period, where the short message withdrawal instruction carries a task identifier, and search the task identifier in a short message sending queue.
The platform server 902 is configured to, when finding the task identifier in the short message sending queue, end the sending process of the task identifier, delete the task identifier from the short message sending queue, and return a withdrawal success prompt to the sender terminal.
In the above embodiment, the identification platform server 902 generates a task identifier corresponding to the short message, the platform server 902 writes the task identifier into a short message sending queue and starts a sending process, the platform server 902 receives a short message withdrawal instruction sent by the sender terminal within a preset time period, the short message withdrawal instruction carries the task identifier, the task identifier is searched in the short message sending queue, when the platform server 902 searches the task identifier in the short message sending queue, the sending process of the task identifier is ended, the task identifier is deleted from the short message sending queue, and a withdrawal success prompt is returned to the sender terminal, so that the short message with problems can be withdrawn, and the waste of short message resources is reduced.
In one embodiment, the short message revocation systematization 900 further includes:
and the platform server 902 is configured to send a short message withdrawal request to the operator server when the task identifier is not found in the short message sending queue, where the short message withdrawal request carries the short message identifier and the platform identifier.
And the operator server is used for receiving the short message withdrawing request and verifying the platform identifier according to the short message withdrawing request.
The operator server is used for detecting whether the short message corresponding to the short message identification is sent to the receiver terminal according to the short message withdrawal request when the verification platform identification passes; and when the short message is not sent to the receiver terminal, the operator server intercepts the short message and returns a withdrawal success prompt to the sender terminal through the platform server 902.
In one embodiment, the short message recall system 900 further includes:
and the operator server is used for sending a short message deleting request to the manufacturer server when the short message is sent to the receiver terminal, wherein the short message deleting request carries the receiver identifier, the short message identifier and the operator identifier.
And the manufacturer server is used for verifying the operator identification according to the short message deleting request, and searching the corresponding receiver terminal according to the receiver identification when the operator identification passes verification.
The manufacturer server is used for calling the target kernel interface to send a short message deleting instruction to the receiving terminal when the receiving terminal is found, so that the receiving terminal deletes the short message corresponding to the short message identification according to the short message deleting instruction; and the manufacturer server returns a withdrawal success prompt to the sender terminal through the operator server and the platform server.
In one embodiment, the short message recall system 900 further includes: and the operator server is used for receiving the equipment identifier sent by the platform server and determining the manufacturer server according to the equipment identifier.
In one embodiment, the short message recall system 900 further includes:
the platform server is used for sending query requests to manufacturer server clusters corresponding to different operating systems, and the query requests carry receiver identifications;
the manufacturer server cluster is used for inquiring the equipment identifier corresponding to the receiver identifier according to the inquiry request, and sending the equipment identifier to the platform server when the equipment identifier can be found in the manufacturer server cluster;
and the platform server is used for receiving the equipment identifier and correspondingly storing the equipment identifier and the receiver identifier.
In one embodiment, the short message recall system 900 further includes:
the platform server is used for sending the short message to the operator server by using a sending process according to the short message sending queue; and the operator server receives the short message and sends the short message to the receiver terminal.
In one embodiment, the short message recall system 900 further includes:
the platform server is used for generating a withdrawal log according to the task identifier when the short message is withdrawn, and storing the withdrawal log;
and the platform server is used for receiving the log withdrawal inquiry command sent by the sender terminal and returning the withdrawn log to the sender terminal according to the log withdrawal inquiry command so as to enable the sender terminal to display the withdrawn log.
For specific limitations of the short message recall system, reference may be made to the above limitations on the short message recall method, which are not described herein again. All modules in the short message withdrawing system can be completely or partially realized through software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 10. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer equipment is used for storing the related data of the short messages. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to realize a short message withdrawal method.
Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory storing a computer program and a processor, the processor when executing the computer program implementing a platform server to perform the steps of: the platform server receives a short message sending instruction sent by a sender terminal, generates a task identifier corresponding to the short message according to the short message sending instruction, and returns the task identifier to the sender terminal; the platform server writes the task identifier into a short message sending queue and starts a sending process; the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries a task identifier, and the task identifier is searched in a short message sending queue; and when the platform server finds the task identifier in the short message sending queue, ending the sending process of the task identifier, deleting the task identifier from the short message sending queue, and returning a withdrawal success prompt to the sender terminal.
In one embodiment, the processor, when executing the computer program, further implements the platform server to perform the steps of: when the task identifier is not found in the short message sending queue, the platform server sends a short message withdrawal request to the operator server, wherein the short message withdrawal request carries the short message identifier and the platform identifier; when the processor executes the computer program, the processor also realizes the execution steps of the operator server: the operator server receives the short message recall request and verifies the platform identification according to the short message recall request; when the verification platform identification passes, the operator server detects whether the short message corresponding to the short message identification is sent to the receiver terminal according to the short message withdrawal request; and the operator server intercepts the short message when the short message is not sent to the receiver terminal, and returns a withdrawal success prompt to the sender terminal through the platform server.
In one embodiment, the processor, when executing the computer program, further implements the operator server to perform the steps of: the operator server sends a short message deleting request to the manufacturer server when the short message is sent to the receiver terminal, wherein the short message deleting request carries a receiver identifier, a short message identifier and an operator identifier; the processor, when executing the computer program, further implements the vendor server to perform the steps of: the manufacturer server verifies the operator identification according to the short message deletion request, and searches a corresponding receiver terminal according to the receiver identification when the operator identification passes verification; when the manufacturer server finds the receiver terminal, calling the target kernel interface to send a short message deleting instruction to the receiver terminal so that the receiver terminal deletes the short message corresponding to the short message identification according to the short message deleting instruction; and the manufacturer server returns a withdrawal success prompt to the sender terminal through the operator server and the platform server.
In one embodiment, the processor, when executing the computer program, further implements the operator service performing steps of: and the operator server receives the equipment identifier sent by the platform server and determines the manufacturer server according to the equipment identifier.
In one embodiment, the processor, when executing the computer program, further implements the platform server to perform the steps of: the platform server sends a query request to a manufacturer server cluster corresponding to different operating systems, wherein the query request carries a receiver identifier; the processor, when executing the computer program, further implements the vendor server to perform the steps of: the manufacturer server cluster inquires the equipment identifier corresponding to the receiver identifier according to the inquiry request, and when the equipment identifier can be found in the manufacturer server cluster, the equipment identifier is sent to the platform server; and the platform server receives the equipment identification and correspondingly stores the equipment identification and the receiver identification.
In one embodiment, the processor, when executing the computer program, further implements the platform server to perform the steps of: the platform server sends the short message to the operator server by using a sending process according to the short message sending queue; when the processor executes the computer program, the processor also realizes the execution steps of the operator server: and the operator server receives the short message and sends the short message to the receiver terminal.
In one embodiment, the processor, when executing the computer program, further implements the platform server to perform the steps of: when the short message is withdrawn, the platform server generates a withdrawal log according to the task identifier and stores the withdrawal log; and the platform server receives a log withdrawal inquiry command sent by the sender terminal, and returns the withdrawn log to the sender terminal according to the log withdrawal inquiry command, so that the sender terminal displays the withdrawn log.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: the platform server receives a short message sending instruction sent by a sender terminal, generates a task identifier corresponding to the short message according to the short message sending instruction, and returns the task identifier to the sender terminal; the platform server writes the task identifier into a short message sending queue and starts a sending process; the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries a task identifier, and the task identifier is searched in a short message sending queue; and when the task identifier exists in the short message sending queue, the platform server finishes the sending process of the task identifier, deletes the task identifier from the short message sending queue and returns a withdrawal success prompt to the sender terminal.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the task identifier does not exist in the short message sending queue, the platform server sends a short message withdrawal request to the operator server, wherein the short message withdrawal request carries the short message identifier and the platform identifier; the operator server receives the short message recall request and verifies the platform identification according to the short message recall request; when the operator server passes the verification, detecting whether the short message corresponding to the short message identification is sent to the receiver terminal according to the short message withdrawal request; and when the short message is not sent to the receiving party terminal, the operator server intercepts the short message and returns a withdrawal success prompt to the sending party terminal through the platform server.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the short message is sent to the terminal of the receiving party, the operator server sends a short message deleting request to the manufacturer server, wherein the short message deleting request carries the identification of the receiving party, the identification of the short message and the identification of the operator; the manufacturer server verifies the operator identification according to the short message deletion request, and searches a corresponding receiver terminal according to the receiver identification when the operator identification passes verification; when the manufacturer server can find the receiver terminal, the manufacturer server calls the target kernel interface to send a short message deleting instruction to the receiver terminal, so that the receiver terminal deletes the short message corresponding to the short message identification according to the short message deleting instruction; and the manufacturer server returns a withdrawal success prompt to the sender terminal through the operator server and the platform server.
In one embodiment, the computer program when executed by the processor further performs the steps of: and the operator server receives the equipment identifier sent by the platform server and determines the manufacturer server according to the equipment identifier.
In one embodiment, the computer program when executed by the processor further performs the steps of: the platform server sends a query request to a manufacturer server cluster corresponding to different operating systems, wherein the query request carries a receiver identifier; the manufacturer server cluster inquires the equipment identifier corresponding to the receiver identifier according to the inquiry request, and when the equipment identifier can be found in the manufacturer server cluster, the equipment identifier is sent to the platform server; and the platform server receives the equipment identification and correspondingly stores the equipment identification and the receiver identification.
In one embodiment, the computer program when executed by the processor further performs the steps of: the platform server sends the short message to the operator server by using a sending process according to the short message sending queue; and the operator server receives the short message and sends the short message to the receiver terminal.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the short message is withdrawn, the platform server generates a withdrawal log according to the task identifier and stores the withdrawal log; and the platform server receives a log withdrawal inquiry command sent by the sender terminal, and returns the withdrawn log to the sender terminal according to the log withdrawal inquiry command, so that the sender terminal displays the withdrawn log.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A short message withdrawal method comprises the following steps:
the platform server receives a short message sending instruction sent by a sender terminal, generates a task identifier corresponding to a short message according to the short message sending instruction, and returns the task identifier to the sender terminal;
the platform server writes the task identifier into a short message sending queue and starts a sending process;
the platform server receives a short message withdrawal instruction sent by a sender terminal within a preset time period, the short message withdrawal instruction carries the task identifier, and the task identifier is searched in the short message sending queue;
when the platform server finds the task identifier in the short message sending queue, the platform server finishes the sending process of the task identifier, deletes the task identifier from the short message sending queue, and returns a withdrawal success prompt to the sender terminal;
when the platform server sends the short message to an operator server and the operator server detects that the short message to be withdrawn is sent to a receiver terminal, the receiver terminal is found through a manufacturer server, and the receiver terminal deletes the short message through a kernel interface.
2. The method of claim 1, wherein after the platform server receives a short message recall instruction sent by a sender terminal within a preset time period, the short message recall instruction carrying a task identifier, and searches for the task identifier in the short message sending queue, the method further comprises:
when the task identifier is not found in the short message sending queue, the platform server sends a short message withdrawing request to an operator server, wherein the short message withdrawing request carries a short message identifier and a platform identifier;
the operator server receives a short message recall request and verifies the platform identification according to the short message recall request;
when the operator server verifies that the platform identification passes, detecting whether the short message corresponding to the short message identification is sent to a receiver terminal according to the short message withdrawal request;
and the operator server intercepts the short message when the short message is not sent to the receiver terminal, and returns a withdrawal success prompt to the sender terminal through the platform server.
3. The method of claim 2, after detecting whether the short message has been sent to the receiver terminal according to the short message recall request, further comprising:
the operator server sends a short message deleting request to a manufacturer server when the short message is sent to the receiver terminal, wherein the short message deleting request carries a receiver identifier, a short message identifier and an operator identifier;
the manufacturer server verifies the operator identification according to the short message deleting request, and when the operator identification passes the verification, a corresponding receiver terminal is searched according to the receiver identification;
when the manufacturer server finds the receiver terminal, calling a target kernel interface to send a short message deleting instruction to the receiver terminal, so that the receiver terminal deletes the short message corresponding to the short message identification according to the short message deleting instruction;
and the manufacturer server returns a withdrawal success prompt to the sender terminal through the operator server and the platform server.
4. The method of claim 3, before the operator server sends the SMS delete request to the vendor server, further comprising:
and the operator server receives the equipment identifier sent by the platform server and determines the manufacturer server according to the equipment identifier.
5. The method of claim 4, wherein before the operator server receives the device identifier sent by the platform server and determines the vendor server according to the device identifier, the method further comprises:
the platform server sends a query request to a manufacturer server cluster corresponding to different operating systems, wherein the query request carries a receiver identifier;
the manufacturer server cluster inquires an equipment identifier corresponding to a receiver identifier according to the inquiry request, and when the equipment identifier can be found in the manufacturer server cluster, the equipment identifier is sent to a platform server;
and the platform server receives the equipment identification and correspondingly stores the equipment identification and the receiver identification.
6. The method of claim 1, wherein after the platform server writes the task identifier into a short message sending queue and starts a sending process, the method further comprises:
the platform server sends the short message to the operator server by using the sending process according to the short message sending queue;
and the operator server receives the short message and sends the short message to a receiver terminal.
7. The method of claim 1, further comprising:
when the short message is withdrawn, the platform server generates a withdrawal log according to the task identifier and stores the withdrawal log;
and the platform server receives a log withdrawal inquiry command sent by the sender terminal, and returns the log withdrawal to the sender terminal according to the log withdrawal inquiry command, so that the sender terminal displays the log withdrawal.
8. A short message recall system, the system comprising:
the platform server is used for receiving a short message sending instruction sent by a sender terminal, generating a task identifier corresponding to a short message according to the short message sending instruction, and returning the task identifier to the sender terminal;
the platform server is used for writing the task identifier into a short message sending queue and starting a sending process;
the platform server is used for receiving a short message withdrawal instruction sent by a sender terminal within a preset time period, wherein the short message withdrawal instruction carries the task identifier, and the task identifier is searched in the short message sending queue;
the platform server is used for ending the sending process of the task identifier when the task identifier is found in the short message sending queue, deleting the task identifier from the short message sending queue, and returning a withdrawal success prompt to the sender terminal; when the platform server sends the short message to an operator server and the operator server detects that the short message to be withdrawn is sent to a receiver terminal, the receiver terminal is found through a manufacturer server, and the receiver terminal deletes the short message through a kernel interface.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program performs the steps of the method of any one of claims 1 to 7 performed by a platform server, or
The processor, when executing the computer program, performs the steps of the method of any one of claims 1 to 7 performed by an operator server, or
The processor, when executing the computer program, performs the steps of the method of any one of claims 1 to 7 performed by the vendor server.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811023099.1A CN108966159B (en) | 2018-09-03 | 2018-09-03 | Short message withdrawing method, system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811023099.1A CN108966159B (en) | 2018-09-03 | 2018-09-03 | Short message withdrawing method, system, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108966159A CN108966159A (en) | 2018-12-07 |
| CN108966159B true CN108966159B (en) | 2022-03-01 |
Family
ID=64475840
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811023099.1A Active CN108966159B (en) | 2018-09-03 | 2018-09-03 | Short message withdrawing method, system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108966159B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109587348B (en) * | 2019-01-25 | 2023-03-21 | 努比亚技术有限公司 | Communication information management method, mobile terminal, and computer-readable storage medium |
| CN113453173B (en) * | 2021-05-14 | 2023-04-11 | 国网河北省电力有限公司衡水供电分公司 | Short message sending method, device and terminal equipment |
| CN113923176B (en) * | 2021-09-30 | 2023-05-23 | 完美世界(北京)软件科技发展有限公司 | Message withdrawal method, device and equipment for instant messaging and computer readable medium |
| CN114338584B (en) * | 2022-01-11 | 2023-11-14 | 平安科技（深圳）有限公司 | Message withdraw method and message transmission system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685312A (en) * | 2011-03-18 | 2012-09-19 | 上海华勤通讯技术有限公司 | Mobile phone with short message cancellation function and short message cancellation realization method for mobile phone |
| CN104661209A (en) * | 2015-03-03 | 2015-05-27 | 中国联合网络通信集团有限公司 | Short message deleting method and system |
| CN104703155A (en) * | 2015-04-08 | 2015-06-10 | 陈包容 | Method and device for deleting text messages |
| CN104869548A (en) * | 2015-06-19 | 2015-08-26 | 陈包容 | Method and device for remotely modifying short messages |
| WO2016086605A1 (en) * | 2014-12-04 | 2016-06-09 | 中兴通讯股份有限公司 | Short message processing method and apparatus |
| US9549300B1 (en) * | 2013-10-21 | 2017-01-17 | West Corporation | Providing data messaging support by intercepting and processing received short message service (SMS) messages at a customer support service |
| WO2017166707A1 (en) * | 2016-03-28 | 2017-10-05 | 乐视控股（北京）有限公司 | Method and apparatus for cancelling sent short message, and electronic device |
| CN107613475A (en) * | 2017-10-31 | 2018-01-19 | 北京拓通信科技有限公司 | A kind of three net intelligent SMSs send system |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20060073671A (en) * | 2004-12-24 | 2006-06-28 | 주식회사 팬택 | Method and system for providing multimedia message withdrawing service and mobile communication terminal thereof |
| CN1845618A (en) * | 2006-04-30 | 2006-10-11 | 广东移动通信有限责任公司 | Long short-message transmitting-receiving system and realizing method |
| KR20110025221A (en) * | 2008-06-26 | 2011-03-09 | 노키아 지멘스 네트웍스 오와이 | Charging for short message delivery |
| CN101384009A (en) * | 2008-10-08 | 2009-03-11 | 深圳华为通信技术有限公司 | Short message cancelling method and terminal |
| CN102098637A (en) * | 2010-12-17 | 2011-06-15 | 上海酷宇通讯技术有限公司 | Cloud computing platform-based short message sending method, short message sending management system and short message server |
| CN103024136A (en) * | 2011-09-28 | 2013-04-03 | 上海手机测试公共服务平台有限公司 | Mobile phone with short message cancelling function and short message cancelling method thereof |
| US9031586B1 (en) * | 2012-01-27 | 2015-05-12 | West Corporation | System and method for providing SMS message services from multiple originators using a shared shortcode |
| CN103167446B (en) * | 2012-08-23 | 2016-08-03 | 深圳市金立通信设备有限公司 | The method of note cancelled by a kind of SMS during sending |
| CN103220644A (en) * | 2013-03-06 | 2013-07-24 | 北京小米科技有限责任公司 | Short message sending method, device and equipment |
| CN105872994A (en) * | 2016-03-28 | 2016-08-17 | 珠海格力电器股份有限公司 | Method and device for sending short message |
| CN106130888A (en) * | 2016-08-28 | 2016-11-16 | 姜俊 | A kind of SMS cancellation system and method |
-
2018
- 2018-09-03 CN CN201811023099.1A patent/CN108966159B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685312A (en) * | 2011-03-18 | 2012-09-19 | 上海华勤通讯技术有限公司 | Mobile phone with short message cancellation function and short message cancellation realization method for mobile phone |
| US9549300B1 (en) * | 2013-10-21 | 2017-01-17 | West Corporation | Providing data messaging support by intercepting and processing received short message service (SMS) messages at a customer support service |
| WO2016086605A1 (en) * | 2014-12-04 | 2016-06-09 | 中兴通讯股份有限公司 | Short message processing method and apparatus |
| CN104661209A (en) * | 2015-03-03 | 2015-05-27 | 中国联合网络通信集团有限公司 | Short message deleting method and system |
| CN104703155A (en) * | 2015-04-08 | 2015-06-10 | 陈包容 | Method and device for deleting text messages |
| CN104869548A (en) * | 2015-06-19 | 2015-08-26 | 陈包容 | Method and device for remotely modifying short messages |
| WO2017166707A1 (en) * | 2016-03-28 | 2017-10-05 | 乐视控股（北京）有限公司 | Method and apparatus for cancelling sent short message, and electronic device |
| CN107613475A (en) * | 2017-10-31 | 2018-01-19 | 北京拓通信科技有限公司 | A kind of three net intelligent SMSs send system |
Non-Patent Citations (1)
| Title |
|---|
| 集群高效通信机制分析;李涛等;《计算机应用研究》;20051028(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108966159A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108966159B (en) | Short message withdrawing method, system, computer equipment and storage medium | |
| CN109359994B (en) | Service processing method, device and system based on block chain | |
| US8204484B2 (en) | System and method for managing missed calls and unread messages | |
| CN104486388A (en) | Accessing method and device of cloud storage file | |
| CN110908778B (en) | Task deployment method, system and storage medium | |
| CN106302609B (en) | Access method and device | |
| CN103826215A (en) | Method and apparatus for carrying out root authority management at terminal equipment | |
| CN109462601B (en) | Multi-platform access method and device based on eSIM | |
| CN108268346B (en) | Data backup method, device, equipment and storage medium | |
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN109257426B (en) | Service line resource loading method and device, computer equipment and storage medium | |
| CN111586671B (en) | Embedded user identification card configuration method and device, communication equipment and storage medium | |
| CN110795171B (en) | Service data processing method, device, computer equipment and storage medium | |
| CN112632375B (en) | Session information processing method, server and storage medium | |
| CN111666145A (en) | Message processing method and system of message queue and computer equipment | |
| CN115396192A (en) | User identity verification method and device, computer equipment and storage medium | |
| CN114281263A (en) | Storage resource processing method, system and equipment of container cluster management system | |
| CN110741617B (en) | Resource updating method and device, computer equipment and storage medium | |
| CN111328068B (en) | Card writing method and device, computer equipment and storage medium | |
| CN113282580A (en) | Method, storage medium and server for executing timed task | |
| CN110673970B (en) | Cross-process calling system and method based on web application | |
| CN108667919B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN115004666A (en) | Registration method, device, equipment and storage medium of Internet of things equipment | |
| CN115510366A (en) | Business message pushing method and device, computer equipment and storage medium | |
| CN107704557B (en) | Processing method and device for operating mutually exclusive data, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |