INAP InitialDP Service Handler

Introduction

The INAP InitialDP Service Handler provides access to services provided by SS7 DB Application by way of the INAP protocol. 

Definitions

The following definitions of terms apply to this document.

Acronyms

General Description

SS7 DB Applications (SDA) allows for flexible routing of messages within the signaling network. It accomplishes this through a combination of Gateway Screening rules, Signaling Gateway Service Handler connections to unique SDA routing functions (termed Service Handlers), and subscriber data services.

Specifically for the INAP InitialDP message, the GWS table “Allowed TCAP OpCode” must have a rule for TCAP Opcode 0 to ensure that only the InitialDP message is redirected to the SDA Service Handler.

Product Perspective

The INAP InitialDP Service Handler provides access to services provided by SDA by way of the INAP protocol. In particular, the InitialDP operation within the INAP protocol provides the mechanism to the signaling network to retrieve information from various services within SDA.

The following services are available for selection and application from the INAP InitialDP Service Handler:

• the TCAP Screening Service– allows the Service Handler to decide if the originator of the query is allowed to send the INAP InitialDP request.
• the ETSI Subscriber Routing Service – allows subscriber-by-subscriber routing decisions to be made.
• the ETSI Number Portability Service – allows the Service Handler to derive a routing number.
• the ETSI Digit Analysis Service – allows the Service Handler to recognize different components of a telephone number
• the ETSI Loop Detection Analysis Service – allows the Service Handler to recognize if a network loop exists related to the porting of subscribers between networks.
• the INAP Content Screening Service - allows the Service Handler to verify the INAP Parameter Content.
• the ETSI Multi-Country Number Portability Service - allows the Service Handler to derive routing numbers
• the Service Key Routing Service - allows the Service Handler to derive a routing number
• the ETSI Multi-Country Digit Analysis Service – allows the Service Handler to recognize different components of a telephone number for the multi-country number portability
• the ETSI Multi-Country Loop Detection Analysis Service – allows the Service Handler to recognize if a network loop exists related to the porting of subscribers between networks for the multi-country number portability.

• OICK- is implemented as a special case of external networks by including the external network digits in the modified digits.

  A Service Handler invokes different services depending on the routing requirements of the customer. This combination of services is determined by analysis of the customer's network routing. Although certain services could work standalone, most functionalities, like Number Portability, inherently require the use of a minimum combination of services. Number Portability's minimum set of services is ETSI Digit Analysis, ETSI Number Portability and ETSI Loop Detection Analysis.

Functional Description

The INAP InitialDP Service Handler has the following functional components:

• TCAP Syntax Verification – the process by which the syntax of the TCAP Layer is verified prior to using information from the message
• INAP Syntax Verification – the process by which the syntax of the received message is verified prior to using information from the message for the various services.
• Service Control – the process by which services are determined to be applicable or not (and are applied)
• Service Event Handling – the process of interpreting the results of an applied service

Product Functions

With the capabilities described in this requirement document, the INAP InitialDP Service Handler feature supports:

• INAP InitialDP routing requests
• authentication of the query source
• authentication of the message rate

User Pre-requisites

To fully assess the impact of the INAP InitialDP Service Handler, the user must have knowledge in the following areas:

• General functionality of the Signaling Server Global
• SCCP routing
• TCAP protocol
• INAP/CAMEL protocol

Functional Requirements

The INAP InitialDP Service Handler is responsible for the following items:

• TCAP syntax verification – a mechanism that verifies the integrity of the structure of the received. TCAP signaling message. This is basic protocol verification of structure and compliance to governing signaling standards.
• INAP/CAMEL syntax verification – a mechanism that verifies the integrity of the structure of the received. IDP operation. This is basic protocol verification of structure and compliance to governing signaling standards.
• Service Control – a mechanism that determines when and if a service is applied.
• Service Event Handling – after a service has been applied; the results of the service need to be interpreted by the Service Handler's message handling logic. For example, the results from the Number Portability and Loop Detection services can drive whether the message is simply relayed to the SCP or if an IDP Connect or IDP Continue is returned to the MSC.

INAP InitialDP Service Handler Overview

The preceding figure displays a visual representation of the order of services within the Service Handler. The TCAP and INAP Syntax Verification functions are applied regardless of user selection, as they must verify the integrity of the signaling message prior to using the information contained in the signaling message.

General Requirements

When the last INAP operation is to be returned for the INAP dialogue by the INAP InitialDP Service table indicates BASIC END.

When the last INAP operation is to be returned for the INAP dialogue by the INAP InitialDP Service Handler, then a TC-Continue shall be used when the dialogueTerminationState column of the shConfiguration table indicates PRE-ARRANGED END.

If the responseRouting column of the found shConfiguration record for the Service Handler indicates that response routing should be routed using MTP routing only (responseRouting = MTP), then the Service Handler shall route all responses using MTP routing only.

If the responseRouting column of the found shConfiguration record for the Service Handler indicates that response routing should be routed using SCCP routing (responseRouting = SCCP), then the Service Handler shall route all responses using SCCP routing.

TCAP Syntax Verification

The INAP InitialDP Service Handler relies on TCAP for dialogue management between the Service Handler and the originating TC-user. As such, the INAP InitialDP Service Handler must support all TCAP primitives and processing requirements for the TCAP messages that are necessary to deliver the services allowed by the Service Handler.

The INAP InitialDP Service Handler expects the following from TCAP:

• a message type of TC-Begin
• a component type of Invoke
• a local operation of IDP (0)
  

Depending on the Services that have been applied, the following INAP operations are supported by the Service Handler:

• InitialDP – this is the primary operation supported by the Service Handler and all applied services. This is the operation that is expected in the first TCAP message received (TC-Begin). All services can be applied (when selected) based on information contained within this message.
• Event Report BCSM – the Service Handler supports this operation since the Service Handler may have previously sent a RequestReportBCSM operation to the originating TC-User. There are two responses that send a RequestReportBCSM.
  • Resolve Ambiguity – this expects the Event Report BCSM to have additional information about the Called Party Number (the reason for the ambiguity resolution). If the Event Report BCSM contains additional information about the Called Party Number, then the services can be reapplied now that there is more information available.
• • Connect To Resource, Play Announcement – this expects the Event Report BCSM to be in combination with the Specialized Resource Report that signifies that the announcement has been played and completed. There are no other services to apply since this is notification of the announcement having been completed.

• Specialized Resource Report – this operation is supported by the Service Handler when received with an Event Report BCSM. This combination is received in response to the message sent by the Service Handler from the Connect To Resource, Play Announcement response.

  • This combination of operations (Event Report BCSM and Specialized Resource Report) will have its own response for selection.

The INAP InitialDP Service Handler shall support TCAP.

The INAP InitialDP Service Handler shall return a TC-Abort to the message originator if

• the TCAP Transaction Portion is not consistent with a TC-Begin, however is otherwise validly structured, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError)

The INAP InitialDP Service Handler shall route the signaling message to the current SCCP destination if

• the TCAP Transaction Portion is not consistent with a TC-Begin, however is otherwise validly structured, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates that the signaling message is to be routed (errorAction = ContinueRouting)

The INAP InitialDP Service Handler shall return a TC-Abort to the message originator if

• the Message Type is a TC-Begin, and
• the Component Type is not an Invoke Component type, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError)

The INAP InitialDP Service Handler shall return a TC-End with Release Call operation to the message originator if

• the Message Type is a TC-Continue, and
• the Component Type is not an Invoke Component type, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError)

The INAP InitialDP Service Handler shall route the signaling message to the current SCCP destination if

• the Component Type is not an Invoke Component type, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates that the signaling message is to be routed (errorAction = ContinueRouting)

The INAP InitialDP Service Handler shall return a Reject Component with a Reject Reason of “Unrecognized Operation” if

• a new dialogue request is received (as indicated by the TC-Begin Transaction Portion) and the Operation Code is not an InitialDP Operation (as defined within EN 301 140-1 ), and
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError).

The INAP InitialDP Service Handler shall route the signaling message to the current SCCP destination if

• a new dialogue request is received (as indicated by the TC-Begin Transaction Portion) and the Operation Code is not an InitialDP Operation (as defined within EN 301 140-1 ), and
• the errorAction column of the found shConfiguration record for the Service Handler indicates that the signaling message is to be routed (errorAction = ContinueRouting)

The INAP InitialDP Service Handler shall return a Reject Component with a Reject Reason of “Unrecognized Operation” if

• a continuing dialogue request is received and the following is contained:
  • an Event Report BCSM and
  • the transaction was expecting an Event Report BCSM as a result of a previous Connect To Resource, Play Announcement response
  • the Specialized Resource Report operation is not present, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError).

The INAP InitialDP Service Handler shall route the signaling message to the current SCCP destination if

• a continuing dialogue request is received and the following is contained:
  • an Event Report BCSM and
  • the transaction was expecting an Event Report BCSM as a result of a previous Connect To Resource, Play Announcement response
  • the Specialized Resource Report operation is not present, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates that the signaling message is to be routed (errorAction = ContinueRouting).

The INAP InitialDP Service Handler shall return a Reject Component with a Reject Reason of “Unrecognized Operation” if

• a continuing dialogue request is received and the following is contained:
  • an Event Report BCSM and
  • the transaction was not expecting an Event Report BCSM as a result of any previous response
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError).

The INAP InitialDP Service Handler shall route the signaling message to the current SCCP destination if:

• a continuing dialogue request is received and the following is contained:
  • the errorAction column of the found shConfiguration record for the Service Handler indicates that the signaling message is to be routed (errorAction = ContinueRouting)
  • an Event Report BCSM and
  • the transaction was not expecting an Event Report BCSM as a result of any previous response.

If a continuing dialogue request is received (as indicated by the TC-Continue Transaction Portion) and the following is contained:

• an Event Report BCSM and
• the transaction was expecting an Event Report BCSM as a result of resolving an ambiguity then all services defined in INAP Syntax Verification shall be applied using a combination of data from the original InitialDP and the Event Report BCSM.

If a continuing dialogue request is received and the following is contained:

• an Event Report BCSM and
• the transaction was expecting an Event Report BCSM as a result of a previous Connect To Resource, Play Announcement response, and
• the Specialized Resource Report operation is present

Then the INAP InitialDP Service Handler shall return a response message containing the following INAP operations:

• DisconnectForwardConnection
• Continue

INAP Syntax Verification

After the TCAP Layer(s) have been successfully verified, the data delivered by TCAP (INAP InitialDP) must be verified. The purpose of this process is to ensure that the InitialDP parameter set has values necessary for the Service Handler. The IDP message must contain the necessary information to allow the Service Handler to perform its database interrogation. The validation of the required parameters within the structure of the INAP InitialDP parameter sequence is in accordance with the governing standards.

The parameter data set is verified only up to the point necessary to derive the information with which to interrogate the database (i.e. the CalledPartyBCD parameter). Parameters that may be present before or after the point at which all necessary information has been retrieved are not validated, or examined, by the Service Handler.

 The INAP InitialDP Service Handler shall return a Return Error Component with Error Code of “Missing Parameter” to the message originator if

• the InitialDP Operation data does not contain the “Service Key” parameter, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates an error is to be returned (errorAction = ReturnError)

The INAP InitialDP Service Handler shall route the signaling message to the current SCCP destination if

• the InitialDP Operation data does not contain the “Service Key” parameter, and
• the errorAction column of the found shConfiguration record for the Service Handler indicates that the signaling message is to be routed (errorAction = ContinueRouting)

Service Control

The INAP InitialDP Service Handler can apply the following services based on user configuration:

• TCAP Screening Service
• ETSI Subscriber Routing Service
• ETSI Number Portability Service
• ETSI Digit Analysis Service
• ETSI Loop Detection Analysis Service
• INAP Content Screening Service
• ETSI Multi-Country Number Portability Service
• Service Key Routing Service
• ETSI Multi-Country Digit Analysis Service
• ETSI Multi-Country Loop Detection Analysis Service
• OICK code included in local prepaid messages.

The Service Handler shall search the shServiceDescription table using the Service Handler’s identity in order to find the list of services and the order of services to be applied.

The Service Handler shall route the signaling message to the current SCCP destination if the search of the shServiceDescription table indicates not found (meaning there is no service to be applied, or all services were applied and no specific response was selected).

For each service that is found in the shServiceDescription table, the Service Handler shall apply the identified service.

After application of each service, the Service Handler shall use the event indicated by the service to search the Service Handler’s event table for the applied service (for example, the shSRSEvent table is the Service Handler’s event table for the ETSI Subscriber Routing Service).

If the search of the Service Handler’s event table for the applied service indicates not found, then the next service identified from the shServiceDescription table shall be applied.

The next service identified from the shServiceDescription table shall be applied if

• the search of the Service Handler’s event table for the applied service indicates found and
• no response is selected or the relay response is selected and
• the nextAction column of the found Service Handler’s event table entry indicates that the next service is to be applied (nextAction = Continue)

After a service is applied, the signaling message shall be routed if

•  no response is selected or a response was selected that allows another service to be applied and
•  the nextAction column of the found Service Handler’s event table entry indicates that the next service cannot be applied (nextAction = Stop)

The signaling message shall be routed regardless of the selection in the nextAction column of the found Service Handler’s event table entry if the response selected is one of the following:

• Return Error
• Continue
• Release Call
• Resolve Ambiguity
• Play announcement
• Connect

If the search of the Service Handler’s event table for the applied service indicates found and the returnError column references a valid response, then the TCAP Return Error message shall be created according to the requirements in Section Return Error.

If the search of the Service Handler’s event table for the applied service indicates found and the continue column indicates that a Continue message is to be sent to the message originator (continue = Yes), then the Continue message shall be created according to the requirements in Section Continue.

If the search of the Service Handler’s event table for the applied service indicates found and the releaseCall column references a valid response, then the Release Call message shall be created according to the requirements in Section Release Call.

If the search of the Service Handler’s event table for the applied service indicates found and the resolveAmbiguity column references a valid response, then the Resolve Ambiguity response shall be created according to the requirements in Section Resolve Ambiguity.

If the search of the Service Handler’s event table for the applied service indicates found and the pAnnouncement column references a valid response, then the Play Announcement response shall be created according to the requirements in Section Connect To Resource and Play Announcement.

If the search of the Service Handler’s event table for the applied service indicates found and the connect column references a valid response, then the Connect message shall be created according to the requirements in Section Connect.

If the search of the Service Handler’s event table for the applied service indicates found and the relay column references a valid response, then the SCCP Called Party Address shall be created according to the requirements in Section Relay Signaling Message.

TCAP Screening Service

The TCAP Screening Service requires the complete signaling message. Therefore the Service Handler will allow the service to have full access to the signaling message.

