PN Gateway Routing Table for Authentication Load Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Converged Personal Network Service (CPNS) systems face increased processing load on the Personal Network (PN) gateway and server due to the need for parsing and routing authentication requests for multiple Personal Network Entities (PNEs), which hampers efficient content download and service access in Consumer Electronics devices.
Innovation Solution
Implementing a method where the PN gateway uses a pre-generated PN routing table to map information about PNEs to their respective IDs, allowing it to forward authentication requests directly to the corresponding PNEs without parsing, thereby reducing the processing load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the PN gateway parses authentication request messages to extract PNE address information and performs routing operations, then the authentication process can be completed, but the processing load on the PN gateway increases significantly
Solution Approach 1:
The PN gateway performs preliminary routing operations during the PN configuration phase, building a routing table that maps PNE addresses to PN document positions. This preliminary action stores the routing information in advance, so that during authentication, the gateway can directly retrieve addresses from the pre-built routing table without parsing the PN document, thus reducing processing load while maintaining authentication reliability
Solution Approach 2:
The patent extracts the routing function from the authentication process. By separating the routing table generation (during configuration) from the authentication verification, the gateway only needs to perform simple table lookups during authentication rather than complex PN document parsing, thereby reducing the processing load while ensuring authentication completion
2Measurement precision
If the PN gateway compiles and parses the PN document at every authentication request, then accurate PNE address information can be obtained, but the time and computational resources are consumed
Solution Approach 1:
The routing table is generated in advance during the PN configuration phase, storing the mapping between PNE addresses and their positions in the PN document. This preliminary compilation eliminates the need for repeated parsing during authentication, reducing processing time while maintaining address information accuracy through the pre-stored routing data
Solution Approach 2:
Instead of repeatedly parsing the original PN document during authentication, the gateway uses a copied routing table structure that contains the essential address mapping information. This copying approach preserves the accuracy of address information while avoiding the time-consuming parsing operation at authentication time
Data Source
AI summary
A method and an apparatus are provided for configuring a Personal Network (PN). A connection request message is received from a Personal Network Entity (PNE) at the PN gateway. A registration request message for a PN, to which the PNE belongs, is transmitted from the PN gateway to a server located in a Wide Area Network (WAN). An authentication request message including ID information of the PN is received at the PN gateway from the server. The authentication request message is forwarded from the PN gateway to one or more PNEs mapped to the ID information of the PN, with reference to a PN routing table in which information about the one or more PNEs is mapped to the ID information of the PN. The one or more PNEs receive a service from the server through the PN gateway.