WO2011023089A1 - 传递及接收Push消息的方法和设备 - Google Patents

传递及接收Push消息的方法和设备 Download PDF

Info

Publication number
WO2011023089A1
WO2011023089A1 PCT/CN2010/076251 CN2010076251W WO2011023089A1 WO 2011023089 A1 WO2011023089 A1 WO 2011023089A1 CN 2010076251 W CN2010076251 W CN 2010076251W WO 2011023089 A1 WO2011023089 A1 WO 2011023089A1
Authority
WO
WIPO (PCT)
Prior art keywords
push
push message
terminal
message
server
Prior art date
Application number
PCT/CN2010/076251
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 华为终端有限公司
Priority to EP10811249.1A priority Critical patent/EP2472776B1/en
Priority to ES10811249.1T priority patent/ES2617188T3/es
Publication of WO2011023089A1 publication Critical patent/WO2011023089A1/zh
Priority to US13/404,910 priority patent/US20120147887A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1859Arrangements for providing special services to substations for broadcast or conference, e.g. multicast adapted to provide push services, e.g. data channels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1863Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1868Measures taken after transmission, e.g. acknowledgments

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and device for transmitting and receiving Push messages. Background technique
  • Push is a content distribution mechanism that uses the client/server mode to work.
  • the Push Initiator PI
  • the Push server sends the Push content to the terminal according to the delivery instruction, wherein the Push server uses the Push Access Protocol (PAP) to obtain the message from the Push message initiator, and then passes the Push Air Protocol (Over The Air, 0TA). ) Send the content to the terminal.
  • PAP Push Access Protocol
  • Push messages can be sent point-to-point or by point-to-multipoint.
  • the terminal may return an acknowledgement message to the Push server, indicating that the Push message is received, and the Push server returns a delivery report to the Push message initiator according to the confirmation message.
  • the Push server needs to repeatedly send the same Push message, which will cause a burden on the bearer network. Therefore, it is necessary to simultaneously send a Push message to a plurality of terminals in a point-to-multipoint manner.
  • the inventor has found that in the process of sending a Push message from a point-to-multipoint, if the Push server transmits a Push message by broadcast or multicast, the target terminal cannot be known in advance due to the Push message, or There is no uplink channel available to return the receive response, making the Push server unable to know the delivery of the Push message. Summary of the invention
  • the embodiment of the invention provides a method and a device for transmitting and receiving an Push message.
  • the Push message can be informed of the delivery of the Push message when the Push server transmits the Push message in a broadcast or multicast manner.
  • Receiving a Push message where the Push message carries an indication of a statistical delivery result; Determining, according to the Push message, transmitting the Push message to the terminal by using a broadcast or multicast manner; and obtaining the delivery report according to the indication of the statistical delivery result.
  • the embodiment of the present invention provides a Push server, including:
  • a receiving unit configured to receive a Push message, where the Push message carries an indication of a statistical delivery result
  • the delivery mode determining unit is configured to determine, according to the Push message, that the Push message is delivered to the terminal by using a broadcast or multicast manner
  • a report obtaining unit configured to obtain a delivery report according to an indication of a statistical delivery result.
  • a terminal including:
  • a receiving unit configured to receive a Push message that is transmitted by the Push server by using a broadcast or a multicast mode, where the Push message carries an indication of returning a response
  • a response returning unit is configured to: according to the indication of returning the received response, to the The Push server returns a response message or establishes a connection with the server.
  • the Push server when the Push server delivers the Push message to the terminal in a broadcast or multicast manner, the Push message carries an indication of the statistical delivery result in the Push message, and the Push server according to the The acquisition delivery report is instructed, so that the delivery of the Push message can be known in the case of transmitting a Push message in a broadcast or multicast manner.
  • FIG. 1 is a flowchart of a method for transmitting an Push message according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for receiving an Push message according to an embodiment of the present invention
  • FIG. 3 is a functional composition diagram of a Push server according to an embodiment of the present invention.
  • FIG. 4 is a second structural diagram of a Push server according to an embodiment of the present invention.
  • FIG. 5 is a functional composition diagram of a terminal according to an embodiment of the present invention
  • FIG. 6 is a second functional diagram of a terminal according to an embodiment of the present invention
  • FIG. 5 is a functional composition diagram of a terminal according to an embodiment of the present invention
  • FIG. 6 is a second functional diagram of a terminal according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a system for transmitting an Push message according to an embodiment of the present invention.
  • Figure 8 is a detailed flow diagram of an embodiment of a method of practicing the present invention. detailed description
  • a method for transmitting an Push message includes:
  • Step 11 Receive a Push message, where the Push message carries an indication of a statistical delivery result
  • the Push server receives the Push message, and the Push message carries an indication of a statistical delivery result.
  • the indication of the result of the statistical delivery is given in the Push message, for example, an indication is given in the Push message parameter, and an implementation example giving an indication in the Quality of Service (QoS) parameter is given as follows:
  • Receiver-Address string can be broadcast, multicast address type
  • Deliver-Report string list Instructs the Push server to count the corresponding delivery results.
  • Deliver-Report Values string list The value of the delivery report type, for example, "number of delivery", indicating statistics
  • the number of Push messages to be sent to the target terminal "Number of Successful Receives”, indicating the number of terminals that successfully counted this Push message. "Number of failures”, indicating the number of terminals that this Push message could not receive or did not send successfully. "Number of rejections”, indicating the number of terminals that this Push message refuses to receive, and so on.
  • the Push server determines the type of delivery result that needs to be counted according to the Del ivery-R print ort indication information in the Push message.
  • the Push server may be a Push Proxy Gateway (PPG) in a point-to-multipoint messaging system, and the Push message is sent by a Push Message Initiator (PI) to a Push Proxy Gateway (PPG), where The indication of the delivery result may be information carried by the PI in the Push message sent to the PPG for requesting the result notification.
  • PPG Push Proxy Gateway
  • PI Push Message Initiator
  • PPG Push Proxy Gateway
  • Step 12 Determine, according to the Push message, that the Push message is delivered by means of broadcast or multicast;
  • the Push server determines, according to the Push message, that the Push message is delivered by means of broadcast or multicast.
  • the Push message initiator may instruct the Push server to send a Push message by means of broadcast or multicast according to the address type in the instruction, or the Push server may The self-determination sends a Push message by means of broadcast or multicast.
  • Step 13 Acquire the delivery report according to the indication of the statistical delivery result.
  • the Push server obtains the delivery report according to the indication of the statistical delivery result, and the obtaining the delivery report according to the indication of the statistical delivery result includes: obtaining a delivery report of all delivery result types, or obtaining only the delivery report of the indicated delivery result type;
  • the Push server can obtain the delivery report by querying the group management server through the following methods: or obtaining the delivery report by receiving the receiving response returned by the terminal; or obtaining the delivery report by querying the number of connections established between the terminal and the server.
  • the Push server can determine the number of the target terminal by sending the Push message to the target terminal.
  • the address information of the target terminal may be obtained before the Push message is sent, and the number of the Push address to be sent to the target terminal is obtained from the number of the target address terminals; and the Push server may Obtaining, according to the number of sent Push messages, or the number of transmissions by the bearer network, the number of actual delivery of the Push message, and obtaining the connection response returned by the receiving terminal or establishing a connection between the terminal and the server. The number of successful Push messages received.
  • the Push server can also obtain the number of users joining the multicast group by querying the bearer network server before sending the Push message; or by collecting the key, access parameters, subscription process, service statement, and return confirmation to join the group. The number of messages, etc., to count the number of terminals receiving the Push message.
  • the terminal judges the Push message delivered by the Push server, and if it carries an indication of returning the response, returns a response to the Push server.
  • the types of responses received include: successful receive response, failed receive response, reject receive response, process response, disable retransmission response, and more.
  • the Push server can calculate the delivery report of the Push message according to the result obtained by the query group management server or according to the receiving response returned by the terminal or the terminal establishing a connection with the server. For the same Push message identifier, the number of statistics is classified and stored, for example, the number of successful Push messages, the number of Push messages failed, and the like.
  • the Push server may actively return a delivery report to the Push message originator, or may return a delivery report to the Push message initiator according to the request delivery report message sent by the Push message initiator, and the return delivery report includes: Returns a delivery report of all delivery result types, or only a delivery report of the requested delivery result type.
  • the Push server can also send a request message for querying a delivery report according to other servers. The Push server determines whether to return the result of the request to other servers according to the return policy, and if so, returns the query result that can be returned.
  • the Push server may transmit the Push message to the terminal in the case that the Push message is transmitted to the terminal by using broadcast or multicast, and the terminal is instructed to return the Receive Response message, but the terminal does not have an uplink channel available to return the received response. And carrying an indication of the bearer mode, so that the terminal returns a receiving response by using the indicated bearer mode.
  • the indicated bearer mode may be one or more types, and it is determined by the terminal to select one of the return receiving responses.
  • the indication information may be carried in the Push message sent to the terminal, for example, in the QoS parameter, or by extending the header field, the value field or the message body of the Push message, and carrying the bearer mode identifier used by the terminal to return the response.
  • the receiving address information and/or the Push message identification information of the return receiving response may be further given, for example, indicating that the receiving response is returned by SMS, Emai l, HTTP, WSP, and SIP signaling.
  • the terminal parses the identifier of the indication bearer mode, activates the corresponding application, and returns the receiving response by using the indicated bearer mode, so that the terminal can still ensure that the terminal returns the receiving response in the case that the terminal has no uplink channel available.
  • An example is given below:
  • Push ID string message message message identifier Receiver-Address string can be broadcast, multicast address type
  • the Report-Return-Method string list indicates the loading mode used by the terminal.
  • SMS, Email, HTTP, WSP, SIP signaling messages return a response.
  • the terminal can also return the receiving response by default.
  • the Push message initiator may also carry a statistical indication in the Push message, so that the Push server performs statistics on the delivery report according to the statistical manner indicated in the Push message.
  • the Push server returns the statistics to the Push message initiator by extending the message header field, the value field, or the message body of the report, so that the Push message initiator can receive the detailed delivery result classification, which is better for the user. Experience.
  • the statistics can be placed in the header of the delivery report.
  • the Push server carries the following statistics in the header of the delivery report returned to the initiator of the Push message:
  • the number of Number can be the number of Push messages sent to the terminal by the Push server, or the number of received responses returned by the terminal.
  • Successful-Number is the number of terminals that successfully receive the Push message.
  • Rejected-Number can also be included to indicate the number of terminals that are refused to receive, Pending - Number indicates the number of terminals being processed, and Undel iverable Number indicates the number of terminals that cannot be delivered.
  • the Push server can also encapsulate the statistical result in the message body of the delivery report, and return it in the following manner.
  • Report status number address information
  • the Push message initiator After receiving the delivery report, the Push message initiator returns a reception response to the Push server.
  • the terminal that returns the receiving response does not return the receiving response or the terminal that returns the failure response may alternatively report the address information of the terminal to the Push message initiator, and the Push message initiator may use the information. Determining whether it is necessary to send the Push message to the terminal that has not successfully received the Push message, and further instructing the Push server to transmit the Push message again in a unicast, multicast, or broadcast manner, or the Push server itself determines whether to unicast, multicast, or according to the terminal address information. The broadcast mode transmits the Push message again, thereby increasing the success rate of the delivery.
  • the method for transmitting a Push message is provided by the embodiment of the present invention.
  • the Push server delivers the Push message to the terminal in a broadcast or multicast manner
  • the Push message carries an indication of the statistical delivery result in the Push message
  • the Push server is instructed to obtain the Push message.
  • the report is delivered, so that the Push server can still know the delivery status of the Push message in the case of broadcast or multicast.
  • a method for receiving an Push message includes:
  • Step 21 Receive a Push message that is sent by the Push server in a broadcast or multicast manner, where the Push message carries an indication of returning a response to receive;
  • the terminal receives the Push message that is transmitted by the Push server in a broadcast or multicast manner, and the Push message carries an indication of returning a response, and the indication of the return receiving response may be given in a QoS parameter in the Push message, for example, Adding a Response-R label to the QoS parameter indicates that the terminal needs to return a receiving response to the Push server.
  • Step 22 Return a receiving response or service to the Push server according to the indication of returning a response to receive Establish a connection.
  • the terminal receives the Push message, and determines the received Push message. If the indication of returning the receiving response is carried, the terminal returns a receiving response to the Push server.
  • the types of responses received include: Successful Receive Response, Receive Receive Response, Reject Receive Response, Processing Response, Disable Retransmission Response, and so on.
  • the Push server collects the delivery report of the Push message according to the receiving response returned by the terminal or the connection between the terminal and the server, so that the Push server can still know the delivery status of the Push message when the Push message is transmitted by broadcast or multicast. .
  • the Push server may transmit the Push message to the terminal in the case that the Push message is transmitted to the terminal by using broadcast or multicast, and the terminal is instructed to return the Receive Response message, but the terminal does not have an uplink channel available to return the received response. And carrying the indication of the bearer mode, so that the terminal activates the corresponding application according to the indication of the bearer mode, and returns a receiving response to the Push server by using the indicated bearer mode.
  • the indicated bearer mode may be one or more types, and it is determined by the terminal to select one of the return receiving responses.
  • the indication information may be carried in the Push message sent to the terminal, for example, in the QoS parameter, or by extending the header field, the value field or the message body of the Push message, and carrying the bearer mode identifier used by the terminal to return the response.
  • the receiving address information and/or the Push message indication information of the return receiving response may be further given, for example, indicating that the receiving response is returned by SMS, Emai l, HTTP, WSP, SIP signaling.
  • the terminal parses the identifier of the indication bearer mode, activates the corresponding application, and returns the receiving response by using the indicated bearer mode, so that the terminal can still ensure that the terminal returns the receiving response in the case that the terminal has no uplink channel available.
  • the terminal can also return the receiving response by default.
  • the method for receiving a Push message provided by the embodiment of the present invention, when the Push server transmits a Push message to the terminal in a broadcast or multicast manner, by instructing the terminal to return a receiving response by carrying an indication of returning the received response in the Push message,
  • the Push server is configured to count the delivery report of the Push message according to the receiving response returned by the terminal or the terminal establishing a connection with the server.
  • an embodiment of the present invention provides a Push server, including:
  • the receiving unit 31 is configured to receive a Push message, where the Push message carries an indication of a statistical delivery result, and the delivery mode determining unit 32 is configured to determine, according to the Push message, that the Push message is delivered to the terminal by using a broadcast or multicast manner. ;
  • the delivery report obtaining unit 33 is configured to obtain the delivery report according to the indication of the statistical delivery result.
  • the obtaining the delivery report according to the indication of the statistical delivery result includes: obtaining a delivery report of all delivery result types, or obtaining only the delivery report of the indicated delivery result type;
  • the report obtaining unit 33 includes at least one of the following modules:
  • a first obtaining module configured to obtain a delivery report by querying the group management server
  • a second obtaining module configured to obtain a delivery report by receiving a response returned by the terminal
  • the third obtaining module is configured to obtain a delivery report by querying the number of connections established between the terminal and the server.
  • the Push server may actively return a delivery report to the Push message originator, or may return a delivery report to the Push message initiator according to the request delivery report message sent by the Push message initiator, and the return delivery report includes: Returns a delivery report of all delivery result types, or only a delivery report of the requested delivery result type.
  • the Push server can also send a request message for querying a delivery report according to other servers. The Push server determines whether to return the result of the request to other servers according to the return policy, and if so, returns the query result that can be returned.
  • the Push server may be a Push Proxy Gateway (PPG) in a point-to-multipoint messaging system, and the Push message received by the PPG is from a Push Message Initiator (PI) to a Push Proxy Gateway (PPG). send.
  • PPG Push Proxy Gateway
  • PI Push Message Initiator
  • PPG Push Proxy Gateway
  • the Push server 3 provided in this embodiment further includes a delivery report returning unit 34, and the delivery report returning unit includes at least one of the following modules:
  • An active return module configured to actively return the delivery report to a Push message initiator
  • a request returning module configured to return the delivery report to the Push message initiator according to the message of the request delivery report sent by the Push message initiator;
  • the policy returning module is configured to: if it is a message sent by the server other than the initiator of the Push message, to determine whether to return the delivery report of the request according to the return policy.
  • the Push server further includes:
  • the bearer mode indicating unit 35 is configured to carry the indication of the bearer mode in the Push message that is delivered to the terminal, so that the terminal activates the corresponding application according to the indication of the bearer mode, and uses the indicated bearer mode to return Receive response. Therefore, in the case that the terminal does not have an uplink channel available, the terminal can still ensure that the terminal returns a reception response.
  • the Push message initiator also carries an indication of the returning report statistics mode in the Push message.
  • the Push server further includes:
  • the statistic unit 36 is configured to perform statistics on the delivery report according to the statistical manner indicated in the Push message.
  • the delivery report returning unit 34 is specifically configured to extend the message header field, the value field, or the message by using the delivery report. The way to return the statistics to the Push message initiator.
  • the Push message initiator can receive detailed delivery result classification, which brings a better experience for the user.
  • the Push server may send the Push message to the terminal again, thereby increasing the success rate of the delivery.
  • the Push server may further include:
  • the retransmission unit 37 is configured to, for the terminal that returns the receiving response and does not return the receiving response, or the terminal that returns the failure response, and then deliver the Push message to the terminal again according to the terminal address information.
  • the Push server provided by the embodiment of the present invention can be applied to Embodiment 1 of the foregoing method.
  • the delivery of the Push message can still be known.
  • an embodiment of the present invention provides a terminal, including:
  • the receiving unit 51 is configured to receive a Push message that is transmitted by the Push server by using a broadcast or a multicast mode, where the Push message carries an indication of returning a response to receive;
  • the response returning unit 52 is configured to return a receiving response to the Push server or establish a connection with the server according to the indication of the return receiving response.
  • the receiving unit 51 of the terminal receives the Push message, and determines the received Push message. If the indication of returning the receiving response is carried, the receiving response is returned to the Push server.
  • the types of responses received include: successful receive response, failed receive response, reject receive response, processing response, disable retransmission response, and so on.
  • the Push server calculates the delivery report of the Push message according to the receiving response returned by the terminal or the connection between the terminal and the server, so that the Push server can still know the delivery of the Push message when the Push message is transmitted by broadcast or multicast.
  • the Push server may carry the indication of the bearer mode in the Push message delivered to the terminal, so that the terminal activates the corresponding application according to the indication of the bearer mode, and uses the The bearer mode indicated returns a receiving response to the Push server, so that in the case that the terminal has no uplink channel available, the terminal can still ensure that the terminal returns a receiving response.
  • the terminal provided by the embodiment of the present invention further includes:
  • the application activation unit 53 is configured to activate the corresponding application according to the bearer mode indicated in the Push message.
  • the response returning unit 52 is specifically configured to return a receiving response to the Push server by using the indicated bearer mode. .
  • the terminal provided by the embodiment of the present invention can be applied to the second embodiment of the foregoing method, so that the Push server can still know the delivery status of the Push message when the Push message is transmitted in a broadcast or multicast manner.
  • an embodiment of the present invention provides a system for transmitting an Push message, including a Push message initiator 10, an Push server 20, and a plurality of terminals 30, where
  • the Push server 20 is configured to receive an instruction for transmitting a Push message sent by the initiator of the Push message, where the received Push message carries an indication of a statistical delivery result, and determines, according to the Push message, a manner of broadcasting or multicasting.
  • the terminal delivers the Push message; and obtains a delivery report according to the indication of the statistical delivery result.
  • the Push server 20 is configured to obtain a delivery report by querying the group management server; or obtain a delivery report by receiving a response returned by the receiving terminal; or obtain a delivery report by querying the number of connections established between the terminal and the server.
  • the delivery report of the acquisition includes: obtaining a delivery report of all delivery result types, or only obtaining a delivery report of the indicated delivery result type.
  • the Push server 20 is further configured to: actively return the delivery report to the Push message initiator; or return the delivery report to the Push message initiator according to the request message of the delivery report sent by the Push message initiator; Alternatively, if it is a request message for transmitting a report sent by a server other than the initiator of the Push message, it is determined according to the return policy whether to return a response and carry the delivery report of the request.
  • the returned delivery report includes: Returns a delivery report for all delivery result types, or only a delivery report for the requested delivery result type.
  • the Push server 20 is further configured to: carry the indication of the bearer mode in the Push message delivered to the terminal, so that the terminal activates the phase according to the indication of the bearer mode.
  • the application should return the received response using the indicated bearer mode.
  • the Push message initiator 10 carries an indication of the statistical mode in the Push message.
  • the Push server 20 is further configured to transmit according to the statistical manner indicated in the Push message.
  • the report performs statistics, and returns the statistical result to the Push message initiator by extending the message header field, the value field, or the message body of the delivery report.
  • a specific process step of implementing the method embodiment provided by the present invention includes:
  • Step 81 The initiator of the Push message sends an instruction to deliver the Push message to the Push server, instructing the Push server to deliver the Push message by means of broadcast or multicast.
  • the Push message carries an indication of a statistical delivery report, and may also carry an indication of the terminal bearer mode, and may also carry a statistical indication.
  • Step 82 The Push server returns a response message. This step is an optional step.
  • Step 83 The Push server delivers the Push message to the terminal by means of broadcast or multicast.
  • Step 84 The terminal determines whether it is necessary to return a receiving response to the received Push message, and further determines whether the used bearer mode is indicated. If there are multiple bearer modes, the terminal activates the corresponding application according to the network conditions, user preferences, settings, capabilities, etc., and selects a bearer mode to return the receiving response.
  • Step 85 After determining, the terminal returns a receiving response to the Push server by using the indicated bearer mode or the default bearer mode.
  • Step 86 After receiving the receiving response returned by the terminal, the Push server performs buffering and classifying statistics, such as the number of successful Push messages, the number of Push messages failed, and the like. If the Push message further carries an indication of the statistical mode, the Push server will perform statistics on the received response returned by the terminal according to the statistical manner of the indication.
  • Step 87 The Push server sends a delivery report to the initiator of the Push message according to the statistical result.
  • the statistical result may be because the delays of receiving the Push message or returning the received response are different. You can send the delivery report in batches, or you can wait for all the results to be counted and return the delivery report together. You can also set a time limit to send the delivery report. In this delivery report, the identifier of the Push message needs to be given, and the initiator of the Push message uses the identifier to identify the result of the delivery report as the reception result report of the Push message.
  • Step 88 After receiving the delivery report, the Push message initiator returns a response message to the Push server.
  • the Push message initiator may add a query request at any step to request the delivery of a Push message.
  • the method steps described in connection with the embodiments disclosed herein may be implemented in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of In the storage medium.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or any other form of In the storage medium.

