WO2012088907A1 - 一种ip多媒体子系统及其恢复用户订阅关系的方法 - Google Patents

一种ip多媒体子系统及其恢复用户订阅关系的方法 Download PDF

Info

Publication number
WO2012088907A1
WO2012088907A1 PCT/CN2011/078968 CN2011078968W WO2012088907A1 WO 2012088907 A1 WO2012088907 A1 WO 2012088907A1 CN 2011078968 W CN2011078968 W CN 2011078968W WO 2012088907 A1 WO2012088907 A1 WO 2012088907A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
server
client
sent
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2011/078968
Other languages
English (en)
French (fr)
Inventor
崔丕锁
陆剑峰
梁斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP11854360.2A priority Critical patent/EP2661043B1/en
Publication of WO2012088907A1 publication Critical patent/WO2012088907A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • 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/1073—Registration or de-registration
    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • 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/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an IP multimedia subsystem and a method for restoring a user subscription relationship.
  • the IP Multimedia Subsystem is the standard for the next generation network defined by the Third Generation Partnership Probect (3GPP). Its distinguishing feature is the use of the Session Initiation Protocol (Session). Initiation Protocol (SIP) system, communication and access-independent, with a variety of service integration capabilities, in line with the trend of communication network convergence development.
  • Session Session Initiation Protocol
  • IP Initiation Protocol
  • Presence is a business capability that allows users to post their own Presence information, allowing users to query the Presence information of another user, or by successfully subscribing to another user's Presence information. After the Presence information is changed, the user is notified of the change of the subscribed information.
  • the client also known as the watcher, such as the user terminal
  • the Presence information can subscribe to the Presence information according to the subscription list (RLS) configured by itself
  • the presence server Presence Server
  • Subscribe to the notification message Subscribe to the notification message (Notify message).
  • the client and the stateful presentation service need to communicate through multiple network elements, there is a possibility of losing the Notify or Notify response, and there is also the possibility of returning an incorrect response by a certain network element due to an abnormal error.
  • the subscription belongs to the session class message when the Notify fails to end the session, subsequent changes can not be notified, which will have a great impact on the user's use of the service and a very bad experience, for example, their friends are obviously online. But the display on your own client is still offline and so on.
  • the object of the present invention is to provide an IP multimedia subsystem and a method for restoring a user subscription relationship, which are used to solve the problem of how to restore a subscription relationship after a server fails to send a subscription notification message to a client in a user subscription process in the IP multimedia subsystem. problem.
  • the present invention provides a method for restoring a user subscription relationship in an IP multimedia subsystem, including:
  • a subscription request is sent to the server, and after receiving the subscription request, the server sends a subscription notification message to the client.
  • the server After sending the subscription notification message, if the server fails to send the subscription notification message, the server sends an instant message to the client to notify that the subscription notification message fails to be sent;
  • the client learns that the subscription notification message fails to be sent, and initiates a subscription request to the server.
  • the subscription objects in the client-initiated subscription request include: friend status information, and/or subscription information, and/or registration status information.
  • the method further includes: the server is configured to notify that the delivered subscription notification message fails to be sent in the following manner: after receiving the subscription notification message, the response returned by the client is not received, or a response other than 2XX is received.
  • the server is configured with a threshold for the number of times the instant message is sent.
  • the method further includes: if the number of times the instant message is sent reaches the configured threshold, the server deletes the user registration information, signs the client, and signs the The administrator performs an alarm; and if the number of times the instant message is sent does not reach the configured threshold, the server continues to send an instant message to notify the client that the subscription notification message fails to be sent.
  • the server refers to a server capable of processing a subscription request in an IP multimedia subsystem service, including: a status presentation server, a group management server, and an instant message server;
  • the client refers to the user's terminal, including computers, mobile phones, and personal digital assistant PDA devices.
  • the present invention also provides an IP multimedia subsystem, including: a client, a server, and an IMS core network, where the client interacts with the server through the IMS core network, where:
  • the client is set to initiate a subscription request to the server after the registration is successful;
  • the server is configured to send a subscription notification message to the client after receiving the subscription request, and send an instant message to the client if the subscription notification message sent by the client fails to be sent after the subscription notification message is sent.
  • the method for notifying the client that the subscription notification message is sent fails;
  • the client is further configured to re-initiate a subscription request to the server after receiving the instant message to learn that the subscription notification message fails to be sent.
  • the subscription objects in the client-initiated subscription request include: friend status information, and/or subscription information, and/or registration status information.
  • the server is further configured to notify that the issued subscription notification message fails to be sent in the following manner: After receiving the subscription notification message, the response returned by the client is not received, or a response of the non-2XX is received.
  • the server is configured with a threshold for sending an instant message; the server is further configured to: if the number of times the instant message is sent reaches the configured threshold, delete the user registration information, sign the client, and And alerting the administrator; and if the number of times the instant message is sent does not reach the configured threshold, the instant message is continuously sent to notify the client that the subscription notification message fails to be sent.
  • the server refers to a server capable of processing a subscription request in an IP multimedia subsystem service, including: a status presentation server, a group management server, and an instant message server;
  • the client refers to the user's terminal, including computers, mobile phones, and personal digital assistant PDA devices.
  • the IP multimedia subsystem of the present invention and the method for restoring the user's subscription relationship may notify the client that the subscription notification message fails to be sent by sending an instant message (Message) after the server fails to send the subscription notification message; the client may then re-send Initiating a subscription request to restore the subscription to related objects, thereby improving the user experience and enhancing the user's use effect.
  • Message instant message
  • FIG. 1 is a schematic diagram of a user login, subscription, and notification in an IMS service in the prior art
  • FIG. 2 is a schematic diagram of an IMS system for restoring a user subscription and its interaction in the embodiment of the present invention
  • FIG. 3 is a schematic diagram of the embodiment of the present invention
  • FIG. 4 is a schematic diagram of signaling interaction of a status presentation server in a specific application scenario to notify a user terminal to resume a subscription session after failing to send a notification message.
  • the server learns that the subscription notification message sent to the client fails to be sent
  • the session message is sent to the client (also called the observer, ie, the user terminal) after the session is deleted.
  • the instant message notifies the client that the subscription session failed, and hopes that the client resumes the session and re-establishes the subscription relationship. This allows the user to eliminate the serious consequences of the client's failure to obtain the notification of the Notify message as soon as the user fails to send the subscription notification message (Notify).
  • the server refers to a server capable of processing a subscription request in an IMS service.
  • the server is usually a status presentation server, a group management server, or an instant message server.
  • the subscription function is supported. The subscription request is restored in accordance with the present invention.
  • the client refers to a user's terminal, including but not limited to a computer, a mobile phone, and a personal digital assistant PDA.
  • the communication protocol may be a SIP (Session Initiation Protocol) protocol or an XCAP (XML Configuration Access Protocol) protocol.
  • SIP Session Initiation Protocol
  • XCAP XML Configuration Access Protocol
  • FIG. 2 in an embodiment of the present invention, an IP multimedia subsystem is provided for restoring a user subscription relationship, and the IP multimedia subsystem includes: a client, a server, and an IMS core network.
  • the client communicates with the server through the IMS core network.
  • the client is an instant messaging client, which can be a customized terminal, and can communicate with a server such as a status presentation server or another service server through a standard protocol.
  • the client initiates a registration request, and after the registration is successful, a subscription request is initiated, and the server returns a successful response after receiving the subscription request, and simultaneously sends a subscription notification message (Notify);
  • the server After the server fails to send the notification notification message (Notify), the server sends an instant message (Message) to the client to notify the client that the subscription notification message (Notify) is failed to be sent; further, the client receives the message.
  • the instant message (Message) After the notification notification message (Notify) fails to be sent, the new subscription request is resent.
  • the subscription objects in the subscription request include: friend status information, subscribed information, and/or registration status information.
  • the server fails to send a subscription notification message (Notify) to send a subscription notification message (Notify), and does not receive a response returned by the client, or receives a non-2XX response.
  • a threshold value for sending an instant message (Message) notification number may be set, which is used to limit the upper limit of the number of transmissions. If a user sends an instant message (Message) notification number that does not reach the specified threshold during the registration period, an instant message (Message) message may be sent; if the specified threshold value has been reached, the process ends. The message message is no longer sent.
  • a method for notifying a client to subscribe to a notification message (Notify) in the present embodiment of the present invention includes the following steps:
  • Step S1 The client initiates a registration request, and after the registration succeeds, the subscription request is initiated.
  • the server After receiving the subscription request, the server returns a successful response, and sends a subscription notification message (Notify) related information to the client.
  • the subscription object includes: The information is subscribed to the information and/or the registration status information, etc.; Step S2, if the notification notification message (Notify) is sent, the server is notified that the subscription notification message (Notify) fails to be sent (ie, the Notify response returned by the client is not received, or the notification is received. Go to the non-2XX response) Delete the session and send an instant message (Message) to the client to notify the client.
  • the sent subscription notification message (Notify) fails to be sent; after receiving the Message message, the client resends the subscription request according to the related information;
  • the notification of the subscription notification message fails, and the response may be a Notify timeout, or a non-2XX response such as 3XX, 4XX, or 5XX is received, and the processing procedure of the related error provided by the related protocol needs to be processed. This is not a problem of concern in the present invention and will not be described here;
  • the server After the client re-initiates the subscription, the server re-issues the subscription notification message (Notify); if the notification of the subscription notification message (Notify) is successful, the client can continue to maintain the subscription session; If the result is unsuccessful, you need to re-execute this step until the number of times the message is delivered reaches the maximum number of allowed delivery.
  • the upper limit of the number of messages sent here is specified by the service side.
  • Step S3 If a user does not reach the specified upper limit when the number of times the message is sent by the server during the registration period, the process returns to step S2 and continues to deliver the message; if the upper limit is reached, the process ends.
  • the notification to the client is discarded, the user registration information is deleted, the client is signed off, and an alarm is issued to the administrator.
  • the server can choose to prohibit the user from logging in, or you can choose to delete only the subscription session. If only the subscription session is deleted, the client cannot obtain the notification of the change of the subscription information afterwards.
  • the upper limit of the number of times the message notification is allowed to be sent is determined by the service side in the IMS.
  • the client After the above-mentioned technical solution about the IMS system and the recovery subscription relationship, after the server sends a Notify notification failure, the client notifies the client that the Notify notification fails by sending a Message message, and the client can then re-initiate the subscription request to restore the related object.
  • the subscription which improves the user experience and increases the user's use.
  • FIG. 4 is a schematic diagram of a process of restoring a subscription session after the Notify notification fails in the IMS system in which the state presentation server is used as the server.
  • the IP multimedia subsystem shown in FIG. 4 is used for restoring a user subscription relationship.
  • the IP multimedia subsystem includes: a user terminal, a status presentation server, and an IMS core network.
  • User terminal pass The IMS core network communicates with the status presentation server, and the user terminal is an instant messaging client, which can be a customized terminal, and can communicate with a status presentation server or other service server through a standard protocol.
  • the user terminal initiates a registration request, and after the registration is successful, initiates a subscription request, and the status presentation server returns a success response after receiving the subscription request, and simultaneously sends a subscription notification message (Notify) related information;
  • the status presentation server learns that the subscription notification message (Notify) failed to be sent, the status message is sent to the user terminal to notify the subscription notification message (Notify) that the transmission failed.
  • the user terminal learns that the subscription notification message (Notify) fails to send, and then resends the new subscription request.
  • the subscription objects include but are not limited to: friend status information, subscribed information, and/or registration status information.
  • the status presentation server is notified that the Notify notification is sent, and the status presentation server does not receive the response returned by the user terminal after receiving the Notify notification, or receives a response other than 2XX.
  • the upper limit value of the number of times the message message is sent may be set. If a user does not reach the specified upper limit when the number of the message notifications sent by the server is within the registration period, the message message may be sent; if the upper limit is reached, the message ends. , no longer send a Message message.
  • the status presentation server notifies the user terminal that the subscription notification message (Notify) fails to be sent, including:
  • Step 401 The user terminal UE initiates a registration request, and after the registration is successful, a subscription request is initiated. After receiving the subscription request, the status presentation server returns a success response, and sends a Notify notification related information to the user terminal.
  • the subscription object includes: friend status information, Subscription information and/or registration status information, etc.;
  • Step 402 If the status notification server fails to receive the Notify notification after receiving the Notify notification (the Notify response is not received by the user terminal, or the non-2XX response is received), the session is deleted, and the message message is sent to the user terminal to notify the user terminal.
  • the Notify notification sent is failed; after receiving the Message message, the user terminal resends the new subscription request according to the related information;
  • the failure of the Notify notification may be a Notify timeout, or a response of the 3XX, 4XX, or 5XX, and the processing of the related error provided by the related protocol is required to be processed. This is not a problem of the present invention. This will not be repeated here;
  • the server After the user terminal re-initiates the subscription, the server re-issues the Notify notification message; if the Notify notification is successful, the user terminal can continue to maintain the subscription session; if the notification is still unsuccessful, this step needs to be performed again until the next step.
  • the number of times the message is sent reaches the maximum number of times the message is allowed to be delivered. The upper limit of the number of times the message is sent is specified by the service side.
  • Step 403 If the number of times the status message is sent by the status presentation server does not reach the specified upper limit, the process returns to step 402 and continues to send the message; if the upper limit is reached, the process ends.
  • the presence server can choose to disable user logins, or it can choose to only delete subscription sessions. If only the subscription session is deleted, the client cannot obtain the notification of the change of the subscription information after this.
  • the upper limit of the number of times the message notification is allowed to be sent is determined by the service side in the IMS.
  • the notification message is notified to the observer to notify the failure, and the user terminal can then re-initiate the subscription request to resume the subscription to the related object. , thereby improving the user experience and increasing the user's use effect.
  • the user terminal is successfully registered, and the subscription is successful.
  • the message is sent to notify the user terminal that the subscription is re-initiated, and the status presentation server sends the Notify process again.
  • Step 1 - Step 2 The user terminal completes registration on the IMS core network, and the core network completes the third party registration on the status presentation server;
  • Step 3 - Step 6 The user terminal sends a subscription, and the status presentation server returns a successful subscription.
  • C. Step 7 - Step 8 the status presentation server sends a Notify message, but does not receive a corresponding response, that is, the Notify notification fails to be sent;
  • Step 9 - Step 12 the status presentation server sends a message request, notifying the user terminal, and the user terminal returns a response;
  • step 13-step 16 the user terminal resends the subscription, and the status presentation server returns a successful response to the subscription;
  • Step 17 - Step 20 the status presentation server delivers the Notify message again, and receives a successful response.
  • the present invention may notify the client that the subscription notification message fails to be sent by sending an instant message (Message) after the server fails to send the subscription notification message; the client may then re-initiate the subscription request to restore the related object.
  • Message instant message
  • the subscription which improves the user experience and enhances the user's use.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

