R-PHY-MAP PRELIMINARY TIME SELECTION

By dynamically adjusting MAP lead times based on measured latency in R-PHY systems, the method improves transmission coordination and user throughput, addressing synchronization challenges in distributed R-PHY architectures.

DE112023001072T5Pending Publication Date: 2024-12-05ARRIS ENTERPRISES LLC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
DE112023001072
Authority / Receiving Office
DE · DE
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-02-24
Filing Date
2023-02-24
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

In R-PHY systems, the synchronization of clocks between the CCAP core and remote PHY devices is challenging due to variable latency in packet-switched networks, making it difficult to coordinate downstream and upstream transmissions effectively.

Method used

A method to determine MAP lead time by using data from MAP messages and comparing it with expected latency, adjusting the MAP lead time dynamically based on measured latency metrics, and employing multiple levels of MAP lead times to manage network conditions.

Benefits of technology

This approach enhances transmission coordination by minimizing data loss and improving user throughput while maintaining robustness against latency variations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Systems and methods for dynamically adjusting a MAP lead time for a MAP message sent from a CCAP kernel to an RPD, based on a comparison of at least one measured latency value with at least one threshold value.
Need to check novelty before this filing date? Find Prior Art

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 63 / 313,600, filed February 24, 2022, the contents of which are incorporated herein by reference in their entirety. BACKGROUND

[0002] The subject matter of this application relates generally to distributed access architectures of a hybrid CATV network and, more particularly, to (Remote Physical) R-PHY architectures that distribute the functions of the cable modem termination system in the network.

[0003] Although cable television (CATV) networks originally delivered content to subscribers over long distances exclusively via an RF transmission system, modern CATV transmission systems have replaced much of the RF transmission path with a more efficient optical network, creating a hybrid transmission system in which cable content terminates as RF signals over coaxial cable but is transmitted using optical signals for most of the distance between the content provider and the subscriber. Specifically, CATV networks include a headend at the content provider for receiving signals representing many content channels, multiplexing them, and distributing them along a fiber optic network to one or more nodes, each located near a group of subscribers.The node then demultiplexes the received optical signal and converts it into an RF signal so that it can be received by viewers. The system in a headend that provides the video channels to a subscriber typically includes numerous EdgeQAM units operating on different frequency bands, which are combined and multiplexed before being output to the ETC network.

[0004] In the past, the headend also included a separate cable modem termination system (CMTS), which was used to provide high-speed data services such as video, cable internet, Voice over Internet Protocol, and so on, to cable subscribers. Typically, a CMTS includes both Ethernet interfaces (or other more traditional high-speed data interfaces) and RF interfaces, allowing internet-bound traffic to be routed (or bridged) through the Ethernet interface, through the CMTS, and then onto the optical RF interfaces connected to the cable company's hybrid fiber-coax (HFC) system. Downstream traffic is delivered from the CMTS to a cable modem in a subscriber's residence, while upstream traffic is delivered from a cable modem in a subscriber's residence back to the CMTS.Many modern HFC CATV systems have combined the functionality of the CMTS with the video delivery system (EdgeQAM) in a single platform called the Converged Cable Access Platform (CCAP).

[0005] As networks grow larger and headends become increasingly overloaded with equipment, many content providers have recently adopted distributed architectures to distribute CMTS / CCAP functionality throughout the network. This distributed access architecture (DAA) keeps the cable data and video signals in digital format for as long as possible and extends the digital signals beyond the CMTS / CCAP deep into the network before converting them to RF. This is achieved by replacing the analog connections between the headend and the access network with a digital (Ethernet / PON) fiber connection.

[0006] One such distributed architecture is the distributed remote PHY access (R-PHY) access architecture, which offloads the physical layer (PHY) of a traditional CCAP to the network's fiber nodes. Therefore, while the core in the CCAP performs higher-level MAC layer processing, the R-PHY device in the node converts the downstream data sent by the core from digital to analog for radio frequency transmission and converts the upstream RF data sent by cable modems from analog to digital for optical transmission to the core.

