SCCP Global Title Translation For Number Portability
When a subscriber changes carrier but keeps the same telephone number, the network must discover the current destination before completing the call or signalling transaction. In SS7 environments, SCCP Global Title Translation (GTT) performs this lookup by converting addressing information into a routable destination, often with support from a number portability database.
For Australian carriers and service providers, this process connects legacy signalling with IP-based SIGTRAN networks, mobile cores, SMS platforms, and interconnects. A correct design must account for number ranges, ported numbers, routing indicators, translation types, and the behaviour of signalling transfer points.
| Area | Before Number Portability | With SCCP GTT For Port-In |
|---|---|---|
| Address used | Original carrier or number-range assumption | Translated routing address |
| Database role | Limited or absent | Identifies the recipient network |
| SCCP function | Basic global title routing | Digit analysis and translation |
| Main risk | Misrouted signalling | Stale data, loops, or failed translations |
| Typical result | Delivery to the range holder | Delivery to the current service provider |
How Port-In Routing Works
A port-in occurs when a customer moves a service to a new provider while retaining the existing number. The number’s original allocation no longer reliably identifies the serving network. A signalling node therefore sends the relevant digits to an NPDB or an integrated portability service, which returns a routing number, network identifier, or translated global title.
The lookup may be triggered for mobile terminating calls, SMS delivery, prepaid service checks, intelligent network queries, or other transactions. SCCP then uses the returned information to select a destination point code, subsystem number, or another global title. The application layer, such as MAP or TCAP, remains focused on the transaction while SCCP handles the addressing decision.
In Australia, this distinction matters across mobile and fixed services, including traffic between Sydney, Melbourne, Brisbane, and regional networks. A number beginning with a familiar mobile or geographic pattern should not be treated as proof of the current carrier.
SCCP Parameters That Shape Translation
A Global Title contains more than the telephone digits. Important fields include the translation type, numbering plan, nature of address indicator, encoding scheme, and address digits. The combination tells an STP how to interpret the value and which translation rule set to apply.
For port-in routing, a rule may match a national significant number, remove an international prefix, or normalise an Australian number beginning with +61 into the format expected by the portability platform. The translation can then replace the original global title with a routing address associated with the recipient network.
Operators should define separate handling for international format, national format, short codes, and service numbers. An incorrect odd or even address indicator can corrupt digit interpretation, while a mismatched numbering plan may cause the STP to reject the message or send it to a default route.
Building A Reliable GTT Rule Set
A practical design starts with a clear decision path: identify the message type, inspect the called party address, normalise the number, query or apply portability data, and route the result. Rules should be ordered from the most specific match to broader fallbacks so that special ranges and service codes are not captured by a generic prefix.
The portability database must be synchronised with the authoritative operational source. Update delays can send traffic to the donor carrier after a successful port-in, while duplicated records can create inconsistent results between geographically separate STPs. A controlled response is needed when the database is unavailable, including a defined fallback route, alarm, retry policy, or rejection treatment.
The signalling topology also affects reliability. Engineers sizing an Australian deployment across multiple sites can use this link-set guide when considering link-set capacity, redundancy, and traffic distribution. The GTT function should have diverse signalling paths rather than relying on one physical or virtual connection.
Testing, Monitoring, And Security
Testing should include ported and non-ported numbers, recently changed records, invalid digits, international presentation, unavailable database responses, and messages arriving from each interconnect. Capture SCCP fields and trace the complete path through the STP, portability service, signalling gateway, and destination network.
Useful operational metrics include translation success rate, database response time, rejected global titles, fallback usage, routing loops, and traffic by destination point code. Alarms should distinguish a genuine unreachable network from a formatting error or an exhausted translation table. During a major event, such as a sporting match in Melbourne or a public holiday surge, capacity data can reveal whether delays come from GTT processing or downstream congestion.
Security controls are equally important. Screen incoming global titles, restrict who may submit translation requests, validate response formats, and prevent unauthorised point-code or subsystem-number access. SIGTRAN deployments should combine SCTP protection, network segmentation, traffic filtering, and disciplined access to signalling gateways. Relevant SS7 solutions can be assessed alongside the existing architecture rather than added as isolated components.
Operational Takeaways For Australian Networks
Number portability makes prefix-based routing insufficient. SCCP GTT must translate the address according to current portability information, preserve the correct SCCP indicators, and deliver the message through a valid signalling route. This is especially important where carriers exchange traffic between metropolitan and regional infrastructure or bridge SS7 services into Diameter, SIP, and other IP systems.
A sound implementation keeps translation logic documented, tests every number format, monitors database freshness, and records the original and translated addresses for troubleshooting. The practical takeaway is simple: treat the dialled number as an input to a controlled portability lookup, then verify that the resulting global title, point code, subsystem, and fallback path all lead to the current serving network.
