WO2009026842A1

WO2009026842A1 - A processing method and device of the session initiation protocol push message

Info

Publication number: WO2009026842A1
Application number: PCT/CN2008/072110
Authority: WO
Inventors: Jian Yang; Lei Wang; Guoqiao Chen; Shunan Fan; Huiping Zhang; Ting Dong; Zheng Wang; Hao Wang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-23
Filing date: 2008-08-22
Publication date: 2009-03-05
Also published as: CN101374267B; CN101374267A

Abstract

A processing method of the session initiation protocol PUSH message is provided. The SIP PUSH message is received firstly; whether it is the right destination receiver of the SIP PUSH message is checked secondly; if NO, the SIP PUSH message is discarded. A SIP PUSH receiver and a SIP PUSH message sender are also provided. The present invention protects the privacy of the user by checking the right destination receiver of SIP PUSH message, and discarding the SIP PUSH message if it is not the right destination receiver of SIP PUSH message.

Description

Method and device for processing session initiation protocol push message

Technical field

The present invention relates to the field of communications technologies, and in particular, to a SIP (Session Initiation Protocol) PUSH (Pushing) message processing method and apparatus. Background technique

With the rapid development of wireless communication technology, the PUSH service has been widely used. The PUSH service is a content distribution mechanism that uses the client/server mode of work and requires the server to distribute the required content without the client making a specific request. In the working framework of the PUSH, the PI (PUSH Initiator, PUSH initiator) sends the PUSH content and transmits the command to the PPG (PUSH Proxy Gateway, PUSH Proxy Gateway), and the PPG transmits the content of the PUSH to the PUSH client according to the requirements of the transfer instruction. end.

The SIP PUSH service uses OTA-SIP (SIP-based over-the-air) technology to encapsulate PUSH OTA (Over The Air) content in SIP messages and utilize existing SIP/IP core networks for transmission. SIP PUSH service maintenance costs are small and have high interoperability, which can reuse existing resources.

1 is a SIP PUSH architecture of the prior art, including a PUSH sending proxy 11 and a PUSH receiving proxy 12. The PUSH sending proxy 11 communicates with the PUSH receiving proxy 12 through the SIP/IP Core network. The PUSH sending proxy 11 is located at the server end (PPG), and the PUSH receiving proxy 12 is located at the receiving end (PUSH receiving end).

2 is a flow chart of implementing a SIP PUSH service in the prior art, including the following steps:

Step S201, PUSH sends a proxy registration PUSH service;

Step S202, sending an available PUSH application and an OMA-UAProf link including device capabilities;

Step S203, the SIP/IP Core network forwards the request to the PUSH sending proxy. Step S204, if the OMA-UAProf link is received, the PUSH sends the proxy to the proxy. UAProf link request device capability;

Step S205, the UAProf server returns the device capability.

Step S206, the PUSH receiving proxy subscribes to the content update to be received; Step S207, the SIP/IP Core network forwards the request to the PUSH sending proxy; Step S208, the PUSH sending proxy receives the content sent to the PUSH receiving proxy; Step S209, PUSH sends the proxy Receiving a message, and selecting a PUSH method based on the content determining delivery mechanism and quality of service (if device capabilities are available);

Step S210: The PUSH sending proxy sends a request to the receiving end via the SIP/IP Core network. In order to improve efficiency, the content in the request may be encoded and converted.

Step S211: The SIP/IP Core network forwards the request to the PUSH receiving agent. The PUSH receiving agent will use business addressing to properly pass the content in the request.

Step S212, after receiving the request, the PUSH receiving agent sends a report to respond.

SIP/IP Core.

Step S213: The SIP/IP Core network forwards the response report to the PUSH sending proxy. Step S214: The PUSH sending proxy processes the received response.

Step S204 to step S207 and step S212 to step S214 are optional steps, and whether or not to perform the step may be selected according to actual conditions.

In carrying out the process of the present invention, the inventors have found that the prior art has at least the following problems:

The terminal address identifier sent by the PPG to the SIP/IP Core needs to be resolved to the actual IP address of the terminal by the SIP/IP Core, and the PUSH receiver can receive the SIP PUSH message. However, if an IP address resolution error or an address is falsified, the SIP/IP Core may deliver the SIP PUSH message to a terminal other than the destination PUSH receiver. When the message sent by the PI to the PUSH receiving end of the PI belongs to the information with high privacy, if the SIP PUSH message is received by the terminal other than the destination PUSH receiving end, the risk of user privacy leakage may occur. Summary of the invention