Landscapes

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

Description

传递及接收 Push消息的方法和设备 本申请要求于 2009年 08月 24日提交中国专利局、 申请号为 200910163085. 4专利申 请名称为 "传递及接收 Push 消息的方法和设备" 的中国专利申请的优先权, 其全部内容 通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域, 具体而言是涉及一种传递及接收 Push消息的方法和设备。 背景技术
推送 (Push) 是一种内容分发机制, 采用客户 /服务器模式的工作方式, 要求服务器 不需要客户端发出具体请求, 就由 Push消息发起者 (Push Initiator, PI ) 向 Push服务 器推送信息和传递指令,再由 Push服务器根据传递指令将 Push内容发送到终端,其中 Push 服务器采用 Push 接入协议 (Push Access Protocol , PAP) 从 Push消息发起者上获取消 息, 再通过 Push空中协议 (Over The Air, 0TA) 将内容发送给终端。
Push消息可以通过点到点, 或通过点到多点的方式进行发送。 在点到点的 Push消息 发送过程中, 终端可以向 Push服务器返回确认消息, 表示接收到该 Push消息, Push服务 器根据此确认消息再向 Push消息发起者返回传递报告。当 Push消息的终端为多个设备时, 如果仍采用点到点的方式, 需要 Push服务器重复发送同一条 Push消息, 这样将造成承载 网络的负担。 因此, 需要通过点到多点的方式来同时发送 Push消息给多个终端。
在实现本发明过程中,发明人研究发现在点到多点的 Push消息发送过程中,如果 Push 服务器采用广播或组播方式传递 Push消息,由于 Push消息传递前无法预先获知目标终端, 或者由于终端没有可使用的上行信道来返回接收响应, 使得 Push服务器无法获知该 Push 消息的传递情况。 发明内容
本发明实施例提供一种传递及接收 Push消息的方法和设备, 在 Push服务器以广播或 组播方式传递 Push消息情况下能够获知 Push消息的传递情况。
本发明实施例提供的一种传递 Push消息的方法, 包括:
接收 Push消息, 所述 Push消息中携带有统计传递结果的指示; 根据所述 Push消息确定通过广播或组播方式向终端传递所述 Push消息; 根据统计传递结果的指示获取传递报告。
发明实施例提供的一种接收 Push消息的方法, 包括:
接收 Push服务器通过广播或组播方式传递的 Push消息, 所述 Push消息中携带有返 回接收响应的指示;
根据所述返回接收响应的指示, 向所述 Push 服务器返回接收响应消息或与服务器建 立连接。
相应于上述方法实施例, 本发明实施例提供了一种 Push服务器, 包括:
接收单元, 用于接收 Push消息, 所述 Push消息中携带有统计传递结果的指示; 传递 方式确定单元, 用于根据所述 Push消息确定通过广播或组播方式向终端传递所述 Push消 息; 传递报告获取单元, 用于根据统计传递结果的指示获取传递报告。
还提供了一种终端, 包括:
接收单元, 用于接收 Push服务器通过广播或组播方式传递的 Push消息, 所述 Push 消息中携带有返回接收响应的指示; 响应返回单元, 用于根据所述返回接收响应的指示, 向所述 Push服务器返回接收响应消息或与服务器建立连接。
由上述本发明实施例提供的技术方案可知, Push服务器在以广播或组播方式向终端传 递 Push消息时,通过 Push消息发起者在所述 Push消息中携带统计传递结果的指示, Push 服务器根据该指示获取传递报告, 因此能够在广播或组播方式传递 Push 消息情况下获知 Push消息的传递情况。 附图说明
为了更清楚地说明本发明实施例的技术方案, 下面将对实施例中所需要使用的附图作 一简单地介绍。
图 1为本发明实施例提供的一种传递 Push消息的方法流程图;
图 2为本发明实施例提供的一种接收 Push消息的方法流程图;
图 3为本发明实施例提供的一种 Push服务器的功能组成图一;
图 4为本发明实施例提供的一种 Push服务器的功能组成图二;
图 5为本发明实施例提供的一种终端的功能组成图一; 图 6为本发明实施例提供的一种终端的功能组成图二;
图 7为本发明实施例提供的一种传递 Push消息的系统组成图;
图 8为实施本发明的方法实施例的一个具体流程步骤图。 具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地 描述。
实施例一
参见图 1, 本发明实施例提供的一种传递 Push消息的方法, 包括:
步骤 11, 接收 Push消息, 在所述 Push消息中携带有统计传递结果的指示;
Push服务器接收 Push消息, 在所述 Push消息中携带有统计传递结果的指示。该统计 传递结果的指示在 Push消息中给出, 例如在 Push消息参数中给出指示, 如下给出在服务 质量 (QoS) 参数中给出指示的实现举例:
< 1 ELEMENT Push -message ( address+ , quality-of- service? ) >
< 1 ATTLIST Push-message
Push-id CDATA #REQUIRED
replace -Push- id CDATA #IMPLIED
replace -method ( pending-only
I all ) "all"
deliver-bef ore- timestamp %Datetime; # IMPLIED
deliver-af ter- timestamp %Datetime; # IMPLIED
source -reference CDATA # IMPLIED
Push 艮务器 -notify- requested- to CDATA #IMPLIED
progress -notes -requested ( true | false ) " false"
< 1 ELEMENT address EMPTY >
Figure imgf000005_0001
以下给出传递报告 Delivery-R印 ort可能的元数据格式:
Figure imgf000005_0002
Receiver- Address 字符串 可以是广播, 组播地址类型
Sender- Address 字符串 给出此传递 4艮告返回给的地址
Deliver-Report 字符串列表 指示 Push服务器统计相应的传递结果
Deliver-Report Values 字符串列表 传递报告类型的取值, 例如, "传递数目", 指示统计此
Push消息将发送给目标终端的数目。 "成功接收数目 ", 指示统计此 Push 消息成功接收的终端数目。 "失败数 目 ",指示统计此 Push消息无法接收或未发送成功的终 端数目。 "拒绝数目", 指示统计此 Push消息拒绝接收 的终端数目等。
Push服务器根据 Push消息中的 Del ivery-R印 ort指示信息判断需要统计的传递结果 类型。
在本发明的实施例中, 所述 Push 服务器可以是点对多点消息系统中 Push 代理网关 (PPG), Push消息由 Push消息发起者 (PI ) 向 Push代理网关 (PPG) 发送, 其中, 统计 传递结果的指示可以是 PI在发送给 PPG的 Push消息中携带的用于请求结果通知的信息。
步骤 12, 根据所述 Push消息确定通过广播或组播方式传递该 Push消息;
Push服务器根据所述 Push消息确定通过广播或组播方式传递该 Push消息,例如 Push 消息发起者可根据指令中的地址类型来指示 Push服务器通过广播或组播等方式发送 Push 消息, 或 Push服务器根据自身判断通过广播或组播的方式发送 Push消息。
步骤 13, 根据统计传递结果的指示获取传递报告。
Push服务器根据统计传递结果的指示获取传递报告,所述根据统计传递结果的指示获 取传递报告包括: 获取全部传递结果类型的传递报告, 或者仅获取所指示传递结果类型的 传递报告;
Push 服务器可通过如下几种方式获取传递报告: 通过查询组管理服务器获取传递报 告; 或通过接收终端返回的接收响应获取传递报告; 或通过查询终端与服务器建立连接的 数目获取传递报告。
例如在 Push消息发起者指示 Push服务器通过组播方式发送该 Push消息时, Push服 务器可以通过查询判断目标终端所在群组, 来获得发送此 Push 消息给目标终端的数目。 其中 Push服务器在通过查询组管理服务器获取传递报告时, 可以在发送该 Push消息前, 获得目标终端的地址信息, 从目标地址终端的数目获得此 Push将发送给目标终端的数目; 并且 Push服务器可根据发送 Push消息的数目, 或承载网络发送的数目获得该 Push消息 实际传递的数目, 以及通过接收终端返回的接收响应或终端与服务器建立连接等操作获得 该 Push消息成功接收的数目。 当然 Push服务器也可以在发送该 Push消息前, 通过查询 承载网络服务器, 获得加入此组播组用户的数目; 或者通过统计分发的密钥, 接入参数, 订阅过程, 业务声明, 返回确认加入组消息的数目等数据, 来统计接收 Push 消息的终端 数目。
终端对 Push服务器传递的 Push消息进行判断, 如果携带有返回接收响应的指示, 则 向 Push服务器返回接收响应。 接收响应的类型包括: 成功接收响应、 失败接收响应、 拒 绝接收响应、 正在处理响应、 禁止重传响应等等。
Push 服务器根据查询组管理服务器获取的结果或根据终端返回的接收响应或终端与 服务器建立连接等操作, 可统计出传递 Push消息的传递报告。 对于同一 Push消息标识, 统计的数目分类存储, 例如 Push消息成功发送的数目, Push消息失败的数目等。
对于获取的传递报告, Push服务器可以主动向 Push消息发起者返回传递报告, 也可 以根据 Push 消息发起者发送的请求传递报告的消息向所述 Push 消息发起者返回传递报 告, 该返回传递报告包括: 返回全部传递结果类型的传递报告, 或者仅返回所请求传递结 果类型的传递报告。 当然 Push服务器也可以根据其他服务器发送查询某项传递报告的请 求消息, Push服务器根据返回策略, 判断是否返回请求的结果给其他服务器, 如果是, 则 返回可返回的查询结果。
对于使用广播或组播等方式将 Push消息传递给终端, 并指示终端返回接收响应消息, 但终端没有上行信道可利用以返回接收响应的情况下, Push服务器可在传递给终端的所 述 Push 消息中携带承载方式的指示, 以使得所述终端使用所述指示的承载方式返回接收 响应。
指示的承载方式可以为一种或者多种, 由终端判断选择其中一种返回接收响应。 此指 示信息可以通过发送给终端的 Push消息中携带,例如在 QoS参数中指示,或通过扩展 Push 消息的消息头域、 值域或消息体, 携带指示终端返回接收响应所使用的承载方式标识, 并 且还可以进一步给出返回接收响应的接收地址信息和 /或 Push消息标识信息等, 例如, 指 示通过 SMS, Emai l , HTTP, WSP, SIP信令返回接收响应。 终端通过解析此指示承载方式 的标识, 并激活相应的应用, 使用所述指示的承载方式返回接收响应, 从而在终端没有上 行信道可利用的情形下, 仍然可以保证终端返回接收响应。 以下给出举例:
类型 取值
Push ID 字符串 Push消息的消息标识 Receiver- Address 字符串 可以是广播, 组播地址类型
Sender- Address 字符串 给出此接收响应返回给的地址
Report-Return-Method 字符串列表 指 示 终 端 使 用 的 承 载 方 式 , 通 过
SMS,Email,HTTP,WSP,SIP信令消息返回接收响应。
当然, 如果传递给终端的 Push 消息中没有指示具体的承载方式, 终端也可以通过默 认的方式返回接收响应。
为增强 Push服务器的统计功能, Push消息发起者还可以在所述 Push消息中携带统计 方式的指示,使得 Push服务器按照所述 Push消息中指示的统计方式对传递报告进行统计。
Push 服务器通过扩展所述传递报告的消息头域、 值域或消息体的方式将统计结果返回给 Push消息发起者, 从而 Push消息发起者能够收到详细的传递结果分类, 为用户带来更好 的体验。
统计结果可以放在传递报告的消息头中, 例如, Push服务器在向 Push消息发起者返 回的传递报告消息头中携带如下统计结果:
Figure imgf000008_0001
其中 Number数可以为 Push服务器将此 Push消息发送给终端的数目, 也可以为终端 返回接收响应的数目。 而 Successful-Number为成功接收该 Push消息的终端数目。 当然 也可包括 Rejected-Number表示拒绝接收的终端数目, Pending - Number表示正在处理的 终端数目, Undel iverable Number表示未能传递的终端数目等统计结果。
< 1 ELEMENT resultnoti f ication-message ( address , qual ity- of - service ? ) > < 1 ATTLIST resultnoti f ication-message
Push- id CDATA #REQUIRED/# IMPLIED )
sender- address CDATA # IMPLJ IED
sender-name CDATA # IMPLJ IED
received- time %Datetime; # IMPLJ IED
Figure imgf000008_0002
liiiiiiiililiiiiliiiB
当然, Push服务器也可以将统计结果封装在传递报告的消息体中, 以如下方式进行返 报告状态 数目 地址信息
Successful-Number n Address Info ej ected-Number n Address Info
Pending-Number n Address Info
Undeliverable-Number n Address Info
Delivered-Number n Address Info
Expired-Numb er n Address Info
Aborted-Number n Address Info
Timeout-Number n Address Info
Cancelled-Number n Address Info
Unkonw-Number n Address Info
Totol-report-Number n Address Info 可选地, Push消息发起者接收到该传递报告后, 向 Push服务器返回接收响应。
另外, 对指示返回接收响应未返回接收响应的终端或返回传递失败响应的终端, 可选 地, Push服务器可以进一步将该终端的地址信息报告给 Push消息发起者, Push消息发起 者可以用此信息判断是否需要向未成功接收 Push消息的终端, 进一步指示 Push服务器以 单播, 组播或广播方式再次传递该 Push消息, 或者 Push服务器自身根据所述终端地址信 息判断是否以单播, 组播或广播方式再次传递该 Push消息, 从而增加传递的成功率。
本发明实施例提供的传递 Push消息的方法, Push服务器在以广播或组播方式向终端 传递 Push消息时, 通过 Push消息发起者在所述 Push消息中携带统计传递结果的指示, 指示 Push服务器获取传递报告, 使得 Push服务器以广播或组播情况下仍能够获知 Push 消息的传递情况。
实施例二
参见图 2, 本发明实施例提供的一种接收 Push消息的方法, 包括:
步骤 21, 接收 Push服务器通过广播或组播方式传递的 Push消息, 在所述 Push消息 中携带有返回接收响应的指示;
终端接收 Push服务器通过广播或组播方式传递的 Push消息, 在所述 Push消息中携 带有返回接收响应的指示, 该返回接收响应的指示可在 Push消息中的 QoS参数中给出, 例如可以在 QoS参数中添加 Response-R印 ort标识指示终端需要向 Push服务器返回接收 响应。
步骤 22, 根据所述返回接收响应的指示, 向所述 Push服务器返回接收响应或与服务 器建立连接。
终端接收到该 Push消息, 对接收到的 Push消息进行判断, 如果携带有返回接收响应 的指示, 则向 Push服务器返回接收响应。 接收响应的类型包括: 成功接收响应、 失败接 收响应、 拒绝接收响应、 正在处理响应、 禁止重传响应等等。 Push服务器根据终端返回的 接收响应或终端与服务器建立连接等操作, 统计出 Push消息的传递报告, 使得 Push服务 器在以广播或组播方式传递 Push消息的情况下, 仍能够获知 Push消息的传递情况。
对于使用广播或组播等方式将 Push消息传递给终端, 并指示终端返回接收响应消息, 但终端没有上行信道可利用以返回接收响应的情况下, Push服务器可在传递给终端的所 述 Push 消息中携带有承载方式的指示, 使得所述终端根据所述承载方式的指示, 激活相 应的应用, 使用所述指示的承载方式向所述 Push服务器返回接收响应。
指示的承载方式可以为一种或者多种, 由终端判断选择其中一种返回接收响应。 此指 示信息可以通过发送给终端的 Push消息中携带,例如在 QoS参数中指示,或通过扩展 Push 消息的消息头域、 值域或消息体, 携带指示终端返回接收响应所使用的承载方式标识, 并 且还可以进一步给出返回接收响应的接收地址信息和 /或 Push消息标示信息等, 例如, 指 示通过 SMS, Emai l , HTTP, WSP, SIP信令返回接收响应。 终端通过解析此指示承载方式 的标识, 并激活相应的应用, 使用所述指示的承载方式返回接收响应, 从而在终端没有上 行信道可利用的情形下, 仍然可以保证终端返回接收响应。 当然, 如果 Push 消息中没有 指示具体的承载方式, 终端也可以通过默认的方式返回接收响应。
本发明实施例提供的接收 Push消息的方法, 在 Push服务器在以广播或组播方式向终 端传递 Push消息时, 通过在所述 Push消息中携带返回接收响应的指示, 指示终端返回接 收响应, 以使得 Push服务器根据终端返回的接收响应或终端与服务器建立连接等操作, 统计出 Push消息的传递报告。
实施例三
参见图 3, 本发明实施例提供一种 Push服务器, 包括:
接收单元 31, 用于接收 Push消息, 所述 Push消息中携带有统计传递结果的指示; 传递方式确定单元 32, 用于根据所述 Push消息确定通过广播或组播方式向终端传递 所述 Push消息; 传递报告获取单元 33, 用于根据统计传递结果的指示获取传递报告。
所述根据统计传递结果的指示获取传递报告包括: 获取全部传递结果类型的传递报 告, 或者仅获取所指示传递结果类型的传递报告;
其中, 所述报告获取单元 33包括如下至少一种模块:
第一获取模块, 用于通过查询组管理服务器获取传递报告;
第二获取模块, 用于通过接收终端返回的接收响应获取传递报告;
第三获取模块, 用于通过查询终端与服务器建立连接的数目获取传递报告。
对于获取的传递报告, Push服务器可以主动向 Push消息发起者返回传递报告, 也可 以根据 Push 消息发起者发送的请求传递报告的消息向所述 Push 消息发起者返回传递报 告, 该返回传递报告包括: 返回全部传递结果类型的传递报告, 或者仅返回所请求传递结 果类型的传递报告。 当然 Push服务器也可以根据其他服务器发送查询某项传递报告的请 求消息, Push服务器根据返回策略, 判断是否返回请求的结果给其他服务器, 如果是, 则 返回可返回的查询结果。
在本发明的实施例中, 所述 Push 服务器可以是点对多点消息系统中 Push 代理网关 (PPG), PPG所接收的 Push消息是由 Push消息发起者 (PI ) 向 Push代理网关 (PPG) 发 送。
为此, 参见图 4, 本实施例提供的 Push服务器 3, 还包括传递报告返回单元 34, 该传 递报告返回单元至少包括如下任一模块:
主动返回模块, 用于主动向 Push消息发起者返回所述传递报告;
请求返回模块, 用于根据 Push消息发起者发送的请求传递报告的消息向所述 Push消 息发起者返回所述传递报告;
策略返回模块, 用于如果是 Push 消息发起者之外的其他服务器发送的请求传递报告 的消息, 则根据返回策略进行判断是否返回所述请求的传递报告。
对于使用广播或组播等方式将 Push消息传递给终端, 并指示终端返回接收响应消息, 但终端没有上行信道可利用以返回接收响应的情况下, 所述 Push服务器还包括:
承载方式指示单元 35, 用于在传递给终端的 Push消息中携带承载方式的指示, 以使 得所述终端根据所述承载方式的指示, 激活相应的应用, 使用所述指示的承载方式返回接 收响应。 从而在终端没有上行信道可利用的情形下, 仍然可以保证终端返回接收响应。 为增强 Push服务器的统计功能, Push消息发起者在所述 Push消息中还携带有对返回 传递报告统计方式的指示, 为此, 仍参见图 4, 所述 Push服务器还包括:
统计单元 36, 用于按照所述 Push消息中指示的统计方式对传递报告进行统计; 同时, 所述传递报告返回单元 34, 具体用于通过扩展所述传递报告的消息头域、值域或消息体的 方式将统计结果返回给 Push消息发起者。 从而 Push消息发起者能够收到详细的传递结果 分类, 为用户带来更好的体验。
另外, 对于指示返回接收响应未返回接收响应的终端或返回传递失败响应的终端, 根 据所述终端地址信息, Push服务器可以向所述终端再次发送该 Push消息, 从而增加传递 的成功率。 为此, 所述 Push服务器还可包括:
重传单元 37,用于对指示返回接收响应未返回接收响应的终端或返回传递失败响应的 终端, 根据所述终端地址信息, 向所述终端再次传递该 Push消息。
本发明实施例提供的 Push服务器, 可应用于上述的方法实施例一, 对以广播或组播 方式传递 Push消息情况下, 仍能够获知 Push消息的传递情况。
实施例四
参见图 5, 本发明实施例提供一种终端, 包括:
接收单元 51, 用于接收 Push服务器通过广播或组播方式传递的 Push消息, 在所述 Push消息中携带有返回接收响应的指示;
响应返回单元 52, 用于根据所述返回接收响应的指示, 向所述 Push服务器返回接收 响应或与服务器建立连接。
终端的接收单元 51接收到该 Push消息, 对接收到的 Push消息进行判断, 如果携带 有返回接收响应的指示, 则向 Push服务器返回接收响应。 接收响应的类型包括: 成功接 收响应、 失败接收响应、 拒绝接收响应、 正在处理响应、 禁止重传响应等等。 Push服务器 根据终端返回的接收响应或终端与服务器建立连接等操作, 统计出 Push消息的传递报告, 使得 Push服务器在以广播或组播方式传递 Push消息情况下, 仍能够获知 Push消息的传 递情况。
对于使用广播或组播等方式将 Push消息传递给终端, 并指示终端返回接收响应消息, 但终端没有上行信道可利用以返回接收响应的情况下, Push 服务器可以在传递给终端的 Push消息中携带承载方式的指示,以使得终端根据所述承载方式的指示,激活相应的应用, 使用所述指示的承载方式向所述 Push服务器返回接收响应, 从而在终端没有上行信道可 利用的情形下, 仍然可以保证终端返回接收响应。 为此参见图 6, 本发明实施例提供的终 端还包括:
应用激活单元 53, 用于根据所述 Push消息中指示的承载方式, 激活相应的应用; 同 时, 所述响应返回单元 52, 具体用于使用所述指示的承载方式向所述 Push服务器返回接 收响应。
本发明实施例提供的终端, 可应用于上述的方法实施例二, 使得 Push服务器在以广 播或组播方式传递 Push消息情况下, 仍能够获知 Push消息的传递情况。
实施例五
参见图 7,本发明实施例提供了一种传递 Push消息的系统,包括 Push消息发起者 10、 Push服务器 20和若干个终端 30, 其中,
所述 Push服务器 20, 用于接收所述 Push消息发起者发送的传递 Push消息的指令, 在接收的 Push消息中携带有统计传递结果的指示, 根据所述 Push消息确定通过广播或组 播方式向终端传递所述 Push消息; 根据统计传递结果的指示获取传递报告。
具体地, 所述 Push服务器 20, 用于通过查询组管理服务器获取传递报告; 或通过接 收终端返回的接收响应获取传递报告; 或通过查询终端与服务器建立连接的数目获取传递 报告。 该获取的传递报告包括: 获取全部传递结果类型的传递报告, 或者仅获取所指示传 递结果类型的传递报告。
此外,所述 Push服务器 20,还用于主动向 Push消息发起者返回所述传递报告;或者, 根据 Push消息发起者发送的传递报告的请求消息向所述 Push消息发起者返回所述传递报 告; 或者, 如果是 Push 消息发起者之外的其他服务器发送的传递报告的请求消息, 则根 据返回策略进行判断是否返回响应并携带所述请求的传递报告。 该返回的传递报告包括: 返回全部传递结果类型的传递报告, 或者仅返回所请求传递结果类型的传递报告。
在终端没有上行信道返回接收响应的情形下, 所述 Push服务器 20, 还用于在传递给 终端的 Push 消息中携带承载方式的指示, 以使得终端根据所述承载方式的指示, 激活相 应的应用, 使用所述指示的承载方式返回接收响应。
为增强 Push服务器 20的统计功能, 所述 Push消息发起者 10在 Push消息中携带统 计方式的指示; 此时, 所述 Push服务器 20, 还用于按照所述 Push消息中指示的统计方式 对传递报告进行统计, 并通过扩展所述传递报告的消息头域、 值域或消息体的方式将统计 结果返回给 Push消息发起者。
参见图 8, 实施本发明提供的方法实施例的一个具体流程步骤, 包括:
步骤 81, Push消息发起者发送传递 Push消息的指令给 Push服务器, 指示 Push服务 器通过广播或组播的方式传递该 Push消息。
在所述 Push消息中携带有统计传递报告的指示, 也可以携带有终端承载方式的指示, 还可以携带有统计方式的指示。
步骤 82, Push服务器返回响应消息。 此步骤为可选步骤。
步骤 83, Push服务器通过广播或组播的方式将 Push消息传递给终端。
步骤 84, 终端对接收到的 Push消息, 判断是否需要返回接收响应, 还可以进一步判 断是否指示有使用的承载方式。 如果指示有多种承载方式, 则终端根据网络情况, 用户偏 好, 设置, 能力等信息, 激活相应的应用, 选择一种承载方式返回接收响应。
步骤 85, 判断后终端使用指示的承载方式或默认的承载方式向 Push服务器返回接收 响应。
步骤 86, Push服务器接收到终端返回的接收响应后,进行缓存并分类统计,例如 Push 消息成功发送的数目, Push消息失败的数目等。 如果在所述 Push消息中还携带有统计方 式的指示, 则所述 Push服务器将按照所述指示的统计方式对所述终端返回的接收响应进 行统计。
步骤 87, Push服务器根据统计结果向 Push消息发起者发送传递报告。 统计结果可能 由于各终端接收 Push 消息或返回接收响应的时延不同, 可以分批发送传递报告, 或可以 等待所有结果统计后一起返回传递报告, 也可以设定一个时限发送传递报告。 在此传递报 告中, 需要给出 Push消息的标识, Push消息发起者用此标识识别此传递报告结果为那条 Push消息的接收结果报告。
步骤 88, Push消息发起者接收到传递报告后, 向 Push服务器返回响应消息。 当然, 此流程中, 在 Push服务器向 Push消息发起者返回传递报告之前, Push消息发 起者可以在任意步骤增加查询请求, 请求某条 Push消息的传递情况。
本领域技术人员还可以意识到, 结合本文中所公开的实施例描述的各示例的单元及实 现步骤, 能够以电子硬件、 计算机软件或者二者的结合来实现, 为了清楚地说明硬件和软 件的可互换性, 在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。 这些功 能究竟以硬件还是软件方式来执行, 取决于技术方案的特定应用和设计约束条件。 本领域 技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能, 但是这种实现不应 认为超出本发明的范围。
结合本文中所公开的实施例描述的方法步骤, 可以用硬件、 处理器执行的软件模块, 或者二者的结合来实施。 软件模块可以置于随机存储器(RAM)、 内存、 只读存储器(R0M)、 电可编程 R0M、 电可擦除可编程 R0M、 寄存器、 硬盘、 可移动磁盘、 CD-R0M、 或任意其它 形式的存储介质中。 上述具体实施例并不用以限制本发明, 对于本技术领域的普通技术人员来说, 凡在不脱离 本发明原理的前提下, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护范 围之内。