一种 IP多媒体子系统及其恢复用户订阅关系的方法
技术领域
本发明涉及通信技术领域， 尤其涉及一种 IP多媒体子系统及其恢复用户 订阅关系的方法。
背景技术
IP多媒体子系统（ IMS , IP Multimedia Subsystem )是第三代合作伙伴组 织 （ Third Generation Partnership Proj ect , 简称 3 GPP )定义的下一代网络的标 准， 它的显著特点是釆用了会话发起协议（Session Initiation Protocol, 简称 SIP )体系， 通讯与接入无关， 具备多种业务融合能力， 顺应了通讯网融合发 展的趋势。
状态呈现（Presence, 简写为 PRS )是一种业务能力， 它允许用户发布自 己的 Presence信息， 允许用户查询另一个用户的 Presence信息， 或者通过成 功订阅另一个用户的 Presence信息而在另一个用户的 Presence信息改变后向 该用户通知已订阅信息的变化。
在目前的实际应用中， 客户端（也称观察者 Watcher, 例如用户终端）可 以根据自己配置的订阅列表 ( RLS )来订阅 （Subscribe ) Presence信息， 状态 呈现服务器（Presence Server )可以针对订阅事件发送订阅通知消息 （Notify 消息） 。 但是因为客户端和状态呈现服务之间需要通过多个网元进行通讯， 这就存在着丟失 Notify或者 Notify响应的可能性， 也存在着因异常错误而由 某个网元返回错误的响应的可能性； 同时因为订阅属于会话类消息， 当 Notify 失败结束会话后， 后继相关的变化无法通知， 将对用户使用业务造成很大的 影响和非常不好的体验， 比如， 自己的好友明明已经上线， 但是在自己的客 户端显示仍然离线等。
因此， IP多媒体子系统的订阅过程中，服务端向客户端发送订阅通知消 息 （Notify ) 失败后， 如何恢复用户订阅关系成为需要解决的技术问题。 发明内容
本发明的目的是提供一种 IP 多媒体子系统及其恢复用户订阅关系的方 法， 用于解决 IP多媒体子系统中用户订阅过程中， 服务端向客户端发送订阅 通知消息失败后如何恢复订阅关系的问题。
为了解决上述问题， 本发明提出了一种 IP多媒体子系统中恢复用户订阅 关系的方法， 包括：
客户端注册成功后向服务端发起订阅请求， 服务端收到所述订阅请求后 向客户端发送订阅通知消息；
服务端在发送订阅通知消息后， 若获知下发的订阅通知消息发送失败， 则向客户端发送即时消息用以通知所述订阅通知消息发送失败； 以及
所述客户端收到所述即时消息后获知所述订阅通知消息发送失败， 重新 向服务端发起订阅请求。
所述客户端发起的订阅请求中的订阅对象包括： 好友状态信息、 和 /或被 订阅信息， 和 /或注册状态信息。
该方法还包括： 所述服务端通过如下方式获知下发的订阅通知消息发送 失败： 在发送订阅通知消息后未收到客户端返回的响应， 或者收到了非 2XX 的响应。
所述服务端配置有发送即时消息的次数的门限值； 该方法还包括： 如果 发送即时消息的次数达到配置的门限值， 则服务端删除用户注册信息， 签退 该客户端， 并向管理员进行告警； 以及， 如果发送即时消息的次数未达到配 置的门限值， 则服务端继续发送即时消息用以通知客户端所述订阅通知消息 发送失败。
所述服务端是指在 IP多媒体子系统业务中能够处理订阅请求的服务器， 包括： 状态呈现服务器、 群组管理服务器和即时消息服务器；
所述客户端是指用户的终端，包括电脑、手机和个人数字助理 PDA设备。 本发明还提供一种 IP多媒体子系统， 包括： 客户端、服务端和 IMS核心 网， 所述客户端通过 IMS核心网与服务端交互， 其中：
客户端设置成在注册成功后向服务端发起订阅请求；
服务端设置成： 在收到所述订阅请求后向客户端发送订阅通知消息， 并 在发送所述订阅通知消息后若获知下发的所述订阅通知消息发送失败， 则向 客户端发送即时消息用以通知客户端所述订阅通知消息发送失败；
所述客户端还设置成在收到即时消息获知所述订阅通知消息发送失败 后， 重新向所述服务端发起订阅请求。
所述客户端发起的订阅请求中的订阅对象包括： 好友状态信息、 和 /或被 订阅信息， 和 /或注册状态信息。
所述服务端还设置成通过如下方式获知下发的订阅通知消息发送失败： 在发送订阅通知消息后未收到客户端返回的响应，或者收到了非 2XX的响应。
所述服务端配置有发送即时消息的次数的门限值；所述服务端还设置成： 如果发送即时消息的次数达到配置的门限值， 则删除用户注册信息， 签退该 客户端， 并向管理员进行告警； 以及， 如果发送即时消息的次数未达到配置 的门限值，则继续发送即时消息用以通知客户端所述订阅通知消息发送失败。
所述服务端是指在 IP多媒体子系统业务中能够处理订阅请求的服务器， 包括： 状态呈现服务器、 群组管理服务器和即时消息服务器；
所述客户端是指用户的终端，包括电脑、手机和个人数字助理 PDA设备。
本发明的 IP多媒体子系统及其恢复用户订阅关系的方法， 可在服务端下 发订阅通知消息失败后， 通过下发即时消息（ Message )通知客户端订阅通知 消息发送失败； 客户端随后可以重新发起订阅请求恢复对相关对象的订阅， 从而提高了用户的体验度， 增强了用户的使用效果。 附图概述
此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中：
图 1是现有技术中用户在 IMS业务中登录注册、 订阅和通知的示意图； 图 2是本发明实施例中用于恢复用户订阅的 IMS系统及其交互示意图； 图 3是本发明实施例中用于通知客户端的订阅通知消息发送失败后恢复 订阅会话的流程图；
图 4是根据本发明实施例中的一种具体应用场景下状态呈现服务器通知 用户终端订阅通知消息发送失败后恢复订阅会话的信令交互示意图。
本发明的较佳实施方式
为使本发明的目的、 技术方案和优点更加清楚， 以下结合附图对本发明 作进一步地详细说明。 需要注意的是， 提供以下的优选实施例以提供对本发 明的全面和透彻理解， 而不是对本发明进行任何限制。
本发明的技术方案中用于恢复订阅会话的主要思路为：
在服务端（例如， 状态呈现服务器 PS )获知发送给客户端的订阅通知消 息发送失败， 则删除会话后发起即时消息（Message消息）发送至客户端（也 称观察者， 即用户终端） ， 通过该即时消息通知客户端订阅会话失败， 希望 客户端恢复会话， 重新建立订阅关系。 这就使得用户在服务端下发订阅通知 消息 （Notify ) 失败后， 能够尽快消除客户端无法获得订阅通知（Notify )信 息的严重后果。
所述服务端是指在 IMS业务中能够处理订阅请求的服务器。 在 IMS业 务中， 服务端通常为状态呈现服务器、 群组管理服务器或即时消息服务器等 等， 对于每一个业务服务器， 如果存在某些信息需要给客户端实时通知， 则 都会支持订阅功能， 都可以依据本发明对订阅请求进行恢复。
所述客户端是指用户的终端， 包括但不局限于电脑、 手机和个人数字助 理 PDA等设备， 这些设备中只要能够接入 IMS网络， 能够通过标准通讯协 议进行通讯的客户端都可以认为是本发明的客户端。 所述通信协议可以是 SIP (会话初始协议， Session Initiation Protocol)协议或 XCAP ( XML配置访问协 议, XML Configuration Access Protocol )协议。 如图 2所示， 本发明的实施例中， 提供了一种 IP多媒体子系统， 用于恢 复用户订阅关系，该 IP多媒体子系统， 包括：客户端，服务端和 IMS核心网。 客户端通过 IMS核心网与服务端进行通信联络， 所述客户端是即时通讯客户 端， 可以是定制终端， 可与状态呈现服务器或者其他业务服务器等服务端通 过标准协议进行通讯。
在所述 IP多媒体子系统中， 客户端发起注册请求， 注册成功后发起订阅 请求，服务端收到订阅请求后返回成功响应，同时发送订阅通知消息（ Notify );
服务端在获知订阅通知消息（Notify )发送失败后， 向客户端发送即时消 息（Message )用以通知所述客户端下发的订阅通知消息（Notify )发送失败； 进一步地， 客户端在收到即时消息 （Message )后， 获知订阅通知消息 ( Notify )发送失败后， 重新发送新的订阅请求。
其中， 订阅请求中的订阅对象包括： 好友状态信息、 被订阅信息和 /或注 册状态信息等。
其中， 所述服务端在获知订阅通知消息（Notify )发送失败， 是指服务端 发送订阅通知消息 （Notify )后， 未收到客户端返回的响应， 或者收到了非 2XX的响应。
进一步地， 可以设置下发即时消息（Message )通知次数的门限值， 用于 限制发送的上限次数。 如果一个用户在注册期间， 服务端下发即时消息 ( Message )通知次数未达到规定的门限值时， 则可发送即时消息（ Message ) 消息； 若已达到规定的门限值时， 则结束， 不再下发 Message消息。
如图 3所示，本发明本实施例中的一种通知客户端订阅通知消息（Notify ) 发送失败的方法， 包括以下步骤：
步骤 S1 , 客户端发起注册请求， 注册成功后发起订阅请求， 服务端收到 订阅请求后返回成功响应， 同时向客户端发送订阅通知消息（ Notify )相关信 息； 其中， 订阅对象包括： 好友状态信息、被订阅信息和 /或注册状态信息等； 步骤 S2 , 如果发送订阅通知消息 （Notify )后， 服务端获知订阅通知消 息（ Notify )发送失败（即没有收到客户端返回的 Notify响应， 或者收到了非 2XX 的响应） 则删除会话， 向客户端发送即时消息 （Message )通知客户端 所述发送的订阅通知消息（Notify )发送失败； 客户端收到 Message消息后根 据相关信息重新发送订阅请求；
其中， 所述订阅通知消息 （Notify )发送失败， 有可以能是 Notify超时， 或者收到 3XX、 4XX或 5XX等非 2XX的响应， 需要按照相关的协议提供的 相关错误的处理流程说明进行处理， 这不是本发明关注的问题， 在此不再赘 述；
其中，客户端重新发起订阅后，服务端重新下发订阅通知消息（ Notify )； 如果本次下发订阅通知消息（Notify )通知成功， 则客户端可以继续保持该订 阅会话； 如果本次通知仍不成功， 需要重新执行本步骤直到下发 Message次 数达到允许下发的次数上限。此处下发 Message次数的上限是由业务侧规定。
步骤 S3 , 如果一个用户在注册期间， 服务端下发 Message消息通知的次 数未达到规定的上限值时， 返回步骤 S2 , 继续下发 Message消息； 若达到上 限则结束。
进一步地， 如果一个用户在注册期间， 服务端发送 Message的次数达到 规定的上限值， 则放弃对客户端的通知， 删除用户注册信息， 签退客户端， 并向管理员进行告警。
此时， 服务端可以选择禁止用户登录， 也可以选择只删除订阅会话。 如 果只删除订阅会话， 客户端无法获得之后的本次订阅信息的变化通知。 所述 允许发送 Message通知的次数上限值由 IMS中的业务侧决定。
通过上述的关于 IMS系统及其恢复订阅关系的技术方案， 在服务端下发 Notify通知失败后， 通过下发 Message消息通知客户端该 Notify通知失败， 客户端随后可以重新发起订阅请求恢复对相关对象的订阅， 从而提高了用户 的体验度， 增加了用户的使用效果。
下面以状态呈现服务器作为服务端的应用实例进行进一步的说明。
图 4是状态呈现服务器作为服务端的 IMS系统中， 在 Notify通知失败后 恢复订阅会话的流程示意图。
图 4所示的一种 IP多媒体子系统， 用于恢复用户订阅关系， 该 IP多媒 体子系统， 包括： 用户终端， 状态呈现服务器和 IMS核心网。 用户终端通过 IMS核心网与状态呈现服务器进行通信联络， 所述用户终端是即时通讯客户 端， 可以是定制终端， 可与状态呈现服务器或者其他业务服务器通过标准协 议进行通讯。
在所述 IP 多媒体子系统中， 用户终端 （UE )发起注册请求， 注册成功 后发起订阅请求， 状态呈现服务器收到订阅请求后返回成功响应， 同时发送 订阅通知消息 （Notify )相关信息；
状态呈现服务器在获知订阅通知消息（Notify )发送失败后， 向用户终端 发送 Message消息通知订阅通知消息 （ Notify )发送失败。
进一步地，用户终端在收到 Message消息后，获知订阅通知消息（Notify ) 发送失败后， 重新发送新的订阅请求。
其中， 订阅对象包括但不限于： 好友状态信息、 被订阅信息和 /或注册状 态信息等。
其中，所述状态呈现服务器在获知 Notify通知发送失败，是指发送 Notify 通知后， 该状态呈现服务器未收到用户终端返回的响应， 或者收到了非 2XX 的响应。
进一步地， 可以设置下发 Message消息通知次数的上限数值， 如果一个 用户在注册期间，服务端下发 Message消息通知次数未达到规定的上限值时， 则可发送 Message消息； 若达到上限则结束， 不再下发 Message消息。
基于图 4所示的 IP多媒体子系统， 状态呈现服务器通知用户终端订阅通 知消息 （Notify )发送失败的方法， 包括：
步骤 401 , 用户终端 UE发起注册请求， 注册成功后发起订阅请求， 状态 呈现服务器收到订阅请求后返回成功响应， 同时向用户终端发送 Notify通知 相关信息； 其中， 订阅对象包括： 好友状态信息、 被订阅信息和 /或注册状态 信息等；
步骤 402, 如果发送 Notify通知后， 状态呈现服务器获知 Notify通知失 败（没有收到用户终端返回的 Notify响应， 或者收到了非 2XX的响应）， 则 删除会话， 向用户终端发送 Message消息通知用户终端所述发送的 Notify通 知失败；用户终端收到 Message消息后根据相关信息重新发送新的订阅请求； 其中，所述 Notify通知失败有可能是 Notify超时，或者是收到 3XX、 4XX 或 5XX的响应，需要按照相关的协议提供的相关错误的处理流程说明进行处 理， 这不是本发明关注的问题， 在此不再赘述；
其中， 用户终端重新发起订阅后， 服务端重新下发 Notify通知消息； 如 果本次 Notify通知成功， 则用户终端可以继续保持该订阅会话； 如果本次通 知仍不成功， 需要重新执行本步骤直到下发 Message次数达到允许下发的次 数上限。 这个下发 Message次数的上限是由业务侧规定。
步骤 403 , 如果一个用户在注册期间， 状态呈现服务器下发 Message消 息通知的次数未达到规定的上限值时， 返回步骤 402 , 继续下发 Message消 息； 若达到上限则结束。
进一步地， 如果一个用户在注册期间， 状态呈现服务器发送 Message的 次数达到规定的上限值， 则放弃对用户终端的通知， 删除用户注册信息， 签 退客户端， 并向管理员进行告警。 此时， 状态呈现服务器可以选择禁止用户 登录， 也可以选择只删除订阅会话。 如果只删除订阅会话， 客户端无法获得 之后的本次订阅信息的变化通知。 所述允许发送 Message通知的次数上限值 由 IMS中的业务侧决定。
通过上述的关于 IMS系统及其恢复订阅关系的技术方案， 在状态呈现服 务器下发 Notify失败后， 通过下发 Message消息通知观察者通知失败， 用户 终端随后可以重新发起订阅请求恢复对相关对象的订阅， 从而提高了用户的 体验度， 增加了用户的使用效果。
在图 4所示的 IMS系统中， 用户终端注册成功， 订阅成功， 但是状态呈 现服务器下发 Notify失败后， 发送 Message消息通知， 用户终端重新发起订 阅， 状态呈现服务器再次发送 Notify的流程。
图 4中的各个详细信令流程如下：
A、 步骤 1-步骤 2 , 用户终端完成在 IMS核心网上面的注册， 以及核心 网完成在状态呈现服务端上的第三方注册；
B、 步骤 3-步骤 6 , 用户终端发送订阅， 状态呈现服务器返回订阅成功的 口向应； C、 步骤 7-步骤 8, 状态呈现服务器下发 Notify消息， 但未接收到对应的 响应， 即发送 Notify通知失败；
D、 步骤 9-步骤 12, 状态呈现服务器下发 Message请求， 通知到用户终 端， 用户终端返回响应；
E、 步骤 13-步骤 16, 用户终端重新发送订阅， 状态呈现服务器返回订阅 成功的响应；
F、 步骤 17-步骤 20, 状态呈现服务器再次下发 Notify消息， 并收到了成 功的响应。
以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。
工业实用性
与现有技术相比， 本发明可在服务端下发订阅通知消息失败后， 通过下 发即时消息（Message )通知客户端订阅通知消息发送失败； 客户端随后可以 重新发起订阅请求恢复对相关对象的订阅， 从而提高了用户的体验度， 增强 了用户的使用效果。

