WO2018214865A1 - 消息回执的处理方法、相关装置、存储介质和处理器 - Google Patents

消息回执的处理方法、相关装置、存储介质和处理器 Download PDF

Info

Publication number
WO2018214865A1
WO2018214865A1 PCT/CN2018/087799 CN2018087799W WO2018214865A1 WO 2018214865 A1 WO2018214865 A1 WO 2018214865A1 CN 2018087799 W CN2018087799 W CN 2018087799W WO 2018214865 A1 WO2018214865 A1 WO 2018214865A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
delivery
receiving terminal
sending
response information
Prior art date
Application number
PCT/CN2018/087799
Other languages
English (en)
French (fr)
Inventor
张文召
Original Assignee
南京中兴新软件有限责任公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 南京中兴新软件有限责任公司 filed Critical 南京中兴新软件有限责任公司
Publication of WO2018214865A1 publication Critical patent/WO2018214865A1/zh

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18—Commands or executable codes
    • 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]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for processing a message receipt, a storage medium, a processor, and an electronic device.
  • GSMA Global System for Mobile Communication Alliance
  • RCS Rich Communication Suite
  • RFC5438 RFC5438
  • IMDN Instant Message Delivery Notification
  • OTT abbreviation of Over The Top, which refers to providing various application services to users through the Internet
  • SIP Session Initiation Protocol
  • the embodiment of the invention provides a method and a device for processing a message receipt, a computer storage medium and a processor, and an electronic device, so as to at least solve the problem that the receipt message sent by the message receiving terminal needs to be processed by the message receiving terminal in the related art. Traffic and processing resources issues.
  • a method for processing a message receipt is provided, which is applied to an instant messaging application server of a converged communication service platform, including: sending a message to a message receiving terminal; and acquiring a first message generated by the message receiving terminal after receiving the message And responding to the information, determining whether the message receiving terminal successfully receives the message according to the first response information; and sending the first returning message to the message sending terminal if the message receiving terminal successfully receives the message.
  • the method before sending the message to the message receiving terminal, the method further includes: receiving an initial message sent by the message sending terminal, where the initial message carries a return request of the initial message; and triggering sending to the message receiving terminal according to the received initial message The message delivery process of the message; triggering the message delivery process of sending the message to the message receiving terminal according to the received message, including: recording the type of the receipt request, wherein the type includes: a delivery success type, a delivery failure type, and a short message delivery type And deleting the field information corresponding to the type of the return request of the initial message in the initial message to generate a message.
  • the method further includes: determining whether to convert the message into a short message according to the state of the message receiving terminal; and sending the message to the Internet Protocol (IP) in the case of determining to convert the message into a short message.
  • IP Internet Protocol
  • a short message gateway in the case of determining not to convert the message into a short message, transmitting a message to the message receiving terminal.
  • sending the first return message to the message sending terminal includes: determining, in the case that the message receiving terminal successfully receives the message, whether the delivery success type is recorded in the instant message application server The receipt request; in the case where the instant messaging application server records the receipt request of the delivery success type, the first receipt message is sent to the message transmitting terminal.
  • the method further includes: determining, in the case that the message receiving terminal does not successfully receive the message, whether the first response information is a preset failure response information; When the response information is the preset failure response information, it is determined whether the delivery request type of the receipt request is recorded in the instant message application server; and when the instant messaging application server records the delivery request of the delivery failure type, the message is sent to the message.
  • the terminal sends a second receipt message.
  • the method includes: determining whether to convert the information into a short message if the first response information is not the preset failure response information; and determining to convert the information into In the case of a short message, the message is sent to the IP short message gateway; in the case where it is determined that the information is not converted into a short message, the message is saved as an offline message and the message is resent to the message receiving terminal.
  • the method further includes: obtaining second response information generated after the IP short message gateway receives the message; determining, according to the second response information, whether the IP short message gateway successfully receives the message; When the short message gateway successfully receives the message, it is determined whether the return request of the short message delivery type is recorded in the instant message application server; and when the instant message application server records the return request of the short message delivery type, the message is sent to the terminal Send a third receipt message.
  • the method further includes: determining, in the case that the IP short message gateway does not successfully receive the message, whether the delivery failure type is recorded in the instant message application server.
  • a receipt request in the case where a delivery request of the delivery failure type is recorded in the instant message application server, the second receipt message is sent to the message transmitting terminal.
  • a message processing device which is applied to an instant messaging application server of a converged communication service platform, and includes: a first sending module configured to send a message to a message receiving terminal; The module is configured to obtain the first response information generated by the message receiving terminal after receiving the message; the first determining module is configured to determine, according to the first response information, whether the message receiving terminal successfully receives the message; and the second sending module is configured to be at the message receiving terminal In the case of successfully receiving a message, the first receipt message is sent to the message transmitting terminal.
  • the device further includes: a receiving module, configured to: before the first sending module sends a message to the message receiving terminal, receive an initial message sent by the message sending terminal, where the initial message carries a return request of the initial message; the triggering module The method is configured to trigger a message delivery process to send a message to the message receiving terminal according to the received initial message; the triggering module includes: a recording module configured to record a type of the return request, wherein the type includes: a delivery success type, a delivery failure type, and And the deleting module is configured to delete the field information corresponding to the type of the return request of the initial message in the initial message, and generate a message.
  • a receiving module configured to: before the first sending module sends a message to the message receiving terminal, receive an initial message sent by the message sending terminal, where the initial message carries a return request of the initial message
  • the triggering module The method is configured to trigger a message delivery process to send a message to the message receiving terminal according to the received initial message; the triggering module includes:
  • the device further includes: a second determining module, configured to: after the deleting module generates the message, determining whether to convert the message into a short message according to a status of the message receiving terminal; and the third sending module is configured to determine to convert the message into a short message
  • the message is sent to the IP short message gateway;
  • the first calling module is configured to call the first sending module to send a message to the message receiving terminal if it is determined not to convert the message into a short message.
  • the second sending module includes: a third determining module, configured to determine, in the case that the message receiving terminal successfully receives the message, whether the delivery request type of the delivery request is recorded in the instant messaging application server; the fourth sending module, configuring In order to record a delivery request of a delivery success type in the instant messaging application server, the first receipt message is sent to the message transmitting terminal.
  • the device further includes: a fourth determining module, configured to determine, after the first determining module determines, according to the first response information, whether the message receiving terminal successfully receives the message, and if the message receiving terminal does not successfully receive the message, determining the first Whether the response information is the preset failure response information, and the fifth determining module is configured to determine, in the case that the first response information is the preset failure response information, whether the delivery request type of the delivery request is recorded in the instant message application server;
  • the sending module is configured to send a second return receipt message to the message sending terminal if the delivery request type of the return request is recorded in the instant messaging application server.
  • the device further includes: a sixth determining module, configured to determine, after the fourth determining module determines whether the first response information is the preset failure response information, where the first response information is not the preset failure response information, Whether to convert the information into a short message; the second calling module is configured to, when determining to convert the information into a short message, call the third sending module to send the message to the IP short message gateway; and the offline module is configured to determine not to convert the information In the case of a short message, the message is saved as an offline message and the message is resent to the message receiving terminal.
  • a sixth determining module configured to determine, after the fourth determining module determines whether the first response information is the preset failure response information, where the first response information is not the preset failure response information, Whether to convert the information into a short message
  • the second calling module is configured to, when determining to convert the information into a short message, call the third sending module to send the message to the IP short message gateway
  • the offline module is configured to determine not to convert the information In
  • the device further includes: a second acquiring module, configured to: after the third sending module sends the message to the IP short message gateway, obtain the second response information generated after the IP short message gateway receives the message; and the seventh determining module, And configured to determine, according to the second response information, whether the IP short message gateway successfully receives the message; and the eighth determining module is configured to determine, if the IP short message gateway successfully receives the message, whether the short message delivery type is recorded in the instant message application server.
  • a receipt request the sixth sending module is configured to send a third return receipt message to the message sending terminal if the return request of the short message delivery type is recorded in the instant messaging application server.
  • the device further includes: a third calling module, configured to: after the seventh determining module determines, according to the second response information, whether the IP short message gateway successfully receives the message, if the IP short message gateway does not successfully receive the message, The fifth determining module determines whether a delivery request type of the delivery request is recorded in the instant messaging application server, and if the delivery request type of the delivery request is recorded in the instant messaging application server, the fifth sending module is called to send the message to the message sending terminal. Second receipt message.
  • a third calling module configured to: after the seventh determining module determines, according to the second response information, whether the IP short message gateway successfully receives the message, if the IP short message gateway does not successfully receive the message.
  • the fifth determining module determines whether a delivery request type of the delivery request is recorded in the instant messaging application server, and if the delivery request type of the delivery request is recorded in the instant messaging application server, the fifth sending module is called to send the message to the message sending terminal. Second receipt message.
  • a storage medium comprising a stored program, wherein the method is executed while the program is running.
  • a processor for executing a program, wherein the method is executed while the program is running.
  • an electronic device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the above method by a computer program.
  • the instant messaging application server of the converged communication service platform sends the first return receipt message to the message sending terminal when the message receiving terminal successfully receives the message, so that the return message of the successful delivery of the message in the prior art can be solved.
  • FIG. 1 is a block diagram showing the hardware structure of an instant messaging application server according to a method for processing a message receipt according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for processing a message receipt according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of an optional method for processing a message receipt according to Embodiment 2 of the present invention.
  • FIG. 4 is a networking diagram of a message when a message does not need to be forwarded according to Embodiment 2 of the present invention.
  • FIG. 5 is a networking diagram of a message when a message needs to be forwarded according to an alternative embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a processing apparatus for message receipt according to an alternative embodiment 3 of the present invention.
  • FIG. 1 is a hardware structural block diagram of an instant messaging application server for processing a message receipt according to an embodiment of the present invention.
  • instant messaging application server 10 may include one or more (only one of which is shown in FIG. 1) processor 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.
  • a processing device a memory 104 for storing data, and a transmission device 106 for communication functions.
  • a processing device a memory 104 for storing data
  • a transmission device 106 for communication functions.
  • FIG. 1 is merely illustrative, and does not limit the structure of the above instant messaging application server.
  • instant messaging application server 10 may also include more or fewer components than those shown in FIG. 1, or have a different configuration than that shown in FIG.
  • the memory 104 can be used to store software programs and modules of the application software, such as program instructions/modules corresponding to the processing method of the message receipt in the embodiment of the present invention, and the processor 102 executes by executing the software program and the module stored in the memory 104.
  • Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 104 may further include memory remotely located relative to processor 102, which may be connected to mobile terminal 10 over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 106 is for receiving or transmitting data via a network.
  • the above-described network specific examples may include a wireless network provided by a communication provider of the instant messaging application server 10.
  • the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • the method provided by the embodiment of the present invention may be applied to a mobile terminal, a computer terminal, or the like in addition to being applicable to a server.
  • FIG. 2 is a process for processing a message receipt according to an embodiment of the present invention.
  • a flow chart of the method, as shown in FIG. 2, the process includes the following steps:
  • Step S202 sending a message to the message receiving terminal
  • Step S204 Acquire first response information generated after the message receiving terminal receives the message
  • Step S206 determining, according to the first response information, whether the message receiving terminal successfully receives the message
  • Step S208 If the message receiving terminal successfully receives the message, send the first return message to the message sending terminal.
  • the IM AS of the RCS service platform sends a message to the message receiving terminal, and obtains the first response information generated after the message receiving terminal receives the message, and determines whether the message receiving terminal successfully receives the message according to the first response information, and the message is When the receiving terminal successfully receives the message, the first sending back message is sent to the message sending terminal.
  • the IM AS can obtain the message successfully after the message receiving terminal receives the message, so the message is successfully delivered.
  • the receipt message can be processed by the RCS service platform, and the return receipt message successfully sent by the message receiving end is changed by the RCS service platform, and the return message of the successful delivery of the message in the prior art needs to be processed by the message receiving terminal.
  • the problem is that the message receiving terminal traffic and processing resources are consumed, thereby reducing the processing and sending of the message receipt of the message receiving terminal, thereby achieving the effect of saving the performance of the message receiving terminal and processing the device specifically for processing the message receipt.
  • the method before sending the message to the message receiving terminal, the method further includes: receiving an initial message sent by the message sending terminal, where the initial message carries a receipt request of the initial message; according to the received initial message
  • the initial message carries the receipt request of the initial message, which is specifically a request for the receipt of the initial message in the Instant Message Disposition Notification (IMDN) of the initial message.
  • IMDN Instant Message Disposition Notification
  • the type of the return request of the initial message may be first determined and recorded; specifically, the type of the return request of the initial message may be recorded in the message session area of the instant messaging application server; and the initial message is deleted from the initial message.
  • the field information corresponding to the type of the receipt request may be field information corresponding to the type of the receipt request of the instant message sending notification parameter of the deletion initial message, and the initial message is converted into a message that can be sent to the message receiving terminal.
  • the initial message is encapsulated by a Common Presence and Instant Messaging (CPIM) method.
  • CPIM Common Presence and Instant Messaging
  • the initial presentation may be parsed by the universal presentation.
  • the initial message encapsulated in the manner of the message obtains the instant message sending notification parameter of the initial message.
  • the instant message sending notification parameter of the initial message is deleted.
  • the message is encapsulated by the universal presentation of the instant message.
  • the method further includes: determining whether to convert the message into a short message according to a status of the message receiving terminal; and sending the message to the IP short message when determining to convert the message into a short message
  • IP-SM-GW Internet Protocol-Short Message-Gateway
  • sending the first return message to the message sending terminal includes: determining, in the event that the message receiving terminal successfully receives the message, the instant message application server Whether the receipt request of the delivery success type is recorded; in the case where the delivery request type of the receipt request is recorded in the instant message application server, the first receipt message is sent to the message transmitting terminal.
  • determining whether the delivery request type of the delivery success type is recorded in the instant messaging application server is specifically determining whether a delivery success type return receipt request is recorded in the message session area of the instant messaging application server, in the message session area of the instant messaging application server.
  • the first receipt message is sent to the message transmitting terminal.
  • the method further includes: determining, in the case that the message receiving terminal does not successfully receive the message, whether the first response information is a preset Failure response information; if the first response information is the preset failure response information, determining whether a delivery failure type return receipt request is recorded in the instant message application server; and the delivery failure type of the receipt request is recorded in the instant message application server In the case, the second return message is sent to the message sending terminal.
  • determining whether a delivery request type of the delivery failure type is recorded in the instant messaging application server is specifically determining whether a delivery failure type return receipt request is recorded in the message session area of the instant messaging application server, in a message session area of the instant messaging application server.
  • the second receipt message is sent to the message transmitting terminal.
  • the method includes: determining whether to convert the information into a short message if the first response information is not the preset failure response information; In the case of determining to convert the information into a short message, the message is sent to the IP short message gateway; in the case of determining not to convert the information into a short message, the message is saved as an offline message and the message is resent to the message receiving terminal.
  • the method further includes: obtaining second response information generated after the IP short message gateway receives the message; determining, according to the second response information, whether the IP short message gateway is Successfully receiving the message; if the IP short message gateway successfully receives the message, determining whether the instant messaging application server records the receipt request of the forwarding short message delivery type; and recording the receipt request of the short message delivery type in the instant messaging application server Next, the third return message is sent to the message sending terminal.
  • determining whether the return request of the short message delivery type is recorded in the instant message application server is specifically determining whether a return request of the short message delivery type is recorded in the message session area of the instant message application server, and the message session in the instant messaging application server In the case where the return request of the short message delivery type is recorded in the area, the third return message is sent to the message transmitting terminal.
  • the method further includes: determining, in the case that the IP short message gateway does not successfully receive the message, whether the instant messaging application server is A receipt request of a delivery failure type is recorded; in the case where a delivery request of a delivery failure type is recorded in the instant message application server, a second receipt message is transmitted to the message transmitting terminal.
  • FIG. 3 is a flowchart of an optional method for processing a message receipt according to an embodiment of the present invention. As shown in FIG. 3, the following specifically includes the following processes:
  • Step 1 The message sending terminal sends a message to the IM AS, which may be an instant message, corresponding to the initial message, and setting an IMDN carrying a delivery-Notification receipt request of the IM AS;
  • Step 2 The IM AS returns a response code to the message sending terminal. If the IM AS receives the success, it returns a response code of the SIP 200 or 202 to the message sending terminal, and the message sending terminal receives the response code of the SIP 200 or 202 returned by the IM AS. , indicating that the message has been sent successfully;
  • the IM AS that returns the response code to the message transmitting terminal is the IM AS to which the message transmitting terminal belongs; the IM AS to which the message transmitting terminal belongs also forwards the message received from the message transmitting terminal to the IM AS to which the message receiving terminal belongs.
  • Step 3 After the IM AS that the message receiving terminal belongs to successfully receives the message, the IM AS starts to trigger the message delivery process.
  • Step 4 When the triggering message is sent, the IM AS to which the message receiving terminal belongs determines the type of the return request carried in the IMDN.
  • the initial message includes the message header and the message body, and the message header usually indicates the initial message.
  • the IMDN is included in the message body, and the message body is encapsulated by the CPIM method.
  • the IM AS parses the imdn.Disposition-Notification parameter in the message body, and determines the type of the receipt request based on the parameter, if the IMDN carries a positive-delivery, a negative-delivery, a forward-delivery If any one or more of the receipt requests, the corresponding receipt request field information in the IMDN of the message body deletes and re-encapsulates the message body, and a message is generated at this time, and the generated message is sent to the message receiving terminal or IP-SM.
  • the positive-delivery receipt request of the message is recorded in the message session area of the IM AS, and the corresponding receipt request field in the IMDN is deleted; if the parsing IMDN exists, there is a forward-delivery The receipt request, the forward-delivery receipt request of the message is recorded in the message session area of the IM AS, and the corresponding receipt request field in the IMDN is deleted;
  • Step 5 Before the IM AS performs message delivery, it is determined whether to convert the message into a short message according to the state of the message receiving terminal; that is, whether the message receiving terminal supports the information sent by the IM AS, according to the China Mobile Converged Communication Service Specification, for receiving If the user is a converged communication user but is not online or the recipient user is not a converged communication user, the message must be forwarded to SMS or converted to a short message link. Therefore, the IM AS can determine whether the message needs to be forwarded according to the status of the message receiving terminal. SMS, go to step 11, if you do not need to send text messages, go to step 6;
  • Step 6 The IM AS sends a message to the message receiving terminal, that is, the message is normally delivered to the message receiving terminal.
  • the network diagram when the message does not need to be forwarded is shown in FIG. 4, and the IM in FIG. 4 refers to the instant message. (Instant Message);
  • Step 7 The message receiving terminal returns a response code, and the IM AS can determine whether the message receiving terminal successfully responds according to the response code returned by the message receiving terminal. Specifically, if the message receiving terminal successfully receives the message, it returns a response of the SIP 200 OK to the IM AS. Code, and step 8 is performed. If the message fails to be delivered, the response code returned by the message receiving terminal is an error response code, and step 9 is performed;
  • Step 8 Although the message receiving terminal successfully receives the message, since the positive-delivery receipt request in the message body CPIM has been deleted, the message receiving terminal does not have a positive-delivery receipt request after parsing the IMMN encapsulated IMDN after receiving the message, so After the processing is performed, the status report of "successful delivery" is not triggered again; after receiving the SIP200 OK response code returned by the message receiving terminal, the IM AS checks the session record of the message recorded in the message session area of the IM AS, if any The positive-delivery receipt request sends a receipt message with a status of ⁇ delivered/> to the message sending terminal; otherwise, the process ends;
  • Step 9 If the message fails to be delivered, the response code returned by the message receiving terminal is an error response code, such as a SIP 4xx, 5xx, or 6xx type error response code.
  • the IM AS needs to determine whether the message receiving terminal fails to respond according to the error response code. If the response is unsuccessful, go to step 9.b). If it is not a failure response, go to step 9.a);
  • the IM AS determines whether to convert the information into a short message. Specifically, the IM AS can determine whether to convert the information into a short message according to a preset text-forwarding policy, and if the information needs to be converted into a short message, Step 11 is performed, if it is not required to convert the information into a short message, step 10 is performed;
  • the short message strategy described herein can be set according to actual business conditions. For example, it can be set that the calling number (message sending terminal) belongs to a certain number of segments, and the information needs to be forwarded to the short message.
  • the calling number can be set to allow the information to be converted into a short message, and the information belonging to the burning type can be set. It is not allowed to convert information to text messages.
  • the foregoing SMS forwarding policy is only a few specific examples, and does not limit all implementation manners of the SMS forwarding policy in this solution. Any other reasonable strategy that can be thought of can be used as a text messaging strategy in this scenario.
  • the said short message means that the information (message) is sent by short message.
  • step 10 it may be further determined whether the information is saved as offline information. If the information is saved as offline information, step 10 may be performed. If the information is not required to be saved as offline information, the IM AS checks the IM AS. Whether there is a negative-delivery receipt request in the session record of the message recorded in the message session area, and if yes, a receipt message with a construction status of ⁇ failed/> is sent to the message sending terminal; otherwise, the process ends;
  • step 10 the information is cached as offline information, and the message receiving terminal may be re-attempted to send a message according to a preset retrying policy or cached for a period of time before retrying to send a message to the message receiving terminal.
  • the purpose of buffering offline information is to send the message to the message receiving terminal.
  • the retry strategy involved can be flexibly set according to the actual situation of the business. For example, after the information is buffered, the message receiving terminal may be resent once every 5 s, and sent continuously three times; or may be resent once to the message receiving terminal every 10 s, and sent twice in succession; If the previous receiving message receiving terminal can successfully receive, then it is not necessary to send the next time.
  • the foregoing retry strategy is only a few specific examples, and does not limit all implementations of the retry strategy in this solution. Any other reasonable strategy that can be thought of can be used as a retry strategy in this scenario.
  • Step 11 the IM AS forwards the message to the IP-SM-GW;
  • Step 12 After the IM AS forwards the message to the IP-SM-GW, the IP-SM-GW returns a response result.
  • the networking diagram when the message needs to be forwarded is shown in FIG. 5, and the SMS in FIG. 5 refers to Simple Message Service, IM refers to Instant Message; IM AS determines whether IP-SM-GW receives the message successfully according to the response result; if the reception is successful, Step 13 is performed, if the information fails, then Perform step 9.b;
  • Step 13 If the IP-SM-GW receives the message successfully, it returns a response code of the SIP 200 OK, and the IM AS checks the message recorded in the message session area of the IM AS according to the SIP 200 OK response code returned by the IP-SM-GW. Whether there is a forward-delivery receipt request in the session record, and if so, a receipt message with a construction status of ⁇ forwarded/> is sent to the message sending terminal; if not, the process ends;
  • the state after the message is forwarded to the short message cannot be notified to the message sending terminal, and the message sending terminal cannot know whether the message is finally transferred to the short message.
  • the message is extended.
  • the request type of the receipt is determined by the RCS service platform, specifically the IM AS in the RCS service platform, and the message for the SMS or SMS link is performed by the RCS service platform, specifically the IM AS in the RCS service platform.
  • the message receipt processing may notify the message sending terminal of the message processing status; the message receiving terminal does not have the perception of the short message receiving request, and the normal processing may be performed after receiving the message sent by the IP-SM-GW.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a processing device for the message receipt is provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 6 is a structural block diagram of a processing device for message receipt according to an embodiment of the present invention.
  • the device includes: a first sending module 22, a first obtaining module 24, a first determining module 26, and a second sending module. 28, and the device is applied to the IM AS of the RCS service platform.
  • the device is described in detail below: the first sending module 22 is configured to send a message to the message receiving terminal, and the first obtaining module 24 is configured to acquire the message receiving terminal.
  • the first determining module 26 is configured to determine, according to the first response information, whether the message receiving terminal successfully receives the message; and the second sending module 28 is configured to: when the message receiving terminal successfully receives the message Sending a first receipt message to the message sending terminal.
  • the device further includes: a receiving module, configured to receive an initial message sent by the message sending terminal before the first sending module 22 sends the message to the message receiving terminal, where the initial message carries an initial message a receipt request of the message; the triggering module is configured to trigger a message delivery process to send a message to the message receiving terminal according to the received initial message; the triggering module includes: a recording module configured to record a type of the receipt request, wherein the type includes: delivery The success type, the delivery failure type, and the short message delivery type; and the deletion module is configured to delete the field information corresponding to the type of the receipt request of the initial message in the initial message, and generate a message.
  • a receiving module configured to receive an initial message sent by the message sending terminal before the first sending module 22 sends the message to the message receiving terminal, where the initial message carries an initial message a receipt request of the message
  • the triggering module is configured to trigger a message delivery process to send a message to the message receiving terminal according to the received initial message
  • the triggering module includes:
  • the device further includes: a second determining module, configured to: after the deleting module generates the message, determine whether to convert the message into a short message according to a status of the message receiving terminal; and the third sending module is configured to be When it is determined that the message is converted into a short message, the message is sent to the IP short message gateway; the first calling module is configured to call the first sending module to send a message to the message receiving terminal if it is determined not to convert the message into a short message.
  • a second determining module configured to: after the deleting module generates the message, determine whether to convert the message into a short message according to a status of the message receiving terminal
  • the third sending module is configured to be When it is determined that the message is converted into a short message, the message is sent to the IP short message gateway; the first calling module is configured to call the first sending module to send a message to the message receiving terminal if it is determined not to convert the message into a short message.
  • the second sending module includes: a third determining module, configured to determine, if the message receiving terminal successfully receives the message, whether the delivery request type of the delivery request is recorded in the instant messaging application server;
  • the fourth sending module is configured to send the first return receipt message to the message sending terminal if the delivery request type of the return request is recorded in the instant messaging application server.
  • the apparatus further includes: a fourth determining module, configured to: after the first determining module determines, according to the first response information, whether the message receiving terminal successfully receives the message, the message receiving terminal does not successfully receive the message.
  • the fifth determining module is configured to determine whether the delivery failure type is recorded in the instant message application server if the first response information is the preset failure response information.
  • the fifth sending module is configured to send a second return receipt message to the message sending terminal if the delivery request type of the return request is recorded in the instant messaging application server.
  • the device further includes: a sixth determining module, configured to: after the fourth determining module determines whether the first response information is the preset failure response information, the first response information is not the preset failure response.
  • a sixth determining module configured to: after the fourth determining module determines whether the first response information is the preset failure response information, the first response information is not the preset failure response.
  • the second calling module is configured to, when determining to convert the information into a short message, call the third sending module to send the message to the IP short message gateway
  • the offline module is configured as In the case where it is determined that the information is not converted into a short message, the message is saved as an offline message and the message is resent to the message receiving terminal.
  • the device further includes: a second obtaining module, configured to: after the third sending module sends the message to the IP short message gateway, obtain the second response information generated by the IP short message gateway after receiving the message a seventh determining module, configured to determine, according to the second response information, whether the IP short message gateway successfully receives the message; the eighth determining module is configured to determine whether the instant message application server records in the case that the IP short message gateway successfully receives the message There is a return receipt request of the short message delivery type; the sixth sending module is configured to send a third return receipt message to the message sending terminal if the return request of the short message delivery type is recorded in the instant message application server.
  • a second obtaining module configured to: after the third sending module sends the message to the IP short message gateway, obtain the second response information generated by the IP short message gateway after receiving the message a seventh determining module, configured to determine, according to the second response information, whether the IP short message gateway successfully receives the message
  • the eighth determining module is configured to determine whether the instant message application server records in the case that
  • the apparatus further includes: a third calling module, configured to: after the seventh determining module determines, according to the second response information, whether the IP short message gateway successfully receives the message, the IP short message gateway does not successfully receive
  • the fifth determining module is called to determine whether a delivery request of the delivery failure type is recorded in the instant messaging application server, and the fifth sending module is invoked if the delivery request of the delivery failure type is recorded in the instant messaging application server. Sending a second return receipt message to the message sending terminal.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • Embodiments of the present invention also provide a storage medium including a stored program, wherein the above method is executed while the program is running.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the first return message is sent to the message transmitting terminal.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Embodiments of the present invention also provide a processor for running a program, wherein the program executes the steps of the above method while it is running.
  • the foregoing program is used to perform the following steps:
  • the first return message is sent to the message transmitting terminal.
  • Embodiments of the present invention also provide an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the above method by a computer program.
  • the foregoing program is used to perform the following steps:
  • the first return message is sent to the message transmitting terminal.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the instant messaging application server of the converged communication service platform sends the first return receipt message to the message sending terminal when the message receiving terminal successfully receives the message, so that the return message of the successful delivery of the message in the prior art can be solved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供了一种消息回执的处理方法和装置。其中，该方法应用于融合通信业务平台的即时消息应用服务器，包括：向消息接收终端发送消息；获取消息接收终端接收消息后产生的第一响应信息；根据第一响应信息确定消息接收终端是否成功接收消息；在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。