Claims

权利 要 求
1、 一种传递 Push消息的方法, 其特征在于, 包括:
接收 Push消息, 所述 Push消息中携带有统计传递结果的指示;
根据所述 Push消息确定通过广播或组播方式向终端传递所述 Push消息;
根据统计传递结果的指示获取传递报告。
2、 根据权利要求 1所述传递 Push消息的方法, 其特征在于, 所述根据统计传递结果 的指示获取传递报告的方式包括;
通过查询组管理服务器获取传递报告; 或
通过接收终端返回的接收响应获取传递报告; 或
通过查询终端与服务器建立连接的数目获取传递报告。
3、 根据权利要求 2所述传递 Push消息的方法, 其特征在于, 所述通过查询组管理服 务器获取传递报告具体为:
在发送所述 Push消息前, 对接收所述 Push消息的目标终端数目进行查询。
4、 根据权利要求 1或 2所述传递 Push消息的方法, 其特征在于, 所述方法还包括: 主动向 Push消息发起者返回所述传递报告;
或者, 根据 Push消息发起者发送的请求传递报告的消息向所述 Push消息发起者返回 所述传递报告;
或者, 如果是 Push 消息发起者之外的其他服务器发送的请求传递报告的消息, 则根 据返回策略进行判断是否返回所述请求的传递报告。
5、 根据权利要求 1或 2所述传递 Push消息的方法, 其特征在于,
所述根据统计传递结果的指示获取传递报告包括: 获取全部传递结果类型的传递报 告, 或者仅获取所指示传递结果类型的传递报告。
6、 根据权利要求 4所述传递 Push消息的方法, 其特征在于, 在终端没有上行信道返 回接收响应的情形下, 所述方法还包括:
在传递给终端的 Push 消息中携带有承载方式的指示, 以使得所述终端根据所述承载 方式的指示, 激活相应的应用, 使用所述指示的承载方式返回接收响应。
7、 根据权利要求 4所述传递 Push消息的方法, 其特征在于, 所述 Push消息中还携 带有统计方式的指示, 所述方法还包括:
按照所述指示的统计方式对传递报告进行统计, 并通过扩展所述传递报告的消息头 域、 值域或消息体的方式将统计结果返回给 Push消息发起者。
8、 根据权利要求 2所述传递 Push消息的方法, 其特征在于, 对指示返回接收响应未 返回接收响应的终端或返回传递失败响应的终端, 根据所述终端的地址信息, 向所述终端 再次传递该 Push消息。
9、 根据权利要求 1-9所述的传递 Push消息的方法, 其特征在于, 所述统计传递结果 的指示为消息发起者 PI发送的 Push消息中携带的用于请求结果通知的信息。
10、 一种接收 Push消息的方法, 其特征在于, 包括:
接收 Push服务器通过广播或组播方式传递的 Push消息, 所述 Push消息中携带有返 回接收响应的指示;
根据所述返回接收响应的指示, 向所述 Push 服务器返回接收响应消息或与服务器建 立连接。
11、 根据权利要求 10所述接收 Push消息的方法, 其特征在于, 所述 Push消息中还 携带有承载方式的指示, 所述方法还包括:
根据所述承载方式的指示, 激活相应的应用, 使用所述指示的承载方式向所述 Push 服务器返回接收响应。
12、 一种 Push服务器, 其特征在于, 包括:
接收单元, 用于接收 Push消息, 所述 Push消息中携带有统计传递结果的指示; 传递方式确定单元, 用于根据所述 Push 消息确定通过广播或组播方式向终端传递所 述 Push消息;
传递报告获取单元, 用于根据统计传递结果的指示获取传递报告。
13、 根据权利要求 12所述的 Push服务器, 其特征在于, 所述传递报告获取单元至少 包括如下任一模块:
第一获取模块, 用于通过查询组管理服务器获取传递报告;
第二获取模块, 用于通过接收终端返回的接收响应获取传递报告;
第三获取模块, 用于通过查询终端与服务器建立连接的数目获取传递报告。
14、 根据权利要求 12或 13所述的 Push服务器, 其特征在于, 还包括传递报告返回 单元, 该传递报告返回单元至少包括如下任一模块:
主动返回模块, 用于主动向 Push消息发起者返回所述传递报告;
请求返回模块, 用于根据 Push消息发起者发送的请求传递报告的消息向所述 Push消 息发起者返回所述传递报告;
策略返回模块, 用于如果是 Push 消息发起者之外的其他服务器发送的请求传递报告 的消息, 则根据返回策略进行判断是否返回所述请求的传递报告。
15、 根据权利要求 14所述的 Push服务器, 其特征在于, 所述 Push服务器还包括: 承载方式指示单元, 用于在传递给终端的 Push 消息中携带承载方式的指示, 以使得 所述终端根据所述承载方式的指示, 激活相应的应用, 使用所述指示的承载方式返回接收 响应。
16、 根据权利要求 14所述的 Push服务器, 其特征在于, 所述 Push服务器还包括: 统计单元, 用于按照所述 Push消息中指示的统计方式对获取的传递报告进行统计; 所述传递报告返回单元, 具体用于通过扩展所述传递报告的消息头域、 值域或消息体 的方式将统计结果返回给 Push消息发起者。
17、 根据权利要求 13所述的 Push服务器, 其特征在于, 所述 Push服务器还包括: 重传单元, 用于对指示返回接收响应未返回接收响应的终端或返回传递失败响应的终 端, 根据所述终端地址信息, 向所述终端再次传递该 Push消息。
18、 根据权利要求 12-17任一项权利要求所述的 Push服务器为点对多点中的 Push代 理网关 PPG
19、 一种终端, 其特征在于, 包括:
接收单元, 用于接收 Push服务器通过广播或组播方式传递的 Push消息, 所述 Push 消息中携带有返回接收响应的指示;
响应返回单元, 用于根据所述返回接收响应的指示, 向所述 Push服务器返回接收响 应消息或与服务器建立连接。
20、 根据权利要求 17所述的终端, 其特征在于, 所述终端还包括:
应用激活单元, 用于根据所述 Push 消息中指示的承载方式, 激活相应的应用; 以使 所述响应返回单元使用所述指示的承载方式向所述 Push服务器返回接收响应。
PCT/CN2010/076251 2009-08-24 2010-08-23 传递及接收Push消息的方法和设备 WO2011023089A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP10811249.1A EP2472776B1 (en) 2009-08-24 2010-08-23 Method and device for delivering and receiving push messages
ES10811249.1T ES2617188T3 (es) 2009-08-24 2010-08-23 Método y dispositivo para enviar y recibir mensajes Push
US13/404,910 US20120147887A1 (en) 2009-08-24 2012-02-24 Method and device for delivering and receiving push message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009101630854A CN101997696A (zh) 2009-08-24 2009-08-24 传递及接收Push消息的方法和设备
CN200910163085.4 2009-08-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/404,910 Continuation US20120147887A1 (en) 2009-08-24 2012-02-24 Method and device for delivering and receiving push message