Claims

权 利 要 求 书
1、 一种 IP多媒体子系统中恢复用户订阅关系的方法， 包括：
客户端注册成功后向服务端发起订阅请求， 服务端收到所述订阅请求后 向客户端发送订阅通知消息；
服务端在发送订阅通知消息后， 若获知下发的订阅通知消息发送失败， 则向客户端发送即时消息用以通知所述订阅通知消息发送失败； 以及
所述客户端收到所述即时消息后获知所述订阅通知消息发送失败， 重新 向服务端发起订阅请求。
2、 如权利要求 1所述的方法， 其中，
所述客户端发起的订阅请求中的订阅对象包括： 好友状态信息、 和 /或被 订阅信息， 和 /或注册状态信息。
3、 如权利要求 1所述的方法， 还包括：
所述服务端通过如下方式获知下发的订阅通知消息发送失败： 在发送所 述订阅通知消息后未收到客户端返回的响应， 或者收到了非 2XX的响应。
4、 如权利要求 1所述的方法， 其中， 所述服务端配置有发送即时消息的 次数的门限值；
所述方法还包括： 如果发送即时消息的次数达到配置的门限值， 则服务 端删除用户注册信息， 签退该客户端， 并向管理员进行告警； 以及
如果发送即时消息的次数未达到配置的门限值， 则服务端继续发送即时 消息用以通知客户端所述订阅通知消息发送失败。
5、 如权利要求 1至 4中任一项所述的方法， 其中，
所述服务端是指在 IP多媒体子系统业务中能够处理订阅请求的服务器， 包括： 状态呈现服务器、 群组管理服务器和即时消息服务器；
所述客户端是指用户的终端， 包括电脑、 手机和个人数字助理设备。
6、 一种 IP多媒体子系统（IMS ) , 包括： 客户端、 服务端和 IMS核心 网， 所述客户端通过 IMS核心网与服务端交互， 其中：
客户端设置成在注册成功后向服务端发起订阅请求； 服务端设置成： 在收到所述订阅请求后向客户端发送订阅通知消息， 并 在发送所述订阅通知消息后若获知下发的所述订阅通知消息发送失败， 则向 客户端发送即时消息用以通知客户端所述订阅通知消息发送失败；
所述客户端还设置成在收到即时消息获知所述订阅通知消息发送失败 后， 重新向所述服务端发起订阅请求。
7、 如权利要求 6所述 IP多媒体子系统， 其中，
所述客户端发起的订阅请求中的订阅对象包括： 好友状态信息、 和 /或被 订阅信息， 和 /或注册状态信息。
8、 如权利要求 6所述 IP多媒体子系统， 其中，
所述服务端还设置成通过如下方式获知下发的订阅通知消息发送失败： 在发送所述订阅通知消息后未收到客户端返回的响应，或者收到了非 2XX的 口向应。
9、 如权利要求 6所述 IP多媒体子系统， 其中， 所述服务端配置有发送 即时消息的次数的门限值；
所述服务端还设置成： 如果发送即时消息的次数达到配置的门限值， 则 删除用户注册信息， 签退该客户端， 并向管理员进行告警； 以及
如果发送即时消息的次数未达到配置的门限值， 则继续发送即时消息用 以通知客户端所述订阅通知消息发送失败。
10、 如权利要求 6至 9中任一项所述 IP多媒体子系统， 其中， 所述服务端是指在 IP多媒体子系统业务中能够处理订阅请求的服务器， 包括： 状态呈现服务器、 群组管理服务器和即时消息服务器；
所述客户端是指用户的终端， 包括： 电脑、 手机和个人数字助理设备。
PCT/CN2011/078968 2010-12-27 2011-08-26 一种ip多媒体子系统及其恢复用户订阅关系的方法 Ceased WO2012088907A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP11854360.2A EP2661043B1 (en) 2010-12-27 2011-08-26 Ip multimedia subsystem and method thereof for restoring user subscription relationship

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010607712.1 2010-12-27
CN201010607712.1A CN102546554B (zh) 2010-12-27 2010-12-27 一种ip多媒体子系统及其恢复用户订阅关系的方法

