We focus on nine societal areas.
TNO cooperates with companies, the public sector and other organisations, to apply our knowledge and expertise with and for others.
We develop knowledge not for its own sake, but for practical application.
TNO offers you the chance to do groundbreaking work and help customers and society with innovative, practical and smart solutions.
Triple play is a key concept for Telco operators in their competition with cable network providers. Telco operators wishing to provide triple play over their xDSL enabled access infrastructures need to adapt to the service model of radio and television distribution in such a way that it suits their access infrastructure. Traditional radio and television distribution is based on a broadcast-and-select mechanism, where all channels are sent to all customers and each customer 'tunes' into the channel of choice. However, this model is not compatible with a DSL network, both in terms of capacity and topology.
This invention discloses a different approach, using IP based transport and IP-multicast and forwarding. The customer subscribes to the delivery tree of a particular channel before this channel is transported to said customer. Therefore the network operates in an 'on-demand delivery' mode. Various protocols are known to achieve this over so called Non Broadcast Multiple Access networks. Due to the inverse multiplexing methodology, these known protocols are not compliant with a High Speed Bundled Access network.
Due to the flexibility these systems and methods offer, they would be extremely useful to any company involved in managing network traffic or manufacturing network equipment.
The main problem is how to arrange the multicast subscription within the radio mesh network when the data flows to the subscriber are inverse multiplexed. The solution is to distribute the subscription process over all radio mesh network elements. In the accompanying figure, host 4, who wishes to subscribe to e.g. CNN, establishes a branch from the mesh network multicast source to itself by sending an "ICMP_Report" message to the IP multicast router. As in the case of HBA, all inverse multiplex elements receive all data for host 4. Due to the inverse multiplexing process there must be a branch from all mesh network elements to host 4. This means sending an "NMCP_Join" message to all mesh network elements.