CN100428825C - Method for recovering service data when service rearrangement / rollback in system of dual attributes - Google Patents
Method for recovering service data when service rearrangement / rollback in system of dual attributes Download PDFInfo
- Publication number
- CN100428825C CN100428825C CNB2006100084892A CN200610008489A CN100428825C CN 100428825 C CN100428825 C CN 100428825C CN B2006100084892 A CNB2006100084892 A CN B2006100084892A CN 200610008489 A CN200610008489 A CN 200610008489A CN 100428825 C CN100428825 C CN 100428825C
- Authority
- CN
- China
- Prior art keywords
- information
- call
- additional information
- message
- context
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000009977 dual effect Effects 0.000 title description 5
- 230000008707 rearrangement Effects 0.000 title 1
- 230000011664 signaling Effects 0.000 claims description 43
- 238000010295 mobile communication Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 abstract description 12
- 238000012545 processing Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 8
- 230000004044 response Effects 0.000 description 8
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 101100346892 Arabidopsis thaliana MTPA1 gene Proteins 0.000 description 2
- 101150069989 MTP2 gene Proteins 0.000 description 2
- 101100098774 Rattus norvegicus Tap2 gene Proteins 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 239000004744 fabric Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 101100346893 Arabidopsis thaliana MTPA2 gene Proteins 0.000 description 1
- 101150006417 MTP3 gene Proteins 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention relates to a method for restoring service data when the service is reversed / returned in a double attribution system, which aims to solve the problem that a steady-state call which is established can not be maintained normally when the service is reversed / returned in the prior art. The present invention has the scheme: in the process of calling, when a soft switch center sends a load bearing operation to a media gateway which is registered to the soft switch center, a corresponding additional message is sent additionally; except for the normal load-bearing operation, the media gateway is also used for storing the received additional message; after the service is reversed / returned to cause the media gateway to be registered to another soft switch center again, a call message including the additional message is reported; the other soft switch center judges whether the current call is a steady-state call or not and carries out the corresponding processing according to the received call message including the additional message, and thereby, the established steady-state call can be maintained normally, and for an unsteady-state call, the MGW and the noumenal resources of an opposite terminal can be released to prevent the resources from being locked.
Description
Technical Field
The present invention relates to a service switching or service rewinding processing technology in a dual-homing system in a mobile communication network, and more particularly, to a method for recovering service data during service switching/rewinding in a dual-homing system.
Background
With the continuous development of mobile communication technology, a structure of separating bearer and control is introduced into the circuit domain core network of WCDMA and CDMA2000 networks, that is, the original Mobile Switching Center (MSC) is divided into two devices, namely a mobile soft switching center (MSCe) and a Media Gateway (MGW). For convenience of description, the network and convention of CDMA2000 are used for description, but the scheme of the present invention is not limited to CDMA2000, and is also applicable to WCDMA and fixed networks.
As shown in fig. 1, the term "dual homing" in the present invention means that one MGW can be connected to two msces, i.e. subordinate to two msces. The two MSCe can work in a main-standby mode: under the normal operation condition, the MGW can only be registered to one of the MSCe; when the MSCe fails, the MGW can register to another MSCe, and the latter MSCe continues to provide service for the resources managed by the MGW.
As can be seen from fig. 1, normally MGW1 is assigned to MSCe1 and MGW2 is assigned to MSCe 2. After the configuration of dual homing, the spare MSCe of MGW1 is MSCe2, and the spare MSCe of MGW2 is MSCe 1. Thus, MSCe1 is configured with MGW2 resources in addition to MGW1 resources, and MSCe1 does not normally use MGW2 resources. Except for configuring the resources of the MGW2, the MSCe2 is also configured with the resources of the MGW1, and the MGW1 is not normally used by the MSCe 2. In normal operation, MGW1 is registered on MSCe1, MGW2 is registered on MSCe2, signaling forwarded via MGW1 is sent to its registered MSCe1, and signaling forwarded via MGW2 is sent to its registered MSCe 2. The BSC in fig. 1 is a base station controller.
When the MSCe1 is disabled for some reason, the MGW attributed to it registers to the MSCe 2; at the same time, MSCe2 will detect the heartbeat interrupt and activate the relevant resource and take over the work of the main MSCe 1. The heartbeat is usually called as heartbeat detection, that is, the local terminal sends a heartbeat message to the opposite terminal entity at regular time, and the opposite terminal returns a heartbeat response message after receiving the heartbeat message; if the local terminal can not receive the heartbeat response message of the opposite terminal within a period of time, the opposite terminal is considered to be in an abnormal state. When the failed MSCe1 returns to normal, the MGW1 attributed to it re-registers with MSCe1, and the MSCe2 detects the heartbeat recovery and terminates the operation of taking over the main MSCe 1. In the above process, relative to MGW1, MSCe1 is the main and MSCe2 is the standby. If MSCe2 failure occurs, relative to MGW2, MSCe2 is the main and MSCe1 is the backup
For the process that the standby MSCe takes over the work when the main MSCe is invalid, the process is called as service switching; the process of recovering the normal takeover operation for the primary MSCe is called service rewinding. In the service switching and service rewinding process in the prior art, the following main problems exist: (1) the MSCe for taking over work (for service switching, the standby MSCe is used for taking over work; for service switching, the main MSCe is used for taking over work) has no bearing information of the established call on the MGW; (2) the MSCe taking over the work has no established signaling connection relation between the call and other entities; (3) there is no subscriber information and other call information for the established call on the working MSCe to take over. The above defects can cause the problems that the subsequent signaling can not be processed normally, the bearing operation can not be carried out normally, the call ticket is lost and the like.
Taking the a-port message as an example, for the traditional circuit domain structure, the signaling between the MSC and the BSC is carried on the signaling No. 7, and the a-port signaling protocol stack is shown in fig. 2. Wherein, MTP is Message Transfer Part (Message Transfer Part), SCCP is signaling connection control Part (signaling connection control Part), and the a port protocol is carried on SCCP.
After the soft switch structure is adopted, the control and the bearing are separated, the MSC is divided into two parts, namely a soft switch MSCe and a media gateway MGW, the signaling Protocol stack of the port a at this time is as shown in fig. 3 (Protocol stacks of other forms can be used, but the Protocol stack is generally adopted for dual homing), as can be seen from the figure, the signaling of No. 7 of the circuit domain is between the MGW and the BSC, and the signaling between the MGW and the MSCe is borne on the IP (Internet Protocol). Wherein M2UA is MTP2 User adaptation layer (SS7 MTP2-User adaptation layer) for providing primitive communication service for MTP3 in IP network and MTP2 at network edge; SCTP is a Stream Control Transport Protocol (Stream Control Transport Protocol). The M2UA approach is equivalent to establishing an IP channel through which MSCe uses the link on the MGW as if it were using the home link.
For the port a protocol, the normal SCCP connection establishment procedure is shown in fig. 4.
(1) After receiving the service request of the upper layer service, the SCCP a allocates its connection reference, records the connection information of the upper layer service, and initiates a connection establishment request (CR) with the connection reference of the a-side to the opposite side (i.e., SCCP B).
(2) After receiving the connection establishment request, the B terminal distributes own connection reference, records the connection reference of the A terminal and sends data to an upper layer service; after receiving the confirmation message of the upper layer service, recording the connection information of the upper layer service, and sending a Connection Confirmation (CC) to the A end, wherein the confirmation contains a B end connection reference and an A end connection reference.
(3) A, B both know the connection reference of the local terminal and the connection reference of the opposite terminal, the connection establishment is completed.
(4) When the follow-up upper layer service needs to send data, a message is sent to the SCCP, wherein the SCCP connection information is contained; SCCP sends message to opposite terminal, which has connection reference of opposite terminal; and after receiving the message, the opposite terminal finds the data record of the local terminal according to the connection reference in the message and sends the data to the upper-layer service module.
When service switching occurs, so that the standby MSCe takes over the work, if there is no signaling connection information, for the subsequent call information from the BSC, the signaling cannot be processed because the corresponding connection reference cannot be found, and finally abnormal disconnection is performed.
Taking the relay side as an example, in the conventional technology, the MSC and the PSTN generally use ISUP or TUP for interfacing. Here, TUP is taken as an example for explanation, and ISUP is similar thereto. The TUP signaling is carried on MTP with the protocol stack as shown in fig. 5. After the soft switch is used, the protocol stack is shown in fig. 6.
When TUP relay call is carried out, a TDM circuit is occupied to carry telephone traffic, the circuit is marked by a unique circuit identification CIC between two entities, and meanwhile, the signaling between the two entities is connected by the CIC. When a call is initiated, a circuit is occupied, a service table number is recorded in a circuit table corresponding to the CIC, and an IAM message with the CIC is sent to an opposite terminal; and after receiving the IAM message, the opposite end occupies a circuit corresponding to the CIC, allocates the service processing table and records the number of the service processing table in the circuit table corresponding to the CIC. The subsequent call messages are also provided with CIC, and the call processing can be normally carried out through the service connection table recorded in the corresponding circuit table.
When service switching occurs, so that the standby MSCe takes over the work, if there is no signaling connection information, for the TUP subsequent call information from the opposite end entity, abnormal call disconnection may be caused because the corresponding service connection table cannot be found or an erroneous service connection table is found.
In order to solve the above technical problem, the solution of the prior art is to make the call information backup between the main MSCe and the standby MSCe in real time. The disadvantage is that the backup data volume is very large and the implementation cost is very high.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to solve the problems that when service switching/rewinding occurs, the established steady-state call cannot be normally maintained, the subsequent call signaling cannot be correctly processed, and the cost is high due to a method for real-time backup between a main soft switch center and a standby soft switch center in the prior art.
The technical scheme adopted by the invention for solving the technical problems is as follows: a method for recovering service data when service switching/rewinding in a dual-homing system is provided, which comprises the following steps:
(S1) during the call, when the soft switch center sends a bearer operation command to its registered media gateway, it adds and sends corresponding additional information;
(S2) the media gateway performs a bearer operation and saves the additional information it received;
(S3) when the service switching/rewinding occurs, the media gateway re-registers to another soft switch center and reports the call information with the additional information;
(S4) the other soft switch center determines whether the current call is a steady state call according to the received call information containing the additional information, and if so, recovers the corresponding bearer information, signaling connection information and user information according to the call information containing the additional information.
In step (S4) of the method of the present invention, if the current call is determined to be an unsteady call, the softswitch center sends a bearer release message to the media gateway and sends a disconnect message to the correspondent entity.
In the step (S4) of the method of the present invention, for a steady call, the ticket information is also recovered.
In the method of the present invention, the additional information may include signaling connection information and user information for a mobile communication system; the call information reported in the step (S3) includes: context, additional information of Context, Termination, and additional information of Termination; in the step (S4), the another softswitch center determines whether the current call is a steady-state call according to a steady-state flag in the additional information of the Context.
In step (S4) of the method of the present invention, if it is determined that the current call is a steady state call, then:
recovering bearing information according to the Context and Termination;
restoring the signaling connection information with other entities according to the Termination additional information;
and recovering the user information and the ticket information according to the additional information of the Context and the additional information of Termination.
In the step (S3) of the method of the present invention, a flow control manner is adopted to report the call information. The flow control mode can be reporting according to a fixed Context number in unit time until all Context information is reported; or distributing the Context number in the specified time to report evenly.
According to the technical scheme, in the invention, as the media gateway stores corresponding additional information (including signaling connection information, user information and the like), and the information can be reported to the soft switching center when service switching or service reversion occurs between the main soft switching center and the standby soft switching center, the soft switching center can recover corresponding bearing information, signaling connection information and user information according to the received call information including the additional information; therefore, the established steady state call can be normally maintained, the subsequent call signaling can be correctly processed, and the call ticket can be normally issued. For non-steady state calling, the load bearing resource on MGW, soft exchange center and opposite terminal entity resource can be released to avoid resource hang-up.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
FIG. 1 is a schematic diagram of a dual homing system;
FIG. 2 is a diagram of a protocol stack for a conventional A-port message
FIG. 3 is a protocol stack diagram of an A-port message after a soft switch fabric is used
FIG. 4 is a schematic diagram of a normal SCCP connection establishment procedure for port A messages;
fig. 5 is a protocol stack diagram of conventional TUP signaling;
figure 6 is a protocol stack diagram of TUP signaling after the use of a soft switch fabric;
fig. 7 is a schematic diagram of a call setup procedure in a preferred embodiment of the invention;
fig. 8 is a schematic diagram of the switch/rewind process in a preferred embodiment of the present invention.
Detailed Description
In the following embodiments, the network and convention of CDMA2000 are described, but the scheme of the present invention is not limited to CDMA2000, and is also applicable to WCDMA and fixed networks.
Since the Media Gateway (MGW) has bearer information for call setup, the bearer information can be recovered through interaction of the MGW and MSCe (mobile soft switching center). However, as can be seen from the foregoing, it is not sufficient to recover the bearer information, and if the signaling information cannot be recovered, the subsequent signaling cannot be processed correctly. Since the MGW has the bearer information, signaling and user information can be further added and stored on the MGW, so that the bearer, the signaling, the user, the ticket and other information can be comprehensively recovered through the interaction between the MGW and the MSCe, and the smooth transition of the service switching and service reversing process is realized. Specifically, in the call establishment process, the MSCe adds additional information (including signaling connection information, user information, etc.) to the bearer operation command of the MGW; and these additional information are kept by the MGW.
When switching or switching back, after MGW registers to new MSCe, it will report the stored load information, user information, signaling information to MSCe, and MSCe recovers the information and rebuilds the signaling, load, user list information of call.
If no switching or rewinding occurs, the additional information sent to the MGW is useless. In order to ensure that normal service processing efficiency is not affected, the additional information should be as compact as possible. Wherein,
(1) for the information which can be inquired and recovered through static data configuration, the information can be omitted, for example, a relay such as TUP, ISUP and the like establishes signaling connection with an opposite terminal entity through CIC, and the CIC information can be obtained by checking static data through Termination reported by MGW, so that the call information can be without CIC;
(2) for the signaling of the a port, since the local end connection reference and the opposite end connection reference are dynamic data, it must be added to the additional information.
(3) Since the call ticket information needs to be recovered through data such as the information of the calling subscriber, the information of the called subscriber, the connection time and the like, corresponding data must be added into the additional information.
When the service switching or the service switching is carried out, after the MGW is registered, the MSCe is informed of the calling information through the Notify message. Meanwhile, MGW reports the relevant Context, termination and call additional information to MSCe. When reporting information, the method adopts flow control to report, and there are two flow control modes: one is that reporting is carried out according to the fixed Context number in unit time until all the Context information is reported; and secondly, distributing the Context number in the specified time and reporting the Context number evenly.
Termination in the present invention is a logical entity on the MGW that can be used to identify circuit resources on the MGW. Context is used to indicate the connection relationship between endpoints. Wherein, Context is applied by MSCe, MGW is allocated, when two terminals join the same Context, default is to connect two terminals in two directions. That is, after the Termination of the calling and called circuits is added to the same Context, the calling and called circuits are actually connected in a bidirectional manner.
After receiving the call information, MSCe restores the bearing, signaling and call ticket information to the steady state call; and for the unsteady state call, initiating disconnection, and sending a disconnection message to the opposite terminal entity so as to prevent the opposite terminal entity from resource hang-up.
In particular, the process in the call setup procedure is shown in fig. 7. Each step is described separately below.
Step 701, the calling user initiates a call, and the calling BSC sends a CM service request (CMService Req) message to the MSCe, where the message includes a calling user identifier, a called number, and the like. This message is carried in the SCCP CR message with the connection reference on the BSC side.
Step 702, MSCe allocates connection reference of local terminal and allocates circuit between MSCe and calling BSC, (CIC is used between MSCe and BSC to identify the circuit, and Termination is used between MSCe and MGW to identify the circuit). The MSCe then sends a join endpoint message (ADD) to the MGW with Termination information (the endpoint is the circuit with the BSC), requests a Context (Context) application, and ADDs Termination to the Context. In this embodiment, additional call information is further added to the message: including the calling user information and the signaling connection relation with the BSC (including the home terminal connection reference and the opposite terminal connection reference).
Step 703, the MGW assigns a Context, adds the corresponding Termination to the Context, and then returns the message to the MSCe, the MSCe records the corresponding Context, and the MGW records the additional call information.
Step 704, MSCe sends Assignment Request message (Assignment Request) to calling BSC, requires to establish the ground circuit and air interface channel between MSC and BSC; this message is carried in a CC message of SCCP with a connection reference of MSC and a connection reference of BSC side.
Step 705, for the case that the called party is a mobile subscriber, the MSC gets the called location information from the HLR.
Step 706, if the HLR finds that the called party is in the MSC that initiated the request, it directly returns a message indicating that the called party is in the MSC that initiated the location request;
step 707, after the ground circuit and the air interface channel of the calling BSC are established, the BSC sends an Assignment Complete message (Assignment Complete) to the MSCe; this message is carried in the SCCP DT message with the MSC's connection reference.
Step 708, the MSCe sends a Paging message (Paging Request) to the BSC where the called party is located; this message is carried in a connectionless message, UDT, message of SCCP.
Step 709, after paging to the called, the called BSC sends a paging response message (pagengresponse) to the MSC. This message is carried in the SCCP CR message with the connection reference on the BSC side.
Step 710, the MSCe allocates the connection reference of the local terminal, and allocates the circuit between the MSCe and the called BSC. MSCe sends join endpoint message (ADD) to MGW with Context and called side Termination information just applied. Additional call information is also added to the message: including the called user information and the signaling connection relation (home terminal connection reference and opposite terminal connection reference) with the BSC.
Step 711, MGW adds terminating on the called side to the context and then returns the message to MSCe. The MGW records the aforementioned additional call information.
Step 712, the MSCe sends an assignment message to the called BSC, and requires to establish a ground circuit and an air interface channel between the MSC and the BSC, and the message carries a ringing parameter to ring the called terminal; this message is carried in a CC message of SCCP with a connection reference of MSC and a connection reference of BSC side.
Step 713, after the ground circuit and the air interface channel are established, the called BSC sends an assignment completion message to the MSC; this message is carried by the SCCP DT message, with the connection reference of the MSC.
Step 714, the MSCe sends Modify bearer message (Modify) to the MGW, with calling side Termination, informing the MGW to play the ring back tone to the calling side.
Step 715, after the MGW completes the operation, a response message (Reply) is sent back to MSCe.
Step 716, after the called party answers, the called BSC sends a CONNECT message to MSCe; this message is carried in SCCP's DT message, with MSCe's connection reference.
Step 717, the MSCe sends a Modify bearer message (Modify) to the MGW, the Termination with the calling side informs the MGW to stop playing the ring back tone to the calling side, and the calling and called terminations are connected in two directions. The modification bearer message adds additional call information: including the information of the calling and called users, the on-time, the steady state flag, etc.
Step 718, MGW returns a response message (Reply) to MSCe.
In the above steps, the MGW records the additional call information in the related message in addition to the normal bearer operation, so as to be used when switching or rewinding the service.
The process when a traffic switch or a traffic rollback occurs is shown in fig. 8. Wherein,
(1) for the call in a steady state, recovering the bearing information according to Context and Termination; restoring the signaling connection information with other entities according to the Termination additional information; and recovering the user information and the ticket information according to the additional information of the Context and the additional information of Termination.
(2) And for the call which is not in a stable state or the call with incomplete information, sending a message for releasing the bearer to the MGW and sending a disconnecting message to the opposite terminal entity so as to prevent the opposite terminal entity from resource hang-up.
It can be seen from the above embodiments that, by the method of the present invention, when the service switching or service switching occurs between the main MSCe and the standby MSCe, the established steady state call can be normally maintained, the subsequent call signaling can be correctly processed, and the call ticket can be normally issued. For non-steady state calling, the resources of MGW and opposite terminal entity can be released to avoid resource hang-up.
Attached table: abbreviations as used herein
Claims (8)
1. A method for recovering service data when service switching/rewinding in a dual-homing system is characterized by comprising the following steps:
(S1) during the call, when the soft switch center sends a bearer operation command to its registered media gateway, it adds and sends corresponding additional information;
(S2) the media gateway performs a bearer operation and saves the additional information it received;
(S3) when the service switching/rewinding occurs, the media gateway re-registers to another soft switch center and reports the call information with the additional information;
(S4) the other soft switch center determines whether the current call is a steady state call according to the received call information containing the additional information, and if so, recovers the corresponding bearer information, signaling connection information and user information according to the call information containing the additional information.
2. The method according to claim 1, wherein in said step (S4), if the current call is determined to be an unsteady call, said softswitch center sends a bearer release message to a media gateway and sends a disconnect message to a correspondent entity.
3. The method according to claim 1, wherein in said step (S4), for steady state calls, the call ticket information is also recovered.
4. The method of claim 1, wherein for a mobile communication system,
the additional information comprises signaling connection information and user information;
the call information reported in the step (S3) includes: context, additional information of Context, Termination, and additional information of Termination;
in the step (S4), the another softswitch center determines whether the current call is a steady-state call according to a steady-state flag in the additional information of the Context.
5. The method according to claim 4, wherein in the step (S4), if it is determined that the current call is a steady state call, then:
recovering bearing information according to the Context and Termination;
restoring the signaling connection information with other entities according to the Termination additional information;
and recovering the user information and the ticket information according to the additional information of the Context and the additional information of Termination.
6. The method according to any of claims 1-5, wherein in the step (S3), the call information is reported in a flow control manner.
7. The method of claim 6, wherein the flow control manner is: reporting according to the fixed Context number in unit time until all the Context information is reported.
8. The method of claim 6, wherein the flow control manner is: and distributing the number of contexts in a specified time and reporting the number evenly.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100084892A CN100428825C (en) | 2006-01-25 | 2006-01-25 | Method for recovering service data when service rearrangement / rollback in system of dual attributes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100084892A CN100428825C (en) | 2006-01-25 | 2006-01-25 | Method for recovering service data when service rearrangement / rollback in system of dual attributes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1874583A CN1874583A (en) | 2006-12-06 |
| CN100428825C true CN100428825C (en) | 2008-10-22 |
Family
ID=37484789
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100084892A Active CN100428825C (en) | 2006-01-25 | 2006-01-25 | Method for recovering service data when service rearrangement / rollback in system of dual attributes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100428825C (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101217824B (en) * | 2008-01-07 | 2010-12-22 | 华为技术有限公司 | Wireless network switching system and its switching method |
| CN101541097B (en) * | 2008-03-19 | 2013-04-17 | 华为技术有限公司 | Method, device and system for recovering bearing |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1434574A (en) * | 2002-01-24 | 2003-08-06 | 华为技术有限公司 | Backup method for mobile exchange center |
| CN1536819A (en) * | 2003-04-11 | 2004-10-13 | 华为技术有限公司 | Method for implementing dual home in next network |
| US20050039069A1 (en) * | 2003-04-03 | 2005-02-17 | Anand Prahlad | Remote disaster data recovery system and method |
-
2006
- 2006-01-25 CN CNB2006100084892A patent/CN100428825C/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1434574A (en) * | 2002-01-24 | 2003-08-06 | 华为技术有限公司 | Backup method for mobile exchange center |
| US20050039069A1 (en) * | 2003-04-03 | 2005-02-17 | Anand Prahlad | Remote disaster data recovery system and method |
| CN1536819A (en) * | 2003-04-11 | 2004-10-13 | 华为技术有限公司 | Method for implementing dual home in next network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1874583A (en) | 2006-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4001813B2 (en) | Monitoring connections to user terminals in telecommunications systems | |
| CN102035798B (en) | Service processing method, system and device for realizing disaster tolerance | |
| WO2006024225A1 (en) | A method for achieving double ascription | |
| CN101083606B (en) | Disaster recovery backup method and apparatus for mobile switching centre simulation | |
| US7496106B2 (en) | Methods and apparatus for providing signalling gateways with multi-network support | |
| JP2009200584A (en) | Emergency call processing apparatus, method and program, server and emergency call processing system using the same | |
| US7151935B2 (en) | Method for initiative setting up calls by service control point in mobile intelligent network | |
| CN100428825C (en) | Method for recovering service data when service rearrangement / rollback in system of dual attributes | |
| JP5313404B2 (en) | Method and system for realizing local call local switch | |
| EP2143260A1 (en) | Telecommunication nodes of sigtran network remaining active in an isolated received state for only receiving traffic related to pre-established or self-initiated sessions | |
| CN101507196B (en) | A fault route reselecting method of the call mediation node and an exchanger and a system thereof | |
| US20110019803A1 (en) | Method and device for presenting reason prompt for video call failure | |
| CN100421492C (en) | Method and soft exchange equipment for recoverying double-home service | |
| CN101883116A (en) | Calling processing method and media gateway | |
| US20130185409A1 (en) | Method and system for determining ip bearer optimization based on virtual media gateway | |
| KR100764431B1 (en) | Processing method for caller information sending service and system thereof | |
| CN101094274A (en) | Method for realizing disaster tolerated uninterrupted call in media gateway of next generation of network | |
| WO2005125222A1 (en) | Method for protecting incoming calls in personalized ring back tone service | |
| WO2012089064A1 (en) | Method and device for interacting control information between access terminal in circuit switch domain and as | |
| WO2006136098A1 (en) | A call processing method | |
| US6493442B1 (en) | AIN triggers to invoke non-AIN features | |
| US8331258B2 (en) | Method and device for responding to termination service state change indication | |
| WO2005122542A1 (en) | Method and system for providing ringback tones | |
| CN100579106C (en) | Method for realizing the channel associated signaling status compatibility under the NGN architecture | |
| JP2006033004A (en) | Communication device, call processing control device, and communication 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 |