[0007] However, once the functionality of the CMTS / CCAP is distributed across a MAC layer, e.g., a CCAP core, and various PHY devices throughout the network, synchronously coordinating transmissions between downstream cable modems and the CCAP core becomes significantly more difficult. To reduce interference, particularly with upstream transmissions, the CCAP sends downstream scheduling messages that inform each cable modem of its assigned transmission slots. These scheduling messages must be received well in advance of these transmission slots. Typically, a CCAP can reliably calculate the transmission delay between the time it sends such messages and the time a cable modem receives the messages, because conditions between the CCAP and the modem typically do not change rapidly. However, such rapid changes do exist in an R-PHY system.Therefore, improved systems and methods in an R-PHY architecture for determining the delay between sending and receiving a MAP message are desired. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] For a better understanding of the invention and to clarify how it can be implemented, reference is now made to the attached drawings, by way of example, in which: Fig. 1A and Fig. 1B show example R-PHY architectures in which a CCAP core is used to synchronously schedule transmissions to and from a plurality of cable modems. Fig. 2 shows an exemplary timing system for determining a MAP lead time delay Fig. Figure 3 shows an alternative timing system for determining a MAP lead time delay. DETAILED DESCRIPTION

[0009] For the purposes of the disclosure and claims, the following terms are defined to facilitate understanding of the described and claimed subject matter: Master clock: A clock that sends time information to a slave clock so that the clock synchronizes its time with that of the master clock. Slave clock: A clock that receives time information from a master clock to synchronize its time with that of the master clock. Grandmaster clock: a clock that only works as a master clock and is the time source for the packet network: Border clock: A clock operates as both a slave and a master clock, with one terminal in a slave state receiving time from a master clock and one or more terminals in a master state passing time information to slave clocks. Map messages: Messages sent by the CCAP that contain bandwidth allocation maps (MAPs). The MAP contains information that indicates when and for how long a cable modem can transmit. The CCAP must send the MAP messages in advance to prevent the cable modem from missing the transmission opportunity. MAP Lead Time: The amount of time the CCAP sends MAP messages before a cable modem is able to transmit. DOCSIS Tics: a unit of time expressed in units of mini-slots since the CMTS initialization time, where one mini-slot is 6.25 µs.

[0010] As mentioned earlier, in R-PHY systems, the clocks of the remote PHY devices (RPDs) and the CCAP core must be synchronized in both phase and frequency to properly schedule data transfers between network components. Fig. 1A shows an exemplary topology 10 used to synchronize devices in an R-PHY architecture. Topology 10 may include a CCAP core 12 synchronized with an RPD 13, which are interconnected via a plurality of network switches 14. The RPD 13 is in turn connected to one or more cable modems 15. Synchronization is achieved by a clock 16 in the core 12, which acts as a grandmaster clock and sends time information to a slave clock 17 in the RPD 13. Those skilled in the art will understand that, although Fig. 1, only one RPD 13 is connected to the core 12, many such RPDs may be connected to the core 12 simultaneously, with each RPD having a slave clock 17 that receives time information from the grandmaster clock 16 in the core. Those skilled in the art will also understand that an alternative timekeeping architecture could include a separate grandmaster clock.

[0011] Fig. Figure 1B shows an alternative topology 18 that differs from topology 10 in that a separate grandmaster clock 19 is used to synchronize both clock 16 in core 12 and clock 17 in RPD 13. In this architecture, clock 16 operates as a boundary clock, being a slave clock of grandmaster clock 19 but acting as the master clock of slave clock 17 in RPD 13.

[0012] As previously mentioned, the CCAP core 12 operates as the MAC layer in an R-PHY system and is responsible for generating and sending periodic downstream MAP packets, i.e., scheduling messages to the cable modems 15 to coordinate upstream transmissions between the network of cable modems 15. The cable modems 15, in turn, use the received MAP messages to determine when each can gain access to the upstream channel and transmit packets in the upstream direction. These MAP messages must be received well in advance of the start of the transmission windows contained in the MAP messages. Typically, the CMTS is configured with the maximum time it takes for a MAP message to propagate through the HFC network to a cable modem so that the CMTS can ensure that it transmits MAPS early enough to be usable upon arrival at the cable modem.In older systems not based on an R-PHY architecture, a CCAP could reliably calculate the maximum transmission delay between the sending of a MAP message and the time it is received by a cable modem because the conditions between the CCAP and a cable modem are largely known in advance.

[0013] However, in an R-PHY system, variable latency is added during the transmission of a MAP message because the MAC layer and the PHY layer of the CMTS are geographically separated by a packet-switched network, and this latency is often unpredictable by an operator. When the MAC layer prepares and sends a bandwidth MAP to the PHY layer, it must determine the additional delay in traversing the packet-switched network between the MAC and PHY layers when determining how early to send a bandwidth MAP packet. Knowing the delay from the MAC layer to the PHY layer is critical to system operation and performance.