Publications (1)

Publication Number Publication Date
WO2012088907A1 true WO2012088907A1 (zh) 2012-07-05

Family

ID=46352524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/078968 Ceased WO2012088907A1 (zh) 2010-12-27 2011-08-26 一种ip多媒体子系统及其恢复用户订阅关系的方法

Country Status (3)

Country Link
EP (1) EP2661043B1 (zh)
CN (1) CN102546554B (zh)
WO (1) WO2012088907A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110507988A (zh) * 2019-08-12 2019-11-29 广州小丑鱼信息科技有限公司 一种游戏断线自动重连方法及系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125591B (zh) * 2013-04-27 2017-10-27 中国移动通信集团河南有限公司 一种基于ims的呼叫控制方法、装置及系统
CN104125134B (zh) * 2013-04-27 2016-04-13 腾讯科技（深圳）有限公司 一种网络交互方法及装置、系统
US9787615B2 (en) 2013-04-27 2017-10-10 Tencent Technology (Shenzhen) Company Limited Apparatus, systems, and methods for network interactions
US9986525B1 (en) * 2016-11-30 2018-05-29 T-Mobile Usa, Inc. Error handling during IMS subscription for registration status
CN110536282B (zh) * 2019-03-28 2023-03-21 中兴通讯股份有限公司 一种事件通知方法及装置
WO2020231116A1 (en) * 2019-05-10 2020-11-19 Samsung Electronics Co., Ltd. Method and edge enabler server for providing dynamic information to edge enabler client running in ue
CN113079029B (zh) * 2020-01-03 2024-01-05 华为技术有限公司 配置信息订阅方法及装置
CN112995697B (zh) * 2021-04-30 2021-09-07 武汉斗鱼鱼乐网络科技有限公司 一种流数据恢复方法、服务器、存储介质及计算机设备
CN114979044B (zh) * 2021-08-10 2023-10-27 中移互联网有限公司 一种针对消息即平台的消息管理方法、节点及电子设备
CN113709248B (zh) * 2021-08-30 2023-11-21 广州大通和亿科技有限公司 业务请求处理方法、系统以及前端、服务端业务处理装置
CN117834721B (zh) * 2023-12-15 2025-04-08 天翼云科技有限公司 一种支持送达确认的消息订阅通知方法和系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101102607A (zh) * 2007-08-08 2008-01-09 中兴通讯股份有限公司 一种ip多媒体子系统ims中处理用户订阅的方法
CN101355442A (zh) * 2007-07-24 2009-01-28 华为技术有限公司 一种呈现服务器及其订阅状态机状态迁移的方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100525197C (zh) * 2007-04-06 2009-08-05 中国科学院计算技术研究所 一种存在信息的订阅、发布和更新方法
KR20090019665A (ko) * 2007-08-21 2009-02-25 삼성전자주식회사 구독자의 선호도를 참조하여 ｓｉｐ을 기반으로 하는이벤트 통지를 제어하는 시스템 및 방법
CN101374117A (zh) * 2007-08-21 2009-02-25 华为技术有限公司 处理电子邮件的方法、电子邮件服务器和客户端
US8134956B2 (en) * 2008-01-24 2012-03-13 At&T Intellectual Property I, L.P. System and method of providing registration alert in an IMS system
EP2297924A1 (en) * 2008-07-01 2011-03-23 Telefonaktiebolaget L M Ericsson (PUBL) Signalling optimisation in a presence service
CN101815079A (zh) * 2009-02-24 2010-08-25 北京邮电大学 基于sip的服务器集群发布服务信息的方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355442A (zh) * 2007-07-24 2009-01-28 华为技术有限公司 一种呈现服务器及其订阅状态机状态迁移的方法
CN101102607A (zh) * 2007-08-08 2008-01-09 中兴通讯股份有限公司 一种ip多媒体子系统ims中处理用户订阅的方法

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110507988A (zh) * 2019-08-12 2019-11-29 广州小丑鱼信息科技有限公司 一种游戏断线自动重连方法及系统