The problem to be solved by the embodiment of the present invention is to provide a processor for processing SIP PUSH messages. The method and device can protect the privacy of the user when the SIP PUSH message is sent incorrectly. To achieve the above objective, the technical solution of the embodiment of the present invention provides a method for processing a SIP PUSH message, including the following steps: receiving a SIP PUSH message; checking whether the correct destination receiving end of the SIP PUSH message is; if not, then losing Discard the SIP PUSH message.

The technical solution of the embodiment of the present invention further provides a SIP PUSH receiving end, which includes a correct destination receiving end checking unit and a SIP PUSH message processing unit. The correct destination receiving end checking unit is configured to check whether the received SIP PUSH is received. The correct destination receiving end of the message; the message processing unit, configured to process the SIP PUSH message according to the check result of the correct destination receiving end checking unit.

The technical solution of the embodiment of the present invention further provides a SIP PUSH message sending end, which includes a SIP PUSH message generating unit, configured to generate and send a SIP PUSH message carrying a privacy protection identifier, where the privacy protection identifier is used to identify the SIP. The PUSH receiving end performs a check of the correct destination receiving end of the SIP PUSH message.

Compared with the prior art, the embodiment of the invention has the following advantages:

In the embodiment of the present invention, the SIP PUSH message is discarded by checking the correct destination receiving end of the SIP PUSH message, and the SIP PUSH message is discarded when the correct destination receiving end of the SIP PUSH message is not received, thereby preventing the SIP PUSH message from being incorrect. The leakage of user privacy caused by delivery. DRAWINGS

1 is a schematic diagram of an architecture of a SIP PUSH in the prior art;

2 is a flow chart of implementing a SIP PUSH service in the prior art;

3 is a flowchart of processing a SIP PUSH message according to an embodiment of the present invention; FIG. 4 is a flowchart of processing another SIP PUSH message according to an embodiment of the present invention; FIG. 5 is another SIP PUSH according to an embodiment of the present invention; FIG. 6 is a flowchart of processing a SIP PUSH message according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of a SIP PUSH receiving end according to an embodiment of the present invention; A schematic diagram of the structure of a SIP PUSH message sending end Figure. detailed description

The specific embodiments of the present invention are further described in detail below with reference to the accompanying drawings and embodiments.

After the SIP PUSH message is forwarded to the PUSH receiving proxy by the SIP/IP Core network, the SIP PUSH receiving end (in this embodiment, the PUSH receiving proxy) processes the SIP PUSH message as shown in FIG. 3 . Includes the following steps:

Step S301: The SIP PUSH receiving end receives the SIP PUSH message forwarded by the SIP/IP Core network. The SIP PUSH message carries the destination identifier, and the destination identifier includes the SIP, the destination address may be a SIP URI (Uniform Resource Identifier) or a mobile station international user directory number MSISDN; the destination terminal may be an IMSI. (International Mobile Subscriber Identity) or Device ID (Identifier).

Step S302: The SIP PUSH receiving end determines whether the destination identifier carried in the SIP PUSH message is the same as the identifier of the SIP PUSH receiving end itself; if yes, the SIP PUSH receiving end is the correct destination receiving end of the SIP PUSH message, Step S304; otherwise, the SIP PUSH receiving end is not the correct destination receiving end of the SIP PUSH message, and the process goes to step S303.

Step S303, discarding the SIP PUSH message and ending.

Step S304, the normal processing flow of the SIP PUSH message is entered, that is, the message is parsed, provided to the upper layer application, or the SIP PUSH message is displayed.

In this embodiment, by checking the correct destination receiving end of the SIP PUSH message and discarding the SIP PUSH message when it is not the correct destination receiving end of the SIP PUSH message, the privacy of the user is protected, and the SIP PUSH message is prevented from being incorrectly delivered. And the leakage of user privacy caused.

The embodiment of the present invention receives the SIP PUSH message to the PUSH in the SIP/IP Core network. After the proxy forwarding, the SIP PUSH receiving end (in this embodiment, the PUSH receiving proxy) processes the SIP PUSH message as shown in FIG. 4, and includes the following steps:

Step S401: The SIP PUSH receiving end receives the SIP PUSH message forwarded by the SIP/IP Core network. The SIP PUSH message carries the destination identifier, and the destination identifier includes the SIP, and the destination address can be a SIP URI or an MSISDN. The identifier of the destination terminal can be an IMSI or a device ID.

Step S402: The SIP PUSH receiving end determines whether the destination identifier carried in the SIP PUSH message is the same as the identifier of the SIP PUSH receiving end itself. If yes, the SIP PUSH receiving end is the correct destination receiving end of the SIP PUSH message. Step S404; Otherwise, the SIP PUSH receiving end is not the correct destination receiving end of the SIP PUSH message, and the process goes to step S403.

Step S403, discarding the SIP PUSH message, returning an error status code to the sending end, and ending.

Step S404, the normal processing flow of the SIP PUSH message is entered, that is, the message is parsed, provided to the upper layer application, or the SIP PUSH message is displayed.

After the SIP PUSH message sending end receives the error status code returned by the SIP PUSH receiving end, the SIP PUSH message sending end performs data retransmission according to the error status code.

Moreover, in this embodiment, by returning an error status code to the transmitting end, the SIP PUSH message sending end may be requested to retransmit the data.

After the SIP PUSH message is forwarded to the PUSH receiving proxy by the SIP/IP Core network, the SIP PUSH receiving end (in this embodiment, the PUSH receiving proxy) processes the SIP PUSH message as shown in FIG. 5 . Includes the following steps:

Step S501, the SIP PUSH receiving end receives the SIP forwarded by the SIP/IP Core network. PUSH message. The SIP PUSH message carries the destination identifier, where the destination identifier includes the SIP, and the destination address can be a SIP URI or an MSISDN; the identifier of the destination terminal can be an IMSI or a device ID.

Step S502: Determine whether to perform a check of the correct destination receiving end of the SIP PUSH message. And determining whether to perform the check of the correct destination receiving end of the SIP PUSH message according to whether the SIP PUSH message carries the privacy protection identifier; if the SIP PUSH message carries the privacy protection identifier, go to step S503; otherwise, go to step S505.

Step S503: The SIP PUSH receiving end determines whether the destination identifier carried in the SIP PUSH message is the same as the identifier of the SIP PUSH receiving end itself. If yes, the SIP PUSH receiving end is the correct destination receiving end of the SIP PUSH message. Step S505; otherwise, the SIP PUSH receiving end is not the correct destination receiving end of the SIP PUSH message, and the process goes to step S504.

Step S504, discarding the SIP PUSH message and ending.

Step S505: Enter a normal processing procedure of the SIP PUSH message, that is, perform message parsing, provide to an upper layer application, or display the SIP PUSH message.

Moreover, in this embodiment, by determining whether the SIP PUSH message carries the privacy protection identifier, it is possible to select whether to perform the check of the correct destination receiving end of the SIP PUSH message. For example, for an advertisement or an announcement message sent by the PI, the privacy protection identifier may not be carried, and the SIP PUSH message is not discarded, but is normally viewed. For a SIP PUSH message with a high privacy requirement, the privacy protection identifier is carried. When the SIP PUSH message is incorrectly delivered, the received terminal is required to discard the message.

After the SIP PUSH message is forwarded to the PUSH receiving proxy by the SIP/IP Core network, the SIP PUSH receiving end (in this embodiment, the PUSH receiving proxy) processes the SIP PUSH message as shown in FIG. 6 . Includes the following steps: Step S601: The SIP PUSH receiving end receives the SIP PUSH message forwarded by the SIP/IP Core network. The SIP PUSH message carries the destination identifier, where the destination identifier includes the SIP, and the destination address can be a SIP URI or an MSISDN; the identifier of the destination terminal can be an IMSI or a device ID.

Step S602, determining whether to perform a check of the correct destination receiving end of the SIP PUSH message. And determining whether to perform the check of the correct destination receiving end of the SIP PUSH message according to whether the SIP PUSH message carries the privacy protection identifier; if the SIP PUSH message carries the privacy protection identifier, go to step S603; otherwise, go to step S605.

Step S603: The SIP PUSH receiving end determines whether the destination identifier carried in the SIP PUSH message is the same as the identifier of the SIP PUSH receiving end itself; if yes, the SIP PUSH receiving end is the correct destination receiving end of the SIP PUSH message, Step S605; Otherwise, the SIP PUSH receiving end is not the correct destination receiving end of the SIP PUSH message, and the process goes to step S604.