Publications (1)

Publication Number Publication Date
WO2011023089A1 true WO2011023089A1 (zh) 2011-03-03

Family

ID=43627253

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076251 WO2011023089A1 (zh) 2009-08-24 2010-08-23 传递及接收Push消息的方法和设备

Country Status (5)

Country Link
US (1) US20120147887A1 (zh)
EP (1) EP2472776B1 (zh)
CN (1) CN101997696A (zh)
ES (1) ES2617188T3 (zh)
WO (1) WO2011023089A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8311041B1 (en) * 2012-06-22 2012-11-13 Google Inc. Systems and methods for automatically adjusting messaging quota
CN103716752B (zh) * 2012-09-29 2017-06-27 上海贝尔股份有限公司 一种分发机器类通信的组消息的方法
US9729651B2 (en) * 2013-09-13 2017-08-08 Electronics And Telecommunications Research Institute Method for delivering push notification and push notification server for performing the same
KR102105561B1 (ko) * 2013-09-13 2020-04-28 한국전자통신연구원 푸시 알림 전송 방법 및 이를 수행하는 푸시 알림 서버
KR102141854B1 (ko) * 2014-02-21 2020-08-06 삼성전자주식회사 푸시 메시지 전송 제어 방법 및 장치
CN105407505B (zh) * 2014-07-18 2019-05-17 青岛海尔智能家电科技有限公司 一种资源控制消息的处理方法及装置
CN105515914B (zh) * 2015-12-24 2019-01-25 无线生活(杭州)信息科技有限公司 一种为Push消息分配流量的方法及装置
US10893955B2 (en) 2017-09-14 2021-01-19 Orthosensor Inc. Non-symmetrical insert sensing system and method therefor
CN108415956A (zh) * 2018-02-06 2018-08-17 北京中兴高达通信技术有限公司 一种状态信息处理方法及设备
US11812978B2 (en) 2019-10-15 2023-11-14 Orthosensor Inc. Knee balancing system using patient specific instruments

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1845550A (zh) * 2005-04-06 2006-10-11 中兴通讯股份有限公司 一种wap终端用户push消息的接收方法及其系统
CN101355488A (zh) * 2007-07-25 2009-01-28 中国移动通信集团公司 网络发起的消息类业务中控制流量的方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2361861A1 (en) * 2001-11-13 2003-05-13 Ibm Canada Limited-Ibm Canada Limitee Wireless messaging services using publish/subscribe systems
US7254614B2 (en) * 2001-11-20 2007-08-07 Nokia Corporation Web services push gateway
EP1502464B1 (en) * 2002-05-06 2005-07-27 Telefonaktiebolaget LM Ericsson (publ) Multi-user multimedia messaging services
DE602006016401D1 (de) * 2006-03-29 2010-10-07 Research In Motion Ltd Vorrichtung und zugeordnetes Verfahren zur Erleichterung der Hintergrundverarbeitung von "Push"-Inhalt

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1845550A (zh) * 2005-04-06 2006-10-11 中兴通讯股份有限公司 一种wap终端用户push消息的接收方法及其系统
CN101355488A (zh) * 2007-07-25 2009-01-28 中国移动通信集团公司 网络发起的消息类业务中控制流量的方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2472776A4 *

