CN102573110B - Call release method and device - Google Patents

Call release method and device Download PDF

Info

Publication number
CN102573110B
CN102573110B CN201110406416.XA CN201110406416A CN102573110B CN 102573110 B CN102573110 B CN 102573110B CN 201110406416 A CN201110406416 A CN 201110406416A CN 102573110 B CN102573110 B CN 102573110B
Authority
CN
China
Prior art keywords
call
message
network element
resource
base station
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.)
Active
Application number
CN201110406416.XA
Other languages
Chinese (zh)
Other versions
CN102573110A (en
Inventor
秦钧
王之曦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201110406416.XA priority Critical patent/CN102573110B/en
Publication of CN102573110A publication Critical patent/CN102573110A/en
Application granted granted Critical
Publication of CN102573110B publication Critical patent/CN102573110B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the invention discloses a call release method and a call release device. The method comprises the following steps of: when a network element detects that a call identifier for identifying a call is abnormal and/or the call is abnormal, releasing resources related to the call, and transmitting a signaling connection control part (SCCP) no-connection type request message to an opposite network element; and receiving an SCCP no-connection type acknowledgement message from the opposite network element, wherein the opposite network element is used for releasing the resources related to the call on an opposite network element side. According to the call release method and the call release device in the embodiment of the invention, the call identifier for identifying the call and the resources related to the call are released simultaneously, so that the call identifier can be effectively utilized, and the success rates of flows such as call switching, call distribution and the like are increased.

Description

Call release method and device
Technical field
The present invention relates to moving communicating field, relate in particular to a kind of call release method and device.
Background technology
Global system for mobile communications (Global System for Mobile communication is called for short GSM) is to carry out signal transmission based on time division multiplexing (Time Division Multiple is called for short TDM) transmission means at first.Afterwards along with Internet protocol (Internet Protocol, abbreviation IP) development of technology and universal, core net (Core Network, be called for short CN) round Realization IPization, and the A interface signaling face IP having introduced between CN and Access Network transmits SIGTRAN, as shown in Figure 1, wherein dotted line represents signaling plane (Signaling) to the Organization Chart of gsm system, and solid line represents user's face (User plane).In this framework, only remaining A interface user plane still adopts TDM mode, becomes the last obstacle of the whole network IPization.So third generation partner program (3 rdgeneration Partnership Project, is called for short 3GPP) the A interface (Ainterface over IP is called for short AoIP) based on IP transmission bearer has been proposed, the solution of A interface user plane IPization is discussed.
When A interface adopts TDM transmission means, by coaxial cable fixed link, connect CN and base station controller (Base Station Controller, be called for short BSC), each calling takies the 64kbps time slot (Timeslot) on this coaxial cable, user's face transmission of an i.e. calling must take a fixing time interval resource, therefore former agreement is used call identification code/cic circuit identification code (Call Identifier Code or Circuit Identifier Code is called for short CIC) to carry out calling of unique identification.The length of CIC cell is 2 bytes, for a coaxial cable (i.e. relaying that uses 2M bandwidth, it can be multiplexed with 32 64kbps time slots), can identify with 5 bit XXXXX the concrete time-gap number of use, with a-k totally 11 bits identify the relaying number of use: the expression way of CIC is as shown in table 1:
Table 1
After introducing AoIP, route between CN and BSC is no longer fixed link, because the timeslot number of call identification code and fixed link is corresponding no longer one by one, therefore also just possibly cannot re-use circuit identification code CIC and identify a calling, so introduced call identification (Call Identifier is called for short Call-ID), carry out identifying call letters.As (the Mobile Switching Center of mobile switching centre, be called for short MSC) or BSC lost the other side's SCCP (Signaling Connection Control Part, be called for short SCCP) during link, the Call-ID of can take synchronously discharges associated call resource as object requirement the other side.If network configuration is MSC pond A-flex (MSC in Pool), some is made mistakes because address causes calling out extremely, thereby while needing batch call release, it is especially efficient that the list of Call-ID just seems.Existing Call-ID is and 32 bit value of bearer independent that its expression way is as shown in table 2:
Table 2
Several Call-ID numerical value can also be merged and count in a Call-ID list, its expression way is as shown in table 3:
Table 3
Call-ID numerical value is calling of unique identification on MSC, BSC.When MSC supports and use the A interface of IPization, in call distribution process and handoff procedure, MSC is concrete Call-ID numerical value of call distribution, and by distribution, ask (Assignment Request) message, handover request (Handover Request) message that this Call-ID numerical value is carried to the relevant BSC of notice in Call Identifier cell, and arrive after this to call out and discharge front MSC and BSC all with this Call-ID numerical value identifying call letters.
After SCCP disconnecting between the relevant MSC of specific call and BSC, direction the other side who this interruption detected sends resetting resource (Reset Resource) message, in message, carry the Call-ID numerical value of indication specific call, notified the other side to discharge relevant resource and reference etc.; After operating successfully, return to resetting resource and reply (Reset Resource Acknowledge) message, carry the calling Call-ID list that resource successfully discharges.
Inventor, in realizing process of the present invention, finds that prior art at least exists following defect: in prior art, stipulate that Call-ID can only be distributed by MSC Server, and notify to BSC by being carried in allocation request message, handover request message.Suppose that MSC Server is according to the value of Call-ID order from small to large successively cycle assignment Call-ID, after normal a release of calling, MSC Server and BSC do not discharge in time corresponding Call-ID numerical value and take, when call out the i time (i≤232) after this calls out corresponding Call-ID numerical value distribution, must again apply for taking this Call-ID numerical value, but because the state of this Call-ID numerical value is " taking ", can cause current call distribution failure.The Call-ID value of BSC, MSC Server both sides just can not keep synchronous consistent like this, has not only caused the waste of Call-ID resource, and has reduced success rate and efficiency that call distribution, calling are switched.
Summary of the invention
The embodiment of the present invention provides a kind of call release method on the one hand, effectively solves prior art call distribution, calls out the defects such as handover success rate is low.
The embodiment of the present invention provides a kind of calling releasing device on the other hand, effectively solves prior art call distribution, calls out the defects such as handover success rate is low.
A kind of call release method providing according to the one side of the embodiment of the present invention, comprising:
When network element detects the abnormal and/or described call exception of the call identification of identifying call letters and/or receives Operation and Maintenance requirement, discharge the resource that described calling is relevant, the state of described call identification is revised as to " free time " by " taking ", send SCCP SCCP without connection type request message to opposite end network element;
Receive SCCP that described opposite end network element returns without connection type acknowledge message, wherein said opposite end network element is called out relevant resource for discharging described in the network element side of opposite end, and the state of the call identification of described identifying call letters is revised as to " free time " by " taking ".
A kind of call release method providing according to the one side of the embodiment of the present invention, comprising:
When calling out normal termination, discharge the resource that described calling is relevant, the state of call identification Call-ID corresponding to described calling is revised as to " free time " by " taking ", send clear command message to described base station controller;
Receive the removing that described base station controller returns and complete message, wherein said base station controller is called out relevant resource for discharging described side of base station controller, and the state of described call identification is revised as to " free time " by " taking ".
According to the one side of the embodiment of the present invention, also provide a kind of call release method, having comprised:
When the calling of terminal by source base station controller successful switch to target base station controller, be released to the resource of the call distribution of described terminal in source base station controller, the state of call identification corresponding to described calling is revised as to " free time " by " taking ", sends clear command message to described source base station controller;
Receive the removing that described source base station controller returns and complete message, wherein said source base station controller is called out relevant resource for discharging described source base station controller side, and the state of described call identification is revised as to " free time " by " taking ".
According to the one side of the embodiment of the present invention, also provide a kind of call release method, having comprised:
Transmission is carried the allocation request message of call identification of distribution to base station controller, when described base station controller, carries out allocation flow failure, receives the distribution failed message that described base station controller sends;
Be released to the resource of the call distribution of described base station controller, and the state of call identification corresponding to described calling is revised as to " free time " by " taking ".
According to the one side of the embodiment of the present invention, also provide a kind of call release method, having comprised:
When receiving switch failure information, be released to the resource of the call distribution of terminal in target base station controller, the state of call identification corresponding to described calling is revised as to " free time " by " taking ".
According to the one side of the embodiment of the present invention, also provide a kind of call release method, having comprised:
When receiving the removing request message of source base station controller transmission, or target base station controller is while breaking down after the switching request acknowledgement message that successfully sends of call distribution resource, be released to the resource of the call distribution of terminal in described source base station controller and target base station controller, the state of the call identification of the call identification of the calling correspondence by described terminal in source base station controller and the described terminal calling correspondence in target base station controller is revised as " free time " by " taking ", send clear command message respectively to described source base station controller and target base station controller,
Receive the removing that described source base station controller and target base station controller return respectively and complete message, wherein said source base station controller and target base station controller are respectively used to discharge calls out relevant resource separately, and the state of calling out separately corresponding call identification is revised as to " free time " by " taking ".
According to the one side of the embodiment of the present invention, also provide a kind of call identification method, it is characterized in that, having comprised:
When calling out relevant network element, all support AoIP interface function, and when described calling remains in described network element, no matter time division multiplexing tdm mode or Internet protocol IP mode are used in the current A interface user plane link of described calling, described calling only identifies with call identification numerical value.
A kind of calling releasing device providing on the other hand according to the embodiment of the present invention, comprising:
Reset message sending module, for the abnormal and/or described call exception of the call identification of identifying call letters being detected when network element and/or receiving Operation and Maintenance requirement, discharge the resource that described calling is relevant, the state of described call identification is revised as to " free time " by " taking ", sends resetting resource message to opposite end network element;
Receive responder module, for receiving the resetting resource response message that described opposite end network element returns, wherein said opposite end network element is called out relevant resource for discharging described opposite end network element side, and the state of the call identification of described identifying call letters is revised as to " free time " by " taking ".
According to the embodiment of the present invention a kind of calling releasing device is also provided on the other hand, comprising:
SCCP message transmission module, for abnormal when the call identification of identifying call letters being detected, and/or described calling is in this network element side or abnormal in opposite end network element side, and/or when receiving Operation and Maintenance requirement and need to remove all-calls, discharge the resource that described all-calls is relevant, the state of call identification corresponding to described all-calls is revised as to " free time " by " taking ", send SCCP without connection type request message to opposite end network element;
Acknowledge message receiver module, for receiving SCCP that described opposite end network element returns without connection type acknowledge message, described opposite end network element is for discharging the relevant resource of described network element side all-calls.
According to the embodiment of the present invention a kind of calling releasing device is also provided on the other hand, comprising:
Resource release module, for discharging the relevant resource of calling of end;
Status modifier module, for being revised as " free time " by the state of call identification corresponding to described calling by " taking ".
The call release method that the embodiment of the present invention provides and device, by when the relevant resource of call release, the state of calling out corresponding call identification is revised as to " free time " by " taking ", the state of the call identification of mobile switching centre and base station controller is consistent, the call identification of the identifying call letters discharging can free out the calling that identifies other in time, therefore solved the problem of call identification waste, improved call setup simultaneously and called out the success rate of switching.
Accompanying drawing explanation
Fig. 1 is prior art gsm system Organization Chart;
Fig. 2 is gsm system Organization Chart of the present invention;
Call release method embodiment mono-flow chart that Fig. 3 provides for the embodiment of the present invention;
Call release method embodiment bis-flow charts that Fig. 4 provides for the embodiment of the present invention;
Call release method embodiment tri-flow charts that Fig. 5 provides for the embodiment of the present invention;
Call release method embodiment tetra-flow charts that Fig. 6 provides for the embodiment of the present invention;
Call release method embodiment five flow charts that Fig. 7 provides for the embodiment of the present invention;
Call release method embodiment six flow charts that Fig. 8 provides for the embodiment of the present invention;
Call release method embodiment seven flow charts that Fig. 9 provides for the embodiment of the present invention;
Call release method embodiment eight flow charts that Figure 10 provides for the embodiment of the present invention;
Call release method embodiment nine flow charts that Figure 11 provides for the embodiment of the present invention;
Call release method embodiment ten flow charts that Figure 12 provides for the embodiment of the present invention;
Call release method embodiment 11 flow charts that Figure 13 provides for the embodiment of the present invention;
Calling releasing device embodiment mono-structural representation that Figure 14 provides for the embodiment of the present invention;
Calling releasing device embodiment bis-structural representations that Figure 15 provides for the embodiment of the present invention;
Calling releasing device embodiment tri-structural representations that Figure 16 provides for the embodiment of the present invention.
Embodiment
The Call-ID of the embodiment of the present invention refers to the unique identification of the specific call that A interface connects between MSC and corresponding BSC, and this Call-ID is distributed by MSC unified management.As shown in Figure 2, be gsm system Organization Chart of the present invention, the gsm system that following examples are all introduced after IP transmission based on this is comprehensively made.
As shown in Figure 3, call release method embodiment mono-flow chart providing for the embodiment of the present invention; The present embodiment comprises the following steps:
Step 101, abnormal and/or this call exception of the call identification of identifying call letters detected and/or receive Operation and Maintenance requirement when network element, discharge this and call out relevant resource, the state of call identification is revised as to " free time " by " taking ", send SCCP without connection type request message to opposite end network element;
The SCCP that step 102, reception opposite end network element return is without connection type acknowledge message, and wherein said opposite end network element is called out relevant resource for discharging this network element side, and the state of calling out relevant call identification is revised as to " free time " by " taking ".
The call release method that the embodiment of the present invention provides, by in the relevant resource of call release, the state of calling out corresponding call identification is revised as to " free time " by " taking ", the state of the call identification of mobile switching centre and base station controller is consistent, the call identification of the calling correspondence discharging can free out follow-up other the calling of sign in time, therefore solved the problem of the wasting of resources, improved call setup simultaneously and called out the success rate of switching.
As shown in Figure 4, call release method embodiment bis-flow charts that provide for the embodiment of the present invention; The present embodiment be take target BS C and is detected that Call-ID is abnormal and to discharge the calling that this Call-ID is corresponding be example, specifically comprises the following steps:
Step 201, MSC Server send handover request (Handover Request) message to BSC, carry the Call-ID1 numerical value into the call distribution under BSC in this message;
Step 202, BSC receive handover request message, obtain Call-ID1 numerical value, BSC judges whether this Call-ID1 numerical value has been distributed to other and called out, and judges whether the state of this Call-ID1 numerical value is " taking ", and judges that whether the identification means of this Call-ID1 is effective; If BSC distributed to other calling by Call-ID1 numerical value before receiving handover request message, the state of this Call-ID1 numerical value had been " taking " before BSC receives handover request message, and/or Call-ID1 identification means is invalid, handoff failure, BSC retains inner calling and the related resource originally identifying with Call-ID1 numerical value, and the switch failure information that transmission carries corresponding failure cause indicated value and/or this Call-ID1 numerical value is to MSCServer;
If this Call-ID1 numerical value has been assigned to other calling in BSC, BSC clear and definite failure cause in switch failure information is " call identification is assigned with ";
Step 203, MSC Server are according to the cause value in the Handover Failure message of receiving, know that handoff failure and Call-ID1 numerical value distribute abnormal, by the status modifier of this Call-ID1 numerical value, it is " free time ", and the related resource that discharges and call out, to BSC, send Reset Resource message, in this message, carry Call-ID1 numerical value;
Step 204, BSC receive that the state of revising Call-ID1 numerical value after Indication message is " free time ", and discharge the related resource of the calling correspondence of Call-ID1 numerical value sign, return carry Call-ID1 numerical value Reset Resource Acknowledge message to MSC Server.
Reset Resource message in the present embodiment be SCCP without the request message of connection type, ResetResource Acknowledge message is that SCCP is without the acknowledge message of connection type;
In the present embodiment, MSC Server revises the state of Call-ID1 numerical value, with discharge this network element on the relevant resource of the calling of Call-ID1 numerical value sign with send Reset Resource message and limit without sequential relationship.
As shown in Figure 5, call release method embodiment tri-flow charts that provide for the embodiment of the present invention; The present embodiment be take the Call-ID numerical value that distributes, and to be assigned with the distribution causing be unsuccessfully example, and concrete steps comprise:
Step 301, MSC Server send and distribute request (Assignment Request) message to BSC, carry MSC Server and distribute to the information such as the IP end points set up on the Call-ID1 of BSC and MGW and/or TDM termination in this message;
Step 302, BSC receives allocation request message and obtains Call-ID1, BSC judges whether this Call-ID1 numerical value has distributed to other calling, whether the state that judges this Call-ID1 numerical value is " taking ", and whether the identification means that judges this Call-ID1 is effective, if BSC distributes to other calling by this Call-Id1, the state of this Call-ID1 numerical value had been " taking " before BSC receives allocation request message, and/or identification means is invalid, distribution failure (Assignment Failure) message that transmission carries corresponding failure cause indicated value and/or this Call-ID1 is to MSC Server,
In BSC, this Call-ID1 numerical value has been distributed to other calling, and distributing clear and definite failure cause in failed message is " call identification is assigned with ";
When judging Call-ID1 numerical value, be assigned to other calling, distributed unsuccessfully, retained BSC inner originally with calling and the related resource of Call-ID1 numerical value sign, returned to Assignment Failure message;
Step 303, MSC Server are according to the cause value in the Assignment Failure message of receiving, know that call setup failure and Call-ID1 numerical value distribute abnormal, MSC Server is revised as " free time " by this Call-ID1 numeric state, and discharge and calling related resource, to BSC, send Reset Resource message, in this message, carry Call-ID1 numerical value;
Step 304, BSC receive that the state of the Call-ID1 numerical value of revising indication after Reset Resource message is " free time ", and discharge the related resource of the calling correspondence of Call-ID1 numerical value sign, return to the Reset Resource Acknowledge message of carrying this Call-ID1 numerical value;
In the present embodiment, MSC Server revises the state of Call-ID1 numerical value and discharges the resource of self and send Reset Resource message and limits without sequential.
As shown in Figure 6, call release method embodiment tetra-flow charts that provide for the embodiment of the present invention; The present embodiment receives operation maintenance command or finds significant trouble with MSC Server, and then the all-calls that need to remove same type under all-calls under this network element or this network element is example, and concrete steps comprise:
Step 401, receive operation maintenance command as MSC Server, or generation significant trouble detected, in the time of need to removing the all-calls of same type under all-calls under this network element or this network element, send SCCP without the request message of connection type each BSC to its administration; The indication of take discharges the resource of all associated call in BSC and revises these states of calling out corresponding Call-ID numerical value is " free time ";
Step 402, each BSC receive SCCP (Signaling Connection and Control Part, be called for short SCCP) without the request message of connection type, success discharges relevant each and calls out relevant resource, and the state that these are called out to corresponding Call-ID numerical value is revised as " free time " by " taking ", return SCCP without connection type confirm message to MSC Server, indicate the all-calls related resource of same type under all-calls relevant to MSC Server in this BSC or this network element and Call-ID successfully to discharge;
In the present embodiment, when BSC receives attended operation instruction or detects significant trouble, in the time of need to removing the all-calls of same type under all-calls under this network element or this network element, also can respectively send to each MSC of association a SCCP without the request message of connection type, idiographic flow is identical with step 401 and 402, and just executive agent MSC Server and BSC replace mutually.
In the present embodiment, the mutual SCCP of MSC Server and BSC has following three kinds without the expression way of the request message of connection type:
Mode A, SCCP can be resetting resource (Reset Resource) message without the request message of connection type, and the SCCP replying is that resetting resource is replied (Reset Resource Acknowledge) message without the acknowledge message of connection type; Call identification list in two message (Call Identifier List) cell need to be designated as the Call-ID (s) of the all-calls under the network element of initiating to ask, or the all-calls of same type under this network element, and there is no need Call-ID (s) to enumerate.
As shown in table 3, identification means for Call Identifier List cell, can by call identification length highest significant position (Length MSB) and call identification length least significant bit (Length LSB) all assignment be 0, and do not carry follow-up concrete " Call Identifier " indication, now Call Identifier List cell length is 3 Octet (byte), or be 0 by other indicating member indication " CallIdentifier " number, and do not carry follow-up concrete " Call Identifier " indication, now Call Identifier List cell length is 2 Octet, be expressed as and initiate all Call-ID (s) that the calling under request network element takies.For the network element of supporting AoIP function, use the method to discharge the all-calls of this network element like this, and notify opposite end network element to discharge the all-calls relevant to this network element; And for the network element of not supporting AoIP function, the A interface that only has AoTDM mode, still can continue to use Reset message request opposite end network element and discharge all all-calls (being the calling of only all AoTDM interface types) relevant with request initiation network element owing to can not identifying Reset Resource, Reset Resource Acknowledge message.
Table 3
Further, in order to improve the efficiency of call release, this mode can, for discharging the all-calls of the upper AoIP interface mode of BSC, MSC, be used existing reset (Reset), reset and confirm (Reset Acknowledge) message for the release of AoTDM interface mode all-calls.
SCCP in mode B, the embodiment of the present invention can be also that the new a pair of SCCP creating is without the message (not using existing Reset/Reset Acknowledge message, Reset Resource/Reset Resource Acknowledge message) of connection type without the request message of connection type and corresponding SCCP without the acknowledge message of connection type, be used to indicate opposite end network element reset, the all-calls of the AoIP interface mode that network element is relevant is initiated in request; For the release of AoTDM interface mode all-calls, still use existing Reset, Reset Acknowledge message.
SCCP in mode C, the embodiment of the present invention increases new indication information unit without the request message of connection type in Reset message, be used to refer to that calling that network element is relevant is initiated in all of opposite end network element reset AoIP interface mode and request and the callings that network element is relevant are initiated in all and request of AoTDM interface mode, and all relevant with the request initiation network element callings of distinguishing interface mode.Corresponding SCCP is used existing Reset Resource Acknowledge message without the acknowledge message of connection type.
The new expression way of Reset message is as follows:
INFORMATION ELEMENT Direction LEN
Message Type type of message Both 1 byte
Cause reason Both 3-4 byte
Call type type of call Both 2 bytes
The Call type cell newly increasing is for just carrying when the network element support AoIP interface function, and opposite end network element could identify Call type cell while also supporting AoIP function, and this element definitions can be as follows:
00: the all-calls of Distinguish not;
The all-calls of 01:AoTDM interface mode;
The all-calls of 10:AoIP interface mode;
11: retain (undefined).
If Reset message has been carried Call type cell, represent transmit leg network element support AoIP interface function, otherwise transmit leg network element does not carry Call type cell in Reset message, ask transmit leg to send the Reset message of not carrying Call type cell, if recipient does not support to carry the Reset message of Call type cell, with prior art recipient, discharge the all-calls relevant to transmit leg (in fact, recipient also only has the calling of AoTDM mode), if but recipient supports the Reset message of carrying Call type cell, judge that transmit leg only has the calling of AoTDM mode, discharge the all-calls relevant to transmit leg (in fact, the calling that recipient is relevant to transmit leg is all AoTDM mode).
If Reset message has been carried Call type cell, but recipient's network element can not be identified the Call type cell in Reset message, represent that recipient's network element only can support AoTDM interface mode, therefore only discharge the all-calls relevant to transmit leg of self; And the transmit leg calling relevant to recipient should be all AoTDM mode too, so two ends can keep calling out release unanimously.If recipient's network element can be identified the Call type cell in Reset message, according to the indication of Call type cell call release by type.
Only to take that the interface type of A interface user plane distinguish to call out be example to Call type cell herein, reality also can be divided type of call according to other standard, in addition along with corresponding call classification increase and decrease, the bit of Call Type indicating member also needs increase and decrease, only needs two ends network element to the understanding of type of call unanimously.
As shown in Figure 7, call release method embodiment five flow charts that provide for the embodiment of the present invention; The normal call release flow process that the present embodiment be take after the built vertical access success of terminal MS is example, and concrete steps are as follows:
Step 501, MS are sent and are torn open chain (Disconnect) message to MSC Server by BSC, request dismantling call link, and BSC is transmitted to MSC Server by the Disconnect message receiving;
Step 502, MSC Server receive after this Disconnect message, send releasing request (Release) message to BSC, and BSC is transmitted to MS by this Release message;
Step 503, MS receive after Release message, stop the timer that all-calls is controlled, discharge mobile management (Mobility Management is called for short MM) link, and by BSC, return and discharged (Release Complete) message to MSC Server;
Step 504, MSC Server also stop the timer that all-calls is controlled after receiving this Release Complete message, and discharge MM link; And discharge the relevant resource of calling of MS, as removed, on MGW, be TDM termination resource or the IP endpoint resources of this call distribution, and the state of calling out corresponding Call-ID numerical value is revised as to " free time " from " taking ", to BSC, send BSSMAP clear command (ClearCommand) message simultaneously;
After step 505, BSC receive the BSSMAP Clear Command message of MSC Server transmission, discharge and all connections of MS discharge the eating dishes without rice or wine of this calling correspondence, ground resource, the state of calling out corresponding Call-ID numerical value is revised as to " free time " from " taking ", to MSC Server, returns to BSSMAP and removed (Clear Complete) message simultaneously;
Step 506, MSC Server send and delete end-points request message to MGW;
Step 507, MGW discharge the resource for call distribution, such as TDM termination or IP end points, and return and delete end points response message to MSC Server.
MSC Server in the present embodiment step 504 sends Clear Command message to BSC, and in step 504, revises the restriction that the state of calling out corresponding Call-ID does not have sequential relationship; The resource relevant with call release, upper for calling out the TDM termination of establishment and the restriction that IP end points does not have sequential relationship yet such as deleting MGW in step 506 and 507.
The calling of the present embodiment discharges flow process also can be initiated by MSC Server, and concrete steps comprise:
Step 511, MSC Server send Disconnect message to MS by BSC, request dismantling call link, and BSC is transmitted to MS by the Disconnect message receiving;
Step 512, MS receive after this Disconnect message, send releasing request message to BSC, and BSC is transmitted to MSC Server by this Release message;
Step 513, MSC Server receive after Release message, stop the timer that all-calls is controlled, and discharge MM link, and return to Release complete to MS by BSC;
Step 514, MS also stop the timer that all-calls is controlled after receiving this Release Complete message, and discharge MM link; Then MS discharges this and calls out relevant resource, is the TDM of this call distribution or IP endpoint resources, and the state of the Call-ID numerical value that calling is taken is revised as " free time " from " taking " as discharged MGW upper;
Step 515, MSC Server send BSSMAP Clear Command message to BSC, and subsequent step is with above-mentioned steps 205-207.
As shown in Figure 8, call release method embodiment six flow charts that provide for the embodiment of the present invention; The present embodiment is to belong to after switching between the BSC of same MSC completes, and the source normal call release of BSC side is example, and for example terminal MS is conversed and used Call-ID1 numerical value to identify this calling under BSC1, and terminal MS successful switch is to target BS C2, and concrete steps comprise:
Step 601, BSC1 send handover request (Handover Required) message to MSC Server, and request is switched to the calling of MS more suitably in community;
In this handover request message, carry the speech coding RanC1 (Ran Codec, Access Network speech coding) of user MS and the current use of BSC1;
Step 602, MSC Server receive after this handover request message, from the community of recommending, selecting Yi Ge community under BSC2 is the Target cell of MS incision, to MGW, send and increase end-points request message (ADD.Req), in this message, carry vocoded information (the preferred RanC of recommendation, be called for short pRanC), carry the terminal point information of matching with BSC2, for example simultaneously, terminal point information can comprise the endpoint type that needs MGW to create, i.e. TDM termination and/or IP end points;
User MS carries out normal speech business under BSC1, and BSC1 and BSC2 belong to same MSC.When MS will be switched and be entered BSC2 by BSC1, due to MSC Server now and do not know the tenability of speech coding of BSC2 current (dynamically) and relevant A interface type, therefore, for guaranteeing fast and successful switch, before incision BSC2, on MGW, need first for BSC2 creates IP end points and/or the TDM termination matching with BSC2.
The increase end-points request message establishing that step 603, MGW basis receive and TDM termination and/or the IP end points of BSC2 pairing, and return to increase end points response message (ADD.Reply), in this message, carry the terminal point information of establishment;
Step 604, MSC Server receive increases end points response message, sends handover request message (Handover Request) to BSC2;
In this handover request message, carry MSC and be MS at the Call-ID2 of the call distribution of BSC2 numerical value, MSC Server is revised as " taking " by the state of this Call-ID2 numerical value from " free time "; (speech coding is arranged by the order of recommending in this message, also to carry MSC-PCL, the information such as the TDM termination that the speech coding that the pRanC wherein upgrading recommends for optimum), MGW side has been distributed and/or IP end points, wherein TDM termination information can comprise CIC cell, and the value of this CIC cell can be the CIC value corresponding to TDM termination of MGW establishment;
Step 605, BSC2 receive after this handover request message, can identify the Call-ID cell carrying in this message, the calling of cutting with the Call-ID2 numerical value sign of carrying in this message, is revised as " taking " by the state of this Call-I D2 numerical value from " free time "; Distribute and call out relevant resource, return to Handover Request Acknowledge (Handover Request Acknowledge) message simultaneously; Optionally, as long as BSC2 can identify the Call-ID cell carrying in handover request message, and call out and remain in BSC2, no matter TDM mode or IP mode are used in current A interface user plane link, this calling is all only by the Call-ID2 numerical value sign of carrying in this message, and No. CIC of the link of current A interface user plane or IP end points are to only representing the current physical link of this calling;
Step 606, MSC Server send switching command message (Handover Command) to BSC1, carry the type of coding RanC2 that BSC2 selects in this switching command message;
Step 607, BSC1 are forwarded to MS by this switching command message;
Step 608, MS successful switch are in the designated cell under target BS C2, and BSC2 sends and confirms that the switching of handover success completes (Handover Complete) message to MSC Server;
Step 609, MSC Server have discharged the resource of originally distributing under BSC1 for MS, as removed on MGW, be TDM termination or the IP end points of the call distribution under BSC1, and from " taking " status modifier, be " free time " state by the Call-ID1 numerical value of the calling correspondence of BSC1, to BSC1, send BSSMAP Clear Command message simultaneously;
Step 610, BSC1 receive BSSMAP Clear Command message, discharge and all connections of MS and release relevant eat dishes without rice or wine, ground resource, and the state of calling out corresponding Call-ID1 numerical value is revised as to " free time " from " taking ", to MSC Server, return to BS SMAP Clear Complete message, represent to discharge complete;
The endpoint type of carrying in the switching request acknowledgement message that step 611, MSC Server return according to BSC2 in step 305, notice MGW deletes the different end points of the type of finally selecting in BSC2 from terminal MS having created.
In the present embodiment, MSC Server sends Clear Command message to BSC1, and revises the restriction that the state of calling out corresponding Call-ID1 does not have sequential relationship; The related resource set up relevant to BSC1 with call release, such as notice MGW deletes as calling out the TDM termination of establishment and/or the restriction that IP end points does not have sequential relationship yet.
As shown in Figure 9, call release method embodiment seven flow charts that provide for the embodiment of the present invention; Calling when the present embodiment is failed with call setup is released to example and describes, and concrete steps comprise:
Step 701, BSC send layer 3 (Complete Layer3) message and, to MSC Server, in this message, carry BSC-SCL1, represent the vocoded information of the current support of BSC1, also represent that BSC1 supports IP type on A interface user plane;
Step 702, MS send Direct Transfer Application Part (Direct Transfer Application Part is called for short DTAP) Setup message and, to MSC Server, in this message, carry MS-SCL, represent the vocoded information that MS supports;
Step 703, MSC Server receive layer 3 message of BSC transmission and the Setup message that MS sends, and are call distribution resource;
Such as be this call distribution TDM termination and/or IP endpoint resources on MGW, and the state of the Call-ID numerical value for this call distribution is revised as to " taking " from " free time ", to BSC, send allocation request message (Assignment Request) message, in this message, carry MSC Server for the Call-ID numerical value of this call distribution, TDM termination information and/or the IP terminal point information of the encoding list of recommendation, MGW establishment;
Step 704, BSC receive allocation request message, optionally, as long as BSC can identify the Call-ID cell carrying in allocation request message, and call out and remain in BSC, no matter TDM mode or IP mode are used in current A interface user plane link, this calling is all only by the Call-ID numerical value sign of carrying in this message, and No. CIC of the link of current A interface user plane or IP end points are to only representing the current physical link of this calling; But BSC carries out allocation flow failure, the Call-ID numerical value that BSC maintenance distributes is " free time " state, to MSC Server, returns and distributes unsuccessfully (Assignment Failure) message;
Step 705, MSC Server receive distribution failed message, discharging is originally that MS is in the resource of the call distribution of BSC, as discharged on MGW, be the TDM termination resource of call distribution and/or IP endpoint resources, the state of the Call-ID numerical value for call distribution is revised as to " free time " from " taking ".
In the present embodiment, MSC Server sends Clear Command message to BSC, and revises the restriction that the state of calling out corresponding Call-ID does not have sequential relationship; The resource relevant with call release, such as notice MGW deletes as calling out the TDM termination of establishment and the restriction that IP end points does not have sequential relationship yet.
As shown in figure 10, call release method embodiment eight flow charts that provide for the embodiment of the present invention; The present embodiment be take and belonged under same MSC the switching between BSC due to the incision of target BS C call not accepted and be unsuccessfully example, wherein source BSC is designated as BSC1, and target BS C is designated as BSC2, and terminal MS is normal talking under BSC1, and with Call-ID1 numerical value, be identified at the calling of BSC1, concrete steps comprise:
Step 801, BSC1 send handover request (Handover Required) message to MSC Server, carry the speech coding RanC1 (Ran Codec, Access Network speech coding) of MS and the current use of BSC1 in this handover request message; Request is switched to the calling of MS more suitably in community;
The information that step 802, MSC report according to BSC1, from the community of recommending, selecting Yi Ge community under BSC2 is the Target cell of MS incision, for BSC2 distributes after related resource success, such as create TDM termination and the IP end points of pairing for BSC2 on MGW; Send handover request (Handover Request) message to BSC2, in this message, carry the Call-ID2 numerical value into the call distribution under BSC2, the state that is about to this Call-ID2 numerical value is revised as " taking " from " free time ", also carries the encoding list of recommendation, the TDM termination information of establishment and IP terminal point information in this message;
The calling that step 803, BSC2 cut with this Call-ID2 numerical value sign, but due to Resources allocation failure or Call-ID2 numerical value, in BSC2, distributed to the reasons such as other call instance (state that is Call-ID2 numerical value is " taking ") and caused handoff failure, BSC2 keeps the state of Call-ID2 numerical value constant, return carry concrete failure reason value handoff failure (Handover Failure) message to MSC Server;
Step 804, MSC Server receive switch failure information, be released to the resources such as end points that BSC2 distributes, the state of the Call-ID2 numerical value distributing for BSC2 is revised back to " free time " from " taking ", alternatively, to BSC1, send handover request refusal (Handover Required Reject) message simultaneously indicate this handoff failure;
Then BSC1 reservation MS is constant with the calling of Call-ID1 numerical value sign.
In the present embodiment, MSC Server sends Clear Command message to BSC2, and revises the restriction that the state of calling out corresponding Call-ID2 does not have sequential relationship; Upper for calling out the related resource of incision BSC2 foundation with release MGW, such as notice MGW deletes as calling out the TDM termination of establishment and the restriction that IP end points does not have sequential relationship yet.
As shown in figure 11, call release method embodiment nine flow charts that provide for the embodiment of the present invention; The present embodiment be take and belonged under same MSC the switching between BSC because source BSC reports handoff failure as example, wherein source BSC is designated as BSC1, and target BS C is designated as BSC2, and terminal MS is normal talking under BSC1, and with Call-ID1 numerical value, be identified at the calling of BSC1, concrete steps comprise:
Step 901, BSC1 send handover request (Handover Required) message to MSC Server, carry the speech coding RanC1 (Ran Codec, Access Network speech coding) of user MS and the current use of BSC1 in this handover request message; Request is switched to the calling of MS more suitably in community;
Step 902, MSC Server according to BSC1 by the information of handover request information reporting, from the community of recommending, selecting Yi Ge community under BSC2 is the Target cell of MS incision, for BSC2 distributes after related resource success, such as create TDM termination and the IP end points of pairing for BSC2 on MGW; To BSC2, send handover request (Handover Request) message, in this message, carry the Call-ID2 numerical value into the call distribution under BSC2, the state of this Call-ID2 numerical value is revised as to " taking " from " free time ", in message, also carry the encoding list of recommendation, the information such as the TDM termination information of establishment and IP end points;
The calling that step 903, BSC2 cut with this Call-ID2 numerical value sign, the state that is about to this Call-ID2 numerical value is revised as " taking " from " free time ", and Resources allocation, returns to Handover Request Acknowledge (Handover Request Acknowledge) message;
Step 904, MSC Server send switching command (Handover Command) message instruct MS by BSC1 to MS and are switched to the designated cell under target BS C2;
Step 905, MS carry out switching after receiving this switching command, but handoff failure sends handoff failure (Handover Failure) message to BSC1;
Step 906, BSC1 keep calling corresponding to Call-ID1 numerical value, send handoff failure (Handover Failure) message to MSC Server simultaneously;
Step 907, MSC Server receive switch failure information, notice MGW is released to the resource of BSC2 distribution as the TDM termination resource and the IP endpoint resources that create, and the state of Call-ID2 numerical value is revised back to " free time " from " taking ", to BSC2, send Clear Command message;
Step 908, BSC2 receive Clear Command message, be released to that all that the calling of MS prepares are eated dishes without rice or wine, ground resource, and the state of the Call-ID2 numerical value that calling is taken is revised as " free time " from " taking ", to MSC Server, return to Clear Complete message.
In the present embodiment, MSC Server sends Clear Command message to BSC2, and revises the restriction that the state of calling out corresponding Call-ID2 does not have sequential relationship; With the relevant resource that is released to calling incision BSC2 foundation on notice MGW, such as notice MGW deletes, be to call out the TDM termination of establishment and the restriction that I P end points does not have sequential relationship yet.
As shown in figure 12, call release method embodiment ten flow charts that provide for the embodiment of the present invention; The present embodiment take that to belong to the switching between BSC under same MSC be unsuccessfully example because source BSC asks call release in handoff procedure, wherein source BSC is designated as BSC1, target BS C is designated as BSC2, terminal MS is normal talking under BSC1, and with Call-ID1 numerical value, be identified at the calling of BSC1, concrete steps comprise:
Step 1001, BSC1 send handover request (Handover Required) message to MSC Server, and request is switched to the calling of MS more suitably in community;
Step 1002, MSC Server according to BSC1 by the information of handover request information reporting, from the community of recommending, selecting Yi Ge community under BSC2 is the Target cell of MS incision, for BSC2 distributes related resource, to BSC2, send handover request (Handover Request) message, in this message, carry the Call-ID2 numerical value into the call distribution under BSC2, the state of this Call-ID2 numerical value is revised as to " taking " from " free time ", this message is also carried the encoding list of recommendation, the information such as the TDM termination information of establishment and IP end points;
Step 1003, BSC2 receive handover request message, calling with this Call-ID2 numerical value sign incision, the state that is about to this Call-ID2 numerical value is revised as " taking " from " free time ", and Resources allocation, returns to Handover Request Acknowledge (Handover Request Acknowledge) message;
Step 1004, MSC Server send switching command (Handover Command) message by BSC1 to MS, and instruct MS is switched to the designated cell under target BS C2;
Step 1005, MS carry out switching after receiving this switching command, but BSC1 sends Clear Request message to MSC Server for some reason in the process of implementation, such as BSC1 does not still receive handoff failure (Handover Failure) message that MS reports after T8 timer expiry, BSC1 sends Clear Request message to MSC Server, and now BSC1 also needs to retain Call-ID1 and is the related resource of call distribution;
Step 1006, MSC Server receive after Clear Request request message, judge calling and can not continue; MSC Server is released to all resources that MS distributes, and the state of Call-ID1 numerical value and Call-ID2 numerical value is revised as to " free time " from " taking "; MSC Server sends respectively Clear Command message to BSC1 and BSC2;
Step 1007, BSC1 and BSC2 receive Clear Command message, be released to all resources that MS prepares, and respectively by calling out corresponding Call-ID1 numerical value, the state of Call-ID2 numerical value is revised as " free time " from " taking ", BSC1 and BSC2 return to Clear Complete message to MSC Server.
In the present embodiment, MSC Server sends Clear Command message to BSC1, BSC2, and revises the restriction that the state of calling out corresponding Call-ID1, Call-ID2 does not have sequential relationship; Upper for calling out the related resource of incision BSC2 foundation with release MGW, such as notice MGW deletes as calling out the TDM termination of establishment and the restriction that IP end points does not have sequential relationship yet.
As shown in figure 13, call release method embodiment 11 flow charts that provide for the embodiment of the present invention; The present embodiment be take and belonged under same MSC the switching between BSC in handoff procedure, to occur be example extremely and unsuccessfully due to MSC Server, source BSC is wherein designated as BSC1, target BS C is designated as BSC2, terminal MS is normal talking under BSC1, and with Call-ID1 numerical value, be identified at the calling of BSC1, concrete steps comprise:
Step 1101, BSC1 send handover request (Handover Required) message to MSC Server, and request is switched to the calling of MS more suitably in community;
Step 1102, MSC Server according to BSC1 by the information of handover request information reporting, from the community of recommending, selecting Yi Ge community under BSC2 is the Target cell of MS incision, for BSC2 distributes after related resource success, to BSC2, send handover request (Handover Request) message, in this message, carry the Call-ID2 numerical value into the call distribution under BSC2, the state of this Call-ID2 numerical value is revised as to " taking " from " free time ", this message is also carried the encoding list of recommendation, the TDM termination information of establishment and IP terminal point information;
Step 1103, BSC2 receive handover request message, calling with the incision of Call-ID2 numerical value sign, the state that is about to this Call-ID2 numerical value is revised as " taking " from " free time ", and Resources allocation, returns to Handover Request Acknowledge (Handover Request Acknowledge) message;
Step 1104, MSC Server send switching command (Handover Command) message instruct MS by BSC1 to MS and are switched to the designated cell under BSC2;
Or MSC Server is before sending Handover Command message, MSC Server just finds to break down, thereby need to be released to all resources that MS distributes, the state of Call-ID1 numerical value and Call-ID2 numerical value is revised as to " free time " from " taking "; MSC Server sends Clear Command message to BSC1 and BSC2 respectively;
Step 1105, BSC1 and BSC2 are released to all resources that MS prepares, respectively by calling out corresponding Call-ID1 numerical value, the state of Call-ID2 numerical value is revised as " free time " from " taking ", BSC1 and BSC2 return to Clear Complete message to MSC Server.
In the present embodiment, MSC Server sends Clear Command message to BSC1, BSC2, and revises the restriction that the state of calling out corresponding Call-ID1, Call-ID2 does not have sequential relationship; The resource relevant with call release, deletes MGW above for calling out the TDM termination of establishment and the restriction that IP end points does not have sequential relationship yet such as notifying.
As shown in figure 14, be calling releasing device embodiment mono-structural representation that the embodiment of the present invention provides, the present embodiment comprises:
Resource release module 1 and status modifier module 2, wherein resource release module 1 is for discharging the relevant resource of calling of end; Status modifier module 2, for being revised as " free time " by the state of call identification corresponding to described calling by " taking ".
The present embodiment also comprises the first receiver module 3, in call distribution flow process, receives the distribution failed message that base station controller sends; Or in calling out switching flow, receiving target base station controller is called out the switch failure information of carrying failure reason value sending after handoff failure; Or in calling out switching flow, reception sources base station controller is called out the switch failure information of carrying failure reason value sending after handoff failure; Or in calling out switching flow, the removing request message that reception sources base station controller sends.Clear command sending module 4, for revising the state of call identification, sends clear command message to base station controller.
The present embodiment also comprises the second receiver module 5, for receiving base station controller, discharges the resource that described calling is relevant, the state of call identification is revised as to " free time " simultaneously by " taking " or the removing returned afterwards completes message.
As shown in figure 15, calling releasing device embodiment bis-structural representations that provide for the embodiment of the present invention, the present embodiment comprises: reset message sending module 6 and reception responder module 7, wherein reset message sending module 6 is for when the abnormal and/or described call exception of the call identification of identifying call letters being detected and/or receiving Operation and Maintenance requirement, discharge the resource that described calling is relevant, the state of call identification is revised as to " free time " by " taking ", sends resetting resource message to opposite end network element; Receive responder module 7 and discharge for receiving described opposite end network element the resource that described calling is relevant, the state of the call identification of described identifying call letters is revised as to " free time " simultaneously or the resetting resource response message of returning afterwards by " taking ".
The reset message sending module 6 of the present embodiment specifically comprises: detecting unit, whether the call identification for detection of identifying call letters is abnormal, and/or whether this calling is abnormal in this network element side, and/or whether this calling is abnormal in opposite end network element side, whether receives Operation and Maintenance request; Releasing unit, calls out relevant resource for discharging this, and the state of call identification is revised as to " free time " by " taking "; Transmitting element, for sending resetting resource message to opposite end network element.Releasing unit is specifically for abnormal when the call identification of identifying call letters being detected, and/or this calls out in this network element side or abnormal in opposite end network element side, and/or while receiving Operation and Maintenance requirement, discharges this and call out relevant resource.
As shown in figure 16, calling releasing device embodiment tri-structural representations that provide for the embodiment of the present invention, the present embodiment comprises: SCCP message transmission module 8 and acknowledge message receiver module 9, wherein SCCP message transmission module 8 is for when needs are removed all-calls, discharge the resource that this all-calls is relevant, the state of call identification corresponding to all-calls is revised as to " free time " by " taking ", send SCCP without connection type request message to opposite end network element; Acknowledge message receiver module 9, for receiving, network element successfully discharges the resource while that all-calls is relevant or afterwards, the SCCP returning is without connection type acknowledge message.The concrete resetting resource message that carries type of call cell that sends of SCCP message transmission module 7.
Finally it should be noted that: above embodiment is only in order to technical scheme of the present invention to be described but not be limited, although the present invention is had been described in detail with reference to preferred embodiment, those of ordinary skill in the art is to be understood that: it still can be modified or be equal to replacement technical scheme of the present invention, and these modifications or be equal to replacement and also can not make amended technical scheme depart from the spirit and scope of technical solution of the present invention.

Claims (13)

1. a call release method, it is characterized in that, comprise: when network element detects the abnormal and/or described call exception of the call identification of identifying call letters, discharge the resource that described calling is relevant, send SCCP SCCP without connection type request message to opposite end network element;
Receive SCCP that described opposite end network element returns without connection type acknowledge message, wherein said opposite end network element is called out relevant resource for discharging described in the network element side of described opposite end;
Wherein, when described network element is supported A interface (AoIP) function of internet protocol-based transmission bearer, described transmission SCCP comprises without connection type request message: send the reset message that carries type of call cell;
Described network element is mobile switching centre, and described opposite end network element is the base station controller associated with described mobile switching centre, or described network element is base station controller, and described opposite end network element is the mobile switching centre associated with described base station controller.
2. method according to claim 1, is characterized in that, the resource that the described calling of described release is relevant comprises:
Discharge the relevant resource of all-calls of same type.
3. method according to claim 2, the relevant resource of all-calls of described release same type comprises:
Discharge the relevant resource of all-calls of AoIP interface mode.
4. according to the call release method described in claim 1-3 any one, it is characterized in that, described network element detects described call exception, comprising:
Described network element receives the notification message that the call identification of described identifying call letters has been assigned with at opposite end network element.
5. a base station controller, is characterized in that, described base station controller is used for:
When the abnormal and/or described call exception of the call identification of identifying call letters being detected, discharge the resource that described calling is relevant, when described base station controller is supported the A interface function of internet protocol-based transmission bearer, transmission carries the reset message of type of call cell to the mobile switching centre with described base station controller pairing;
Receive SCCP SCCP that described mobile switching centre returns without connection type request message SCCP without connection type acknowledge message, relevant resource is called out for discharging described in described mobile switching centre side by wherein said mobile switching centre.
6. base station controller according to claim 5, is characterized in that, described base station controller discharges the relevant resource of all-calls of AoIP interface mode.
7.Yi Zhong mobile switching centre, is characterized in that, described mobile switching centre is used for:
When the abnormal and/or described call exception of the call identification of identifying call letters being detected, discharge the resource that described calling is relevant, when described mobile switching centre supports the A interface function of internet protocol-based transmission bearer, transmission carries the reset message of type of call cell to the base station controller with the pairing of described mobile switching centre;
Receive SCCP SCCP that described base station controller returns without connection type request message SCCP without connection type acknowledge message, wherein said base station controller is called out relevant resource for discharging described in described side of base station controller.
8. mobile switching centre according to claim 7, is characterized in that, described mobile switching centre discharges the relevant resource of all-calls of AoIP interface mode.
9. a call release method, it is characterized in that, comprise: when network element detects the abnormal and/or described call exception of the call identification of identifying call letters, discharge the resource that described calling is relevant, send SCCP SCCP without connection type request message to opposite end network element;
Receive SCCP that described opposite end network element returns without connection type acknowledge message, wherein said opposite end network element is called out relevant resource for discharging described in the network element side of described opposite end; Wherein, described SCCP is the resetting resource message of carrying call identification without connection type request message, and described SCCP is the resetting resource response message of carrying call identification without connection type acknowledge message;
Described network element is mobile switching centre, and described opposite end network element is the base station controller associated with described mobile switching centre, or described network element is base station controller, and described opposite end network element is the mobile switching centre associated with described base station controller.
10. call release method according to claim 9, is characterized in that, described in described call exception detected and specifically comprise:
Described calling detected abnormal in described network element side, and/or receive the notification message of the call exception of described opposite end network element.
11. call release methods according to claim 10, is characterized in that, described in receive the notification message of the call exception of described opposite end network element, comprising: receive the notification message that the call identification of described identifying call letters has been assigned with at opposite end network element.
12. 1 kinds of base station controllers, is characterized in that, described base station controller is used for:
When the abnormal and/or described call exception of the call identification of identifying call letters being detected, discharge the resource that described calling is relevant, send resetting resource message to the mobile switching centre with described base station controller pairing;
Receive the resetting resource response message that described mobile switching centre returns, relevant resource is called out for discharging described mobile switching centre side by wherein said mobile switching centre.
13.Yi Zhong mobile switching centre, is characterized in that, described mobile switching centre is used for:
When the abnormal and/or described call exception of the call identification of identifying call letters being detected, discharge the resource that described calling is relevant, send resetting resource message to the base station controller with the pairing of described mobile switching centre;
Receive the resetting resource response message that described base station controller returns, wherein said base station controller is called out relevant resource for discharging described side of base station controller.
CN201110406416.XA 2008-08-14 2008-08-14 Call release method and device Active CN102573110B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201110406416.XA CN102573110B (en) 2008-08-14 2008-08-14 Call release method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110406416.XA CN102573110B (en) 2008-08-14 2008-08-14 Call release method and device

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN2008101183659A Division CN101651889B (en) 2008-08-14 2008-08-14 Call release method and device

Publications (2)

Publication Number Publication Date
CN102573110A CN102573110A (en) 2012-07-11
CN102573110B true CN102573110B (en) 2014-11-05

Family

ID=46417259

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110406416.XA Active CN102573110B (en) 2008-08-14 2008-08-14 Call release method and device

Country Status (1)

Country Link
CN (1) CN102573110B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1283049A (en) * 1999-09-18 2001-02-07 深圳市中兴通讯股份有限公司 Method for reducting message loss rate by call protection
CN101102613A (en) * 2007-08-03 2008-01-09 中兴通讯股份有限公司 An implementation method for final call in IP multimedia subsystem centrally controlled service

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1283049A (en) * 1999-09-18 2001-02-07 深圳市中兴通讯股份有限公司 Method for reducting message loss rate by call protection
CN101102613A (en) * 2007-08-03 2008-01-09 中兴通讯股份有限公司 An implementation method for final call in IP multimedia subsystem centrally controlled service

Also Published As

Publication number Publication date
CN102573110A (en) 2012-07-11

Similar Documents

Publication Publication Date Title
CN100471323C (en) Method for acquiring system information as switching residence
CN104937963A (en) Method and device for group communication, having robust mobility
CN102421152B (en) Method and device for identifying bearing type
CN101925042A (en) Method and system for controlling tunnel identifier allocation and devices
CN102223669B (en) It creates data inverse-transmitting channel and distributes the method and system of Internet protocol
CN102123460A (en) Method for realizing group calling service handover in trunked mobile communication system
CN101009940A (en) Handover method for minimizing packet call reconnection delay time and multi-mode terminal for the same
CN101971692A (en) Assignment and handover in a radio communication network
CN101651889B (en) Call release method and device
KR20140104494A (en) Methods and apparatus for controlling circuit switched fall back of a mobile station from e-utran to utran/geran in a full-multi-operator core network
CN101925146B (en) Method for realizing load balance of voice service, user terminal and base station
CN101431740A (en) Method and apparatus for call handover in a telecommunications system
KR101012004B1 (en) Apparatus and method for saving resource between core network and base station controller in a mobile communication system
CN109802982B (en) Dual-connection implementation method, device and system
JP5313404B2 (en) Method and system for realizing local call local switch
CN102577576A (en) Local switching
CN101754326A (en) Paging method, device and system
EP2448362B1 (en) Release processing method for connection resources and apparatus thereof
CN102573110B (en) Call release method and device
CN102282888B (en) Method, apparatus and system for call handover and process
CN102045794B (en) Call switching method between base station systems and mobile communication system
EP2320697B1 (en) Method for switching msc-pool inter offices
CN102388655B (en) Base station controller (BSC), mobile switching center (MSC) and switch method for calling mode
CN102395124B (en) Call switching method, call establishment method, call switching device and call establishment device
WO2023120174A1 (en) Base station, network node, first core network node, second core network node, and methods performed by them

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
EE01 Entry into force of recordation of patent licensing contract

Application publication date: 20120711

Assignee: Apple Computer, Inc.

Assignor: Huawei Technologies Co., Ltd.

Contract record no.: 2015990000755

Denomination of invention: Call release method and device

Granted publication date: 20141105

License type: Common License

Record date: 20150827

LICC Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model