The TCAP Screening Service shall be applied using the complete signaling message.

ETSI Subscriber Routing Service

The ETSI Subscriber Routing Service requires that a Subscriber Number is present. The selection of the INAP InitialDP parameter to be used for the Subscriber Number is listed in the initialDPListForSN table. If the INAP InitialDP does not contain the parameter designated to be used for the Subscriber Number, then the ETSI Subscriber Routing Service cannot be applied. The reason that the ETSI Subscriber Routing Service cannot be applied in this case is due to the absence of any data on which to apply the routing service.

If an InitialDP is received then the INAP InitialDP Service Handler shall take the parameter listed in the sn1 column of the referenced initialDPListForSN table entry to use as the Subscriber Number for the ETSI Subscriber Routing Service.

If an InitialDP is received and if no parameter can be found within the received INAP InitialDP that matches to a parameter designated for use as the Subscriber Number in the ETSI Subscriber Routing Service as defined in the sn(n) column of the referenced initialDPListForSN table entry, then the ETSI Subscriber Routing Service shall not be applied.

If an EventReportBCSM is received with the “eventTypeBCSM” of “collectedInfo”, then the INAP InitialDP Service Handler shall take the parameter listed in the erbListforSN column of the shConfiguration table to use as the Subscriber Number for the ETSI Subscriber Routing Service.

If an EventReportBCSM is received with the “eventTypeBCSM” of “collectedInfo” and if no parameter can be found within the received EventReportBCSM that matches to a parameter designated for use as the Subscriber Number in the ETSI Subscriber Routing Service as defined in the erbListforSN column of the shConfiguration table, then the ETSI Subscriber Routing Service shall not be applied.

The ETSI Subscriber Routing Service shall be applied using the National Significant portion of the Subscriber Number (refer to Table INAP PARAMETERS FOR THE ETSI DIGIT ANALYSIS SERVICE and Table INAP DIGIT STRING DETERMINATION TABLE).

ETSI Number Portability Service

The ETSI Number Portability Service requires that a Subscriber Number is present. The selection of the INAP InitialDP parameter to be used for the Subscriber Number is listed in the initialDPListForSN table. If the INAP InitialDP does not contain the parameter designated to be used for the Subscriber Number, then the ETSI Number Portability Service cannot be applied. The reason that the ETSI Number Portability Service cannot be applied in this case is due to the absence of any data on which to apply the routing service.

If an InitialDP is received then the INAP InitialDP Service Handler shall take the parameter listed in the sn1 column of the referenced initialDPListForSN table entry to use as the Subscriber Number for the ETSI Number Portability Service.

If an InitialDP is received and if no parameter can be found within the received INAP InitialDP that matches to a parameter designated for use as the Subscriber Number in the ETSI Number Portability Service as defined in the sn(n) column of the referenced initialDPListForSN table entry, then the ETSI Number Portability Service shall not be applied.

If an EventReportBCSM is received with the “eventTypeBCSM” of “collectedInfo”, then the INAP InitialDP Service Handler shall take the parameter listed in the erbListforSN column of the shConfiguration table to use as the Subscriber Number for the ETSI Number Portability Service.

If a EventReportBCSM is received with the “eventTypeBCSM” of “collectedInfo” and if no parameter can be found within the received EventReportBCSM that matches to a parameter designated for use as the Subscriber Number in the ETSI Number Portability Service as defined in the erbListforSN column of the shConfiguration table, then the ETSI Number Portability Service shall not be applied.

The ETSI Number Portability Service shall be applied using the National Significant portion of the Subscriber Number (refer to INAP PARAMETERS FOR THE ETSI DIGIT ANALYSIS SERVICE and Table INAP DIGIT STRING DETERMINATION TABLE).

ETSI Multi-Country Number Portability Service

The ETSI Multi-Country Number Portability Service requires that a Subscriber Number is present. The selection of the INAP InitialDP parameter to be used for the Subscriber Number is listed in the initialDPListForSN table. If the INAP InitialDP does not contain the parameter designated to be used for the Subscriber Number, then the ETSI Multi-Country Number Portability Service cannot be applied. The reason that the ETSI Multi-Country Number Portability Service cannot be applied in this case is due to the absence of any data on which to apply the routing service.

If an InitialDP is received then the INAP InitialDP Service Handler shall take the parameter listed in the sn1  column of the referenced initialDPListForSN table entry to use as the Subscriber Number for the ETSI Multi-Country Number Portability Service.

If an InitialDP is received and if no parameter can be found within the received INAP InitialDP that matches to a parameter designated for use as the Subscriber Number in the ETSI Multi-Country Number Portability Service as defined in the sn(n) column of the referenced initialDPListForSN table entry, then the ETSI Multi-Country Number Portability Service shall not be applied.

If an EventReportBCSM is received with the “eventTypeBCSM” of “collectedInfo”, then the INAP InitialDP Service Handler shall take the parameter listed in the erbListforSN column of the shConfiguration table to use as the Subscriber Number for the ETSI Multi-Country Number Portability Service.

If a EventReportBCSM is received with the “eventTypeBCSM” of “collectedInfo” and if no parameter can be found within the received EventReportBCSM that matches to a parameter designated for use as the Subscriber Number in the ETSI Multi-Country Number Portability Service as defined in the erbListforSN column of the shConfiguration table, then the ETSI Multi-Country Number Portability Service shall not be applied

The Subscriber Number digits format shall be determined based on INAP DIGIT STRING DETERMINATION TABLE.

The ETSI Multi-Country Number Portability Service shall be applied using the Subscriber Number (CC + National Number) (refer to INAP PARAMETERS FOR THE ETSI DIGIT ANALYSIS SERVICE)

If the ETSI Multi-Country Digit Analysis Service is not applied, and the Subscriber Number digits format determined is International, then the ETSI Multi-Country Number Portability Service  shall be applied using the digit string that is received as follows:

• If the Nature of Address is Unknown then the digits excluding first two digits in the digit sequence (zeros) shall be used.
• If the Nature of Address is International then the complete digit string shall be used

If the ETSI Multi-Country Digit Analysis Service is applied, and the Subscriber Number digits format determined is International, then the Country Code supplied by the ETSI Multi-Country Digit Analysis Service shall be prefixed to the national portion of the Subscriber Number digits prior to applying the ETSI Multi-Country Number Portability Service.

If the Subscriber Number digits format determined is National, then the value indicated in the countryCode column of the defaultCCForMCntNP table shall be prefixed to the Subscriber Number digits prior to applying the ETSI Multi-Country Number Portability Service.

If the Subscriber Number digits format determined is National and the countryCode column of the defaultCCForMCntNP table is not provisioned, then the value indicated in the countryCode column of the general table shall be prefixed to the Subscriber Number digits prior to applying the ETSI Multi-Country Number Portability Service.

If the Subscriber Number digits format determined is National and if the Country Code is not provisioned in both defaultCCForMCntNP table and general table, then the ETSI Multi-Country Number Portability Service shall not be applied.

ETSI Digit Analysis Service

The ETSI Digit Analysis Service provides the Service Handler the ability to recognize different components of a telephone number. The ETSI Digit Analysis Service requires the subscriber number and the type of number as inputs for applying the service.  

The table gives the description of the input parameters:

INAP Parameters for the ETSI Digit Analysis Service

INAP Digit String Determination table

The ETSI Digit Analysis Service shall be applied using the following:

• the Subscriber Number 
• the Type of Number

ETSI Loop Detection Analysis Service

The ETSI Loop Detection Analysis Service requires the event generated by the ETSI Digit Analysis Service and the event generated by the ETSI Number Portability Service as inputs for applying the service.
If the dependent services are not applied, then an empty reference will be used for the missing analysis component.

The ETSI Loop Detection Analysis Service shall be applied using the following as input:

•  the event generated by the ETSI Digit Analysis Service or empty reference (NULL), if ETSI Digit Analysis Service is not applied and, 
•  the event generated by the ETSI Number Portability Service or empty reference (NULL), if ETSI Number Portability Service is not applied

INAP Content Screening Service

The INAP Content Screening Service provides the Service Handler the ability to verify the INAP Parameter Content.

The INAP Content Screening Service shall be applied using the complete received INAP InitialDP operation data.

Service Key Routing Service

The Service Key Routing Service provides the routing information related to the received Service Key parameter.

The Service Key Routing Service shall be applied using the received Service Key parameter

ETSI Multi-Country Digit Analysis Service

The ETSI Multi-Country Digit Analysis Service provides the Service Handler the ability to recognize different components of a telephone number for the Multi-Country Number Portability. The ETSI Multi- Country Digit Analysis Service requires the following input information for applying the service:

• subscriber number
• type of number

The following table shows the description of the input parameters:

Input Parameters for the ETSI Multi-Country Digit Analysis Service

The ETSI Multi-Country Digit Analysis Service shall be applied using the following:

• the Subscriber Number
• the Type of Number
  

ETSI Multi-Country Loop Detection Analysis Service

The ETSI Multi-Country Loop Detection Analysis Service requires the following input information:

• the event generated as a result of the application of the ETSI Multi-Country Digit Analysis Service, and
• the event generated as a result of the application of the ETSI Multi-Country Number Portability Service

If the dependent services are not applied, then an empty reference will be used for the missing analysis component. The following table shows the description of the input parameters:

Input Parameters for the ETSI Multi-Country Loop Detection Analysis Service

The ETSI Multi-Country Loop Detection Analysis Service shall be applied using the following as input:

• the event generated by the ETSI Multi-Country Digit Analysis Service or empty reference (NULL), if ETSI Multi-Country Digit Analysis Service is not applied, and
• the event generated by the ETSI Multi-Country Number Portability Service or empty reference (NULL), if ETSI Multi-Country Number Portability Service is not applied

Support OICK code

OICK codes are implemented as a special case of external networks by including the external network digits in the modified digits.

When the called digits are to be modified the column initialDPBCDNPRN in the table initialDPCalledPartyBCD table, it indicates the format for the returned new number.
The existing formats include:

• No - indicates that the digits are to be left unchanged.
• Yes - indicates the legacy format that depends on the type of number.
• ton_natl_cc_n_rn_y
• ton_intl_cc_y_rn_y
• ton_unkn_cc_y_rn_y
• ton_unkn_cc_n_rn_y

For international numbers the new digits are <country code><routing network> <called party digits>, otherwise the digits are <routing network> <called party digits>. The remainder types have the digits in the order <country code><routing network><called party digits>, where the types that have cc_n having no digits for the country code.

To support OICK an external network part is added to the new number: <country code><routing network><external network><called party digits>.

New formats for non-empty external networks are

• ton_natl_cc_y_rn_y_en_y
• ton_natl_cc_n_rn_y_en_y
• ton_intl_cc_y_rn_y_en_y
• ton_intl_cc_n_rn_y_en_y
• ton_unkn_cc_y_rn_y_en_y
• ton_unkn_cc_n_rn_y_en_y

If any component of the reconstructed by the rule are not found in the original incoming called digits for example enter network, then no digits will be inserted in its place, but processing will continue.

For the existing formats described above, the external network will be zero digits long.

In addition the column  inap_shdb.initialDPCalledParty.initialDPNPRN will be modified from having the enumeration"Yes", "No" to the enumeration

• Yes,
• No,
• noa_natl_cc_y_rn_y_en_y
• noa_natl_cc_n_rn_y_en_y
• noa_intl_cc_y_rn_y_en_y 
• noa_intl_cc_n_rn_y_en_y 
• noa_unkn_cc_y_rn_y_en_y
• noa_unkn_cc_n_rn_y_en_y
• noa_natl_cc_y_rn_y_en_n
• noa_natl_cc_n_rn_y_en_n
• noa_intl_cc_y_rn_y_en_n 
• noa_intl_cc_n_rn_y_en_n 
• noa_unkn_cc_y_rn_y_en_n
• noa_unkn_cc_n_rn_y_en_n

The formatting of the result digits is as described above.  The Nature Of Address for the output depends of noa_*_.

Result Digits

In this feature, the first action taken is a digit analysis service on the incoming message. Entries are provisioned in the table to search for prefixes, up to 6 digits in length, that match a particular pattern prior to the national digits. The GUI interface can be used for provisioning these tables, but in an sql language, it looks like:

insert into etsi_da_db.extPrefix (start, end, event) values (776, 777, NULL)

It is also possible to use a different table that looks for similar digits prior to international digits.

These tables effectively remove the digits before the number portability. The number remains unchanged when it is relayed to the HLR. From the discussion, it sounded like they needed RN+OICK+NATIONAL digits. It looks like that is development work to add that option to the rebuilding of the called party address.

Responses

The following responses are available to the INAP InitialDP Service Handler.

• Return An Error – this response, when selected, causes a TCAP Return Error component to be returned.
  • This response does not allow other services to be applied once it is taken. The reason being that the Service Handler has decided to send a response to the originator based on an event generated by an applied service. So to continue to apply other services to the signaling message would not be appropriate.
• Continue – this response, when selected, causes an INAP Continue operation to be returned. This response does not allow other services to be applied once it is taken. The reason being that the Service Handler has decided to send a response to the originator based on an event generated by an applied service. So to continue to apply other services to the signaling message would not be appropriate.
• Release Call– this response, when selected, causes an INAP Release Call operation to be returned. This response does not allow other services to be applied once it is taken. The reason being that the Service Handler has decided to send a response to the originator based on an event generated by an applied service. So to continue to apply other services to the signaling message would not be appropriate.Connect To Resource, Play Announcement – this response, when selected, causes the INAP Connect To Resource and Play Announcement operations to be returned. This response does not allow other services to be applied once it is taken. The reason being that the Service Handler has decided to send a response to the originator based on an event generated by an applied service. So to continue to apply other services to the signaling message would not be appropriate.Connect– this response, when selected, causes the INAP Connect to be returned. This response does not allow other services to be applied once it is taken. The reason being that the Service Handler has decided to send a response to the originator based on an event generated by an applied service. So to continue to apply other services to the signaling message would not be appropriate.
• Resolve Ambiguity-this response, when selected, causes the INAP Request Report BCSM and Collect Information operations to be returned. Selecting this response would be appropriate when the result of the subscriber number database search indicates AMBIGUOUS.
  • This response does not allow other services to be applied once it is taken. The reason being that the Service Handler has decided to send a response to the originator based on an event generated by an applied service. So to continue to apply other services to the signaling message would not be appropriate.
• Relay Signaling Message– this response, when selected, causes the signaling message to be onward routed to the SCCP destination. This response allows other services to be applied once it is taken.
  • SCCP Called Party Address Content – the content of the SCCP Called Party Address can be established by the user. For example, a Routing Number provided from the ETSI Subscriber Routing Service can be included in the Global Title Address.
  • INAP InitialDP Content – the parameters that are included in the original received InitialDP can be modified. For example, a Routing Number provided from the ETSI Subscriber Routing Service can be included in the Called Party Number