[0014] Fig. Figure 2 shows a method for determining an appropriate MAP lead time in an R-PHY system. In this method, a CCAP core 20 has a master clock 21 used to synchronize its time with that of a slave clock 23 in an RPD 22, ensuring that both the core 20 and the RPD 22 have been synchronized to the same DOCIS tics since CMTS initialization. Those skilled in the art will understand that the master clock 21 may be a grandmaster clock or, in turn, a boundary clock serving as a slave clock to a separate grandmaster clock.

[0015] The CCAP core 28 may use a DEPI Latency Measurement (DLM) message exchange protocol that uses Downstream External PHY Interface (DEPI) messages to measure the latency between the CCAP core 20 and the RPD 22. Specifically, the CCAP core 20 sends a DLM request message 24 to the RPD 22. Before transmitting the DLM request message 24 in the packet-switched network, the CCAP core 20 writes a timestamp to the packet and records the transmission time of the packet by the CCAP core. The units for this timestamp are preferably DOCSIS tics. When the DLM request 24 arrives at the RPD 22, the RPD 22 records the time of packet reception. The RPD 22 then creates a DLM response message 26 that contains the timestamp from the CCAP core 22 and a timestamp indicating the time the packet was received at the RPD 22, both in units of DOCSIS tics.The RPD 22 then transmits this DLM response to the CCAP core, which then subtracts the CCAP core timestamp from the RPD timestamp to obtain a resulting value that indicates the one-way latency 28 from the CCAP core 20 to the RPD 22 in DOCSIS tics. This time can be converted to units of seconds. Once the CCAP core 20 has the latency measurement, it can make estimates of the other delays in the time it takes for the bandwidth MAP packet to travel from the CCAP core 20 to the cable modem and use these estimates, along with the latency measurement from the CCAP core 20 to the RPD 22, to determine the ideal time to transmit a bandwidth MAP so that it arrives at a cable modem within tolerance.

[0016] The Fig. The method shown in Figure 2 can have several disadvantages. First, DLM requires additional dataplane messages to achieve its destination. Second, DLM requires extensive changes to the CCAP core and RPD to format and process DLM messages and to handle message failure scenarios. Furthermore, the CCAP core must regularly track sent and pending messages. Third, a CCAP core can be connected to hundreds of RPDs. Regularly sending a DLM request and processing a DLM response from potentially hundreds of RPDs can overwhelm the processing capacity of the CCAP core.

[0017] Fig. Figure 3 shows an alternative system and method for determining an appropriate MAP lead time in an R-PHY system that, instead of exchanging separate messages for measuring packet delay from a CCAP core 30 to an RPD 32, uses data from the MAP messages themselves to estimate the delay and adjust a MAP lead time accordingly. MAP messages include a MAP allocation start time, which is the start time of the time slot for which the MAP allocates bandwidth. By examining the MAP allocation start time in a received MAP and comparing it with the time at which the RPD receives the MAP message, an RPD can determine the actually measured "HFC map lead time," which corresponds to the reception time relative to the MAP allocation start time. The RPD 32 can record, store, and report this data back to the CCAP core 30 if necessary. In determining its MAP lead time, i.e.The time the CCAP core calculates to send a MAP message before the window to which the MAP applies. The CCAP core has made certain assumptions about the latency between the MAC layer and the PHY layer and, from these assumptions, determined an expected HFC map lead time by which the RPD should have received the MAP. The MAC layer device can compare the measured HFC map lead time reported by the PHY layer device with its own expected HFC map lead time. Based on this comparison, the MAC layer can determine whether the assumed latency is correct and adjust the assumed latency until the expected HFC map lead time matches the measured HFC map lead time.

[0018] In particular, a system may include a CCAP core 30 with a master clock 31 connected to an RPD 32 with a slave clock 33 via a packet-switched network. The master clock 31 and the slave clock 33 ensure that both the core 30 and the RPD 32 are synchronized to the same DOCIS tics since CMTS initialization. The CCAP core 30 may construct a MAP message 34 that includes a start time for the window in which the MAP allocates bandwidth, recorded as start_alloc_time_mini_slots. The MAP message is transmitted to the RPD 32, which would normally forward the MAP message downstream to its RF port. Before doing so, however, the RPD 23 analyzes the MAP message to retrieve the start_alloc_time_mini_slots and records this value along with a timestamp for the receipt of the MAP message, pkt_arrival_time_docsis_tick.

