FQDN-Based Mobile Device Registration in Packet Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As the number of devices on mobile communication networks increases, network operators face a shortage of mobile device numbers (MDNs and MSISDNs) for allocating packet-based addresses, particularly for devices not configured for voice or messaging services, necessitating a method to register devices using fully-qualified domain names (FQDNs) for data communications.
Innovation Solution
A system where a packet data network gateway (PGW) generates and assigns packet-based addresses to mobile devices, which are then associated with FQDNs through an authentication, authorization, and accounting (AAA) server and dynamic DNS server, enabling devices to communicate with internet-connected servers without requiring MDNs or MSISDNs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If MDNs and MSISDNs are used to identify and address devices for data communications, then devices can be uniquely identified on the network, but network operators will run out of available numbers to allocate as device variety and number increase
Solution Approach 1:
The patent applies universality by allowing FQDNs to serve multiple purposes: devices with voice services use both MDN and FQDN, while devices without voice services use only FQDN for data communications. This multi-functional approach allows the system to accommodate diverse device types without being constrained by the limited MDN pool.
Solution Approach 2:
The patent introduces FQDN as an intermediary identifier that bridges the gap between traditional circuit-switched numbering (MDN/MSISDN) and packet-based data communications. The FQDN acts as a mediator that enables devices to be addressed in data communications without requiring allocation of scarce MDN resources.
2Adaptability or versatility
If FQDNs are used to register devices without MDNs, then more devices can be accommodated on the network, but a new registration mechanism and address allocation system must be implemented
Solution Approach 1:
The patent merges the existing MDN-based identification system with the FQDN-based identification system into a unified framework. Devices can be registered with both types of identifiers, and the system intelligently routes communications based on the device configuration, thereby supporting device diversity without requiring completely separate systems.
Solution Approach 2:
The patent implements a dynamic registration system where devices can be configured to use MDN, FQDN, or both identifiers depending on their service requirements. The network dynamically selects the appropriate identification method based on the device type and service subscription, allowing flexibility without imposing unnecessary complexity on all devices.
3Productivity
If packet-based addresses are allocated using FQDNs, then devices without voice services can communicate efficiently, but ensuring secure and accurate address allocation requires additional authentication and authorization mechanisms
Solution Approach 1:
The AAA server performs multiple functions including authentication, authorization, and FQDN-based address allocation within a single unified system. This multi-functional approach consolidates security mechanisms rather than adding separate layers, thereby supporting efficient data communications without proportionally increasing system complexity.
Data Source
AI summary
A mobile communication device registers for data communication through a mobile communication network with a packet-based network. The device may or may not have a mobile device number, and registers using a fully-qualified-domain-name (FQDN) uniquely identifying the device in a domain-name-system (DNS) of the packet-based network. A packet-data-network gateway assigns a packet-based address for the device, and generates a request for registering the address with the FQDN in a DNS server. Alternatively, the device generates the packet-based address based on a received portion of the address, retrieves the FQDN from an identity module, and sends a DNS-Update message to the DNS server including the address and FQDN. Again alternatively, a DNS server receives an encrypted DNS update message including a FQDN and a packet-based address, and decrypts the message prior to registering the address and FQDN in a DNS database.