Return Error

The Return Error response causes a TCAP Return Error component to be returned to the originator of the signaling message.

If the response selected by the Service Handler for a specific event generated by the Service indicates Return Error, then a TCAP Return Error component shall be sent to the message originator.

Refer to Return Error Content for the content of the Return Error message.

 Continue

The Continue response causes an INAP Continue operation to be returned to the originator of the signaling message.

If the response selected by the Service Handler for a specific event generated by the Service indicates Continue, then an INAP Continue operation shall be sent to the message originator.

Please refer to INAP Continue Content for the content of the INAP Continue operation.

Release Call

The Release Call response causes an INAP Release Call operation to be returned to the originator of the signaling message.

If the response selected by the Service Handler for a specific event generated by the Service indicates Release Call, then an INAP Release Call operation shall be sent to the message originator.

Refer to INAP Release Call Content.

Resolve Ambiguity

The Resolve Ambiguity response allows the INAP InitialDP Service Handler to open a dialogue with the originating TC-User for the purposes of requesting additional information about an incomplete dialed number. This response is limited to the service events that are related to ambiguity resolution.

To apply this to another event generated from the ETSI Subscriber Routing Service or ETSI Number Portability Service or ETSI Multi-Country Number Portability Service would be out-of-context.

If the response selected by the Service Handler for a specific event generated by the Service indicates Resolve Ambiguity, then the following INAP operations shall be sent to the message originator:

• RequestReportBCSM – please refer to Section INAP Request Report BCSM operation for the content of the INAP Request Report BCSM operation.
• CollectInfo – please refer to Section INAP Collect Info operation for the content of the INAP Collect Info operation

Connect To Resource and Play Announcement

The Connect To Resource, Play Announcement response allows the INAP InitialDP Service Handler to open a dialogue with the originating TC-User for the purposes of directing the originating TC-User to play an announcement to the calling party.

If the response selected by the Service Handler for a specific event generated by the Service indicates Connect To Resource, Play Announcement, then the following INAP operations shall be sent to the message originator:

• RequestReportBCSM – please refer to Section INAP REQUEST REPORT BCSM CONTENT for the content of the INAP Request Report BCSM operation
• ConnectToResource – please refer to Section INAP CONNECT TO RESOURCE CONTENT for the content of the INAP Connect To Resource operation 
• Play Announcement – please refer to Section INAP PLAY ANNOUNCEMENT CONTENT for the content of the INAP Play Announcement operation

Connect

The Connect response allows the INAP InitialDP Service Handler to indicate the routing details for the subscriber.

If the response selected by the Service Handler for a specific event generated by the Service indicates Connect, then the INAP operation “Connect” shall be sent to the message originator. Please refer to Section INAP CONNECT CONTENT for the content of the “Connect” operation.

The INAP operation “SendChargingInformation” shall be included prior to the “Connect” operation if the includeSCI column from the connect table indicates that the “SendChargingInformation” operation shall be included (includeSCI = Yes). Please refer to Section INAP SEND CHARGING INFORMATION CONTENT for the content of the “SendChargingInformation” operation.

Relay Signaling Message

The "Relay" response allows the INAP InitialDP Service Handler to allow the SCCP Called Party Address to be manipulated with the intent to allow the message to be routed to the new SCCP destination (may be subject to the responses of further Services).

If the modifySCCPCdPA column from the relay table indicates that the SCCP Called Party Address is to be modified (modifySCCPCdPA = Yes), then the SCCP Called Party Address shall be modified as defined in Section GLOBAL TITLE ADDRESS MANIPULATION.

If the modifyInitialDPParam column from the relay table indicates that the InitialDP parameters are to be modified (modifyInitialDPParam = Yes), then the parameters of the InitialDP shall be modified as defined in Section INAP INITIALDP CONTENT.

Message Content

Return Error Content

The format of the signaling message when an error response is to be built is described by a record within the returnError table.

A TCAP Return Error component shall be build as follows:

• the Return Error component parameter “Error Code” shall be set to the value in the errorCode column of the found returnError table record.

INAP Continue Content

An INAP Continue operation contains no parameters.

INAP Release Call Content

If an INAP Release Call operation is to be sent, the content of the Release Call shall be

• the “initialCallSegment” parameter shall be present and configured as follows:
• the “Coding Standard” shall be set to the value of the codingStandard column from the releaseCall table 
• the “Location” shall be set to the value of the location column from the releaseCall table 
• the “Cause” shall be set to the value of the cause column from the releaseCall table

INAP Request Report BCSM Content

When the RequestReportBCSM operation is included for connecting to a resource, the following RequestReportBCSM parameters are applied:

INAP Request Report BCSM Content

The RequestReportBCSM parameter “bcsmEvents” shall be present. Please refer to Section bcsmEvents Content for the “bcsmEvents” content.

bcsmEvents Content

The “bcsmEvents” parameter “eventTypeBCSM” shall be present and set to the value of the evenTypeBCSM column from the requestReportBCSM table.

The “bcsmEvents” parameter “monitorMode” shall be present and set to the value of the monitorMode column from the requestReportBCSM table.

The “bcsmEvents” parameter “legID” shall be present if the includeLegID column from the requestReportBCSM table indicates that the “legID” parameter shall be included (includeLegID = Yes). Please refer to Section legID Content for the “legID” content.

The “bcsmEvents” parameter “legID” shall not be present if the includeLegID column from the requestReportBCSM table indicates that the “legID” parameter shall not be included (includeLegID = No).

The “bcsmEvents” parameter “dpSpecificCriteria” shall be present if the includeDpSpecificCriteria column from the requestReportBCSM table indicates that the “dpSpecificCriteria” parameter shall be included (includeDpSpecificCriteria = Yes). Please refer to Section dpSpecificCriteria Content for the “dpSpecificCriteria” content

The “bcsmEvents” parameter “dpSpecificCriteria” shall not be present if the includeDpSpecificCriteria column from the requestReportBCSM table indicates that the “dpSpecificCriteria” parameter shall not be 

included (includeDpSpecificCriteria = No).

legID Content

The “bcsmEvents.legID.sendingSideID” parameter shall be present and set to the value of the legIDSendingSideID column from the requestReportBCSM table.

dpSpecificCriteria Content

The “bcsmEvents.dpSpecificCriteria” parameter selection shall be set to the parameter indicated in the dpSpecificCriteria table.
Please refer to Section  for the “numberOfDigits” content
Please refer to Section applicationTimer Content for tnumberOfDigits Contenthe “applicationTimer” content

numberOfDigits Content

If the RequestReportBCSM parameter “dpSpecificCriteria” parameter selection is the numberOfDigits column from the dpSpecificCriteria table, then the “bcsmEvents.dpSpecificCriteria.numberOfDigits” parameter shall be included.

The “numberOfDigits” value shall be set to exactly one (1) if the value of the numberOfDigits column from the dpSpecificCriteria table indicates REQUEST EXACTLY ONE DIGIT.

The “numberOfDigits” value shall be set to the number of digits received in the number causing the ambiguity plus one more digit if the value of the numberOfDigits column from the dpSpecificCriteria table indicates REQUEST ALL DIGITS PLUS ONE MORE.

applicationTimer Content

If the RequestReportBCSM parameter “dpSpecificCriteria” parameter selection is the applicationTimer column from the dpSpecificCriteria table, then the “bcsmEvents.dpSpecificCriteria.applicationTimer” parameter shall be present and set to the value of the applicationTimer column.

INAP Collect Info Content

There are no parameters for the “Collect Info” operation.

INAP Connect To Resource Content

When the ConnectToResource operation is included for connecting to a resource, the following ConnectToResource parameters are applied:

INAP Connect To Resource Content

The ConnectToResource parameter “resourceAddress” shall be present. Please refer to Section resourceAddress Content for the content of the “resourceAddress” parameter.

The ConnectToResource parameter “serviceInteractionIndicatorsTwo” shall be present if the includeSvcIntIndTwo column from the connectToResource table indicates that the “serviceInteractionIndicatorsTwo” parameter shall be included (includeSvcIntIndTwo = Yes). Please refer to Section serviceInteractionIndicatorsTwo Content for the content of the “serviceInteractionsTwo” parameter.

The ConnectToResource parameter “serviceInteractionIndicatorsTwo” shall not be present if the includeSvcIntIndTwo column from the connectToResource table indicates that the “serviceInteractionIndicatorsTwo” parameter shall not be included (includeSvcIntIndTwo = No).

resourceAddress Content

The ConnectToResource parameter “resourceAddress” shall be set to the parameter indicated in the resourceAddress table.

legID Content

The ConnectToResource parameter “resourceAddress.legID” shall be present if the resourceAddressParam column from the resourceAddress table indicates that the “legID” parameter shall be included.

If the ConnectToResource parameter “resourceAddress.legID” is to be included, then the “resourceAddress.legID” parameter selection shall be set to the parameter indicated in the legID table.

If the ConnectToResource parameter “resourceAddress.legID” is to be included and the choice of parameter selected in the legID table is the sendingSideID column, then the “resourceAddress.legID.sendingSideID” parameter shall be present and set to the value of the sendingSideID column from the legID table.

If the ConnectToResource parameter “resourceAddress.legID” is to be included and the choice of parameter selected in the legID table is the receivingSideID column, then the “resourceAddress.legID.receivingSideID” parameter shall be present and set to the value of the receivingSideID column from the legID table.

none Content

The ConnectToResource parameter “resourceAddress.none” shall be present if the resourceAddressParam column from the resourceAddress table indicates that the “none” parameter shall be included.

serviceInteractionIndicatorsTwo Content

The following requirements apply if the “serviceInteractionIndicatorsTwo” is to be included in the ConnectToResource operation.

The “serviceInteractionIndicatorsTwo” parameter “backwardServiceInteractionIndicator” shall be present if the includeBackwardSvcIntInd column from the serviceIntIndTwo table indicates that the “backwardServiceInteractionIndicator” parameter shall be included (includeBackwardSvcIntInd = Yes). Please refer to Section backwardServiceInteractionIndicator Content for the “backwardServiceInteractionIndicator” content.

The “serviceInteractionIndicatorsTwo” parameter “backwardServiceInteractionIndicator” shall not be present if the includeBackwardSvcIntInd column from the serviceIntIndTwo table indicates that the “backwardServiceInteractionIndicator” parameter shall not be included (includeBackwardSvcIntInd = No )

The “serviceInteractionIndicatorsTwo” parameter “bothwayThroughConnectionIndicator” shall be present if the includeBothWayThrConInd column from the serviceIntIndTwo table indicates that the “bothwayThroughConnectionIndicator” parameter shall be included (includeBothWayThrConInd = Yes). Please refer to Section bothwayThroughConnectionIndicator Content for the “bothwayThroughConnectionIndicator” content.

The “serviceInteractionIndicatorsTwo” parameter “bothwayThroughConnectionIndicator” shall not be present if the includeBothWayThrConInd column from the serviceIntIndTwo table indicates that the “bothwayThroughConnectionIndicator” parameter shall not be included (includeBothWayThrConInd = No).

The “serviceInteractionIndicatorsTwo” parameter “connectedNumberTreatmentIndicator” shall be present if the includeConnectedNumTrtInd column from the serviceIntIndTwo table indicates that the “connectedNumberTreatmentIndicator” parameter shall be included (includeConnectedNumTrtInd = Yes).

The “serviceInteractionIndicatorsTwo” parameter “connectedNumberTreatmentIndicator” shall not be present if the includeConnectedNumTrtInd column from the serviceIntIndTwo table indicates that the “connectedNumberTreatmentIndicator” parameter shall not be included (includeConnectedNumTrtInd = No).

backwardServiceInteractionIndicator Content

The “backwardServiceInteractionIndicator” parameter “conferenceTreatmentIndicator” shall be present if the includeConfTrtInd column from the backwardSvcIntInd table indicates that the “conferenceTreatmentIndicator” parameter shall be included (includeConfTrtInd = Yes).

The “backwardServiceInteractionIndicator” parameter “conferenceTreatmentIndicator” shall not be present if the includeConfTrtInd column from the backwardSvcIntInd table indicates that the “conferenceTreatmentIndicator” parameter shall not be included (includeConfTrtInd = No).

The “backwardServiceInteractionIndicator” parameter “callCompletionTreatmentIndicator” shall be present if the includeCallComTrtInd column from the backwardSvcIntInd table indicates that the “callCompletionTreatmentIndicator” parameter shall be included (includeCallComTrtInd = Yes).

The “backwardServiceInteractionIndicator” parameter “callCompletionTreatmentIndicator” shall not be present if the includeCallComTrtInd column from the backwardSvcIntInd table indicates that the “callCompletionTreatmentIndicator” parameter shall not be included (includeCallComTrtInd = No).

conferenceTreatmentIndicator Content

The “backwardServiceInteractionIndicator” parameter “conferenceTreatmentIndicator” is to be included, then the value of the “conferenceTreatmentIndicator” shall be set to the value of the confTrtInd column from the backwardSvcIntInd table.

callCompletionTreatmentIndicator Content

The “backwardServiceInteractionIndicator” parameter “callCompletionTreatmentIndicator” is to be included, then the value of the “callCompletionTreatmentIndicator” shall be set to the value of the callComTrtInd column from the backwardSvcIntInd table.

bothwayThroughConnectionIndicator Content

If the “bothwayThroughConnectionIndicator” parameter is to be included, then the value of the “bothwayThroughConnectionIndicator” shall be set to the value of the bothWayThrConInd column from the serviceIntIndTwo table.

connectedNumberTreatmentIndicator Content

If the “connectedNumberTreatmentIndicator” parameter is to be included, then the value of the “connectedNumberTreatmentIndicator” shall be set to the value of the connectedNumTrtInd column from the serviceIntIndTwo table.

INAP Play Announcement Content

When the PlayAnnouncement operation is included for connecting to a resource, the following PlayAnnouncement parameters are applied:

INAP Play Announcement

The PlayAnnouncement parameter “informationToSend” shall be present. Please refer to Section informationToSend Content for the content of the “informationToSend” parameter.

The PlayAnnouncement parameter “disconnectFromIPForbidden” shall be present. Please refer to Section disconnectFromIPForbidden Content for the content of the “disconnectFromIPForbidden” parameter.

The PlayAnnouncement parameter “requestAnnouncementComplete” shall be present. Please refer to Section requestAnnouncementComplete Content  for the content of the “requestAnnouncementComplete” parameter.

informationToSend Content

