CN102893691B - A kind of method, system and business control device processing Call Collision - Google Patents
A kind of method, system and business control device processing Call Collision Download PDFInfo
- Publication number
- CN102893691B CN102893691B CN201280001195.0A CN201280001195A CN102893691B CN 102893691 B CN102893691 B CN 102893691B CN 201280001195 A CN201280001195 A CN 201280001195A CN 102893691 B CN102893691 B CN 102893691B
- Authority
- CN
- China
- Prior art keywords
- calling
- active calls
- context
- call
- called
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 113
- 238000012545 processing Methods 0.000 title description 26
- 230000008569 process Effects 0.000 claims abstract description 74
- 238000001514 detection method Methods 0.000 claims description 11
- 238000012544 monitoring process Methods 0.000 claims description 8
- 230000004069 differentiation Effects 0.000 claims description 7
- 238000012360 testing method Methods 0.000 claims description 6
- 238000003672 processing method Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 11
- 238000011084 recovery Methods 0.000 description 9
- 238000012163 sequencing technique Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 6
- 230000011664 signaling Effects 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 239000002699 waste material Substances 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000002708 enhancing effect Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 150000001875 compounds Chemical class 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000006386 memory function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/22—Synchronisation circuits
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a kind of method, system and the business control device that process Call Collision, the method comprises: in call establishment, and business control device obtains the calling and called mark of active calls; According to the call context of this calling and called identifier lookup buffer memory, determine whether the context of the afoul calling with active calls; If have, then instruct MS C discharges active calls; If no, then the context of buffer memory active calls, the active calls and instruct MS C continues, when successful connection active calls or when finding that active calls is released in handshaking procedure, deletes the context of active calls; Wherein, the context of the active calls of buffer memory comprises the calling and called mark of active calls.The application embodiment of the present invention, improves percept of call completed to a certain extent, reduces call loss.
Description
Technical field
The present invention relates to communication technical field, particularly a kind of method, system and business control device processing Call Collision.
Background technology
In existing calling procedure, if when terminal A calling terminal B, terminal B forward terminal A makes a call, now, bid conflict, the calling that terminal A and terminal B initiate all can busy, thus the calling cannot successfully set up between A and B, reduce call successful rate.
Summary of the invention
The embodiment of the present invention provides a kind of method, system and the business control device that process Call Collision, to improve call successful rate.
First aspect, the method for process Call Collision comprises:
In call establishment, business control device obtains the calling and called mark of active calls;
According to the call context of this calling and called identifier lookup buffer memory, determine whether the context of the afoul calling with active calls;
If have, then indicate moving exchanging center MSC release active calls;
If no, then the context of buffer memory active calls, the active calls and instruct MS C continues, when successful connection active calls or when finding that active calls is released in handshaking procedure, deletes the context of active calls; Wherein, the context of the active calls of buffer memory comprises the calling and called mark of active calls.
In the first possible implementation of first aspect, in the process continuing active calls, if receive busy event, business control device carries out time delay wait, sends the instruction of the active calls that again continues when reaching default delay duration to MSC.
In the implementation that the second of first aspect is possible, in the process continuing active calls, if receive busy event, business control device detects the called state of active calls in real time, when described called recovery idle condition being detected, send the instruction of the active calls that again continues to MSC.
In conjunction with first aspect or the first possible implementation of first aspect or the possible implementation of the second of first aspect, in the implementation that the third is possible, if do not distinguish calling and called in the call context of buffer memory, then the context of afoul calling is specially the call context that the calling and called that include active calls identify with active calls.
In conjunction with first aspect or the first possible implementation of first aspect or the possible implementation of the second of first aspect, in the 4th kind of possible implementation, if there are differentiation calling and called in the call context of buffer memory, then the context of afoul calling is specially with active calls: the caller of record is the called of active calls, and the called of record is the call context of the caller of active calls.
In conjunction with the 4th kind of possible implementation of first aspect, in the 5th kind of possible implementation, continuing in active calls process, if receive the Initial Detection Point IDP message that MSC initiates at test point DP12, business control device searches the call context of buffer memory, determine not with the context of the afoul calling of active calls, and the context of active calls buffer memory time, instruct MS C continues the active calls that continues.
Second aspect, business control device comprises:
Acquiring unit, in call establishment, obtains the calling and called mark of active calls;
Control unit, for the call context of calling and called identifier lookup buffer memory obtained according to described acquiring unit, determines whether the context of the afoul calling with active calls; If have, then indicate moving exchanging center MSC release active calls; If no, then the context of buffer memory active calls, and indicate described MSC to continue active calls, when successful connection active calls or when finding that active calls is released in handshaking procedure, delete the context of active calls; Wherein, the context of the active calls of described buffer memory comprises the calling and called mark of active calls.
In the first possible implementation of second aspect, business control device also wraps: draw together delay unit, for monitoring delay duration, when arriving default delay duration, notifies described control unit; Control unit is also in the process continuing active calls, if receive busy event, then carry out time delay wait, and trigger described delay unit startup monitoring, when receive that described delay unit sends reach the notice of default delay duration time, send the instruction of the active calls that again continues to described MSC.
In the implementation that the second of second aspect is possible, business control device also wraps: detecting unit, for detecting the called state of active calls in real time, notifies described control unit when described called recovery idle condition being detected; Control unit is also in the process continuing active calls, if receive busy event, then triggering described detecting unit start detection, when receiving the notice of the described called recovery idle condition that described detecting unit sends, sending the instruction of the active calls that again continues to described MSC.
In the implementation that the third is possible, in conjunction with second aspect or the first possible implementation of second aspect or the possible implementation of the second of second aspect, if do not distinguish calling and called in the call context of buffer memory, then the context of afoul calling is specially the call context that the calling and called that include active calls identify with active calls.
In the 4th kind of possible implementation, in conjunction with second aspect or the first possible implementation of second aspect or the possible implementation of the second of second aspect, if there are differentiation calling and called in the call context of buffer memory, then the context of afoul calling is specially with active calls: the caller of record is the called of active calls, and the called of record is the call context of the caller of active calls.
In the 5th kind of possible implementation, in conjunction with the 4th kind of possible implementation of second aspect, processing unit is also in the process continuing active calls, if receive from communication unit the Initial Detection Point IDP message that described MSC initiates at monitoring point DP12, then search the call context of buffer memory in memory cell, determine not with the context of the afoul calling of active calls, and the context of active calls buffer memory time, described MSC continues the active calls that continues.
The third aspect, the system of process Call Collision, comprises the business control device in the 5th kind of possible implementation of the possible implementation of the second of the first possible implementation of moving exchanging center MSC and second aspect or second aspect or second aspect or the third possible implementation of second aspect or the 4th kind of possible implementation of second aspect or second aspect; Wherein, the instruction that MSC is used for issuing according to described business control device processes active calls.
In the embodiment of the present invention, owing to being deleted by the context of active calls at successful connection active calls or when finding that active calls is released in handshaking procedure, thus guarantee that the context of business control device buffer memory is the context of the calling be in call establishment.Therefore, when receiving calling, business control device can determine whether there is Call Collision according to the call context of buffer memory, when there is Call Collision, active calls is discharged, thus ensure that another successful connection called out to a certain extent, improve percept of call completed, avoid the waste of Internet resources.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme of the embodiment of the present invention, be briefly described to the accompanying drawing used required in embodiment below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
The method flow diagram of the process Call Collision that Fig. 1 provides for the embodiment of the present invention;
Call Collision process flow figure under the scene 1 that Fig. 2 provides for the embodiment of the present invention;
Fig. 3 is the flow chart of another embodiment of Call Collision processing method under scene 1;
The flow chart of the Call Collision processing method under the scene 2 that Fig. 4 provides for the embodiment of the present invention;
Fig. 5 is the flow chart of another embodiment of Call Collision processing method under scene 2;
The flow chart of the Call Collision processing method under the scene 3 that Fig. 6 provides for the embodiment of the present invention;
Fig. 7 provides the structural representation of business control device for the embodiment of the present invention;
Fig. 8 provides the structural representation of business control device for another embodiment of the present invention;
Fig. 9 provides the structural representation of business control device for another embodiment of the present invention;
Figure 10 provides the structural representation of the business control device based on computer system for the embodiment of the present invention;
Figure 11 provides the structural representation of the system of solution Call Collision for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
In the process of calling terminal calling terminal called, terminal called is also in the process of calling calling terminal, and this phenomenon is referred to as Call Collision in embodiments of the present invention.The method flow diagram of the process Call Collision that Fig. 1 provides for the embodiment of the present invention, as shown in the figure, the method processing Call Collision in this embodiment comprises:
S100, in call establishment, business control device obtains the calling and called mark of active calls;
Wherein, business control device is the equipment carrying out Business Processing and carry out Call-Control1 in calling procedure, such as, and the service control point (servicecontrolpoint in intelligent network, SCP), in embodiments of the present invention for the treatment of Call Collision business.Call Collision business is the business for solving Call Collision.
Mobile switching centre (mobileswitchingcenter, MSC) after receiving the calling of calling terminal initiation, if determine, caller or terminal called have been contracted Call Collision business, the message being used for trigger call conflict business is then sent to business control device, as Initial Detection Point (initialdomainpart, IDP) message, business control device obtains the calling and called mark of active calls from this message.
Wherein, MSC can determine whether signing Call Collision business according to caller or called CAMEL-Subscription-Information, this CAMEL-Subscription-Information can be that the user of mobile network enhancing logic applies CAMEL-Subscription-Information (customizedapplicationsformobilenetworkenhancedlogic (CAMEL) subscriptioninformation, CSI).
Optionally, MSC also can give tacit consent to all users and to have contracted Call Collision business, according to the address of pre-configured business control device after receiving calling, sends the message of trigger call conflict business to business control device.
S102, according to the call context of this calling and called identifier lookup buffer memory, determines whether there is the context of the afoul calling with active calls; If have, then perform S104; If no, then perform S106;
Wherein, business control device is cached with the context of the calling be in call establishment, and the context of each calling comprises the calling and called mark of this calling.Business control device can determine whether there is conflict calling by the call context of searching buffer memory.Certainly, call context in local cache call context, also can be buffered in outside memory device by business control device.
Concrete, business control device can not distinguish calling and called (only the mark of buffer memory calling and called itself) when the call context of buffer memory, also calling and called (namely except the mark of buffer memory calling and called itself, also mark this mark and belong to caller or called) can be distinguished.
If do not distinguish calling and called in the call context of buffer memory, be specially with the context of the afoul calling of active calls the call context that the calling and called that include active calls identify.When business control device finds out the call context of the calling and called mark comprising active calls in the call context of buffer memory, determine to there is the calling conflicted with active calls.
Under normal circumstances, according to whether there being the call context comprising these calling and called mark to determine whether there is Call Collision in the call context of buffer memory.Under some particular demands, as when in same calling, second time sends to business control device the message being used for trigger call conflict business, whether the caller can determining the record in call context is further the called of active calls, whether called be the caller of active calls, in order to avoid using this calling self as conflict calling, because the buffer memory context of this calling during this calling first time trigger call conflict business.Concrete, if having differentiation calling and called in the call context of buffer memory, then the context of afoul calling is specially with active calls: the caller of record is the called of active calls, and record called is the call context of the caller of active calls.Business control device has found out call context in the call context of buffer memory, it is recorded as the called identification being designated active calls of caller, and this call context is recorded as called when being designated the calling identification of active calls, determines to there is the calling conflicted with active calls.
S104, instruct MS C discharge active calls.
Concrete, business control device sends the instruction of release active calls to MSC, and as call release (releasecall, RC) signaling, MSC is according to this instruction release active calls.
S106, the context of buffer memory active calls, the active calls and instruct MS C continues, when successful connection active calls or when finding that active calls is released in handshaking procedure, deletes the context of active calls; Wherein, the context of the active calls of buffer memory comprises the calling and called mark of active calls.
Concrete, when there is not conflict calling, business control device sends the instruction of the active calls that continues to MSC, and as (continue) message that continues, instruct MS C continues active calls.Wherein, business control device can to receive called party answer message that MSC reports to determine successful connection active calls, and the release event reported to receive MSC is determined in handshaking procedure, find that active calls is released.
In step S106, the context of buffer memory can be used as the foundation judging Call Collision in subsequent treatment, such as, before the context deleting active calls, the calling that the called caller to active calls receiving active calls is initiated, now, business control device can determine according to the call context of buffer memory the calling that there is conflict.
In above-described embodiment, owing to being deleted by the context of active calls when successful connection active calls or when finding that active calls is released in handshaking procedure, thus guarantee that the context of business control device buffer memory is the context of the calling be in call establishment.Therefore, when receiving calling, business control device can determine whether there is Call Collision according to the call context of buffer memory, when there is Call Collision, active calls is discharged, thus ensure that another successful connection called out conflicted with active calls to a certain extent, improve percept of call completed, avoid the waste of Internet resources.
Due in call establishment, there is time delay in signaling transmission, therefore, under some special screnes, also needs to be further processed.Such as, after abovementioned steps S106, MSC receives the active calls instruction that continues, and by terminal A initiate call proceeding to terminal B time, terminal B does not also have enough time to discharge (having a fixed response time from being discharged into terminal recovery idle condition) to the calling that terminal A initiates, now, there will be the situation of busy, MSC can report busy event to business control device.Therefore, in order to solve this special circumstances, service processing equipment further can also process on basis embodiment illustrated in fig. 1.Specifically can adopt following two kinds of processing modes:
Mode one: in the process continuing active calls, if receive busy event, business control device carries out time delay wait, sends the instruction of the active calls that again continues when reaching default delay duration to MSC.Wherein, default delay duration can preset based on experience value, such as 10 seconds.
Mode two: in the process continuing active calls, if receive busy event, business control device detects the called state of active calls in real time, when described called recovery idle condition being detected, sends the instruction of the active calls that again continues to MSC.
By above-mentioned process, solve some unsuccessful problems that in particular cases continue, percept of call completed is obtained and further improves.And above-mentioned two kinds of modes respectively have advantage, the process of mode one, without the need to mutual with miscellaneous equipment, directly waited for, is saved Internet resources; Mode two directly can know called state, and accuracy is high.
In addition, the situation of Call Collision business of all having contracted calling and called both sides, also may there is following situation: after service processing equipment instruct MS C continues active calls, MSC according to the CAMEL-Subscription-Information of terminal called (as, T-CSI) again the message (e.g., IDP message) for triggering conflict business is sent to this service processing equipment.Now, service processing equipment can further include following process on the basis of Fig. 1 or other embodiment above-mentioned: continuing in active calls process, if receive MSC at test point (detectionpoint, DP) 12 initiate Initial Detection Point IDP message time, business control device searches the call context of buffer memory, determine to there is not conflict calling and the context of active calls buffer memory, instruct MS C continues the active calls that continues.The present embodiment is also to process in particular cases, and object is further to improve percept of call completed, to save Internet resources.
The scheme of the embodiment of the present invention can be applied in intelligent network or other network, for the ease of understanding, the embodiment of the present invention is all described for the message in intelligent network, when being applied in other network, can be replaced the message in other network with similar functions.
If realize with intelligent network the scheme that the embodiment of the present invention provides, need in attaching position register (homelocationregister, HLR) for user contracts Call Collision business.Namely also comprised before the step S100 shown in Fig. 1 and carry out CAMEL-Subscription-Information setting in advance, CAMEL-Subscription-Information setting up procedure is as follows: HLR makes and preserves the CAMEL-Subscription-Information of user, comprise Originating CAMEL Subscription Information (originatingCAMELsubscriptioninformation, and Terminating CAMEL Subscription Information (terminatedCAMELsubscriptioninformation, T-CSI) O-CSI).Service key in O-CSI and T-CSI is the service key of Call Collision business, and the address in O-CSI and T-CSI is the address of the business control device of process Call Collision business.If contracted user does caller, MSC sends the message being used for trigger call conflict business to business control device according to the O-CSI of this user, if contracted user does called, MSC sends the message being used for trigger call conflict business to business control device according to the T-CSI of this user.In abovementioned steps S100, the calling and called mark of business control device acquisition active calls can specifically comprise: business control device receives the message for trigger call conflict business that mobile switching centre sends according to caller or called CAMEL-Subscription-Information, and the calling and called obtaining active calls from this message identify.
Be further detailed the embodiment of the present invention with concrete application scenarios below, following scene is all for intelligent network, and therefore, business control device is the SCP in intelligent network in the examples below.
Scene 1: terminal A is signing Call Collision business, the not signing Call Collision business of terminal B, and wherein, the calling of terminal A to terminal B is called that calling a, terminal B are called calling b to the calling of terminal A, assuming that calling a occurs prior to calling b.
Fig. 2 is the Call Collision process flow figure under scene 1, and as shown in the figure, in the present embodiment, Call Collision processing method comprises:
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 being used for trigger call conflict business to SCP according to the O-CSI of terminal A;
Wherein, the service key of Call Collision business and the calling and called mark of calling a is carried in IDP message.The CAMEL-Subscription-Information O-CSI of terminal A can obtain from visitor location register (visitorlocationregister, VLR).Wherein, VLR can close with MSC and be located in a physical entity, also can be two independently physical entities.The embodiment of the present invention can be closed with MSC with VLR and is set to example and be described.
A203:SCP obtains the calling and called mark of calling a, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is not the calling conflicted with calling a;
Wherein, each call context comprises the calling and called mark of respective call, by searching the call context of buffer memory, the call context of the calling and called mark comprising calling a can be determined whether, thus determine whether there is and the calling of calling out a and conflicting, because calling a occurs prior to calling b in the present embodiment, therefore, the call context less than the calling and called mark comprising calling a is searched.
A204: the context of buffer memory calling a, wherein, the context of the calling a of buffer memory comprises the calling and called mark of calling a;
Concrete, when buffer memory call context, can not be distinguished calling and called mark, direct storaging mark A and mark B.
A205: send continue message to MSC, instruct MS C replay call a;
Optionally, when sending continue message, report Basic Call State Model BCSM event (requestreport (BasicCallStateMode can be sent request further to MSC, BCSM) event, RRBE) message, this RRBE message is used to indicate MSCa and monitors called party answer, busy, nonreply, the event such as unreachable, and this process can realize with reference to prior art.
It should be noted that step a204 and a205 does not have sequencing restriction when performing.
A206:MSCa sends initial address message (InitialAddressMessage, IAM) to the visited place MSCb of terminal B;
Before calling a is routed to terminal B by MSCa, namely before step a206, if terminal B has initiated calling b, SCP is to the process of calling b, 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 being used for trigger call conflict business to SCP according to the T-CSI of called (terminal A);
Wherein, the service key of Call Collision business and the calling and called mark of calling b is carried in IDP message.
B203:SCP obtains the calling and called mark of calling b, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is the calling conflicted with calling b;
Because calling a occurs prior to calling b, in a204, buffer memory comprises the call context of terminal A mark and terminal B mark, therefore, can find the call context of the calling and called mark comprising calling b in this step, thus determine to there is conflict calling.
B204: send RC message to MSCb, instruct MS Cb call release b;
The resource of b205:MSCb call release b, makes B terminal return to idle condition.
In the present embodiment, completed before step a206 the process of calling b, therefore, when MSC receives IAM message, calling b is released, so calling a can by successful connection, concrete process is as follows:
Step a207:MSCb call terminal B and to MSCa return address full message (addresscompletemessage, ACM);
A208: after terminal called response, MSCb sends address response message (addressanswermessage, ANM) to MSCa;
A209:MSCa sends Basic Call State Model BCSM reporting events (eventreportbasiccallstatemodel, ERB) message to SCP and reports response event;
A210:SCP sends Continue message instruct MS Ca call establishment a to MSCa;
A211:SCP deletes the context of the calling a of buffer memory.
It should be noted that step a210 and a211 does not have sequencing restriction when performing.
A212: calling a successfully sets up, and terminal A and terminal B starts call.
Because signaling transmission exists time delay, therefore, although likely there is calling b occurs in before calling a is routed to terminal B by MSCa, but in the situation that the before future of step a206 obtains and discharges, for this situation, as shown in Figure 3, Fig. 3 is the flow chart of another embodiment of Call Collision processing method under scene 1, and in the present embodiment, Call Collision processing method comprises in process:
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 being used for trigger call conflict business to SCP according to the O-CSI of terminal A;
Wherein, the service key of Call Collision business and the calling and called mark of calling a is carried in IDP message.
A303:SCP obtains the calling and called mark of calling a, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is not the calling conflicted with calling a;
Wherein, each call context comprises the calling and called mark of respective call, by searching the call context of buffer memory, the call context of the calling and called mark comprising calling a can be determined whether, thus determine whether there is and the calling of calling out a and conflicting, because calling a occurs prior to calling b in the present embodiment, therefore, the call context less than the calling and called mark comprising calling a is searched.
A304: the context of buffer memory calling a, wherein, the context of the calling a of buffer memory comprises the calling and called mark of calling a;
Concrete, when buffer memory call context, can not calling and called be distinguished.
A305: send continue message to MSC, instruct MS C replay call a;
Optionally, when sending continue message, report Basic Call State Model BCSM event (requestreportBCSM (basiccallstatemode) event can be sent request further to MSC, RRBE) message, this RRBE message is used to indicate MSCa and monitors called party answer, busy, nonreply, the event such as unreachable, and this process can realize with reference to prior art.
It should be noted that step a304 and a305 does not have sequencing restriction when performing.
A306:MSCa sends initial address message (initialaddressmessage, IAM) to the visited place MSCb of terminal B;
Before calling a is routed to terminal B by MSCa, namely before step a306, if terminal B has initiated calling b, SCP is to calling b process, step b301-b305 is the processing procedure of calling b, and wherein the processing procedure of step b301-b305 can with reference to the step b201-b205 shown in figure 2.
Just in the present embodiment, not yet completed before step a306 the process of calling b, therefore, when MSC receives IAM message, calling b is not released, so calling a cannot successful connection.Now, the subsequent treatment of calling a is comprised:
A307:MSCb returns REL message informing to MSCa and continues unsuccessfully, and carries cause value: Called Busy;
A308:MSCa sends ERB message to SCP, reports busy event;
A309:SCP carries out time delay wait;
Time delay is herein that terminal B returns to idle condition in order to the process of Waiting for Call b completes, and delay duration can pre-set based on experience value.In order to accuracy is higher, this step can also adopt another kind of alternative, i.e. the state of the real-time sense terminals B of SCP, when detecting that terminal B recovers idle condition, sends Reconnect message to MSC.
A310: send Reconnect message when time delay reaches default delay duration to MSC, instruct MS C is replay call a again;
A311:MSCa sends IAM to MSCb.
After this process of a312-a317 with reference to the a207-a212 in figure 2, can repeat no more here.
Scene 2: terminal A and terminal B is all signing Call Collision business, and belongs to identical SCP.Wherein, the calling of terminal A to terminal B is called that calling a, terminal B are called calling b to the calling of terminal A, assuming that calling a occurs prior to calling b.
Fig. 4 is the Call Collision process flow figure under scene 2, and as shown in the figure, in this embodiment, Call Collision processing method comprises:
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 being used for trigger call conflict business to SCP according to the O-CSI of terminal A;
Wherein, the service key of Call Collision business and the calling and called mark of calling a is carried in IDP message.
A403:SCP obtains the calling and called mark of calling a, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is not the calling conflicted with calling a;
Wherein, each call context comprises the calling and called mark of respective call, by searching the call context of buffer memory, the call context of the calling and called mark comprising calling a can be determined whether, thus determine whether there is and the calling of calling out a and conflicting, because calling a occurs prior to calling b in the present embodiment, therefore, the call context less than the calling and called mark comprising calling a is searched.
A404: the context of buffer memory calling a, wherein, the context of the calling a of buffer memory comprises the calling and called mark of calling a;
In the present embodiment, need when buffer memory call context to be distinguished calling and called, as adopted the form of " calling identification=A, called identification=B ".
A405: send continue message to MSC, instruct MS C replay call a;
Optionally, when sending continue message, report Basic Call State Model BCSM event (requestreportBCSM (basiccallstatemode) event can be sent request further to MSC, RRBE) message, this RRBE message is used to indicate MSCa and monitors called party answer, busy, nonreply, the event such as unreachable, and this process can realize with reference to prior art.
It should be noted that step a404 and a405 does not have sequencing restriction when performing.
A406:MSCa sends the IDP message being used for trigger call conflict business to SCP according to the T-CSI of called (terminal B);
Because terminal B has also contracted Call Collision business, MSCa has triggered IDP message according to called T-CSI, this time triggers as test point DP12 triggers.The service key of Call Collision business and the calling and called mark of calling a is carried in IDP message.Wherein, MSCa can obtain the CAMEL-Subscription-Information T-CSI of terminal B from the HLR of terminal B.
A407:SCP searches the call context of buffer memory, determines to there is not conflict calling and the context buffer memory of calling a after receiving the IDP message that MSCa triggers at DP12;
Due in step a404 buffer memory calling a context, the call context of the calling and called mark comprising calling a can be found that there is herein when searching, because the calling identification in the call context that finds out is A herein, called identification is B, identify consistent with the calling and called of calling a, therefore, there is not conflict calling and the call context buffer memory of calling a, therefore, direct instruct MS C is continued replay call a by SCP.
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;
Before calling a is routed to terminal B by MSCa, namely before step a409, if terminal B has initiated calling b, SCP is to the process of calling b, 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 being used for trigger call conflict business to SCP according to the O-CSI of terminal B;
Wherein, the service key of Call Collision business and the calling and called mark of calling b is carried in IDP message.
B403:SCP obtains the calling and called mark of calling b, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is the calling conflicted with calling b;
Because calling a occurs prior to calling b, in a404, buffer memory comprises the call context of terminal A mark and terminal B mark, therefore, can find the call context of the calling and called mark comprising calling b in this step, thus determine to there is conflict calling.
B404: send RC message to MSCb, instruct MS Cb call release b;
The resource of b405:MSCb call release b, makes B terminal return to idle condition.
The present embodiment is situation about completing before step a409 the process of calling b, and therefore, when MSC receives the IAM message sent in step a409, calling b is released, so calling a can by successful connection, concrete process is:
Step a410:MSCb call terminal B also returns ACM to MSCa;
After this process of step a411-a415 with reference to the a208-a212 in figure 2, can repeat no more here.
Similar, in scene 2, although also may there is calling b occurs in before calling a is routed to terminal B by MSCa, but in the situation that the before future of step a409 obtains and discharges, for this situation, as shown in Figure 5, Fig. 5 is the flow chart of another embodiment of Call Collision processing method under scene 2, and in this embodiment, Call Collision processing method comprises in process:
Wherein, the process of step a501-a509 with reference to the a401-a409 in figure 4, can repeat no more here.
Before calling a is routed to terminal B by MSCa, namely before step a509, if terminal B has initiated calling b, SCP is to calling b process, step b501-b505 is the processing procedure of calling b, and wherein, the processing procedure of step b501-b505 can refer step b401-b405.
Just in the present embodiment, the process of calling b was not yet completed before step a409, therefore with embodiment illustrated in fig. 3 similar, returns REL message informing in step a510:MSCb to MSCa and continue unsuccessfully, and carry cause value: be busy;
A511:MSCa sends ERB message to SCP, reports busy event;
A512:SCP carries out time delay wait;
Time delay is herein that terminal B returns to idle condition in order to the process of Waiting for Call b completes, and delay duration can pre-set based on experience value.In order to accuracy is higher, this step can also adopt another kind of alternative, i.e. the state of the real-time sense terminals B of SCP, when detecting that terminal B recovers idle condition, sends Reconnect message to MSC.
A513: send Reconnect message when time delay reaches default delay duration to MSC, instruct MS C is replay call a again;
A514:MSCa sends IAM to MSCb.
After this process of a515-a520 with reference to the a207-a212 in figure 2, can repeat no more here.
Scene 3: terminal A and terminal B is all signing Call Collision business, and belongs to different SCP, and terminal A belongs to SCPa, and terminal B belongs to SCPb.Wherein, the calling of terminal A to terminal B becomes calling a, terminal B and becomes calling b, assuming that calling a is prior to calling b generation to the calling of terminal A.
Fig. 6 is the flow chart of the Call Collision processing method under scene 3, and as shown in the figure, in this embodiment, 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 being used for trigger call conflict business to SCPa according to the O-CSI of terminal A;
Wherein, the service key of Call Collision business and the calling and called mark of calling a is carried in IDP message.
A603:SCPa obtains the calling and called mark of calling a, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is not the calling conflicted with calling a;
Wherein, each call context comprises the calling and called mark of respective call, by searching the call context of buffer memory, the call context of the calling and called mark comprising calling a can be determined whether, thus determine whether there is and the calling of calling out a and conflicting, because calling a occurs prior to calling b in the present embodiment, therefore, the call context less than the calling and called mark comprising calling a is searched.
A604: the context of buffer memory calling a, wherein, the context of the calling a of buffer memory comprises the calling and called mark of calling a;
In the present embodiment, can not be distinguished calling and called when buffer memory call context.
A605: send continue message to MSC, instruct MS C replay call a;
Optionally, when sending continue message, report Basic Call State Model BCSM event (requestreportBCSM (basiccallstatemode can be sent request further to MSC,) event, RRBE) message, this RRBE message is used to indicate MSCa and monitors called party answer, busy, nonreply, the event such as unreachable, and this process can realize with reference to prior art.
It should be noted that step a604 and a605 does not have sequencing restriction when performing.
A606:MSCa sends the IDP message being used for trigger call conflict business to SCPb according to the T-CSI of called (terminal B);
Wherein, the service key of Call Collision business and the calling and called mark of calling a is carried in IDP message.
Now, if called out b to occur before step a606, and in SCPb buffer memory calling b context, namely before step b604 occurs in step a606, when receiving the IDP message in step a606 as SCPb, SCPb can judge there is the calling conflicted with calling a, therefore, calling a can be discharged, specifically process see step a607-a612.
Obtain the calling and called mark of calling a in step a607:SCPb, with the call context of the calling and called identifier lookup buffer memory obtained, determine to exist the call context of the calling and called mark comprising calling a;
A608: send RC message to MSCa, instruct MS Ca call release a;
A609:MSCa sends ERB information reporting release event to SCPa;
A610:SCPa deletes the context of the calling a of 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 A terminal return to idle condition.
In the present embodiment, the process for calling b is as follows:
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 being used for trigger call conflict business to SCPb according to the O-CSI of terminal B;
Wherein, the service key of Call Collision business and the calling and called mark of calling b is carried in IDP message.
B603:SCPb obtains the calling and called mark of calling b, with the call context of the calling and called identifier lookup buffer memory obtained, determines to there is not the calling conflicting with calling b;
Before step b603 occurs in step a606, therefore, in SCPb, there is not the call context of the calling and called mark comprising calling b, thus determine to there is not the calling conflicted with calling b.
B604: the context of buffer memory calling b, wherein, the context of the calling b of buffer memory comprises the calling and called mark of calling b;
Concrete, when buffer memory call context, can not be distinguished calling and called mark, direct storaging mark A and mark B.
B605: send continue message to MSCb, instruct MS Cb replay call b;
Optionally, when sending continue message, report Basic Call State Model BCSM event (requestreportBCSM (basiccallstatemode) event can be sent request further to MSC, RRBE) message, this RRBE message is used to indicate MSCb and monitors called party answer, busy, nonreply, the event such as unreachable, and this process can realize with reference to prior art.
It should be noted that, step b604 and b605 does not have sequencing restriction when performing.
B606:MSCb sends the IDP message being used for trigger call conflict business to SCPa according to the T-CSI of called (the terminal A) of calling b;
The present embodiment is described after occurring in step a612 for step b606.
B607:SCPa obtains the calling and called mark of calling b, with the call context of the calling and called identifier lookup buffer memory obtained, determines not deposit and the calling of calling out b and conflicting;
After step b606 occurs in step a612, calling a has discharged and context call out a is deleted, therefore, searches the call context identified less than the calling and called comprising calling b, thus determines not deposit and the calling of calling out b and conflicting.
B608: the context of buffer memory calling b, wherein, the context of the calling b of buffer memory comprises the calling and called mark of calling b;
B609: send continue message to MSCb, instruct MS Cb replay call b;
Step b610-step b619 is call-connection process, and wherein step b610-b615 can refer step a206-a211, repeats no more here.
After step b615, send ERB information reporting response event in step b616:MSCb to SCPa;
B617:SCPa sends Continue message instruct MS Cb call establishment b to MSCb;
B618:SCPa deletes the context of the calling b of buffer memory.
It should be noted that step b617 and b618 does not have sequencing restriction when performing.
B619: calling b successfully sets up, and terminal A and terminal B starts call.
Be only a kind of embodiment under scene 3 shown in Fig. 6, for other embodiment, similar process can be carried out referring to figs. 2 to embodiment illustrated in fig. 6.As scene 3 times, if calling b occur in step a606 after and calling a be switched to terminal B before be not also able to do in time release, now appear in the process of replay call a, SCPa receives the situation that MSCa reports busy event, in the case, can refer to Fig. 3 step a309-a310 to calling b process.
It should be noted that, solve the Call Collision problem under above-mentioned arbitrary scene, all can improve percept of call completed to a certain extent, reduce call loss.Therefore, when reality is implemented, can as required, select only to process the Call Collision problem under some scene.
The embodiment of the present invention provides the device embodiment realizing each step in said method embodiment further.Fig. 7 shows a kind of embodiment of business control device.In this embodiment, business control device comprises:
Acquiring unit 701, in call establishment, obtains the calling and called mark of active calls;
Control unit 702, for the call context of the calling and called identifier lookup buffer memory according to described acquiring unit 701 acquisition, determines whether the context of the afoul calling with active calls; If have, then indicate moving exchanging center MSC release active calls; If no, then the context of buffer memory active calls delays, the active calls and instruct MS C continues, and when successful connection active calls or when finding that active calls is released in handshaking procedure, deletes the context of active calls; Wherein, the context of the active calls of buffer memory comprises the calling and called mark of active calls.
Concrete, mobile switching centre (mobileswitchingcenter, MSC) after receiving the calling of calling terminal initiation, if determine, caller or terminal called have been contracted Call Collision business, then send the message being used for trigger call conflict business to business control device, as Initial Detection Point (initialdomainpart, IDP) message, after acquiring unit 701 in business control device receives this message, from this message, obtain the calling and called mark of active calls.
Wherein, MSC can determine whether signing Call Collision business according to caller or called CAMEL-Subscription-Information, this CAMEL-Subscription-Information can be that the user of mobile network enhancing logic applies CAMEL-Subscription-Information (customizedapplicationsformobilenetworkenhancedlogic (CAMEL) subscriptioninformation, CSI).Optionally, MSC also can give tacit consent to all users and to have contracted Call Collision business, sends the message of trigger call conflict business after receiving calling directly to business control device.It should be noted that, in the CAMEL-Subscription-Information of Call Collision business, can O-CSI and T-CSI be comprised.
The calling and called of active calls mark is supplied to control unit 702 by acquiring unit 701, and control unit 702, according to the call context of this calling and called identifier lookup buffer memory, determines whether there is the context of the afoul calling with active calls.Wherein, if do not distinguish calling and called in the call context of buffer memory, be specially with the context of the afoul calling of active calls the call context that the calling and called that include active calls identify.When control unit 702 finds out the call context of the calling and called mark comprising active calls in the call context of buffer memory, determine to there is the calling conflicted with active calls.If there are differentiation calling and called in the call context of buffer memory, be specially with the context of the afoul calling of active calls: the caller of record is the called of active calls, and the called of record is the call context of the caller of active calls.Control unit 702 has found out call context in the call context of buffer memory, it is recorded as the called identification being designated active calls of caller, and this call context is recorded as called when being designated the calling identification of active calls, determines to there is the calling conflicted with active calls.
In the embodiment shown in above-mentioned Fig. 7, control unit 702 by sending the instruction of release active calls to MSC, as call release (releasecall, RC) signaling, can carry out instruct MS C and discharges active calls.When there is not conflict calling, control unit 702 can by sending to MSC the instruction of active calls of continuing, and as (continue) message that continues, instruct MS C continues active calls.In addition, control unit 702 can to receive called party answer message that MSC reports to determine successful connection active calls, and the release event reported to receive MSC is determined in handshaking procedure, find that active calls is released.
In above-described embodiment, the buffer memory of call context is controlled by control unit 702, and determine whether there is Call Collision according to the call context of buffer memory, and determine there is Call Collision time, active calls is discharged, thus ensure that the afoul successful connection that another is called out with active calls to a certain extent, improve percept of call completed, avoid the waste of Internet resources.
Due in call establishment, there is time delay in signaling transmission, therefore, under some special screnes, also needs to be further processed.The instruction that continues of control unit 702 transmission is such as received at MSC, and by terminal A initiate call proceeding to terminal B time, terminal B does not also have enough time to discharge (having a fixed response time from being discharged into terminal recovery idle condition) to the calling that terminal A initiates, now, there will be the situation of busy, MSC can report busy event to business control device.Therefore, in order to solve this special circumstances, service processing equipment can also comprise delay unit 703 further 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, for monitoring delay duration, when arriving default delay duration, notifies control unit 702; Control unit 702 is also in the process continuing active calls, if receive busy event, then carry out time delay wait, and Time delay unit 703 starts monitoring, when receive that described delay unit sends reach the notice of default delay duration time, send to MSC the instruction of active calls of again continuing.
Optionally, in another embodiment, service processing equipment also can comprise detecting unit 704 further 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, for detecting the called state of active calls in real time, notifies control unit 702 when this called recovery idle condition being detected; Control unit 702 is also in the process continuing active calls, if receive busy event, then trigger detecting unit 704 start detection, when receiving the notice of the called recovery idle condition that detecting unit 704 sends, sends the instruction of the active calls that again continues to MSC.
By above-mentioned process, solve some unsuccessful problems that in particular cases continue, percept of call completed is obtained and further improves.And above-mentioned two kinds of modes respectively have advantage, the process of mode one, without the need to mutual with miscellaneous equipment, directly waited for, is saved Internet resources; Mode two directly can know called state, and accuracy is high.
In addition, the situation of Call Collision business of all having contracted calling and called both sides, also may there is following situation: after service processing equipment instruct MS C continues active calls, MSC according to the CAMEL-Subscription-Information of terminal called (as, T-CSI) again the message (e.g., IDP message) for triggering conflict business is sent to this service processing equipment.Now, control unit 702 is at Fig. 7, on Fig. 8 or basis embodiment illustrated in fig. 9, can further include following function: for continuing in active calls process, if receive MSC when the Initial Detection Point IDP message that test point (detectionpoint, DP) 12 is initiated, search the call context of buffer memory, determine to there is not conflict calling and the context of active calls buffer memory, instruct MS C continues the active calls that continues.When solving Call Collision in the case, need in the call context of buffer memory to distinguish calling and called.The present embodiment is also to process in particular cases, and object is further to improve percept of call completed, to save Internet resources.
In concrete application scenarios, the function of business control device can as shown in embodiment of the method Fig. 2 to Fig. 6, and wherein, mutual between business control device and MSC all can have been controlled by control unit 702.
Business control device in the embodiment of the present invention can realize based on computer system, and the method shown in Fig. 1-Fig. 6 all can realize in based on the business control device of computer system.Figure 10 shows the embodiment of the business control device realized based on computer system.In the present embodiment, business control device can comprise: processor 1001, memory 1002 and communication interface 1003.Memory 1002 is for program code stored.The program code of processor 1001 for storing in execute store 1002.In the embodiment of the present invention, memory 1002 stores the first program code, and processor 1001, for performing this first program code, comprises and performs following operation: in call establishment, obtains the calling and called mark of active calls; According to the call context of this calling and called identifier lookup buffer memory, determine whether the context of the afoul calling with active calls; If have, then indicate moving exchanging center MSC release active calls; If no, then the context of buffer memory active calls, the active calls and instruct MS C continues, when successful connection active calls or when finding that active calls is released in handshaking procedure, deletes the context of active calls; Wherein, the context of the active calls of buffer memory comprises the calling and called mark of active calls.Communication interface 1003, for external device communication, as communicated with MSC.Message (as shown in embodiment of the method Fig. 1-6) mutual between business control device and MSC is all sent by communication interface 1003 and is received.Wherein, processor 1001 processes the message that communication interface 1003 receives according to the program code in memory 1002, and mutual by communication interface 1003 and external equipment.Processor 1001 can be central processing unit (centralprocessingunit, CPU), application-specific integrated circuit (ASIC) (application-specificintegratedcircuit, ASIC) etc.Wherein, the business control device in the present embodiment can comprise bus 1104.Connect by bus 1104 between processor 1101, memory 1002 and communication interface 1103 and communicate.Wherein, memory 1002 can comprise: random access memory (randomaccessmemory, RAM), read-only memory (read-onlymemory, ROM), and disk etc. have the entity of memory function.Call context in the embodiment of the present invention can be buffered in RAM.
Wherein, if do not distinguish calling and called in the call context of buffer memory, be specially with the context of the afoul calling of active calls the call context that the calling and called that include active calls identify.Processor 1001 perform above-mentioned determine whether with active calls afoul calling contextual operate time, when being specially the call context finding out the calling and called mark comprising active calls in the call context of buffer memory, then determine to there is the calling conflicted with active calls.If there are differentiation calling and called in the call context of buffer memory, be specially with the context of the afoul calling of active calls: the caller of record is the called of active calls, and the called of record is the call context of the caller of active calls.Processor 1001 perform above-mentioned determine whether with active calls afoul calling contextual operate time, be specially the called identification being designated active calls of the caller finding out record in the call context of buffer memory, and record called is when being designated the call context of the calling identification of active calls, determine to there is the calling conflicted with active calls.
When specific implementation, transmit the problems such as time delay owing to there is signaling, therefore, under some special screnes, also need to be further processed.In the case, memory 1002 also stores the second program code, processor 1001 is also for performing this second program code, comprise and perform following operation: if in the process continuing active calls, receive busy event, carry out time delay wait, when reaching default delay duration, send the instruction of the active calls that again continues to MSC.Or, memory 1002 also stores the 3rd program code, and processor 1001, also for performing the 3rd program code, comprising and performing following operation: the called state detecting active calls in real time, when described called recovery idle condition being detected, send the instruction of the active calls that again continues to MSC.
In addition, the situation of Call Collision business of all having contracted calling and called both sides, also may there is following situation: after service processing equipment instruct MS C continues active calls, MSC according to the CAMEL-Subscription-Information of terminal called (as, T-CSI) again the message (e.g., IDP message) for triggering conflict business is sent to this service processing equipment.In the case, memory 1002 also stores the 4th program code, processor 1001 is also for performing the 4th program code, comprise and perform following operation: if continuing in active calls process, receive the Initial Detection Point IDP message that MSC initiates at test point (detectionpoint, DP) 12, the call context of buffer memory searched by processor 1001, determine not exist conflict calling and the context of active calls buffer memory time, instruct MS C continues the active calls that continues.When solving Call Collision in the case, need in the call context of buffer memory to distinguish calling and called.
The embodiment of the present invention provides the system embodiment realizing each step in said method embodiment further.Figure 11 shows a kind of embodiment processing the system of Call Collision.In this embodiment, the system processing Call Collision comprises: business control device 1101 and mobile switching centre (mobileswitchingcenter, MSC) 1102.Wherein, the concrete structure of business control device 1101 can with reference to the device embodiment part of business control device, as the business control device in Fig. 7, Fig. 8, Fig. 9 and Figure 10.The instruction of MSC then for issuing according to business control device 1101 processes active calls.If the scheme of the embodiment of the present invention is applied in intelligent network, the user that can strengthen logic based on mobile network between business control device 1101 and MSC1102 applies (customizedapplicationsformobilenetworkenhancedlogic, CAMEL) agreement and communicates.Business control device 1101 can be the SCP in intelligent network.The upper Service Switching Point (serviceswitchingpoint, SSP) disposed in intelligent network of MSC1102, MSC1102 by SSP and business control device 1101 mutual.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention can use hardware implementing, or firmware realizes, or their compound mode realizes.When implemented in software, above-mentioned functions can be stored in computer-readable medium or as the one or more instruction on computer-readable medium or code and transmit.Computer-readable medium comprises computer-readable storage medium and communication media, and wherein communication media comprises any medium being convenient to transmit computer program from a place to another place.Storage medium can be any usable medium that computer can access.Be not limited to as example: 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 carrying or storing the expectation with instruction or data structure form program code and can by any other medium of computer access.In addition.Any connection can be suitable become computer-readable medium.Such as, if software be use coaxial cable, optical fiber cable, twisted-pair feeder, Digital Subscriber Line (DSL) or such as infrared ray, radio and microwave and so on wireless technology from website, server or other remote source, so the wireless technology of coaxial cable, optical fiber cable, twisted-pair feeder, DSL or such as infrared ray, wireless and microwave and so on be included in affiliated medium fixing in.As used in the present invention, dish (Disk) and dish (disc) comprise compression laser disc (CD), laser dish, laser disc, Digital Versatile Disc (DVD), floppy disk and Blu-ray Disc, the copy data of the usual magnetic of its mid-game, dish then carrys out the copy data of optics with laser.Combination above also should be included within the protection range of computer-readable medium.
The above; be only specific embodiments of the invention, but protection scope of the present invention is not limited thereto, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; change can be expected easily or replace, 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.
Claims (9)
1. process a method for Call Collision, it is characterized in that, described method comprises:
In call establishment, business control device obtains the calling and called mark of active calls;
According to the call context of described calling and called identifier lookup buffer memory, determine whether the context of the afoul calling with active calls;
If have, then indicate moving exchanging center MSC release active calls;
If no, then the context of buffer memory active calls, and indicate described MSC to continue active calls, when successful connection active calls or when finding that active calls is released in handshaking procedure, delete the context of active calls; Wherein, the context of the active calls of described buffer memory comprises the calling and called mark of active calls; Wherein,
In the process continuing active calls, if receive busy event, described business control device carries out time delay wait, sends the instruction of the active calls that again continues when reaching default delay duration to described MSC.
2. the method for claim 1, it is characterized in that, if do not distinguish calling and called in the call context of buffer memory, describedly determine whether that the context of the afoul calling with active calls specifically comprises: determine whether to find the call context that the calling and called that include active calls identify, include the call context of the calling and called mark of active calls if find, then indicate the context of the afoul calling with active calls.
3. the method for claim 1, it is characterized in that, if there are differentiation calling and called in the call context of buffer memory, describedly determine whether that the context of the afoul calling with active calls specifically comprises: determine whether that finding caller is the called of active calls, and called be the call context of the caller of active calls, if finding caller is the called of active calls, and called be the call context of the caller of active calls, then indicate the context of the afoul calling with active calls.
4. method as claimed in claim 3, it is characterized in that, continuing in active calls process, if receive the Initial Detection Point IDP message that MSC initiates at test point DP12, business control device searches the call context of buffer memory, determine not with the context of the afoul calling of active calls, and the context of active calls buffer memory time, indicate described MSC to continue the active calls that continues.
5. a business control device, is characterized in that, comprising:
Acquiring unit, in call establishment, obtains the calling and called mark of active calls;
Control unit, for the call context of calling and called identifier lookup buffer memory obtained according to described acquiring unit, determines whether the context of the afoul calling with active calls; If have, then indicate moving exchanging center MSC release active calls; If no, then the context of buffer memory active calls, and indicate described MSC to continue active calls, when successful connection active calls or when finding that active calls is released in handshaking procedure, delete the context of active calls; Wherein, the context of the active calls of described buffer memory comprises the calling and called mark of active calls;
Described equipment also comprises: delay unit, for monitoring delay duration, when arriving default delay duration, notifies described control unit; Described control unit is also in the process continuing active calls, if receive busy event, then carry out time delay wait, and trigger described delay unit startup monitoring, when receive that described delay unit sends reach the notice of default delay duration time, send the instruction of the active calls that again continues to described MSC.
6. business control device as claimed in claim 5, is characterized in that, if do not distinguish calling and called in the call context of buffer memory, and the described call context being specially the calling and called that include active calls with the context of the afoul calling of active calls and identifying.
7. business control device as claimed in claim 5, it is characterized in that, if there are differentiation calling and called in the call context of buffer memory, describedly to be specially with the context of the afoul calling of active calls: the caller of record is the called of active calls, and record called is the call context of the caller of active calls.
8. business control device as claimed in claim 7, it is characterized in that, described control unit is also in the process continuing active calls, if receive the Initial Detection Point IDP message that described MSC initiates at monitoring point DP12, then search the call context of buffer memory, determine not with the context of the afoul calling of active calls, and the context of active calls buffer memory time, indicate described MSC to continue the active calls that continues.
9. process a system for Call Collision, it is characterized in that, comprise moving exchanging center MSC and the business control device described in any one of claim 5-8;
Described MSC, processes active calls for the instruction issued according to described business control device.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2012/079669 WO2014019226A1 (en) | 2012-08-03 | 2012-08-03 | Method, system, and service control device for processing call collision |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102893691A CN102893691A (en) | 2013-01-23 |
| CN102893691B true CN102893691B (en) | 2015-11-25 |
Family
ID=47535614
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201280001195.0A Expired - Fee Related CN102893691B (en) | 2012-08-03 | 2012-08-03 | A kind of method, system and business control device processing Call Collision |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102893691B (en) |
| WO (1) | WO2014019226A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106031294B (en) * | 2015-01-30 | 2019-06-11 | 华为技术有限公司 | A kind of processing method and terminal device of terminal device Call Collision |
| CN105991594A (en) * | 2015-02-15 | 2016-10-05 | 中兴通讯股份有限公司 | Call processing method and device |
| US11239907B2 (en) | 2015-12-07 | 2022-02-01 | Hytera Communications Corporation Limited | Call processing method and device |
| US10959278B2 (en) | 2017-02-22 | 2021-03-23 | Huawei Technologies Co., Ltd. | Call setup method and apparatus |
| US11363661B2 (en) * | 2018-03-21 | 2022-06-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and arrangements for assisting recovery of call setup failure in a wireless communication system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101155389A (en) * | 2006-09-27 | 2008-04-02 | 大唐移动通信设备有限公司 | Method and device for processing call collision |
| KR20090021509A (en) * | 2007-08-27 | 2009-03-04 | 에스케이 텔레콤주식회사 | System and method for preventing collision call in mobile communication network |
| WO2010111830A1 (en) * | 2009-03-31 | 2010-10-07 | 阿尔卡特朗讯公司 | Method and corresponding device for processing calling conflict in communication network |
-
2012
- 2012-08-03 CN CN201280001195.0A patent/CN102893691B/en not_active Expired - Fee Related
- 2012-08-03 WO PCT/CN2012/079669 patent/WO2014019226A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101155389A (en) * | 2006-09-27 | 2008-04-02 | 大唐移动通信设备有限公司 | Method and device for processing call collision |
| KR20090021509A (en) * | 2007-08-27 | 2009-03-04 | 에스케이 텔레콤주식회사 | System and method for preventing collision call in mobile communication network |
| WO2010111830A1 (en) * | 2009-03-31 | 2010-10-07 | 阿尔卡特朗讯公司 | Method and corresponding device for processing calling conflict in communication network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102893691A (en) | 2013-01-23 |
| WO2014019226A1 (en) | 2014-02-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102893691B (en) | A kind of method, system and business control device processing Call Collision | |
| US9264922B2 (en) | Method and system for ensuring service continuity in case of a proxy profile gateway failure or interruption | |
| US7349693B2 (en) | Method for implementing a call connection between a non-local calling subscriber and a local called subscriber who is an intelligent network subscriber | |
| NO320769B1 (en) | Method of activating intelligent network services in a mobile communication system, as well as mobile communication system | |
| US20130310029A1 (en) | Avoid accidental roaming by triggering a network re-attachment procedure | |
| RU2010139420A (en) | METHOD OF UPDATING INFORMATION ON THE LOCATION OF SUBSCRIBER EQUIPMENT | |
| WO2009129711A1 (en) | A call forward shifting method, device and system | |
| WO2018166328A1 (en) | Information processing method, apparatus, computer readable storage medium and electronic device | |
| US8718640B2 (en) | Method for triggering roaming retry and a home location register | |
| CN104105079A (en) | Call transfer method and device | |
| US7974611B2 (en) | Method, apparatus or software for managing a call in a telecommunications network | |
| CN105338615A (en) | UE (User Equipment) registration method, entity and system | |
| JP5313404B2 (en) | Method and system for realizing local call local switch | |
| US7924992B2 (en) | Method of ensuring call processing for intelligent user | |
| CN106998546B (en) | A kind of co-location update method, system and relevant device | |
| CA2793043C (en) | Method, short message center, home location register and system for achieving short message user roaming between networks | |
| US8660553B2 (en) | Method and system for bypassing called intelligence | |
| EP3407585B1 (en) | Generation of information based on event data of a call | |
| CN102835156B (en) | For the method for call proceeding and device thereof and system | |
| CN105682155A (en) | Method and device for identifying whether PDN (Packet Data Network) connection is influenced by PGW (Packet Data Network Gateway) fault with MME (Mobility Management Entity) | |
| CN103024712A (en) | Method and device for handling callback businesses | |
| KR100285504B1 (en) | Method for accessing between intelligent network system and intelligent peripheral | |
| CN108966291B (en) | Method and device for recovering circuit switched fallback, mobile management entity and user terminal | |
| KR100285507B1 (en) | Device of call processing for International Mobile Telecommunication-2000 Intelligent Network Services in Intelligent network Capability set 2 and method thereof | |
| US20090003262A1 (en) | Method, system and device for signaling processing in a cdma system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170718 Address after: 510640 Guangdong City, Tianhe District Province, No. five, road, public education building, unit 371-1, unit 2401 Patentee after: Guangdong Gaohang Intellectual Property Operation Co., Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Liu Zhifeng Inventor before: Zhou Wen |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170905 Address after: 053000 No. 1, Longhua village, Longhua Town, Hengshui, Hebei, Jingxian County Patentee after: Liu Zhifeng Address before: 510640 Guangdong City, Tianhe District Province, No. five, road, public education building, unit 371-1, unit 2401 Patentee before: Guangdong Gaohang Intellectual Property Operation Co., Ltd. |
|
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: 541199 Lingui County, Guilin, Lingui County, Lingui Town, Xinglin Road, No. 1, unit 202, Room 202 Patentee after: Liu Zhifeng Address before: 053000 No. 1, Longhua village, Longhua Town, Hengshui, Hebei, Jingxian County Patentee before: Liu Zhifeng |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20151125 Termination date: 20180803 |