CN102769835A - Method and device for call handling - Google Patents
Method and device for call handling Download PDFInfo
- Publication number
- CN102769835A CN102769835A CN201110115133XA CN201110115133A CN102769835A CN 102769835 A CN102769835 A CN 102769835A CN 201110115133X A CN201110115133X A CN 201110115133XA CN 201110115133 A CN201110115133 A CN 201110115133A CN 102769835 A CN102769835 A CN 102769835A
- Authority
- CN
- China
- Prior art keywords
- user
- state
- application server
- calling
- respect
- 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.)
- Pending
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The invention provides a method for call handling. The method for call handling includes that an application server on a calling party side monitors a call initiated to a user in a current district, and when a failed call is monitored, the application server on the calling party side positively transmits a subscription request to an application server on a called party side so as to subscribe the called state; and the application server on the called party side monitors user events in the district thereof, positively reckons the called state according to the monitored events and informs the application server on the calling party side of the called latest state. Therefore, a calling party can know the state of a called party timely and accurately, and the communication establishment success rate can be increased. Moreover, the called party can have different states for different calling parties. Different from the prior art, the method has the advantages that a core network can reckon the state of the user positively and timely rather than passively waits for notices of the user, and more states can be provided, so that more information can be provided.
Description
Technical field
The application relates to communication network, relates in particular to a kind of method and apparatus of handling calling.
Background technology
When the calling subscriber called out the called subscriber, through the situation that regular meeting's appearance can't be connected, for example the called subscriber did not start shooting, converses, is inconvenient to answer or the called subscriber does not carry mobile phone etc.When if the calling subscriber has urgent thing, called callback is answered or waited for passively to retry up to called again and again usually.Yet the called subscriber sometimes is inconvenient to answer, and such as just in session, does not perhaps have timely callback caller afterwards, does not perhaps have timely discovery not receive calls etc., causes the calling subscriber can't successfully call out the called subscriber.These all are because the calling subscriber does not know the situation of the call failure that called subscriber's current states causes.Thereby network needs to infer called subscriber's state and with called subscriber's state subscriber call in time.
Some standard has been done relevant regulation such as TS 24.141 to the business that appears in the IMS network among the 3GPP, has wherein described the IMS entity and how to have subscribed to and issuing and presenting information, can comprise user's upstate in this presentation information.But present the notice that business focuses on called state, these states all are known states and are that called subscriber oneself confirms it does not describe the state how the IMS core net detected or to infer certain entity automatically.
Summary of the invention
In order to solve the deficiency that exists in the prior art, the present invention proposes a kind of brand-new scheme of calling out of in communication network, handling.
According to a first aspect of the invention, proposed a kind of method that in application server, is used to handle calling, this method may further comprise the steps: a1. calls out the local Client-initiated of said application server and monitors; The calling of a2. the not success that monitors being set up, to the application server transmission subscribe request of said calling called end, said subscribe request is used to subscribe to said called state; This method also comprises: a3. receives the state notification message from second application server, comprising second state of user; A4. to user's transmit status notification message of subscribing to said second User Status, comprising said second state of user.
Preferably, after above-mentioned steps a4, this method is further comprising the steps of: if said second user's of a5. upstate is available, then said application server is said second user and subscribe to set up between the user of said second User Status and call out.
Preferably, said step a2 further comprises: said subscribe request is used to subscribe to the state of said called caller with respect to said calling; Said state notification message among the said step a3 further comprises the upstate of second user with respect to first user; Said step a4 further comprises: to said first user's transmit status notification message, comprising said second user with respect to first state of user.
Preferably, said step a5 further comprises: if said second user is available with respect to first state of user, then said application server is set up calling between said second user and said first user.
According to a second aspect of the invention, proposed a kind of method that in application server, is used to handle calling, said method comprising the steps of: b1. monitors the incident relevant with state exchange that the local user of said application server is taken place; B2. according to the incident that monitors, the more state of user of the said incident of kainogenesis; B3. to the application server transmit status notification message of subscribing to said User Status, wherein comprised said user's last state;
Preferably, said method is further comprising the steps of: b4. receives the state subscription request from first application server, has wherein comprised subscriber's sign and subscribed person sign; B5. judge whether said subscriber has the authority of subscription; If b6. said subscriber has the authority of subscription,, wherein comprised said subscribed person's last state to the first application server transmit status notification message.
Preferably, said b2 further comprises: as said user during to a certain calling no response, said state of user is set to " unavailable "; When said user had refused a certain calling, said state of user was set to " only note can be used "; When said user when a certain user has initiated to call out or has replied a certain calling, said state of user is set to " available "; When said user when a certain user has sent note and current state when " unavailable ", said state of user is set to " only note can be used ".
Preferably, said b2 further comprises: when said user has refused from first user calling, said user all is set to " only note can be used " with respect to the state of user that priority is equal to or less than said first user; As said user during to a certain calling no response, said user is set to " unavailable " with respect to every other state of user; When said user when a certain user has initiated calling, said user is set to " available " with respect to every other state of user; When said user answer during from first user calling, said user all is set to " available " with respect to the state of user that priority is greater than or equal to said first user; When said user answer during from first user calling, be " unavailable " if said user is lower than said first user's state of user with respect to certain priority, then said state is set to " only note can be used "; When said user when first user has sent note, if said user is " unavailable " with respect to other certain state of user, then said state is set to " only note can be used ".
According to a third aspect of the present invention, proposed a kind of device that in application server, is used to handle calling, said device comprises: first monitoring device is used for the local Client-initiated of said application server called out and monitors; Subscribe to device, be used for the calling to the not success foundation that monitors, to the application server transmission subscribe request of said calling called end, said subscribe request is used to subscribe to said called state; First receiving device is used to receive the state notification message from second application server, comprising second state of user; First dispensing device is used for to user's transmit status notification message of subscribing to said second User Status, comprising said second state of user.
Preferably, said device also comprises: the call setup device, but be used for when said second user's upstate for the time spent at said application server said second user with subscribe to set up between the user of said second User Status and call out.
Preferably, the said subscription device subscribe request of sending is further used for subscribing to the state of said called caller with respect to said calling; The state notification message that said first receiving device receives further comprises the upstate of second user with respect to first user; Said first dispensing device is further used for to said first user's transmit status notification message, comprising said second user with respect to first state of user.
Preferably, but said call setup device be further used between said second user and said first user, setting up calling with respect to first state of user for the time spent as said second user.
According to a forth aspect of the invention, proposed a kind of device that in application server, is used to handle calling, said device comprises: second monitoring device is used for the incident relevant with state exchange that the local user of said application server is taken place monitored; The state updating device is used for taking place according to the event update that monitors the state of user of said incident; The state notifying device is used for wherein having comprised said user's last state to the application server transmit status notification message of subscribing to said User Status;
Preferably, said device also comprises: second receiving system, be used to receive state subscription request from first application server, and wherein comprised subscriber's sign and subscribed person sign; Judgment means is used to judge whether said subscriber has the authority of subscription; Said state notifying device also is used for having when subscribing to authority to the first application server transmit status notification message as said subscriber, has wherein comprised said subscribed person's last state.
Preferably,, said state updating device is further used for: as said user during to a certain calling no response, said state of user is set to " unavailable "; When said user had refused a certain calling, said state of user was set to " only note can be used "; When said user when a certain user has initiated to call out or has replied a certain calling, said state of user is set to " available "; When said user when a certain user has sent note and current state when " unavailable ", said state of user is set to " only note can be used ".
Preferably, said state updating device is further used for: when said user has refused from first user calling, said user all is set to " only note can be used " with respect to the state of user that priority is equal to or less than said first user; As said user during to a certain calling no response, said user is set to " unavailable " with respect to every other state of user; When said user when a certain user has initiated calling, said user is set to " available " with respect to every other state of user; When said user answer during from first user calling, said user all is set to " available " with respect to the state of user that priority is greater than or equal to said first user; When said user answer during from first user calling, be " unavailable " if said user is lower than said first user's state of user with respect to certain priority, then said state is set to " only note can be used "; When said user when first user has sent note, if said user is " unavailable " with respect to other certain state of user, then said state is set to " only note can be used ".
Through method and apparatus of the present invention, core network can be extrapolated called subscriber's state automatically according to event, and in time notice is given the calling subscriber; Thereby make the calling subscriber after learning called state, take appropriate action; Such as when learning that called state is " unavailable ", avoid attempting blindly redialing, thereby save because of repeatedly redialing shared Internet resources; Call peer again when learning that called state becomes " available "; When learning that called state is " only note can be used ", only through note with to side communication, the calling that averts failure.Adopt method and apparatus of the present invention, can improve the success rate of call setup to a certain extent, save Internet resources.
And the present invention can provide the different called state for different calling subscribers, so not only can protect called privacy, and very big flexibility is provided.
The various aspects of the present invention explanation of specific embodiment that will be through hereinafter and more clear.
Description of drawings
Through reading the detailed description of doing with reference to following accompanying drawing that non-limiting example is done, above-mentioned and other characteristics of the present invention will become more apparent:
Fig. 1 shows application scenarios sketch map according to an embodiment of the invention;
Fig. 2 shows the flow chart that processing according to an embodiment of the invention is called out;
Fig. 3 shows the flow chart that processing according to an embodiment of the invention is called out;
Fig. 4 shows the structured flowchart of in application server, handling the device of calling out according to an embodiment of the invention;
Fig. 5 shows the structured flowchart of in application server, handling the device of calling out according to an embodiment of the invention.
Same or analogous mark is used to represent same or analogous step or device in the accompanying drawing.
Embodiment
At first, several notions of using among the present invention are made explanations.Among this paper, be divided into following three kinds for terminal use's state:
Available: being meant that other users can successfully set up with this user in time communicates by letter, comprise through call out and through note, no response can not appear calling out, call out be rejected, situation such as the untimely answer of note.
Only note can be used: when terminal use's state during for " only note can be used ", this terminal use advises that other users communicate by letter with its foundation through note rather than through calling out.At this moment, this terminal use possibly be in is inconvenient to the state answering or call, such as, medium just in session, when this terminal use of other customer calls, no response possibly occur calling out, call out situation such as be rejected.
Unavailable: being meant that other users can not successfully set up with this user in time communicates by letter, and comprises through calling out and passing through note.It is to be noted; When being in " unavailable " state; Be not meant that other users can not call out this user or send short messages to this user, and be meant as this user of other customer calls or no response possibly appear calling out when this user sends short messages, call out be rejected, situation such as the untimely answer of note.
Below will combine accompanying drawing that each exemplary embodiment of the present invention is described in detail.
Fig. 1 shows application scenarios sketch map according to an embodiment of the invention.User a, user c, user d are the users under the application server A administration, and they link to each other through network 101.User b, user e are the users under the application server B administration, and they link to each other through network 102.Application server A links to each other through network 103 with application server B.Network 101, network 102 and network 103 can be the PSTN networks, also can be the IMS networks, and they can be same type of networks, also can be inhomogeneous networks.Fig. 1 only is exemplary, just lists out the content relevant with the present invention, and those skilled in the art should be understood that this system also should comprise network element and the circuit that other are essential.
Fig. 2 shows the flow chart that processing according to an embodiment of the invention is called out, and describes its process in detail below in conjunction with Fig. 1.In this embodiment, network 103 is the IMS network, and the initial condition of user b is " available ".At first, shown in step S2a1, application server A calls out its local Client-initiated and monitors, and the calling of promptly user a, user c and user d being initiated is monitored.And in application server B one side, it will be monitored the incident relevant with state exchange that its local user is taken place, and shown in the step S2b1 among Fig. 2, the incident of user b and user e is monitored.Hereinafter will be made explanations to " incident relevant with state exchange ".It is pointed out that step S2a1 and step S2b1 are two mutual independent step, do not have inevitable precedence.And step S2a1 and step S2b1 are all carrying out always, can not stop because of having monitored an incident.
At this moment, incident E21 takes place, i.e. user a calling party b but user b dont answer.
For application server A, because this incident occurs on the user a in its administration, and this calling is that user a initiates, and should call out and successfully set up, so it has monitored incident E21.Subsequently; Application server A is with the step S2a2 shown in the execution graph 2; Send subscribe request to this application server of calling out called end, promptly the application server B under user b sends subscribe request, such as the Subscribe message shown in Fig. 2; The value of the Event field of this Subscribe message is set to availability; Be used for representing the state of application server A, be understood that the sign that should comprise subscriber and subscribed person in this Subscribe message, be i.e. the sign of user a and user b to application server B booking reader b.
For application server B, when incident E21 took place, it had equally also monitored, because this incident can cause the state variation of user b.Because user b is to the calling dont answer of user a, expression user b does not find and should call out that might not carry communication terminal by user b, at this moment, application server B is set to " unavailable " with the state of user b from " available " this moment.Application server B can be according to the design and the actual needs of system; Confirm that which incident is " incident relevant with state exchange " and state transition rules, exemplarily and has without limitation listed some event and state transformation rules relevant with state exchange below:
As user b during to a certain calling no response, the state of user b is set to " unavailable ";
When user b had refused a certain calling, the state of user b was set to " only note can be used ";
When user b when a certain user has initiated to call out or has replied a certain calling, the state of user b is set to " available ";
When user b when a certain user has sent note and current state when " unavailable ", the state of user b is set to " only note can be used ".
It is pointed out that step S2a2 and step S2b2 are two mutual independent step, do not have inevitable precedence.In Fig. 2, step S2b2 takes place prior to step S2a2.
Application server B can inquire about the application server of the state whether booking reader b is arranged behind the state that has upgraded user b, if having, and then to the application server transmit status notification message of this subscription, the last state of informing user b.Among Fig. 2, application server B does not receive the subscribe request of application server A in the state fashion of having upgraded user b, and therefore, after incident E21 took place, application server B only upgraded the state of user b.
Application server B just behind the step S2a2 among Fig. 2, extracts the subscriber and subscribed person sign, the i.e. sign of user a and user b that wherein comprise after the state subscription request that receives from application server A.Subsequently, application server B is with the step S2b3 in the execution graph 2, and whether judges a has the authority of the state of booking reader b.User b can tabulation of predefined, lists the user who allows to subscribe to its state, and according to this tabulation judges a therein whether application server B.
If step S2b3 judges the authority that user a has the state of booking reader b; Then application server B can notify the last state of user b to application server A; Shown in the step S2b4 among Fig. 2; Application server B such as Notify message, has wherein comprised the last state " unavailable " of user b to application server A transmit status notification message.
After application server A had received above-mentioned state notification message, the last state of user b that can in time will wherein comprise was notified the user to this state of subscription, i.e. user a is shown in step S2a3 among Fig. 2.Like this, user a can know in time that user b state at this moment is " unavailable ", can avoid attempting blindly redialing, thereby save because of repeatedly redialing shared Internet resources.
Subsequently, incident E22 takes place: user b has called out user c.
As previously mentioned, application server B is promptly monitoring the incident relevant with state exchange that its local user is taken place always at execution in step S2b1 always.Visible application server B can monitor incident E22 by the exemplary incident relevant with state exchange that enumerate of preceding text.Then, application server B meeting execution in step S2b5, the state of renewal user b, according to the exemplary state transformation rule of enumerating of preceding text, the state of user b is updated to " available " from " unavailable ".
As previously mentioned, application server B can inquire about the application server of the state whether booking reader b is arranged behind the state that has upgraded user b, if having, and then to the application server transmit status notification message of this subscription, the last state of informing user b.At this moment, application server A has subscribed to the state of user b to application server B, so; Application server B can execution in step S2b6, notify the last state of user b to application server A, such as; Send Notify message to application server A, wherein comprised the last state " available " of user b.
After application server A has received above-mentioned state notification message, also can be in time notify the user to this state of subscription with the last state of the user b that wherein comprises, i.e. user a is shown in step S2a4 among Fig. 2.Like this, user a can know in time that the state of user b this moment is " available ", calls out b this moment again or just can successfully set up communication to the user b letter of making a start, and in time obtains the feedback of user b.
Preferably, after step S2a4, when application server A is " available " at the state of learning user b, can initiatively between user a and user b, sets up and call out, for the user provides bigger facility.It is prior art that application server A sets up the process of calling out, and this paper repeats no more at this.
In another preferred embodiment, user b has different state with respect to different users.Describe this embodiment in detail below in conjunction with Fig. 3.
In this embodiment, the user under the application server A administration has different priority.The priority of user a is P1, and the priority of user c is P2, and the priority of user d is P3, and P1＞P2＞P3.User b is " available " with respect to the initial condition of user c and user b with respect to the initial condition of user d with respect to the initial condition of user a, user b.
As shown in Figure 3, application server A is execution in step S3a1, and it is identical with step S2a1 among Fig. 2, and application server A calls out its local Client-initiated and monitors, and the calling of promptly user a, user c and user d being initiated is monitored.And in application server B one side, it will be monitored the incident relevant with state exchange that its local user is taken place, and shown in the step S3b1 among Fig. 3, the incident of user b and user e is monitored.Hereinafter will be made explanations to " incident relevant with state exchange ".It is pointed out that step S3a1 and step S3b1 are two mutual independent step, do not have inevitable precedence.And step S3a1 and step S3b1 are all carrying out always, can not stop because of having monitored an incident.
At this moment, incident E31 takes place, i.e. user a calling party b but user b dont answer.
For application server A, because this incident occurs on the user a in its administration, and this calling is that user a initiates, and should call out and successfully set up, so it has monitored incident E31.Subsequently; Application server A is with the step S3a2 shown in the execution graph 3; Send subscribe request to this application server of calling out called end, promptly the application server B under user b sends subscribe request, such as the Subscribe message shown in Fig. 3; The value of the Event field of this Subscribe message is set to availability; Be used for representing that application server A to the state of application server B booking reader b with respect to user a, is understood that the sign that should comprise subscriber and subscribed person in this Subscribe message, i.e. the sign of user a and user b.
For application server B, when incident E31 took place, it had equally also monitored, because this incident can cause the state variation of user b.Because user b is to the calling dont answer of user a; Expression user b does not find and should call out this moment; Might not carry communication terminal by user b, at this moment, application server B is set to " unavailable " with respect to the state of user a from " available " with user b; Simultaneously, also user b all is set to " unavailable " from " available " with respect to state, the user b of user c with respect to the state of user d.Application server B can be according to the design and the actual needs of system; Confirm that which incident is " incident relevant with state exchange " and state transition rules, exemplarily and has without limitation listed some event and state transformation rules relevant with state exchange below:
When user b has refused from a certain user calling; User b all is set to " only note can be used " with respect to the state of user that priority is equal to or less than this user; Such as, user b has refused the calling of user c, and then application server B is after having monitored this incident; User b all is set to " only note can be used " with respect to the state of user c and user b with respect to the state of user d, and user b is constant with respect to the state of user a;
As user b during to a certain calling no response, user b is set to " unavailable " with respect to every other state of user, such as above-mentioned incident E31;
When user b when a certain user has initiated calling, user b is set to " available " with respect to every other state of user;
When user b has replied from a certain user calling; User b all is set to " available " with respect to the state of user that priority is greater than or equal to this user; Such as; User b has replied the calling from user c, and then user b all will be set to " available " with respect to the state of user a and user b with respect to the state of user c;
When user b has replied from a certain user calling; If being lower than this user's state of user with respect to certain priority, user b is " unavailable "; Then said state is set to " only note can be used ", such as, if user b is " unavailable " with respect to the current state of user c; And user b has replied the calling from user a, and then user b will be set to " only note can be used " with respect to the state of user c;
When user b when a certain user has sent note; If user b is " unavailable " with respect to other certain state of user; Then said state is set to " only note can be used ", such as, if user b is " unavailable " with respect to the current state of user c; And user b has sent note to user a, and then user b will be set to " only note can be used " with respect to the state of user c.
It is pointed out that step S3a2 and step S3b2 are two mutual independent step, do not have inevitable precedence.In Fig. 3, step S3b2 takes place prior to step S3a2.
Application server B can inquire about the application server of the state whether booking reader b is arranged behind the state that has upgraded user b, if having, and then to the application server transmit status notification message of this subscription, the last state of informing user b.Among Fig. 3, application server B does not receive the subscribe request of application server A in the state fashion of having upgraded user b, and therefore, after incident E31 took place, application server B only upgraded the state of user b.
Application server B just behind the step S3a2 among Fig. 3, extracts the subscriber and subscribed person sign, the i.e. sign of user a and user b that wherein comprise after the state subscription request that receives from application server A.Subsequently, application server B is with the step S3b3 in the execution graph 3, and whether judges a has the authority of the state of booking reader b.User b can tabulation of predefined, lists the user who allows to subscribe to its state, and according to this tabulation judges a therein whether application server B.
If step S3b3 judges the authority that user a has the state of booking reader b; Then application server B can notify user b to application server A with respect to the last state of user a; Shown in the step S3b4 among Fig. 3; Application server B such as Notify message, has wherein comprised the last state " unavailable " of user b with respect to user a to application server A transmit status notification message.
After application server A had received above-mentioned state notification message, the last state of user b that can in time will wherein comprise was notified the user to this state of subscription, i.e. user a is shown in step S3a3 among Fig. 3.Like this, user a can know in time that user b state at this moment is " unavailable ", can avoid attempting blindly redialing, thereby save because of repeatedly redialing shared Internet resources.
Subsequently, incident E32 takes place: user b has called out user c.
As previously mentioned, application server B is promptly monitoring the incident relevant with state exchange that its local user is taken place always at execution in step S3b1 always.Visible application server B can monitor incident E32 by the exemplary incident relevant with state exchange that enumerate of preceding text.Then; Application server B meeting execution in step S3b5; Upgrade user b with respect to the state of user a, user b with respect to the state of user c and user b state with respect to user d; According to the exemplary state transformation rule of enumerating of preceding text, user b all from " unavailable " is updated to " available " with respect to the state of user c and user b with respect to the state of user d with respect to the state of user a, user b.
As previously mentioned, application server B can inquire about the application server of the state whether booking reader b is arranged behind the state that has upgraded user b, if having, and then to the application server transmit status notification message of this subscription, the last state of informing user b.At this moment, application server A has subscribed to the state of user b to application server B, particularly; User a under the application server A has subscribed to the state of user b, so, application server B meeting execution in step S3b6; Notify user b last state to application server A with respect to user a; Such as, send Notify message to application server A, wherein comprised the last state " available " of user b with respect to user a.
After application server A has received above-mentioned state notification message, also can be in time notify the user to this state of subscription with the last state of the user b that wherein comprises, i.e. user a is shown in step S3a4 among Fig. 3.Like this, user a can know in time that this moment, user b was " available " with respect to its state, calls out b this moment again or just can successfully set up communication to the user b letter of making a start, and in time obtains the feedback of user b.
Preferably, after step S3a4, application server A can initiatively set up between user a and user b and call out, for the user provides bigger facility when learning that the state of user b with respect to user a is " available ".It is prior art that application server A sets up the process of calling out, and this paper repeats no more at this.
Fig. 4 shows the structured flowchart of in application server A, handling the device of calling out according to an embodiment of the invention.This device 400 comprises first monitoring device 401, subscribes to device 402, first receiving device 403, first dispensing device 404 and call setup device 405.Specify the course of work of this device below in conjunction with application scenarios shown in Figure 1.
At first, first monitoring device 401 is called out its local Client-initiated and is monitored, and the calling of promptly user a, user c and user d being initiated is monitored.It is pointed out that first monitoring device 401 working always, can not stop because of having monitored an incident.
At this moment, user a calling party b but user b dont answer.
For first monitoring device 401, because this incident occurs on the user a in the application server A administration, and this calling is that user a initiates, and should call out and successfully set up, so it monitors this incident.Subsequently; Subscribe to device 402 and will send subscribe request to this application server of calling out called end, promptly the application server B under user b sends subscribe request, such as Subscribe message; The value of the Event field of this Subscribe message is set to availability; Be used for representing the state of application server A, be understood that the sign that should comprise subscriber and subscribed person in this Subscribe message, be i.e. the sign of user a and user b to application server B booking reader b.
Subsequently, after first receiving device 403 has been received the state notification message from application server B,, wherein comprised the last state " unavailable " of user b such as Notify message.The last state of the user b that first dispensing device 404 can in time will wherein comprise is notified the user to this state of subscription, i.e. user a.Like this, user a can know in time that user b state at this moment is " unavailable ", can avoid attempting blindly redialing, thereby save because of repeatedly redialing shared Internet resources.
Subsequently, user b has called out user c.
After first receiving device 403 can be received the state notification message from application server B,, wherein comprised the last state " available " of user b such as Notify message.First dispensing device 404 also can in time be notified the user to this state of subscription, i.e. user a with the last state of the user b that wherein comprises.Like this, user a can know in time that the state of user b this moment is " available ", calls out b this moment again or just can successfully set up communication to the user b letter of making a start, and in time obtains the feedback of user b.
Preferably, when call setup device 405 is " available " at the state of learning user b, can initiatively between user a and user b, sets up and call out, for the user provides bigger facility.It is prior art that call setup device 405 is set up the process of calling out, and this paper repeats no more at this.
Preferably, user b has different state with respect to different users, correspondingly, subscribes to device 402 and is further used for the state of booking reader b with respect to user a to the state subscription request that application server B sends; The state notification message that first receiving device 403 receives further comprises the state of user b with respect to user a; First dispensing device 404 comprises the state of user b with respect to user a in the state notification message that user a sends; Call setup device 405 is further used for during for " available ", between user a and user b, set up and calling out with respect to the state of user a as user b.
Fig. 5 shows the structured flowchart of in application server B, handling the device of calling out according to an embodiment of the invention.This device 500 comprises second monitoring device 501, state updating device 502, state notifying device 503, second receiving system 504 and judgment means 505.Specify the course of work of this device below in conjunction with application scenarios shown in Figure 1.
At first, the incident relevant with state exchange that the local user of second monitoring device, 501 application server B is taken place monitored, and promptly the incident of user b and user e monitored.Hereinafter will be made explanations to " incident relevant with state exchange ".It is pointed out that second monitoring device 501 working always, can not stop because of having monitored an incident.
At this moment, user a calling party b but user b dont answer.
Because this incident can cause the state variation of user b, second monitoring device 501 has monitored this incident.Because user b is to the calling dont answer of user a, expression user b does not find and should call out that might not carry communication terminal by user b, at this moment, state updating device 502 is set to " unavailable " with the state of user b from " available " this moment.Second monitoring device 501 can be according to the design and the actual needs of system with state updating device 502; Confirm that which incident is " incident relevant with state exchange " and state transition rules, exemplarily and has without limitation listed some event and state transformation rules relevant with state exchange below:
As user b during to a certain calling no response, the state of state updating device 502 user b is set to " unavailable ";
When user b had refused a certain calling, the state of state updating device 502 user b was set to " only note can be used ";
When user b when a certain user has initiated to call out or has replied a certain calling, the state of state updating device 502 user b is set to " available ";
When user b when a certain user has sent note and current state when " unavailable ", the state of state updating device 502 user b is set to " only note can be used ".
If judgment means 505 is judged the authority that user a has the state of booking reader b; Then state notifying device 503 can be notified the last state of user b to application server A; State notifying device 503 is to application server A transmit status notification message; Such as Notify message, wherein comprised the last state " unavailable " of user b.
Subsequently, user b has called out user c.
As previously mentioned, second monitoring device 501 is being worked always, is promptly monitoring the incident relevant with state exchange that its local user is taken place always.Can monitor this incident by visible second monitoring device 501 of the exemplary incident relevant that enumerate of preceding text with state exchange.Then, state updating device 502 can upgrade the state of user b, and according to the exemplary state transformation rule of enumerating of preceding text, the state of user b is updated to " available " from " unavailable ".
As previously mentioned; State updating device 502 is behind the state that has upgraded user b, and state notifying device 503 can be inquired about the application server of the state whether booking reader b is arranged, if having; Then to the application server transmit status notification message of this subscription, the last state of informing user b.At this moment, application server A has subscribed to the state of user b to application server B, so; State notifying device 503 is notified the last state of user b to application server A; Such as, send Notify message to application server A, wherein comprised the last state " available " of user b.
Preferably, user b has different state with respect to different users, such as, the priority of user a is P1, and the priority of user c is P2, and the priority of user d is P3, and P1＞P2＞P3.Correspondingly, state updating device 502 is further used for:
When user b has refused from a certain user calling; User b all is set to " only note can be used " with respect to the state of user that priority is equal to or less than this user; Such as, user b has refused the calling of user c, and then second monitoring device 501 is after having monitored this incident; State updating device 502 all is set to " only note can use " with respect to the state of user c and user b with respect to the state of user d with user b, and user b is constant with respect to the state of user a;
As user b during to a certain calling no response, user b is set to " unavailable " with respect to every other state of user;
When user b when a certain user has initiated calling, user b is set to " available " with respect to every other state of user;
When user b has replied from a certain user calling; User b all is set to " available " with respect to the state of user that priority is greater than or equal to this user; Such as; User b has replied the calling from user c, and then user b all will be set to " available " with respect to the state of user a and user b with respect to the state of user c;
When user b has replied from a certain user calling; If being lower than this user's state of user with respect to certain priority, user b is " unavailable "; Then said state is set to " only note can be used ", such as, if user b is " unavailable " with respect to the current state of user c; And user b has replied the calling from user a, and then user b will be set to " only note can be used " with respect to the state of user c;
When user b when a certain user has sent note; If user b is " unavailable " with respect to other certain state of user; Then said state is set to " only note can be used ", such as, if user b is " unavailable " with respect to the current state of user c; And user b has sent note to user a, and then user b will be set to " only note can be used " with respect to the state of user c.
To those skilled in the art, obviously the invention is not restricted to the details of above-mentioned example embodiment, and under the situation that does not deviate from spirit of the present invention or essential characteristic, can realize the present invention with other concrete form.Therefore; No matter from which point; All should regard embodiment as exemplary; And be nonrestrictive, scope of the present invention is limited accompanying claims rather than above-mentioned explanation, therefore is intended to the implication of the equivalents that drops on claim and all changes in the scope are included in the present invention.Should any Reference numeral in the claim be regarded as limit related claim.In addition, obviously other unit or step do not got rid of in " comprising " speech, and odd number is not got rid of plural number.A plurality of unit of stating in system's claim or device also can be realized through software or hardware by a unit or device.The first, the second word such as grade is used for representing title, and does not represent any specific order.
Claims (16)
1. method that in application server, is used to handle calling said method comprising the steps of:
A1. the local Client-initiated of said application server is called out and monitored;
The calling of a2. the not success that monitors being set up, to the application server transmission subscribe request of said calling called end, said subscribe request is used to subscribe to said called state;
Said method also comprises:
A3. receive state notification message, comprising second state of user from second application server;
A4. to user's transmit status notification message of subscribing to said second User Status, comprising said second state of user.
2. method according to claim 1 is characterized in that, and is after the said step a4, further comprising the steps of:
If a5. said second user's upstate is available, then said application server is said second user and subscribe to set up between the user of said second User Status and call out.
3. method according to claim 1 is characterized in that,
Said step a2 further comprises: said subscribe request is used to subscribe to the state of said called caller with respect to said calling;
Said state notification message among the said step a3 further comprises the upstate of second user with respect to first user;
Said step a4 further comprises: to said first user's transmit status notification message, comprising said second user with respect to first state of user.
4. method according to claim 3; It is characterized in that; Said step a5 further comprises: if said second user is available with respect to first state of user, then said application server is set up calling between said second user and said first user.
5. method that in application server, is used to handle calling said method comprising the steps of:
B1. the incident relevant with state exchange that the local user of said application server is taken place monitored;
B2. according to the incident that monitors, the more state of user of the said incident of kainogenesis;
B3. to the application server transmit status notification message of subscribing to said User Status, wherein comprised said user's last state;
6. method according to claim 5 is characterized in that, said method is further comprising the steps of:
B4. receive state subscription request, wherein comprised subscriber's sign and subscribed person sign from first application server;
B5. judge whether said subscriber has the authority of subscription;
If b6. said subscriber has the authority of subscription,, wherein comprised said subscribed person's last state to the first application server transmit status notification message.
7. method according to claim 5 is characterized in that, said b2 further comprises:
As said user during to a certain calling no response, said state of user is set to " unavailable ";
When said user had refused a certain calling, said state of user was set to " only note can be used ";
When said user when a certain user has initiated to call out or has replied a certain calling, said state of user is set to " available ";
When said user when a certain user has sent note and current state when " unavailable ", said state of user is set to " only note can be used ".
8. method according to claim 5 is characterized in that, said b2 further comprises:
When said user has refused from first user calling, said user all is set to " only note can be used " with respect to the state of user that priority is equal to or less than said first user;
As said user during to a certain calling no response, said user is set to " unavailable " with respect to every other state of user;
When said user when a certain user has initiated calling, said user is set to " available " with respect to every other state of user;
When said user answer during from first user calling, said user all is set to " available " with respect to the state of user that priority is greater than or equal to said first user;
When said user answer during from first user calling, be " unavailable " if said user is lower than said first user's state of user with respect to certain priority, then said state is set to " only note can be used ";
When said user when first user has sent note, if said user is " unavailable " with respect to other certain state of user, then said state is set to " only note can be used ".
9. device that in application server, is used to handle calling, said device comprises:
First monitoring device is used for the local Client-initiated of said application server called out and monitors;
Subscribe to device, be used for the calling to the not success foundation that monitors, to the application server transmission subscribe request of said calling called end, said subscribe request is used to subscribe to said called state;
First receiving device is used to receive the state notification message from second application server, comprising second state of user;
First dispensing device is used for to user's transmit status notification message of subscribing to said second User Status, comprising said second state of user.
10. device according to claim 9 is characterized in that, said device also comprises:
The call setup device, but be used for when said second user's upstate for the time spent at said application server said second user with subscribe to set up between the user of said second User Status and call out.
11. method according to claim 9 is characterized in that,
The subscribe request that said subscription device sends is further used for subscribing to the state of said called caller with respect to said calling;
The state notification message that said first receiving device receives further comprises the upstate of second user with respect to first user;
Said first dispensing device is further used for to said first user's transmit status notification message, comprising said second user with respect to first state of user.
12. method according to claim 11 is characterized in that, but said call setup device is further used for said second user and said first user between setting up calling with respect to first state of user for the time spent as said second user.
13. a device that in application server, is used to handle calling, said device comprises:
Second monitoring device is used for the incident relevant with state exchange that the local user of said application server is taken place monitored;
The state updating device is used for taking place according to the event update that monitors the state of user of said incident;
The state notifying device is used for wherein having comprised said user's last state to the application server transmit status notification message of subscribing to said User Status.
14. method according to claim 13 is characterized in that, said device also comprises:
Second receiving system is used to receive the state subscription request from first application server, has wherein comprised subscriber's sign and subscribed person sign;
Judgment means is used to judge whether said subscriber has the authority of subscription;
Said state notifying device also is used for having when subscribing to authority to the first application server transmit status notification message as said subscriber, has wherein comprised said subscribed person's last state.
15. method according to claim 13 is characterized in that, said state updating device is further used for:
As said user during to a certain calling no response, said state of user is set to " unavailable ";
When said user had refused a certain calling, said state of user was set to " only note can be used ";
When said user when a certain user has initiated to call out or has replied a certain calling, said state of user is set to " available ";
When said user when a certain user has sent note and current state when " unavailable ", said state of user is set to " only note can be used ".
16. method according to claim 13 is characterized in that, said state updating device is further used for:
When said user has refused from first user calling, said user all is set to " only note can be used " with respect to the state of user that priority is equal to or less than said first user;
As said user during to a certain calling no response, said user is set to " unavailable " with respect to every other state of user;
When said user when a certain user has initiated calling, said user is set to " available " with respect to every other state of user;
When said user answer during from first user calling, said user all is set to " available " with respect to the state of user that priority is greater than or equal to said first user;
When said user answer during from first user calling, be " unavailable " if said user is lower than said first user's state of user with respect to certain priority, then said state is set to " only note can be used ";
When said user when first user has sent note, if said user is " unavailable " with respect to other certain state of user, then said state is set to " only note can be used ".
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110115133XA CN102769835A (en) | 2011-05-05 | 2011-05-05 | Method and device for call handling |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110115133XA CN102769835A (en) | 2011-05-05 | 2011-05-05 | Method and device for call handling |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102769835A true CN102769835A (en) | 2012-11-07 |
Family
ID=47097060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110115133XA Pending CN102769835A (en) | 2011-05-05 | 2011-05-05 | Method and device for call handling |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102769835A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105207879A (en) * | 2014-06-03 | 2015-12-30 | 联想(北京)有限公司 | Communication method and electronic devices |
| CN105282730A (en) * | 2014-05-26 | 2016-01-27 | 中国电信股份有限公司 | Method and system for acquiring terminal communication state in IMS (IP multimedia subsystem) and application server |
| CN106331386A (en) * | 2015-07-02 | 2017-01-11 | 华为技术有限公司 | Terminal state synchronization method, related device and system |
| CN106412855A (en) * | 2016-06-30 | 2017-02-15 | 北京小米移动软件有限公司 | Information prompting and transmitting methods and devices |
| CN115665238A (en) * | 2022-09-21 | 2023-01-31 | 深圳市米糠云科技有限公司 | Method and system for processing data publishing and subscribing of call center |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050286495A1 (en) * | 2004-06-29 | 2005-12-29 | Interdigital Technology Corporation | System and method for call routing and paging across different types of networks |
| CN1905472A (en) * | 2005-07-27 | 2007-01-31 | 华为技术有限公司 | Method for implementing IMS network reliability |
| CN101217598A (en) * | 2007-01-04 | 2008-07-09 | 中国移动通信集团公司 | A call-back method and system in busy circumstances |
-
2011
- 2011-05-05 CN CN201110115133XA patent/CN102769835A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050286495A1 (en) * | 2004-06-29 | 2005-12-29 | Interdigital Technology Corporation | System and method for call routing and paging across different types of networks |
| CN1905472A (en) * | 2005-07-27 | 2007-01-31 | 华为技术有限公司 | Method for implementing IMS network reliability |
| CN101217598A (en) * | 2007-01-04 | 2008-07-09 | 中国移动通信集团公司 | A call-back method and system in busy circumstances |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105282730A (en) * | 2014-05-26 | 2016-01-27 | 中国电信股份有限公司 | Method and system for acquiring terminal communication state in IMS (IP multimedia subsystem) and application server |
| CN105282730B (en) * | 2014-05-26 | 2019-04-12 | 中国电信股份有限公司 | Terminal communications status acquisition methods and system and application server in IMS network |
| CN105207879A (en) * | 2014-06-03 | 2015-12-30 | 联想(北京)有限公司 | Communication method and electronic devices |
| CN106331386A (en) * | 2015-07-02 | 2017-01-11 | 华为技术有限公司 | Terminal state synchronization method, related device and system |
| CN106331386B (en) * | 2015-07-02 | 2019-10-15 | 华为技术有限公司 | SOT state of termination synchronous method, relevant apparatus and system |
| CN106412855A (en) * | 2016-06-30 | 2017-02-15 | 北京小米移动软件有限公司 | Information prompting and transmitting methods and devices |
| CN115665238A (en) * | 2022-09-21 | 2023-01-31 | 深圳市米糠云科技有限公司 | Method and system for processing data publishing and subscribing of call center |
| CN115665238B (en) * | 2022-09-21 | 2023-09-08 | 深圳市米糠云科技有限公司 | Method and system for processing call center data publish and subscribe |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101515949B (en) | Methods and systems for facilitating transfer of sessions between user devices | |
| CN101155389B (en) | Method and device for processing call collision | |
| WO2020019526A1 (en) | Call management and control method and system, and computer apparatus and storage medium thereof | |
| JP2004533760A (en) | Method and system for using usage state information of terminal device | |
| US20040141606A1 (en) | Network-originated group call | |
| CN102769835A (en) | Method and device for call handling | |
| CN102484668B (en) | Meeting scheduler sending reminders | |
| JP6169568B2 (en) | System and method for passive communication service | |
| CN101710909A (en) | Method and system for displaying card information of calling user | |
| CN102546554A (en) | IP (Internet Protocol) multimedia subsystem and method thereof for recovering user subscription relationship | |
| CN102611805A (en) | Communication information notifying method, information reporting method, server and communication terminals | |
| CN101765076A (en) | Method, device and system for partially locking termination function | |
| CN101394294A (en) | Access method, system and apparatus for network multimedia meeting | |
| CN102111728B (en) | Network connection management module and method of mobile terminal | |
| CN100481770C (en) | Service system, information control apparatus, and information control method | |
| CN103391303B (en) | Service fault noticing method and server using same | |
| CN102739877B (en) | The method that information of terminal user is shared, the method for calling and server | |
| CN104955136A (en) | Terminal management apparatus, terminal, communication system, terminal management method, and program | |
| CN101426183B (en) | Group communication system and method triggered by mobile telephone on the basis of network group | |
| CN103200340B (en) | Realize method, call management system and the terminal of call management | |
| CN101374282A (en) | Method and apparatus for displaying different states of wireless one-key-through user in different groups | |
| CN102771107A (en) | Call attempt notification | |
| CN101361332A (en) | Mobile e-mail server, system and method for e-mail affair processing | |
| CN115134422A (en) | Service processing method, video network terminal, master control device, electronic device and medium | |
| KR20060130799A (en) | System and method for providing of user status information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20121107 |
|
| RJ01 | Rejection of invention patent application after publication |