Alias APN Translation for Seamless Carrier Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing technologies face challenges in seamlessly migrating wireless devices from one carrier network to another due to differences in Access Point Names (APNs), leading to issues such as the need for manual updates, incompatibility between device management clients, and the inability to connect to new networks without pre-loaded carrier-specific APNs or device management clients, especially with low-cost devices.

Innovation Solution

The introduction of alias APNs, which allow for the translation of non-standard APNs from one carrier network to another, enabling wireless devices to connect to a new network by mapping external APNs to internal APNs within the Home Subscriber Server, facilitating transparent APN updates without reprogramming the device APN tables.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If carrier-specific APNs are used in wireless networks, then network connectivity and service quality are improved, but device compatibility and ease of migration between carriers deteriorate

Engineering Contradiction:

Improvenetwork connectivityVSAvoiddevice compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary translation mechanism between device APN tables and network APN requirements. The network translates carrier-specific APNs into device-recognized APNs, acting as a mediator that allows devices to maintain their original APN configurations while connecting to different carrier networks through translation.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes APN parameters based on the target carrier network. Instead of requiring fixed carrier-specific APNs in devices, the network modifies APN parameters (names, types, protocols) to match both the device capabilities and the target carrier requirements, enabling flexible migration.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If manual APN updates are performed during carrier migration, then network connectivity is restored, but user convenience and migration simplicity deteriorate

Engineering Contradiction:

Improvenetwork connectivityVSAvoidmigration simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements automated self-service migration where the network automatically translates and updates APN configurations without requiring user intervention. When a device registers with a new carrier, the network autonomously performs APN translation and updates the device's APN table, eliminating manual configuration steps.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The network performs preliminary APN translation and configuration updates before the device actually needs to connect. By pre-translating APNs during the registration phase and storing them in the device's APN table, the system ensures connectivity is ready without requiring manual updates at the point of need.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If device APN tables are reprogrammed for new carriers, then network compatibility is improved, but device complexity and manufacturing burden increase

Engineering Contradiction:

Improvenetwork compatibilityVSAvoiddevice management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of programming devices with multiple carrier-specific APN tables, the patent inverts the approach by keeping a single universal APN table in the device and performing translation at the network side. This reduces device complexity while maintaining compatibility with multiple carriers through the network's translation capability.

Inventive Principle:

Principle #13The other way round (Inversion)

4Reliability

If carrier-specific device management clients are required, then service quality is improved, but ease of manufacture and device cost deteriorate

Engineering Contradiction:

Improveservice qualityVSAvoiddevice production simplicity

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The patent makes the device management client universal by removing carrier-specific requirements. A single client implementation can work with multiple carriers because the network handles carrier-specific translations, eliminating the need for separate carrier-specific client versions and simplifying device manufacturing.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10736014B2Simplified carrier migration using alias access point identification

Publication Date: 2020.08.04 VERIZON PATENT & LICENSING INC

AI summary

A network receives a connection request, from a wireless device, that includes a first Access Point Name (APN) that is invalid in a first wireless carrier network. The network device translates the first APN to a second APN that is valid in the first wireless carrier network. The network device uses the second APN in signaling associated with a connection between the wireless device and the first wireless carrier network.