The “PlayAnnouncement” parameter “informationToSend” parameter selection shall be set to the parameter indicated in the informationToSend table.
Please refer to Section inbandInfo Content for the “inbandInfo” parameter content. Please refer to Section tone Content for the “tone” parameter content.
Please refer to Section displayInformation Content for the “displayInformation parameter content.

inbandInfo Content

The “informationToSend.inbandInfo” parameter “messageID” shall be present. Please refer to Section messageID Content for the “messageID” parameter content.

The “informationToSend.inbandInfo.numberOfRepetitions” parameter shall be present if the includeNumOfRepetitions column from the inbandInfo table indicates that the “numberOfRepetitions” parameter shall be included (includeNumOfRepetitions = Yes). Please refer to Section numberOfRepetitions Content for the “numberOfRepetitions” parameter content.

The “informationToSend.inbandInfo.numberOfRepetitions” parameter shall not be present if the includeNumOfRepetitions column from the inbandInfo table indicates that the “numberOfRepetitions” parameter shall not be included (includeNumOfRepetitions = No).

The “informationToSend.inbandInfo.duration” parameter shall be present if the includeDuration column from the inbandInfo table indicates that the “duration” parameter shall be included (includeDuration = Yes). Please refer to Section duration Content for the “duration” parameter content.

The “informationToSend.inbandInfo.duration” parameter shall not be present if the includeDuration column from the inbandInfo table indicates that the “duration” parameter shall not be included (includeDuration = No).

The “informationToSend.inbandInfo.interval” parameter shall be present if the includeInterval column from the inbandInfo table indicates that the “interval” parameter shall be included (includeInterval = Yes). Please refer to Section interval Content for the “interval” parameter content.

The “informationToSend.inbandInfo.interval” parameter shall not be present if the includeInterval column from the inbandInfo table indicates that the “interval” parameter shall not be included (includeInterval = No).

messageID Content

The “informationToSend.inbandInfo” parameter “messageID” parameter selection shall be set to the parameter indicated in the messageID table.
Please refer to Section elementaryMessageID Content for the “messageID” parameter content.

elementaryMessageID Content

The “informationToSend.inbandInfo.messageID” parameter “elementaryMessageID” value shall be set to the value of the elementaryMessageID column from the messageID table.

numberOfRepetitions Content

If the “informationToSend.inbandInfo.numberOfRepetitions” parameter is to be included, then the value of the “informationToSend.inbandInfo.numberOfRepetitions” parameter shall be set to the value of the numberOfRepetitions column from the inbandInfo table.

duration Content

If the “informationToSend.inbandInfo.duration” parameter is to be included, then the value of the “informationToSend.inbandInfo.duration” parameter shall be set to the value of the duration column from the inbandInfo table.

interval Content

If the “informationToSend.inbandInfo.interval” parameter is to be included, then the value of the “informationToSend.inbandInfo.interval” parameter shall be set to the value of the interval column from the inbandInfo table.

tone Content

The “informationToSend.tone” parameter “toneID” shall be present. Please refer to Section toneID Content for the “toneID” parameter content.

The “informationToSend.tone” parameter “duration” shall be present if the includeDuration column from the tone table indicates that the “informationToSend.tone” parameter “duration” shall be included (includeDuration = Yes). Please refer to Section duration Content for the “duration” parameter content.

toneID Content

The “tone” parameter “toneID” shall be set to the value of the toneID column from the tone table.

duration Content

The “tone” parameter “duration” shall be set to the value of the duration column from the tone table.

displayInformation Content

The “informationToSend” parameter “displayInformation” shall be set to the value of the displayInformation column from the informationToSend table.

disconnectFromIPForbidden Content

The “PlayAnnouncement” parameter “disconnectFromIPForbidden” shall be set to the value of the disconnectFromIPForbidden column from the PlayAnnouncement table.

requestAnnouncementComplete Content

The “PlayAnnouncement” parameter “requestAnnouncementComplete” shall be set to the value of the reqAnnouncementComplete column from the PlayAnnouncement table.

INAP Connect Content

The “Connect” parameter “destinationRoutingAddress” shall be present. Please refer to Section destinationRoutingAddress Content for the “destinationRoutingAddress” content.

The “Connect” parameter “cutAndPaste” shall be present if the includeCutAndPaste column from the connectParameters table indicates that the “cutAndPaste” parameter shall be included (includeCutAndPaste
= Yes). Please refer to Section cutAndPaste Content for the “cutAndPaste” content.

The “Connect” parameter “cutAndPaste” shall not be present if the includeCutAndPaste column from the connectParameters table indicates that the “cutAndPaste” parameter shall not be included (includeCutAndPaste = No).

The “Connect” parameter “displayInformation” shall be present if the includeDisplayInfo column from the connectParameters table indicates that the “displayInformation” parameter shall be included (includeDisplayInfo = Yes). Please refer to Section displayInformation Content for the “displayInformation” content.

The “Connect” parameter “displayInformation” shall not be present if the includeDisplayInfo column from the connectParameters table indicates that the “displayInformation” parameter shall not be included (includeDisplayInfo = No).

The “Connect” parameter “serviceInteractionIndicatorsTwo” shall be present if the includeSvcIntIndTwo column from the connectParameters table indicates that the “serviceInteractionIndicatorsTwo” parameter shall be included (includeDisplayInfo = Yes). Please refer to Section serviceInteractionIndicatorsTwo Content for the “serviceInteractionIndicatorsTwo” conten

The “Connect” parameter “serviceInteractionIndicatorsTwo” shall not be present if the includeSvcIntIndTwo column from the connectParameters table indicates that the “serviceInteractionIndicatorsTwo” parameter shall not be included (includeDisplayInfo = No).

destinationRoutingAddress Content

The “destinationRoutingAddress” parameter “calledPartyNumber” shall be present. Please refer to Section   CalledParty Number Content for the “calledPartyNumber” content.

calledPartyNumber Content

The construction of the “calledPartyNumber” parameter is based on the user’s configuration. The user has several choices that allow the content of the “calledPartyNumber” to be defined.

• SRSRN – build the “calledPartyNumber” contents based on a routing number provided by the ETSI Subscriber Routing Service.
• NPRN– build the “calledPartyNumber” contents based on a routing number provided by the ETSI Number Portability Service and the “original address”.
• Default Called Party Number – build the “calledPartyNumber” contents based on a provisioned Default Called Party Number data.
• Original Address - build the “calledPartyNumber” contents based on the “original address”. 
• Multi-Country NPRN – build the “calledPartyNumber” contents based on a routing number provided by the ETSI Multi-Country Number Portability Service and the “original address”.

If the draBasedOnSRSRN column references a valid entry from the draSRSRN table, then the “destinationRoutingAddress” parameter “calledPartyNumber” shall be built using information from the references draSRSRN table entry. Please refer to Section Called Party Number Based On ETSI SRS Routing Number for the requirements regarding the construction of the address based on an ETSI Subscriber Routing Service’s Routing Number.

If the “destinationRoutingAddress” parameter “calledPartyNumber” is to be built based on a routing number provided by the ETSI Number Portability Service (draBasedOnNPRN = Yes), then the “destinationRoutingAddress” parameter “calledPartyNumber” shall be built according to the requirements in Section Called Party Number Based On ETSI Number Portability Routing Number

If the “destinationRoutingAddress” parameter “calledPartyNumber” is to be built based on a routing number provided by the ETSI Multi-Country Number Portability Service (draBasedOnMCntNPRN = Yes), then the “destinationRoutingAddress” parameter “calledPartyNumber” shall be built according to the requirements in Section Called Party Number Based On ETSI Multi-Country Number Portability Routing Number

If the defaultDRACdPA column references a valid entry from the defaultDRACdPA table, then the “destinationRoutingAddress” parameter “calledPartyNumber” shall be built using information from the

If the originalAddress column indicates that the “destinationRoutingAddress” parameter “calledPartyNumber” is to be built using the original address (originalAddress = Yes), then the “destinationRoutingAddress” parameter “calledPartyNumber” shall be built according to the requirements in Section Called Party Number Based On Original Address

Called Party Number Based On ETSI SRS Routing Number

This section defines the requirements for building the Called Party Number content based on routing number provided by the ETSI Subscriber Routing Service.

If the routing number referenced by the draSRSRN table is not available from the ETSI Subscriber Routing Service, then the “calledPartyNumber” parameter shall be built using information from the “original address” as defined in Section Called Party Number Based On Original Address

If the value of the rnType column from the rnTypeforSRSRN table indicates replace CdPA (rnType = ReplaceCdPA), then the Nature of Address of the “calledPartyNumber” parameter shall be set to digitsFormat associated with the routing number.

If the value of the rnType column from the rnTypeforSRSRN table indicates replace CdPA (rnType = ReplaceCdPA), then the Numbering Plan of the “calledPartyNumber” parameter shall be set to E.164
Numbering Plan.

If the value of the rnType column from the rnTypeforSRSRN table indicates replace CdPA (rnType = ReplaceCdPA), then the digits of the “calledPartyNumber” parameter shall be set to the digits of the routing number.

If the value of the rnType column from the rnTypeforSRSRN table indicates Prefix CdPA (rnType = PrefixCdPA), then the “calledPartyNumber” parameter shall be built as follows:

• The Numbering Plan of the “calledPartyNumber” parameter shall be set to the Numbering Plan of the “original address”.
• The Nature of Address of the “calledPartyNumber” parameter shall be set to the Nature of Address of the “original address”
• If the “original address” digits format determined is International, then digits shall be set to:
  
  • CC + RN + National Significant Portion of the “original address”
• If the “original address” digits format determined is National, then digits shall be set to:
  • RN + National Significant Portion of the “original address”

Called Party Number Based On ETSI Number Portability Routing Number

This section defines the requirements for building the Called Party Number content based on routing number provided by the ETSI Number Portability Service.

If the “destinationRoutingAddress” parameter “calledPartyNumber” is to be built based on routing number provided by the ETSI Number Portability Service and a routing number is not available from the ETSI Number Portability Service, then the “calledPartyNumber” parameter shall be built using information from the “original address” as defined in Section Called Party Number Based On Original Address.

The Numbering Plan of the “calledPartyNumber” parameter shall be set to the Numbering Plan of the “original address”.

If ETSI Digit Analysis Service is applied and digit format of the “original address” is International, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• CC + RN + National Significant Portion of the “original address”.

If ETSI Digit Analysis Service is applied and digit format of the “original address” is National, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• RN + National Significant Portion of the “original address”.

If ETSI Digit Analysis Service is not applied, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• If the “original address” digits format determined is International, then digits shall be set to:

• • CC + RN + National Significant Portion of the “original address”

• If the “original address” digits format determined is National, then digits shall be set to:
  •  RN + National Significant Portion of the “original address”

The Nature of Address of the “calledPartyNumber” parameter shall be set as follows:

• International if Country Code is included in “calledPartyNumber” digits
• National if Country Code is not included in “calledPartyNumber” digits

Called Party Number Based On ETSI Multi-Country Number Portability Routing Number

This section defines the requirements for building the Called Party Number content based on routing number provided by the ETSI Multi-Country Number Portability Service.

If the “destinationRoutingAddress” parameter “calledPartyNumber” is to be built based on routing number provided by the ETSI Multi-Country Number Portability Service and a routing number is not available from the ETSI Multi-Country Number Portability Service, then the “calledPartyNumber” parameter shall be built using information from the “original address” as defined in Section calledPartyNumber Content

The Numbering Plan of the “calledPartyNumber” parameter shall be set to the E.164 Numbering Plan.

If the value of mCntNPRNSelection column from the draCalledPartyNumber table indicates use ExchangeID (mCntNPRNSelection = useExchangeID), then the digits of the “calledPartyNumber” parameter shall be set as follows:

• exchangeID

If the value of mCntNPRNSelection column from the draCalledPartyNumber table indicates use OperatorID (mCntNPRNSelection = useOperatorID), then the digits of the “calledPartyNumber” parameter shall be set as follows:

• operatorID

If the value of mCntNPRNSelection column from the draCalledPartyNumber table indicates concatenate ExchangeID and OperatorID (mCntNPRNSelection = concatenateExIDOpID), then the digits of the “calledPartyNumber” parameter shall be set as follows:

• exchangeID + operatorID

The Nature of Address of the “calledPartyNumber” parameter shall be set to National.

Called Party Number Based On Default Called Party Number

This section defines the requirements for building the Called Party Number content based on provisioned Default Called Party Number data.

If the referenced defaultDRACdPA table entry is not available, then the “calledPartyNumber” parameter shall be built using information from the original address as defined in Section Called Party Number Based On Original Address.

The Nature of Address of the “calledPartyNumber” parameter shall be set to natureOfAddress defined in the defaultDRACdPA table.

The Numbering Plan of the “calledPartyNumber” parameter shall be set to numberingPlan defined in the defaultDRACdPA table.

The digits of the “calledPartyNumber” parameter shall be set to the digits defined in the defaultDRACdPA  table.

Called Party Number Based On Original Address

The “calledPartyNumber” parameter is built using information from the “original address”.

The Numbering Plan of the “calledPartyNumber” parameter shall be set to the Numbering Plan of the “original address”.

If ETSI Digit Analysis Service is applied and digit format of the “original address” is International, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• CC + National Significant Portion of the “original address”.

If ETSI Digit Analysis Service is applied and digit format of the “original address” is National, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• National Significant Portion of the “original address”.

If ETSI Digit Analysis Service is not applied, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• If the “original address” digits format determined is International, then digits shall be set to:

• • CC + National Significant Portion of the “original address”.

• If the “original address” digits format determined is National, then digits shall be set to:

• National Significant Portion of the “original address”.

The Nature of Address of the “calledPartyNumber” parameter shall be set as follows:

• International if Country Code is included in “calledPartyNumber” digits
• National if Country Code is not included in “calledPartyNumber” digits.

cutAndPaste Content

The “cutAndPaste” parameter is an optional parameter within the Connect. However, there are times when the presence of the “cutAndPaste” parameter is determined based on the content of the “destinationRoutingAddress”. Specifically, if the “destinationRoutingAddress” contains only a Routing Number that is an ETSI Number Portability Routing Number or an ETSI Multi-Country Number Portability Routing Number, and then the “cutAndPaste” parameter will always be included and set to a value of zero. This is to protect against an ambiguous interpretation of the “destinationRoutingAddress”. By including the “cutAndPaste” parameter with a value of zero, the “destinationRoutingAddress”, in this case, is explicitly being reported as a prefix to the existing “calledPartyNumber”.

If the “destinationRoutingAddress” contains only a Network Routing Number of type ETSI Number Portability Routing Number, then the “cutAndPaste” parameter shall be present with a value of zero, regardless of the selection in the includeCutAndPaste column of the connectParameters table.