[0019] The "start_alloc_time_mini_slots" value in the bandwidth MAP packet is expressed in units of mini-slots since the CMTS initialization time. The RPD 32 preferably converts this timestamp into units of DOCSIS ticks since the CMTS initialization. This can be done by considering the "mini-slot size" assigned to the MAP, which is configured by the CCAP core 30 on the RPD 32 during RPD initialization. The configured mini-slot size parameter is the size of a single mini-slot in DOCSIS ticks. Therefore, start_alloc_time_mini_slots in the bandwidth MAP packet is multiplied by the mini-slot size to obtain the resulting allocation start time in DOCSIS ticks, which is stored as map_alloc_start_time_docsis_tick. The RPD can also estimate the time from the recording of the pkt_arrival_time_docsis_tick to the time the bandwidth MAP packet is actually transmitted downstream over its RF port.This estimate is fairly constant for the RPD 32, as the processing time for bandwidth MAP packets does not vary much over time. This constant is also preferably expressed in units of DOCSIS ticks and can be denoted as est_processing_time_docsis_ticks.

[0020] A time expressed in units of DOCSIS ticks can be converted to seconds by multiplying it by the constant seconds_per_docsis_tick, which is equal to 1 / 10240000. Thus, the RPD can create a message 36 that includes the time in seconds that the RPD 32 actually received the MAP message 34 before the MAP start allocation time, using the following formula: hfc_map_lead_time_secs=(map_alloc_start_time_docsis_tick−(pkt_arrival_time_docsis_tick+est_processing_time_docs_tick))*seconds_per_docsis_tick.

[0021] Message 36 may then be sent to the CCAP core 30, which may use the measured MAP lead time to dynamically adjust its MAP lead time. In some embodiments, the CCAP core 30 may examine the recorded samples and determine whether the measured HFC map lead time is within a tolerance threshold for a portion of the RF equipment connected to the reporting RPD 32. If the HFC map lead time is out of tolerance, the CCAP core 30 may take a number of actions, including, but not limited to, (i) alerting the operator via logging or another user interface; (ii) adjusting its internal algorithms for how early to transmit bandwidth MAPs to the RPD to bring the HFC map lead time back into tolerance; and (iii) collecting and storing data for later analysis to identify and troubleshoot network issues.

[0022] In some embodiments, the RPD 32 may periodically examine a MAP packet and record the HFC map lead time for those packets. Each HFC map lead time is recorded as a sample in a database and stored on the RPD 32. In some implementations, the RPD 32 may store the most recent X samples for retrieval by the CCAP core 30 or a cable operator. The RPD 32 may provide storage for a number of samples because the network latency between the CCAP core 30 and the RPD 32 may vary over time based on routing, congestion, and other factors.

[0023] In many cases, it may not be desirable to frequently change the MAP pre-run time, especially based on only small changes in latency, as this requires processing resources. However, it is worth noting that some operators use networks that provide a normal path and a redundant path from the core to the RPD. The redundant path is typically longer and requires a longer MAP pre-run time, as a too-short MAP pre-run time can lead to data loss and modem deregistration. However, when using the shorter normal path, a shorter MAP pre-run time contributes to the performance improvement, as a shorter MAP pre-run time results in better user throughput and lower delays.

[0024] Novel systems and methods are disclosed that avoid excessive MAP lead time adjustments and maintain user throughput while avoiding data loss. In particular, the present specification discloses systems and methods that use a small number of discrete MAP lead times and switch between these values ​​based on a comparison of a measured latency metric with a threshold latency metric. In one exemplary embodiment, there may be only two levels of MAP lead times and a single threshold latency metric. Other embodiments may use more levels of MAP lead time values ​​and more associated threshold latency metrics.

[0025] Fig.4 shows an exemplary method according to an embodiment of the disclosure. At step 110, a latency metric is selected, and at step 112, a counter is set. At step 114, a low MAP lead time is acquired from a CCAP core, such as core 30, and sent in a downstream MAP message. At step 116, one or more latency metrics L mThe latency metric may be obtained in any suitable manner. For example, in one embodiment, the latency from a CCAP core to a remote device may be measured by the CCAP core using Downstream External PHY Interface (DEPI) latency measurements. In other embodiments, latency measurements may be calculated based on the exchange of Precision Timing Protocol (PTP) messages between a CCAP core and a remote device. These latency measurements may be calculated by the CCAP core or, alternatively, calculated by a remote device and sent to a CCAP core.

