CN101867590A - Subscription method based on session initiation protocol, and device thereof - Google Patents
Subscription method based on session initiation protocol, and device thereof Download PDFInfo
- Publication number
- CN101867590A CN101867590A CN200910130092A CN200910130092A CN101867590A CN 101867590 A CN101867590 A CN 101867590A CN 200910130092 A CN200910130092 A CN 200910130092A CN 200910130092 A CN200910130092 A CN 200910130092A CN 101867590 A CN101867590 A CN 101867590A
- Authority
- CN
- China
- Prior art keywords
- entity
- subscription
- subscribes
- subscribing
- authentication
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 91
- 230000000977 initiatory effect Effects 0.000 title abstract description 26
- 230000004044 response Effects 0.000 claims abstract description 99
- 230000005540 biological transmission Effects 0.000 claims description 46
- 230000008859 change Effects 0.000 claims description 41
- 230000006854 communication Effects 0.000 description 13
- 238000004891 communication Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 4
- 239000000203 mixture Substances 0.000 description 4
- 230000011664 signaling Effects 0.000 description 3
- 230000014509 gene expression Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000005728 strengthening Methods 0.000 description 1
Images
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
- H04L2101/38—Telephone uniform resource identifier [URI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
- H04L2101/385—Uniform resource identifier for session initiation protocol [SIP URI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention discloses a subscription method based on session initiation protocol, which comprises the steps of: receiving the request message which is used for substituting the subscription of a subscription entity and sent by an agent subscription entity, wherein the request message for substituting the subscription of the subscription entity at least comprises event subscribed by the subscription entity and uniform resource locator (URI) of the subscription entity; according to the event subscribed by the subscription entity and the uniform resource locator (URI) of the subscription entity in the request message for substituting the subscription of the subscription entity, sending subscription confirming notification message to the subscription entity; and receiving the authentication sent by the subscription entity, and establishing the conversation with the subscription entity by confirming the response for subscription confirming notification message. The embodiment of the invention also provides a device of the subscription method. The technical scheme of the invention achieves the aim that the agent subscription entity replaces the subscription entity to subscribe for the event in an event notification entity.
Description
Technical field
The present invention relates to communication technical field, be specifically related to the method for subscribing and the device of dialogue-based initializtion protocol.
Background technology
Conversation initialized protocol (SIP, Session Initial Protocol) is a kind of signaling control protocol that is realized real time communication by IETF in a kind of internet protocol-based (IP, Internet Protocol) network of proposition in 1999.SIP is used for describing generation, modification, one of termination or more than the session between the participant.Its main purpose is in order to solve the signaling control in the IP network, and with the communication of soft switch, thereby constitute follow-on value-added service platform, provide better value-added service to industries such as telecommunications, bank, finance.SIP has broken the transmission mode of conventional telecommunications business, based on the standard of internet, cellular system and internet application is merged, and IP-based multimedia service is provided.Session Initiation Protocol is plurality of advantages more and more obtain the communicating by letter favor of industry because it is simple, be easy to expand, be convenient to realize etc., becoming next generation network (NGN, Next General Network) one of core protocol, and Session Initiation Protocol is defined as the signaling protocol of 3-G (Generation Three mobile communication system) so that IP to be provided multimedia service by 3GPP working group
The subscribing notification method is to be based upon to subscribe between entity and the notification entity in the existing Session Initiation Protocol, as shown in Figure 1, concrete grammar comprises: subscribe to entity and send subscribe request to notification entity, notification entity sends the response (being 200OK) of confirming subscription and gives the subscription entity, makes to subscribe to foundation dialogue between entity and the notification entity; In the dialogue of having set up, when resource status subscribed in the notification entity changes, the notification entity transmission includes the notification message of current subscribed state information of event to subscribing to entity, subscribes to entity after notified message, sends response (being 200OK) to notification entity.
In research and practice process to prior art, the present inventor finds that this subscribing notification method only is applicable to subscribes between entity and the notification entity, and the prior art scheme underaction has limitation.
Summary of the invention
The embodiment of the invention provides method for subscribing, device and the communication system of dialogue-based initializtion protocol.
The embodiment of the invention provides a kind of method for subscribing of dialogue-based initializtion protocol, comprising:
The reception agency subscribes to the replacement of entity transmission and subscribes to the request message of entity subscribes, comprises at least in the request message of described replacement subscription entity subscribes: subscribe to the incident of entity subscribes and the URL(uniform resource locator) URI of subscription entity;
According to the incident of the subscription entity subscribes in the request message of described replacement subscription entity subscribes and the URI of subscription entity, send and confirm that subscribing notification message is to the subscription entity;
Receive of the response of the authentication of subscription entity transmission, the dialogue between foundation and the described subscription entity by described affirmation subscribing notification message.
The embodiment of the invention also provides a kind of event notice entity, comprising: first receiving element and first transmitting element;
Described first receiving element, be used to receive the request message that the agency subscribes to the replacement subscription entity subscribes of entity transmission, comprise at least in the request message of described replacement subscription entity subscribes: subscribe to the incident of entity subscribes and the URL(uniform resource locator) URI of subscription entity; Receive of the response of the authentication of subscription entity transmission, the dialogue between foundation and the described subscription entity by described affirmation subscribing notification message;
Described first transmitting element, be used for when the request message of judging described replacement subscription entity subscribes passes through authentication, according to the incident of the subscription entity subscribes in the request message of described replacement subscription entity subscribes and the URI of subscription entity, send and confirm that subscribing notification message is to the subscription entity.
The embodiment of the invention also provides a kind of subscription entity, comprising: the 6th receiving element, second authenticating unit and the 6th transmitting element;
Described the 6th receiving element is used to receive the replacement that the event notice entity sends and subscribes to the request message of entity subscribes;
Described second authenticating unit, the request message that is used for the described replacement that receives is subscribed to entity subscribes carries out authentication;
Described the 6th transmitting element, be used for when authentication by the time, send authentication by this response of request message that replaces subscribing to entity subscribes to the event notice entity, set up and the event notice entity between dialogue.
The embodiment of the invention also provides a kind of agency to subscribe to entity, comprising: the 7th receiving element and the 8th transmitting element;
Described the 7th receiving element is used to receive the subscription incident that entity sends of subscribing to;
Described the 7th transmitting element is used for the subscription incident that receives according to described, sends to replace subscribing to the request message of entity subscribes to the event notice entity.
The embodiment of the invention adopts the replacement that receives the transmission of agency's subscription entity to subscribe to the request message of entity subscribes, this replacement being subscribed to the request message of entity subscribes resolves, after the authentication, send authentication and subscribe to entity to the agency by response, according to the request message that replaces subscribing to entity subscribes, send and confirm that subscribing notification message is to subscribing to entity, receive and subscribe to the response of entity authentication by this affirmation subscribing notification message, set up and subscribe to the dialogue between the entity, thereby realized that the agency subscribes to the purpose that entity replaces subscribing to the incident in the entity subscribes event notice entity, has greater flexibility.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the general flow chart of prior art subscribing notification method in Session Initiation Protocol;
Fig. 2 is the general flow chart of a kind of method for subscribing based on Session Initiation Protocol of providing of the embodiment of the invention one;
Fig. 3 is the general flow chart of a kind of method for subscribing based on Session Initiation Protocol of providing of the embodiment of the invention two;
Fig. 4 is a kind of general flow chart that obtains the method for subscription incident in the embodiment of the invention two;
Fig. 5 is the another kind of general flow chart that obtains the method for subscription incident in the embodiment of the invention two;
Fig. 6 is the logic composition diagram of a kind of communication system based on SIP of providing of the embodiment of the invention three;
Fig. 7 is the logic composition diagram of a kind of event notice entity of providing of the embodiment of the invention four;
Fig. 8 is a kind of logic composition diagram of subscribing to entity that the embodiment of the invention five provides;
Fig. 9 is a kind of logic composition diagram of subscribing to entity of acting on behalf of that the embodiment of the invention six provides.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is a part of embodiment of the present invention, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
The embodiment of the invention provides a kind of method for subscribing of dialogue-based initializtion protocol, and the embodiment of the invention also provides corresponding device thereof and communication system.Below be elaborated respectively.
Embodiment one,
The embodiment of the invention provides a kind of method for subscribing based on Session Initiation Protocol, and referring to shown in Figure 2, this method comprises:
Step 1: receive the request message that the agency subscribes to the replacement subscription entity subscribes of entity transmission, comprise at least in this request message: subscribe to the incident of entity subscribes and the URL(uniform resource locator) (URI, Uniform Resource Identifier) of subscribing to entity;
Step 2: resolve the replacement that receives and subscribe to the request message of entity subscribes;
Step 3: the request message according to resolving, carry out authentication to this request message;
Step 4: whether judge this request message by authentication, if, execution in step 6; If not, send the unsanctioned response of authentication and subscribe to entity to the agency.
The explanation of above-mentioned steps 2 to 4 is the explanations of giving an example at existing Session Initiation Protocol, in fact, the executive agent of this method, as event notice entity execution in step 2 to 4 not, directly execution in step 6 and step 7 also are feasible.Literal all in this specification all should have identical understanding.
Step 6:, send and confirm that subscribing notification message is to subscribing to entity according to the URI of events subscribed in the request message that passes through authentication that obtains in the step 4 and subscription entity;
Step 7: the response message that this affirmations subscribing notification message authentication is passed through that receive to subscribe to that entity sends, set up and the subscription entity between dialogue.
Optionally, when the result who judges in the step 4 is a request message when passing through authentication, this method can also be carried out:
Step 5: the response that the transmission authentication is passed through is subscribed to entity to the agency, sets up and act on behalf of the dialogue between the subscription entity.
By above to step 1 in this method to the explanation of step 7, adopt the replacement that receives the transmission of agency's subscription entity to subscribe to the request message of entity subscribes in this method, this replacement being subscribed to the request message of entity subscribes resolves, after the authentication, send authentication and subscribe to entity to the agency by response, according to the request message that replaces subscribing to entity subscribes, send and confirm that subscribing notification message is to subscribing to entity, the response message that this affirmation subscribing notification message authentication is passed through that receive to subscribe to that entity sends, set up and subscribe to the dialogue between the entity, thereby realized that the agency subscribes to the purpose that entity replaces subscribing to the incident in the entity subscribes event notice entity.
Embodiment two,
A kind of method for subscribing that the embodiment of the invention provides based on Session Initiation Protocol, this method is similar to the method that embodiment one provides, and the method that present embodiment provides is another kind of preferable implementation method.Before the method that present embodiment is provided is done explanation, at first this method applied scene is done explanation, this method can be that the IP multi-media network that is applied in based on SIP also can be applied in other networks based on SIP, participate in carrying out the network architecture that the entity in this method forms, comprising: the agency subscribes to entity, subscribes to entity and event notice entity.
A kind of method for subscribing based on Session Initiation Protocol that present embodiment is provided is done explanation below, and referring to shown in Figure 3, this method comprises:
Steps A 1: agency's subscription entity is according to the subscription incident of the subscription entity that obtains, and the request message that transmission replaces subscribing to entity subscribes includes but not limited to the subscription incident to the event notice entity in the request message of described replacement subscription entity subscribes;
Wherein, need to prove that the subscription incident that the agency subscribes to the subscription entity that obtains in the entity can preset, also can act on behalf of to subscribe to and communicate by letter between entity and the subscription entity and obtain,
Concrete, the request message body that entity subscribes is subscribed in the replacement that agency's subscription entity sends in the steps A 1 can be following code:
SUBSCRIBE?sip:8613507551006@imsdemo.com?SIP/2.0
Via:SIP/2.0/UDP?10.85.29.189:8012;rport;branch=z9hG4bK486ad8db-0041eb
To:<sip:8613507551006@imsdemo.com>
From:<sip:8613507551005@imsdemo.com>;tag=486aff88
Contact:<sip:8613507551006@10.85.29.189:8012;transport=udp>
Call-ID:ZdmAg12893-ID00000002-H9M024S43@10.85.29.189
CSeq:3SUBSCRIBE
Route:<sip:orig@2.32.32.7:30820;lr>
Max-Forwards:70
Expires:3030
Event:refer-event
Re-EVENT:reg
Re-TO:sip:8613507551007@imsdemo.com;xxxx
8613507551007@imsdemo.com
Re-EXPIRES:6060
Accept:application/reginfo+xml
Content-Length:0
Above-mentioned message represents that URI is that the agency of sip:8613507551005@imsdemo.com subscribes to entity will to replace URI be the subscription entity of sip:8613507551007@imsdemo.com, subscribes to URI and be the notice of the reg incident in the event notice entity of sip:8613507551006@imsdemo.com.
Wherein, being explained as follows of content in some header fields and the header field in this message body:
Header field Re-EVENT and content thereof are used for expression subscription entity will subscribe to incident; Header field Re-TO and content representation thereof are subscribed to the URI of entity and are subscribed to entity and act on behalf of the authentication information of subscribing between the entity; Header field Re-EXPIRES and content thereof are used to represent to subscribe to the duration that entity will be subscribed to incident.The concrete meaning of other header fields please refer to RFC3265 and RFC3261.
Need to prove that the authentication information between subscription entity and the agency's subscription entity also can adopt other form except in the Re-TO header field, as: authentication information in message body, comprised.The concrete form of authentication information determines that according to concrete method for authenticating the form of above-mentioned authentication information not should be appreciated that the restriction to the embodiment of the invention.
More than be that the agency subscribes to entity and sends to a kind of form of message that the request message of entity subscribes is subscribed in the replacement of event notice entity, other forms of message or message body can also be arranged, should not be construed restriction of the invention process for strengthening the cited embodiment of exploitativeness of the present invention herein.
Steps A 2: the event notice entity is resolved the request message that entity subscribes is subscribed in this replacement after receiving and replacing subscribing to the request message of entity subscribes;
Steps A 3: after the event notice entity is resolved successfully to the request message that replaces the subscription entity subscribes, this replacement is subscribed to the request of entity subscribes and carry out authentication;
Wherein, it will be appreciated that, optionally, when resolving the request message identification that replaces the subscription entity subscribes in the steps A 2, execution in step X1: after the event notice entity is resolved failure to the request message that replaces the subscription entity subscribes, send errored response and subscribe to entity to the agency, the message that promptly sends 4xx is subscribed to entity, end operation to the agency;
Wherein, also it will be appreciated that, optionally, when in the steps A 3 when replace subscribing to the request message failed authentication of entity subscribes, execution in step X2: after the event notice entity is to the request message failed authentication that replaces the subscription entity subscribes, transmission can be resolved and the response of failed authentication is subscribed to entity to the agency, as the 4xx response, and end operation.
Steps A 4: after event notice entity in the steps A 3 passes through the request message authentication that replaces the subscription entity subscribes, send authentication and pass through response, set up and act on behalf of the dialogue of subscribing between the entity to agency's subscription entity;
Steps A 5: after in the steps A 3 the request message authentication of subscribing to being passed through, the trigger event notification entity is according to the subscription incident in the request message that replaces subscribing to entity subscribes and subscribe to the URI of entity, sends and confirms that subscribing notification message is to subscribing to entity;
Need to prove, under the situation that the event notice entity passes through the request message authentication that replaces the subscription entity subscribes, trigger execution in step A5, and can not trigger steps A 5 after step X1 or the step X2.
Wherein, need to prove, in Session Initiation Protocol, it has been generally acknowledged that in the communication process based on dialogue, two the entity communication processs first time are set up the process of dialogue for request, the event notice entity sends and confirms subscribing notification message to the process of subscribing to entity in this embodiment, is equal to the event notice entity and initiatively sends and subscribe to the request of setting up dialogue between the entity.Steps A 5 is different with the notice based on Session Initiation Protocol of the prior art (NOTIFY) method, and existing NOTIFY method based on Session Initiation Protocol must be to be attached in the dialogue of having set up, and just can carry out.
Also need to prove for the ease of understanding, if be example still with a concrete request message body that replaces subscribing to entity subscribes in the steps A 1, the affirmation subscribing notification message that the event notice entity sends in steps A 5 can with reference to as next sample:
RE-NOTIFY?sip:8613507551007@10.85.29.189:8012;transport=udp?SIP/2.0
Via:SIP/2.0/UDP
10.78.234.29:5060;branch=z9hG4bKe804612b1f8303ffd2dfc486a;Role=1;
Call-ID:ZdmAg12893-ID00000002-H9M024S43@10.85.29.189
From:<sip:8613507551006@imsdemo.com>;tag=fcbc63a9
To:<sip:8613507551006@imsdemo.com>
CSeq:1RE-NOTIFY
Accept:application/sdp
Contact:<sip:2.32.32.7:30820>
Contact?Binding:<sip:2.32.32.7:30820>
Max-Forwards:69
Event:reg
Subscription-State:request;pol=xxxx;expires=6060
Content-Length:0
Content-Type:application/reginfo+xml
Wherein, this is confirmed in the sample of subscribing notification message, confirm that the RE-NOTIFY in the subscribing notification message represents that this affirmation subscribing notification message is a kind of new communication information that is different from prior art, can will use the Notification Method of this affirmation subscribing notification message to be called proactive notification method, i.e. RE-NOTIFY.In header field Subscription-State, comprise value Request, be used to show primary request.The value of this header field is not worth for this reason in the follow-up event change notification message; The value of parameter p ol is that xxxx represents to subscribe to the authentication information between entity and the agency's subscription entity, and parameter expires value is that the duration are subscribed in 6060 expressions, i.e. the duration of talking with between event notice entity and the subscription entity.Can be about this explanation of confirming other information in the subscribing notification message sample with reference to existing based on the notification message among the NOTIFY of Session Initiation Protocol, affirmation subscribing notification message in the present embodiment in the steps A 5 is used for setting up dialogue, so do not comprise the message body based on the NOTIFY of Session Initiation Protocol.
Steps A 6: after the subscription entity receives this affirmation subscribing notification message, this affirmation subscribing notification message is resolved;
Steps A 7: in subscribing to entity,, this affirmation subscribing notification message is carried out authentication to after this affirmation subscribing notification message parse success;
Wherein, by the explanation of steps A 6, subscribe to entity and can judge self whether to need to subscribe to the incident that is comprised in the affirmation subscribing notification message to steps A 7.After authentication is passed through, show that subscribing to entity confirms that needs are subscribed to and confirm the subscription incident that comprised in the subscribing notification message, and the information relevant, as duration of talking with between subscription entity and the event notice entity etc. with this subscription incident.
Steps A 8: when subscribing to entity this affirmations subscribing notification message authentication is passed through, subscribe to entity send authentication by this response of request message that replaces the subscription entity subscribes to the event notice entity, can be 200OK message;
Need to prove that the Expires header field in the response has shown the time that final subscription should continue, after the event notice entity is received this response, can subscribe to the time that continues according to the content modification of parameter in this response.This is different with the response to notification message among the RFC3265, is that notification entity sends the response message to subscribe message in RFC3265, sends response message to event change notification message for subscribing to entity in this example.
Steps A 9: the event notice entity receives authentication in the steps A 8 by confirming the response of subscribing notification message, set up with the subscription entity between dialogue.
By of the explanation of above steps A 1, can realize that the agency subscribes to the incident in the entity replacement subscription entity subscribes event notice entity to steps A 9.By above explanation to this method as can be known, this method is based on Session Initiation Protocol and has realized the method for subscribing in the network, has enriched the business based on Session Initiation Protocol, has enriched user experience.
Wherein, preferred, in steps A 6, when subscribing to entity parsing affirmation subscribing notification message failure, before steps A 8, this method can also comprise:
Step X3: to after this affirmation subscribing notification message parse failure, send and resolve failure response to the event notice entity in subscribing to entity, this response specifically can be the message of SIP 4xx, end operation.
It will be appreciated that also preferred, in steps A 7, when to the failure of affirmation subscribing notification message authentication, before steps A 8, this method can also comprise:
Step X4: when subscribing to entity when confirming the failure of subscribing notification message authentication, transmission can resolve and the unsanctioned response of authentication to the event notice entity, this response is concrete also can be the message of SIP 4xx, end operation.
For the ease of understanding, need to prove that also by the explanation of above a kind of method for subscribing based on Session Initiation Protocol that present embodiment is provided, the event notice entity is successively subscribed to entity with the agency, subscribed to entity and set up dialogue in the method.Follow-up subscribe to entity or subscribe to entity with the agency when communicating by letter, can be attached to and act on behalf of respectively and subscribe to entity or subscribe in the dialogue that entity sets up and carry out when this event notice entity.Therefore, for the method that makes present embodiment provide is more optimized, this method can also comprise following illustrated step.
Preferably, wherein after each, this method can also comprise in step X3, step X4, steps A 9:
Steps A 10: the response that the event notice entity sends according to the subscription entity that receives sends the notice request of confirming the result and subscribes to entity to the agency;
Need to prove that the affirmation result's who sends in the steps A 10 notice request includes but not limited to as follows:
(1) if the response that the subscription entity that receives sends is the response of SIP 200OK, the event notice entity is set up and the dialogue of subscribing to inter-entity.And the affirmation result's that transmission " is subscribed to the entity subscribes success " to agency's subscription entity notice request, perhaps the affirmation result's of " third party subscribes to success " notice request can think that subscribing to entity is exactly the third party, below has identical explanation;
(2) if the response that the subscription entity that receives sends is the response of SIP 4xx, cancellation of event notice entity and the notice affairs of subscribing between the entity, i.e. dialogue is set up in cancellation, and the agency is subscribed to the notice request of entity " the transmission third party subscribes to failure ".
Steps A 11: the agency subscribes to that the affirmation result's that entity sends the event notice entity that receives notice request is resolved, authentication;
Steps A 12: the agency subscribes to the result of entity according to parsing or authentication, sends response accordingly.
It will be appreciated that in realizing the method that the embodiment of the invention provides, the situation of acquiescence is for the agency subscribes to entity after completing steps A12, be through with and the event notice entity between dialogue.In fact, also can on the A1 step, define the duration that the agency subscribes to entity and the dialogue of event notice inter-entity, whether finish dialogue between the two and be to subscribe to and talk with the duration (being Expires:3030) in the request message of entity subscribes and determine by the replacement in the steps A 1.
Wherein, steps A 10 to steps A 12 is can existing SIP-NOTIFY method identical, specifies with reference to RFC3256.
More than the explanation of method that present embodiment is provided, make this method can realize acting on behalf of to subscribe to entity to replace subscribing to the incident in the entity subscribes event notice entity; When incident subscribed in the event notice entity changed, the event notice entity was included in the information of event change in the event change notification message, sends to the subscription entity.Therefore, preferred, this method can also comprise:
Steps A 13: the event notice entity according to set up in the steps A 9 and subscribe to dialogue between the entity, send event change notification message to subscribing to entity, comprise the information of event change in this event change notification message;
Wherein, the form of the event change notification message that sends in the steps A 13 can be similar to notification message format in the steps A 5, and the information of the event change form with message body is attached in this event change notification message.
Steps A 14: after subscribing to entity reception event change notification message, resolve and/or this event change notification message of authentication;
Steps A 15: subscribe to the result of entity, send event change notification and respond to the event notice entity according to parsing and/or authentication;
Steps A 16: the event notice entity receives the response of the event change notification message of subscribing to the entity transmission.
It will be appreciated that in the subscription duration of regulation, incident subscribed in the event notice entity changes, then can repeat above-mentioned steps A13 to steps A 16 between event notice entity and the subscription entity.
Preferably, after steps A 16, the method that present embodiment provides can also comprise:
Steps A 17: the event notice entity is according to the response of the event change notification message of the subscription entity transmission that receives in the steps A 16, and transmission subscription entity obtains the notice request of the state of subscription incident and subscribes to entity to the agency;
Wherein, the subscription entity that sends of the event notice entity notice request of obtaining the state of subscription incident can comprise the following form that is not limited to:
(1) if the response that the subscription entity that receives sends is the response of SIP 200OK, the event notice entity sends the notice request of " subscribe to entity and successfully obtain the subscription incident " and subscribes to entity for the agency;
(2) if the response that the subscription entity that receives sends is the response of SIP 4xx section, notice affairs between cancellation of event notice entity and the subscription entity, be end dialog, and the agency is subscribed to the notice request that entity sends " subscribe to entity and obtain the failure of subscription incident ".
Wherein, steps A 17 is similar to steps A 10, it will be appreciated that, steps A 17 normally in steps A 1, set and the event notice entity between dialogue just carry out during the duration, if do not set the dialogue duration in the steps A 1, subscribe to dialogue between entity and the event notice entity to the resource consumption of system in order to reduce the agency, usually after complete steps A 12, the initiatively dialogue between End Event notification entity and the agency's subscription entity.If it is interested in the notice things of subscribing between entity and the event notice entity that the agency subscribes to entity, the agency subscribe to that entity can be set in steps A 1 and the event notice entity between duration of talking with, promptly set the value of Expires header field.
Steps A 18 is to steps A 19, and is corresponding with A12 similar with steps A 11, please refer to the explanation to steps A 11 and A12.When the duration of subscribing to the dialogue of setting up between entity and the event notice entity finishes, the end-of-dialogue between them, whole flow process finishes.
Before the duration finishes, can also carry out the operation that following notice refreshes between event notice entity and the subscription entity, need to prove that this process is optionally, comprising:
Steps A 20: the event notice entity sends the refresh notification request message to the subscription entity according to event notice entity in the request message of the replacement subscription entity subscribes of agency's subscription entity transmission and the information of the dialogue duration between the subscription entity;
Wherein, the refresh notification request message that sends in this steps A 20 can be identical with the notification message that event notice entity in the steps A 5 sends for the first time, when the value of parameter expires be 0 or the value of Subscribe-State during for terminated explanation event notice entity want and the talk time end of subscribing between the entity, the effect of the refresh notification request message of event notice entity transmission is to confirm whether will finish this dialogue.When the value of parameter expires is the value of non-0 value and Subscribe-State when being request, show that the event notice entity wants inquiry to subscribe to entity, the subscription time closes to an end, and whether will revise the subscription time.Can comprise the Expires header field in the follow-up response message shows this request responding.
Steps A 21: subscribe to entity and receive the refresh notification request message, resolve and/or this notification message of authentication, according to the message that presets, the response that sends the refresh notification request message is to the event notice entity.
By execution in step A20 and steps A 21, whether event notice entity and subscribe to confirms end dialog between the entity, subscribe to entity according to the message that presets, whether determine end dialog, and the message that will confirm end dialog is included in and sends to the event notice entity in the response.Need continue dialogue if subscribe to entity, then the value of the expires that comprises in the response of returning is re-set as non-0 value.
Except the illustrated event notice entity of above steps A 20 and A21 initiatively and subscribe to end dialog between the entity, in fact, when following incident took place, dialogue between the two also was terminated, and comprising:
(1) subscribing to entity returns error message or notice request is not had response;
(2) subscribe to that Expires header field value is 0 in the message that entity returns.
Preferably, two kinds of agencies subscribe to entity to obtain the method for the subscription incident of subscribing to entity as follows among the above-mentioned steps A1:
As shown in Figure 4, a kind of method of obtaining the subscription incident comprises:
Step a1: the agency subscribes to entity and sends SIP INFO request, comprises the information and the authentication information of the incident of pulling subscription in this request message at least;
Step a2: after the subscription entity receives this SIP INFO request, parsing, this SIP INFO request of authentication;
Step a3: when authentication is passed through, sending the response that comprises the subscription incident and subscribe to entity to the agency in the subscription entity, also can be 200OK message;
Step a4: after agency's subscription entity receives the response of this affirmation subscription incident, get access to the subscription incident of subscribing to entity.
Another kind obtains the method for subscription incident, as shown in Figure 5, comprising:
Step b1: subscribe to entity and send the SIP-PUBLISH request, comprise subscription incident and authentication information in this request at least;
Step b2: after agency's subscription entity was received this SIP-PUBLISH request, parsing, this SIP-PUBLISH request of authentication got access to the subscription incident of subscribing to entity;
Step b3: the agency subscribes to entity when authentication is passed through, and sends the response of confirming the subscription incident and subscribes to entity, i.e. 200OK message to the agency.
More than be that two kinds of agencies subscribe to the method that entity gets access to subscription entity subscribes incident, these two kinds of methods all are based on the method that Session Initiation Protocol obtains the subscription incident, it will be appreciated that, above-mentioned two kinds of methods adopt SIPINFO and SIP PUBLISH method respectively, in specific implementation process, be not limited to said method,, also can use SIP INFO method in the method two as using SIP PUBLISH method in the method one.Even, adopt other SIP method, carry subscription incident and authentication information and finish above-mentioned functions, also be allowed to.Further, the agency subscribes to the method that entity obtains the subscription incident and can be not limited to Session Initiation Protocol method (SIPMethod).
Explanation by above step to this method, the event notice entity has been realized and has been acted on behalf of to subscribe to and set up dialogue and end dialog between the entity, also realize the incident notification entity and subscribed to the process of setting up dialogue and end dialog between the entity, in above-described two dialogues, successful realization the agency subscribe to the purpose that the entity agency subscribes to the incident in the entity subscribes event notice entity, expand existing Session Initiation Protocol, made the user can enjoy better experience.
Embodiment three,
Present embodiment provides a kind of communication system, and referring to as shown in Figure 6, this common system comprises: the agency subscribes to entity 10, event notice entity 20 and subscribes to entity 30.
Wherein, the agency subscribes to entity 10, is used for the subscription incident according to the subscription entity 30 that obtains, and sends to replace subscribing to the request message of entity subscribes to event notice entity 20;
Subscribe to entity 30, be used to receive the affirmation subscribing notification message that event notice entity 20 sends, this affirmation subscribing notification message is resolved and authentication, when this confirms that subscribing notification message is by after the authentication, send authentication and pass through this response of confirming subscribing notification message to event notice entity 20, this authentication can be 200OK by the response of this affirmation subscribing notification message.
Wherein, message transmitted can all be a sip message between event notice entity 20 and agency's subscription entity 10, the subscription entity 30; Message transmitted can be an arbitrary form between agency's subscription entity 10 and the subscription entity 30.
Need to prove that also three kinds of entities all are respectively a kind of network entities.Wherein, it can be the user agent (UA that has now in the SIP network that the agency subscribes to entity, User Agent), or (the IMS of internet protocol multi-media system, IP Media System) user device in network unit (UE, User Equipment), P-CSCF or application server (AS, Application Service); It is similar with the subscription entity to subscribe to entity, also can be UA in the SIP network, the perhaps UE in the IMS network, P-CSCF or AS; The event notice entity can be the UA in the existing SIP network, the perhaps UE in the IMS network, AS or CSCF etc.
Explanation by above a kind of communication system based on Session Initiation Protocol that present embodiment is provided, event notice entity 20 and agency subscribe to and set up dialogue between the entity 10, subscribe to the request message of entity subscribes according to the replacement of obtaining in the dialogue, send and confirm that subscribing notification message is to subscribing to entity 30, initiatively set up dialogue with subscription entity 20, after receiving the 200OK message of subscribing to entity 20 transmissions, set up and subscribe to the dialogue between the entity 20, realized subscribing to the purpose that entity 20 is subscribed to incident in the event notice entity 30.
Preferably, event notice entity 20 also is used for after the request message authentication of this replacement subscription entity subscribes is passed through, and sends authentication and passes through response to agency's subscription entity 10, sets up and act on behalf of the dialogue of subscribing between the entity;
The agency subscribes to entity 10, also is used to receive the response that authentication that event notice entity 20 sends passes through and subscribes to entity to the agency, set up and event notice entity 20 between dialogue.
Preferably, event notice entity 20 also is used for subscribing to the response that entity 30 sends according to receiving, and sends the notice request of confirming the result and subscribes to entity 10 to the agency; The response that receives that the agency subscribes to that entity 10 sends to the notice request of confirming the result;
Then the agency subscribes to entity 10, also be used to receive the affirmation result's that event notice entity 20 sends notice request, notice request to this affirmation result is resolved and/or authentication, according to the result of parsing and/or authentication, sends the response to the notice request of confirming the result.
Preferably, event notice entity 20 also is used for basis and subscribes to the dialogue that entity 30 is set up, and sends event change notification message to subscribing to entity 30, comprises the signal of event change in this event change notification message; Receive and subscribe to the event change notification response that entity sends;
Then subscribe to entity 30, also be used to receive event change notification message, resolve and/or this event change notification message of authentication,, send event change notification and respond to event notice entity 20 according to the result of parsing and/or authentication.
Preferably, event notice entity 20, also be used for according to receive subscribe to that entity 30 sends the event change notification response, send to subscribe to the notice request that entity obtains the state of subscription incident and subscribe to entity, the response of notice request that this subscription entity is obtained the state of subscription incident that receives that the agency subscribes to that entity 10 sends to the agency;
Then the agency subscribes to entity 10, also be used to receive the notice request that the subscription entity obtains the state of subscription incident, this request is resolved and/or authentication, according to resolving and/or the result of authentication, the response of notice request that sends the corresponding state that this subscription entity is obtained the subscription incident is to event notice entity 20.
Preferably, event notice entity 20 also is used to send the refresh notification request to subscribing to entity 30, receive subscribe to that entity 30 sends to this refresh notification request responding;
Subscribe to entity 30, also be used to receive the refresh notification request, this refresh notification request is resolved and/or authentication,, send this event notice entity 20 of refresh notification request responding according to resolving and/or authenticating result.
Explanation by above preferred embodiment to this communication system, make event notice entity 20 can with subscribe in the dialogue that entity 10 initiatively sets up, to act on behalf of and subscribe to entity 10 agency's subscription entities 30 events subscribed, being notified to of active subscribed to entity 10 when this event change; And event notice entity 20 can also send to subscription status the agency and subscribe to entity 10, is convenient to act on behalf of the monitoring of subscribing to 10 pairs of these incidents of entity; End dialog between the entity 30 can also be realized initiatively and be subscribed to event notice entity 20.By above explanation as can be known, the realization of this communication system makes Session Initiation Protocol obtain more expansion.
Embodiment four
Present embodiment provides a kind of event notice entity, and referring to shown in Figure 7, this event notice entity comprises: first receiving element 201 and first transmitting element 204.
Wherein, first receiving element 201, be used to receive the request message that the agency subscribes to the replacement subscription entity subscribes of entity transmission, comprise at least in the request message of described replacement subscription entity subscribes: subscribe to the incident of entity subscribes and the URL(uniform resource locator) URI of subscription entity; Receive of the response of the authentication of subscription entity transmission, the dialogue between foundation and the described subscription entity by described affirmation subscribing notification message;
First transmitting element 204 is used for the 3rd events subscribed and the URI that subscribes to entity according to the request message of described replacement subscription entity subscribes, sends to confirm that subscribing notification message is to the subscription entity.
It will be appreciated that, when the authentication that receives the transmission of subscription entity in first receiving element 201 is passed through to confirm the response of subscribing notification message, the active foundation of event notice entity success and the dialogue between the subscription entity.
Optionally, this event notice entity also comprises: first authenticating unit 203 is used for the request message of described replacement subscription entity subscribes is carried out authentication;
First transmitting element 204 then, the request message that also is used for subscribing to entity subscribes when described replacement be during by authentication, sends the response that authentication passes through and subscribe to entity to the agency, set up with agency's subscription entity between dialogue.
Explanation by the above event notice entity that present embodiment is provided, this event notice entity receives the request message that the agency subscribes to the replacement subscription entity subscribes of entity transmission, the 3rd subscription request message is resolved, after the authentication, send authentication and subscribe to entity to the agency by response, according to the request message that replaces subscribing to entity subscribes, send a notification message to subscribing to entity, receive and subscribe to the response of entity authentication by this affirmation subscribing notification message, set up and subscribe to the dialogue between the entity, thereby realized that the agency subscribes to the purpose that entity replaces subscribing to the incident in the entity subscribes event notice entity.
Preferably, first transmitting element 204 in this event notice entity also is used for when judging that request message that entity subscribes is subscribed in described replacement is by authentication, sends the response that authentication passes through and subscribes to entity to the agency, set up with agency's subscription entity between dialogue.
Preferably, this event notice entity can also comprise: second transmitting element 205 and second receiving element 206, and the dotted line shown in Fig. 7 represents that these two logical blocks are to occur in pairs, the dotted line between other the logical block also has identical explanation.
Wherein, second transmitting element 205 is used for the response according to the subscription entity transmission that receives, and sends the notice request of confirming the result and subscribes to entity to the agency;
Wherein, the concrete message that sends in second transmitting element 205 can be including, but not limited to as follows:
(1) if the response that the subscription entity that receives sends is the response of SIP 200 OK, the event notice entity is set up and the dialogue of subscribing to inter-entity.And the notice request of the agency being subscribed to entity transmission " it is successful to subscribe to entity subscribes ";
(2) if the response that the subscription entity that receives sends is the response of SIP 4xx section, cancellation of event notice entity and the notice affairs of subscribing between the entity, i.e. end dialog, and the notice request of the agency being subscribed to entity " send subscribe to entity subscribes fail ".
Second receiving element 206 is used to receive that the agency subscribes to that entity sends to the response of the notice request of confirming the result.
By why making this event notice entity itself and the subscription status of subscribing between the entity can be notified to agency's subscription entity second receiving element 206 and second transmitting element 205.
Preferably, this event notice entity can also comprise: the 3rd transmitting element 207 and the 3rd receiving element 208,
Wherein, the 3rd transmitting element 207 is used for basis and subscribes to the dialogue that entity is set up, and sends event change notification message to subscribing to entity;
Wherein, the sign of successfully setting up dialogue can be according to receive in first receiving element the response of authentication by notification message.
The 3rd receiving element 208 is used to receive the event change notification response of subscribing to the entity transmission.
By increasing the 3rd transmitting element 207 and the 3rd receiving element 208, make that this event notice entity can be according to the incident of subscribing to entity subscribes, when incident changed, notice was subscribed to entity.
Preferably, this event notice entity can also comprise: the 4th transmitting element 209 and the 4th receiving element 210.
Wherein, the 4th transmitting element 209, the event change notification that is used for receiving according to the 3rd receiving element 208 responds, and transmission subscription entity obtains the notice request of the state of subscription incident and subscribes to entity to the agency;
The 4th receiving element 210 is used to receive that the agency subscribes to that entity sends obtains the request responding same period of the state of subscription incident to subscribing to entity.
By increasing the 4th transmitting element 209 and the 4th receiving element 210, make this event notice entity and to subscribe between the entity subscription status and be notified to the agency and subscribe to entity it.
Preferably, this event notice entity can also comprise: the 5th transmitting element 211 and the 5th receiving element 212.
Wherein, the 5th transmitting element 211 is used to send the refresh notification request to subscribing to entity;
Wherein, specifically can be to subscribe to event notice entity and the information of subscribing to the dialogue duration between the entity in the request message that replacement that entity sends subscribes to entity subscribes in the 5th transmitting element 211, send the refresh notification request to the subscription entity according to the agency that first receiving element receives.
The 5th receiving element 212, be used to receive subscribe to that entity sends to this refresh notification request responding.
By increasing the 5th transmitting element 211 and the 5th receiving element 212, make the event notice entity can initiatively finish and subscribe to the dialogue of setting up between the entity.
Embodiment five
Present embodiment provides a kind of subscription entity, referring to shown in Figure 8, comprising: the 6th receiving element 301, second authenticating unit 303 and the 6th transmitting element 304.
Wherein, the 6th receiving element 301 is used to receive the replacement that the event notice entity sends and subscribes to the request message of entity subscribes;
Described second authenticating unit 303, the request message that is used for the described replacement that receives is subscribed to entity subscribes carries out authentication;
Described the 6th transmitting element 304, be used for when authentication by the time, send authentication by this response of request message that replaces subscribing to entity subscribes to the event notice entity, set up and the event notice entity between dialogue.
Optionally, the 6th receiving element 301 also is used to receive the event change notification message that the event notice entity sends;
Then second authenticating unit 303 also is used for described event change notification message is carried out authentication;
Then the 6th transmitting element 304 also is used for according to authenticating result, and the response that sends event change notification message is to described event notice entity.
Optionally, the 6th receiving element 301 also is used to receive the refresh notification request that described event notice entity sends;
Then second authenticating unit 303 also is used for authentication is carried out in described refresh notification request;
The 6th transmitting element 304 then also is used for according to authenticating result and the information that presets, send the refresh notification request responding to shown in the event notice entity.
By above this explanation of subscribing to entity has been set up dialogue between this subscription entity and the event notice entity, this dialogue is that the successor notification entity sends the dialogue that the subscription incident is depended on.
Embodiment six
Present embodiment provides a kind of agency to subscribe to entity, referring to shown in Figure 9, comprising: the 7th receiving element 401 and the 8th transmitting element 402;
Wherein, the 7th receiving element 401 is used to receive the subscription incident that entity sends of subscribing to;
The 7th transmitting element 402 is used for the subscription incident that receives according to described, sends to replace subscribing to the request message of entity subscribes to the event notice entity.
Optionally, the 7th receiving element 401 also is used to receive the response that authentication that described event notice entity sends is passed through, set up and the event notice entity between dialogue.
Optionally, the 7th receiving element 401, the subscription entity that also is used for described event notice entity transmission obtains the notice request of the state of subscription incident;
The 7th transmitting element then is used to send response to notice request to the event notice entity.
By the above explanation that this agency is subscribed to entity, this agency's subscription entity can replace subscribing to the incident in the entity subscribes event notice entity, and the function that feasible agency subscribes to entity is abundanter.
One of ordinary skill in the art will appreciate that all or part of step in the whole bag of tricks of the foregoing description is to instruct relevant hardware to finish by program, this program can be stored in the computer-readable recording medium, and storage medium can comprise: ROM, RAM, disk or CD etc.
More than a kind of method for subscribing based on Session Initiation Protocol, device that the embodiment of the invention provided are described in detail, used specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (18)
1. the method for subscribing of a dialogue-based initializtion protocol is characterized in that, comprising:
The reception agency subscribes to the replacement of entity transmission and subscribes to the request message of entity subscribes, comprises at least in the request message of described replacement subscription entity subscribes: subscribe to the incident of entity subscribes and the URL(uniform resource locator) URI of subscription entity;
According to the incident of the subscription entity subscribes in the request message of described replacement subscription entity subscribes and the URI of subscription entity, send and confirm that subscribing notification message is to the subscription entity;
Receive of the response of the authentication of subscription entity transmission, the dialogue between foundation and the described subscription entity by described affirmation subscribing notification message.
2. method according to claim 1 is characterized in that, the replacement that described reception agency subscribes to the entity transmission is subscribed to after the request message of entity subscribes, and described method also comprises:
The request message of described replacement being subscribed to entity subscribes carries out authentication;
When the request message authentication of described replacement subscription entity subscribes was passed through, the response that the transmission authentication is passed through was subscribed to entity to described agency, and foundation and described agency subscribe to the dialogue between the entity.
3. method according to claim 1 is characterized in that, described reception is subscribed to after the response of authentication by described affirmation subscribing notification message of entity transmission, and described method also comprises:
Subscribe to entity by confirming the response of subscribing notification message, send the notice request of confirming the result to the agency according to the described authentication that receives.
4. method according to claim 1 is characterized in that, the response of the authentication of entity transmission by described affirmation subscribing notification message subscribed in described reception, and after the dialogue between foundation and the described subscription entity, described method also comprises:
According to described foundation and subscribe to dialogue between the entity, send event change notification message to described subscription entity;
Receive the response of the event change notification message of described subscription entity transmission.
5. method according to claim 4 is characterized in that, after the response of the event change notification message that the described subscription entity of described reception sends, described method also comprises:
According to the response of described event change notification message, transmission subscription entity obtains the notice request of the state of subscription incident and subscribes to entity to described agency.
6. according to each described method of claim 1 to 5, it is characterized in that the response of the authentication of entity transmission by described affirmation subscribing notification message subscribed in described reception, after the dialogue between foundation and the described subscription entity, described method also comprises:
Subscribe to event notice entity and the information of subscribing to the dialogue duration between the entity in the request message that replacement that entity sends subscribes to entity subscribes according to described agency, the request of transmission refresh notification is to described subscription entity.
7. an event notice entity is characterized in that, comprising: first receiving element and first transmitting element;
Described first receiving element, be used to receive the request message that the agency subscribes to the replacement subscription entity subscribes of entity transmission, comprise at least in the request message of described replacement subscription entity subscribes: subscribe to the incident of entity subscribes and the URL(uniform resource locator) URI of subscription entity; Receive of the response of the authentication of subscription entity transmission, the dialogue between foundation and the described subscription entity by described affirmation subscribing notification message;
Described first transmitting element, be used for when the request message of judging described replacement subscription entity subscribes passes through authentication, according to the incident of the subscription entity subscribes in the request message of described replacement subscription entity subscribes and the URI of subscription entity, send and confirm that subscribing notification message is to the subscription entity.
8. event notice entity according to claim 7 is characterized in that, described event notice entity also comprises: first authenticating unit is used for the request message of described replacement subscription entity subscribes is carried out authentication;
The request message that described first transmitting element also is used for subscribing to entity subscribes when described replacement is during by authentication, sends the response that authentication passes through and subscribes to entity to the agency, set up with agency's subscription entity between dialogue.
9. event notice entity according to claim 7 is characterized in that, described event notice entity also comprises: second receiving element and second transmitting element;
Described second transmitting element is used for subscribing to entity by confirming the response of subscribing notification message, send the notice request of confirming the result to the agency according to the described authentication that receives;
Described second receiving element is used to receive that the agency subscribes to that entity sends to the response of the notice request of confirming the result.
10. event notice entity according to claim 7 is characterized in that, described event notice entity also comprises: the 3rd receiving element and the 3rd transmitting element;
Described the 3rd transmitting element, be used for according to described foundation and subscribe to dialogue between the entity, send event change notification message to described subscription entity;
Described the 3rd receiving element is used to receive the response of the event change notification message that described subscription entity sends.
11. event notice entity according to claim 10 is characterized in that, described event notice entity also comprises: the 4th receiving element and the 4th transmitting element;
Described the 4th transmitting element is used for the response according to described event change notification message, and transmission subscription entity obtains the notice request of the state of subscription incident and subscribes to entity to described agency;
Described the 4th receiving element is used to receive that described agency subscribes to that entity sends to subscribing to the response of notice request that entity obtains the state of subscription incident.
12. according to each described event notice entity of claim 7 to 11, described event notice entity also comprises: the 5th transmitting element and the 5th receiving element;
Described the 5th transmitting element is used for subscribing to the event notice entity and the information of subscribing to the dialogue duration between the entity that the request message of entity subscribes is subscribed in replacement that entity sends according to described agency, and the request of transmission refresh notification is to described subscription entity;
Described the 5th receiving element is used to receive the refresh notification request responding that described subscription entity sends.
13. subscribe to entity for one kind, it is characterized in that, comprising: the 6th receiving element, second authenticating unit and the 6th transmitting element;
Described the 6th receiving element is used to receive the replacement that the event notice entity sends and subscribes to the request message of entity subscribes;
Described second authenticating unit, the request message that is used for the described replacement that receives is subscribed to entity subscribes carries out authentication;
Described the 6th transmitting element, be used for when authentication by the time, send authentication by this response of request message that replaces subscribing to entity subscribes to the event notice entity, set up and the event notice entity between dialogue.
14. subscription entity according to claim 13 is characterized in that, described the 6th receiving element also is used to receive the event change notification message that the event notice entity sends;
Described second authenticating unit also is used for described event change notification message is carried out authentication;
Described the 6th transmitting element also is used for according to authenticating result, and the response that sends event change notification message is to described event notice entity.
15., it is characterized in that described the 6th receiving element also is used to receive the refresh notification request that described event notice entity sends according to claim 13 or 14 described subscription entities;
Described second authenticating unit also is used for authentication is carried out in described refresh notification request;
Described the 6th transmitting element also is used for according to authenticating result and the information that presets, send the refresh notification request responding to shown in the event notice entity.
16. an agency subscribes to entity, it is characterized in that, comprising: the 7th receiving element and the 8th transmitting element;
Described the 7th receiving element is used to receive the subscription incident that entity sends of subscribing to;
Described the 7th transmitting element is used for the subscription incident that receives according to described, sends to replace subscribing to the request message of entity subscribes to the event notice entity.
17. agency according to claim 16 subscribes to entity, it is characterized in that, described the 7th receiving element also is used to receive the response that authentication that described event notice entity sends is passed through, set up and the event notice entity between dialogue.
18. agency according to claim 16 subscribes to entity, it is characterized in that, described the 7th receiving element, and the subscription entity that also is used for described event notice entity transmission obtains the notice request of the state of subscription incident;
Described the 7th transmitting element is used to send response to notice request to described event notice entity.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910130092.4A CN101867590B (en) | 2009-04-14 | 2009-04-14 | Subscription method based on session initiation protocol, and device thereof |
PCT/CN2010/071174 WO2010118656A1 (en) | 2009-04-14 | 2010-03-22 | Subscription method and device based on session initiation protocol |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910130092.4A CN101867590B (en) | 2009-04-14 | 2009-04-14 | Subscription method based on session initiation protocol, and device thereof |
Publications (2)
Publication Number | Publication Date |
---|---|
CN101867590A true CN101867590A (en) | 2010-10-20 |
CN101867590B CN101867590B (en) | 2013-04-24 |
Family
ID=42959155
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN200910130092.4A Expired - Fee Related CN101867590B (en) | 2009-04-14 | 2009-04-14 | Subscription method based on session initiation protocol, and device thereof |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101867590B (en) |
WO (1) | WO2010118656A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108833331A (en) * | 2018-04-09 | 2018-11-16 | 海信集团有限公司 | A kind of creation of resource object, resource object state reporting method and device |
CN111865888A (en) * | 2019-04-29 | 2020-10-30 | 华为技术有限公司 | A kind of authorization method and device for proxy subscription |
WO2020220919A1 (en) * | 2019-04-29 | 2020-11-05 | 华为技术有限公司 | Authorization method and device for proxy subscription |
CN114710557A (en) * | 2022-04-12 | 2022-07-05 | 树根互联股份有限公司 | Data transmission method and device and data release equipment |
US20230027164A1 (en) * | 2019-09-26 | 2023-01-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, apparatuses and computer-readable media relating to event subscription in a communication network |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050015499A1 (en) * | 2003-05-15 | 2005-01-20 | Georg Mayer | Method and apparatus for SIP user agent discovery of configuration server |
CN1859322A (en) * | 2005-12-17 | 2006-11-08 | 华为技术有限公司 | Method for searching user's information |
CN101002451A (en) * | 2004-06-23 | 2007-07-18 | 诺基亚公司 | Method, system and computer program to enable querying of resources in a certain context by definition of SIP event package |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0213726D0 (en) * | 2002-06-14 | 2002-07-24 | Nokia Corp | A communication system |
US20040255302A1 (en) * | 2003-06-10 | 2004-12-16 | Nokia Corporation | Systems and methods for content and service registration, query and subscription, and notification across local service discovery domains |
CN101047691B (en) * | 2006-04-29 | 2010-04-07 | 华为技术有限公司 | Method for integral controlling subscribe |
-
2009
- 2009-04-14 CN CN200910130092.4A patent/CN101867590B/en not_active Expired - Fee Related
-
2010
- 2010-03-22 WO PCT/CN2010/071174 patent/WO2010118656A1/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050015499A1 (en) * | 2003-05-15 | 2005-01-20 | Georg Mayer | Method and apparatus for SIP user agent discovery of configuration server |
CN101002451A (en) * | 2004-06-23 | 2007-07-18 | 诺基亚公司 | Method, system and computer program to enable querying of resources in a certain context by definition of SIP event package |
CN1859322A (en) * | 2005-12-17 | 2006-11-08 | 华为技术有限公司 | Method for searching user's information |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108833331A (en) * | 2018-04-09 | 2018-11-16 | 海信集团有限公司 | A kind of creation of resource object, resource object state reporting method and device |
CN108833331B (en) * | 2018-04-09 | 2020-12-08 | 海信集团有限公司 | Resource object creating method and device and resource object state reporting method and device |
CN111865888A (en) * | 2019-04-29 | 2020-10-30 | 华为技术有限公司 | A kind of authorization method and device for proxy subscription |
WO2020220919A1 (en) * | 2019-04-29 | 2020-11-05 | 华为技术有限公司 | Authorization method and device for proxy subscription |
CN111865888B (en) * | 2019-04-29 | 2022-08-19 | 华为技术有限公司 | Proxy subscription authorization method and device |
US20230027164A1 (en) * | 2019-09-26 | 2023-01-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, apparatuses and computer-readable media relating to event subscription in a communication network |
US12182637B2 (en) * | 2019-09-26 | 2024-12-31 | Telefonaktiebolaget L M Ericsson (Publ) | Method, apparatuses and computer-readable media relating to event subscription in a communication network |
CN114710557A (en) * | 2022-04-12 | 2022-07-05 | 树根互联股份有限公司 | Data transmission method and device and data release equipment |
Also Published As
Publication number | Publication date |
---|---|
CN101867590B (en) | 2013-04-24 |
WO2010118656A1 (en) | 2010-10-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101682617B (en) | Method for determining multimedia capacity, multimedia application server and system | |
CN101518031B (en) | Mechanism for charging and session handling supporting forking | |
EP2266282B1 (en) | Apparatus, method, system and program for communication | |
JP4549414B2 (en) | Communication method and communication system | |
US9106716B2 (en) | Method, apparatus, and system for cross-platform conference convergence | |
EP1619854A1 (en) | SIP message extension for push to watch service | |
EP1909434A1 (en) | Subscribing method and device | |
CN101227457A (en) | System and method for identifying communication service | |
CN101674313A (en) | SIP registration method for server to actively inform user switching, system and device thereof | |
KR20110050439A (en) | Method and system for selective call forwarding based on media attributes in telecommunication network | |
WO2008044970A1 (en) | Ims device reconfiguration | |
US7912042B2 (en) | IMS surrogate registration | |
CN101867590B (en) | Subscription method based on session initiation protocol, and device thereof | |
CN101779443A (en) | Call transfer with multiple application servers in session initiation protocol-based network | |
US7945275B2 (en) | Sessions in a communication system | |
CN102342076A (en) | Capability Query Handling in a Communication Network | |
CN101123523B (en) | A method for creating combined conference of multiple media types | |
US20110090904A1 (en) | Method and network element for implementing a customized video service in ims networks | |
CN1889565B (en) | Session establishing method | |
CN101005502B (en) | Service scenario obtaining, control method and its control system and medium resource server | |
CN101789932B (en) | Game service processing method, device and system | |
EP2314040A1 (en) | Auxiliary sip services | |
CN101031139B (en) | Method for controlling call entity release session | |
CN104205765A (en) | HOLD announcement configuration | |
CN101686137A (en) | Implement method, device and system of conference service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
CF01 | Termination of patent right due to non-payment of annual fee | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130424 |