If the “destinationRoutingAddress” contains only a Network Routing Number of type ETSI Multi-Country Number Portability Routing Number, then the “cutAndPaste” parameter shall be present with a value of zero, regardless of the selection in the includeCutAndPaste column of the connectParameters table.

If the “cutAndPaste” parameter is to be included, then the value of the “cutAndPaste” parameter shall be set to a value equivalent to the number of digits in the received “calledPartyNumber” parameter.

displayInformation Content

The “displayInformation” parameter allows for a text string to be sent to the end user.

If the “displayInformation” parameter is to be included in the Connect operation, then the text shall be set to the text in the displayInformation column of the connectParameters table.

serviceInteractionIndicatorsTwo Content

The following requirements apply if the “serviceInteractionIndicatorsTwo” is to be included in the Connect operation.

The “serviceInteractionIndicatorsTwo” parameter “forwardServiceInteractionIndicator” shall be present if the includeforwardSvcIntInd column from the serviceIntIndTwo table indicates that the “forwardServiceInteractionIndicator” parameter shall be included (includeforwardSvcIntInd = Yes ). Please refer to Section forwardServiceInteractionInd Content for the “forwardServiceInteractionIndicator” content.

The “serviceInteractionIndicatorsTwo” parameter “forwardServiceInteractionIndicator” shall not be present if the includeforwardSvcIntInd column from the serviceIntIndTwo table indicates that the “forwardServiceInteractionIndicator” parameter shall not be included (includeforwardSvcIntInd = No).

The “serviceInteractionIndicatorsTwo” parameter “backwardServiceInteractionIndicator” shall be present if the includeBackwardSvcIntInd column from the serviceIntIndTwo table indicates that the “backwardServiceInteractionIndicator” parameter shall be included (includeBackwardSvcIntInd = Yes). Please refer to Section backwardServiceInteractionInd Content for the “backwardServiceInteractionIndicator” content.

The “serviceInteractionIndicatorsTwo” parameter “backwardServiceInteractionIndicator” shall not be present if the includeBackwardSvcIntInd column from the serviceIntIndTwo table indicates that the “backwardServiceInteractionIndicator” parameter shall not be included (includeBackwardSvcIntInd = No).

The “serviceInteractionIndicatorsTwo” parameter “suspendTimer” shall be present if the IncludeSuspendTimer column from the serviceIntIndTwo table indicates that the “suspendTimer” parameter shall be included (IncludeSuspendTimer = Yes). Please refer to Section suspendTimer Content for the “suspendTimer” content.

The “serviceInteractionIndicatorsTwo” parameter “suspendTimer” shall not be present if the IncludeSuspendTimer column from the serviceIntIndTwo table indicates that the “suspendTimer” parameter shall not be included (IncludeSuspendTimer = No).

The “serviceInteractionIndicatorsTwo” parameter “connectedNumberTreatmentIndicator” shall be present if the includeConnectedNumTrtInd column from the serviceIntIndTwo table indicates that the “connectedNumberTreatmentIndicator” parameter shall be included (includeConnectedNumTrtInd = Yes). Please refer to Section connectedNumberTreatmentInd Content for the “connectedNumberTreatmentIndicator” content.

The “serviceInteractionIndicatorsTwo” parameter “connectedNumberTreatmentIndicator” shall not be present if the includeConnectedNumTrtInd column from the serviceIntIndTwo table indicates that the “connectedNumberTreatmentIndicator” parameter shall not be included (includeConnectedNumTrtInd = No).

The “serviceInteractionIndicatorsTwo” parameter “suppressCallDiversionNotification” shall be present if the includeSupCallDivNotif column from the serviceIntIndTwo table indicates that the “suppressCallDiversionNotification” parameter shall be included (includeSupCallDivNotif = Yes). Please refer to Section suppressCallDiversionNotification Content for the content of the “suppressCallDiversionNotification” parameter.

The “serviceInteractionIndicatorsTwo” parameter “suppressCallDiversionNotification” shall not be present if the includeSupCallDivNotif column from the serviceIntIndTwo table indicates that the “suppressCallDiversionNotification” parameter shall not be included (includeSupCallDivNotif = No).

The “serviceInteractionIndicatorsTwo” parameter “suppressCallTransferNotification” shall be present if the IncludeSupCallTransNotif column from the serviceIntIndTwo table indicates that the “suppressCallTransferNotification” parameter shall be included (IncludeSupCallTransNotif = Yes). Please refer to Section suppressCallTransferNotification Content for the content of the “suppressCallTransferNotification” parameter.

The “serviceInteractionIndicatorsTwo” parameter “suppressCallTransferNotification” shall not be present if the IncludeSupCallTransNotif column from the serviceIntIndTwo table indicates that the “suppressCallTransferNotification” parameter shall not be included (IncludeSupCallTransNotif = N ).

The “serviceInteractionIndicatorsTwo” parameter “allowCdINNoPresentationInd” shall be present if the includeAllowCdINNoPrInd column from the serviceIntIndTwo table indicates that the “allowCdINNoPresentationInd” parameter shall be included (includeAllowCdINNoPrInd = Yes). Please refer to Section allowCdINNoPresentationInd Content for the content of the “allowCdINNoPresentationInd” parameter.

The “serviceInteractionIndicatorsTwo” parameter “allowCdINNoPresentationInd” shall not be present if the includeAllowCdINNoPrInd column from the serviceIntIndTwo table indicates that the “allowCdINNoPresentationInd” parameter shall not be included (includeAllowCdINNoPrInd = No).

The “serviceInteractionIndicatorsTwo” parameter “userDialogueDurationInd” shall be present if the includeuserDlgDurationInd column from the serviceIntIndTwo table indicates that the “userDialogueDurationInd” parameter shall be included (includeuserDlgDurationInd = Yes). Please refer to Section 4.8.4.8 for the content of the “userDialogueDurationInd” parameter.

The “serviceInteractionIndicatorsTwo” parameter “userDialogueDurationInd” shall not be present if the includeuserDlgDurationInd column from the serviceIntIndTwo table indicates that the “userDialogueDurationInd” parameter shall not be included (includeuserDlgDurationInd = No).

forwardServiceInteractionInd Content

The “forwardServiceInteractionInd” parameter “conferenceTreatmentIndicator” shall be present if the includeConfTrtInd column from the forwardSvcIntInd table indicates that the “conferenceTreatmentIndicator” parameter shall be included (includeConfTrtInd = Yes). Please refer to Section conferenceTreatmentIndicator Content for the content of the “conferenceTreatmentIndicator” parameter.

The “forwardServiceInteractionInd” parameter “conferenceTreatmentIndicator” shall not be present if the includeConfTrtInd column from the forwardSvcIntInd table indicates that the “conferenceTreatmentIndicator” parameter shall not be included (includeConfTrtInd = No).

The “forwardServiceInteractionInd” parameter “callDiversionTreatmentIndicator” shall be present if the includeCallDivTrtInd column from the forwardSvcIntInd table indicates that the “callDiversionTreatmentIndicator” parameter shall be included (includeCallDivTrtInd = Yes). Please refer to Section callDiversionTreatmentIndicator Content for the content of the “callDiversionTreatmentIndicator” parameter.

The “forwardServiceInteractionInd” parameter “callDiversionTreatmentIndicator” shall not be present if the includeCallDivTrtInd column from the forwardSvcIntInd table indicates that the “callDiversionTreatmentIndicator” parameter shall not be included (includeCallDivTrtInd = No).

The “forwardServiceInteractionInd” parameter “callOfferingTreatmentIndicator” shall be present if the includeCallOfferingTrtInd column from the forwardSvcIntInd table indicates that the “callOfferingTreatmentIndicator” parameter shall be included (includeCallOfferingTrtInd = Yes). Please refer to Section callOfferingTreatmentIndicator Content for the content of the “callOfferingTreatmentIndicator” parameter.

The “forwardServiceInteractionInd” parameter “callOfferingTreatmentIndicator” shall not be present if the includeCallOfferingTrtInd column from the forwardSvcIntInd table indicates that the “callOfferingTreatmentIndicator” parameter shall not be included (includeCallOfferingTrtInd = No).

The “forwardServiceInteractionInd” parameter “callingPartyRestrictionIndicator” shall be present if the includeCallingPartyRestInd column from the forwardSvcIntInd table indicates that the “callingPartyRestrictionIndicator” parameter shall be included (includeCallingPartyRestInd = Yes). Please refer to Section callingPartyRestrictionIndicator Content for the content of the “callingPartyRestrictionIndicator” parameter.

The “forwardServiceInteractionInd” parameter “callingPartyRestrictionIndicator” shall not be present if the includeCallingPartyRestInd column from the forwardSvcIntInd table indicates that the “callingPartyRestrictionIndicator” parameter shall not be included (includeCallingPartyRestInd = No ).

conferenceTreatmentIndicator Content

The “conferenceTreatmentIndicator” parameter shall be set to the value of the conferenceTrtInd column from the forwardSvcIntInd table.

callDiversionTreatmentIndicator Content

The “callDiversionTreatmentIndicator” parameter shall be set to the value of the callDiversionTrtInd column from the forwardSvcIntInd table.

callOfferingTreatmentIndicator Content

The “callOfferingTreatmentIndicator” parameter shall be set to the value of the callOfferingTrtInd column from the forwardSvcIntInd table.

callingPartyRestrictionIndicator Content

The “callingPartyRestrictionIndicator” parameter shall be set to the value of the callingPartyRestInd column from the forwardSvcIntInd table.

backwardServiceInteractionInd Content

The “backwardServiceInteractionInd” parameter “conferenceTreatmentIndicator” shall be present if the includeConfTrtInd column from the backwardSvcIntInd table indicates that the “conferenceTreatmentIndicator” parameter shall be included (includeConfTrtInd = Yes). Please refer to Section conferenceTreatmentIndicator Content for the content of the “conferenceTreatmentIndicator” parameter.

The “backwardServiceInteractionInd” parameter “conferenceTreatmentIndicator” shall not be present if the includeConfTrtInd column from the backwardSvcIntInd table indicates that the “conferenceTreatmentIndicator” parameter shall not be included (includeConfTrtInd = No).

conferenceTreatmentIndicator Content

The “conferenceTreatmentIndicator” parameter shall be set to the value of the confTrtInd column from the backwardSvcIntInd table.

suspendTimer Content

The “suspendTimer” parameter shall be set to the value of the suspendTimer column from the serviceIntIndTwo table.

connectedNumberTreatmentInd Content

The “connectedNumberTreatmentInd” parameter shall be set to the value of the connectedNumTrtInd column from the serviceIntIndTwo table.

suppressCallDiversionNotification Content

The “suppressCallDiversionNotification” parameter shall be set to the value of the suppressCallDivNotif column from the serviceIntIndTwo table.

suppressCallTransferNotification Content

The “suppressCallTransferNotification” parameter shall be set to the value of the suppressCallTransNotif column from the serviceIntIndTwo table.

allowCdINNoPresentationInd Content

The “allowCdINNoPresentationInd” parameter shall be set to the value of the allowCdINNoPresentationInd column from the serviceIntIndTwo table.

userDialogueDurationInd Content

The “userDialogueDurationInd” parameter shall be set to the value of the userDialogueDurationInd column from the serviceIntIndTwo table.

INAP Send Charging Information Content

The structure of the SendChargingInformation operation shall be as indicated in the “SendChargingInformation Format” parameter.

Format 1 Content

The format, or structure, of the SendChargingInformation operation identified by “Format 1” is as follows:

SendChargingInformationArg ::= SEQUENCE { SCIBillingChargingCharacteristics [0] ::= CHOICE { performChargeDetermination [27] NULL } partyToCharge [1] LegID ::= CHOICE { sendingSideID [0],  receivingSideID [1] } }

The “SCIBillingChargingCharacteristics” parameter shall be included in the SendChargingInformation operation. Please refer to Section SCIBillingChargingCharacteristics Content for the content of the “SCIBillingChargingCharacteristics” parameter.

The “partyToCharge” parameter shall be included in the SendChargingInformation operation. Please refer to Section partyToCharge Content for the content of the “partyToCharge” parameter.

SCIBillingChargingCharacteristics Content

The “performChargeDetermination” parameter shall be included in the “SCIBillingChargingCharacteristics” parameter. Please refer to Section performChargeDetermination Content for the content of the “performChargeDetermination” parameter.

performChargeDetermination Content

The “performChargeDetermination” parameter shall be empty.

partyToCharge Content

The “partyToCharge” parameter selection shall be set to the parameter indicated in the partyToCharge table

If the “partyToCharge” parameter selection is the “sendingSideID”, then the “sendingSideID” parameter shall be present and set to the value of the sendingSideID column from the partyToCharge table.

If the “partyToCharge” parameter selection is the “receivingSideID”, then the “receivingSideID” parameter shall be present and set to the value of the receivingSideID column from the partyToCharge table.

Format 2 Content

The format, or structure, of the SendChargingInformation operation identified by “Format 2” is as follows:

SendChargingInformationArg ::= Sequence { SCIBillingChargingCharacteristics [ 0 ] ::= Sequence { ChargeLevel [0] ::= Implicit Sequence { SCP Charge Number [0] ::= OctetString } Transparent Data [2] ::= 'AFFE' } partyToCharge [1] ::= Choice { sendingSideID [0],  receivingSideID [1] } }

The “SCIBillingChargingCharacteristics” parameter shall be included in the SendChargingInformation operation. Please refer to Section SCIBillingChargingCharacteristics Content for the content of the “SCIBillingChargingCharacteristics” parameter.

 The “partyToCharge” parameter shall be included in the SendChargingInformation operation. Please refer to Section partyToCharge Content for the content of the “partyToCharge” parameter.

SCIBillingChargingCharacteristics Content

The “chargeLevel” parameter shall be included in the “SCIBillingChargingCharacteristics” parameter. Please refer to Section chargeLevel Content for the content of the “chargeLevel” parameter

The “transparentData” parameter shall be included in the “SCIBillingChargingCharacteristics” parameter. Please refer to Section transparentData Content for the content of the “transparentData” parameter.

chargeLevel Content

The “SCPChargeNumber” parameter shall be included in the “chargeLevel” parameter. Please refer to Section SCPChargeNumber Content for the content of the “SCPChargeNumber” parameter.

SCPChargeNumber Content

The construction of the “SCPChargeNumber” parameter is based on the user’s configuration. The user has three choices that allow the content of the “SCPChargeNumber” to be defined.

• SRSRN – build the SCPChargeNumber contents based on a routing number provided by the ETSI Subscriber Routing Service
• Default SCP Charge Number – build the SCPChargeNumber contents based on a provisioned default SCPChargeNumber data
• no Routing Number (empty) may be used within the “SCPChargeNumber” parameter

