Patent Grant
7046788
The invention is based on a priority application EP 03290703.2 which is hereby incorporated by reference.
This invention is related in general to the field of telecommunications systems. More particularly, the invention is related to a SS7 signaling server and method for routing SS7 links in a telecommunications network. More particularly, the invention is related to a SAS Application Service. The invention is related to the European patent applications EP 02360267.5, now U.S. Ser. No. 10/656,125, and EP 02360268.3 which hereby, now U.S. Ser. No. 10/642,687, are incorporated by reference.
A SS7 signaling server for routing SS7 links includes a signaling transfer point (STP) and a signaling application server (SAS). The SAS is capable to process at least one application process. Each application process, e.g. an individual INAP, MAP, CAP, or any TCAP User, TCAP Relay, or SCCP Relay service request has to be identified and processed.
The SS7 signaling server for routing SS7 links, includes e.g. a signaling transfer point (STP) and a signaling application server (SAS); SS7=Signaling System No. 7. STP and SAS have different functionalities. The STP has at least one external interface to connect the STP via at least one SS7 link to at least one telecommunications unit, and an internal interface to connect the STP to the SAS. The STP processes incoming SS7 messages, e.g. in the MTP1, MTP2, MTP3, and SCCP layer. The SAS is capable to process at least one application service request, advantageously at least two different application service requests. The STP identifies a single application service request in one incoming SS7 message and provides the identified single application service request to the SAS for further processing. The SAS has e.g. two TCAP processes to identify two different application services, e.g. INAP and MAP. STP and SAS are interconnected via an internal interworking protocol, e.g. using TCP/IP (transmission control protocol/internet protocol). The interworking protocol is called Advanced Signaling Transport Protocol (ASTP).
The signaling server is e.g. highly configurable and efficient regarding run-time. The signaling server is capable of processing multiple application service requests, e.g. mobile number portability (MNP), service number portability (SNP), screening, intelligent network (IN) services, TCAP services, MAP services, CAP services, TCAP Relay, TCAP User Relay, SCCP Relay.
The SS7 signaling server for routing SS7 links, includes e.g. a signaling transfer point (STP) and a signaling application server (SAS),
It is an object of the invention to provide an advantageous method to process a SAS Application Service request.
An inventive method to process a SAS Application Service request includes the steps of: performing an Inbound Message Analysis, performing a Service Decision, performing an Outbound Message Synthesis, wherein the Inbound Message Analysis includes an Application Specific Inbound Protocol Check, an NoAI (Nature of Address Indicator) Analysis and an Inbound Digit Analysis, wherein the Service Decision includes a Database Search and an Application Specific Evaluation of Database Search Indications, and wherein the Outbound Message Synthesis includes generating an Output Digit String making use of an application specific Output Digit String Configuration Table, which includes the parameter SAS Application Service Id and at least one of the following parameters: Output Digit String Id, Auxiliary Number Name, Nature of Address Indicator, Auxiliary Number Presence, Auxiliary Number Position.
In a preferred embodiment of the invention the Outbound Message Synthesis includes generating an Output Digit String making further use of at least one Outbund Processing Configuration Table, which includes the parameter SAS Application Service Id and at least one of the following parameters: Number Type, Portability Status, Inbound NoAI Value, Response Action Id, Output Digit String Id.
In a further preferred embodiment of the invention the Service Decision further includes a Generic Loop Detection Analysis making use of at least one application specific Loop Detection Configuration Table, which includes the parameter SAS Application Service Id and at least one of the following parameters: SAS Database Id, SAS Database Table Id, Number type, Portability Status, Loop Detection state and Action.
Advatageously the Database Search is performed in a Single Number Table and subsequently in a Range Number Table if the Single Number Table query indicates a NO MATCH or an Error in the Single Number Table.
The invention can be used for a variety of services:
In a first embodiment the SAS Application Service is INAP based Number Portability, and the Output Digit String Configuration Table includes INAP based Number Portability Ids (MNP-INAP-O-VM-IW).
In a second embodiment the SAS Application Service is SRI (Send Routing Information) terminating Number Portability, and the Output Digit String Configuration Table includes SRI terminating Number Portability Ids (MNP-SRIt-O-VM-IW).
In a third embodiment the SAS Application Service is MAP Forward Short Message Access Screening, and the Output Digit String Configuration Table includes Forward Short Message Access Screening Ids (MAP-FSM).
In a fourth embodiment the SAS Application Service is Fixed SCCP Routing, and the Output Digit String Configuration Table includes Fixed SCCP Routing Ids (FNP-SRF).
In a fifth embodiment the SAS Application Service is CAP IDP Relay Mobile Number Portability, and the Output Digit String Configuration Table includes CAP IDP Relay Mobile Number Portability Ids (MNP-CAP-RELAY-IW).
In a sixth embodiment the SAS Application Service is INAP IDP Relay, and the Output Digit String Configuration Table includes INAP IDP Relay Ids (INAP-IDP-RELAY-I/W).
In a seventh embodiment the SAS Application Service is Mobile SCCP Routing, and the Output Digit String Configuration Table includes Mobile SCCP Routing Ids (MNP-NCR).
The inventive method could be implemented using different kind of hardware and software equipment, e.g.:
An inventive Signaling application server (SAS) comprises at least one processor, at least one database and at least one processing software for processing at least one application service request, wherein the at least one processing software is programmed in such a way that identifying and processing at least one application service request is enabled—including e.g. a signaling connection control part (SCCP) process and/or at least one transaction capabilities application part (TCAP) process to identify at least one application service request—, and wherein processing a SAS application service, comprises the steps of:
performing an inbound message analysis,
performing a Service Decision including a database search,
performing an Outbound Message Synthesis including generating an Output Digit String making use of an application specific Output Digit String Configuration Table, which includes the parameter SAS Application Service Id and at least one of the following parameters: Output Digit String Id, Auxiliary Number Name, Nature of Address Indicator, Auxiliary Number Presence, Auxiliary Number Position.
An inventive SS7 signaling server for routing SS7 links, includes a signaling transfer point (STP), and a signaling application server (SAS),
For a better understanding of the present invention, reference is made to the accompanying drawings, in which:
The preferred embodiments of the present invention are illustrated in
INAP Based Number Portability
Short Description:
This service embraces INAP NP (Number Portability) with optionally voice mail for both mobile and fixed network, which may request one or more digits if the number is either incomplete or ambiguous. All these combinations are configurable.
The calling number of the INAP IDP message and optionally the additional digits of the ERB message are used to interrogate the subscriber database. The database contents and the configuration data are used to examine what kind of message is send and what number the message is filled with.
The three stages of the Application Service:
Inbound Message Analysis:
This stage starts with some service specific inbound protocol checks, e.g. decoded operation code, calling and called number size. If the values are ok, both numbers are extracted for further usage.
The NoA (Nature of Address) is extracted from the calling address in the calling number field.
Depending on the NoA a specific analyse string is chosen. That analyse string describes which auxiliary number parts are mandatory or optionally. Then the auxiliary number parts are analysed. If found and correct, then remove auxiliary number part from received E.164 or MSIN Based number and store it internally. E.164 is e.g. defined in ITU-T E.164, MSIN is e.g. defined in ITU-T E.212. This analysis is done step by step for each possible auxiliary number part. If ambiguous then one or more digits are requested, depending on service specific configuration items. When the analysis of the auxiliary number parts terminates successfully, then the second stage starts. Each auxiliary number part is to be stored in a record containing its name, its position, its value, and its presence. Inbound Processing is configured based on the specification of the received digit string and other application service specific configuration items.
The inbound digit anaylsis makes use of an input digit string configuration table. The inbound digit analysis e.g. serves to analyse the called or the calling party address. The input digit string configuration table includes at least two of the following parameters: SAS Application Service Id, Input Digit String Id, Auxiliary Number Name, Global Title Indicator, Nature of Address Indicator, Auxiliary Number Presence, Auxiliary Number Position.
Service Decision:
This stage analyses the core part of the received number in the Single Number and Range Number tables. Additional digits might be requested. The Extended Match Indicator is to be used if required. Service Decision includes also Loop Detection. The Service Decision is executed dependent on configuration data items and the Transition Indicator, the Default/Exception Indicator, and the Single Number Flag of the Single Number and Range Number tables.
For those SAS Application Services that are required to search the E.164 or MSIN Based Tables for routing information, the following principles apply. The search of the E.164 or MSIN Based Tables constitutes the main service decision. Figure depicts the SDL diagram of the Service Decision.
Database Search
The Evaluation of Database Search Indications is a SAS Application Service specific matter, also the decision whether or not to perform another SAS Database search. The Application Specific Evaluation of Database Search Indications includes for instance actions like requesting additional digits in case the database search came back with an indication that the queried number was AMBIGUOUS. Both, the application specific evaluations and the decision for further database searches, depend on the SAS Application Service's service logic, configurable items such as “Open/Closed Numbering Plan”, “Block/Single Number Dialling”, “Request More Digits Yes/No”, and other things.
Generic Loop Detection Analysis
Loop detection is provided to prevent signalling loops within the signalling network. Signalling loops may occur when the routing databases in different signalling networks contain inconsistent routing information for network subscribers. The ability to detect signalling loops is defined within the scope of each SAS Application Service and may not be present in all SAS Application Services. Also, the response taken to the detection of a signalling loop is defined within the scope of each SAS Application Service.
There are two kinds of loop detection: a generic one and an application specific one. The generic one is specified in detail here. The applications specific ones are specified at the respective SAS Application Services.
The generic mechanism for the detection of signalling loops is a two step process and requires the co-operation of the underlying switched network in order to succeed. First, the underlying switched network will pass any received Inter-Network Routing Number to the SAS as part of the concerned address (i.e. the SCCP Called Party Address GTAI). This first step signals the SAS Loop Detection algorithm that the signalling message has originated outside of the current signalling network. Secondly, the E.164 database(s) search must resolve to a combination of the pair (E.164 Number Type, Portability Status) that is marked as a candidate for looping. With these two criteria met, the signalling loop is detected.
This implies, that there has to be configuration table which indicates for each pair (E.164 Number Type, Portability Status), whether loop detection is to be enabled or not.
As a temporary relaxation of the SAS Loop Detection, the Transition Time capability was introduced. This provides a synchronisation period for recent database updates. If the Transition Indicator is marked “Transition Time is not yet over”, then the SAS Loop Detection is either bypassed or relaxed.
Outbound Message Synthesis:
Depending on the result of this database query and the inbound processing, the response is generated. Outbound processing is configured based on the specification of the digit string to be sent off, the Service Control Data Record, the Number Type and the Portability Status, and other configuration data items.
Configuration tables control Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example. The SAS Application Service is the same as the one used above: MNP-INAP With Optional Voice Mail Inter-working.
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string. This service used the following response actions: INAP Continue, INAP Connect, INAP ReleaseCall and INAP Return Error.
Within the Connect message the parameters ‘Include Cut And Paste’ are configurable. Depending on a configurable parameter Connect message can be send either to original or alternate number. Depending on a configurable parameter the routing number can be included or send as a parameter. The alternate number is configured by number, Nature Of Address and Numbering Plan. If the Connect message to original number is sent the configurable flag Send Charging Information is evaluated, too.
An error code is configurable as parameter of the Return Error message depending on the database result. For each database result another Return Error Code can be configured.
If a Release Call message is sent a Release Cause depending on the database result can be configured. For each database result another Release Cause can be configured.
There are eight configurable outbound actions for this Service Handler:
Configuration Data:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 12 presents the information necessary to specify an input digit string. Table 13 specifies the mapping between the Input Digit String to the Output Digit String. Table 14 specifies the mapping between the Output Digit String and the Protocol Element.
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164/MSIN Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
Table 15 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is contained in Table 16.
Scenarios:
With INAP Continue.
SRI Terminating Number Portability
Short Description:
This service encompasses SRI terminating NP (SRI=Send Routing Information, NP=Number Portability) with optionally voice mail for a mobile network. The service is highly configurable.
The second and all further embodiments of the inventions are described using partly the some figures and tables as used for the first embodiment.
The SRI terminating service handles the SRI (Send Routing Information) message of the MAP (Mobile Application Part) protocol. Of the incoming message, the parameter ‘MSISDN’ is analysed. The MSISDN may or may not contain a voice mail infix, this is configurable. The service terminates the SRI message according to its configuration by an SRI Response message, a TCAP Error, a TCAP Reject or by discarding the request. In the SRI Response message, the parameters Roaming Number and IMSI are set. The IMSI is set to a fixed, configurably default IMSI (an IMSI must be present as per the MAP standard).
An instance of the SRI Terminating service can either work together with an instance of the SRF service (Mobile SCCP routing) or work stand-alone.
A typical case for numbers with voice mail infix is that the SRI Terminating service instance handles all requests by sending an appropriate SRI response.
Alternatively—typically for numbers without voice mail infix—, the SRF service instance handles requests that stay in the own network by relaying the request to the appropriate HLR, while it forwards requests that require a foreign network to the SRI Terminating service. The SRI Terminating service instance handles these requests by terminating them with an appropriate SRI Response.
Multiple instances of the SRI Terminating service with different configurations can run inside the SAS in parallel.
The three stages are described in detail as follows:
For those SAS Application Services that are required to search the E.164 or MSIN Based Tables for routing information, the following principles apply. The search of the E.164 or MSIN Based Tables constitutes the main service decision. Figure depicts the SDL diagram of the Service Decision.
The Evaluation of Database Search Indications is a SAS Application Service specific matter, also the decision whether or not to perform another SAS Database search. The Application Specific Evaluation of Database Search Indications may include for instance actions like requesting additional digits in case the database search came back with an indication that the queried number was AMBIGUOUS. Both, the application specific evaluations and the decision for further database searches, depend on the SAS Application Service's service logic, configurable items such as “Open/Closed Numbering Plan”, “Block/Single Number Dialling”, “Request More Digits Yes/No”, and other things.
The SRI Terminating service never requests additional digits because this is neither possible nor necessary in the MAP protocol. The MSISDN parameter always contains all digits. If the database search indicates AMIGUOUS, the SRI Terminating service treats this as a database error.
Loop Detection is a mechanism to discover inconsistencies in the received data, which might be caused by a condition that causes the SS7 message to loop through the SS7 network. There are two kinds of loop detection: a generic one and an application specific one. The generic one is specified in detail here. The applications specific ones are specified at the respective SAS Application Services.
Table 1 shows an E.164 Single Number Table for the Example.
Table 2 shows an E.164 Range Number Table for the Example.
Table 3 shows a Service Control Data Table for the Example.
Table 4 shows an Auxiliary Number Table for the Example.
Detection of Loops
Loop detection is provided to prevent signalling loops within the signalling network. Signalling loops may occur when the routing databases in different signalling networks contain inconsistent routing information for network subscribers. The ability to detect signalling loops is defined within the scope of each SAS Application Service and may not be present in all SAS Application Services. Also, the response taken to the detection of a signalling loop is defined within the scope of each SAS Application Service.
As stated above, there is a Generic Loop Detection mechanism, which applies to many SAS Application Service, and there are SAS Application Service specific Loop Detection mechanisms. The Generic Loop Detection mechanism is in detail specified here.
There is no application specific Loop Detection mechanisms in the SRI terminating service. Only the Generic Loop Detection is executed.
Generic Loop Detection Analysis
The generic mechanism for the detection of signalling loops is a two step process and requires the co-operation of the underlying switched network in order to succeed. First, the underlying switched network will pass any received Inter-Network Routing Number to the SAS as part of the concerned address (i.e. the SCCP Called Party Address GTAI). This first step signals the SAS Loop Detection algorithm that the signalling message has originated outside of the current signalling network. Secondly, the E.164 database(s) search must resolve to a combination of the pair (E.164 Number Type, Portability Status) that is marked as a candidate for looping. With these two criteria met, the signalling loop is detected.
This implies, that there has to be configuration table which indicates for each pair (E.164 Number Type, Portability Status), whether loop detection is to be enabled or not.
As a temporary relaxation of the SAS Loop Detection, the Transition Time capability was introduced. This provides a synchronisation period for recent database updates. If the Transition Indicator is marked “Transition Time is not yet over”, then the SAS Loop Detection is either bypassed or relaxed.
Configuration tables control Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example. The SAS Application Service is the same as the one used above: MNP-SRIt With Optional Voice Mail Inter-working.
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string.
There are the following configurable outbound actions for this Service Handler:
Table 21 shows the configuration example for the case that the SRI terminating service is used stand-alone (typical for numbers with voice mail infix).
For the configuration where the SRI terminating service works together with the SRF service (see 0, typical for numbers without voice mail infix), the column “Response Action Id1” in the rows ONNPO and FNPI would contain “Send TCAP Error” and the last three columns of those rows would contain null values.
Configuration Data:
Table 11 shows Details of the Loop Detection Status Configuration Table.
Configuration Items for Outbound Digits Synthesis:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 12 presents the information necessary to specify an input digit string. Table 13 specifies the mapping between the Input Digit String to the Output Digit String. Table 14 specifies the mapping between the Output Digit String and the Protocol Element.
Table 12 shows Details of the Output Digit String Configuration Table.
Table 13 shows Details of the Input Digit String To Output Digit String Mapping Table.
Table 14 shows Details of the Input Digit String To Protocol Element Mapping Table
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164/MSIN Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
Table 16 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Normal Completion.
Tbale 16 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is contained in Table 22.
Table 17 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Abnormal Completion.
Scenarios:
MAP Forward Short Message Access Screening
Short Description of the Service:
In order to protect against fraud a Short Message Service Center (SMSC) normally validates if the originator of an incoming short message is belonging to the home network. Analyzing the A-number within the short message allows this validation.
However, within a Mobile Number Portability environment, the MSISDN no longer indicates the home network of the subscriber since this number could now belong to another mobile network operator. Therefore, a screening function is required based on the mobile number portability status of the originator's MSISDN. All incoming MO-FSM messages are intercepted and the MAP SM-RP-OA parameter is used as a key for searching in the number portability database.
If the calling party number within the MAP SM-RP-OA address was found in the database as an imported or regular subscriber of the concerned provider, the MO-FSM is forwarded to the SMSC. Otherwise, a backward message is created containing a MAP error code.
Detailed Description of the Service:
Inbound Message Analysis:
Application Specific Inbound Protocol Checks:
The following checks are performed for the MAP FSM service:
If all inbound protocol checks are passed successfully the NoAI of the SM-RP-OA MSISDN is extracted. In case the NoAI is not supported continue with the current SCCP routing mechanism. Otherwise select a NoAI specific analysis string. This string specifies which auxiliary number parts are existing and which of them are mandatory or optional.
Inbound Digit Analysis:
The inbound digit analysis is performed together with the analysis string.
Service Decision:
Database Search
The extracted core part of the MSISDN is used as a key for searching in the number portability database. The search algorithm is depicted in
Application Specific Evaluation of DB Search Indications
If the DB search result is different from MATCH in SINGLE TABLE/MATCH in RANGE TABLE the Not Found Response Action is executed. This action is configurable and is either set to Continue Routing or Return an Error.
In any other case one of the following response actions is selected:
This response action is configuration controlled and depends on the Service Control Data Record, the Number Type, the Portability Status and other configuration data items.
Table 1 shows an Example for an E.164 Single Number Table.
Table 2 shows an Example for an E.164 Range Number Table.
Notes to Table 1 and Table 2: Due to space reasons only three Service Control Data Slots are shown instead of five.
Table 3 shows an Example for a Service Control Data Table.
Table 4 shows an Example for a Service Control Slots Configuration Table.
Outbound Message Synthesis:
Configuration tables control Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example (see Tables 10–12 and Tables 23–27). The SAS Application Service is the same as the one used above, MAP FSM (with a response action set to Continue Routing with Routing Number Prefix).
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string.
There are the following configurable outbound actions for this Service Handler:
Note to Table 26: In this example the MO-FSM message is just forwarded based on the current SCCP routing mechanism without changing the SCCP CdPA GTA.
Configuration Data:
Configuration Items for Loop Detection:
Table 10 shows Details of the Loop Detection Status Configuration Table.
Note: For the MAP FSM service the loop detection status is always set to Disabled.
Configuration Items for Outbound Digits Synthesis:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 11 presents the information necessary to specify an output digit string. Table 12 specifies the mapping between the Input Digit String to the Output Digit String. Table 13 specifies the mapping between the Output Digit String and the Protocol Element.
Table 11 shows Details of the Output Digit String Configuration Table.
Table 12 shows Details of the Input Digit String to Output Digit String Mapping Table.
Table 13 shows Details of the Input Digit String to Protocol Element Mapping Table.
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. In the future the same principle can be applied to other number parts as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data in the future the same principle can be applied to other number parts as well.
Table 14 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Normal Completion.
Table 14 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is specified in Table 15.
Table 15 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Abnormal Completion.
Scenarios:
Fixed SCCP Routing
Short Description:
This service realizes Number Portability on SCCP level for fixed networks (Signalling Relay Function (SRF)).
The three stages are described in detail as follows:
For those SAS Application Services that are required to search the E.164 or MSIN Based Tables for routing information, the following principles apply. The search of the E.164 or MSIN Based Tables constitutes the main service decision.
The Evaluation of Database Search Indications is a SAS Application Service specific matter, also the decision whether or not to perform another SAS Database search. Both, the application specific evaluations and the decision for further database searches, depend on the SAS Application Service's service logic, configurable items and other things.
Loop Detection is a mechanism to discover inconsistencies in the received data, which might be caused by a condition that causes the SS7 message to loop through the SS7 network. There are two kinds of loop detection: a generic one and an application specific one. The generic one is specified in detail here. The applications specific ones are specified at the respective SAS Application Services.
Table 1 shows E.164 Single Number Table for the Example.
Table 2 shows E.164 Range Number Table for the Example.
Table 3 shows Service Control Data Table for the Example.
Table 4 shows Auxiliary Number Table for the Example.
Detection of Loops and other Inconsistencies:
Loop detection is provided to prevent signalling loops within the signalling network. Signalling loops may occur when the routing databases in different signalling networks contain inconsistent routing information for network subscribers. The ability to detect signalling loops is defined within the scope of each SAS Application Service and may not be present in all SAS Application Services. Also, the response taken to the detection of a signalling loop is defined within the scope of each SAS Application Service.
As stated above, there is a Generic Loop Detection mechanism, which applies to many SAS Application Service, and there are SAS Application Service specific Loop Detection mechanisms. The Generic Loop Detection mechanism is in detail specified here. The SAS Application Service specific Loop Detection mechanisms are outlined here and are specified at the respective SAS Application Service.
Generic Loop Detection Analysis:
The generic mechanism for the detection of signalling loops is a two step process and requires the co-operation of the underlying switched network in order to succeed. First, the underlying switched network will pass any received Inter-Network Routing Number to the SAS as part of the concerned address (i.e. the SCCP Called Party Address GTAI). This first step signals the SAS Loop Detection algorithm that the signalling message has originated outside of the current signalling network. Secondly, the E.164 database(s) search must resolve to a combination of the pair (E.164 Number Type, Portability Status) that is marked as a candidate for looping. With these two criteria met, the signalling loop is detected.
This implies, that there has to be configuration table which indicates for each pair (E.164 Number Type, Portability Status), whether loop detection is to be enabled or not.
As a temporary relaxation of the SAS Loop Detection, the Transition Time capability was introduced. This provides a synchronisation period for recent database updates. If the Transition Indicator is marked “Transition Time is not yet over”, then the SAS Loop Detection is either bypassed or relaxed.
Configuration tables control Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example. The SAS Application Service is the same as the one used above: FNP-Signalling Relay Function (FNP-SRF).
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string.
There are the following configurable outbound actions for this Service Handler:
Configuration Data:
Table 11 shows Details of the Loop Detection Status Configuration Table.
Configuration Items for Outbound Digits Synthesis:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 12 presents the information necessary to specify an input digit string. Table 13 specifies the mapping between the Input Digit String to the Output Digit String. Table 14 specifies the mapping between the Output Digit String and the Protocol Element.
Table 12 shows Details of the Output Digit String Configuration Table.
Table 13 shows Details of the Input Digit String To Output Digit String Mapping Table.
Table 14 shows Details of the Input Digit String To Protocol Element Mapping Table.
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164/MSIN Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. The same principle can in the future be applied to other number ports as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
Table 15 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Normal Completion.
Table 15 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is contained in Table 33.
Table 16 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Abnormal Completion.
Scenarios:
CAP IDP Relay Mobile Number Portability
Short Description
This service includes CAP IDP Relay MNP (Mobile Number Portability) with optionally voice mail. All these combinations are configurable.
In short, the service use the address information contained in the CAP IDP data to interrogate the subscriber database. The contents of the database (i.e. Routing Numbers) are inserted into the data layer address information and the IDP message is onward routed.
The three stages of the Application Service
Inbound Message Analysis:
This stage analyses the core part of the received number in the Single Number and Range Number tables. The Extended Match Indicator is to be used if required. The Service Decision is executed dependent on configuration data items and the Transition Indicator, the Default/Exception Indicator, and the Single Number Flag of the Single Number and Range Number tables.
For those SAS Application Services that are required to search the E.164 or MSIN Based Tables for routing information, the following principles apply. The search of the E.164 or MSIN Based Tables constitutes the main service decision.
Database Search:
The Evaluation of Database Search Indication is a SAS Application Service specific matter, also the decision whether or not to perform another SAS Database search. The Application Specific Evaluation of Database Search Indications includes some specific actions. Both, the application specific evaluations and the decision for further database searches, depend on the SAS Application Service's service logic, configurable items such as “Open/Closed Numbering Plan”, “Block/Single Number Dialling”, “Request More Digits Yes/No”, and other things.
Table 1 shows E.164 Single Number Table for the Example.
Table 2 shows E.164 Range Number Table for the Example.
Table 3 shows Service Control Data Table for the Example.
Table 4 shows Service Control Slots Configuration Table for the Example.
Outbound Message Synthesis:
Depending on the result of this database query and the inbound processing, the response is generated. Outbound processing is configured based on the specification of the digit string to be sent off, the Service Control Data Record, the Number Type and the Portability Status, and other configuration data items.
Configuration tables control the Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example. The SAS Application Service is the same as the one used above in the Cap IDP Relay with Optional Voice Mail Inter-working.
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string.
There is only one configurable outbound action for this Service Handler:
Configuration Data:
Configuration Items for Outbound Digits Synthesis:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 12 presents the information necessary to specify an input digit string. Table 13 specifies the mapping between the Input Digit String to the Output Digit String. Table 14 specifies the mapping between the Output Digit String and the Protocol Element.
Table 12 shows Details of the Output Digit String Configuration Table.
Table 13 shows Details of the Input Digit String to Output Digit String Mapping Table.
Table 14 shows Details of the Input Digit String to Protocol Element Mapping Table.
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164/MSIN Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
Table 15 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Normal Completion.
Table 15 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is contained in Table 39.
Table 16 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Abnormal Completion.
Scenarios:
INAP IDP Relay (Prepaid I/W)
Short Description:
This service includes INAP IDP Relay (Prepaid/I/W) with optionally voice mail; IDP=Initial DP. All these combinations are configurable.
In short, the service use the address information contained in the INAP IDP data to interrogate the subscriber database. The contents of the database (i.e. Routing Numbers) are inserted into the data layer address information and the IDP message is onward routed.
The three stages of the Application Service:
Inbound Message Analysis:
This stage analyses the core part of the received number in the Single Number and Range Number tables. The Extended Match Indicator is to be used if required. The Service Decision is executed dependent on configuration data items and the Transition Indicator, the Default/Exception Indicator, and the Single Number Flag of the Single Number and Range Number tables.
For those SAS Application Services that are required to search the E.164 or MSIN Based Tables for routing information, the following principles apply. The search of the E.164 or MSIN Based Tables constitutes the main service decision.
Database Search:
The Evaluation of Database Search Indication is a SAS Application Service specific matter, also the decision whether or not to perform another SAS Database search. The Application Specific Evaluation of Database Search Indications includes some specific actions. Both, the application specific evaluations and the decision for further database searches, depend on the SAS Application Service's service logic, configurable items such as “Open/Closed Numbering Plan”, “Block/Single Number Dialling”, “Request More Digits Yes/No”, and other things.
Table 1 shows E.164 Single Number Table for the Example.
Table 2 shows E.164 Range Number Table for the Example.
Table 3 shows Service Control Data Table for the Example.
Table 4 shows Service Control Slots Configuration Table for the Example.
Outbound Message Synthesis:
Depending on the result of this database query and the inbound processing, the response is generated. Outbound processing is configured based on the specification of the digit string to be sent off, the Service Control Data Record, the Number Type and the Portability Status, and other configuration data items.
Configuration tables control the Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example. The SAS Application Service is the same as the one used above in the INAP IDP Relay with Optional Voice Mail Inter-working.
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string.
There are only two configurable outbound actions for this Service Handler:
Configuration Data:
Configuration Items for Outbound Digits Synthesis:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 12 presents the information necessary to specify an input digit string. Table 13 specifies the mapping between the Input Digit String to the Output Digit String. Table 14 specifies the mapping between the Output Digit String and the Protocol Element.
Table 12 shows Details of the Output Digit String Configuration Table.
Table 13 shows Details of the Input Digit String to Output Digit String Mapping Table.
Table 14 shows Details of the Input Digit String to Protocol Element Mapping Table.
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164/MSIN Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
Table 15 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Normal Completion.
Table 15 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is contained in Table 44.
Table 16 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Abnormal Completion.
Scenarios:
Mobile SCCP Routing
Short Description:
This service realizes Number Portability on SCCP level for mobile networks (e.g. Signalling Relay Function (SRF), Non Call Related Service (NCR), Flexible Routing (FLR)).
The three stages are described in detail as follows:
For those SAS Application Services that are required to search the E.164 or MSIN Based Tables for routing information, the following principles apply. The search of the E.164 or MSIN Based Tables constitutes the main service decision.
The Evaluation of Database Search Indications is a SAS Application Service specific matter, also the decision whether or not to perform another SAS Database search. Both, the application specific evaluations and the decision for further database searches, depend on the SAS Application Service's service logic, configurable items and other things.
Loop Detection is a mechanism to discover inconsistencies in the received data, which might be caused by a condition that causes the SS7 message to loop through the SS7 network. There are two kinds of loop detection: a generic one and an application specific one. The generic one is specified in detail here. The applications specific ones are specified at the respective SAS Application Services.
Table 1 shows E.164 Single Number Table for the Example.
Table 2 shows E.164 Range Number Table for the Example.
Table 3 shows Service Control Data Table for the Example.
Table 4 shows Auxiliary Number Table for the Example.
Detection of Loops and other Inconsistencies:
Loop detection is provided to prevent signalling loops within the signalling network. Signalling loops may occur when the routing databases in different signalling networks contain inconsistent routing information for network subscribers. The ability to detect signalling loops is defined within the scope of each SAS Application Service and may not be present in all SAS Application Services. Also, the response taken to the detection of a signalling loop is defined within the scope of each SAS Application Service.
As stated above, there is a Generic Loop Detection mechanism, which applies to many SAS Application Service, and there are SAS Application Service specific Loop Detection mechanisms. The Generic Loop Detection mechanism is in detail specified here. The SAS Application Service specific Loop Detection mechanisms are outlined here and are specified at the respective SAS Application Service.
Generic Loop Detection Analysis:
The generic mechanism for the detection of signalling loops is a two step process and requires the co-operation of the underlying switched network in order to succeed. First, the underlying switched network will pass any received Inter-Network Routing Number to the SAS as part of the concerned address (i.e. the SCCP Called Party Address GTAI). This first step signals the SAS Loop Detection algorithm that the signalling message has originated outside of the current signalling network. Secondly, the E.164 database(s) search must resolve to a combination of the pair (E.164 Number Type, Portability Status) that is marked as a candidate for looping. With these two criteria met, the signalling loop is detected.
This implies, that there has to be configuration table which indicates for each pair (E.164 Number Type, Portability Status), whether loop detection is to be enabled or not.
As a temporary relaxation of the SAS Loop Detection, the Transition Time capability was introduced. This provides a synchronisation period for recent database updates. If the Transition Indicator is marked “Transition Time is not yet over”, then the SAS Loop Detection is either bypassed or relaxed.
Configuration tables control Outbound Message Synthesis. The configuration tables of the Outbound Message Synthesis are illustrated by an example. The SAS Application Service is the same as the one used above: MNP-Non Call Related Service (MNP-NCR).
An Output Address includes the triple (NoAI, Numbering Plan, Digit String). The Output Digit String Configuration Table specifies the necessary output digit strings of the SAS Application Service, including a NoAI value. The value for Numbering Plan is implicitly present in the service logic of the SAS Application Service. Memory has to be allocated for the digit string elements of the Output Digit String Configuration Table, plus for Nat1 and Nat2 or Nat.
The SAS Application Service Specific Outbound Processing Configuration Table for Normal and Abnormal Completion contains up to 10 Response Actions. One or more of these Response Actions can be used to insert configured values at defined positions in the output digit string.
There are the following configurable outbound actions for this Service Handler:
Configuration Data:
Table 11 shows Details of the Loop Detection Status Configuration Table.
Configuration Items for Outbound Digits Synthesis:
Each SAS Application Service shall have a configuration data item, which specifies the structure of each possible output digit string on the basis of its general abstract structure. Each output digit string is associated to a protocol parameter to which it is sent. It is even possible to associate more than one output digit string to a given protocol parameter. The structure of the output digit string is specified by the list of its auxiliary numbers. The following information shall be specified for each output digit string. Table 12 presents the information necessary to specify an input digit string. Table 13 specifies the mapping between the Input Digit String to the Output Digit String. Table 14 specifies the mapping between the Output Digit String and the Protocol Element.
Table 12 Details of the Output Digit String Configuration Table.
Table 13 Details of the Input Digit String To Output Digit String Mapping Table.
Table 14 Details of the Input Digit String To Protocol Element Mapping Table.
A single output digit sting shall be able to be selected—based on its Id—from a set of possible output digit strings. The selection is done based on the value combination of (E.164/MSIN Number Type, Portability Status). A table has to be present to specify this configuration data.
It shall be possible to specify which Service Control Slot (i.e. Service Control Data Sequence Number) of the found entry in the single number or range number table is to be used in the outbound processing depending on the value combination of (E.164 Number Type, Portability Status). A table has to be present to specify this configuration data. The same principle can in the future be applied to other number parts as well.
It shall be possible to specify which action is to be done in the outbound digit processing depending on the value combination of (E.164 Number Type, Portability Status). Possible actions are the type of message to be used, etc. A table has to be present to specify this configuration data. The same principle can in the future be applied to other number ports as well.
Table 15 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Normal Completion.
Table 15 contains the application specific outbound processing in case an entry was found in the Single Number or Range Number Table. However, it is possible that no entry is found in both tables. This abnormal outbound processing is contained in Table 50.
Table 16 shows Details of the SAS Application Service Specific Outbound Processing Configuration Table—Abnormal Completion.
Scenarios:
In all seven embodiments of the invention the specific configurations in the tables are examples. Other configurations are possible. The specific scenarios are also examples. Other scenarios are possible.
The SAS and the SS7 signaling server are each able to process at least one SAS Application Service request. The SAS may process one, two, three, . . . , or seven different SAS Application Service requests according to the seven embodiments of the invention, thus implementing part of the embodiments or all seven at the same time, or may process alternatively or in addition other service requests. The functionality of the SAS can easily be modified by software reprogramming and reconfiguration. The same applys to the SS7 signaling server.
| Number | Date | Country | Kind |
|---|---|---|---|
| 03290703 | Mar 2003 | EP | regional |
| Number | Name | Date | Kind |
|---|---|---|---|
| 5712908 | Brinkman et al. | Jan 1998 | A |
| 5768361 | Cowgill | Jun 1998 | A |
| 6011803 | Bicknell et al. | Jan 2000 | A |
| 6366658 | Bjornberg et al. | Apr 2002 | B1 |
| 6535599 | Torrey et al. | Mar 2003 | B1 |
| 6631186 | Adams et al. | Oct 2003 | B1 |
| 6662017 | McCann et al. | Dec 2003 | B1 |
| 6714533 | Weich et al. | Mar 2004 | B1 |
| 6731741 | Fourcand et al. | May 2004 | B1 |
| 6826198 | Turina et al. | Nov 2004 | B1 |
| 20010029182 | McCann et al. | Oct 2001 | A1 |
| 20020131400 | Tinsley et al. | Sep 2002 | A1 |
| 20030228012 | Williams et al. | Dec 2003 | A1 |
| 20050152383 | Schantz | Jul 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 1 139 674 | Oct 2001 | EP |
| Number | Date | Country | |
|---|---|---|---|
| 20040184594 A1 | Sep 2004 | US |