[0026] At step 118, the calculated latency metric(s) may be compared with one or more thresholds L sbe compared. If the latency metric is greater than the applicable threshold, a higher MAP time is selected at step 120. In a preferred embodiment, in an optional step 122, a counter is set from an initial value of zero to a value of "N". As explained below, this counter is used to ensure that the higher MAP value does not decrease until a threshold number of measurements show reduced latency. In this particular preferred embodiment, a single latency measurement exceeding a threshold may cause the method to use a higher MAP lead time, but this higher MAP time is not reduced until a number of consecutive measurements indicate that this is justified. This precaution increases the robustness of the method and minimizes the number of cases where a MAP message is not received in a timely manner.

[0027] After the counter is adjusted at step 122, a new latency measurement is obtained at step 116 and then compared again to a threshold at step 118. If the comparison shows that the measured latency is still above the threshold, the higher MAP time is reselected and the counter remains at the value "N." (Those skilled in the art will recognize that if more than two MAP times are used, requiring comparison to more than one threshold, the MAP time can be increased even further at step 120.)

[0028] Returning to step 118, if the measured latency is less than the applicable threshold, step 124 determines whether the counter is zero. If not, the counter is decremented by one, and the process returns to step 116 to perform a new latency measurement, and so on. The above operations continue until the counter is decremented to zero. At this point, the process returns to step 114, where the MAP time decreases to the lower value.

[0029] It should be understood that the invention is not limited to the particular embodiment described, and that variations may be made therein without departing from the scope of the invention as defined in the appended claims, as interpreted in accordance with the principles of applicable law, including the doctrine of equivalents or any other principle that expands the enforceable scope of a claim beyond its literal scope. Unless the context indicates otherwise, a reference in a claim to the number of instances of an element, whether a reference to one instance or more than one instance, requires at least the stated number of instances of the element, but is not intended to exclude from the scope of the claim a structure or method having more instances of that element than stated.The word "comprising" or a derivative thereof, when used in a claim, is used in a non-exclusive sense that is not intended to exclude the presence of other elements or steps in a claimed structure or method. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] US Application No. 63 / 313,600

[0001]

Claims

[1] Method comprising: Setting a plurality of predetermined MAP advance time values; Measuring a latency between a CCAP core and a remote device transmitting upstream; Selecting one of the plurality of predetermined MAP lead time values based on the measured latency; and Send a reservation MAP to the remote device with the identified MAP lead time. [2] The method of claim 1, including the step of comparing the measured latency with at least one threshold value. [3] The method of claim 2, wherein the number of thresholds is one less than the number of the plurality of predetermined MAP lead times. [4] The method of claim 1, including the step of modifying a counter value based on the comparison of the measured latency with the threshold value. [5] The method of claim 4, wherein the counter is either incremented or decremented based on whether or not the measured latency exceeds the threshold. [6] The method of claim 4, wherein the counter is decremented if the counter is greater than one and the measured latency is not greater than the threshold. [7] The method of claim 1, wherein the number of the plurality of predetermined MAP lead times is two. [8] The method of claim 1, wherein the number of the plurality of predetermined MAP lead times is greater than two. [9] The method of claim 1, wherein a higher predetermined MAP time is selected when a signal instance of a measured latency value exceeds the threshold. [10] The method of claim 9, wherein a lower predetermined MAP time is selected after determining that a plurality of consecutively measured latency values have not exceeded the threshold. [11] A CCAP core for communicating with a remote device in a communications network, the CCAP core configured to determine a latency associated with transmitting a MAP message to the remote device and to use the determined latency to select from a plurality of predetermined MAP lead times for communicating in the MAP message. [12] The CCAP core of claim 1, configured to compare the measured latency with at least one threshold. [13] The CCAP core of claim 12, wherein the number of thresholds is one less than the number of the plurality of predetermined MAP lead times. [14] The CCAP core of claim 12, configured to modify a counter value based on the comparison. [15] The CCAP core of claim 14, wherein the counter is either incremented or decremented based on whether or not the measured latency exceeds the threshold. [16] The CCAP core of claim 14, configured to decrement the counter if the counter is greater than one and the measured latency is not greater than the threshold. [17] The CCAP core of claim 11, wherein the number of the plurality of predetermined MAP lead times is two. [18] The CCAP core of claim 11, wherein the number of the plurality of predetermined MAP lead times is greater than two. [19] The CCAP core of claim 11, configured to select a higher-order predetermined MAP time when a signal instance of a measured latency value exceeds the threshold. [20] The CCAP core of claim 19, configured to select a lower predetermined MAP time after determining that a plurality of consecutively measured latency values have not exceeded the threshold.

Citation Information

Patent Citations

  • R-phy map advance time selection

    US63313600P0