1. SIR Basics – 1 Shared Registration System (SRS)
User Input:
Rules
Routing Patterns
Mobile ID Input:
Number Portability
LERG/GDD
Provisioning/
User Interface
Industry Data Acquisition
MySQL
Database
Rules Scheduling
Rules
Processing
Distribution
SOAP Routing Data
Target Name Servers

2. SIR Basics – 2 Routing Patterns
A collection of ENUM Resource Records to be used for the Routing result Distributed to Name servers
Resource Record Types
NS – Name Server delegation for Tier 1 operation
Ex: NS NS04.VERIZON.NET.
NAPTR – Final Routing data for Tier 2 operation
Ex: NAPTR "U" "E2U+SIP"
Ex: NAPTR "U" "E2U+SMS"
Ex: NAPTR "U" "E2U+MMS"
Readily extensible for other record types, if needed
Special case – TXT record used as a “NULL” placeholder

3. SIR Basics – 3 Rules – These seven types:
Registrations (Apply to one numbering object)
TNs (T – 10-dig NANP, E – E.164 International
National Destination Codes (N – NXX, B – 1000s Block, C – International NDC)
Broad Rules (Apply to many TNs and NDCs)
Routing Location (L – LRNs, Routing Numbers/Prefixes)
Ranges (R – 3, 6, 7 digits US/CA, 1 to 9 digits elsewhere)
Each Rule has an owning “Entity” and a Routing Pattern result
Each Entity is “equivalent” to a set of MID Company Codes

4. SIR Basics – 4 “Routine” vs. “Mass” Changes Routine Change Processing
Routine Changes are handled at the next processing cycle.
Applies to: Most Registration Rules and Industry changes and “small” Range Rules ( up to 10K subtending TNs)
Exception: High volume of changes in one cycle.
“Mass” Changes are handled as a background process
Applies to: High-volume changes, “large” Range Rules, Location Rules, Routing Pattern Changes, Company Equivalency Changes
Use available work time between routine cycles
Rotate through the numbering plan, consider leading digits
Select and process efficiently-sized segments of work

5. SIR Routing Examples
A Hypothetical Service-Provider with realistic Industry Data (Entity ID AT001)
In NPA 732, uses a broad rule to leverage very detailed TN-by-TN LNP data for all assigned TNs
For one particular set of TNs, wants to provide a new TN-specific routing
Pick a Numbering Object, TN1
Follow a Rule creation for TN1, and then a port for TN1

6. SIR Examples: What Happens 1
(Per-TN Rule overrides NPA range Rule)
Initially, TN1 ( ) assigned to AT001
Range rule for NPA 732 gives Routing Pattern ATRP14, one NS record result
Step 1. AT001 adds a Rule for TN1, giving RP ATRP15, one NAPTR record results

7. SIR Examples: What Happens 2
(Per-TN Rule becomes inoperative on Port-Out)
After previous step, TN1 ( ) still assigned to AT001
TN rule for gives Routing Pattern ATRP15, one NAPTR record result
Step 2. Port TN1 to a non-participating SP
Picks up ‘NULL’ RP, one TXT record result (returns no-record when queried for NAPTR)