Heksagon Destination Management Solution
Gain centralized control over routing and billing destination hierarchies and prefix organization.
Maximize Routing Accuracy. Standardize Destination Structures
Inconsistent destination structures among carriers create fundamental mapping challenges that prevent effective routing comparison, lead to billing disputes, and make selling pricelists unreliable.
Template Destination Tables solve this by establishing a single master destination hierarchy. Heksagon’s Destination Management automatically translates each carrier's native structure into your standard template during import, enabling consistent routing optimization. Maintain multiple destination templates (e.g., for international routing or selling pricelist generation) to ensure the appropriate granularity for every business function. Apply new pricing instantly and gain the ability to eliminate incorrect billing and improve operational efficiency at scale.
Heksagon Destination Management Features
Destination Management supports multiple template types and organizational strategies within a single deployment, enabling operators to maintain appropriate destination granularity for routing optimization, regulatory compliance, billing accuracy, and customer pricing simultaneously without conflicts.
Unified Destination Structure & Standardization
- Template Destination Architecture: Establish a single master hierarchy that standardizes all carrier pricing data for consistent LCR optimization and billing.
- Multi-Template Support: Maintain independent destination structures for different needs, such as high-granularity routing, national numbering plans (regulatory compliance), and simplified customer-facing product pricing.
- Multi-Language Support: Store and display destination names in alternate languages to support region-specific reporting and customer communication.
Automated Mapping and Data Integrity
- Automatic Destination Mapping: Instantly translate a carrier's native destinations to your internal templates during pricelist import using prefix correlation.
- Mapping Validation and Alerting: Automatically flag errors like unmatched carrier prefixes (preventing orphaned pricing) and new prefix detection, ensuring your master templates are always current.
- Prefix Conflict Detection: Identify and resolve overlapping prefixes across destinations to eliminate routing ambiguity and disputes.
- Validity Period Management: Define destination and prefix effective dates to manage planned numeration changes and support historical analysis.
Routing, Billing, and Commercial Integration
- Granular Routing Control: Enable routing decisions down to the individual number level, while assigning optimization algorithms, quality thresholds, and business rules per destination or group.
- Product-Specific Pricing: Define product-specific destination sets to control which destinations appear in customer pricelists and how they are named, supporting tailored service tiers.
- Zero-Rated Filtering Support: Automatically manage the inclusion or exclusion of zero-priced destinations from customer pricelists, optimizing clarity and preventing clutter.
- Audit Readiness: Deactivate old destinations while preserving historical data for billing reconciliation, regulatory reporting, and dispute resolution.
How Heksagon Destination Management Works
Heksagon Destination Management operates as the foundational reference data layer that ensures consistency across all interconnect processes. Template structures flow into routing optimization for carrier comparison, selling pricelist generation for customer presentation, billing validation for invoice accuracy, and analytics for commercial reporting.
Template Organization and Maintenance
Template Destination Tables establish the single, standardized destination structure for your entire operation.
- Routing Destinations: These form the primary template, organizing prefixes at the optimal granularity (e.g., country + network type) required for effective carrier price comparison and routing optimization.
- Product Destinations: These reference the routing destinations but group them into customer-friendly categories for selling pricelists. For example, multiple granular mobile destinations can roll up to a single "Mobile" product destination.
Maintenance accommodates all numeration changes, new prefixes, and regulatory updates. Validity dates track when these changes take effect, ensuring routing uses the correct definitions for any given time period, and all modifications are logged for audit purposes.
Integration Across the Interconnect Lifecycle
The standardized destination structure ensures accurate and consistent data across all major LCR functions.
- Pricelist Import: Price Management automatically maps carrier destinations to your templates, enabling apples-to-apples price comparison regardless of the carrier's native structure. Unmapped prefixes are flagged for review.
- Routing & Switch: The Intelligent LCR and Switch Automation reference the same templates when generating priority lists and making real-time routing decisions, guaranteeing consistent destination treatment.
- Billing & Analytics: Billing processes validate CDR destinations against the templates for accurate charging. Analytics aggregates traffic and financial data by template destinations for consistent commercial reporting across time periods.
Didn't Find What You Were Looking For?
Frequently Asked Questions
Why maintain multiple destination templates instead of one unified structure?
Different interconnect functions require different destination granularities. Routing optimization needs detailed carrier comparison (separating mobile networks), while customer pricelists need simplified presentation (combined mobile). Multiple templates serve each purpose optimally without forcing inappropriate granularity on all functions.
How does Heksagon’s solution handle carriers that frequently change destination structures?
Provider destination tables store each carrier's native, changing structure automatically during import. Mapping rules then translate this volatility to stable internal templates, insulating routing and billing from carrier reorganizations. Only mapping updates are needed, not core routing logic.
What happens when number portability moves prefixes between carriers?
MNP data (Mobile Number Portability) is loaded into special destination tables that override standard prefix-to-carrier associations. Routing queries check MNP tables first, ensuring ported numbers route correctly. This separation maintains template integrity while accommodating real-time portability changes.
Can destination templates accommodate country-specific regulatory requirements?
Yes. Special destination tables support regulatory numeration structures that may differ from commercial routing organization. For instance, national billing might require destination breakdown by original number range owner per mandate, while international routing uses simpler country-level organization. Both coexist independently.
How are destination changes communicated to external systems?
The platform provides interface options for destination template synchronization, including file export (CSV/Excel), API access for real-time queries, and direct database links. External systems retrieve current template structures, prefix assignments, and validity dates to maintain consistency across the ecosystem.
Let's Get in Touch!
Interested in our Destination Management solution? Fill out the form and our solution experts will contact you in two business days!