Step S604, discarding the SIP PUSH message, returning an error status code to the sending end, and ending.

Step S605, the normal processing flow of the SIP PUSH message is entered, that is, the message is parsed, provided to the upper layer application, or the SIP PUSH message is displayed.

In this embodiment, when the correct destination receiving end of the SIP PUSH message is checked, and not the correct destination receiving end of the SIP PUSH message, the SIP PUSH message is discarded, the privacy of the user is protected, and the SIP PUSH message is prevented from being incorrectly delivered. The resulting leakage of user privacy.

In addition, in this embodiment, by determining whether the SIP PUSH message carries the privacy protection identifier, whether to perform the check of the correct destination receiving end of the SIP PUSH message may be selected. For example, for an advertisement or an announcement type message sent by a PI, the privacy protection identifier may not be carried, and the SIP PUSH message is not discarded, but is normally viewed. For a SIP PUSH message with a high privacy requirement, the privacy protection identifier is carried. When the SIP PUSH message is incorrectly delivered, the received terminal is required to discard the message.

A SIP PUSH receiving end structure of the embodiment of the present invention is as shown in FIG. 7, and includes a privacy protection identifier identifying unit 71, a correct destination receiving end checking unit 72, a SIP PUSH message processing unit 73, and an error status code generating unit 74; The correct destination receiving end checking unit 72 is communicably connected to the privacy protection identifier identifying unit 71, the SIP PUSH message processing unit 73, and the error status code generating unit 74, respectively.

The privacy protection identifier identifying unit 71 is configured to determine whether to perform the check of the correct destination receiving end of the SIP PUSH message according to the privacy protection identifier carried in the SIP PUSH message; if the determination result is yes, the receiver checking unit 72 performs the SIP. The correct destination of the PUSH message is checked at the receiving end.

The correct destination receiving end checking unit 72 is configured to check whether it is the correct destination receiving end of the received SIP PUSH message; and transmits the checking result to the SIP PUSH message processing unit 73 and the error status code generating unit 74. The correct destination receiving end checking unit 72 further includes a message receiving subunit 721 and a destination identification detecting subunit 722, wherein the message receiving subunit 721 is communicatively coupled to the destination identification detecting subunit 722. The message receiving subunit 721 is configured to receive the SIP PUSH message and send the received SIP PUSH message to the destination identity detecting subunit 722. The destination identifier detecting sub-unit 722 is configured to detect whether the destination identifier carried in the SIP PUSH message is the same as the identifier of the SIP PUSH receiving end itself; if yes, the correct destination receiving end of the SIP PUSH message; The correct destination receiver of the SIP PUSH message. The destination identifier includes the destination address (the content in the To field) or the identifier of the destination terminal in the SIP PUSH message. The destination address may be a SIP URI or an MSISDN; the identifier of the destination terminal may be an IMSI or a device ID.

The message processing unit 73 is configured to process the SIP PUSH message according to the check result of the correct destination receiving end checking unit 72. If the result of the check is the correct destination receiving end of the SIP PUSH message, the normal processing flow of the SIP PUSH message is entered, The SIP PUSH message is parsed, provided to the upper layer application, or displayed to the SIP PUSH message; if the check result is not the correct destination receiving end of the SIP PUSH message, the SIP PUSH message is discarded.

The error status code generating unit 74 is configured to generate and return an error status code to the transmitting end based on the result of the check by the receiving end checking unit 72 for the correct purpose. If the result of the check is the correct destination receiving end of the SIP PUSH message, no operation is performed; if the check result is not the correct destination receiving end of the SIP PUSH message, an error status code is generated and returned to the transmitting end. After the SIP PUSH message sending end receives the error status code returned by the SIP PUSH receiving end, the SIP PUSH message sending end performs data retransmission according to the error status code.

A SIP PUSH message transmitting end of the embodiment of the present invention has a structure as shown in FIG. 8, and includes a SIP PUSH message generating unit 81 and an error status code processing unit 82, wherein the SIP PUSH message generating unit 81 is in communication with the error status code processing unit 82. .

The SIP PUSH message generating unit 81 is configured to generate and send a SIP PUSH message carrying a privacy protection identifier, where the privacy protection identifier is used to identify that the SIP PUSH receiving end performs the check of the correct destination receiving end of the SIP PUSH message. The error status code processing unit 82 is configured to perform retransmission of data based on the received error status code.

In addition, in this embodiment, by determining whether the SIP PUSH message carries the privacy protection identifier, whether to perform the check of the correct destination receiving end of the SIP PUSH message may be selected. For example, for an advertisement or an announcement type message sent by a PI, the privacy protection identifier may not be carried, and the SIP PUSH message is not discarded, but is normally viewed. For a SIP PUSH message with a high privacy requirement, the privacy protection identifier is carried. When the SIP PUSH message is incorrectly delivered, the received terminal is required to discard the message. The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It should be considered as the scope of protection of the present invention.

Claims

Rights request

A method for processing a session initiation protocol push message, characterized in that it comprises the following steps:

Receiving a session initiation protocol to push a SIP PUSH message;

Check whether the correct destination receiving end of the SIP PUSH message is; if not, discard the SIP PUSH message.

2. The method for processing a session initiation protocol push message according to claim 1, wherein if it is not the correct destination receiving end of the SIP PUSH message, the method further comprises: returning an error status code to the transmitting end.

The method for processing a session initiation protocol push message according to claim 1, wherein after receiving the SIP PUSH message, the method further comprises: performing SIP PUSH according to whether the SIP PUSH message carries a privacy protection identifier The judgment of the correct destination of the message is checked; if the SIP PUSH message carries the privacy protection identifier, the correct destination receiver of the SIP PUSH message is checked.

The method for processing a session initiation protocol push message according to claim 1, wherein the checking is a correct destination receiving end of the SIP PUSH message, and specifically includes:

Determining whether the identity of the SIP PUSH message is the same as the destination identifier carried in the SIP PUSH message; if yes, the correct destination receiving end of the SIP PUSH message; otherwise, it is not the correct destination receiving end of the SIP PUSH message.

The method for processing a session initiation protocol push message according to claim 4, wherein the destination identifier includes a destination address in the SIP PUSH message or an identifier of the destination terminal; and the destination address includes a session initialization protocol uniform resource identifier. The SIP URI or the mobile station international subscriber directory number MSISDN; the identity of the destination terminal includes an International Mobile Subscriber Identity (IMSI) or a device identifier.

The method for processing a session initiation protocol push message according to claim 1, wherein, if it is the correct destination receiving end of the SIP PUSH message, performing message parsing, providing to the upper layer application, or displaying the SIP PUSH message. .

7. A SIP PUSH receiving end, comprising: a correct destination receiving end checking unit and a SIP PUSH message processing unit;

The correct destination receiving end checking unit is configured to check whether it is the correct destination receiving end of the received SIP PUSH message;

The message processing unit is configured to process the SIP PUSH message according to the check result of the correct destination receiving end checking unit.

8. The SIP PUSH receiving end according to claim 7, wherein the correct destination receiving end checking unit comprises a message receiving subunit and a destination identifier detecting subunit; and the message receiving subunit is configured to receive a SIP PUSH message. And sending the received SIP PUSH message to the destination identifier detecting subunit;

The destination identifier detecting subunit is configured to detect whether the destination identifier carried in the SIP PUSH message is the same as the identifier of the SIP PUSH receiving end itself.

The SIP PUSH receiving end according to claim 8, wherein the destination identifier includes a destination address in the SIP PUSH message or an identifier of the destination terminal; and the destination address includes a session initiation protocol uniform resource identifier SIP URI or The mobile station international subscriber directory number MSISDN; the identifier of the destination terminal includes an International Mobile Subscriber Identity (IMSI) or a device identifier.

The SIP PUSH receiving end according to claim 7, further comprising an error status code generating unit, configured to generate and return an error status code to the transmitting end according to the checking result of the correct destination receiving end checking unit.

The SIP PUSH receiving end according to claim 7, further comprising a privacy protection identifier identifying unit, configured to perform correct destination receiving of the SIP PUSH message according to the privacy protection identifier carried in the SIP PUSH message The judgment of the end of the inspection.

12. A SIP PUSH message sending end, comprising: a SIP PUSH message generating unit, configured to generate and send a SIP PUSH message carrying a privacy protection identifier, where the privacy protection identifier is used to identify a SIP PUSH receiving end. The correct destination of the SIP PUSH message is checked at the receiving end.

13. The SIP PUSH message transmitting end according to claim 12, wherein: An error status code processing unit is further included for performing retransmission of data according to the received error status code.