If the scpChrgNumSRSRN column references a valid entry from the scpChrgNumSRSRN table, then the “SCPChargeNumber” parameter shall be built using the references scpChrgNumSRSRN table entry.

If the defaultSCPChrgNum column references a valid entry from the defaultSCPChrgNum table, then the “SCPChargeNumber” parameter shall be built using the references defaultSCPChrgNum table entry.

If a Routing Number is allowed to be used within the “SCPChargeNumber”, then the “SCPChargeNumber” parameter shall be formatted as follows:

SCPChargeNumber content for SCI Format 2

where n = number of digits in the Routing Number and xxxx are bit representations

If the scpChrgNumSRSRN column references an invalid entry from the scpChrgNumSRSRN table, then the ETSI Subscriber Routing Service routing number shall not be used within the “SCPChargeNumber”.

If the defaultSCPChrgNum column references an invalid entry from the defaultSCPChrgNum table, then the default SCPChargeNumber data shall not be used within the “SCPChargeNumber”.

transparentData Content

The “transparentData” parameter shall be set to the value of the transparentData column from the sciFormat2 table.

partyToCharge Content

The “partyToCharge” parameter selection shall be set to the parameter indicated in the partyToCharge table.

If the “partyToCharge” parameter selection is the “sendingSideID”, then the “sendingSideID” parameter shall be present and set to the value of the sendingSideID column from the partyToCharge table.

If the “partyToCharge” parameter selection is the “receivingSideID”, then the “receivingSideID” parameter shall be present and set to the value of the receivingSideID column from the partyToCharge table.

Format 3

The format, or structure, of the SendChargingInformation operation identified by “Format 3” is as follows:

SendChargingInformationArg ::= Sequence { SCIBillingChargingCharacteristics [0] ::= OctetString  partyToCharge [1] ::= Choice { sendingSide [0] receivingSide [0] } }

The “SCIBillingChargingCharacteristics” parameter shall be included in the SendChargingInformation operation. Please refer to Section SCIBillingChargingCharacteristics Content for the content of the “SCIBillingChargingCharacteristics” parameter.

The “partyToCharge” parameter shall be included in the SendChargingInformation operation. Please refer to Section partyToCharge Content for the content of the “partyToCharge” parameter.

SCIBillingChargingCharacteristics Content

The construction of the “SCIBillingChargingCharacteristics” parameter is based on the user’s configuration. The user has three choices that allow the content of the “SCIBillingChargingCharacteristics” to be defined.

• SRSRN – build the “SCIBillingChargingCharacteristics” contents based on a routing number provided by the ETSI Subscriber Routing Service
• Default SCI Billing Characteristics – build the “SCIBillingChargingCharacteristics” contents based on a provisioned default SCPChargeNumber data
• no Routing Number (empty) may be used within the “SCIBillingChargingCharacteristics” parameter

If the sciBillingSRSRN column references a valid entry from the sciBillingSRSRN table, then the “SCIBillingChargingCharacteristics” parameter shall be built using the references sciBillingSRSRN table entry.

If the defaultSCIBilling column references a valid entry from the defaultSCIBilling table, then the “SCIBillingChargingCharacteristics” parameter shall be built using the references defaultSCIBilling table entry.

If a Routing Number is allowed to be used within the “SCIBillingChargingCharacteristics”, then the “SCIBillingChargingCharacteristics” parameter shall be formatted as follows:

SCIBillingChargingCharacteristics for SCI Format 3

where n = number of digits in the Routing Number and xxxx are bit representations

If the sciBillingSRSRN column references an invalid entry from the sciBillingSRSRN table, then the ETSI Subscriber Routing Service routing number shall not be used within the “SCIBillingChargingCharacteristics”.

If the defaultSCIBilling column references an invalid entry from the defaultSCIBilling table, then the default SCPChargeNumber data shall not be used within the “SCIBillingChargingCharacteristics”.

partyToCharge Content

The “partyToCharge” parameter selection shall be set to the parameter indicated in the partyToCharge table.

If the “partyToCharge” parameter selection is the “sendingSideID”, then the “sendingSideID” parameter shall be present and set to the value of the sendingSideID column from the partyToCharge table.

If the “partyToCharge” parameter selection is the “receivingSideID”, then the “receivingSideID” parameter shall be present and set to the value of the receivingSideID column from the partyToCharge table.

INAP InitialDP Content

If the InitialDP operation content is to be modified, then the user has the choice of which parameters should be modified and the choice of how those selected parameters will be modified. The following Response parameters will control the parameters within the InitialDP:

• Modify calledPartyNumber
• Modify calledPartyBCDNumber

The “calledPartyNumber” parameter shall be modified as defined in Section calledPartyNumber Content if:

• the modifyCalledParty column from the initialDPParameters table indicates that the “calledPartyNumber” parameter shall be modified (modifyCalledParty = Yes), and

• the “calledPartyNumber” parameter is present in the InitialDP parameter sequence.

The “calledPartyNumber” parameter shall not be modified if:

• the modifyCalledParty column from the initialDPParameters table indicates that the “calledPartyNumber” parameter shall not be modified (modifyCalledParty = No), or
• the modifyCalledParty column from the initialDPParameters table indicates that the “calledPartyNumber” parameter shall be modified (modifyCalledParty = Yes), and the “calledPartyNumber” parameter is not present in the InitialDP parameter sequence.

The “calledPartyBCDNumber” parameter shall be modified as defined in Section calledPartyBCDNumber Content if:

• the modifyCalledPartyBCD column from the initialDPParameters table indicates that the “calledPartyBCDNumber” parameter shall be modified (modifyCalledPartyBCD = Yes), and
• the “calledPartyBCDNumber” parameter is present in the InitialDP parameter sequence.

The “calledPartyBCDNumber” parameter shall not be modified if:

• the modifyCalledPartyBCD column from the initialDPParameters table indicates that the “calledPartyBCDNumber” parameter shall not be modified (modifyCalledPartyBCD = No), or
• the modifyCalledPartyBCD column from the initialDPParameters table indicates that the “calledPartyBCDNumber” parameter shall be modified (modifyCalledPartyBCD = Yes), and the “calledPartyBCDNumber” parameter is not present in the InitialDP parameter sequence.

calledPartyNumber Content

The construction of the “calledPartyNumber” parameter is based on the user’s configuration. The user has several choices that allow the content of the “calledPartyNumber” to be defined.

• SRSRN – build the calledPartyNumber contents based on a routing number provided by the ETSI Subscriber Routing Service
• NPRN– build the calledPartyNumber contents based on a routing number provided by the ETSI Number Portability Service and the “calledPartyNumber”.
•  Default Called Party – build the calledPartyNumber contents based on a provisioned Default Called Party data.
•  Multi-Country NPRN– build the calledPartyNumber contents based on a routing number provided by the Multi-Country ETSI Number Portability Service and the “calledPartyNumber”.

If the initialDPSRSRN column references a valid entry from the initialDPSRSRN table, then the INAP InitialDP parameter “calledPartyNumber” shall be built using information from the references initialDPSRSRN table entry. Please refer to Section 4.10.1.1 for the requirements regarding the construction of the address based on an ETSI Subscriber Routing Service’s Routing Number.

If the initialDPNPRN column indicates that the INAP InitialDP parameter “calledPartyNumber” is to be built based on routing number provided by the ETSI Number Portability Service (initialDPNPRN = Yes), then the INAP InitialDP parameter “calledPartyNumber” shall be built according to the requirements in sectionInitialDP Called Party Number Based On ETSI Number Portability Routing Number.

If the defaultIDPCalledParty column references a valid entry from the defaultIDPCalledParty table, then the INAP InitialDP parameter “calledPartyNumber” shall be built using information from the references defaultIDPCalledParty table entry. Please refer to Section InitialDP Called Party Number Based On Default Called Party Number for the requirements regarding the construction of the address based on the provisioned Default Called Party Number data.

If the initialDPMCntNPRN column indicates that the INAP InitialDP parameter “calledPartyNumber” is to be built based on routing number provided by the Multi-Country ETSI Number Portability Service (initialDPMCntNPRN = Yes), then the INAP InitialDP parameter “calledPartyNumber” shall be built according to the requirements in section  InitialDP Called Party Number Based On ETSI Multi-Country Number Portability Routing Number

InitialDP Called Party Number Based On ETSI SRS Routing Number

This section defines the requirements for building the Called Party Number content based on routing number provided by the ETSI Subscriber Routing Service.

The Nature of Address of the “calledPartyNumber” parameter shall be set to digitsFormat associated with the routing number.

The Numbering Plan of the “calledPartyNumber” parameter shall be set to E.164 Numbering Plan.

The digits of the “calledPartyNumber” parameter shall be set to the digits of the routing number.

InitialDP Called Party Number Based On ETSI Number Portability Routing Number

This section defines the requirements for building the Called Party Number content based on routing number provided by the ETSI Number Portability Service.

The Numbering Plan of the “calledPartyNumber” parameter shall remain unchanged.

If ETSI Digit Analysis Service is applied and digit format of the “calledPartyNumber” is International, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• CC + RN + National Significant Portion of the “calledPartyNumber”.

If ETSI Digit Analysis Service is applied and digit format of the “calledPartyNumber” is National, then the digits of the “calledPartyNumber” parameter shall be set as follows:

•  RN + National Significant Portion of the “calledPartyNumber”.

If ETSI Digit Analysis Service is not applied, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• If the “calledPartyNumber” digits format determined is International, then digits shall be set to:

• • CC + RN + National Significant Portion of the “calledPartyNumber”.

• If the “calledPartyNumber” digits format determined is National, then digits shall be set to:
  •   RN + National Significant Portion of the “calledPartyNumber”.

The Nature of Address of the “calledPartyNumber” parameter shall be set as follows:

• International if Country Code is included in “calledPartyNumber” digits
• National if Country Code is not included in “calledPartyNumber” digits.

InitialDP Called Party Number Based On Default Called Party Number

This section defines the requirements for building the Called Party Number content based on provisioned Default Called Party Number data.

The Nature of Address of the “calledPartyNumber” parameter shall be set to natureOfAddress defined in the defaultIDPCalledParty table.

The Numbering Plan of the “calledPartyNumber” parameter shall be set to numberingPlan defined in the defaultIDPCalledParty table.

The digits of the “calledPartyNumber” parameter shall be set to the digits defined in the defaultIDPCalledParty table.

InitialDP Called Party Number Based On ETSI Multi-Country Number Portability Routing Number

This section defines the requirements for building the Called Party Number content based on routing number provided by the ETSI Multi-Country Number Portability Service.

The Numbering Plan of the “calledPartyNumber” parameter shall remain unchanged.

If ETSI Multi-Country Digit Analysis Service is applied and digit format of the “calledPartyNumber” is International, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• CC + RN + National Significant Portion of the “calledPartyNumber”.

  The value of RN depends on the value of mCntNPRNSelection column from the initialDPCalledParty table.

If ETSI Multi-Country Digit Analysis Service is applied and digit format of the “calledPartyNumber” is National, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• RN + National Significant Portion of the “calledPartyNumber”.

If ETSI Multi-Country Digit Analysis Service is not applied, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• If the “calledPartyNumber” digits format determined is International, then digits shall be set to:

• • CC + RN + National Significant Portion of the “calledPartyNumber”.

• If the “calledPartyNumber” digits format determined is National, then digits shall be set to: 
  • RN + National Significant Portion of the “calledPartyNumber.”

The Nature of Address of the “calledPartyNumber” parameter shall be set as follows:

• International if Country Code is included in “calledPartyNumber” digits.
• National if Country Code is not included in “calledPartyNumber” digits.

calledPartyBCDNumber Content

The construction of the “calledPartyBCDNumber” parameter is based on the user’s configuration. The user has several choices that allow the content of the “calledPartyBCDNumber” to be defined.

• SRSRN – build calledPartyBCDNumber contents based on routing number provided by the ETSI Subscriber Routing Service
• NPRN– build calledPartyBCDNumber contents based on routing number provided by the ETSI Number Portability Service and the “calledPartyBCDNumber”

• Default Called Party – build calledPartyBCDNumber contents based on provisioned Default Called Party data

If the initialDPBCDSRSRN column references a valid entry from the initialDPBCDSRSRN table, then the INAP InitialDP parameter “calledPartyNumber” shall be built using information from the references initialDPBCDSRSRN table entry. Please refer to Section InitialDP Called Party BCD Number Based On ETSI SRS Routing Number for the requirements regarding the construction of the address based on the ETSI Subscriber Routing Service’s Routing Number.

If the initialDPBCDNPRN column references a valid entry from the initialDPBCDNPRN table, then the INAP InitialDP parameter “calledPartyNumber” shall be built using information from the references initialDPBCDNPRN table entry. Please refer to Section InitialDP Called Party BCD Number Based On ETSI Number Portability Routing Number  for the requirements regarding the construction of the address based on the ETSI Number Portability Service’s Routing Number.

If the defaultInitialDPBCD column references a valid entry from the defaultInitialDPBCD table, then the INAP InitialDP parameter “calledPartyNumber” shall be built using information from the references defaultInitialDPBCD table entry. Please refer to Section InitialDP Called Party BCD Number Based On Default Called Party Number for the requirements regarding the construction of the address based on the provisioned Default Called Party Number data.

InitialDP Called Party BCD Number Based On ETSI SRS Routing Number

This section defines the requirements for building the Called Party BCD Number content based on routing number provided by the ETSI Subscriber Routing Service.

The Nature of Address of the “calledPartyNumber” parameter shall be set to digitsFormat associated with the routing number.

The Numbering Plan of the “calledPartyNumber” parameter shall be set to E.164 Numbering Plan

The digits of the “calledPartyNumber” parameter shall be set to the digits of the routing number.

InitialDP Called Party BCD Number Based On ETSI Number Portability Routing Number

This section defines the requirements for building the Called Party BCD Number content based on routing number provided by the ETSI Number Portability Service.

The Numbering Plan of the “calledPartyBCDNumber” parameter shall remain unchanged.

If ETSI Digit Analysis Service is applied and digit format of the “calledPartyBCDNumber” is International, then the digits of the “calledPartyBCDNumber” parameter shall be set as follows:

• CC + RN + National Significant Portion of the “calledPartyBCDNumber”.

If ETSI Digit Analysis Service is applied and digit format of the “calledPartyNumber” is National, then the digits of the “calledPartyNumber” parameter shall be set as follows:

• RN + National Significant Portion of the “calledPartyBCDNumber”.

If ETSI Digit Analysis Service is not applied, then the digits of the “calledPartyBCDNumber” parameter shall be set as follows:

