Network Element Last Hop Device Address Determination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In agile networks, particularly those using Cable Hybrid Fiber Coax, repeatedly discovering the last hop device address for client devices is inefficient, especially in environments like VoIP applications where quality of service (QoS) needs to be managed for each call, as existing methods require sending addressing packets to each client device.
Innovation Solution
A method and system that determine last hop device addresses without sending addressing requests to each client device by using a database to store and manage client device addresses, including a time-to-live (TTL) value for viability, and using a client device address mask to indicate a range of addresses, allowing for efficient retrieval of last hop device addresses without repeated inquiries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If addressing packets are sent to each client device to discover last hop device addresses, then accurate last hop device address information is obtained, but network bandwidth is consumed and discovery time is increased
Solution Approach 1:
The system performs preliminary action by having client devices send their own addressing packets to the network element, which pre-establishes the mapping between client addresses and last hop device addresses in the database before actual communication needs occur. This preliminary discovery phase eliminates the need for repeated address requests during subsequent operations.
Solution Approach 2:
The system creates a copy of the address mapping information by having client devices transmit their addressing packets containing their own address information to the network element. The network element stores this copied information in a database, creating a reference copy that can be queried without sending new packets to client devices for each query.
2Reliability
If addressing packets are sent to each client device for repeated QoS management, then current QoS information is obtained, but network bandwidth is consumed and operational efficiency is reduced
Solution Approach 1:
The system performs preliminary action by establishing the address mapping database during an initial phase where client devices transmit their addressing packets. Once this database is populated, the system can answer repeated QoS management queries by simply looking up stored information rather than sending new addressing packets to each client device, thereby maintaining reliability while significantly improving operational efficiency.
Solution Approach 2:
The system implements feedback by having client devices send addressing packets containing their own address information back to the network element. This feedback mechanism allows the network element to build and maintain an accurate database of address mappings, enabling reliable QoS management without repeated bandwidth-consuming queries.
3Productivity
If a database is used to store last hop device addresses, then repeated address queries become efficient, but system complexity increases
Solution Approach 1:
The system implements self-service by having client devices automatically transmit their own addressing packet information to the network element without requiring manual configuration or complex setup procedures. The client devices essentially service themselves by providing their own address mapping information, which simplifies the overall system complexity despite the introduction of database storage functionality.
Data Source
AI summary
Method and system of determining addressing in a network environment where client devices are serviced by a number of last hop devices. The method and system including determining client device addresses serviced by the last hop devices as a function of last hop device addresses and client address masks associated with each last hop device.