Description

消息回执的处理方法、相关装置、存储介质和处理器
相关申请的交叉引用
本申请基于申请号为201710380009.3、申请日为2017年5月25日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的内容在此以引入方式并入本申请。
技术领域
本发明涉及通信领域，具体而言，涉及一种消息回执的处理方法和装置、存储介质、处理器和电子装置。
背景技术
随着通信技术的飞速发展，也刺激了短信息(短消息)、彩信(多媒体消息)、即时消息、电子邮件和语音邮件等消息类业务的发展，按照全球移动通信系统联盟(Global System for Mobile Communication Alliance，简称为GSMA)的融合通信(Rich Communication Suite，简称为RCS)规范以及RFC5438(RFC为Request For Comments的简写，一系列以编号排定的文件)定义，消息发送终端发送消息时可以携带即时消息发送通知(Instant Message Delivery Notification，简称为IMDN)请求消息回执。对于投递失败(negative-delivery)的消息回执请求，由RCS业务平台进行处理，而对于投递成功(positive-delivery)的消息回执请求，则由消息接收终端进行处理。
与基于私有协议的OTT(Over The Top的缩写，指通过互联网向用户提供各种应用服务)消息产品相比，基于会话发起协议(Session Initiation Protocol，简称为SIP)的RCS消息，协议中消息头冗余多，消息接收终端进行处理positive-delivery的消息回执请求时，会耗费更多的流量和消息处 理资源。
发明内容
本发明实施例提供一种消息回执的处理方法和装置、计算机存储介质和处理器、电子装置，以至少解决相关技术中消息成功投递的回执消息需要由消息接收终端处理而造成的耗费消息接收终端流量和处理资源的问题。
根据本发明的一个实施例，提供了一种消息回执的处理方法，应用于融合通信业务平台的即时消息应用服务器，包括：向消息接收终端发送消息；获取消息接收终端接收消息后产生的第一响应信息；根据第一响应信息确定消息接收终端是否成功接收消息；在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
可选的，向消息接收终端发送消息之前，方法还包括：接收消息发送终端发送的初始消息，其中，初始消息中携带有初始消息的回执请求；根据接收到的初始消息触发向消息接收终端发送消息的消息下发流程；根据接收到的消息触发向消息接收终端发送消息的消息下发流程，包括：记录回执请求的类型，其中，类型包括：投递成功类型、投递失败类型和转短信投递类型；以及删除初始消息中与初始消息的回执请求的类型对应的字段信息，生成消息。
可选的，生成消息之后，方法还包括：根据消息接收终端的状态确定是否将消息转化为短信；在确定将消息转化为短信的情况下，将消息发送给网际协议(Internet Protocol，简写成IP)短消息网关；在确定不将消息转化为短信的情况下，向消息接收终端发送消息。
可选的，在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息，包括：在消息接收终端成功接收消息的情况下，确定即时消息应用服务器中是否记录有投递成功类型的回执请求；在即时消息应 用服务器中记录有投递成功类型的回执请求的情况下，向消息发送终端发送第一回执消息。
可选的，根据第一响应信息确定消息接收终端是否成功接收消息之后，方法还包括：在消息接收终端未成功接收消息的情况下，确定第一响应信息是否为预设失败响应信息；在第一响应信息是预设失败响应信息的情况下，确定即时消息应用服务器中是否记录有投递失败类型的回执请求；在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，向消息发送终端发送第二回执消息。
可选的，确定第一响应信息是否为预设失败响应信息之后，方法包括：在第一响应信息不是预设失败响应信息的情况下，确定是否将信息转化为短信；在确定将信息转化为短信的情况下，将消息发送给IP短消息网关；在确定不将信息转化为短信的情况下，将消息存为离线消息并重新向消息接收终端发送消息。
可选的，将消息发送给IP短消息网关之后，方法还包括：获取IP短消息网关接收消息后产生的第二响应信息；根据第二响应信息确定IP短消息网关是否成功接收消息；在IP短消息网关成功接收消息的情况下，确定即时消息应用服务器中是否记录有转短信投递类型的回执请求；在即时消息应用服务器中记录有转短信投递类型的回执请求的情况下，向消息发送终端发送第三回执消息。
可选的，根据第二响应信息确定IP短消息网关是否成功接收消息之后，方法还包括：在IP短消息网关未成功接收消息的情况下，确定即时消息应用服务器中是否记录有投递失败类型的回执请求；在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，向消息发送终端发送第二回执消息。
根据本发明的另一个实施例，提供了一种消息回执的处理装置，应用 于融合通信业务平台的即时消息应用服务器，包括：第一发送模块，配置为向消息接收终端发送消息；第一获取模块，配置为获取消息接收终端接收消息后产生的第一响应信息；第一确定模块，配置为根据第一响应信息确定消息接收终端是否成功接收消息；第二发送模块，配置为在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
可选的，装置还包括：接收模块，配置为在第一发送模块向消息接收终端发送消息之前，接收消息发送终端发送的初始消息，其中，初始消息中携带有初始消息的回执请求；触发模块，配置为根据接收到的初始消息触发向消息接收终端发送消息的消息下发流程；触发模块包括：记录模块，配置为记录回执请求的类型，其中，类型包括：投递成功类型、投递失败类型和转短信投递类型；以及删除模块，配置为删除初始消息中与初始消息的回执请求的类型对应的字段信息，生成消息。
可选的，装置还包括：第二确定模块，配置为在删除模块生成消息之后，根据消息接收终端的状态确定是否将消息转化为短信；第三发送模块，配置为在确定将消息转化为短信的情况下，将消息发送给IP短消息网关；第一调用模块，配置为在确定不将消息转化为短信的情况下，调用第一发送模块向消息接收终端发送消息。
可选的，第二发送模块包括：第三确定模块，配置为在消息接收终端成功接收消息的情况下，确定即时消息应用服务器中是否记录有投递成功类型的回执请求；第四发送模块，配置为在即时消息应用服务器中记录有投递成功类型的回执请求的情况下，向消息发送终端发送第一回执消息。
可选的，装置还包括：第四确定模块，配置为在第一确定模块根据第一响应信息确定消息接收终端是否成功接收消息之后，在消息接收终端未成功接收消息的情况下，确定第一响应信息是否为预设失败响应信息；第五确定模块，配置为在第一响应信息是预设失败响应信息的情况下，确定 即时消息应用服务器中是否记录有投递失败类型的回执请求；第五发送模块，配置为在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，向消息发送终端发送第二回执消息。
可选的，装置还包括：第六确定模块，配置为在第四确定模块确定第一响应信息是否为预设失败响应信息之后，在第一响应信息不是预设失败响应信息的情况下，确定是否将信息转化为短信；第二调用模块，配置为在确定将信息转化为短信的情况下，调用第三发送模块将消息发送给IP短消息网关；离线模块，配置为在确定不将信息转化为短信的情况下，将消息存为离线消息并重新向消息接收终端发送消息。
可选的，装置还包括：第二获取模块，配置为在第三发送模块将消息发送给IP短消息网关之后，获取IP短消息网关接收消息后产生的第二响应信息；第七确定模块，配置为根据第二响应信息确定IP短消息网关是否成功接收消息；第八确定模块，配置为在IP短消息网关成功接收消息的情况下，确定即时消息应用服务器中是否记录有转短信投递类型的回执请求；第六发送模块，配置为在即时消息应用服务器中记录有转短信投递类型的回执请求的情况下，向消息发送终端发送第三回执消息。
可选的，装置还包括：第三调用模块，配置为在第七确定模块根据第二响应信息确定IP短消息网关是否成功接收消息之后，在IP短消息网关未成功接收消息的情况下，调用第五确定模块确定即时消息应用服务器中是否记录有投递失败类型的回执请求，以及在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，调用第五发送模块向消息发送终端发送第二回执消息。
根据本发明的又一个实施例，还提供了一种存储介质，存储介质包括存储的程序，其中，程序运行时执行上述方法。
根据本发明的又一个实施例，还提供了一种处理器，处理器用于运行 程序，其中，程序运行时执行上述方法。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，处理器通过计算机程序执行上述方法。
本发明实施例中，由于融合通信业务平台的即时消息应用服务器在消息接收终端成功接收消息时，向消息发送终端发送第一回执消息，因此，可以解决现有技术中消息成功投递的回执消息需要由消息接收终端处理而造成的耗费消息接收终端流量和处理资源的问题，进而达到了节省消息接收终端流量和处理资源的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例1的消息回执的处理方法的即时消息应用服务器的硬件结构框图；
图2是根据本发明实施例2的消息回执的处理方法的流程图；
图3是根据本发明实施例2的一种可选的消息回执的处理方法的流程图；
图4是根据本发明实施例2的消息不需要转短信时的组网图；
图5是根据本发明可选实施例的2的消息需要转短信时的组网图；
图6是根据本发明可选实施例3的消息回执的处理装置的结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例所提供的方法实施例可以在各种服务器中执行，例如融合通信业务平台的即时消息应用服务器(简称为即时消息应用服务器)、群聊应用服务器(GCAS)。以运行在即时消息应用服务器上为例，图1是本发明实施例的一种消息回执的处理方法的即时消息应用服务器的硬件结构框图。如图1所示，即时消息应用服务器10可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的存储器104、以及用于通信功能的传输装置106。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述即时消息应用服务器的结构造成限定。例如，即时消息应用服务器10还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储应用软件的软件程序以及模块，如本发明实施例中的消息回执的处理方法对应的程序指令/模块，处理器102通过运行存储在存储器104内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体 实例可包括即时消息应用服务器10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
当然，在一些应用场景下，本发明实施例提供的方法除了可以应用在服务器中，还可以应用在移动终端、计算机终端或者类似的运算装置中执行。
实施例2
在本实施例中提供了一种消息回执的处理方法，应用于RCS业务平台的即时消息应用服务器(Instant Message Application Server，简称为IM AS)，图2是根据本发明实施例的消息回执的处理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，向消息接收终端发送消息；
步骤S204，获取消息接收终端接收消息后产生的第一响应信息；
步骤S206，根据第一响应信息确定消息接收终端是否成功接收消息；
步骤S208，在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
通过上述步骤，由RCS业务平台的IM AS向消息接收终端发送消息，并获取消息接收终端接收消息后产生的第一响应信息，根据第一响应信息确定消息接收终端是否成功接收消息，并在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息，在RCS业务平台中，IM AS可以通过消息接收终端接收消息后的响应信息获知消息已下发成功，所以消息下发成功的回执消息可以由RCS业务平台处理，通过将需要消息接收端处理的消息下发成功的回执消息改由RCS业务平台实现，解决了现有技 术中消息成功投递的回执消息需要由消息接收终端处理而造成的耗费消息接收终端流量和处理资源的问题，由此减少消息接收终端的消息回执的处理和发送，进而达到了节省消息接收终端流量和处理资源具体为处理消息回执的设备性能的效果。
在一种可选的实施例中，向消息接收终端发送消息之前，方法还包括：接收消息发送终端发送的初始消息，其中，初始消息中携带有初始消息的回执请求；根据接收到的初始消息触发向消息接收终端发送消息的消息下发流程；根据接收到的消息触发向消息接收终端发送消息的消息下发流程包括：记录回执请求的类型，其中，类型包括：投递成功类型(positive-delivery)、投递失败类型(negative-delivery)和转短信投递类型(forward-delivery)；以及删除初始消息中与初始消息的回执请求的类型对应的字段信息，生成消息。
具体的，初始消息中携带有初始消息的回执请求，具体为初始消息的即时消息处理通知参数(Instant Message Disposition Notification，简称为IMDN)中携带有初始消息的回执请求。触发消息下发流程时，可以首先确定并记录初始消息的回执请求的类型；具体可以在即时消息应用服务器中的消息会话区中记录初始消息的回执请求的类型；删除初始消息中与初始消息的回执请求的类型对应的字段信息、具体可以为删除初始消息的即时消息发送通知参数中与消初始息的回执请求的类型对应的字段信息，初始消息即转化为可以向消息接收终端发送的消息。
在一种可选的实施例中，初始消息由通用呈现即时消息(Common Presence and Instant Messaging，简称为CPIM)的方式封装，在确定初始消息的回执请求的类型时，可以首先解析由通用呈现即时消息的方式封装的初始消息，得到初始消息的即时消息发送通知参数，在确定了初始消息的即时消息发送通知参数中携带的初始消息的回执请求的类型后，删除初始 消息的即时消息发送通知参数中与初始消息的回执请求的类型对应的字段信息并生成消息之后，由通用呈现即时消息的方式封装消息。
在一种可选的实施例中，生成消息之后，方法还包括：根据消息接收终端的状态确定是否将消息转化为短信；在确定将消息转化为短信的情况下，将消息发送给IP短消息网关(Internet Protocol-Short Message-Gateway，简称为IP-SM-GW)；在确定不将消息转化为短信的情况下，向消息接收终端发送消息。
在一种可选的实施例中，在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息，包括：在消息接收终端成功接收消息的情况下，确定即时消息应用服务器中是否记录有投递成功类型的回执请求；在即时消息应用服务器中记录有投递成功类型的回执请求的情况下，向消息发送终端发送第一回执消息。
具体的，确定即时消息应用服务器中是否记录有投递成功类型的回执请求具体为确定即时消息应用服务器的消息会话区中是否记录有投递成功类型的回执请求，在即时消息应用服务器的消息会话区中记录有投递成功类型的回执请求的情况下，向消息发送终端发送第一回执消息。
在一种可选的实施例中，根据第一响应信息确定消息接收终端是否成功接收消息之后，方法还包括：在消息接收终端未成功接收消息的情况下，确定第一响应信息是否为预设失败响应信息；在第一响应信息是预设失败响应信息的情况下，确定即时消息应用服务器中是否记录有投递失败类型的回执请求；在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，向消息发送终端发送第二回执消息。
具体的，确定即时消息应用服务器中是否记录有投递失败类型的回执请求具体为确定即时消息应用服务器的消息会话区中是否记录有投递失败类型的回执请求，在即时消息应用服务器的消息会话区中记录有投递失败 类型的回执请求的情况下，向消息发送终端发送第二回执消息。
在一种可选的实施例中，确定第一响应信息是否为预设失败响应信息之后，方法包括：在第一响应信息不是预设失败响应信息的情况下，确定是否将信息转化为短信；在确定将信息转化为短信的情况下，将消息发送给IP短消息网关；在确定不将信息转化为短信的情况下，将消息存为离线消息并重新向消息接收终端发送消息。
在一种可选的实施例中，将消息发送给IP短消息网关之后，方法还包括：获取IP短消息网关接收消息后产生的第二响应信息；根据第二响应信息确定IP短消息网关是否成功接收消息；在IP短消息网关成功接收消息的情况下，确定即时消息应用服务器中是否记录有转短信投递类型的回执请求；在即时消息应用服务器中记录有转短信投递类型的回执请求的情况下，向消息发送终端发送第三回执消息。
具体的，确定即时消息应用服务器中是否记录有转短信投递类型的回执请求具体为确定即时消息应用服务器的消息会话区中是否记录有转短信投递类型的回执请求，在即时消息应用服务器的消息会话区中记录有转短信投递类型的回执请求的情况下，向消息发送终端发送第三回执消息。
在一种可选的实施例中，根据第二响应信息确定IP短消息网关是否成功接收消息之后，方法还包括：在IP短消息网关未成功接收消息的情况下，确定即时消息应用服务器中是否记录有投递失败类型的回执请求；在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，向消息发送终端发送第二回执消息。
在一种具体的实施例中，图3是本发明实施例的一种可选的消息回执的处理方法的流程图，如图3所示，具体包括以下流程：
步骤1，消息发送终端向IM AS发送消息，具体可以是即时消息，对应上述初始消息，并设置IM AS的IMDN携带发送通知 (delivery-Notification)回执请求；
步骤2，IM AS向消息发送终端返回响应码，如果IM AS接收成功，则向消息发送终端返回SIP 200或者202的响应码，消息发送终端收到IM AS返回的SIP 200或者202的响应码后，显示消息已发送成功；
这里，向消息发送终端返回响应码的IM AS是消息发送终端归属的IM AS；消息发送终端归属的IM AS还将从消息发送终端接收到的消息转发至消息接收终端归属的IM AS。
步骤3，消息接收终端归属的IM AS成功接收到消息后，IM AS开始触发消息下发流程；
步骤4，在触发消息下发流程时，首先，消息接收终端归属的IM AS判断IMDN中携带的回执请求的类型，通常初始消息包括消息头和消息体这两个部分，消息头通常指明初始消息来源于哪个终端去往哪个终端、消息从来源终端到去往终端所经过的路由等信息。本步骤中，IMDN是包括在消息体里的，消息体通过CPIM方法进行封装。具体的、IM AS解析消息体中的imdn.Disposition-Notification(即时消息处理通知)参数，并基于此参数，判断回执请求的类型，如果IMDN携带有positive-delivery、negative-delivery、forward-delivery的回执请求的任意一种或几种，则消息体的IMDN中相应的回执请求字段信息删除并重新封装消息体，此时生成消息，所生成的消息即为即将发送给消息接收终端或IP-SM-GW的消息，同时在消息会话区记录该消息的positive-delivery、negative-delivery、forward-delivery的回执请求类型，然后由IM AS进行消息投递；通过将消息体的IMDN中相应的回执请求字段信息删除并重新封装消息体，可以避免消息接收终端向消息发送终端二次发送回执消息；
具体为，如果解析IMDN存在有positive-delivery回执请求，则在IM AS的消息会话区记录该消息的positive-delivery回执请求，同时删除IMDN中 相应的回执请求字段；如果解析IMDN存在有forward-delivery回执请求，则在IM AS的消息会话区记录该消息的forward-delivery回执请求，同时删除IMDN中相应的回执请求字段；
步骤5，在IM AS进行消息投递之前，需要根据消息接收终端的状态确定是否将消息转化为短信；也就是判断消息接收终端是否支持IM AS发送的信息，按照中国移动融合通信业务规范，对于接收方用户是融合通信用户但不在线或者接收方用户不是融合通信的用户，消息都要转短信或者转为短信链接，因此IM AS根据消息接收终端的状态可以判断是否需要转短信，如果消息需要转短信，则执行步骤11，如果不需要转短信，则执行步骤6；
步骤6，IM AS向消息接收终端发送消息，即将消息进行正常投递给消息接收终端；其中，消息不需要转短信时的组网图如图4所示，图4中的IM指的是即时消息(Instant Message)；
步骤7，消息接收终端返回响应码，IM AS根据消息接收终端返回的响应码可以判断消息接收终端是否成功响应，具体的，如果消息接收终端成功接收消息，则向IM AS返回SIP 200 OK的响应码，并执行步骤8，如果消息下发失败，消息接收终端返回的响应码为错误响应码，此时执行步骤9；
步骤8，虽然消息接收终端成功接收消息，但是由于消息体CPIM中的positive-delivery回执请求已被删除，消息接收终端接收消息后解析CPIM封装的IMDN不会有positive-delivery回执请求，因此不会再做处理，即不会再触发“投递成功”的状态报告；IM AS接收到消息接收终端返回的SIP200 OK响应码后，检查IM AS的消息会话区中记录的该消息的会话记录，如果有positive-delivery的回执请求，则构造状态为<delivered/>的回执消息发送给消息发送终端，否则，流程结束；
步骤9，如果消息下发失败，消息接收终端返回的响应码为错误响应码， 如SIP 4xx、5xx或者6xx类错误响应码等，IM AS需要根据错误响应码判断消息接收终端是否响应失败，如果失败响应，则执行步骤9.b)，如果不是失败响应，则执行步骤9.a)；
9.a)如果不是失败响应，则IM AS确定是否将信息转化为短信，具体的，IM AS可以根据预设的转短信策略判断是否将信息转化为短信，如果需要将信息转化为短信，则执行步骤11，如果不需要将信息转化为短信，则执行步骤10；
本领域技术人员应该而知，此处所说的转短信策略可以依据实际业务情况而设置。例如，可以设置主叫号码(消息发送终端)属于某个号段的需要将信息转短信，可以设置主叫号码不欠费的允许将信息转为短信，可以设置属于阅后即焚类型的信息不允许将信息转为短信。前述的转短信策略仅是几种具体举例而已，并不限定本方案中转短信策略的所有实现方式。能够想到的任何其他合理的策略均可作为本方案中的转短信策略。此处，可以理解，所说的转短信的意思是说将信息(消息)以短信方式下发。
9.b)如果是失败响应，可以进一步确定是否将信息存为离线信息，如果将信息存为离线信息，可以执行步骤10，如果不需要将信息存为离线信息，则IM AS检查IM AS的消息会话区中记录的该消息的会话记录中是否有negative-delivery的回执请求，如果有则构造状态为<failed/>的回执消息发送给消息发送终端，否则，流程结束；
步骤10，将信息缓存为离线信息，可以按照预设的重试策略直接向消息接收终端重新尝试发送消息或者缓存一段时间后再向消息接收终端重新尝试发送消息。
这里，缓存为离线信息的目的在于需要将该消息发送至消息接收终端。所涉及的重试策略可以依据业务的实际情况而灵活设置。例如，在进行信息的缓存之后，可以每隔5s向消息接收终端重新发送一次，连续发送三次； 也可以每隔10s向消息接收终端重新发送一次，连续发送二次；在连续发送多次的方案中，如果前一次发送消息接收终端能够成功接收，那么就不需要再发送下一次。前述的重试策略仅是几种具体举例而已，并不限定本方案中重试策略的所有实现方式。能够想到的任何其他合理的策略均可作为本方案中的重试策略。
步骤11，IM AS将消息转发到IP-SM-GW；
步骤12，IM AS将消息转发到IP-SM-GW后，IP-SM-GW返回响应结果；其中，消息需要转短信时的组网图如图5所示，图5中的SMS指的是简单消息服务(Simple Message Service)，IM指的是即时消息(Instant Message)；IM AS根据响应结果判断IP-SM-GW是否接收消息成功；如果接收成功则执行步骤13，如果接收信息失败，则执行步骤9.b；
步骤13，如果IP-SM-GW接收消息成功则返回SIP 200 OK的响应码，IM AS根据IP-SM-GW返回的SIP 200 OK响应码，检查IM AS的消息会话区中记录的该消息的会话记录中是否有forward-delivery的回执请求，如果有，则构造状态为<forwarded/>的回执消息发送给消息发送终端；如果没有，则流程结束；
具体的，按照消息回执标准状态和流程，现有技术中消息转短信后的状态无法通知到消息发送终端，消息发送终端无法获知消息最终是否转短信的状态，本发明实施例中，通过扩展消息回执的请求类型，并由RCS业务平台、具体是RCS业务平台中的IM AS对回执请求进行判断，对于转短信或者转短信链接的消息由RCS业务平台、具体是RCS业务平台中的IM AS进行消息回执处理，可以将消息处理状态通知到消息发送终端；消息接收终端对转短信回执请求无感知，接收到IP-SM-GW发送的消息后正常处理即可。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根 据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例3
在本实施例中还提供了一种消息回执的处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的消息回执的处理装置的结构框图，如图6所示，该装置包括：第一发送模块22、第一获取模块24、第一确定模块26和第二发送模块28，并且该装置应用于RCS业务平台的IM AS，下面对该装置进行详细说明：第一发送模块22，配置为向消息接收终端发送消息；第一获取模块24，配置为获取消息接收终端接收消息后产生的第一响应信息；第一确定模块26，配置为根据第一响应信息确定消息接收终端是否成功接收消息；第二发送模块28，配置为在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
在一种可选的实施例中，装置还包括：接收模块，配置为在第一发送模块22向消息接收终端发送消息之前，接收消息发送终端发送的初始消息，其中，初始消息中携带有初始消息的回执请求；触发模块，配置为根据接收到的初始消息触发向消息接收终端发送消息的消息下发流程；触发模块 包括：记录模块，配置为记录回执请求的类型，其中，类型包括：投递成功类型、投递失败类型和转短信投递类型；以及删除模块，配置为删除初始消息中与初始消息的回执请求的类型对应的字段信息，生成消息。
在一种可选的实施例中，装置还包括：第二确定模块，配置为在删除模块生成消息之后，根据消息接收终端的状态确定是否将消息转化为短信；第三发送模块，配置为在确定将消息转化为短信的情况下，将消息发送给IP短消息网关；第一调用模块，配置为在确定不将消息转化为短信的情况下，调用第一发送模块向消息接收终端发送消息。
在一种可选的实施例中，第二发送模块包括：第三确定模块，配置为在消息接收终端成功接收消息的情况下，确定即时消息应用服务器中是否记录有投递成功类型的回执请求；第四发送模块，配置为在即时消息应用服务器中记录有投递成功类型的回执请求的情况下，向消息发送终端发送第一回执消息。
在一种可选的实施例中，装置还包括：第四确定模块，配置为在第一确定模块根据第一响应信息确定消息接收终端是否成功接收消息之后，在消息接收终端未成功接收消息的情况下，确定第一响应信息是否为预设失败响应信息；第五确定模块，配置为在第一响应信息是预设失败响应信息的情况下，确定即时消息应用服务器中是否记录有投递失败类型的回执请求；第五发送模块，配置为在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，向消息发送终端发送第二回执消息。
在一种可选的实施例中，装置还包括：第六确定模块，配置为在第四确定模块确定第一响应信息是否为预设失败响应信息之后，在第一响应信息不是预设失败响应信息的情况下，确定是否将信息转化为短信；第二调用模块，配置为在确定将信息转化为短信的情况下，调用第三发送模块将消息发送给IP短消息网关；离线模块，配置为在确定不将信息转化为短信 的情况下，将消息存为离线消息并重新向消息接收终端发送消息。
在一种可选的实施例中，装置还包括：第二获取模块，配置为在第三发送模块将消息发送给IP短消息网关之后，获取IP短消息网关接收消息后产生的第二响应信息；第七确定模块，配置为根据第二响应信息确定IP短消息网关是否成功接收消息；第八确定模块，配置为在IP短消息网关成功接收消息的情况下，确定即时消息应用服务器中是否记录有转短信投递类型的回执请求；第六发送模块，配置为在即时消息应用服务器中记录有转短信投递类型的回执请求的情况下，向消息发送终端发送第三回执消息。
在一种可选的实施例中，装置还包括：第三调用模块，配置为在第七确定模块根据第二响应信息确定IP短消息网关是否成功接收消息之后，在IP短消息网关未成功接收消息的情况下，调用第五确定模块确定即时消息应用服务器中是否记录有投递失败类型的回执请求，以及在即时消息应用服务器中记录有投递失败类型的回执请求的情况下，调用第五发送模块向消息发送终端发送第二回执消息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例4
本发明的实施例还提供了一种存储介质，该存储介质包括存储的程序，其中，上述程序运行时执行上述方法。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
向消息接收终端发送消息；
获取消息接收终端接收消息后产生的第一响应信息；
根据第一响应信息确定消息接收终端是否成功接收消息；
在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
实施例5
本发明的实施例还提供了一种处理器，该处理器用于运行程序，其中，该程序运行时执行上述方法中的步骤。
可选地，在本实施例中，上述程序用于执行以下步骤：
向消息接收终端发送消息；
获取消息接收终端接收消息后产生的第一响应信息；
根据第一响应信息确定消息接收终端是否成功接收消息；
在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
实施例6
本发明的实施例还提供了一种电子装置，该电子装置包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，处理器通过计算机程序执行上述方法。
可选地，在本实施例中，上述程序用于执行以下步骤：
向消息接收终端发送消息；
获取消息接收终端接收消息后产生的第一响应信息；
根据第一响应信息确定消息接收终端是否成功接收消息；
在消息接收终端成功接收消息的情况下，向消息发送终端发送第一回执消息。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
本发明实施例中，由于融合通信业务平台的即时消息应用服务器在消息接收终端成功接收消息时，向消息发送终端发送第一回执消息，因此，可以解决现有技术中消息成功投递的回执消息需要由消息接收终端处理而造成的耗费消息接收终端流量和处理资源的问题，进而达到了节省消息接收终端流量和处理资源的效果。