• If the “calledPartyBCDNumber” digits format determined is International, then digits shall be set to:

• • CC + RN + National Significant Portion of the “calledPartyBCDNumber”.
• If the “calledPartyBCDNumber” digits format determined is National, then digits shall be set to:
  • RN + National Significant Portion of the “calledPartyBCDNumber”.

The Nature of Address of the “calledPartyBCDNumber” parameter shall be set as follows:

• International if Country Code is included in “calledPartyBCDNumber” digits.
• National if Country Code is not included in “calledPartyBCDNumber” digits.

InitialDP Called Party BCD Number Based On Default Called Party Number

This section defines the requirements for building the Called Party BCD Number content based on provisioned Default Called Party Number data.

The Nature of Address of the “calledPartyBCDNumber” parameter shall be set to natureOfAddress defined in the defaultInitialDPBCD table.

The Numbering Plan of the “calledPartyBCDNumber” parameter shall be set to numberingPlan defined in the defaultInitialDPBCD table.

The digits of the “calledPartyBCDNumber” parameter shall be set to the digits defined in the defaultInitialDPBCD table.

Global Title Address Manipulation

The following parameters are available for modification within the Called Party Address:

• Routing Indicator
• Global Title Indicator
• Subsystem Number
• Translation Type
• Numbering Plan
• Digits

The content of the Called Party Address fundamentally depends upon where the source for constructing the Called Party Address resides. The user has several choices that allow a source for the Called Party Address to be defined.

• Original Called Party Address – build the Called Party Address contents based on the received SCCP Called Party Address.
• SRSRN – build the Called Party Address contents based on a routing number provided by the ETSI Subscriber Routing Service
• NPRN – build the Called Party Address contents based on a routing number provided by the ETSI Number Portability Service and “address source”.
• Default Called Party Address – build the Called Party Address contents based on a provisioned Default Called Party Address data.
• ServiceKeyRN - build the Called Party Address contents based on a routing number provided by the Service Key Routing Service.

The first parameter defined in the sccpCdPAAddressSource table that can be found within the received signaling message shall be used as the source for the modified SCCP Called Party Address.

If the originalCdPA column references a valid entry from the originalCdPA table, then the SCCP Called Party Address shall be built using information from the references originalCdPA table entry. Please refer to Section Original Called Party Address for the requirements regarding the construction of the address based on the original received Called Party Address.

If the srsRN column references a valid entry from the srsRN table, then the SCCP Called Party Address shall be built using information from the references srsRN table entry. Please refer to Section SCCP CdPA based on ETSI Subscriber Routing Service Routing Number for the requirements regarding the construction of the address based on the ETSI Subscriber Routing Service’s Routing Number.

If the npRN column references a valid entry from the npRN table, then the SCCP Called Party Address shall be built using information from the references npRN table entry. Please refer to Section SCCP CdPA based on ETSI Number Portability Service Routing Number for the requirements regarding the construction of the address based on the ETSI Number Portability Service’s Routing Number.

If the defaultCdPA column references a valid entry from the defaultCdPA table, then the SCCP Called Party
Address shall be built using information from the references defaultCdPA table entry. Please refer to Section Default Called Party Address for the requirements regarding the construction of the address based on information from the defaultCdPA table.

If the useServiceKeyRN column indicates that the SCCP Called Party Address shall be built based on
routing information provided by the Service Key Routing Service (useServiceKeyRN = Yes), then the SCCP Called Party Address shall be built according to the requirements in Section SCCP CdPA based on Service Key Routing Service Routing Number.

Original Called Party Address

When the SCCP Called Party Address is to be built using information from the original received Called Party Address, then the following SCCP Called Party Address parameters can be modified:

• Routing Indicator
• Subsystem Number
• Translation Type

If the SCCP Called Party Address does not contain a valid Global Title format (i.e. GTI = 0), then the signaling message shall be discarded.

If the Global Title Address is not 0 then the Routing Indicator shall be set to indicate Global Title routing.

If the Subsystem Number is present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be set to the value contained in the ssn column.

If the Subsystem Number is not present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be inserted into the Called Party Address and set to the value contained in the ssn column.

If the Translation Type is supported by the Global Title Indicator and the modifyTT column indicates that the Translation Type is to be modified (modifyTT = Yes), then the Translation Type shall be set to the value contained in the tt column.

SCCP CdPA based on ETSI Subscriber Routing Service Routing Number

When the SCCP Called Party Address is to be built using information from a Routing Number provided by the ETSI Subscriber Routing Service, then the following SCCP Called Party Address parameters can be built:

• Routing Indicator
• Global Title Indicator
• Subsystem Number
• Translation Type
• Numbering Plan
• Nature of Address
• Digits

If the Global title Indicator does not support a Global Title Address (GTI = 0), then Global Title Indicator shall be set to four (4).

The Routing Indicator shall be set to indicate Global Title routing.

If the Subsystem Number is present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be set to the value contained in the ssn column.

If the Subsystem Number is not present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be inserted into the Called Party Address and set to the value contained in the ssn column.

If the Global Title Indicator supports the Translation Type and the modifyTT column indicates that the Translation Type is to be modified (modifyTT = Yes), then the Translation Type shall be set to the value contained in the tt column.

If the Numbering Plan is supported by the Global Title Indicator, then the Numbering Plan shall be set to E.164 Numbering Plan. 

If the Nature of Address is supported by the Global Title Indicator value, then it shall be set to indicate:

• International if the digitsFormat associated with the routing number indicates international
• National Significant if the digitsFormat associated with the routing number indicates national

The digits shall be set to the digits of the referenced routing number.

SCCP CdPA based on ETSI Number Portability Service Routing Number

When the SCCP Called Party Address is to be built using information from a Routing Number provided by the ETSI Number Portability Service, then the following SCCP Called Party Address parameters can be built:

• Routing Indicator
• Global Title Indicator
• Numbering Plan
• Nature of Address
• Digits

If the Global title Indicator does not support a Global Title Address (GTI = 0), then Global Title Indicator shall be set to four (4).

The Routing Indicator shall be set to indicate Global Title routing.

If the Subsystem Number is present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be set to the value contained in the ssn column.

If the Subsystem Number is not present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be inserted into the Called Party Address and set to the value contained in the ssn column.

If the Global Title Indicator supports the Translation Type and the modifyTT column indicates that the Translation Type is to be modified (modifyTT = Yes), then the Translation Type shall be set to the value contained in the tt column.

If the Global Title Indicator supports the Numbering Plan, then the Numbering Plan shall be set to SCCP
equivalent of the “address source” parameters Numbering Plan.

If ETSI Digit Analysis Service is applied and digit format of the “address source” is International, then the digits shall be set as follows: 

• CC + RN + National Significant Portion of “address source”.

If ETSI Digit Analysis Service is applied and digit format of the “address source” is National, then the digits shall be set as follows: 

• RN + National Significant Portion of “address source”.

If ETSI Digit Analysis Service is not applied, then the digits shall be set as follows:

• If the “address source” digits format determined is International, then digits shall be set to:
• CC + RN + National Significant Portion of “address source”

• If the “address source” digits format determined is National, then digits shall be set to:

• • RN + National Significant Portion of “address source”

    If ETSI Digit Analysis Service is not applied, then the “address source” digits format is determined based on Nature of Address.

    If the “address source” selected is SCCP Called Party Address then the digits format shall be determined.

If the Global Title Indicator supports Nature of Address, then the Nature of Address shall be set as follows:

• International if Country Code is included in Called Party Address digits
• National if Country Code is not included in Called Party Address digits.

Default Called Party Address

When the SCCP Called Party Address is to be built using information from the defaultCdPA table, then the following SCCP Called Party Address parameters can be built:

• Routing Indicator
• Global Title Indicator
• Subsystem Number
• Translation Type
• Numbering Plan
• Nature of Address
• Digits

If the Global title Indicator does not support a Global Title Address (GTI = 0), then Global Title Indicator shall be set to four (4).

The Routing Indicator shall be set to indicate Global Title routing.

If the Subsystem Number is present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be set to the value contained in the ssn column.

If the Subsystem Number is not present in the Called Party Address and the modifySSN column indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be inserted into the Called Party Address and set to the value contained in the ssn column.

If the Global Title Indicator supports the Translation Type and the modifyTT column indicates that the Translation Type is to be modified (modifyTT = Yes), then the Translation Type shall be set to the value contained in the tt column.

If the Global Title Indicator supports the Numbering Plan, then the Numbering Plan shall be set to numberingPlan defined in the defaultCdPA table.

If the Global Title Indicator supports the Nature of Address, then the Nature of Address shall be set to natureOfAddress defined in the defaultCdPA table.

The digits shall be set to digits defined in the defaultCdPA table.

SCCP CdPA based on Service Key Routing Service Routing Number

 When the SCCP Called Party Address is to be built using information from a Routing Number provided by the Service Key Routing Service, then the following SCCP Called Party Address parameters can be built:

• Routing Indicator
• Global Title Indicator
• Subsystem Number
• Translation Type
• Numbering Plan
• Nature of Address
• Digits

If the Global title Indicator does not support a Global Title Address (GTI = 0), then Global Title Indicator shall be set to four (4).

The Routing Indicator shall be set to indicate Global Title routing.

If the Subsystem Number is present in the Called Party Address and the modifySSN column from the found routing number table entry indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be set to the ssn associated with the referenced routing number.

If the Subsystem Number is not present in the Called Party Address and the modifySSN column from the found routing number table entry indicates that the Subsystem Number is to be set (modifySSN = Yes), then the Subsystem Number shall be inserted into the Called Party Address and set to the ssn associated with the referenced routing number.

If the Global Title Indicator supports the Translation Type and the modifyTT column from the found routing number table entry indicates that the Translation Type is to be modified (modifyTT = Yes), then the Translation Type shall be set to the translationType associated with the referenced routing number.

If the Global Title Indicator supports the Numbering Plan, then the Numbering Plan shall be set to the numberingPlan associated with the referenced routing number.

If the Global Title Indicator supports the Nature of Address, then the Nature of Address shall be set to natureOfAddress associated with the referenced routing number.

The digits shall be set to digits of the referenced routing number. 

Schemas

The following tables are declared within the INAP InitialDP Service Handler database:

• shConfiguration
• shServiceDescription
• initialDPListForSN
• defaultCCForMCntNP
• returnError
• releaseCall
• resolveAmbiguity
• requestReportBCSM
• legID
• dpSpecificCriteria
• announcementData
• connectToResource
• resourceAddress
• playAnnouncement
• informationToSend
• inbandInfo
• messageID
• tone
• connect
• connectParameters
• draCalledPartyNumber
• draSRSRN
• rnTypeforSRSRN
• defaultDRACdPA
• serviceIntIndTwo
• forwardSvcIntInd
• backwardSvcIntInd
• sendChargingInformation
• partyToCharge
• sciFormat2
• scpChargeNumber
• scpChrgNumSRSRN
• defaultSCPChrgNum
• sciFormat3
• sciBillingChrgCh
• sciBillingSRSRN
• defaultSCIBilling
• relay
• sccpCalledPartyAddress
• sccpCdPAAddressSource
• originalCdPA
• srsRN
• defaultCdPA
• initialDPParameters
• initialDPCalledParty
• initialDPSRSRN
• defaultIDPCalledParty
• initialDPCalledPartyBCD
• initialDPBCDSRSRN
• defaultInitialDPBCD
• shSRSEvent
• shTCAPScrnEvent
• shNPEvent
• shDigitAnalysisEvent
• shMultiCntDAEvent
• shLoopDetectionEvent
• shMultiCntLAEvent
• shINAPContentScrEvent
• shMultiCntNPEvent
• shServiceKeyEvent
• npRN

The schema for the database shall be named inap_schema.

The table space for the INAP InitialDP Service Handler database shall be named inapsh_ts and be configured as: /nfmd0a/fr/dbs/inap_shdb

The database name for INAP InitialDP Service Handler database shall be inap_shdb and use the inapsh_ts table space.

shConfiguration

The shConfiguration table declares general parameters for the Service Handler that can vary from one instance to another.

The table name of the shConfiguration table shall be shConfiguration. The following columns shall be defined in the shConfiguration table:

shConfiguration

The primary key for the shConfiguration table shall be sh column.

shServiceDescription

The shServiceDescription table declares the services that are enabled for the Service Handler and the order in which the service will be applied.

The table name of the shServiceDescription table shall be shServiceDescription. The following columns shall be defined in the shServiceDescription table:

shServiceDescription

The primary key for the shServiceDescription table shall be sh and order column.

InitialDPListForSN

The initialDPListForSN table declares the InitialDP List of Parameters for Subscriber Number.

The table name of the initialDPListForSN table shall be initialDPListForSN. The following columns shall be defined in the initialDPListForSN table:

initialDPListForSN

The primary key for the initialDPListForSN table shall be the name column.

defaultCCForMCntNP

The defaultCCForMCntNP table declares the default country code that shall be used for the ETSI Multi- Country Number Portability service when the Subscriber Number digits are received in national format.

The table name of the defaultCCForMCntNP table shall be defaultCCForMCntNP. The following columns shall be defined in the defaultCCForMCntNP table:

The primary key for the defaultCCForMCntNP table shall be sh column.

returnError

The returnError table declares a TCAP error code that can be used by the Service Handler.

The table name of the returnError table shall be returnError. The following columns shall be defined in the returnError table:

The primary key for the returnError table shall be the name column.

releaseCall

The releaseCall table declares the content of the “Release Call” operation that is available for the Service Handler to use

The table name of the releaseCall table shall be releaseCall. The following columns shall be defined in the releaseCall table:

The primary key for the releaseCall table shall be the name column.

resolveAmbiguity

The resolveAmbiguity table declares the content of the “Resolve Ambiguity” response that is available for the Service Handler to use.

The table name of the resolveAmbiguity table shall be resolveAmbiguity. The following columns shall be defined in the resolveAmbiguity table:

The primary key for the resolveAmbiguity table shall be the name column.

requestReportBCSM

The requestReportBCSM table declares the content of the “requestReportBCSM” operation that is available for the Service Handler to use.

The table name of the requestReportBCSM table shall be requestReportBCSM. The following columns shall be defined in the requestReportBCSM table:

The primary key for the requestReportBCSM table shall be the name column.

legID

The legID table declares the content of the “legID” parameter that is available for the Service Handler to use.

The table name of the legID table shall be legID. The following columns shall be defined in the legID table:

The primary key for the legID table shall be the name column.

dpSpecificCriteria

The dpSpecificCriteria table declares the content of the “dpSpecificCriteria” parameter that is available for the Service Handler to use.

The table name of the dpSpecificCriteria table shall be dpSpecificCriteria. The following columns shall be defined in the dpSpecificCriteria table:

The primary key for the dpSpecificCriteria table shall be the name column.

announcementData

The announcementData table declares the content of the “requestReportBCSM.playAnnouncement” parameter that is available for the Service Handler to use.

The table name of the announcementData table shall be announcementData. The following columns shall be defined in the announcementData table:

The primary key for the playAnnouncement table shall be the name column.

connectToResource

The connectToResource table declares the content of the “connectToResource” operation that is available for the Service Handler to use.

The table name of the connectToResource table shall be connectToResource. The following columns shall be defined in the connectToResource table:

The primary key for the connectToResource table shall be the name column.

resourceAddress

The resourceAddress table declares the content of the “resourceAddress” parameter that is available for the Service Handler to use.

The table name of the resourceAddress table shall be resourceAddress. The following columns shall be defined in the resourceAddress table:

The primary key for the resourceAddress table shall be the name column.

playAnnouncement

The playAnnouncement table declares the content of the “playAnnouncement” operation that is available for the Service Handler to use.

The table name of the playAnnouncement table shall be playAnnouncement. The following columns shall be defined in the playAnnouncement table:

The primary key for the playAnnouncement table shall be the name column.

informationToSend

The informationToSend table declares the content of the “informationToSend” parameter that is available for the Service Handler to use.

The table name of the informationToSend table shall be informationToSend. The following columns shall be defined in the informationToSend table:

The primary key for the informationToSend table shall be the name column.

inbandInfo

The inbandInfo table declares the content of the “inbandInfo” parameter that is available for the Service Handler to use.

The table name of the inbandInfo table shall be inbandInfo. The following columns shall be defined in the inbandInfo table:

The primary key for the inbandInfo table shall be the name column.

messageID

The messageID table declares the content of the “messageID” parameter that is available for the Service Handler to use.

The table name of the messageID table shall be messageID. The following columns shall be defined in the messageID table:

The primary key for the messageID table shall be the name column.

tone

The tone table declares the content of the “tone” parameter that is available for the Service Handler to use.

The table name of the tone table shall be tone. The following columns shall be defined in the tone table:

The primary key for the tone table shall be the name column.

connect

The connect table defines the content of the INAP operation “Connect” that is available for the Service Handler to use.

The table name of the connect table shall be connect. The following columns shall be defined in the connect table:

The primary key for the connect table shall be the name column.

connectParameters

The connectParameters table defines the content of the “connect” parameters that is available for the Service Handler to use.

The table name of the connectParameters table shall be connectParameters. The following columns shall be defined in the connectParameters table:

The primary key for the connectParameters table shall be the name column.

draCalledPartyNumber

The draCalledPartyNumber table defines the choice for building the “connect.destinationRoutingAddress” parameter “calledPartyNumber” that is available for the Service Handler to use.

The table name of the draCalledPartyNumber table shall be draCalledPartyNumber. The following columns shall be defined in the draCalledPartyNumber table:

The primary key for the draCalledPartyNumber table shall be the name column.

draSRSRN

The draSRSRN table declares the content of the “connect.destinationRoutingAddress” parameter “calledPartyNumber” that is available for the Service Handler to use.

The table name of the draSRSRN table shall be draSRSRN. The following columns shall be defined in the draSRSRN table:

The primary key for the draSRSRN table shall be the name column.

 rnTypeforSRSRN

The rnTypeforSRSRN table gives the routing number type for the ETSI Subscriber Routing Service Routing Number.

The table name of the rnTypeforSRSRN table shall be rnTypeforSRSRN. The following columns shall be defined in the rnTypeforSRSRN table:

The primary key for the rnTypeforSRSRN table shall be sh column.

defaultDRACdPA

The defaultDRACdPA table declares the content of the “connect.destinationRoutingAddress” parameter “calledPartyNumber” that is available for the Service Handler to use.

 The table name of the defaultDRACdPA table shall be defaultDRACdPA. The following columns shall be defined in the defaultDRACdPA table:

The primary key for the defaultDRACdPA table shall be the name column.

serviceIntIndTwo

The serviceIntIndTwo table defines the content of the “serviceInteractionIndicatorsTwo” parameter that is available for the Service Handler to use.

The table name of the serviceIntIndTwo table shall be serviceIntIndTwo. The following columns shall be defined in the serviceIntIndTwo table:

The primary key for the serviceIntIndTwo table shall be the name column.

forwardSvcIntInd

The forwardSvcIntInd table defines the content of the “forwardServiceInteractionIndicator” parameter that is available for the Service Handler to use.

The table name of the forwardSvcIntInd table shall be forwardSvcIntInd. The following columns shall be defined in the forwardSvcIntInd table:

The primary key for the forwardSvcIntInd table shall be the name column.

backwardSvcIntInd

The backwardSvcIntInd table defines the content of the “backwardServiceInteractionIndicator” parameter that is available for the Service Handler to use.

The table name of the backwardSvcIntInd table shall be backwardSvcIntInd. The following columns shall be defined in the backwardSvcIntInd table:

The primary key for the backwardSvcIntInd table shall be the name column.

sendChargingInformation

The sendChargingInformation table defines the choice for the Send Charging Information operation.

The table name of the sendChargingInformation table shall be sendChargingInformation. The following columns shall be defined in the sendChargingInformation table:

The primary key for the sendChargingInformation table shall be the name column.

partyToCharge

The partyToCharge table defines the content of the “partyToCharge” parameter that is available for the Service Handler to use.

The table name of the partyToCharge table shall be partyToCharge. The following columns shall be defined in the partyToCharge table:

The primary key for the partyToCharge table shall be the name column.

sciFormat2

The sciFormat2 table defines the content of the Send Charging Information Format2.

The table name of the sciFormat2 table shall be sciFormat2. The following columns shall be defined in the sciFormat2 table:

The primary key for the sciFormat2 table shall be the name column.

scpChargeNumber

The scpChargeNumber table defines the content of the “scpChargeNumber” parameter that is available for the Service Handler to use.

The table name of the scpChargeNumber table shall be scpChargeNumber. The following columns shall be defined in the scpChargeNumber table:

The primary key for the scpChargeNumber table shall be the name column.

scpChrgNumSRSRN

The scpChrgNumSRSRN table declares the content of the “scpChargeNumber” parameter that is available for the Service Handler to use.

The table name of the scpChrgNumSRSRN table shall be scpChrgNumSRSRN. The following columns shall be defined in the scpChrgNumSRSRN table:

The primary key for the scpChrgNumSRSRN table shall be the name column.

defaultSCPChrgNum

The defaultSCPChrgNum table declares the content of the “scpChargeNumber” parameter that is available for the Service Handler to use.

The table name of the defaultSCPChrgNum table shall be defaultSCPChrgNum. The following columns shall be defined in the defaultSCPChrgNum table:

The primary key for the defaultSCPChrgNum table shall be the name column.

sciFormat3

The sciFormat3 table defines the content of the Send Charging Information Format3.

The table name of the sciFormat3 table shall be sciFormat3. The following columns shall be defined in the sciFormat3 table:

The primary key for the sciFormat3 table shall be the name column.

sciBillingChrgCh

The sciBillingChrgCh table defines the content of the “SCIBillingChargingCharacteristics” parameter.

The table name of the sciBillingChrgCh table shall be sciBillingChrgCh. The following columns shall be defined in the sciBillingChrgCh table:

The primary key for the sciBillingChrgCh table shall be the name column.

sciBillingSRSRN

The sciBillingSRSRN table declares the content of the “SCIBillingChargingCharacteristics” parameter that is available for the Service Handler to use.

The table name of the sciBillingSRSRN table shall be sciBillingSRSRN. The following columns shall be defined in the sciBillingSRSRN table:

The primary key for the sciBillingSRSRN table shall be the name column.

defaultSCIBilling

The defaultSCIBilling table declares the content of the “SCIBillingChargingCharacteristics” parameter that is available for the Service Handler to use.

The table name of the defaultSCIBilling table shall be defaultSCIBilling. The following columns shall be defined in the defaultSCIBilling table:

The primary key for the defaultSCIBilling table shall be the name column.

relay

The relay table defines the content of a “relay” response.

The table name of the relay table shall be relay. The following columns shall be defined in the relay table:

The primary key for the relay table shall be the name column.

sccpCalledPartyAddress

The sccpCalledPartyAddress table declares the content of the SCCP Called Party Address that is available for the Service Handler to use.

The table name of the sccpCalledPartyAddress table shall be sccpCalledPartyAddress. The following columns shall be defined in the sccpCalledPartyAddress table:

The primary key for the sccpCalledPartyAddress table shall be the name column.

sccpCdPAAddressSource

The sccpCdPAAddressSource table defines the source for building the SCCP Called Party Address.

The table name of the sccpCdPAAddressSource table shall be sccpCdPAAddressSource. The following columns shall be defined in the sccpCdPAAddressSource table:

The primary key for the sccpCdPAAddressSource table shall be the name column.

originalCdPA

The originalCdPA table declares the content of the SCCP Called Party Address that is available for the Service Handler to use.

The table name of the originalCdPA table shall be originalCdPA. The following columns shall be defined in the originalCdPA table:

The primary key for the originalCdPA table shall be the name column.

srsRN

The srsRN table declares the content of the SCCP Called Party Address that is available for the Service Handler to use.

The table name of the srsRN table shall be srsRN. The following columns shall be defined in the srsRN table:

The primary key for the srsRN table shall be the name column.

defaultCdPA

The defaultCdPA table declares the content of the SCCP Called Party Address that is available for the
Service Handler to use.

The table name of the defaultCdPA table shall be defaultCdPA. The following columns shall be defined in the defaultCdPA table:

The primary key for the defaultCdPA table shall be the name column.

initialDPParameters

The initialDPParameters table defines the content of an INAP InitialDP message.

The table name of the initialDPParameters table shall be initialDPParameters. The following columns shall be defined in the initialDPParameters table:

The primary key for the initialDPParameters table shall be the name column.

initialDPCalledParty

The initialDPCalledParty table defines the content of an INAP InitialDP message.

The table name of the initialDPCalledParty table shall be initialDPCalledParty. The following columns shall be defined in the initialDPCalledParty table:

The primary key for the initialDPCalledParty table shall be the name column.

initialDPSRSRN

The initialDPSRSRN table declares the content of the INAP InitialDP parameter “calledPartyNumber” that is available for the Service Handler to use.

The table name of the initialDPSRSRN table shall be initialDPSRSRN. The following columns shall be defined in the initialDPSRSRN table:

The primary key for the initialDPSRSRN table shall be the name column.

defaultIDPCalledParty

The defaultIDPCalledParty table declares the content of the INAP InitialDP parameter “calledPartyNumber” that is available for the Service Handler to use.

The table name of the defaultIDPCalledParty table shall be defaultIDPCalledParty. The following columns shall be defined in the defaultIDPCalledParty table:

The primary key for the defaultIDPCalledParty table shall be the name column.

initialDPCalledPartyBCD

The initialDPCalledPartyBCD table defines the content the “calledPartyNumberBCD” parameter that is available for the Service Handler to use.

The table name of the initialDPCalledPartyBCD table shall be initialDPCalledPartyBCD. The following columns shall be defined in the initialDPCalledPartyBCD table:

The primary key for the initialDPCalledPartyBCD table shall be the name column.

initialDPBCDSRSRN

The initialDPBCDSRSRN table declares the content of the “calledPartyNumberBCD” parameter that is available for the Service Handler to use.

The table name of the initialDPBCDSRSRN table shall be initialDPBCDSRSRN. The following columns shall be defined in the initialDPBCDSRSRN table:

The primary key for the initialDPBCDSRSRN table shall be the name column.

defaultInitialDPBCD

The defaultInitialDPBCD table declares the content of the “calledPartyNumberBCD” parameter that is available for the Service Handler to use.

The table name of the defaultInitialDPBCD table shall be defaultInitialDPBCD. The following columns shall be defined in the defaultInitialDPBCD table:

The primary key for the defaultInitialDPBCD table shall be the name column.

shSRSEvent

The shSRSEvent table maps the events generated by the ETSI Subscriber Routing Service to responses that are provided by the Service Handler.

The table name of the shSRSEvent table shall be shSRSEvent. The following columns shall be defined in the shSRSEvent table:

The primary key for the shSRSEvent table shall be sh and event columns.

shTCAPScrnEvent

The shTCAPScrnEvent table maps the events generated by the TCAP Screening Service to responses that are provided by the Service Handler.  

The table name of the shTCAPScrnEvent table shall be shTCAPScrnEvent. The following columns shall be defined in the shTCAPScrnEvent table:

The primary key for the shTCAPScrnEvent table shall be sh and event columns.

shNPEvent

The shNPEvent table maps the events generated by the ETSI Number Portability Service to responses that are provided by the Service Handler.

The table name of the shNPEvent table shall be shNPEvent. The following columns shall be defined in the shNPEvent table:

The primary key for the shNPEvent table shall be sh and event columns.

shDigitAnalysisEvent

The shDigitAnalysisEvent table maps the events generated by the ETSI Digit Analysis Service to responses that are provided by the Service Handler.

The table name of the shDigitAnalysisEvent table shall be shDigitAnalysisEvent. The following columns shall be defined in the shDigitAnalysisEvent table:

The primary key for the shDigitAnalysisEvent table shall be sh and event columns.

shMultiCntDAEvent

The shMultiCntDAEvent table maps the events generated by the ETSI Multi-Country Digit Analysis Service to responses that are provided by the Service Handler.

The table name of the shMultiCntDAEvent table shall be shMultiCntDAEvent. The following columns shall be defined in the shMultiCntDAEvent table:

The primary key for the shMultiCntDAEvent table shall be sh and event columns.

shLoopDetectionEvent

The shLoopDetectionEvent table maps the events generated by the ETSI Loop Detection Analysis Service to responses that are provided by the Service Handler.

The table name of the shLoopDetectionEvent table shall be shLoopDetectionEvent. The following columns shall be defined in the shLoopDetectionEvent table:

The primary key for the shLoopDetectionEvent table shall be sh and event columns.

shMultiCntLAEvent

The shMultiCntLAEvent table maps the events generated by the ETSI Multi-Country Loop Detection Analysis Service to responses that are provided by the Service Handler.

The table name of the shMultiCntLAEvent table shall be shMultiCntLAEvent. The following columns shall be defined in the shMultiCntLAEvent table:

The primary key for the shMultiCntLAEvent table shall be sh and event columns.

shINAPContentScrEvent

The shINAPContentScrEvent table maps the events generated by the INAP Content Screening Service to responses that are provided by the Service Handler.

The table name of the shINAPContentScrEvent table shall be shINAPContentScrEvent. The following columns shall be defined in the shINAPContentScrEvent table: