WO2009026842A1 - Procédé et dispositif de traitement de la messagerie instantanée du protocole d'initiation de session - Google Patents

Procédé et dispositif de traitement de la messagerie instantanée du protocole d'initiation de session Download PDF

Info

Publication number
WO2009026842A1
WO2009026842A1 PCT/CN2008/072110 CN2008072110W WO2009026842A1 WO 2009026842 A1 WO2009026842 A1 WO 2009026842A1 CN 2008072110 W CN2008072110 W CN 2008072110W WO 2009026842 A1 WO2009026842 A1 WO 2009026842A1
Authority
WO
WIPO (PCT)
Prior art keywords
push message
sip
sip push
receiving end
destination
Prior art date
Application number
PCT/CN2008/072110
Other languages
English (en)
Chinese (zh)
Inventor
Jian Yang
Lei Wang
Guoqiao Chen
Shunan Fan
Huiping Zhang
Ting Dong
Zheng Wang
Hao Wang
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009026842A1 publication Critical patent/WO2009026842A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • 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.
  • SIP Session Initiation Protocol
  • PUSH Pushing
  • 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.
  • the PI PUSH Initiator, PUSH initiator
  • the PPG PUSH Proxy Gateway, PUSH Proxy Gateway
  • 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.
  • 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).
  • FIG. 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.
  • 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.
  • Step S213 The SIP/IP Core network forwards the response report to the PUSH sending proxy.
  • 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.
  • 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.
  • the SIP/IP Core may deliver the SIP PUSH message to a terminal other than the destination PUSH receiver.
  • 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.
  • 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.
  • 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 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.
  • the embodiment of the invention has the following advantages:
  • 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.
  • FIG. 1 is a schematic diagram of an architecture of a SIP PUSH in the prior art
  • FIG. 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
  • the SIP PUSH receiving end 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.
  • the embodiment of the present invention receives the SIP PUSH message to the PUSH in the SIP/IP Core network.
  • the SIP PUSH receiving end 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.
  • the SIP PUSH message sending 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.
  • the SIP PUSH message sending end may be requested to retransmit the data.
  • the SIP PUSH receiving end 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.
  • the privacy protection identifier may not be carried, and the SIP PUSH message is not discarded, but is normally viewed.
  • the privacy protection identifier is carried.
  • the received terminal is required to discard the message.
  • 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.
  • the SIP PUSH message sending 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.
  • the SIP PUSH message 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.
  • the SIP PUSH message sending end may be requested to retransmit the data.
  • 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.
  • the SIP PUSH message sending end may be requested to retransmit the data.
  • the privacy protection identifier may not be carried, and the SIP PUSH message is not discarded, but is normally viewed.
  • the privacy protection identifier is carried.
  • the received terminal is required to discard the message.

Abstract

L'invention concerne un procédé de traitement de la messagerie instantanée du protocole d'initiation de session (SIP PUSH). La messagerie SIP PUSH est reçue en premier lieu; s'il s'agit de la destination correcte, le destinataire du message SIP PUSH est vérifié en second lieu; dans le cas contraire, la messagerie SIP PUSH est ignorée. L'invention concerne en outre un destinataire SIP PUSH et un expéditeur de messagerie SIP PUSH. La confidentialité de l'utilisateur est protégée par vérification du destinataire de la destination correcte de la messagerie SIP PUSH, et ignorance de la messagerie SIP PUSH s'il ne s'agit pas du destinataire de la destination correcte de la messagerie SIP PUSH.
PCT/CN2008/072110 2007-08-23 2008-08-22 Procédé et dispositif de traitement de la messagerie instantanée du protocole d'initiation de session WO2009026842A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710147350.0 2007-08-23
CN200710147350.0A CN101374267B (zh) 2007-08-23 2007-08-23 一种会话初始化协议推送消息的处理方法及装置

Publications (1)

Publication Number Publication Date
WO2009026842A1 true WO2009026842A1 (fr) 2009-03-05

Family

ID=40386704

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072110 WO2009026842A1 (fr) 2007-08-23 2008-08-22 Procédé et dispositif de traitement de la messagerie instantanée du protocole d'initiation de session

Country Status (2)