Claims (19)

  1. 一种消息回执的处理方法，应用于融合通信业务平台的即时消息应用服务器，包括：
    向消息接收终端发送消息；
    获取所述消息接收终端接收所述消息后产生的第一响应信息；
    根据所述第一响应信息确定所述消息接收终端是否成功接收所述消息；
    在所述消息接收终端成功接收所述消息的情况下，向消息发送终端发送第一回执消息。
  2. 根据权利要求1所述的方法，其中，向消息接收终端发送消息之前，所述方法还包括：
    接收所述消息发送终端发送的初始消息，其中，所述初始消息中携带有所述初始消息的回执请求；
    根据接收到的所述初始消息触发向所述消息接收终端发送所述消息的消息下发流程；
    其中，根据接收到的所述消息触发向所述消息接收终端发送所述消息的消息下发流程，包括：
    记录所述回执请求的类型，其中，所述类型包括：投递成功类型、投递失败类型和转短信投递类型；以及
    删除所述初始消息中与所述初始消息的回执请求的类型对应的字段信息，生成所述消息。
  3. 根据权利要求2所述的方法，其中，生成所述消息之后，所述方法还包括：
    根据所述消息接收终端的状态确定是否将所述消息转化为短信；
    在确定将所述消息转化为短信的情况下，将所述消息发送给网际协议 IP短消息网关；
    在确定不将所述消息转化为短信的情况下，向所述消息接收终端发送所述消息。
  4. 根据权利要求2或3所述的方法，其中，在所述消息接收终端成功接收所述消息的情况下，向消息发送终端发送第一回执消息，包括：
    在所述消息接收终端成功接收所述消息的情况下，确定所述即时消息应用服务器中是否记录有所述投递成功类型的回执请求；
    在所述即时消息应用服务器中记录有所述投递成功类型的回执请求的情况下，向所述消息发送终端发送所述第一回执消息。
  5. 根据权利要求2所述的方法，其中，根据所述第一响应信息确定所述消息接收终端是否成功接收所述消息之后，所述方法还包括：
    在所述消息接收终端未成功接收所述消息的情况下，确定所述第一响应信息是否为预设失败响应信息；
    在所述第一响应信息是预设失败响应信息的情况下，确定所述即时消息应用服务器中是否记录有所述投递失败类型的回执请求；
    在所述即时消息应用服务器中记录有所述投递失败类型的回执请求的情况下，向所述消息发送终端发送第二回执消息。
  6. 根据权利要求5所述的方法，其中，确定所述第一响应信息是否为预设失败响应信息之后，所述方法包括：
    在所述第一响应信息不是预设失败响应信息的情况下，确定是否将所述信息转化为短信；
    在确定将所述信息转化为短信的情况下，将所述消息发送给IP短消息网关；
    在确定不将所述信息转化为短信的情况下，将所述消息存为离线消息并重新向所述消息接收终端发送所述消息。
  7. 根据权利要求3或6所述的方法，其中，将所述消息发送给IP短消息网关之后，所述方法还包括：
    获取所述IP短消息网关接收所述消息后产生的第二响应信息；
    根据所述第二响应信息确定所述IP短消息网关是否成功接收所述消息；
    在所述IP短消息网关成功接收所述消息的情况下，确定所述即时消息应用服务器中是否记录有所述转短信投递类型的回执请求；
    在所述即时消息应用服务器中记录有所述转短信投递类型的回执请求的情况下，向所述消息发送终端发送第三回执消息。
  8. 根据权利要求7所述的方法，其中，根据所述第二响应信息确定所述IP短消息网关是否成功接收所述消息之后，所述方法还包括：
    在所述IP短消息网关未成功接收所述消息的情况下，确定所述即时消息应用服务器中是否记录有所述投递失败类型的回执请求；
    在所述即时消息应用服务器中记录有所述投递失败类型的回执请求的情况下，向所述消息发送终端发送第二回执消息。
  9. 一种消息回执的处理装置，应用于融合通信业务平台的即时消息应用服务器，包括：
    第一发送模块，配置为向消息接收终端发送消息；
    第一获取模块，配置为获取所述消息接收终端接收所述消息后产生的第一响应信息；
    第一确定模块，配置为根据所述第一响应信息确定所述消息接收终端是否成功接收所述消息；
    第二发送模块，配置为在所述消息接收终端成功接收所述消息的情况下，向消息发送终端发送第一回执消息。
  10. 根据权利要求9所述的装置，其中，所述装置还包括：
    接收模块，配置为在所述第一发送模块向所述消息接收终端发送所述消息之前，接收所述消息发送终端发送的初始消息，其中，所述初始消息中携带有所述初始消息的回执请求；
    触发模块，配置为根据接收到的所述初始消息触发向所述消息接收终端发送所述消息的消息下发流程；
    所述触发模块包括：
    记录模块，配置为记录所述回执请求的类型，其中，所述类型至少包括：投递成功类型、投递失败类型和转短信投递类型；以及
    删除模块，配置为删除所述初始消息中与所述初始消息的回执请求的类型对应的字段信息，生成所述消息。
  11. 根据权利要求10所述的装置，其中，所述装置还包括：
    第二确定模块，配置为在所述删除子模块生成所述消息之后，根据所述消息接收终端的状态确定是否将所述消息转化为短信；
    第三发送模块，配置为在确定将所述消息转化为短信的情况下，将所述消息发送给IP短消息网关；
    第一调用模块，配置为在确定不将所述消息转化为短信的情况下，调用所述第一发送模块向所述消息接收终端发送所述消息。
  12. 根据权利要求10或11所述的装置，其中，所述第二发送模块包括：
    第三确定模块，配置为在所述消息接收终端成功接收所述消息的情况下，确定所述即时消息应用服务器中是否记录有所述投递成功类型的回执请求；
    第四发送模块，配置为在所述即时消息应用服务器中记录有所述投递成功类型的回执请求的情况下，向所述消息发送终端发送所述第一回执消息。
  13. 根据权利要求11所述的装置，其中，所述装置还包括：
    第四确定模块，配置为在所述第一确定模块根据所述第一响应信息确定所述消息接收终端是否成功接收所述消息之后，在所述消息接收终端未成功接收所述消息的情况下，确定所述第一响应信息是否为预设失败响应信息；
    第五确定模块，配置为在所述第一响应信息是预设失败响应信息的情况下，确定所述即时消息应用服务器中是否记录有所述投递失败类型的回执请求；
    第五发送模块，配置为在所述即时消息应用服务器中记录有所述投递失败类型的回执请求的情况下，向所述消息发送终端发送第二回执消息。
  14. 根据权利要求13所述的装置，其中，所述装置还包括：
    第六确定模块，配置为在所述第四确定模块确定所述第一响应信息是否为预设失败响应信息之后，在所述第一响应信息不是预设失败响应信息的情况下，确定是否将所述信息转化为短信；
    第二调用模块，配置为在确定将所述信息转化为短信的情况下，调用所述第三发送模块将所述消息发送给网际协议IP短消息网关；
    离线模块，配置为在确定不将所述信息转化为短信的情况下，将所述消息存为离线消息并重新向所述消息接收终端发送所述消息。
  15. 根据权利要求14所述的装置，其中，所述装置还包括：
    第二获取模块，配置为在所述第三发送模块将所述消息发送给IP短消息网关之后，获取所述IP短消息网关接收所述消息后产生的第二响应信息；
    第七确定模块，配置为根据所述第二响应信息确定所述IP短消息网关是否成功接收所述消息；
    第八确定模块，配置为在所述IP短消息网关成功接收所述消息的情况下，确定所述即时消息应用服务器中是否记录有所述转短信投递类型的回 执请求；
    第六发送模块，配置为在所述即时消息应用服务器中记录有所述转短信投递类型的回执请求的情况下，向所述消息发送终端发送第三回执消息。
  16. 根据权利要求15所述的装置，其中，所述装置还包括：
    第三调用模块，配置为在所述第七确定模块根据所述第二响应信息确定所述IP短消息网关是否成功接收所述消息之后，在所述IP短消息网关未成功接收所述消息的情况下，调用所述第五确定模块确定所述即时消息应用服务器中是否记录有所述投递失败类型的回执请求，以及在所述即时消息应用服务器中记录有所述投递失败类型的回执请求的情况下，调用所述第五发送模块向所述消息发送终端发送第二回执消息。
  17. 一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至8中任一项所述的方法。
  18. 一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至8中任一项所述的方法。
  19. 一种电子装置，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器通过所述计算机程序执行所述权利要求1至8中任一项所述的方法。