Also Published As

Publication number Publication date
EP2661043A4 (en) 2016-06-01
CN102546554B (zh) 2015-01-28
EP2661043B1 (en) 2017-10-04
CN102546554A (zh) 2012-07-04
EP2661043A1 (en) 2013-11-06

Similar Documents

Publication Publication Date Title
WO2012088907A1 (zh) 一种ip多媒体子系统及其恢复用户订阅关系的方法
CN103733701B (zh) 用于订阅互联网协议多媒体子系统(ims)应用服务注册状态的系统和方法
EP3228102B1 (en) Sip ims call forking to multiple associated devices
JP6169568B2 (ja) パッシブ通信サービスのためのシステムおよび方法
CN107431698A (zh) 电信系统中的ims间服务支持
US9037675B2 (en) Method for performing inter-user equipment transfer in wireless communication system based on internet protocol multimedia subsystem
US20160100375A1 (en) Sip user release
WO2015172629A1 (zh) 一种消息传输的方法、装置及系统
CN103096295B (zh) 用户状态更新方法、系统及业务服务器、sip终端
CN109120578B (zh) 一种实现链路连接处理的方法及装置
US11997146B1 (en) IMS restoration triggered by receipt of a MWI or a text message via fallback protocol
CN101860804A (zh) 预定义加入群组会话的加入实现方法和系统
CN107295203A (zh) 一种多方通话会议中的消息传输方法及装置
US11558468B2 (en) Mobile client recovery using push notifications to execute exponential back-off procedure
US8984117B2 (en) System and method for re-publication of information in a network-based communication system
CN105376727A (zh) 数据卡处理方法及装置
CN102083052B (zh) 一种成员呈现信息订阅控制方法、系统及装置
WO2012058943A1 (zh) Ip多媒体子系统、订阅forking的方法及装置
WO2013097222A1 (zh) 业务发放的方法、注册服务器及终端
EP3068096A1 (en) Method and device for broadcasting a media stream through a telecommunication network within a spatial scope
JP2013537012A (ja) コール転送の宛先の監視

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

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

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011854360

Country of ref document: EP