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 the present invention's part embodiment, 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 obtains under the creative work prerequisite.
Call out in the process of terminal called at calling terminal, terminal called also is in the process of calling out calling terminal, and this phenomenon is referred to as Call Collision in embodiments of the present invention.The method flow diagram of the processing Call Collision that Fig. 1 provides for the embodiment of the invention, as shown in the figure, the method for processing Call Collision among this embodiment comprises:
S100, in call establishment, business control device obtains the calling and called sign of current calling;
Wherein, business control device is to carry out Business Processing and call out the equipment of control in calling procedure, such as, (the service control point of the service control point in the intelligent network, SCP), professional for the treatment of Call Collision in embodiments of the present invention.The Call Collision business is for the business that solves Call Collision.
(the mobile switching center of mobile switching centre, MSC) receive the calling that calling terminal initiates after, Call Collision is professional if definite caller or terminal called have been contracted, then send the message that is used for triggering the Call Collision business to business control device, such as initial test point (initial domain part, IDP) message, business control device are obtained the calling and called sign of current calling from this message.
Wherein, MSC can determine whether that signatory Call Collision is professional according to caller or called CAMEL-Subscription-Information, this CAMEL-Subscription-Information can be that the user of mobile network enhancing logic uses CAMEL-Subscription-Information (customizedapplications for mobile network enhanced logic (CAMEL) subscriptioninformation, C SI).
Optionally, it is professional that MSC also can give tacit consent to all users Call Collision of having contracted, receiving call out after according to the address of pre-configured business control device, send the message that triggers the Call Collision business to business control device.
S102 according to the call context that this calling and called sign is searched buffer memory, determines whether to exist the context with the afoul calling of current calling; If have, then carry out S104; If no, then carry out S106;
Wherein, business control device is cached with the context that is in the calling in the call establishment, comprises the calling and called sign of this calling in the context of each calling.The call context of buffer memory can determine whether to exist conflict to call out to business control device by searching.Certainly, business control device can in the local cache call context, also can be buffered in call context in the outside memory device.
Concrete, business control device can not distinguished calling and called (the only sign of buffer memory calling and called itself) when the call context of buffer memory, also can distinguish calling and called (namely except the sign of buffer memory calling and called itself, also mark this sign and belong to caller or called).
If do not distinguish calling and called in the call context of buffer memory, be specially the call context of the calling and called sign that includes current calling with the context of the afoul calling of current calling.When business control device finds out the call context of the calling and called sign that comprises current calling in the call context of buffer memory, determine the calling of existence and current Call Collision.
Generally, according to whether there being the call context that comprises this calling and called sign can determine whether to exist Call Collision in the call context of buffer memory.Under some particular demands, when sending the message that is used for triggering Call Collision business such as the second time in same calling to business control device, whether the caller that can further determine the record in the call context is the called of current calling, whether called be the caller of current calling, call out as conflict in order to avoid should call out self because should callings the first time when triggering the Call Collision business buffer memory context of this calling.Concrete, if the differentiation calling and called are arranged in the call context of buffer memory, then the context with the afoul calling of current calling is specially: the caller of record is the called of current calling, and the called of record is the call context of the caller of current calling.Business control device has found out call context in the call context of buffer memory, it is recorded as the called identification that is designated current calling of caller, and this call context is recorded as called when being designated the calling identification of current calling, determines to exist the calling with current Call Collision.
S104, instruct MS C discharge current calling.
Concrete, business control device sends the instruction that discharges current calling to MSC, and such as call release (release call, RC) signaling, MSC discharges current calling according to this instruction.
S106, the context of the current calling of buffer memory, and the instruct MS C current calling that continues when finding that when successfully continuing current calling or in handshaking procedure current calling has been released, are deleted the context of current calling; Wherein, the context of the current calling of buffer memory comprises the calling and called sign of current calling.
Concrete, in the situation that does not exist conflict to call out, business control device sends the instruction of current calling that continues to MSC, as (continue) message that continues, the instruct MS C current calling that continues.Wherein, business control device can be determined the current calling of successful connection to receive the called party answer message that MSC reports, and determines to find that to receive the release event that MSC reports current calling is released in handshaking procedure.
The context of buffer memory can be used as the foundation of judging Call Collision among the step S106 in subsequent treatment, such as, before the context of the current calling of deletion, receive the called calling of initiating to the caller of current calling of current calling, at this moment, business control device can determine to exist according to the call context of buffer memory the calling of conflict.
In above-described embodiment, owing to when the current calling of discovery has been released when the current calling of successful connection or in handshaking procedure the context of current calling is deleted, thereby the context of guaranteeing the business control device buffer memory is the context that is in the calling in the call establishment.Therefore, when receiving calling, business control device can determine whether to exist Call Collision according to the call context of buffer memory, when having Call Collision, current calling is discharged, thereby guaranteed to a certain extent the successful connection with another calling of current Call Collision, improve percept of call completed, avoided the waste of Internet resources.
Because in call establishment, signaling transmits and has time-delay, therefore, under some special screnes, also needs to be further processed.Such as, after abovementioned steps S106, MSC receives the current calling indication that continues, and the call proceeding that terminal A is initiated is during to terminal B, the calling that terminal B initiates to terminal A does not also have enough time to discharge (one fixed response time being arranged from being discharged into terminal recovery idle condition), at this moment, the situation of busy can occur, MSC can report the busy event to business control device.Therefore, in order to solve this special circumstances, service processing equipment can also further be processed on basis embodiment illustrated in fig. 1.Specifically can adopt following two kinds of processing modes:
Mode one: in the process of current calling that continues, if receive the busy event, the business control device wait of delaying time sends the instruction of the current calling that again continues to MSC when reaching default delay duration.Wherein, default delay duration can rule of thumb be worth and presets, such as 10 seconds.
Mode two: in the process of current calling that continues, if receive the busy event, business control device detects the called state of current calling in real time, when detecting described called recovery idle condition, sends the instruction of the current calling that again continues to MSC.
By above-mentioned processing, some unsuccessful problems that in particular cases continue have been solved, so that percept of call completed has obtained further improving.And above-mentioned dual mode respectively has advantage, and the processing of mode one need not with miscellaneous equipment mutual, directly waits for get final product the saving Internet resources; Mode two can directly be known called state, and accuracy is high.
In addition, in all the contracted situation of Call Collision business of calling and called both sides, also following situation may appear: after service processing equipment instruct MS C continues current calling, MSC according to the CAMEL-Subscription-Information of terminal called (as, T-CSI) again send to this service processing equipment and be used for triggering the professional message of conflict (such as, IDP message).At this moment, service processing equipment can further include following processing on the basis of Fig. 1 or above-mentioned other embodiment: in the current calling procedure that continuing, if receive MSC at test point (detection point, DP) 12 initiate Initial Detection Point IDP message the time, business control device is searched the call context of buffer memory, determine not exist conflict to call out and the context of current calling buffer memory, the instruct MS C current calling that continues to continue.Present embodiment also is the processing in particular cases, and purpose is further to improve percept of call completed, with conserve network resources.
The scheme of the embodiment of the invention can be applied in intelligent network or other network, for the ease of understanding, the embodiment of the invention all message in the intelligent network describes as example, and is in the time of in being applied to other network, replaceable for having the message of similar functions in other network.
If realize the scheme that the embodiment of the invention provides with intelligent network, need to be professional for the signatory Call Collision of user in attaching position register (home location register, HLR).Namely before step S100 shown in Figure 1, also comprise and carry out in advance the CAMEL-Subscription-Information setting, the CAMEL-Subscription-Information setting up procedure is as follows: HLR makes and preserves user's CAMEL-Subscription-Information, comprise Originating CAMEL Subscription Information (originating CAMELsubscription information, O-C SI) and Terminating CAMEL Subscription Information (terminated CAMELsubscription information, T-CSI).Service key among O-CSI and the T-CSI is the service key of Call Collision business, and the address among O-CSI and the T-CSI is the address of the business control device of processing Call Collision business.If the contracted user does caller, MSC sends the message that is used for triggering the Call Collision business according to this user's O-CSI to business control device, if the contracted user does called, MSC sends the message that is used for triggering the Call Collision business according to this user's T-CSI to business control device.The calling and called sign that business control device obtains current calling among the abovementioned steps S100 can specifically comprise: business control device receives the message that is used for triggering the Call Collision business that mobile switching centre sends according to caller or called CAMEL-Subscription-Information, and obtains the calling and called sign of current calling from this message.
The below is further detailed the embodiment of the invention with concrete application scenarios, and following scene is all take intelligent network as example, and therefore, business control device is the SCP in the intelligent network in following examples.
Scene 1: terminal A contracts has Call Collision professional, and the signatory Call Collision of terminal B is professional, and wherein, terminal A is called calling a to the calling of terminal B, and terminal B is called calling b to the calling of terminal A, supposes that calling out a occurs prior to calling out b.
Fig. 2 is the Call Collision process flow figure under the scene 1, and as shown in the figure, the Call Collision processing method comprises in the present embodiment:
The calling a to terminal B that the visited place moving exchanging center MSC a receiving terminal A of a201: terminal A initiates;
A202:MSCa sends the IDP message that is used for triggering the Call Collision business according to the O-CSI of terminal A to SCP;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out a.The CAMEL-Subscription-Information O-CSI of terminal A can obtain from visitor location register (visitor location register, VLR).Wherein, VLR can close with MSC and be located in the physical entity, also can be two independently physical entities.The embodiment of the invention can be closed with MSC with VLR and is made as example and describe.
A203:SCP obtains the calling and called sign of calling out a, with the call context that the calling and called sign of obtaining is searched buffer memory, determines not exist the calling that conflicts with calling a;
Wherein, the calling and called sign that comprises respective call in each call context, by searching the call context of buffer memory, can determine whether to comprise the call context of the calling and called sign of calling out a, thereby determine whether to exist the calling that conflicts with calling a, owing to call out a prior to calling out the b generation, therefore, search less than the call context that comprises the calling and called sign of calling out a in the present embodiment.
A204: buffer memory is called out the context of a, and wherein, the context of the calling a of buffer memory comprises the calling and called sign of calling out a;
Concrete, in the buffer memory call context, can the calling and called sign not distinguished, directly storaging mark A and sign B.
A205: send continue message, instruct MS C replay call a to MSC;
Optionally, when sending continue message, can further send request report Basic Call State Model BCSM event (request report (Basic Call State Mode to MSC, BCSM) event, RRBE) message, this RRBE message is used to indicate MSCa monitoring called party answer, busy, nonreply, the event such as unreachable, and this processing can realize with reference to prior art.
Need to prove that step a204 and a205 do not have the sequencing restriction when carrying out.
A206:MSCa sends initial address message (Initial AddressMessage, IAM) to the visited place MSCb of terminal B;
To call out before a is routed to terminal B at MSCa, namely before step a206, if terminal B has initiated calling b, SCP is to calling out the processing of b, and is specific as follows:
The calling b to terminal A that the visited place moving exchanging center MSC b receiving terminal B of b201: terminal B initiates;
B202:MSCb sends the IDP message that is used for triggering the Call Collision business according to the T-CSI of called (terminal A) to SCP;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out b.
B203:SCP obtains the calling and called sign of calling b, with the call context that the calling and called sign of obtaining is searched buffer memory, determines to exist the calling that conflicts with calling b;
Occur prior to calling out b owing to calling out a, buffer memory comprises the call context that terminal A identifies and terminal B identifies in a204, therefore, can find in this step the call context that comprises the calling and called sign of calling out b, thereby determine to exist the calling that conflicts.
B204: send RC message, instruct MS Cb call release b to MSCb;
The resource of b205:MSCb call release b makes the B terminal return to idle condition.
In the present embodiment, the processing of calling out b was finished before step a206, therefore, when MSC receives IAM message, called out b and be released, can be by successful connection so call out a, concrete process is as follows:
Step a207:MSCb call terminal B and to the full message in MSCa return address (addresscomplete message, ACM);
A208: after terminal called was replied, MSCb sent address response message (addressanswer message, ANM) to MSCa;
A209:MSCa sends Basic Call State Model BCSM reporting events (event report basiccall state model, ERB) message to SCP and reports the event of replying;
A210:SCP sends Continue message instruct MS Ca call establishment a to MSCa;
The context of the calling a of a211:SCP deletion buffer memory.
Need to prove that step a210 and a211 do not have the sequencing restriction when carrying out.
A212: call out a and successfully set up, terminal A and terminal B begin conversation.
Because transmitting, signaling has time-delay, therefore, although might exist and call out b and occur in MSCa and will call out a and be routed to before the terminal B, but the situation that before step a206, does not have enough time to discharge, for this situation, process as shown in Figure 3, Fig. 3 is the flow chart of another embodiment of the Call Collision processing method under the scene 1, and the Call Collision processing method comprises in the present embodiment:
The calling a to terminal B that the visited place moving exchanging center MSC a receiving terminal A of a301: terminal A initiates;
A302:MSCa sends the IDP message that is used for triggering the Call Collision business according to the O-CSI of terminal A to SCP;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out a.
A303:SCP obtains the calling and called sign of calling out a, with the call context that the calling and called sign of obtaining is searched buffer memory, determines not exist the calling that conflicts with calling a;
Wherein, the calling and called sign that comprises respective call in each call context, by searching the call context of buffer memory, can determine whether to comprise the call context of the calling and called sign of calling out a, thereby determine whether to exist the calling that conflicts with calling a, owing to call out a prior to calling out the b generation, therefore, search less than the call context that comprises the calling and called sign of calling out a in the present embodiment.
A304: buffer memory is called out the context of a, and wherein, the context of the calling a of buffer memory comprises the calling and called sign of calling out a;
Concrete, in the buffer memory call context, can not distinguish calling and called.
A305: send continue message, instruct MS C replay call a to MSC;
Optionally, when sending continue message, can further send request report Basic Call State Model BCSM event (request report BCSM (basic call state mode) event to MSC, RRBE) message, this RRBE message is used to indicate MSCa monitoring called party answer, busy, nonreply, the event such as unreachable, and this processing can realize with reference to prior art.
Need to prove that step a304 and a305 do not have the sequencing restriction when carrying out.
A306:MSCa sends initial address message (initial addressmessage, IAM) to the visited place MSCb of terminal B;
To call out before a is routed to terminal B at MSCa, namely before step a306, if terminal B has initiated calling b, SCP processes calling out b, step b301-b305 is for calling out the processing procedure of b, and wherein the processing procedure of step b301-b305 can be with reference to step b201-b205 shown in Figure 2.
Just in the present embodiment, still uncompleted before step a306 to the processing of calling out b, therefore, when MSC receives IAM message, call out b and be not released, can't successful connection so call out a.At this moment, the subsequent treatment of calling out a is comprised:
A307:MSCb returns the REL message informing to MSCa and continues unsuccessfully, and carries cause value: Called Busy;
A308:MSCa sends ERB message to SCP, reports the busy event;
The a309:SCP wait of delaying time;
Time-delay herein is that terminal B returns to idle condition for the finishing dealing with of Waiting for Call b, and delay duration can rule of thumb be worth and sets in advance.For accuracy is higher, this step can also adopt another kind of alternative, and namely the state of the real-time sense terminals B of SCP when detecting terminal B recovery idle condition, sends Reconnect message to MSC.
A310: send Reconnect message to MSC when time-delay reaches default delay duration, instruct MS C is replay call a again;
A311:MSCa sends IAM to MSCb.
After this processing of a312-a317 can with reference to the a207-a212 among the figure 2, repeat no more here.
Scene 2: terminal A and terminal B are all signatory to have Call Collision professional, and belongs to identical SCP.Wherein, terminal A is called calling a to the calling of terminal B, and terminal B is called calling b to the calling of terminal A, supposes that calling out a occurs prior to calling out b.
Fig. 4 is the Call Collision process flow figure under the scene 2, and as shown in the figure, the Call Collision processing method comprises among this embodiment:
The calling a to terminal B that the visited place moving exchanging center MSC a receiving terminal A of a401: terminal A initiates;
A402:MSCa sends the IDP message that is used for triggering the Call Collision business according to the O-CSI of terminal A to SCP;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out a.
A403:SCP obtains the calling and called sign of calling out a, with the call context that the calling and called sign of obtaining is searched buffer memory, determines not exist the calling that conflicts with calling a;
Wherein, the calling and called sign that comprises respective call in each call context, by searching the call context of buffer memory, can determine whether to comprise the call context of the calling and called sign of calling out a, thereby determine whether to exist the calling that conflicts with calling a, owing to call out a prior to calling out the b generation, therefore, search less than the call context that comprises the calling and called sign of calling out a in the present embodiment.
A404: buffer memory is called out the context of a, and wherein, the context of the calling a of buffer memory comprises the calling and called sign of calling out a;
In the present embodiment, in the buffer memory call context, need to be distinguished calling and called, as adopting the form of " calling identification=A, called identification=B ".
A405: send continue message, instruct MS C replay call a to MSC;
Optionally, when sending continue message, can further send request report Basic Call State Model BCSM event (request report BCSM (basic call state mode) event to MSC, RRBE) message, this RRBE message is used to indicate MSCa monitoring called party answer, busy, nonreply, the event such as unreachable, and this processing can realize with reference to prior art.
Need to prove that step a404 and a405 do not have the sequencing restriction when carrying out.
A406:MSCa sends the IDP message that is used for triggering the Call Collision business according to the T-CSI of called (terminal B) to SCP;
The Call Collision business because terminal B has also contracted, MSCa triggers IDP message according to called T-CSI, and this time triggering triggers for test point DP12.The calling and called sign of carrying the service key of Call Collision business in the IDP message and calling out a.Wherein, MSCa can obtain from the HLR of terminal B the CAMEL-Subscription-Information T-CSI of terminal B.
A407:SCP receives MSCa after the IDP message that DP12 triggers, the call context of searching buffer memory, and the context of determining not exist conflict to call out and call out a is buffer memory;
Since among the step a404 buffer memory call out the context of a, can find to comprise the call context of the calling and called sign of calling out a herein when searching, because the calling identification in the call context that finds out is A herein, called identification is B, consistent with the calling and called sign of calling out a, therefore, not existing conflict to call out and the call context of calling a buffer memory, therefore, SCP continues replay call a with direct instruct MS C.
A408:SCP sends continue message to MSCa, and instruct MS C continues replay call a.
A409:MSCa sends IAM to the visited place MSCb of terminal B;
To call out before a is routed to terminal B at MSCa, namely before step a409, if terminal B has initiated calling b, SCP is to calling out the processing of b, and is specific as follows:
The calling b to terminal A that the visited place moving exchanging center MSC b receiving terminal B of b401: terminal B initiates;
B402:MSCb sends the IDP message that is used for triggering the Call Collision business according to the O-CSI of terminal B to SCP;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out b.
B403:SCP obtains the calling and called sign of calling b, with the call context that the calling and called sign of obtaining is searched buffer memory, determines to exist the calling that conflicts with calling b;
Occur prior to calling out b owing to calling out a, buffer memory comprises the call context that terminal A identifies and terminal B identifies in a404, therefore, can find in this step the call context that comprises the calling and called sign of calling out b, thereby determine to exist the calling that conflicts.
B404: send RC message, instruct MS Cb call release b to MSCb;
The resource of b405:MSCb call release b makes the B terminal return to idle condition.
Therefore the situation of present embodiment for the processing of calling out b was finished before step a409, when MSC receives the IAM message that sends among the step a409, called out b and be released, can be by successful connection so call out a, and concrete process is:
Step a410:MSCb call terminal B also returns ACM to MSCa;
After this processing of step a411-a415 can with reference to the a208-a212 among the figure 2, repeat no more here.
Similarly, in scene 2, although also may exist and call out b and occur in MSCa and will call out a and be routed to before the terminal B, but the situation that before step a409, does not have enough time to discharge, for this situation, process as shown in Figure 5, Fig. 5 is the flow chart of another embodiment of the Call Collision processing method under the scene 2, and the Call Collision processing method comprises among this embodiment:
Wherein, the processing of step a501-a509 can with reference to the a401-a409 among the figure 4, repeat no more here.
To call out before a is routed to terminal B at MSCa, namely before step a509, if terminal B has initiated calling b, SCP processes calling out b, step b501-b505 is the processing procedure of calling b, wherein, but the processing procedure refer step b401-b405 of step b501-b505.
Just in the present embodiment, the processing of calling out b was not yet finished before step a409, therefore with embodiment illustrated in fig. 3 similar, returned the REL message informing at step a510:MSCb to MSCa and continue unsuccessfully, and carry cause value: be busy;
A511:MSCa sends ERB message to SCP, reports the busy event;
The a512:SCP wait of delaying time;
Time-delay herein is that terminal B returns to idle condition for the finishing dealing with of Waiting for Call b, and delay duration can rule of thumb be worth and sets in advance.For accuracy is higher, this step can also adopt another kind of alternative, and namely the state of the real-time sense terminals B of SCP when detecting terminal B recovery idle condition, sends Reconnect message to MSC.
A513: send Reconnect message to MSC when time-delay reaches default delay duration, instruct MS C is replay call a again;
A514:MSCa sends IAM to MSCb.
After this processing of a515-a520 can with reference to the a207-a212 among the figure 2, repeat no more here.
Scene 3: terminal A and terminal B are all signatory to have Call Collision professional, and belongs to different SCP, and terminal A belongs to SCPa, and terminal B belongs to SCPb.Wherein, terminal A becomes calling a to the calling of terminal B, and terminal B becomes calling b to the calling of terminal A, supposes that calling out a occurs prior to calling out b.
Fig. 6 is the flow chart of the Call Collision processing method under the scene 3, and as shown in the figure, among this embodiment, the Call Collision processing method comprises:
The calling a to terminal B that the visited place moving exchanging center MSC a receiving terminal A of a601: terminal A initiates;
A602:MSCa sends the IDP message that is used for triggering the Call Collision business according to the O-CSI of terminal A to SCPa;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out a.
A603:SCPa obtains the calling and called sign of calling out a, with the call context that the calling and called sign of obtaining is searched buffer memory, determines not exist the calling that conflicts with calling a;
Wherein, the calling and called sign that comprises respective call in each call context, by searching the call context of buffer memory, can determine whether to comprise the call context of the calling and called sign of calling out a, thereby determine whether to exist the calling that conflicts with calling a, owing to call out a prior to calling out the b generation, therefore, search less than the call context that comprises the calling and called sign of calling out a in the present embodiment.
A604: buffer memory is called out the context of a, and wherein, the context of the calling a of buffer memory comprises the calling and called sign of calling out a;
In the present embodiment, in the buffer memory call context, can calling and called not distinguished.
A605: send continue message, instruct MS C replay call a to MSC;
Optionally, when sending continue message, can further send request report Basic Call State Model BCSM event (request report BCSM (basic call state mode to MSC,) event, RRBE) message, this RRBE message is used to indicate MSCa monitoring called party answer, busy, nonreply, the event such as unreachable, and this processing can realize with reference to prior art.
Need to prove that step a604 and a605 do not have the sequencing restriction when carrying out.
A606:MSCa sends the IDP message that is used for triggering the Call Collision business according to the T-CSI of called (terminal B) to SCPb;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out a.
At this moment, if calling out b before step a606 occurs, and among the SCPb buffer memory call out the context of b, be that step b604 occurs in before the step a606, when SCPb received IDP message among the step a606, SCPb can judge and exist and the calling of calling out a and conflicting, therefore, calling a can be discharged, specifically process referring to step a607-a612.
Obtain the calling and called sign of calling out a at step a607:SCPb, with the call context that the calling and called sign of obtaining is searched buffer memory, determine to exist the call context that comprises the calling and called sign of calling out a;
A608: send RC message, instruct MS Ca call release a to MSCa;
A609:MSCa sends ERB information reporting release event to SCPa;
The context of the calling a of a610:SCPa deletion buffer memory;
A611:SCPa sends RC message to MSCa, and instruct MS Ca continues call release a;
The resource of a612:MSCa call release a makes the A terminal return to idle condition.
In the present embodiment, as follows for the processing of calling out b:
The calling b to terminal A that the visited place moving exchanging center MSC b receiving terminal B of b601: terminal B initiates;
B602:MSCb sends the IDP message that is used for triggering the Call Collision business according to the O-CSI of terminal B to SCPb;
The calling and called sign of wherein, carrying the service key of Call Collision business in the IDP message and calling out b.
B603:SCPb obtains the calling and called sign of calling out b, with the call context that the calling and called sign of obtaining is searched buffer memory, determines not exist the calling that conflicts with calling b;
Because step b603 occurs in before the step a606, therefore, there is not the call context that comprises the calling and called sign of calling out b among the SCPb, thereby determines not exist the calling that conflicts with calling b.
B604: buffer memory is called out the context of b, and wherein, the context of the calling b of buffer memory comprises the calling and called sign of calling out b;
Concrete, in the buffer memory call context, can the calling and called sign not distinguished, directly storaging mark A and sign B.
B605: send continue message, instruct MS Cb replay call b to MSCb;
Optionally, when sending continue message, can further send request report Basic Call State Model BCSM event (request report BCSM (basic call state mode) event to MSC, RRBE) message, this RRBE message is used to indicate MSCb monitoring called party answer, busy, nonreply, the event such as unreachable, and this processing can realize with reference to prior art.
Need to prove that step b604 and b605 do not have the sequencing restriction when carrying out.
B606:MSCb sends the IDP message that is used for triggering the Call Collision business according to the T-CSI of called (the terminal A) that call out b to SCPa;
Present embodiment occurs in after the step a612 as example take step b606 and describes.
B607:SCPa obtains the calling and called sign of calling out b, with the call context that the calling and called sign of obtaining is searched buffer memory, determines not deposit and the calling of calling out b and conflicting;
Because step b606 occurs in after the step a612, call out that a has discharged and the context of calling out a is deleted, therefore, search the call context that identifies less than comprising the calling and called of calling out b, thus not definite not depositing and the calling of calling out b and conflicting.
B608: buffer memory is called out the context of b, and wherein, the context of the calling b of buffer memory comprises the calling and called sign of calling out b;
B609: send continue message, instruct MS Cb replay call b to MSCb;
Step b610-step b619 is call-connection process, but step b610-b615 refer step a206-a211 wherein repeats no more here.
After the step b615, send the ERB information reporting at step b616:MSCb to SCPa and reply event;
B617:SCPa sends Continue message instruct MS Cb call establishment b to MSCb;
The context of the calling b of b618:SCPa deletion buffer memory.
Need to prove that step b617 and b618 do not have the sequencing restriction when carrying out.
B619: call out b and successfully set up, terminal A and terminal B begin conversation.
Shown in Figure 6 only is a kind of embodiment under the scene 3, for other embodiment, can carry out similar processing referring to figs. 2 to embodiment illustrated in fig. 6.As scene 3 times, b occurs in step a606 afterwards and also be not able to do in time release before calling a is switched to terminal B if call out, can appear in the process of replay call a this moment, SCPa receives the situation that MSCa reports the busy event, in the case, can process calling out b with reference to Fig. 3 step a309-a310.
Need to prove, solve the Call Collision problem under above-mentioned arbitrary scene, all can improve to a certain extent percept of call completed, reduce call loss.Therefore, when reality is implemented, can as required, select only the Call Collision problem under some scene to be processed.
The embodiment of the invention further provides the device embodiment that realizes each step among the said method embodiment.Fig. 7 shows a kind of embodiment of business control device.In this embodiment, business control device comprises:
Acquiring unit 701 is used at call establishment, obtains the calling and called sign of current calling;
Control unit 702, the call context that the calling and called sign that is used for obtaining according to described acquiring unit 701 is searched buffer memory determines whether the context with the afoul calling of current calling; If have, then indicate moving exchanging center MSC to discharge current calling; If no, then the context of the current calling of buffer memory is slow, and the instruct MS C current calling that continues, and when successfully continuing current calling or when finding that current calling has been released in handshaking procedure, deletes the context of current calling; Wherein, the context of the current calling of buffer memory comprises the calling and called sign of current calling.
Concrete, (the mobile switching center of mobile switching centre, MSC) receive the calling that calling terminal initiates after, Call Collision is professional if definite caller or terminal called have been contracted, then send the message that is used for triggering the Call Collision business to business control device, such as initial test point (initial domain part, IDP) message, after acquiring unit 701 in the business control device receives this message, from this message, obtain the calling and called sign of current calling.
Wherein, MSC can determine whether that signatory Call Collision is professional according to caller or called CAMEL-Subscription-Information, this CAMEL-Subscription-Information can be that the user of mobile network enhancing logic uses CAMEL-Subscription-Information (customizedapplications for mobile network enhanced logic (CAMEL) subscriptioninformation, CSI).Optionally, it is professional that MSC also can give tacit consent to all users Call Collision of having contracted, and directly sends the message that triggers the Call Collision business to business control device after calling out receiving.Need to prove, can comprise O-CSI and T-CSI in the CAMEL-Subscription-Information of Call Collision business.
Acquiring unit 701 offers control unit 702 with the calling and called of current calling sign, and the call context that control unit 702 is searched buffer memory according to this calling and called sign determines whether to exist the context with the afoul calling of current calling.Wherein, if do not distinguish calling and called in the call context of buffer memory, be specially the call context of the calling and called sign that includes current calling with the context of the afoul calling of current calling.When control unit 702 finds out the call context of the calling and called sign that comprises current calling in the call context of buffer memory, determine the calling of existence and current Call Collision.If the differentiation calling and called are arranged in the call context of buffer memory, be specially with the context of the afoul calling of current calling: the caller of record is the called of current calling, and the called of record is the call context of the caller of current calling.Control unit 702 has found out call context in the call context of buffer memory, it is recorded as the called identification that is designated current calling of caller, and this call context is recorded as called when being designated the calling identification of current calling, determines to exist the calling with current Call Collision.
In above-mentioned embodiment shown in Figure 7, control unit 702 can by sending the instruction that discharges current calling to MSC, such as call release (release call, RC) signaling, come instruct MS C to discharge current calling.In the situation that does not exist conflict to call out, control unit 702 can be by sending the instruction of current calling that continues to MSC, as (continue) message that continues, the instruct MS C current calling that continues.In addition, control unit 702 can be determined the current calling of successful connection to receive the called party answer message that MSC reports, and determines to find that to receive the release event that MSC reports current calling is released in handshaking procedure.
In above-described embodiment, buffer memory by control unit 702 control call context, and determine whether to exist Call Collision according to the call context of buffer memory, and determining when having Call Collision, current calling is discharged, thereby guaranteed to a certain extent and the successful connection of afoul another calling of current calling, improved percept of call completed, avoided the waste of Internet resources.
Because in call establishment, signaling transmits and has time-delay, therefore, under some special screnes, also needs to be further processed.Such as the indication that continues that receives control unit 702 transmissions at MSC, and the call proceeding that terminal A is initiated is during to terminal B, the calling that terminal B initiates to terminal A does not also have enough time to discharge (one fixed response time being arranged from being discharged into terminal recovery idle condition), at this moment, the situation that busy can occur, MSC can report the busy event to business control device.Therefore, in order to solve this special circumstances, service processing equipment can also further comprise delay unit 703 on basis embodiment illustrated in fig. 7, as shown in Figure 8, and the structural representation of the service processing equipment that Fig. 8 provides for another embodiment of the present invention.Wherein, delay unit 703 is used for the monitoring delay duration, when arriving default delay duration, and notice control unit 702; Control unit 702 also is used in the process of current calling that continues, if receive the busy event, the wait of then delaying time, and Time delay unit 703 starts monitoring, when receive that described delay unit sends reach the notice of default delay duration the time, send the instruction of the current calling that again continues to MSC.
Optionally, in another embodiment, service processing equipment also can further comprise detecting unit 704 on basis embodiment illustrated in fig. 7, as shown in Figure 9, and the structural representation of the service processing equipment that Fig. 9 provides for another embodiment of the present invention.Wherein, detecting unit 704 is used for detecting in real time the called state of current calling, notice control unit 702 when detecting this called recovery idle condition; Control unit 702 also is used in the process of current calling that continues, if receive the busy event, detection trigger unit 704 start detection then when receiving the notice of the called recovery idle condition that detecting unit 704 sends, send the instruction of the current calling that again continues to MSC.
By above-mentioned processing, some unsuccessful problems that in particular cases continue have been solved, so that percept of call completed has obtained further improving.And above-mentioned dual mode respectively has advantage, and the processing of mode one need not with miscellaneous equipment mutual, directly waits for get final product the saving Internet resources; Mode two can directly be known called state, and accuracy is high.
In addition, in all the contracted situation of Call Collision business of calling and called both sides, also following situation may appear: after service processing equipment instruct MS C continues current calling, MSC according to the CAMEL-Subscription-Information of terminal called (as, T-CSI) again send to this service processing equipment and be used for triggering the professional message of conflict (such as, IDP message).At this moment, control unit 702 is at Fig. 7, on Fig. 8 or the basis embodiment illustrated in fig. 9, can further include following function: be used at the current calling procedure that continues, if receive MSC when the Initial Detection Point IDP message that test point (detection point, DP) 12 is initiated, the call context of searching buffer memory, determine not exist conflict to call out and the context of current calling buffer memory, the instruct MS C current calling that continues to continue.When the Call Collision that solves in the case, need to distinguish calling and called in the call context of buffer memory.Present embodiment also is the processing in particular cases, and purpose is further to improve percept of call completed, with conserve network resources.
In concrete application scenarios, the function of business control device can be such as embodiment of the method Fig. 2 to shown in Figure 6, and wherein, all can be controlled by control unit 702 alternately between business control device and the MSC being finished.
Business control device in the embodiment of the invention can realize that based on computer system Fig. 1-method shown in Figure 6 all can realize in the business control device based on computer system.Figure 10 shows the embodiment of the business control device of realizing based on computer system.Business control device can comprise in the present embodiment: processor 1001, memory 1002 and communication interface 1003.Memory 1002 is used for program code stored.Processor 1001 is used for the program code of execute store 1002 storages.In the embodiment of the invention, memory 1002 stores the first program code, and processor 1001 is used for carrying out this first program code, comprises and carries out following operation: in call establishment, obtain the calling and called sign of current calling; Call context according to this calling and called sign is searched buffer memory determines whether the context with the afoul calling of current calling; If have, then indicate moving exchanging center MSC to discharge current calling; If no, the then context of the current calling of buffer memory, and the instruct MS C current calling that continues when successfully continuing current calling or when finding that current calling has been released in handshaking procedure, is deleted the context of current calling; Wherein, the context of the current calling of buffer memory comprises the calling and called sign of current calling.Communication interface 1003 is used for and external device communication, as communicating by letter with MSC.Message (shown in embodiment of the method Fig. 1-6) mutual between business control device and the MSC is all by communication interface 1003 sending and receivings.Wherein, processor 1001 is processed the message that communication interface 1003 receives according to the program code in the memory 1002, and mutual by communication interface 1003 and external equipment.Processor 1001 can be central processing unit (centralprocessing unit, CPU), application-specific integrated circuit (ASIC) (application-specific integrated circuit, ASIC) etc.Wherein, the business control device in the present embodiment can comprise bus 1104.Can connect and communication by bus 1104 between processor 1101, memory 1002 and the communication interface 1103.Wherein, memory 1002 can comprise: random access memory (random access memory, RAM), and read-only memory (read-only memory, ROM), disks etc. have the entity of memory function.Call context in the embodiment of the invention can be buffered among the RAM.
Wherein, if do not distinguish calling and called in the call context of buffer memory, be specially the call context of the calling and called sign that includes current calling with the context of the afoul calling of current calling.Processor 1001 is when carrying out the above-mentioned contextual operation that determines whether with the afoul calling of current calling, when being specially the call context that in the call context of buffer memory, finds out the calling and called sign that comprises current calling, then determine the calling of existence and current Call Collision.If the differentiation calling and called are arranged in the call context of buffer memory, be specially with the context of the afoul calling of current calling: the caller of record is the called of current calling, and the called of record is the call context of the caller of current calling.Processor 1001 is when carrying out the above-mentioned contextual operation that determines whether with the afoul calling of current calling, be specially the called identification that is designated current calling of the caller that in the call context of buffer memory, finds out record, and during the call context of the called calling identification that is designated current calling of record, determine the calling of existence and current Call Collision.
When specific implementation, owing to exist signaling to transmit the problems such as time-delay, therefore, under some special screnes, also need to be further processed.In the case, memory 1002 is also stored the second program code, processor 1001 also is used for carrying out this second program code, comprise and carry out following operation: if in the process of current calling that continues, receive the busy event, the wait of delaying time sends the instruction of the current calling that again continues to MSC when reaching default delay duration.Perhaps, memory 1002 is also stored the 3rd program code, and processor 1001 also is used for carrying out the 3rd program code, comprises and carries out following operation: the called state that detects in real time current calling, when detecting described called recovery idle condition, send the instruction of the current calling that again continues to MSC.
In addition, in all the contracted situation of Call Collision business of calling and called both sides, also following situation may appear: after service processing equipment instruct MS C continues current calling, MSC according to the CAMEL-Subscription-Information of terminal called (as, T-CSI) again send to this service processing equipment and be used for triggering the professional message of conflict (such as, IDP message).In the case, memory 1002 is also stored quadruple pass order code, processor 1001 also is used for carrying out this quadruple pass order code, comprise and carry out following operation: if in the current calling procedure that continues, receive the Initial Detection Point IDP message that MSC initiates at test point (detection point, DP) 12, processor 1001 is searched the call context of buffer memory, determine not exist conflict to call out and the context of current calling during buffer memory, the instruct MS C current calling that continues to continue.When the Call Collision that solves in the case, need to distinguish calling and called in the call context of buffer memory.
The embodiment of the invention further provides the system embodiment that realizes each step among the said method embodiment.Figure 11 shows a kind of embodiment that processes the system of Call Collision.In this embodiment, the system of processing Call Collision comprises: business control device 1101 and mobile switching centre (mobile switching center, MSC) 1102.Wherein, the concrete structure of business control device 1101 can be with reference to the device embodiment part of business control device, such as the business control device among Fig. 7, Fig. 8, Fig. 9 and Figure 10.MSC then is used for according to the indication that business control device 1101 issues current calling being processed.If the scheme of the embodiment of the invention is applied in the intelligent network, but user's application (customized applications for mobile network enhancedlogic, CAMEL) agreement of movement-based net enhancing logic communicates between business control device 1101 and the MSC1102.Business control device 1101 can be the SCP in the intelligent network.The upper Service Switching Point (service switching point, SSP) of disposing in the intelligent network of MSC1102, MSC1102 is mutual by SSP and business control device 1101.
Through the above description of the embodiments, the those skilled in the art can be well understood to the present invention and can realize with hardware, or the firmware realization, or their compound mode realizes.When using software to realize, above-mentioned functions can be stored in the computer-readable medium or as one or more instructions or code on the computer-readable medium and transmit.Computer-readable medium comprises computer-readable storage medium and communication media, and wherein communication media comprises any medium of being convenient to transmit from a place to another place computer program.Storage medium can be any usable medium that computer can access.As example but be not limited to: computer-readable medium can comprise RAM, ROM, EEPROM, CD-ROM or other optical disc storage, magnetic disk storage medium or other magnetic storage apparatus or can be used in the program code that carries or store the expectation with instruction or data structure form and can be by any other medium of computer access.In addition.Any connection can be suitable become computer-readable medium.For example, if software be use coaxial cable, optical fiber cable, twisted-pair feeder, Digital Subscriber Line (DSL) or the wireless technology such as infrared ray, radio and microwave from the website, server or the transmission of other remote source, under coaxial cable, optical fiber cable, twisted-pair feeder, DSL or the wireless technology such as infrared ray, wireless and microwave are included in so in the photographic fixing of medium.As used in the present invention, dish (Disk) and dish (disc) comprise compression laser disc (CD), laser dish, laser disc, digital universal laser disc (DVD), floppy disk and Blu-ray Disc, the copy data of the common magnetic of its mid-game, dish then come the copy data of optics with laser.Top combination also should be included within the protection range of computer-readable medium.
The above; be specific embodiments of the invention only, but protection scope of the present invention is not limited to this, anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; can expect easily changing or replacing, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.