PCT/CN2018/087799 2017-05-25 2018-05-22 消息回执的处理方法、相关装置、存储介质和处理器 WO2018214865A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710380009.3 2017-05-25
CN201710380009.3A CN108933727B (zh) 2017-05-25 2017-05-25 消息回执的处理方法和装置

Publications (1)

Publication Number Publication Date
WO2018214865A1 true WO2018214865A1 (zh) 2018-11-29

Family

ID=64396226

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087799 WO2018214865A1 (zh) 2017-05-25 2018-05-22 消息回执的处理方法、相关装置、存储介质和处理器

Country Status (2)

Country Link
CN (1) CN108933727B (zh)
WO (1) WO2018214865A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006880A (zh) * 2021-10-25 2022-02-01 北京有竹居网络技术有限公司 一种消息回执的获取方法、装置、电子设备和存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111314202A (zh) * 2018-12-11 2020-06-19 中兴通讯股份有限公司 消息发送方法和装置
CN110457342B (zh) * 2019-07-02 2023-01-06 网联清算有限公司 交易处理方法及装置
CN110557752B (zh) * 2019-07-19 2021-01-22 珠海格力电器股份有限公司 一种信息保护方法、信息保护装置、电子设备和计算机可读介质
CN112449313A (zh) * 2019-08-30 2021-03-05 普天信息技术有限公司 宽带集群系统中彩信业务附件下载确认方法及装置
CN111107503A (zh) * 2019-12-30 2020-05-05 珠海市小源科技有限公司 融合通信消息即平台业务的短信回落方法、设备及系统
CN112187629B (zh) * 2020-10-20 2022-04-29 珠海市小源科技有限公司 5g通信的消息撤回方法、计算机装置及计算机可读存储介质
CN113242172B (zh) * 2021-04-26 2023-02-28 福建天泉教育科技有限公司 一种消息的应答方法及系统
CN115277614A (zh) * 2021-04-29 2022-11-01 成都鼎桥通信技术有限公司 消息处理的方法、设备、存储介质及程序产品
CN113746721B (zh) * 2021-08-02 2022-11-29 咪咕音乐有限公司 邮件处理方法、服务器及存储介质
CN113840245B (zh) * 2021-11-16 2023-03-31 中国电信股份有限公司 用于rcs消息的通信方法和通信系统
CN115334466B (zh) * 2022-08-15 2023-08-04 北京泰镝科技股份有限公司 一种消息的发送方法、装置、电子设备及存储介质
CN115658337B (zh) * 2022-10-14 2023-07-11 广州市玄武无线科技股份有限公司 一种消息全生命周期处理方法及分布式消息系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6978293B1 (en) * 2000-02-29 2005-12-20 Microsoft Corporation Methods and systems for selecting criteria for a successful acknowledgement message in instant messaging
CN101179520A (zh) * 2006-12-28 2008-05-14 腾讯科技（深圳）有限公司 一种感知邮件状态的方法及系统
CN101360278A (zh) * 2008-09-17 2009-02-04 华为技术有限公司 一种即时消息收发的方法、系统和设备
CN101971584A (zh) * 2008-02-06 2011-02-09 高通股份有限公司 用于消息的递送确认的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6978293B1 (en) * 2000-02-29 2005-12-20 Microsoft Corporation Methods and systems for selecting criteria for a successful acknowledgement message in instant messaging
CN101179520A (zh) * 2006-12-28 2008-05-14 腾讯科技（深圳）有限公司 一种感知邮件状态的方法及系统
CN101971584A (zh) * 2008-02-06 2011-02-09 高通股份有限公司 用于消息的递送确认的方法和设备
CN101360278A (zh) * 2008-09-17 2009-02-04 华为技术有限公司 一种即时消息收发的方法、系统和设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006880A (zh) * 2021-10-25 2022-02-01 北京有竹居网络技术有限公司 一种消息回执的获取方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN108933727B (zh) 2022-09-27
CN108933727A (zh) 2018-12-04

