Single URL File Transfer via NAPTR Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file transfer methods in Rich Communication Services (RCS) systems require generating multiple URLs for different file locations, leading to wastage of computing and network resources due to the need to configure URLs based on peering relationships and transfer methods.
Innovation Solution
Implementing file location records, specifically Name Authority Pointer (NAPTR) records, to enable a single URL for file transfer, regardless of peering relationships, allowing the terminating network provider to determine the file location and transfer method, thereby preserving resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple URLs are generated for different file locations based on peering relationships, then file transfer compatibility across different network providers is improved, but computing and network resources are wasted due to redundant URL configurations
Solution Approach 1:
The patent implements a universal file transfer mechanism where a single URL can be used regardless of peering relationships or transfer methods. The terminating network provider's system automatically determines the appropriate file location and transfer method (direct NNI or indirect via hub) based on this single URL, eliminating the need for multiple specialized URLs for different scenarios.
Solution Approach 2:
The patent introduces an intermediary system at the terminating network provider that acts as a mediator between the single URL and the actual file transfer. This intermediary automatically resolves the file location by querying the originating network provider and determines the optimal transfer method, thereby eliminating the need for the originating provider to configure multiple URLs for different peering relationships.
2Reliability
If multiple URL configurations are implemented for different transfer methods, then file transfer reliability across peering relationships is improved, but device complexity increases due to multiple configuration requirements
Solution Approach 1:
The patent extracts the complexity of determining file location and transfer method from the originating network provider's URL configuration and relocates it to the terminating network provider's system. The originating provider only needs to provide a single URL, while the terminating provider's system handles the complex logic of resolving the actual file location and selecting the transfer method based on peering relationships.
Solution Approach 2:
The system implements self-service automation where the terminating network provider's system automatically queries the originating network provider to determine the actual file location and automatically selects the appropriate transfer method (direct NNI or indirect via hub). This eliminates manual configuration of multiple URLs and reduces complexity while maintaining reliability.
Data Source
AI summary
In some implementations, a device may receive file location information identifying a file to be transferred to a user device associated with the first network provider. The file location information identifies a domain name associated with a second network provider. The device may provide, based on the file location information, a first request to obtain one or more first records. The one or more first records identify a first supplemental content device. The device may provide, based on the one or more first records, a second request to obtain one or more second records. The one or more second records identify a second supplemental content device. The device may obtain, based on the one or more second records, the file from the second supplemental content device, and provide the file to the user device.