Country Link
CN (1) CN101374267B (fr)
WO (1) WO2009026842A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103200229A (zh) * 2013-02-28 2013-07-10 北京百度网讯科技有限公司 推送信息的处理方法及设备、浏览器、浏览器插件
CN104767746B (zh) * 2015-03-26 2018-05-01 上海大唐移动通信设备有限公司 推送消息接收方法、消息推送方法、客户端及服务器

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10133884A1 (de) * 2001-07-12 2003-01-30 Materna Gmbh Information & Com Verfahren und System zur Abwicklung bargeldloser Zahlungen
US20040203581A1 (en) * 2002-10-07 2004-10-14 Msafe Ltd. Method system and device for monitoring data pushed to a wireless communication device
CN1870601A (zh) * 2005-05-27 2006-11-29 佛山市顺德区顺达电脑厂有限公司 推播信息接收方法与具有信息过滤功能的携带式电子装置
CN1889562A (zh) * 2005-06-28 2007-01-03 华为技术有限公司 对接收初始会话协议请求消息的设备进行认证的方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7765316B1 (en) * 2000-10-10 2010-07-27 Intel Corporation Scheduling the uploading of information from a client to a server
CN1859723A (zh) * 2005-05-02 2006-11-08 北京三星通信技术研究有限公司 支持合并的电路域呼叫与ims会话的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10133884A1 (de) * 2001-07-12 2003-01-30 Materna Gmbh Information & Com Verfahren und System zur Abwicklung bargeldloser Zahlungen
US20040203581A1 (en) * 2002-10-07 2004-10-14 Msafe Ltd. Method system and device for monitoring data pushed to a wireless communication device
CN1870601A (zh) * 2005-05-27 2006-11-29 佛山市顺德区顺达电脑厂有限公司 推播信息接收方法与具有信息过滤功能的携带式电子装置
CN1889562A (zh) * 2005-06-28 2007-01-03 华为技术有限公司 对接收初始会话协议请求消息的设备进行认证的方法

Also Published As

Publication number Publication date
CN101374267A (zh) 2009-02-25
CN101374267B (zh) 2011-04-20

Similar Documents

Publication Publication Date Title
KR101106926B1 (ko) 단문 메시지 세션 설정 프로토콜에서의 제출 리포트 처리 방법 및 장치와 컴퓨터 판독가능한 매체
US8170590B2 (en) Method, system and apparatus for forking transmission of short message service
JP5650748B2 (ja) コンバージドｉｐメッセージング（ｃｐｍ）とショートメッセージサービス（ｓｍｓ）との間のインターワーキングサービスを提供するための方法及びインターネットプロトコルショートメッセージゲートウェイ（ｉｐ−ｓｍ−ｇｗ）
CA2568599A1 (fr) Transmission des capacites d'un terminal pour la prise en charge d'un service de messages courts
JP2012253783A (ja) 統合ｉｐメッセージングサービスにおけるメッセージスレッドを管理する方法及びシステム
JP2008507861A5 (fr)
US10868780B2 (en) Method of notifying a sender of an inability to deliver a message to an unreachable terminal
EP1677551B1 (fr) Système, appareil et procédé pour améliorer un terminal de communication mobile en service "Push-to-talk"
US20070184868A1 (en) Apparatus, and associated method, for notifying, delivering, and deleting media bursts communicated in a push-to-talk over cellular communication system
EP2227044A1 (fr) Procédé, équipement d'éléments de réseau et système réseau pour la notification d'état de distribution de message instantané
EP2146511A1 (fr) Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie
EP2224652B1 (fr) Procédé, système, serveur et terminal destinés à annuler un message de type push
US8656001B2 (en) Communication system, application server and communication method for server cooperation
JP4940335B2 (ja) 電話交換装置及び電話端末及び電話システムで使用される制御方法
US20130097331A1 (en) Submit Report Handling In SMSIP
US20100306349A1 (en) Method and System for Configuring Service on Terminal
US8644153B2 (en) Infrastructure for mediation device to mediation device communication
CN101584202A (zh) 基于会话发起协议(sip)的用户平面位置服务
WO2009026842A1 (fr) Procédé et dispositif de traitement de la messagerie instantanée du protocole d'initiation de session
JP4541333B2 (ja) 端末装置、システム、方法、及びプログラム
WO2007033552A1 (fr) Procede pour traiter le message dans le service de message multimedia et systeme y afferant
EP2445262A1 (fr) Système et procédé de routage de messages instantanés
KR100604723B1 (ko) 데이터 버스트 메시지를 이용한 멀티미디어 데이터 수신확인 및 읽기 확인 서비스 제공 방법 및 시스템
KR20120056987A (ko) Ｆｍｃ 통신 기반의 호 설정 방법 및 호 연결 인프라
WO2007053999A1 (fr) Méthode et système de réalisation de la fonction message court de terminal sip

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: 08784101

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: 08784101

Country of ref document: EP

Kind code of ref document: A1