The content of the invention
Present invention problem to be solved first is to provide one kind and realizes that intelligent network SCP disaster tolerance is protected using signaling front end processor
Method, this method can utilize SCP system signaling front end processors signaling processing ability and redundant computation ability, relative to traditional
N+1 standby systems, it is small with putting into, the characteristics of simple and easy to apply.Therefore, the present invention uses following technical scheme:
A kind of method that utilization signaling front end processor realizes the protection of intelligent network SCP disaster tolerance, it is characterised in that utilize Service control
The signaling processing ability and redundant computation ability of point SCP system signaling front end processors, Service control is detected in the signaling front end processor
After point SCP system background failures, service control point (SCP) system signaling processing, the letter are taken over by the signaling front end processor comprehensively
Make the signaling of front end processor handle the intelligent network feature for ignoring user, continued by ordinary call.
On the basis of using above-mentioned technical proposal, the present invention can also be using technical scheme further below:
The scheme is comprised the steps of:
(1), SCP systems it is initial, increase MTP message transfer part MTP local users configuration in the signaling front end processor, with
And TCAP, the TCAP of ansi standard, WIN, the routing configuration in Intelligent Network Application Protocol layer and the data configuration of local SCCP, ITU standard;
(2), SCP systems are when normally running, the signaling front end processor completes MTP protocol processing, and logical with SCP system backgrounds
Letter, communication media is Ethernet, and the availability and the accessibility of internal network on the preposition machine monitoring SCP backstages of the signaling;When
SCP backstages exception or Network Abnormal, then into step(3);
(3), signaling front end processor switching MTP user data purpose point to, be changed to by being sent to SCP system backgrounds originally
It is sent to local signaling connection control protocol SCCP agreement layer;
(4), MTP user data flow through local signaling connection control protocol SCCP agreement layer, transaction capabilities application section
Divide after Transaction Capabilities Application Part layer processing, reach the local WIN protocol layers of the signaling front end processor or Intelligent Network Application Protocol layer, local WIN is assisted
Layer or Intelligent Network Application Protocol layer are discussed by ordinary call processing, intelligent network response message is returned to service switching point, is called
Continue;
(5), behind SCP backstages or network disaster recovery, the purpose of MTP user data is switched back into SCP system backgrounds, by
SCP system backgrounds are taken over and recover normal intelligent network business processing procedure.
The signaling front end processor is according to the different point codings distributed in cdma network or fixed network, in step(4)Middle SCCP associations
View layer distinguishes heterogeneous networks using the Transaction Capabilities Application Part for being ITU standards or the Transaction Capabilities Application Part of ASNI standards according to GT translation results,
And SCCP agreement layer user data is correctly sent to different Transaction Capabilities Application Part layers.
The signaling front end processor is in step(4)Middle WIN protocol layers and Intelligent Network Application Protocol layer includes below scheme:C host is letter
Make flow, the called signaling process of C nets, C nets unconditional or signaling process of calling forwarding on busy, C net no-answer call connection signalings
Flow and fixed network signaling process.
Another technical problem to be solved of the invention is to provide a kind of device for realizing the above method.Therefore, this hair
Bright use following technical scheme:
Apparatus of the present invention is characterized in that it is embedded in the system signaling front end processor of service control point (SCP), including following mould
Block:
The MTP modules of switching user data flow direction are supported, for the step(1)Middle MTP local users configuration, Yi Ji
The step(2)When middle SCP systems are normally run, MTP protocol processing and the step in the signaling front end processor(3)With
Step(5)The switching that middle MTP user data purpose is pointed to;
Intercommunication module, for providing communication between MTP modules and SCP system backgrounds;
Failure judging module, in the step(2)The availabilities of middle monitoring SCP system backgrounds and internal network can
Up to property, judge whether malfunction, decision signaling front end processor enter the step(3)Or step(5);
SCCP modules, for the step(4)SCCP agreement is handled in signaling front end processor, and supports the step(1)In
The routing configuration and data configuration of SCCP agreement layer.
The TCAP modules of ITU standards, for the step(4)The Transaction Capabilities Application Part processing of ITU standards in signaling front end processor, and
Support the step(1)The Transaction Capabilities Application Part layer data configuration of middle ITU standards;
The TCAP modules of ansi standard, for the step(4)The Transaction Capabilities Application Part processing of ansi standard in signaling front end processor,
And support the step(1)The Transaction Capabilities Application Part layer data configuration of middle ansi standard.
WIN modules, for the step(4)WIN protocol processes in signaling front end processor, by all C net callings by common
Call flows are performed, while supporting the step(1)Middle WIN Protocol layer datas configuration;
INAP modules, for the step(4)Intelligent Network Application Protocol processing in signaling front end processor, the calling of all fixed network nets is pressed
Ordinary call handling process is performed, while supporting the step(1)Middle Intelligent Network Application Protocol layer data configuration.
Name Resolution:
SCP:Service control point (Service Control Point)
MTP:MTP message transfer part (Message Transfer Part)
SCCP:Signaling connection control protocol (Signaling Connection (and) Control Part)
TCAP:TCAP Transaction Capability Application Part (Transaction Capabilities Application Part)
WIN:Wireless intelligent network (Wireless Intelligent Network)
INAP:Intelligent network application protocol (Intelligent Network Application Protocol)
GT:Global title (Global Title)
MSC:Mobile switching centre (Mobile Switching Center)
GMSC:Mobile switching centre's gateway (Gateway Mobile Switching Center)
SSP:Service Switching Point (Service Switching Point)
ASNI:ANSI (American National Standards Institute) is North America
Standards setting organizations
ITU:International Telecommunication Union (International Telecommunication Union) is an international group
Knit, the main management system and standard for being responsible for establishing international wireless electricity and telecommunications
C nets:Cdma network
Fixed network:Traditional PSTN network
Ordinary call:Refer to calling of the calling and called both sides without signing intelligent network business
Due to using technical scheme, it can be handled using the signaling of service control point (SCP) system signaling front end processor
Ability and redundant computation ability, after signaling front end processor detection service control point (SCP) system background failure, by the signaling
Front end processor takes over service control point (SCP) system signaling processing, small with putting into relative to traditional N+1 standby systems, letter comprehensively
Single easy the characteristics of.
Embodiment
The present embodiment is so that telecommunications fixed network and C nets provide the SCP system reforms of intelligent network business as an example, to the letter of SCP systems
Make front end processor carry out plant modification of the present invention, reach following requirement:Automatic detection SCP system backgrounds failure or network event
Barrier, is switched to signaling front end processor takeover mode, and signaling front end processor realizes the purpose by ordinary call replay call.
The utilization signaling front end processor of the present embodiment realizes that the method for intelligent network SCP disaster tolerance protection is comprised the steps of:
(1), SCP systems it is initial, increase MTP message transfer part MTP local users configuration in the signaling front end processor, with
And TCAP, the TCAP of ansi standard, WIN, the routing configuration in Intelligent Network Application Protocol layer and the data configuration of local SCCP, ITU standard;
(2), SCP systems are when normally running, the signaling front end processor completes MTP protocol processing, and logical with SCP system backgrounds
Letter, communication media is Ethernet, and the availability and the accessibility of internal network on the preposition machine monitoring SCP backstages of the signaling;When
SCP backstages exception or Network Abnormal, then into step(3);
(3), signaling front end processor switching MTP user data purpose point to, be changed to by being sent to SCP system backgrounds originally
It is sent to local signaling connection control protocol SCCP agreement layer;
(4), MTP user data flow through local signaling connection control protocol SCCP agreement layer, transaction capabilities application section
Divide after Transaction Capabilities Application Part layer processing, reach the local WIN protocol layers of the signaling front end processor or Intelligent Network Application Protocol layer, local WIN is assisted
Layer or Intelligent Network Application Protocol layer are discussed by ordinary call processing, intelligent network response message is returned to service switching point, is called
Continue;
(5), behind SCP backstages or network disaster recovery, the purpose of MTP user data is switched back into SCP system backgrounds, by
SCP system backgrounds are taken over and recover normal intelligent network business processing procedure.
The signaling front end processor is according to the different point codings distributed in cdma network or fixed network, in step(4)Middle SCCP associations
View layer distinguishes heterogeneous networks using the Transaction Capabilities Application Part for being ITU standards or the Transaction Capabilities Application Part of ASNI standards according to GT translation results,
And SCCP agreement layer user data is correctly sent to different Transaction Capabilities Application Part layers.
The signaling front end processor is in step(4)Middle WIN protocol layers and Intelligent Network Application Protocol layer includes below scheme:C host is letter
Make flow, the called signaling process of C nets, C nets unconditional or signaling process of calling forwarding on busy, C net no-answer call connection signalings
Flow and fixed network signaling process.
Disaster tolerance protection device in refer to the attached drawing 1, signaling front end processor is included with lower module:
The MTP modules of switching user data flow direction are supported, for the step(1)Middle MTP local users configuration, Yi Ji
The step(2)When middle SCP systems are normally run, MTP protocol processing and the step in the signaling front end processor(3)With
Step(5)The switching that middle MTP user data purpose is pointed to;
Intercommunication module, for providing communication between MTP modules and SCP system backgrounds;
Failure judging module, in the step(2)The availabilities of middle monitoring SCP system backgrounds and internal network can
Up to property, judge whether malfunction, decision signaling front end processor enter the step(3)Or step(5);
SCCP modules, for the step(4)SCCP agreement is handled in signaling front end processor, and supports the step(1)In
The routing configuration and data configuration of SCCP agreement layer.
The TCAP modules of ITU standards, for the step(4)The Transaction Capabilities Application Part processing of ITU standards in signaling front end processor, and
Support the step(1)The Transaction Capabilities Application Part layer data configuration of middle ITU standards;
The TCAP modules of ansi standard, for the step(4)The Transaction Capabilities Application Part processing of ansi standard in signaling front end processor,
And support the step(1)The Transaction Capabilities Application Part layer data configuration of middle ansi standard.
WIN modules, for the step(4)WIN protocol processes in signaling front end processor, by all C net callings by common
Call flows are performed, while supporting the step(1)Middle WIN Protocol layer datas configuration;
INAP modules, for the step(4)Intelligent Network Application Protocol processing in signaling front end processor, the calling of all fixed network nets is pressed
Ordinary call handling process is performed, while supporting the step(1)Middle Intelligent Network Application Protocol layer data configuration.
When SCP systems are initial, failure judging module config failure detection switch, for controlling whether to open this protection device
Function;MTP modules are in addition to the data such as configuration MTP protocol layer basic signaling link, signalling route, in addition it is also necessary to the sheet of configuration switching
Ground destination, the flow direction for controlling MTP user data after detection failure;The GT translation numbers of SCCP modules configuration SCCP agreement layer
Client layer is the TCAP modules of ITU standards or the TCAP modules of ansi standard according to this and correspondingly;The TCAP modules of ITU standards and
The local matter processing quantity of Transaction Capabilities Application Part layer is respectively configured in the TCAP modules of ansi standard;WIN modules configure IN service class
Type, such as VPN are configured to 96, PPC and are configured to slotting code before the configuration of 128, INAP modules, for ordinary call flow processing provide according to
According to.
MTP modules are needed between increase and failure judging module in addition to possessing signalling system No.7 code requirement function in this implementation
Control function, according to the court verdict of breakdown judge module, decides whether that MTP customer traffics are switched into front end processor is originally located in
Reason, in such as Fig. 1 by->Path is switched to->->Path or->->Path;Intercommunication module except be responsible for
SCP system backgrounds are set up outside reliable communication connection, increase communication path state-detection and reporting fault judging module function;Failure
Judge module is believed by setting up the heartbeat detection between SCP system backgrounds, monitoring network interface state, collecting intercommunication module status
The key messages such as the availability and network reachability of the means such as breath monitoring SCP system backgrounds, if judging need according to monitored results
Start signaling front end processor disaster tolerance defencive function, then notify MTP module failures to occur, switch customer traffic;SCCP modules possess 7
Number signaling specification requires function, and intelligent network TCAP message employs the connectionless type transfer messages of SCCP, in addition in this implementation
Also have according to GT translation results, correct selection upper strata is using the Transaction Capabilities Application Part of ITU standards or the Transaction Capabilities Application Part of ansi standard
Processing function;The TCAP modules of ITU standards and the TCAP modules of ANSI standards meet signalling system No.7 code requirement, they
Upper-layer user is respectively INAP modules and WIN modules;INAP modules and WIN modules do not provide complete INAP or WIN protocol layers
Function, but specially treated flow is employed, refer to accompanying drawing 2 ~ 6.Used due to not preserving intelligent network locally in signaling front end processor
Family business datum, the serial flow purpose is to ensure replay call, without the intelligent network attribute of holding calling.
Accompanying drawing 2, C host is signaling process.
Step 2.1 ~ 2.4, MSC/SSP detects trigger and initiates ORREQ to SCP systems, and WIN modules receive corresponding requests
Transactional query indication, responds orreq(Wherein, WIN modules do not do number translation and do not provide terminatiolist parameters,
Service key(DMH_ServiceID)Parameter is pre-configuration data), indicate that MSC/SSP proceeds call treatment;
Step 2.5 ~ 2.8, SCP system receives ANLYZD, and WIN modules are directly in response to anlyzd, service key(DMH_
ServiceID)For pre-configuration data;
Step 2.9 ~ 2.10, after user answers, SCP systems receive the OANSWER message that MSC/SSP is sent.WIN moulds
The block record calling time started, other processing are not done;
Step 2.11 ~ 2.14, after user's communication terminates, SCP systems receive the ODISCONNECT that MSC/SSP is sent up,
WIN modules record end of conversation time, the duration of call, odisconnect, cut-out calling are issued to MSC/SSP.
Accompanying drawing 3, the called signaling process of C nets.
Step 3.1 ~ 3.4, SCP system receives ANLYZD (Initial triggers) message, returns and responds to MSC/SSP
Anlyzd, service key(DMH_ServiceID)For pre-configuration data;
Step 3.5 ~ 3.8, SCP system receives ANLYZD, and (Called_Routing_Address_Available is triggered
Device) message, WIN modules to MSC/SSP return response anlyzd, service key(DMH_ServiceID)For pre-configuration data;
Step 3.9 ~ 3.10, after user answers, SCP systems receive the TANSWER message that MSC/SSP is sent.WIN moulds
The block record calling time started, other processing are not done;
Step 3.11 ~ 3.14, after user's communication terminates, SCP systems receive the TDISCONNECT that MSC/SSP is sent up.
WIN modules record end of conversation time, the duration of call, tdisconnect, cut-out calling are issued to MSC/SSP.
Accompanying drawing 4, C nets are unconditional/divert when busy signaling process.
Step 4.1 ~ 4.4, SCP system receives ANLYZD (Initial triggers) message, and WIN modules are returned to MSC/SSP
Echo and answer anlyzd, service key(DMH_ServiceID)For pre-configuration data;
Step 4.5 ~ 4.8, core net does forward, and SCP systems receive ANLYZD (Calling_Routing_Address_
Available triggers) message(Wherein, parameter DMH_RedirectionIndicator is designated as forwarded calls).WIN moulds
Block returns to response analyzd message, service key(DMH_ServiceID)For pre-configuration data;
Step 4.9 ~ 4.10, after user answers, SCP systems receive the OANSWER message that MSC/SSP is sent.WIN moulds
The block record calling time started, other processing are not done;
Step 4.11 ~ 4.14, after user's communication terminates, SCP systems receive the ODISCONNECT that MSC/SSP is sent up,
WIN modules record end of conversation time, the duration of call, odisconnect, cut-out calling are issued to GMSC/SSP.
Accompanying drawing 5, C net Call Forwarding No Reply signaling processes.
Step 5.1 ~ 5.4, SCP system receives ANLYZD (Initial triggers) message, and WIN modules are returned to MSC/SSP
Echo and answer anlyzd, service key(DMH_ServiceID)For pre-configuration data;
Step 5.5 ~ 5.8, SCP system receives ANLYZD, and (Called_Routing_Address_Available is triggered
Device) message, WIN modules are handled by normal called service, to MSC/SSP return response anlyzd, service key(DMH_
ServiceID)For pre-configuration data;
Step 5.9 ~ 5.12, after user is unresponsive, core net does forward, and SCP systems receive ANLYZD (Calling_
Routing_Address_Available triggers) message(Wherein, parameter DMH_RedirectionIndicator refers to
It is shown as forwarded calls).WIN modules return to response analyzd message to MSC/SSP;
Step 5.13 ~ 5.14, after user answers, SCP systems receive the OANSWER message that MSC/SSP is sent.WIN modules
The record calling time started, other processing are not done;
Step 5.15 ~ 5.18, after user's communication terminates, SCP systems receive the ODISCONNECT that MSC/SSP is sent up,
WIN modules record end of conversation time, the duration of call, odisconnect, cut-out calling are issued to SCP.
Accompanying drawing 6, fixed network signaling process.
Step 6.1 ~ 6.4, SCP system is received in the IDP message that MSC/SSP is sent, WIN module check IDP message and is called
Number argument, and pre-configured preceding slotting code is matched, remove the preceding slotting code matched in called number, obtain real called party number.
WIN modules carry connect operations with TC-END, fill in real called party number argument, notify the autonomous replay calls of SSP, and tie
Beam is talked with current TC;
Step 6.5 ~ 6.8, SCP system receives the non-IDP message that MSC/SSP is sent, and WIN modules are carried with TC-END
Reject is operated, and is notified SSP and is terminated current TC dialogues.
Each message in accompanying drawing is illustrated below
Fig. 2
Numbering |
Message |
Explanation |
2.1 |
ORREQ |
Originate call attempt authentication trigger point operation requests |
2.2 |
TC_QUERY_WITH_PERM_IND |
Transactional query indication |
2.3 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
2.4 |
Orreq |
Originate the operation response of call attempt authentication trigger point |
2.5 |
ANLYZD |
Analyze information trigger point operation requests |
2.6 |
TC_CONVERSATION_WITH_PERM_IND |
Transaction session indication |
2.7 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
2.8 |
Analyzd |
Analyze the operation response of information trigger point |
2.9 |
OANSWER |
Caller response trigger point operation requests |
2.10 |
TC_UNI_INDICATION |
The unidirectional indication of affairs |
2.11 |
ODISCONNECT |
Caller is taken out stitches trigger point operation requests |
2.12 |
TC_RESPONSE_IND |
Transaction response indication |
2.13 |
TC_RESPONSE_REQ |
Transaction response request primitive |
2.14 |
Odisconnect |
Caller take out stitches trigger point operation response |
Fig. 3
Numbering |
Message |
Explanation |
3.1 |
ANLYZD(Initial) |
Analyze information trigger point operation requests(Initial triggers) |
3.2 |
TC_QUERY_WITH_PERM_IND |
Transactional query indication |
3.3 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
3.4 |
Anlyzd |
Analyze the operation response of information trigger point |
3.5 |
ANLYZD(Called_Routing_Address_Available) |
Analyze information trigger point operation requests(Called_Routing_Address_Available triggers) |
3.6 |
TC_CONVERSATION_WITH_PERM_IND |
Transaction session indication |
3.7 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
3.8 |
Analyzd |
Analyze the operation response of information trigger point |
3.9 |
TANSWER |
Called party answer trigger point operation requests |
3.10 |
TC_UNI_INDICATION |
The unidirectional indication of affairs |
3.11 |
TDISCONNECT |
Called trigger point operation requests of taking out stitches |
3.12 |
TC_RESPONSE_IND |
Transaction response indication |
3.13 |
TC_RESPONSE_REQ |
Transaction response request primitive |
3.14 |
Tdisconnect |
Called trigger point operation response of taking out stitches |
Fig. 4
Numbering |
Message |
Explanation |
4.1 |
ANLYZD(initial) |
Analyze information trigger point operation requests(Initial triggers) |
4.2 |
TC_QUERY_WITH_PERM_IND |
Transactional query indication |
4.3 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
4.4 |
Analyzd |
Analyze the operation response of information trigger point |
4.5 |
ANLYZD(Calling_Routing_Address_Available) |
Analyze information trigger point operation requests(Calling_Routing_Address_Available triggers) |
4.6 |
TC_CONVERSATION_WITH_PERM_IND |
Transaction session indication |
4.7 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
4.8 |
Analyzd |
Analyze the operation response of information trigger point |
4.9 |
OANSWER |
Caller response trigger point operation requests |
4.10 |
TC_UNI_INDICATION |
The unidirectional indication of affairs |
4.11 |
ODISCONNECT |
Caller is taken out stitches trigger point operation requests |
4.12 |
TC_RESPONSE_IND |
Transaction response indication |
4.13 |
TC_RESPONSE_REQ |
Transaction response request primitive |
4.14 |
Odisconnect |
Caller take out stitches trigger point operation response |
Fig. 5
Numbering |
Message |
Explanation |
5.1 |
ANLYZD(initial) |
Analyze information trigger point operation requests(Initial triggers) |
5.2 |
TC_QUERY_WITH_PERM_IND |
Transactional query indication |
5.3 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
5.4 |
Analyzd |
Analyze the operation response of information trigger point |
5.5 |
ANLYZD(called_Routing_Address_Available) |
Analyze information trigger point operation requests(Called_Routing_Address_Available triggers) |
5.6 |
TC_CONVERSATION_WITH_PERM_IND |
Transaction session indication |
5.7 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
5.8 |
Analyzd |
Analyze the operation response of information trigger point |
5.9 |
ANLYZD(Calling_Routing_Address_Available) |
Analyze information trigger point operation requests(Calling_Routing_Address_Available triggers) |
5.10 |
TC_CONVERSATION_WITH_PERM_IND |
Transaction session indication |
5.11 |
TC_CONVERSATION_WITH_PERM_REQ |
Transaction session request primitive |
5.12 |
Analyzd |
Analyze the operation response of information trigger point |
5.13 |
OANSWER |
Caller response trigger point operation requests |
5.14 |
TC_UNI_INDICATION |
The unidirectional indication of affairs |
5.15 |
ODISCONNECT |
Caller is taken out stitches trigger point operation requests |
5.16 |
TC_RESPONSE_IND |
Transaction response indication |
5.17 |
TC_RESPONSE_REQ |
Transaction response request primitive |
5.18 |
Odisconnect |
Caller take out stitches trigger point operation response |
Fig. 6
Numbering |
Message |
Explanation |
6.1 |
lDP |
Start DP operations |
6.2 |
ITU_TC_BEGIN_IND(IDP) |
BEGIN indications(Band IDP operations) |
6.3 |
ITU_TC_END_REQ(CONNECT) |
END request primitives(Band CONNECT operations) |
6.4 |
CONNECT |
Attended operation |
6.5 |
not lDP |
Non- IDP operations |
6.6 |
ITU_TC_BEGIN_IND |
BEGIN indications |
6.7 |
ITU_TC_END_REQ(REJECT) |
END request primitives(Band REJECT operations) |
6.8 |
REJECT |
Refusal operation |