Time Warner Cable Enterprises LLC

Time Warner Cable Inc.

Wesley E George, Iv

Robert Seastrom

Chris Roosenraad

David Trout

Jeffrey A Aitken

A mobile communication device initiates display of a point of interest as being located at particular coordinates on a map. In response to receiving an input command from a user of the mobile communication device indicating that the particular location of the point of interest as specified by the map is incorrect, the mobile communication device forwards a communication (specifying a location of the mobile communication device and an identity of the point of interest) over a network to a map management resource. Based on feedback from the mobile communication device, the map management resource updates map data an actual location of the point of interest as opposed to an incorrect location as specified by the particular coordinates on the map. Subsequent distribution of the updated map information from the map management resource specifies the proper coordinates of the point of interest in the geographical region.

Map information management and correction of geodata

A first request, to access a web site associated with a domain name, is obtained at a gateway router interposed between a local area network and an internet service provider's infrastructure, from a host on the local area network. The gateway router has Domain Name Service (DNS) resolver capability. The first request is received while the gateway router has upstream connectivity to the internet service provider's infrastructure via IPv6 but not via IPv4. Further steps include sending, from the gateway router, the first request; obtaining, at the gateway router, an indication that an IPv4 address will imminently be required for the gateway router; and, responsive to obtaining the indication, sending, from the gateway router, into the internet service provider's infrastructure, a second request, for an IPv4 address for the gateway router.

Use of DNS information as trigger for dynamic IPV4 address allocation

A method for providing seamless redundancy in an output data stream includes the steps of: receiving a first data stream originating from a first location, the first data stream being conveyed over a first network path; receiving at least a second data stream originating from a second location that is geographically distinct from the first location, the second data stream comprising nominally identical content relative to the first data stream, the second data stream being conveyed over a second network path that is topologically distinct from the first network path; and combining first data segments from the first data stream and second data segments from the second data stream to generate a single, uninterrupted output data stream having a reduced likelihood of overlapping, missing and/or corrupt data segments.

System and method for seamless switching between data streams

A file is multicast from an error-correcting multicast apparatus to a plurality of endpoints forming a first multicast group, over a network segmented into at least second and third multicast groups. The second and third multicast groups are subsets of the first multicast group. Given ones of the endpoints are assigned to the second and third multicast groups based on likelihood of experiencing similar errors. At the error-correcting multicast apparatus, over the network, a retransmission request is obtained from a first one of the endpoints, based on at least one of loss and corruption of a portion of the file during the multicasting of the file to the first one of the endpoints. The portion of the file is retransmitted, via multicasting, over the network, to one of the second and third multicast groups.

Apparatus, method and computer program product for error correction in variably reliable and/or hierarchical networks

A system and method for resolving a DNS request using metadata. An intelligent name server receives a request to resolve a domain name via a network. The intelligent name server acquires at least one metadata element about the source of the request. The domain name request is transformed into a CNAME request that includes the at least one metadata element and the domain name to be resolved. The CNAME request is sent to a metadata aware DNS server for resolution. The metadata aware DNS server maps the domain name to one or more network addresses stored in a look-up table. The included metadata is used to select a 'best' host address to include in a response.

System and method for resolving a DNS request using metadata

A system and method for routing multicast packets. A multicast packet is received at an inbound interface on a switch/router. S,G data are obtained from the packet and used to search an OIL table. If the S,G data are found in the OIL table, the packet is forwarded on an outbound interface associated with the S,G data. If the S,G data are not found in the OIL table, the multicast routing table is consulted to obtain a longest match for the packet, and the packet is forwarded on the interface(s) which correspond to the longest match route. The multicast routing table may include a single entry, such that all packets that do not match an entry in the OIL are forwarded on the same outbound interface. The multicast routing table may include multiple entries with different covered ranges of (S,G).

Growing community of inventors

Manassas, VA, United States of America

Wesley E George, Iv