WO2007059704A1 - Procede et systeme d'acquisition d'informations dans un protocole de lancement de session - Google Patents

Procede et systeme d'acquisition d'informations dans un protocole de lancement de session Download PDF

Info

Publication number
WO2007059704A1
WO2007059704A1 PCT/CN2006/003134 CN2006003134W WO2007059704A1 WO 2007059704 A1 WO2007059704 A1 WO 2007059704A1 CN 2006003134 W CN2006003134 W CN 2006003134W WO 2007059704 A1 WO2007059704 A1 WO 2007059704A1
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
event
server
registration
message
Prior art date
Application number
PCT/CN2006/003134
Other languages
English (en)
Chinese (zh)
Inventor
Xiao 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 WO2007059704A1 publication Critical patent/WO2007059704A1/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]

Definitions

  • the present invention relates to communication technologies, and more particularly to a method and system for acquiring resource information in a Session Initiation Protocol (SIP).
  • SIP Session Initiation Protocol
  • the Session Initiation Protocol is one of the multimedia communication system framework protocols developed by the Internet Engineering Task Force (IETF). It is a text-based application layer control protocol, independent of the underlying protocol, used to establish, modify or terminate. Two or more multimedia sessions in an IP network.
  • SIP uses an event notification framework, including subscription (SUBSCRIBE) and notification (NOTIFY).
  • SUBSCRIBE is used for event subscription, and NOTIFY is used to deliver event notification.
  • the event notification refers to a user initiating a subscription to an event or resource to another user or resource, so that the former can receive any information about the event or resource from the latter, such as the current state of the resource or Changes, etc.
  • Figure 1 shows the subscription process in the existing SIP (see RFC3265), including: Step 101: The Subscriber sends a subscription (SUBSCRIBE) request to the Notifier to subscribe to the resources of interest to itself.
  • Step 101 The Subscriber sends a subscription (SUBSCRIBE) request to the Notifier to subscribe to the resources of interest to itself.
  • SUBSCRIBE subscription
  • the Subscriber indicates which resource or resources are of interest to them.
  • Notifier is the owner of the resource.
  • Step 102 The Notifier allows the subscriber to subscribe, and sends a 200 OK response to the Subscriber. After that, a subscription dialog and a subscription instance are established between Subscriber and Notifier.
  • the dialog refers to a SIP relationship between two communicating parties, which provides necessary information as a basis for routing and message sequencing by both communicating parties.
  • Step 103 The Notif!er sends a notification (NOTIFY) message to the Subscriber, and the message body of the NOTIFY message carries the resource information requested by the Subscriber.
  • NOTIFY notification
  • Step 104 After receiving the NOTIFY message, the Subscriber sends a 200 OK response to the Notifier, indicating that the NOTIFY message is successfully received.
  • the above subscription process is to issue a subscription request by the Subscriber, the Subscriber refers to a User Agent (UA), receives a subscription request of the Subscriber by the Notifier, and sends a NOTIFY message to the Subscriber, where the Notifier is usually an event server (Event) Server).
  • the Event Server is used as a subscriber.
  • a IETF draft document proposes to associate a registration with a subscription, and a list of subscription event packages is carried in the registration message to initiate a subscription at the same time as registration. In this way, the user terminal does not need to separately issue a subscription request to the Event Server, thereby reducing the amount of message interaction when the user terminal starts.
  • the user terminal (UA) and the registration server (Registrar) interact with the REGISTER message and the NOTIFY message, and the Event Server uses the publishing mechanism to inform the Registrar of the latest resource information.
  • a defined protocol for SIP ie RFC3903
  • the publishing mechanism like the subscription mechanism of Figure 1, can use the same format header and message body to indicate the status of the event. The difference is that the publishing mechanism does not need to create a dialog.
  • the Event Server can have both the functionality of a Subscriber and a Publisher, or it can have only the functionality of a Subscriber, or only the functionality of a publishing server.
  • FIG. 3 shows the flow of subscription processing in the prior art.
  • Steps 301-302 The UA sends a registration message to the Registrar, the registration message carries the associated subscription event package, the Registrar replies with a 200 OK response to the UA, and establishes a subscription dialog between the UA and the Registrar.
  • the registration message sent by the UA carries a subscription header field, and the header field includes a list of subscription event packages for indicating which events the UA wants to subscribe to.
  • the 200 OK response returned by the Registrar also carries a subscription header field for indicating to the UA which events are allowed to subscribe.
  • Steps 303 ⁇ 304 The Event Server publishes the resource information maintained by itself to the Registrar through the PUBLISH message, and the Registrar replies with a 200 OK response.
  • Steps 305 ⁇ 306 According to the resource information released by the Event Server, the Registrar synchronously updates the resource information recorded by itself, and sends the latest UA requesting resource information to the UA through a NOTIFY message, and the UA replies with a 200 OK response to the Registrar.
  • the Event Server notifies the Registrar of the resource information through the publishing mechanism
  • the redundant resource information is released to the Registrar along with the resource information (that is, the useful resource information) that the UA requests to subscribe to, which will occupy the network bandwidth and the processing of the Registrar.
  • Storage capacity resulting in a certain waste of resources.
  • the prior art also provides another process of subscription processing (see FIG. 4), specifically: Event Server subscribes to the registration event package of the UA in advance to the Registrar; when the UA issues a registration message of the associated subscription to the Registrar, the Registrar notifies the Event Server. (via NOTIFY message)
  • the UA requires registration, and carries the subscription event package of the UA in the NOTIFY message; the Event Server acts as the subscription server and sends the NOTIFY directly to the UA.
  • Interest establish a subscription and subscription instance for itself and the UA.
  • the process requires a subscription dialog and subscription instance to be established between the UA and the Event Server. If the UA is associated with multiple subscription event packages when registering, each subscription event package corresponds to a different Event Server. The UA will establish a subscription dialog and a subscription instance with multiple Event Servers respectively, which will increase the overhead of the UA. In addition, existing standards (such as RFC3265) do not support the establishment of a subscription dialog between UA and Event Server, which makes the process need to extend existing standards and is more complicated to implement.
  • FIG. 5 is a flow chart of another subscription process provided in the prior art, specifically: the Event Server subscribes to the Registrar to register the UA registration event package; the UA registers with the Registrar, and carries the associated subscription event package; the Registrar notifies the Event Server (via NOTIFY)
  • the UA requires registration, and carries the subscription event package of the UA in the NOTIFY message; the Event Server acts as the publishing server, and sends the latest UA required subscription information to the Registrar through the PUBLISH message; the Registrar and the UA establish a subscription dialog and a subscription instance.
  • the resource information that the UA requests to subscribe to is notified to the UA through a NOTIFY message.
  • the invention provides a method and a system for acquiring resource information in SIP, and the main technical solutions are:
  • a method for obtaining resource information in a session initiation protocol includes: a user terminal initiating a registration message for association publication, the registration message carrying at least one event package, where the event package is used to indicate resource information that the user terminal requests to acquire;
  • a resource information acquisition system in a session initiation protocol comprising: a user terminal, a registration server, and an event server;
  • the user terminal is configured to initiate a registration message of the associated advertisement, where the registration message carries at least one event package, where the event package is used to indicate resource information that the user terminal requests to obtain; the registration server is configured to obtain the subscription information from the event server.
  • the user terminal requests the acquired resource information, and sends the resource information to the user terminal in a publishing manner.
  • a resource information acquisition system in a session initiation protocol comprising: a user terminal, a registration server, and an event server;
  • the user terminal is configured to initiate a registration message of the associated advertisement, where the registration message carries at least one event package, where the event package is used to indicate resource information that the user terminal requests to obtain;
  • the registration server is configured to acquire an event carried in the registration message. Package, and send a notification message to the event server;
  • the event server is configured to receive the notification message, and send the resource information requested by the user terminal to the user terminal in a publishing manner.
  • the UA interacts with the Registrar or the Event Server through the PUBLISH mechanism, so that the UA can obtain the subscription of the user terminal without having to establish and maintain the subscription dialog and the subscription instance.
  • Resource information reduces the overhead of maintenance and management of the UA.
  • the Registrar obtains the resource information required by the UA from the subscription server through the subscription mechanism, which enables the Registrar to obtain useful resource information according to the requirements of the UA, reduce the waste of network bandwidth, and improve the efficiency of resource information acquisition.
  • Registrar obtains resource information from Event Server, it only needs to establish a subscription dialog between the two, which saves the maintenance and management overhead of Event Server and meets the requirements of existing standards.
  • Figure 1 is a flow chart of a subscription process in an existing SIP
  • FIG. 2 is a schematic diagram of a subscription processing model in the prior art
  • FIG. 5 is a flowchart of still another subscription process in the prior art
  • FIG. 6 is a schematic diagram of a subscription processing model in an embodiment of the present invention.
  • FIG. 7 is a flowchart of a subscription process in an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a subscription processing model in another embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a subscription processing model in still another embodiment of the present invention. Mode for carrying out the invention
  • the UA subscribes simultaneously during the registration process. In this way, the UA does not need to change the existing subscription mechanism to obtain the resource information that it wishes to subscribe to. Moreover, the UA does not need to establish and maintain a subscription dialog and a subscription instance when registering, so the method can reduce the overhead of the UA and meet the requirements of existing standards.
  • the interface between the UA and the Registrar adopts the SUBSCRIBE mechanism, and the Event Server issues resource information to the Registrar through the PUBLISH mechanism.
  • the Event Server can directly inform the UA of the resource information through the non-standard SUBSCRIBE mechanism, or provide the resource information to the Registrar by using a mixture of the SUBSCRIBE mechanism and the PUBLISH mechanism.
  • the interface between the UA and the Registrar uses the PUBLISH mechanism, and the Registrar obtains resource information from the Event Server through the SUBSCRIBE mechanism.
  • This subscription processing model is completely different from the prior art.
  • the present embodiment newly expands a header field that can be carried in the REGISTER message of the SIP protocol, and is used to transmit a list of resource information that the UA wants to acquire when registering.
  • the header field is called Pub- Reg.
  • Pub-Reg (“Pub-Reg") HCOLON (pub-event* (COMMA pub-event))
  • Event-type event-package *(".” event-template
  • Event-package token-nodot
  • Event-template token-nodot
  • Pub-aor "aor” EQUAL (SIP-URI / SIPS-URI)
  • the Pub-event defined above records the event package that the UA expects to obtain through the PUBLISH mechanism.
  • the Pub-event contains the event package type (event-type) and the event package parameter (pub-event-param).
  • the event-type and event header fields have the same definitions, and are not detailed here.
  • ub-event-param contains pub-aor and generic-param, and pub-aor is used to indicate the record of the secretary sent by the event package.
  • the definitions of the address (AOR, Address-of-Record), generic-param and Event header fields: 3 ⁇ 4 are all the same, and will not be detailed here.
  • the Pub-Reg header can either pass the UA's request for multiple resource information.
  • the format of the Pub-Reg header field described above is only a specific example of the present invention, and the Pub-Reg header field can be implemented in any format, and is not limited to this format.
  • the Event header field may be used to pass an event packet of the resource information that the UA wants to acquire through the PUBLISH mechanism at the time of registration, but in this way, multiple event packets cannot be delivered at the same time, and can only be delivered one by one.
  • the message body of the registration message may be carried by the message body, and the message body may be encoded by text or XML, or other possible coding modes, which are not limited by the present invention.
  • a list of event packets may be carried in the message body of the registration message in the following format:
  • the following format can be used:
  • Sip example@example . server ⁇ com
  • the 13 ⁇ 4 ⁇ 1> element is the root element of the event package list, the element includes multiple event packages, the ⁇ 61 ⁇ ] ⁇ > element represents an event package, and the attribute "name" represents the event package name.
  • the child element ⁇ &01 represents the destination AOR sent by the event package.
  • Figure ⁇ is a subscription processing flow according to an embodiment of the present invention.
  • the UA associates the published event package with the registration process to present the UA friend.
  • Step 701 The UA issues a registration message of the associated publication, and the registration message carries a Pub-Reg header field. Among them, pub-aor records the destination Uniform Resource Identifier (URI) sent by the event package, and the event package is presence.
  • URI Uniform Resource Identifier
  • Step 702 After receiving the registration message, the Registrar finds that the registration message carries the Pub-Reg header field, and the Registrar extracts the corresponding content, constructs a SUBSCRIBE request, and initiates a subscription to the Event Server.
  • Step 703 The Event Server returns a 200 OK response to the Registrar, indicating that the subscription is successful.
  • Step 704 The Registrar returns a 200 OK response to the UA, indicating that the registration is successful.
  • the 200 OK response carries the Pub-Reg header field, and the recorded event packet is successfully registered. This embodiment is called prsssnce.
  • Step 705 The Event Server sends a NOTIFY message to the Registrar to notify the Registrar of the resource information subscribed to.
  • Step 706 Registrar replies to the Event Server with a 200 OK response to confirm Received the NOTIFY message.
  • Step 707 The Registrar converts the received NOTIFY message into a PUBLISH message and sends it to the UA.
  • Step 708 The UA replies with a 200 OK response to the Registrar to confirm that it has received the PUBLISH message.
  • FIG. 8 A subscription processing model according to another embodiment of the present invention is shown in FIG. 8. Specifically, the UA sends an associated registration message to the Registrar; the Registrar takes the event packet in the registration message, and notifies the Event Server that provides the resource information through the NOTIFY message. After the Event Server receives the NOTIFY message, it directly publishes the subscribed resource information to the UA through the PUBLISH mechanism.
  • the interface between the Event Server and the Registrar can also be changed to the PUBLISH mode.
  • the subscription processing model of this embodiment is shown in Figure 9.
  • the Event Server informs the Registrar of the resource information maintained by itself, and the UA initiates the association release.
  • the Registrar sends the resource information of the UA subscription to the UA through the PUBLISH message.
  • the Event Server notifies the Registrar of the resource information through the publishing mechanism, which will result in redundant resource information, such as resource information that the UA does not request to obtain, and will also be released to Registra.
  • the network server when the user terminal requests to obtain the resource information, the network server provides the resource information to the user terminal in a publishing manner.
  • the network server may refer to either a registration server or a single event server.
  • the registration server and the event server can also be collectively referred to as a network server, and the interaction between the registration server and the event server is the internal interaction of the network server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé et un système d'acquisition d'informations de ressources, qui comprend les stades suivants: l'agent utilisateur envoie un message d'enregistrement associé à la publication, le message d'enregistrement transporte au moins un paquet d'événements, qui est utilisé pour indiquer les informations de ressources requises par l'agent utilisateur; le serveur Web publie le message à l'intention de l'agent utilisateur, qui transporte les informations de ressources requises par un agent utilisateur; le système comprend un agent utilisateur, un registrateur et un serveur d'événements. Dans ces procédé et système, l'agent utilisateur communique avec le registrateur ou le serveur d'événements au moyen d'un mécanisme PUBLISH, de manière à permettre à l'agent utilisateur d'acquérir les informations de ressources auxquelles est abonné l'agent utilisateur sans qu'il soit nécessaire d'établir et de maintenir le dialogue d'abonnement et l'exemple d'abonnement; les coûts d'entretien et de gestion s'en trouvent réduits.
PCT/CN2006/003134 2005-11-25 2006-11-21 Procede et systeme d'acquisition d'informations dans un protocole de lancement de session WO2007059704A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510101847.X 2005-11-25
CN200510101847.XA CN1972279B (zh) 2005-11-25 2005-11-25 一种会话发起协议资源事件包获取方法

Publications (1)

Publication Number Publication Date
WO2007059704A1 true WO2007059704A1 (fr) 2007-05-31

Family

ID=38066919

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003134 WO2007059704A1 (fr) 2005-11-25 2006-11-21 Procede et systeme d'acquisition d'informations dans un protocole de lancement de session

Country Status (2)

Country Link
CN (1) CN1972279B (fr)
WO (1) WO2007059704A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101335634B (zh) * 2007-06-29 2011-12-28 华为技术有限公司 提供联系人信息的方法、系统及网络设备
CN101594356B (zh) * 2009-06-29 2012-09-05 中兴通讯股份有限公司 网元资源处理方法、装置以及系统
CN102577317A (zh) * 2011-12-31 2012-07-11 华为技术有限公司 业务发放的方法、注册服务器及终端
CN110958210A (zh) * 2018-09-27 2020-04-03 展讯通信（上海）有限公司 通过ims注册流程获知网络能力的方法、装置及移动终端
CN111147534B (zh) * 2018-11-05 2022-12-16 中兴通讯股份有限公司 一种微服务架构下的通信方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1543167A (zh) * 2002-12-02 2004-11-03 ���ǵ�����ʽ���� 利用会话发起协议的终端注册方法
WO2005051029A1 (fr) * 2003-11-19 2005-06-02 National Institute Of Information And Communications Technology, Independent Administrative Agency Systeme de communication radio

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6853634B1 (en) * 1999-12-14 2005-02-08 Nortel Networks Limited Anonymity in a presence management system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1543167A (zh) * 2002-12-02 2004-11-03 ���ǵ�����ʽ���� 利用会话发起协议的终端注册方法
WO2005051029A1 (fr) * 2003-11-19 2005-06-02 National Institute Of Information And Communications Technology, Independent Administrative Agency Systeme de communication radio

Also Published As

Publication number Publication date
CN1972279B (zh) 2010-08-11
CN1972279A (zh) 2007-05-30

Similar Documents

Publication Publication Date Title
EP1985094B1 (fr) Représentation d'information d'état de disponibilité de réseau en information de présence
US7634564B2 (en) Systems and methods for invoking a service from a plurality of event servers in a network
US9112902B2 (en) Service subscription associated with real time composition of services
US20040128344A1 (en) Content and service registration, query and subscription, and notification in networks
WO2009092263A1 (fr) Terminal, serveur, procédé pour gérer ledit terminal et procédé pour rapporter des informations de capacité relatives à ce terminal
WO2009033376A1 (fr) Procédé et système de sélection de chemin
WO2007068209A1 (fr) Procede, systeme et dispositif d'envoi de messages instantanes ims
WO2013026327A1 (fr) Procédé d'interrogation de capacité, terminal de communication et serveur d'application
WO2008089642A1 (fr) Procédé, dispositif et système pour le transfert d'informations de terminal dans un sous-système multimédia
EP1909434A1 (fr) Méthode et dispositif d abonnement
WO2007059704A1 (fr) Procede et systeme d'acquisition d'informations dans un protocole de lancement de session
US8315247B2 (en) System and method for providing registration-coupled subscriptions in a session initiation protocol (SIP) environment
WO2009015587A1 (fr) Procédé, système et appareil de routage soap
WO2008098500A1 (fr) Procédé et appareil pour découvrir un service de flux de données multimédia et appareil pour découvrir un service
WO2007022707A1 (fr) Procede, systeme et unite de prestation de services d'application
WO2010102588A1 (fr) Procédé et système pour commander une conférence multimédia
WO2007079647A1 (fr) Procede, appareil et systeme de sauvegarde en reseau d'un systeme d'application sip
EP1978707B1 (fr) Procédé et système pour la génération et l'acquisition de droits d'auteurs et centre d'octroi de droits
WO2009015586A1 (fr) Procédé pour transmettre des informations de service, entité fonctionnelle de réseau et dispositif utilisateur
WO2007068194A1 (fr) Procede permettant d'effectuer une actualisation de lots dans un mecanisme d'abonnement, abonne et terminal de notificateur
WO2007124662A1 (fr) Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement
WO2011085121A2 (fr) Procédés, systèmes et supports lisibles par ordinateur pour fournir des informations d'entité observatrice d'événements de protocole d'ouverture de session (sip) dans un réseau de communication
WO2009024053A1 (fr) Procédé et système pour transférer un message de découverte d'opération et entité fonctionnelle pour une découverte d'opération
WO2007131433A1 (fr) Procédé et système d'acheminement d'un message relatif à une demande d'abonnement
WO2007031029A1 (fr) Procede d'abonnement a l'etat des ressources base sur le protocole d'ouverture de session

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06828174

Country of ref document: EP

Kind code of ref document: A1