Also Published As

Publication number Publication date
ES2617188T3 (es) 2017-06-15
CN101997696A (zh) 2011-03-30
EP2472776B1 (en) 2016-12-14
US20120147887A1 (en) 2012-06-14
EP2472776A1 (en) 2012-07-04
EP2472776A4 (en) 2012-10-03

Similar Documents

Publication Publication Date Title
WO2011023089A1 (zh) 传递及接收Push消息的方法和设备
AU2005278898B2 (en) Method and device for acknowledging data in point-to-multipoint transmission systems
US8880719B2 (en) Method and system for multicast delivery of multimedia content on demand
EP1716658B1 (en) A method for data repair in a system capable of handling multicast and broadcast transmissions
US20100226301A1 (en) Feedback Technique for a Hierarchically Organized Broadcast/Multicast Service Area
WO2014011098A2 (en) Broadcasting of data files and file repair procedure with regards to the broadcasted data files
JP2015511409A5 (zh)
EP1990949B1 (en) System and method for multimedia broadcast/multicast service data transmission
WO2010022608A1 (zh) 一种多播广播业务管理方法、装置与系统
CA2561712C (en) Data repair enhancements for multicast/broadcast data distribution
EP2878098B1 (en) User equipment node, server node and methods performed in such nodes for performing file repair procedure
WO2004030399A1 (en) Multicast data transfer
CN105723751B (zh) 在通信系统中用于启用反馈传输的方法和装置
CA2675990C (en) Submit report handling in smsip
US9634845B2 (en) Session switching during ongoing data delivery in a network
WO2007102060A2 (en) Uplink signaling for multicast transmission
WO2009152717A1 (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: 10811249

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2010811249

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2010811249

Country of ref document: EP