Abstract: In one embodiment, a method comprises receiving, by a network device, one or more advertisement messages comprising timing information describing a quality of a network clock that is originated by a master clock device at a root of a directed acyclic graph (DAG); the network device executing an objective function for the DAG providing an optimized loopless time topology for the network clock, synchronized to the master clock device, based on the timing information; and the network device attaching to a parent device in the DAG based on the objective function, for optimized generation of the network clock by the network device.

Abstract: In one embodiment, a method comprises receiving, by a network device, one or more advertisement messages comprising timing information describing a quality of a network clock that is originated by a master clock device at a root of a directed acyclic graph (DAG); the network device executing an objective function for the DAG providing an optimized loopless time topology for the network clock, synchronized to the master clock device, based on the timing information; and the network device attaching to a parent device in the DAG based on the objective function, for optimized generation of the network clock by the network device.

Abstract: An accurate non-Data Over Cable Service Interface Specification (non-DOCSIS) clock signal is generated at the downstream output of a DOCSIS network. In one example method, a downstream DOCSIS Timing Protocol (DTP) client in the DOCSIS network is frequency synchronized to an upstream DTP server in the DOCSIS network. DOCSIS timing information, along with one or more timing correction factors received at the DTP client, is used to time synchronize the DTP client to the DTP server. Based on the time and frequency synchronization between the DTP server and the DTP client, the clock signal is generated at the output of the DTP client in accordance with the non-DOCSIS timing protocol.

Abstract: An accurate non-Data Over Cable Service Interface Specification (non-DOCSIS) clock signal is generated at the downstream output of a DOCSIS network. In one example method, a downstream DOCSIS Timing Protocol (DTP) client in the DOCSIS network is frequency synchronized to an upstream DTP server in the DOCSIS network. DOCSIS timing information, along with one or more timing correction factors received at the DTP client, is used to time synchronize the DTP client to the DTP server. Based on the time and frequency synchronization between the DTP server and the DTP client, the clock signal is generated at the output of the DTP client in accordance with the non-DOCSIS timing protocol.

Abstract: An accurate non-Data Over Cable Service Interface Specification (non-DOCSIS) clock signal is generated at the downstream output of a DOCSIS network. In one example method, a downstream DOCSIS Timing Protocol (DTP) client in the DOCSIS network is frequency synchronized to an upstream DTP server in the DOCSIS network. DOCSIS timing information, along with one or more timing correction factors received at the DTP client, is used to time synchronize the DTP client to the DTP server. Based on the time and frequency synchronization between the DTP server and the DTP client, the clock signal is generated at the output of the DTP client in accordance with the non-DOCSIS timing protocol.

Abstract: A method is provided in one example embodiment and includes providing a time protocol assistant associated with a time-synchronized domain (TSD). The TSD includes a set of nodes that are synchronized to a same time source. The TSD has defined egress and ingress edge points where bidirectional measurements can be made and the egress and ingress edge points are coupled to the time protocol assistant. The method also includes synchronizing one or more packets flowing through a network that includes the TSD through the same time source. In more specific embodiments, the nodes are synchronized to the same time source via the network and the same time source is a grandmaster clock that synchronizes one or more transparent clocks. In yet other embodiments, the transparent clocks manipulate precision time protocol (PTP) packets sent by the grandmaster clock.

Abstract: An accurate non-Data Over Cable Service Interface Specification (non-DOCSIS) clock signal is generated at the downstream output of a DOCSIS network. In one example method, a downstream DOCSIS Timing Protocol (DTP) client in the DOCSIS network is frequency synchronized to an upstream DTP server in the DOCSIS network. DOCSIS timing information, along with one or more timing correction factors received at the DTP client, is used to time synchronize the DTP client to the DTP server. Based on the time and frequency synchronization between the DTP server and the DTP client, the clock signal is generated at the output of the DTP client in accordance with the non-DOCSIS timing protocol.

Abstract: A method is provided in one example embodiment and includes providing a time protocol assistant associated with a time-synchronized domain (TSD). The TSD includes a set of nodes that are synchronized to a same time source. The TSD has defined egress and ingress edge points where bidirectional measurements can be made and the egress and ingress edge points are coupled to the time protocol assistant. The method also includes synchronizing one or more packets flowing through a network that includes the TSD through the same time source. In more specific embodiments, the nodes are synchronized to the same time source via the network and the same time source is a grandmaster clock that synchronizes one or more transparent clocks. In yet other embodiments, the transparent clocks manipulate precision time protocol (PTP) packets sent by the grandmaster clock.

Abstract: Providing a multicast service includes maintaining multicast service information at an application server. The multicast service information describes a multicast service having an associated subscriber, and the multicast service is operable to deliver multicast content from a multicast source. A cell supporting a user device associated with the subscriber is determined, and creation of a bearer path for the multicast service is initiated. Delivery of the multicast content to the user device is enabled using the bearer path.

Abstract: Providing a multicast service includes maintaining multicast service information at an application server. The multicast service information describes a multicast service having an associated subscriber, and the multicast service is operable to deliver multicast content from a multicast source. A cell supporting a user device associated with the subscriber is determined, and creation of a bearer path for the multicast service is initiated. Delivery of the multicast content to the user device is enabled using the bearer path.