Similar Documents

Publication Publication Date Title
WO2018214865A1 (zh) 消息回执的处理方法、相关装置、存储介质和处理器
JP4884924B2 (ja) 端末機とそのメッセージ処理方法
EP2304907B1 (en) A message delivery mechanism
RU2431944C2 (ru) Способ доставки сообщений в системе связи
US9384471B2 (en) Spam reporting and management in a communication network
US10419371B2 (en) Methods and systems for delayed notifications in communications networks
JP5666020B2 (ja) パケット交換ネットワークを介してアプリケーション発信テキスト・メッセージを配送するための方法および装置
US20090030917A1 (en) Multimedia messaging service-based database synchronization
KR20140066765A (ko) 문자 메시지들에 대한 보관 제어
JP4923155B2 (ja) コンテンツの送受信の停止及び再開方法
CN103929730A (zh) 触发消息发送的方法、设备及系统
WO2011137830A1 (zh) 一种业务分发平台消息推送方法、相关设备及系统
RU2608469C2 (ru) Способ и устройство высокоэффективной доставки уведомлений в реальном времени с малым временем задержки
US20120155459A1 (en) Converged messaging across legacy and ip domains
EP2160051A1 (en) Methods and devices for messaging
EP3664384A1 (en) Network message fallback and deduplication
US9456325B2 (en) Transmission of a multimedia message doubled with the transmission of a text message
WO2015103604A1 (en) Techniques for a device trigger recall/replace procedure
WO2012173752A1 (en) Interface between restful web services and packet-switched networks for text messaging
US10063648B2 (en) Relaying mobile communications
CN101374254A (zh) 通信系统中传送报告的方法及设备
WO2011140904A1 (zh) 一种消息处理方法、装置和应用服务器
WO2012167473A1 (zh) 消息状态设置方法和cpm业务服务器
US20140378103A1 (en) Archiving a delivery status for a text message
WO2012022074A1 (zh) 用户信息的查询方法及多媒体消息中心

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18805772

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18805772

Country of ref document: EP

Kind code of ref document: A1