US20150295684A1 - Determining and managing upstream profiles in docsis 3.1 network environments - Google Patents
Determining and managing upstream profiles in docsis 3.1 network environments Download PDFInfo
- Publication number
- US20150295684A1 US20150295684A1 US14/685,422 US201514685422A US2015295684A1 US 20150295684 A1 US20150295684 A1 US 20150295684A1 US 201514685422 A US201514685422 A US 201514685422A US 2015295684 A1 US2015295684 A1 US 2015295684A1
- Authority
- US
- United States
- Prior art keywords
- probing
- channel
- snr
- determining
- group delay
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B3/00—Line transmission systems
- H04B3/54—Systems for transmission via power distribution lines
- H04B3/542—Systems for transmission via power distribution lines the information being in digital form
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
- H04J3/0658—Clock or time synchronisation among packet nodes
- H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
- H04J3/0667—Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
- H04J3/0658—Clock or time synchronisation among packet nodes
- H04J3/0673—Clock or time synchronisation among packet nodes using intermediate nodes, e.g. modification of a received timestamp before further transmission to the next packet node, e.g. including internal delay time or residence time into the packet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2801—Broadband local area networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2697—Multicarrier modulation systems in combination with other modulation techniques
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/32—Carrier systems characterised by combinations of two or more of the types covered by groups H04L27/02, H04L27/10, H04L27/18 or H04L27/26
- H04L27/34—Amplitude- and phase-modulated carrier systems, e.g. quadrature-amplitude modulated carrier systems
- H04L27/3405—Modifications of the signal space to increase the efficiency of transmission, e.g. reduction of the bit error rate, bandwidth, or average power
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/32—Carrier systems characterised by combinations of two or more of the types covered by groups H04L27/02, H04L27/10, H04L27/18 or H04L27/26
- H04L27/34—Amplitude- and phase-modulated carrier systems, e.g. quadrature-amplitude modulated carrier systems
- H04L27/345—Modifications of the signal space to allow the transmission of additional information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/006—Quality of the received signal, e.g. BER, SNR, water filling
Definitions
- This disclosure relates in general to the field of communications and, more particularly, to determining and managing upstream profiles in Data Over Cable Service Interface Specification (DOCSIS) 3.1 network environments.
- DOCSIS Data Over Cable Service Interface Specification
- DOCSIS is an international telecommunications standard that has evolved to permit addition of high-bandwidth data transfer to an existing cable TV (CATV) system utilizing Quadrature Amplitude Modulation (QAM) and/or Quadrature phase-shift keying (QPSK) Radio Frequency (RF) modulation. It is employed by many cable television operators to provide Internet access over their existing hybrid fiber-coaxial (HFC) infrastructure.
- CATV cable TV
- QAM Quadrature Amplitude Modulation
- QPSK Quadrature phase-shift keying
- RF Radio Frequency
- the DOCSIS system is a Point-to-Multipoint communications system, the corresponding standards defining Media Access Control (MAC)/physical layer (PHY) standards associated with providing high speed data over a hybrid fiber coaxial (HFC) network and is not naturally applicable for digital fiber.
- MAC Media Access Control
- PHY physical layer
- IP Internet Protocol
- FIG. 1 is a simplified block diagram illustrating a communication system for determining and managing upstream profiles in DOCSIS 3.1 network environments
- FIG. 2 is a simplified block diagram illustrating example details of embodiments of the communication system
- FIG. 3 is a simplified block diagram illustrating other example details of embodiments of the communication system
- FIG. 4 is a simplified block diagram illustrating yet other example details of embodiments of the communication system
- FIG. 5 is a simplified block diagram illustrating yet other example details of embodiments of the communication system.
- FIG. 6 is a simplified flow diagram illustrating example operations that may be associated with an embodiment of the communication system.
- An example method for determining and managing upstream profiles in Data Over Cable Service Interface Specification (DOCSIS) 3.1 network environments includes determining, at a Converged Cable Access Platform (CCAP) core, channel conditions independent of any channel effect over a hybrid fiber coaxial (HFC) network between a remote physical layer (R-PHY) entity coupled to the CCAP core and a cable modem (CM) in the DOCSIS 3.1 network environment, and assigning an upstream profile to the CM based on the channel conditions.
- the channel conditions include signal to noise ratio (SNR), modulation error ratio (MER) or group delay.
- assigning the upstream profile includes determining a quadrature amplitude modulation (QAM) order based on the SNR or MER, and determining a pilot pattern based on the group delay, the combination of the QAM order and the pilot pattern identifying the upstream profile.
- QAM quadrature amplitude modulation
- the term “profile” specifies modulation order and pilot patterns for active data sub-carriers of an Orthogonal Frequency-Division Multiplex Access (OFDMA) channel; in other words, a combination of a particular modulation order and pilot pattern indicates a unique profile.
- OFDMA Orthogonal Frequency-Division Multiplex Access
- an upstream direction indicates a communication path from CMs to the CCAP core; a downstream direction indicates a communication path from the CCAP core to the CMs.
- MER is digital complex baseband SNR and the terms “SNR” and “MER” are used interchangeably herein, unless specifically differentiated.
- FIG. 1 is a simplified block diagram illustrating a communication system 10 for determining and managing upstream profiles in DOCSIS 3.1 network environments in accordance with one example embodiment.
- FIG. 1 illustrates a network 11 (indicated generally by an arrow) facilitating communication between a Converged Cable Access Platform (CCAP) core 12 and an R-PHY entity 14 over a converged interconnect network (CIN) 16 , and between R-PHY entity 14 and multiple cable modems (CMs) 18 ( 1 )- 18 ( 3 ) over a hybrid fiber coaxial (HFC) network 20 .
- CCAP Converged Cable Access Platform
- CIN converged interconnect network
- CMs cable modems
- HFC hybrid fiber coaxial
- network 11 can include any number of CCAP cores, each connected to a plurality of R-PHY entities, each of which is connected to multiple CMs within the broad scope of the embodiments.
- CCAP core 12 and R-PHY entity 14 together comprise a CCAP, which is typically a combination of a DOCSIS cable modem termination system (CMTS) and an edge QAM (EQAM).
- CCAP core 12 and R-PHY entity 14 can communicate remotely in some embodiments over CIN 16 that can span across different geographic locations; in other embodiments, CIN 16 may comprise a set of interfaces within the same chassis.
- OFDMA Orthogonal frequency division multiplexing
- OFDMA is a method of multi-carrier digital communication where wide-band information data is distributed across many narrow-band subcarriers in the frequency domain.
- OFDMA is a method of multi-user digital communications, wherein each user utilizes an allotment of the available sub-carriers and time intervals for their individual communication. Because the fundamental operation and advantages of OFDMA systems is similar to that of OFDM systems in a multipath wireless propagation environment, the terms OFDM and OFDMA are used here interchangeably.
- OFDM divides the upstream spectrum into multiple equally spaced subcarriers.
- the subcarrier spacing is 25 kHz or 50 kHz, corresponding to 40 us or 20 us long symbol duration, respectively.
- the subcarriers are divided into multiple equally sized clusters called mini-slots.
- Each mini-slot consists of Q subcarriers, where Q equals to 16 or 8 corresponding to 25 kHz or 50 kHz subcarrier spacing, respectively.
- a QAM order and a pilot pattern (e.g., reference signal with information known apriori to the receiver; pilot patterns have known, fixed characteristics when they are transmitted) are assigned to each mini-slot.
- OFDM orthogonal frequency-division multiplexing
- the QAM order and pilot pattern can change from one mini-slot to another.
- DOCSIS 3.1 supports up to eleven (11) levels of QAM orders (Quadrature Phase Shift Keying (QPSK)-4KQAM, squared and non-squared (the notation KQAM is used to indicate a modulation scheme encoding log 2 (K) bits per symbol, thereby providing K symbols)) and 8 different pilot patterns.
- QPSK Quadrature Phase Shift Keying
- KQAM is used to indicate a modulation scheme encoding log 2 (K) bits per symbol, thereby providing K symbols
- DOCSIS 3.1 specifications allow for profiles 22 to be assigned to each CM 18 allowing upstream resource allocations and dictating how upstream symbols are demodulated at CCAP core 12 .
- profiles 22 ( 1 ) and 22 ( 2 ) are assigned to CM 18 ( 1 );
- profiles 22 ( 3 ) and 22 ( 4 ) are assigned to CM 18 ( 2 );
- profiles 22 ( 5 ) and 22 ( 6 ) are assigned to CM 18 ( 3 ); and so on.
- each of profiles 22 specifies the QAM order for data symbols and pilot pattern of a mini-slot of an upstream OFDMA channel.
- Each OFDM channel has its own unique set of profiles 22 (e.g., profiles 22 describe subcarriers at a particular frequency, and each OFDM channel occupies different frequencies.) From a packet forwarding perspective, each profile 22 creates a unique path through an OFDM channel from R-PHY entity 14 to CMs 18 .
- the term ‘profile’ can be considered a PHY level description for the packet forwarding mechanism; the term ‘path’ can be considered a MAC level description for the packet forwarding mechanism.
- Profiles 22 can allow for effective optimization of the transmission path to or from CMs 18 that can tolerate a higher modulation.
- the aggregate capacity of the OFDM channel depends upon the configuration of each of profiles 22 characterizing the OFDM channel and the relative usage of each profile 22 because all profiles 22 (for each OFDM channel) in combination share the aggregate channel capacity (for each OFDM channel).
- Each profile 22 profile can be characterized (e.g., indicated, defined, specified, parameterized, etc.) by the QAM orders and pilot patterns on the mini-slots over the spectrum.
- each CM 18 should support up to two profiles 22 for upstream data traffic.
- profile 22 can be synonymous with data Interval Usage Codes (IUCs); their allocations are signaled by MAP messages.
- IUCs Interval Usage Codes
- CCAP core 12 determines the allocation of profiles 22 to each OFDM channel, and to each CM 18 .
- the profile management involves two distinct tasks: (1) determine the OFDM profile parameters (e.g., QAM order and pilot pattern); (2) assign profiles 22 to groups of CMs 18 from whom CCAP core 12 receives upstream signals with similar fidelity, for example, based on the quality of their respective communication links with R-PHY entity 14 over HFC network 20 .
- CCAP core 12 attempts to make a profile assignment to CM 18 ( 1 ).
- CM 18 ( 1 ) is eligible to be assigned two profiles, and CCAP core 12 determines the QAM orders and pilot patterns that characterize two profiles 22 ( 1 ) and 22 ( 2 ), for example, based on the bandwidth availability and other communication link conditions between R-PHY entity 14 and CM 18 ( 1 ).
- a probing signal scheduler 24 in CCAP core 12 may schedule a wide band probing signal and allocate two probing opportunities within the same probe frame in a probing request 26 for CM 18 ( 1 ), which may be forwarded to CM 18 ( 1 ) over HFC network 20 .
- CM 18 ( 1 ) may respond with a probing signal 28 .
- a segmentation module 30 in CCAP core 12 divides the spectrum of probing signal 28 (also referred to herein as the channel response) into multiple segments.
- a modulation error ratio (MER)/ signal to noise ratio (SNR) module 32 determines a ‘true’ MER/SNR of probing signal 28 that is independent of the effect of the OFDM channel (e.g., each channel may affect SNR/MER differently, for example, through group delay variation, amplitude tilt or ripple, and micro-reflections) for each segment.
- MER refers to a ratio of average symbol power to average error power (e.g., the higher the MER, the cleaner (less distorted) the received signal).
- the segmentation is evaluated and adjusted substantially continuously with each probing opportunity. In some embodiments, the segmentation is evaluated by examining how quickly the QAM order and pilot pattern vary from one segment to another, and re-adjusted with each probing opportunity if necessary. Each segment includes multiple mini-slots that have the same QAM order and pilot pattern. In some embodiments, the segments are not equal in size. In other embodiments, the segments may be substantially equal in size.
- the QAM order can be determined by the inherent spectrum efficiency or channel capacity of the mini-slot, which may be determined from signal MER/SNR measurements at the input of a low-density parity-check (LDPC) decoder in MER/SNR module 32 after channel estimation.
- a group delay calculator 34 may compute the average group delay of each segment, which is correlated with the channel variation.
- Group delay variation refers to a difference in propagation time between one frequency and another (e.g., some frequency components of the signal may arrive at the output before others, causing distortion of the received signal).
- the group delay is estimated through a phase ramp in frequency domain, which can be an effective scheme with low complexity.
- Group delay calculator 34 may determine the QAM order for each segment by mapping the computed MER/SNR to QAM order using a MER/SNR-QAM order Look-Up-Table (LUT) 36 .
- LUT Look-Up-Table
- MER/SNR-QAM order LUT 36 may be preconfigured in CCAP core 12 using simulations, calibrations, heuristic techniques, or other mechanisms.
- a pilot pattern module 38 in CCAP core 12 may determine how quickly the channel gain varies within the mini-slot (8 or 16 subcarriers, total 400 kHz BW), for example, to select a pilot pattern with proper pilot density. Pilot pattern module 38 may determine the profile granularity over the spectrum (e.g., by grouping multiple adjacent mini-slots together and assign the same QAM order and pilot pattern to reduce computations and upstream channel allocation complexity). In some embodiments, pilot pattern module 38 may determine the pilot pattern for each segment by mapping the computed group delay to pilot patterns using a group delay-pilot pattern LUT 40 . In various embodiments, group delay-pilot pattern LUT 40 may be preconfigured in CCAP core 12 using simulations, calibrations, heuristic techniques, or other mechanisms.
- Pilot pattern module 38 may generate multiple profiles from a base profile by adding margins.
- a profile updater 42 in CCAP core 12 may also update profiles 22 to cope with varying channels and cable modem conditions.
- Assigned profiles 22 ( 1 ) and 22 ( 2 ) may be mapped to CM 18 ( 1 ) in a CM-profile table 44 .
- a processor 46 and a memory element 48 may facilitate the operations described herein.
- segmentation can simplify CMTS algorithms to evaluate upstream probing signal 28 , for example, by not requiring processor intensive per sub-carrier computations.
- the operations described herein can allow dynamically adjusting a size of profiles 22 , and reducing computation and complexity of upstream schedulers.
- various modules may be implemented (e.g., execute on) hardware accelerators using appropriate hardware configured with suitable software.
- the network topology can include any number of cable modems, customer premises equipment, servers, switches (including distributed virtual switches), routers, and other nodes inter-connected to form a large and complex network.
- Network 11 represents a series of points or nodes of interconnected communication paths for receiving and transmitting packets and/or frames of information that are delivered to communication system 10 .
- a node may be any electronic device, computer, printer, hard disk drive, client, server, peer, service, application, or other object capable of sending, receiving, or forwarding information over communications channels in a network.
- Elements of FIG. 1 may be coupled to one another through one or more interfaces employing any suitable connection (wired or wireless), which provides a viable pathway for electronic communications. Additionally, any one or more of these elements may be combined or removed from the architecture based on particular configuration needs.
- Network 11 offers a communicative interface between cable modem network components, and may include any local area network (LAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Internet, Extranet, wide area network (WAN), virtual private network (VPN), or any other appropriate architecture or system that facilitates communications in a network environment.
- Network 11 may implement any suitable communication protocol for transmitting and receiving data packets within communication system 10 .
- the architecture of the present disclosure may include a configuration capable of TCP/IP, TDMA, and/or other communications for the electronic transmission or reception information in a network.
- the architecture of the present disclosure may also operate in conjunction with any suitable protocol, where appropriate and based on particular needs.
- gateways, routers, switches, and any other suitable nodes may be used to facilitate electronic communication between various nodes in the network.
- a communication link may represent any electronic link supporting a network environment such as, for example, cable, Ethernet, wireless technologies (e.g., IEEE 802.11x), ATM, fiber optics, etc. or any suitable combination thereof.
- communication links may represent a remote connection through any appropriate medium (e.g., digital subscriber lines (DSL), telephone lines, T1 lines, T3 lines, wireless, satellite, fiber optics, cable, Ethernet, etc. or any combination thereof) and/or through any additional networks such as a wide area networks (e.g., the Internet).
- DSL digital subscriber lines
- T1 lines T1 lines
- T3 lines wireless, satellite, fiber optics, cable, Ethernet, etc. or any combination thereof
- any additional networks such as a wide area networks (e.g., the Internet).
- CCAP core 12 may comprise a hardware appliance with appropriate ports, processors, memory elements, interfaces, and other electrical and electronic components that facilitate the functions described herein.
- the various modules in CCAP core 12 may comprise hardware devices or software applications or combination thereof executing within CCAP core 12 to perform the operations described herein.
- the various modules in CCAP core 12 may comprise hardware devices or software applications executing outside CCAP core 12 , for example, in a separate appliance, server, or other network element and coupled (e.g., connected to, in communication with, etc.) to CCAP core 12 in network 11 .
- R-PHY entity 14 may comprise suitable hardware components and interfaces for facilitating the operations described herein.
- R-PHY entity 14 may be embedded in or be part of another hardware component, such as a broadband processing engine (comprising a motherboard, microprocessors and other hardware components).
- R-PHY entity 14 comprises downstream and upstream PHY, deployed in a Coaxial Media Converter (CMC) that supports RF functions at the PHY layer.
- CMC Coaxial Media Converter
- CCAP core 12 and R-PHY entity 14 may be located in the same chassis; in other embodiments, CCAP core 12 and R-PHY entity 14 may be located in different physical locations, remote from each other and coupled over a Layer 2 or Layer 3 network with various other network elements, such as switches and routers intervening there between.
- FIG. 2 is a simplified block diagram illustrating example details associated with segmentation according to an embodiment of communication system 10 .
- the frequency spectrum of probing signal 28 may be segmented in N segments 50 ( 1 )- 50 (N). In some embodiments, segmentation is performed at mini-slot boundaries.
- the spectrum may be segmented to account for upstream channel variation. For example, portions of the spectrum with large channel variations may be segmented into small size segments (e.g., fine segmentation); portions of the spectrum with small channel variations may be segmented into large size segments (e.g., coarse segmentation).
- channel variation is estimated from probing signal 28 detected in a current probing opportunity; in other embodiments, channel variation may be estimated from probing signal 28 in current and previous probing opportunities. Segmentation may be continuously evaluated and adjusted based on the latest channel information.
- the spectrum may be segmented such that the SNR and channel response remain relatively constant within each segment.
- the SNR and group delay may be computed for each segment separately. Variations of the SNR and group delay between segments may also be determined. If the variation is greater than a preconfigured threshold (e.g., 30%), size of the segments where rapid changes occur may be reduced correspondingly (e.g., by splitting one segment into two). If the variation is less than another preconfigured threshold (e.g., 5%) the segment size may be increased by combining adjacent segments. The segmentation may be re-evaluated and adjusted substantially continuously with each probing opportunity.
- a preconfigured threshold e.g. 30%
- size of the segments where rapid changes occur may be reduced correspondingly (e.g., by splitting one segment into two).
- another preconfigured threshold e.g., 5%
- the segmentation may be re-evaluated and adjusted substantially continuously with each probing opportunity.
- segmentation is applicable to active subcarriers, and not to ‘excluded subcarriers’ 52 .
- excluded subcarriers are forced to zero-valued modulation at the transmitter.
- Subcarriers are excluded to prevent interference to other transmissions that occupy the same spectrum, for example, to accommodate legacy channels.
- Subcarriers are also excluded outside of the active OFDM bandwidth. Excluded subcarriers are common to all profiles 22 . The non-excluded subcarriers are referred to as active subcarriers.
- FIG. 3 is a simplified block diagram illustrating example details of a probe frame 54 according to an embodiment of communication system 10 .
- Frequency is graphed along a vertical axis
- time (or symbols) is graphed along a horizontal axis.
- probing signal scheduler 24 schedules two probing opportunities 56 ( 1 ) and 56 ( 2 ) in a single probe frame 54 .
- probing signal 28 may comprise a pseudo-random binary sequence (PRBS) modulated with binary phase-shift keying (BPSK).
- Probing signal 28 may be by de-randomized by removing the known PRBS sequence from probing signal 28 . The channel effect may be removed to compute the ‘true’ SNR/MER.
- the de-randomized probing signals for a first opportunity and a second opportunity (P 1 (i) and P 2 (i) respectively) for the i th active subcarrier may be obtained by multiplying probing signal 28 with the known probing PRBS as follows:
- S 1 (i), S 2 (i) are, respectively, probing signal 28 at the first opportunity and the second opportunity;
- PRBS(i) is the known PRBS;
- index i runs over active subcarriers in the segment.
- the SNR/MER can be computed from the following equation:
- Ns is the total number of active subcarriers in the segment.
- the formula utilizes the fact that probing signal is modulated with BPSK (e.g., reference point on a QAM constellation is 1; in a general sense, a constellation represents the possible symbols (e.g., waveform such as a pulse or tone representing a certain number of bits) that may be selected by a given modulation scheme).
- the SNR computed as described herein may include no channel effect, and may be a true representative for the MER/SNR at the input of LDPC decoder. Thereafter, the QAM order for the segment can be obtained through MER/SNR-QAM order LUT 36 .
- FIG. 4 is a simplified diagram illustrating an example MER/SNR-QAM order LUT 36 according to an embodiment of communication system 10 .
- MER/SNR-QAM order LUT 36 may be generated from simulations, testing, calibration, heuristics, or other suitable mechanisms within the broad scope of the embodiments.
- MER/SNR-QAM order LUT 36 represents an association between the QAM constellation (indicative of the QAM order) and SNR (or MER). If the SNR/MER is known, a lookup of MER/SNR-QAM order LUT 36 can indicate the corresponding QAM order to be used for profile 22 .
- FIG. 5 is a simplified diagram illustrating an example group delay-pilot pattern LUT 40 according to an embodiment of communication system 10 .
- Group delay may be associated with a pilot pattern in group delay-pilot pattern LUT 40 based on simulations, testing, calibration, heuristics, or other suitable mechanisms within the broad scope of the embodiments.
- the group delay (e.g., time offset) can be a good indication of channel variation, which in turn can determine a suitable pilot pattern density (e.g., number of pilot patterns in a signal of known duration).
- the group delay is estimated from a phase ramp in each segment. For example, in each segment, a dot product of the conjugate of probing signal 28 on the i th subcarrier with probing signal 28 on the next ((i+1) th ) subcarrier may be obtained:
- P(i) and P(i+1) are, respectively, probing signal 28 detected on i th and (i+1) th subcarriers in the segment being evaluated.
- the result bi may be summed over the subcarriers in the segment:
- the group delay g_t may be computed as follows:
- sc is a subcarrier space (e.g., 25 kHz or 50 kHz).
- the pilot pattern for the segment can be obtained according to group delay-pilot pattern LUT 40 .
- group delay-pilot pattern LUT 40 For example, if g_t is computed to be less than 10 times a preconfigured threshold value t0, a predetermined pattern 1 may be used in the 50 kHz subcarrier space, whereas pattern 5 may be used in the 25 kHz subcarrier space. If g_t is between 10 times t0 and 20 times t0, pattern 2 may be used in the 50 kHz subcarrier space, whereas pattern 6 may be used in the 25 kHz subcarrier space.
- the thresholds e.g., t0, 10*t0, 20*t0, etc.
- the thresholds can be changed to suit particular needs within the broad scope of the embodiments.
- CMs 18 can support up to two upstream profiles for data traffic (and additional profiles for downstream traffic).
- additional profiles can be generated from a base profile (e.g., determined as described herein) by adding margins. For example, assume that profile 22 ( 1 ) is designated for short and high priority messages, 3 dB margin can be added to obtain another QAM order from MER/SNR-QAM order LUT 36 and an additional level can be added to the group delay to obtain another pilot pattern from group delay—pilot pattern LUT 40 to generate another profile 22 ( 2 ).
- IUC Interval Usage Code
- CMs 18 profile information to CMs 18 is carried through an Interval Usage Code (IUC) in a downstream message from the CMTS to CMs 18 .
- IUCs In a general sense, tells IUCs indicate to each cable modem the type of modulation (and other characteristics) to use depending upon the information the cable modems are transmitting to the CMTS.
- the profiles can be identified by any one of IUCs 5 , 6 , 9 , 10 , 11 , 12 , 13 in a downstream message.
- IUC 13 may be used to inform CMs 18 of assigned profiles 22 and for carrying upstream traffic.
- IUC 13 has robust settings that allow data transmission on all the segments.
- Profile measurement and selection on the data profiles configured on a channel is performed according to various mechanisms. For example, during or after CM 18 ( 1 ) registration, the CMTS has the option of assigning CM 18 ( 1 ) one or two data profiles 22 ( 1 ) and 22 ( 2 ) that have higher bandwidth capacity than IUC 13 , based on the service agreement associated with CM 18 ( 1 )'s service flows. After the registration, the CMTS may adjust profile settings to better fit RF plant and/or modem conditions which may vary over time.
- the mechanisms described herein according to various embodiments can be used to measure and evaluate profile performance before assigning the profiles to CMs 18 , and/or to adjust profiles 22 in use.
- FIG. 6 is a simplified flow diagram illustrating example operations 100 that may be associated with embodiments of communication system 10 .
- operations 100 are described in association with CM 18 ( 1 ); however, the operations may be applicable to any one or more CMs 18 in communication system 10 .
- probing signal scheduler 24 at CCAP core 12 may generate probing request 26 .
- CCAP core 12 and R-PHY entity 14 may transmit probing request 26 to CM 18 ( 1 ).
- CCAP core 12 may receive probing signal 28 from CM 18 ( 1 ).
- segmentation module 30 at CCAP core 12 may segment probing signal 28 according to various channel response characteristics. For example, portions of probing signal 28 with high channel variations may be segmented finely into small segments; portions of probing signal 28 with low channel variations may be segmented coarsely into large segments.
- the segment count may be initialized (e.g., segment count set to 1; a first segment selected; etc.)
- MER/SNR module 32 at CCAP core 12 may compute the true SER/MER for the selected segment discounting channel effects.
- the QAM order corresponding to the computed SER/MER may be determined from MER/SNR-QAM order LUT 36 .
- group delay calculator 34 may compute the group delay for the segment.
- a base pilot pattern corresponding to the computed group delay may be determined from group delay-pilot pattern LUT 40 .
- multiple profiles may be generated based on the base profile, for example, by adding margins.
- references to various features e.g., elements, structures, modules, components, steps, operations, characteristics, etc.
- references to various features e.g., elements, structures, modules, components, steps, operations, characteristics, etc.
- references to various features are intended to mean that any such features are included in one or more embodiments of the present disclosure, but may or may not necessarily be combined in the same embodiments.
- optically efficient refers to improvements in speed and/or efficiency of a specified outcome and do not purport to indicate that a process for achieving the specified outcome has achieved, or is capable of achieving, an “optimal” or perfectly speedy/perfectly efficient state.
- At least some portions of the activities outlined herein may be implemented in software in, for example, R-PHY entity 14 and/or CCAP core 12 .
- one or more of these features may be implemented in hardware, provided external to these elements, or consolidated in any appropriate manner to achieve the intended functionality.
- the various components may include software (or reciprocating software) that can coordinate in order to achieve the operations as outlined herein.
- these elements may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof.
- R-PHY entity 14 and/or CCAP core 12 described and shown herein may also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
- some of the processors and memory elements associated with the various nodes may be removed, or otherwise consolidated such that a single processor and a single memory element are responsible for certain activities.
- the arrangements depicted in the FIGURES may be more logical in their representations, whereas a physical architecture may include various permutations, combinations, and/or hybrids of these elements. It is imperative to note that countless possible design configurations can be used to achieve the operational objectives outlined here. Accordingly, the associated infrastructure has a myriad of substitute arrangements, design choices, device possibilities, hardware configurations, software implementations, equipment options, etc.
- the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM)), an ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for storing electronic instructions, or any suitable combination thereof.
- FPGA field programmable gate array
- EPROM erasable programmable read only memory
- EEPROM electrically erasable programmable read only memory
- ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for
- These devices may further keep information in any suitable type of non-transitory storage medium (e.g., random access memory (RAM), read only memory (ROM), field programmable gate array (FPGA), erasable programmable read only memory (EPROM), electrically erasable programmable ROM (EEPROM), etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs.
- RAM random access memory
- ROM read only memory
- FPGA field programmable gate array
- EPROM erasable programmable read only memory
- EEPROM electrically erasable programmable ROM
- any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’
- any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’
- communication system 10 may be applicable to other exchanges or routing protocols.
- communication system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements, and operations may be replaced by any suitable architecture or process that achieves the intended functionality of communication system 10 .
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Power Engineering (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
- Synchronisation In Digital Transmission Systems (AREA)
Abstract
Description
- This application claims the benefit of priority under 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/979,325 entitled “REMOTE PHY ARCHITECTURE,” filed Apr. 14, 2014, which is hereby incorporated by reference in its entirety.
- This disclosure relates in general to the field of communications and, more particularly, to determining and managing upstream profiles in Data Over Cable Service Interface Specification (DOCSIS) 3.1 network environments.
- Driven by market evolution towards triple-play services, cable operators in emerging markets are seeking standardized and digital fiber-based solutions for economical and future proof access technologies. Much of the demand is driven by the need to provide higher bandwidth packet transport for Internet connectivity, video and voice services. DOCSIS is an international telecommunications standard that has evolved to permit addition of high-bandwidth data transfer to an existing cable TV (CATV) system utilizing Quadrature Amplitude Modulation (QAM) and/or Quadrature phase-shift keying (QPSK) Radio Frequency (RF) modulation. It is employed by many cable television operators to provide Internet access over their existing hybrid fiber-coaxial (HFC) infrastructure. Traditionally, the DOCSIS system is a Point-to-Multipoint communications system, the corresponding standards defining Media Access Control (MAC)/physical layer (PHY) standards associated with providing high speed data over a hybrid fiber coaxial (HFC) network and is not naturally applicable for digital fiber. However, Cisco® remote-PHY (R-PHY) technology bridges the gap, leveraging existing Internet Protocol (IP) technologies to deploy data over digital fiber, enabling two-way services over cable.
- To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
-
FIG. 1 is a simplified block diagram illustrating a communication system for determining and managing upstream profiles in DOCSIS 3.1 network environments; -
FIG. 2 is a simplified block diagram illustrating example details of embodiments of the communication system; -
FIG. 3 is a simplified block diagram illustrating other example details of embodiments of the communication system; -
FIG. 4 is a simplified block diagram illustrating yet other example details of embodiments of the communication system; -
FIG. 5 is a simplified block diagram illustrating yet other example details of embodiments of the communication system; and -
FIG. 6 is a simplified flow diagram illustrating example operations that may be associated with an embodiment of the communication system. - An example method for determining and managing upstream profiles in Data Over Cable Service Interface Specification (DOCSIS) 3.1 network environments is provided and includes determining, at a Converged Cable Access Platform (CCAP) core, channel conditions independent of any channel effect over a hybrid fiber coaxial (HFC) network between a remote physical layer (R-PHY) entity coupled to the CCAP core and a cable modem (CM) in the DOCSIS 3.1 network environment, and assigning an upstream profile to the CM based on the channel conditions. In specific embodiments, the channel conditions include signal to noise ratio (SNR), modulation error ratio (MER) or group delay. In some embodiments, assigning the upstream profile includes determining a quadrature amplitude modulation (QAM) order based on the SNR or MER, and determining a pilot pattern based on the group delay, the combination of the QAM order and the pilot pattern identifying the upstream profile.
- As used herein, the term “profile” specifies modulation order and pilot patterns for active data sub-carriers of an Orthogonal Frequency-Division Multiplex Access (OFDMA) channel; in other words, a combination of a particular modulation order and pilot pattern indicates a unique profile. Further, an upstream direction indicates a communication path from CMs to the CCAP core; a downstream direction indicates a communication path from the CCAP core to the CMs. Note that MER is digital complex baseband SNR and the terms “SNR” and “MER” are used interchangeably herein, unless specifically differentiated.
- Turning to
FIG. 1 ,FIG. 1 is a simplified block diagram illustrating acommunication system 10 for determining and managing upstream profiles in DOCSIS 3.1 network environments in accordance with one example embodiment.FIG. 1 illustrates a network 11 (indicated generally by an arrow) facilitating communication between a Converged Cable Access Platform (CCAP)core 12 and an R-PHY entity 14 over a converged interconnect network (CIN) 16, and between R-PHY entity 14 and multiple cable modems (CMs) 18(1)-18(3) over a hybrid fiber coaxial (HFC)network 20. Note thatnetwork 11 can include any number of CCAP cores, each connected to a plurality of R-PHY entities, each of which is connected to multiple CMs within the broad scope of the embodiments.CCAP core 12 and R-PHY entity 14 together comprise a CCAP, which is typically a combination of a DOCSIS cable modem termination system (CMTS) and an edge QAM (EQAM). CCAPcore 12 and R-PHY entity 14 can communicate remotely in some embodiments overCIN 16 that can span across different geographic locations; in other embodiments,CIN 16 may comprise a set of interfaces within the same chassis. - For purposes of illustrating the techniques of
communication system 10, it is important to understand the communications that may be traversing the system shown inFIG. 1 . The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Such information is offered earnestly for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the present disclosure and its potential applications. - DOCSIS 3.1 specifies OFDMA for upstream channelization. Orthogonal frequency division multiplexing (OFDM) is a method of multi-carrier digital communication where wide-band information data is distributed across many narrow-band subcarriers in the frequency domain. OFDMA is a method of multi-user digital communications, wherein each user utilizes an allotment of the available sub-carriers and time intervals for their individual communication. Because the fundamental operation and advantages of OFDMA systems is similar to that of OFDM systems in a multipath wireless propagation environment, the terms OFDM and OFDMA are used here interchangeably.
- OFDM divides the upstream spectrum into multiple equally spaced subcarriers. In DOCSIS, the subcarrier spacing is 25 kHz or 50 kHz, corresponding to 40 us or 20 us long symbol duration, respectively. The subcarriers are divided into multiple equally sized clusters called mini-slots. Each mini-slot consists of Q subcarriers, where Q equals to 16 or 8 corresponding to 25 kHz or 50 kHz subcarrier spacing, respectively. A QAM order and a pilot pattern (e.g., reference signal with information known apriori to the receiver; pilot patterns have known, fixed characteristics when they are transmitted) are assigned to each mini-slot. (In contrast to single carrier systems (such as SC-QAM), coherent orthogonal frequency-division multiplexing (OFDM) systems traditionally have pilot patterns placed at specified intervals in time and frequency, in the OFDM frequency-time signal space, to facilitate simple channel estimation for a range of frequencies and channel dispersion.) The QAM order and pilot pattern can change from one mini-slot to another. DOCSIS 3.1 supports up to eleven (11) levels of QAM orders (Quadrature Phase Shift Keying (QPSK)-4KQAM, squared and non-squared (the notation KQAM is used to indicate a modulation scheme encoding log2(K) bits per symbol, thereby providing K symbols)) and 8 different pilot patterns.
- DOCSIS 3.1 specifications allow for
profiles 22 to be assigned to eachCM 18 allowing upstream resource allocations and dictating how upstream symbols are demodulated at CCAPcore 12. For example, profiles 22(1) and 22(2) are assigned to CM 18(1); profiles 22(3) and 22(4) are assigned to CM 18(2); profiles 22(5) and 22(6) are assigned to CM 18(3); and so on. In a general sense, each ofprofiles 22 specifies the QAM order for data symbols and pilot pattern of a mini-slot of an upstream OFDMA channel. Each OFDM channel has its own unique set of profiles 22 (e.g.,profiles 22 describe subcarriers at a particular frequency, and each OFDM channel occupies different frequencies.) From a packet forwarding perspective, eachprofile 22 creates a unique path through an OFDM channel from R-PHY entity 14 toCMs 18. The term ‘profile’ can be considered a PHY level description for the packet forwarding mechanism; the term ‘path’ can be considered a MAC level description for the packet forwarding mechanism. -
Profiles 22 can allow for effective optimization of the transmission path to or fromCMs 18 that can tolerate a higher modulation. The aggregate capacity of the OFDM channel depends upon the configuration of each ofprofiles 22 characterizing the OFDM channel and the relative usage of eachprofile 22 because all profiles 22 (for each OFDM channel) in combination share the aggregate channel capacity (for each OFDM channel). Eachprofile 22 profile can be characterized (e.g., indicated, defined, specified, parameterized, etc.) by the QAM orders and pilot patterns on the mini-slots over the spectrum. According to DOCSIS 3.1, eachCM 18 should support up to twoprofiles 22 for upstream data traffic. In the upstream,profile 22 can be synonymous with data Interval Usage Codes (IUCs); their allocations are signaled by MAP messages. -
CCAP core 12 determines the allocation ofprofiles 22 to each OFDM channel, and to eachCM 18. The profile management involves two distinct tasks: (1) determine the OFDM profile parameters (e.g., QAM order and pilot pattern); (2) assignprofiles 22 to groups ofCMs 18 from whomCCAP core 12 receives upstream signals with similar fidelity, for example, based on the quality of their respective communication links with R-PHY entity 14 overHFC network 20. - Assume, merely as an example, and not as a limitation that CCAP
core 12 attempts to make a profile assignment to CM 18(1). According to DOCSIS 3.1 specifications, CM 18(1) is eligible to be assigned two profiles, andCCAP core 12 determines the QAM orders and pilot patterns that characterize two profiles 22(1) and 22(2), for example, based on the bandwidth availability and other communication link conditions between R-PHY entity 14 and CM 18(1). To determine the QAM order and pilot pattern for each mini-slot, a probing signal scheduler 24 inCCAP core 12 may schedule a wide band probing signal and allocate two probing opportunities within the same probe frame in aprobing request 26 for CM 18(1), which may be forwarded to CM 18(1) overHFC network 20. CM 18(1) may respond with aprobing signal 28. - A
segmentation module 30 inCCAP core 12 divides the spectrum of probing signal 28 (also referred to herein as the channel response) into multiple segments. A modulation error ratio (MER)/ signal to noise ratio (SNR)module 32 determines a ‘true’ MER/SNR of probingsignal 28 that is independent of the effect of the OFDM channel (e.g., each channel may affect SNR/MER differently, for example, through group delay variation, amplitude tilt or ripple, and micro-reflections) for each segment. Note that MER refers to a ratio of average symbol power to average error power (e.g., the higher the MER, the cleaner (less distorted) the received signal). - In some embodiments, the segmentation is evaluated and adjusted substantially continuously with each probing opportunity. In some embodiments, the segmentation is evaluated by examining how quickly the QAM order and pilot pattern vary from one segment to another, and re-adjusted with each probing opportunity if necessary. Each segment includes multiple mini-slots that have the same QAM order and pilot pattern. In some embodiments, the segments are not equal in size. In other embodiments, the segments may be substantially equal in size.
- In a general sense, the QAM order can be determined by the inherent spectrum efficiency or channel capacity of the mini-slot, which may be determined from signal MER/SNR measurements at the input of a low-density parity-check (LDPC) decoder in MER/
SNR module 32 after channel estimation. Agroup delay calculator 34 may compute the average group delay of each segment, which is correlated with the channel variation. “Group delay” refers to a negative derivative of phase with respect to frequency, expressed mathematically as g_t=−(dφ/dω) and expressed in units of time such as nanoseconds. Group delay variation refers to a difference in propagation time between one frequency and another (e.g., some frequency components of the signal may arrive at the output before others, causing distortion of the received signal). - In some embodiments, the group delay is estimated through a phase ramp in frequency domain, which can be an effective scheme with low complexity.
Group delay calculator 34 may determine the QAM order for each segment by mapping the computed MER/SNR to QAM order using a MER/SNR-QAM order Look-Up-Table (LUT) 36. In various embodiments, MER/SNR-QAM order LUT 36 may be preconfigured inCCAP core 12 using simulations, calibrations, heuristic techniques, or other mechanisms. - A
pilot pattern module 38 inCCAP core 12 may determine how quickly the channel gain varies within the mini-slot (8 or 16 subcarriers, total 400 kHz BW), for example, to select a pilot pattern with proper pilot density.Pilot pattern module 38 may determine the profile granularity over the spectrum (e.g., by grouping multiple adjacent mini-slots together and assign the same QAM order and pilot pattern to reduce computations and upstream channel allocation complexity). In some embodiments,pilot pattern module 38 may determine the pilot pattern for each segment by mapping the computed group delay to pilot patterns using a group delay-pilot pattern LUT 40. In various embodiments, group delay-pilot pattern LUT 40 may be preconfigured inCCAP core 12 using simulations, calibrations, heuristic techniques, or other mechanisms.Pilot pattern module 38 may generate multiple profiles from a base profile by adding margins. Aprofile updater 42 inCCAP core 12 may also updateprofiles 22 to cope with varying channels and cable modem conditions. Assigned profiles 22(1) and 22(2) may be mapped to CM 18(1) in a CM-profile table 44. Aprocessor 46 and amemory element 48 may facilitate the operations described herein. - In various embodiments, segmentation can simplify CMTS algorithms to evaluate upstream probing
signal 28, for example, by not requiring processor intensive per sub-carrier computations. The operations described herein can allow dynamically adjusting a size ofprofiles 22, and reducing computation and complexity of upstream schedulers. In some embodiments, various modules may be implemented (e.g., execute on) hardware accelerators using appropriate hardware configured with suitable software. - Turning to the infrastructure of
communication system 10, the network topology can include any number of cable modems, customer premises equipment, servers, switches (including distributed virtual switches), routers, and other nodes inter-connected to form a large and complex network.Network 11 represents a series of points or nodes of interconnected communication paths for receiving and transmitting packets and/or frames of information that are delivered tocommunication system 10. A node may be any electronic device, computer, printer, hard disk drive, client, server, peer, service, application, or other object capable of sending, receiving, or forwarding information over communications channels in a network. Elements ofFIG. 1 may be coupled to one another through one or more interfaces employing any suitable connection (wired or wireless), which provides a viable pathway for electronic communications. Additionally, any one or more of these elements may be combined or removed from the architecture based on particular configuration needs. -
Network 11 offers a communicative interface between cable modem network components, and may include any local area network (LAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Internet, Extranet, wide area network (WAN), virtual private network (VPN), or any other appropriate architecture or system that facilitates communications in a network environment.Network 11 may implement any suitable communication protocol for transmitting and receiving data packets withincommunication system 10. The architecture of the present disclosure may include a configuration capable of TCP/IP, TDMA, and/or other communications for the electronic transmission or reception information in a network. The architecture of the present disclosure may also operate in conjunction with any suitable protocol, where appropriate and based on particular needs. In addition, gateways, routers, switches, and any other suitable nodes (physical or virtual) may be used to facilitate electronic communication between various nodes in the network. - Note that the numerical and letter designations assigned to the elements of
FIG. 1 do not connote any type of hierarchy; the designations are arbitrary and have been used for purposes of teaching only. Such designations should not be construed in any way to limit their capabilities, functionalities, or applications in the potential environments that may benefit from the features ofcommunication system 10. It should be understood thatcommunication system 10 shown inFIG. 1 is simplified for ease of illustration. - In some embodiments, a communication link may represent any electronic link supporting a network environment such as, for example, cable, Ethernet, wireless technologies (e.g., IEEE 802.11x), ATM, fiber optics, etc. or any suitable combination thereof. In other embodiments, communication links may represent a remote connection through any appropriate medium (e.g., digital subscriber lines (DSL), telephone lines, T1 lines, T3 lines, wireless, satellite, fiber optics, cable, Ethernet, etc. or any combination thereof) and/or through any additional networks such as a wide area networks (e.g., the Internet).
- In particular embodiments,
CCAP core 12 may comprise a hardware appliance with appropriate ports, processors, memory elements, interfaces, and other electrical and electronic components that facilitate the functions described herein. In some embodiments, the various modules inCCAP core 12 may comprise hardware devices or software applications or combination thereof executing withinCCAP core 12 to perform the operations described herein. In other embodiments, the various modules inCCAP core 12 may comprise hardware devices or software applications executing outsideCCAP core 12, for example, in a separate appliance, server, or other network element and coupled (e.g., connected to, in communication with, etc.) toCCAP core 12 innetwork 11. - R-
PHY entity 14 may comprise suitable hardware components and interfaces for facilitating the operations described herein. In some embodiments, R-PHY entity 14 may be embedded in or be part of another hardware component, such as a broadband processing engine (comprising a motherboard, microprocessors and other hardware components). In some embodiments, R-PHY entity 14 comprises downstream and upstream PHY, deployed in a Coaxial Media Converter (CMC) that supports RF functions at the PHY layer. - Note that is some embodiments,
CCAP core 12 and R-PHY entity 14 may be located in the same chassis; in other embodiments,CCAP core 12 and R-PHY entity 14 may be located in different physical locations, remote from each other and coupled over aLayer 2 orLayer 3 network with various other network elements, such as switches and routers intervening there between. - Turning to
FIG. 2 ,FIG. 2 is a simplified block diagram illustrating example details associated with segmentation according to an embodiment ofcommunication system 10. The frequency spectrum of probingsignal 28 may be segmented in N segments 50(1)-50(N). In some embodiments, segmentation is performed at mini-slot boundaries. The spectrum may be segmented to account for upstream channel variation. For example, portions of the spectrum with large channel variations may be segmented into small size segments (e.g., fine segmentation); portions of the spectrum with small channel variations may be segmented into large size segments (e.g., coarse segmentation). In some embodiments, channel variation is estimated from probingsignal 28 detected in a current probing opportunity; in other embodiments, channel variation may be estimated from probingsignal 28 in current and previous probing opportunities. Segmentation may be continuously evaluated and adjusted based on the latest channel information. - In various embodiments, the spectrum may be segmented such that the SNR and channel response remain relatively constant within each segment. The SNR and group delay may be computed for each segment separately. Variations of the SNR and group delay between segments may also be determined. If the variation is greater than a preconfigured threshold (e.g., 30%), size of the segments where rapid changes occur may be reduced correspondingly (e.g., by splitting one segment into two). If the variation is less than another preconfigured threshold (e.g., 5%) the segment size may be increased by combining adjacent segments. The segmentation may be re-evaluated and adjusted substantially continuously with each probing opportunity.
- Note that segmentation is applicable to active subcarriers, and not to ‘excluded subcarriers’ 52. In a general sense, excluded subcarriers are forced to zero-valued modulation at the transmitter. Subcarriers are excluded to prevent interference to other transmissions that occupy the same spectrum, for example, to accommodate legacy channels. Subcarriers are also excluded outside of the active OFDM bandwidth. Excluded subcarriers are common to all profiles 22. The non-excluded subcarriers are referred to as active subcarriers.
- Turning to
FIG. 3 ,FIG. 3 is a simplified block diagram illustrating example details of aprobe frame 54 according to an embodiment ofcommunication system 10. Frequency is graphed along a vertical axis, and time (or symbols) is graphed along a horizontal axis. For the purpose of determiningupstream profile 22, probing signal scheduler 24 schedules two probing opportunities 56(1) and 56(2) in asingle probe frame 54. In an example embodiment, probing opportunities 56(1) and 56(2) are configured with no-stagger, no skip, and starting index=0. - In various embodiments, probing
signal 28 may comprise a pseudo-random binary sequence (PRBS) modulated with binary phase-shift keying (BPSK). Probingsignal 28 may be by de-randomized by removing the known PRBS sequence from probingsignal 28. The channel effect may be removed to compute the ‘true’ SNR/MER. The de-randomized probing signals for a first opportunity and a second opportunity (P1(i) and P2(i) respectively) for the ith active subcarrier may be obtained by multiplying probingsignal 28 with the known probing PRBS as follows: -
P1(i)=S1(i)*PRBS(i); -
P2(i)=S2(i)*PRBS(i); -
i=1,2, . . . - where S1(i), S2(i) are, respectively, probing
signal 28 at the first opportunity and the second opportunity; PRBS(i) is the known PRBS; and index i runs over active subcarriers in the segment. The channel estimation independent of the channel effect may be computed as: -
- The leveraged de-randomized probing signal P12(i) (i=1,2, . . . ) contains no channel effects.
- After the channel estimation, the SNR/MER can be computed from the following equation:
-
- Where Ns is the total number of active subcarriers in the segment. The formula utilizes the fact that probing signal is modulated with BPSK (e.g., reference point on a QAM constellation is 1; in a general sense, a constellation represents the possible symbols (e.g., waveform such as a pulse or tone representing a certain number of bits) that may be selected by a given modulation scheme). The SNR computed as described herein may include no channel effect, and may be a true representative for the MER/SNR at the input of LDPC decoder. Thereafter, the QAM order for the segment can be obtained through MER/SNR-
QAM order LUT 36. - Turning to
FIG. 4 ,FIG. 4 is a simplified diagram illustrating an example MER/SNR-QAM order LUT 36 according to an embodiment ofcommunication system 10. MER/SNR-QAM order LUT 36 may be generated from simulations, testing, calibration, heuristics, or other suitable mechanisms within the broad scope of the embodiments. MER/SNR-QAM order LUT 36 represents an association between the QAM constellation (indicative of the QAM order) and SNR (or MER). If the SNR/MER is known, a lookup of MER/SNR-QAM order LUT 36 can indicate the corresponding QAM order to be used forprofile 22. - Turning to
FIG. 5 ,FIG. 5 is a simplified diagram illustrating an example group delay-pilot pattern LUT 40 according to an embodiment ofcommunication system 10. Group delay may be associated with a pilot pattern in group delay-pilot pattern LUT 40 based on simulations, testing, calibration, heuristics, or other suitable mechanisms within the broad scope of the embodiments. The group delay (e.g., time offset) can be a good indication of channel variation, which in turn can determine a suitable pilot pattern density (e.g., number of pilot patterns in a signal of known duration). In various embodiments, the group delay is estimated from a phase ramp in each segment. For example, in each segment, a dot product of the conjugate of probingsignal 28 on the ith subcarrier with probingsignal 28 on the next ((i+1)th) subcarrier may be obtained: -
bi=conj(P″(i))·P′(i+1); i=1, 2 . . . - where P(i) and P(i+1) are, respectively, probing
signal 28 detected on ith and (i+1)th subcarriers in the segment being evaluated. The result bi may be summed over the subcarriers in the segment: -
- The group delay g_t may be computed as follows:
-
- where sc is a subcarrier space (e.g., 25 kHz or 50 kHz).
- Based on the group delay g_t, the pilot pattern for the segment can be obtained according to group delay-
pilot pattern LUT 40. For example, if g_t is computed to be less than 10 times a preconfigured threshold value t0, apredetermined pattern 1 may be used in the 50 kHz subcarrier space, whereaspattern 5 may be used in the 25 kHz subcarrier space. If g_t is between 10 times t0 and 20 times t0,pattern 2 may be used in the 50 kHz subcarrier space, whereaspattern 6 may be used in the 25 kHz subcarrier space. Note that the thresholds (e.g., t0, 10*t0, 20*t0, etc.) can be changed to suit particular needs within the broad scope of the embodiments. - In various embodiments,
CMs 18 can support up to two upstream profiles for data traffic (and additional profiles for downstream traffic). In some embodiments, additional profiles can be generated from a base profile (e.g., determined as described herein) by adding margins. For example, assume that profile 22(1) is designated for short and high priority messages, 3 dB margin can be added to obtain another QAM order from MER/SNR-QAM order LUT 36 and an additional level can be added to the group delay to obtain another pilot pattern from group delay—pilot pattern LUT 40 to generate another profile 22(2). - Typically, profile information to
CMs 18 is carried through an Interval Usage Code (IUC) in a downstream message from the CMTS toCMs 18. In a general sense, tells IUCs indicate to each cable modem the type of modulation (and other characteristics) to use depending upon the information the cable modems are transmitting to the CMTS. In DOCSIS 3.1, the profiles can be identified by any one ofIUCs CMs 18 of assignedprofiles 22 and for carrying upstream traffic. Generally IUC 13 has robust settings that allow data transmission on all the segments. Profile measurement and selection on the data profiles configured on a channel is performed according to various mechanisms. For example, during or after CM 18(1) registration, the CMTS has the option of assigning CM 18(1) one or two data profiles 22(1) and 22(2) that have higher bandwidth capacity than IUC 13, based on the service agreement associated with CM 18(1)'s service flows. After the registration, the CMTS may adjust profile settings to better fit RF plant and/or modem conditions which may vary over time. The mechanisms described herein according to various embodiments can be used to measure and evaluate profile performance before assigning the profiles toCMs 18, and/or to adjustprofiles 22 in use. - Turning to
FIG. 6 ,FIG. 6 is a simplified flow diagram illustratingexample operations 100 that may be associated with embodiments ofcommunication system 10. Note thatoperations 100 are described in association with CM 18(1); however, the operations may be applicable to any one ormore CMs 18 incommunication system 10. At 102, probing signal scheduler 24 atCCAP core 12 may generate probingrequest 26. At 104,CCAP core 12 and R-PHY entity 14 may transmit probingrequest 26 to CM 18(1). At 104,CCAP core 12 may receive probingsignal 28 from CM 18(1). At 108,segmentation module 30 atCCAP core 12 maysegment probing signal 28 according to various channel response characteristics. For example, portions of probingsignal 28 with high channel variations may be segmented finely into small segments; portions of probingsignal 28 with low channel variations may be segmented coarsely into large segments. - At 110, the segment count may be initialized (e.g., segment count set to 1; a first segment selected; etc.) At 112, MER/
SNR module 32 atCCAP core 12 may compute the true SER/MER for the selected segment discounting channel effects. At 114, the QAM order corresponding to the computed SER/MER may be determined from MER/SNR-QAM order LUT 36. At 116,group delay calculator 34 may compute the group delay for the segment. At 120, a base pilot pattern corresponding to the computed group delay may be determined from group delay-pilot pattern LUT 40. At 122, multiple profiles may be generated based on the base profile, for example, by adding margins. At 124, a determination may be made whether computation for substantially all segments are completed. If not, the operations step to 126, at which the segment count is advanced (e.g., incremented; next segment selected; etc.) If computations for substantially all segments have been completed, at 128, segment to segment variation of QAM order and pilot pattern may be determined. - At 130, a determination may be made whether to adjust the segmentation. If segments are to be adjusted, the operations may step back to 108, and continue thereafter. For example, if the segment to segment variation in SNR and group delay is larger than a preconfigured threshold, the segment sizes in the affected segments may be halved. If the segment to segment variation in SNR and group delay is smaller than a preconfigured threshold, the segment sizes in the affected segments may be doubled; and so on. The operations may continue until segmentation adjustment is not needed further. Thereafter, at 132, profiles (as determined from the QAM order and pilot patterns) may be assigned to CM 18(1).
- Note that in this Specification, references to various features (e.g., elements, structures, modules, components, steps, operations, characteristics, etc.) included in “one embodiment”, “example embodiment”, “an embodiment”, “another embodiment”, “some embodiments”, “various embodiments”, “other embodiments”, “alternative embodiment”, and the like are intended to mean that any such features are included in one or more embodiments of the present disclosure, but may or may not necessarily be combined in the same embodiments. Furthermore, the words “optimize,” “optimization,” and related terms are terms of art that refer to improvements in speed and/or efficiency of a specified outcome and do not purport to indicate that a process for achieving the specified outcome has achieved, or is capable of achieving, an “optimal” or perfectly speedy/perfectly efficient state.
- In example implementations, at least some portions of the activities outlined herein may be implemented in software in, for example, R-
PHY entity 14 and/orCCAP core 12. In some embodiments, one or more of these features may be implemented in hardware, provided external to these elements, or consolidated in any appropriate manner to achieve the intended functionality. The various components may include software (or reciprocating software) that can coordinate in order to achieve the operations as outlined herein. In still other embodiments, these elements may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. - Furthermore, R-
PHY entity 14 and/orCCAP core 12 described and shown herein (and/or their associated structures) may also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. Additionally, some of the processors and memory elements associated with the various nodes may be removed, or otherwise consolidated such that a single processor and a single memory element are responsible for certain activities. In a general sense, the arrangements depicted in the FIGURES may be more logical in their representations, whereas a physical architecture may include various permutations, combinations, and/or hybrids of these elements. It is imperative to note that countless possible design configurations can be used to achieve the operational objectives outlined here. Accordingly, the associated infrastructure has a myriad of substitute arrangements, design choices, device possibilities, hardware configurations, software implementations, equipment options, etc. - In some of example embodiments, one or more memory elements (e.g., memory elements 48) can store data used for the operations described herein. This includes the memory element being able to store instructions (e.g., software, logic, code, etc.) in non-transitory media, such that the instructions are executed to carry out the activities described in this Specification. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, processors (e.g., processor 46) could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM)), an ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for storing electronic instructions, or any suitable combination thereof.
- These devices may further keep information in any suitable type of non-transitory storage medium (e.g., random access memory (RAM), read only memory (ROM), field programmable gate array (FPGA), erasable programmable read only memory (EPROM), electrically erasable programmable ROM (EEPROM), etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. The information being tracked, sent, received, or stored in
communication system 10 could be provided in any database, register, table, cache, queue, control list, or storage structure, based on particular needs and implementations, all of which could be referenced in any suitable timeframe. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ - It is also important to note that the operations and steps described with reference to the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, the system. Some of these operations may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the discussed concepts. In addition, the timing of these operations may be altered considerably and still achieve the results taught in this disclosure. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by the system in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the discussed concepts.
- Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. For example, although the present disclosure has been described with reference to particular communication exchanges involving certain network access and protocols,
communication system 10 may be applicable to other exchanges or routing protocols. Moreover, althoughcommunication system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements, and operations may be replaced by any suitable architecture or process that achieves the intended functionality ofcommunication system 10. - Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C.
section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/685,422 US9660774B2 (en) | 2014-04-14 | 2015-04-13 | Determining and managing upstream profiles in DOCSIS 3.1 network environments |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201461979325P | 2014-04-14 | 2014-04-14 | |
US14/685,422 US9660774B2 (en) | 2014-04-14 | 2015-04-13 | Determining and managing upstream profiles in DOCSIS 3.1 network environments |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150295684A1 true US20150295684A1 (en) | 2015-10-15 |
US9660774B2 US9660774B2 (en) | 2017-05-23 |
Family
ID=54265960
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/680,873 Expired - Fee Related US9692563B2 (en) | 2014-04-14 | 2015-04-07 | Upstream contention measurement reporting and mitigation in DOCSIS remote PHY network environments |
US14/685,422 Expired - Fee Related US9660774B2 (en) | 2014-04-14 | 2015-04-13 | Determining and managing upstream profiles in DOCSIS 3.1 network environments |
US14/685,452 Expired - Fee Related US9692564B2 (en) | 2014-04-14 | 2015-04-13 | Downstream external physical interface transport in DOCSIS 3.1 network environments |
US14/685,403 Expired - Fee Related US9722739B2 (en) | 2014-04-14 | 2015-04-13 | Managing time offset and frequency drift in asynchronous DOCSIS remote PHY network environments |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/680,873 Expired - Fee Related US9692563B2 (en) | 2014-04-14 | 2015-04-07 | Upstream contention measurement reporting and mitigation in DOCSIS remote PHY network environments |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/685,452 Expired - Fee Related US9692564B2 (en) | 2014-04-14 | 2015-04-13 | Downstream external physical interface transport in DOCSIS 3.1 network environments |
US14/685,403 Expired - Fee Related US9722739B2 (en) | 2014-04-14 | 2015-04-13 | Managing time offset and frequency drift in asynchronous DOCSIS remote PHY network environments |
Country Status (1)
Country | Link |
---|---|
US (4) | US9692563B2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9692563B2 (en) | 2014-04-14 | 2017-06-27 | Cisco Technology, Inc. | Upstream contention measurement reporting and mitigation in DOCSIS remote PHY network environments |
US9918326B2 (en) * | 2015-05-27 | 2018-03-13 | Comcast Cable Communications, Llc | Optimizing resources in data transmission |
US20180219621A1 (en) * | 2017-01-31 | 2018-08-02 | Arcom Digital, Llc | Communicating Network Maintenance Data in a Cable System |
CN109218858A (en) * | 2018-09-11 | 2019-01-15 | 北京邮电大学 | Frequency spectrum distributing method, device and storage medium for space division multiplexing optical-fiber network |
US10608897B2 (en) * | 2016-11-10 | 2020-03-31 | Applied Broadband Inc. | Broadband profile management |
US10616622B2 (en) | 2018-06-06 | 2020-04-07 | Arcom Digital Patent, Llc | Detection of CPD from signals captured at remote PHY device |
US11082732B2 (en) | 2019-08-07 | 2021-08-03 | Arcom Digital Patent, Llc | Detection of CPD using leaked forward signal |
US11095407B2 (en) * | 2015-05-15 | 2021-08-17 | Huawei Technologies Co., Lid. | Signal processing method, apparatus, and system |
US20220060864A1 (en) * | 2020-08-20 | 2022-02-24 | Rooster, LLC | Asset Tracking Systems and Methods |
US11283559B2 (en) | 2019-06-17 | 2022-03-22 | Casa Systems, Inc. | Methods and apparatus for generating and using dynamic profiles for cable transmission systems |
US11456967B2 (en) * | 2019-03-04 | 2022-09-27 | Arris Enterprises Llc | System and method for increasing flexibility and high availability in remote network devices |
US11469938B1 (en) * | 2019-12-06 | 2022-10-11 | Harmonic, Inc. | Distributed scheduling in remote PHY |
US20230090396A1 (en) * | 2021-09-17 | 2023-03-23 | Comcast Cable Communications, Llc | Network Management for Band Splits |
US11997050B2 (en) | 2023-06-14 | 2024-05-28 | Casa Systems, Inc. | Methods and apparatus for generating and using dynamic profiles for cable transmission systems |
Families Citing this family (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104662857A (en) * | 2012-03-30 | 2015-05-27 | 瑞典爱立信有限公司 | Method and system for robust precision time protocol synchronization |
DE102012222885A1 (en) * | 2012-12-12 | 2014-06-12 | Bayerische Motoren Werke Aktiengesellschaft | Method for assigning timestamps to received data packets |
KR101542016B1 (en) * | 2014-09-17 | 2015-08-05 | 성균관대학교산학협력단 | Gateway apparatus and method for synchronizing heterogeneous network domains in vehicle |
WO2016095099A1 (en) * | 2014-12-16 | 2016-06-23 | 华为技术有限公司 | Time synchronization method and apparatus |
US9584302B2 (en) * | 2015-06-05 | 2017-02-28 | Analog Devices Global | Method and apparatus for synchronization of slave clock to master clock |
JP6424791B2 (en) * | 2015-10-08 | 2018-11-21 | 株式会社デンソー | Wireless communication device, wireless communication system |
US10944591B2 (en) * | 2015-10-14 | 2021-03-09 | Electrolux Home Products, Inc. | Automatically setting a clock of a network-connected apparatus |
CN105743598B (en) * | 2016-01-26 | 2018-06-26 | 华中科技大学 | A kind of Industrial Ethernet clock synchronizing method and system |
DE112017000152T5 (en) * | 2016-02-22 | 2018-06-28 | Harmonic Inc. | Virtual Core of a CCAP (Converged Cable Access Platform) |
WO2017144082A1 (en) * | 2016-02-23 | 2017-08-31 | Telefonaktiebolaget Lm Ericsson (Publ) | Time synchronization between nodes connected by a wireless network |
US9673970B1 (en) * | 2016-02-25 | 2017-06-06 | Khalifa University Of Science, Technology And Research | Methods and systems for estimating frequency synchronization accuracy |
PL3211889T3 (en) * | 2016-02-26 | 2019-09-30 | Teleste Oyj | An arrangement for distributed catv network |
US10009929B1 (en) * | 2016-03-24 | 2018-06-26 | Sprint Spectrum L.P. | Contention-based random access |
US9820275B2 (en) | 2016-04-15 | 2017-11-14 | Cisco Technology, Inc. | Proactive upstream scheduling for flows in a point-to-multipoint communications network |
US10728595B2 (en) | 2016-06-07 | 2020-07-28 | Viavi Solutions Inc. | Upstream sweep test with sweep server signaling |
US10341083B2 (en) | 2016-09-09 | 2019-07-02 | Huawei Technologies Co., Ltd. | System and methods for network synchronization |
US10439712B2 (en) * | 2016-09-09 | 2019-10-08 | Huawei Technologies Co., Ltd. | System and methods for determining propagation delay |
US10404585B1 (en) * | 2016-12-19 | 2019-09-03 | Harmonic, Inc. | Dynamically segregating sources of ingress at a node |
CN109923802B (en) * | 2017-01-20 | 2021-01-08 | 华为技术有限公司 | Data processing method, optical access equipment and optical access system |
CN110546526A (en) * | 2017-02-14 | 2019-12-06 | Quadrac株式会社 | Device and system |
CN108540354A (en) * | 2017-03-02 | 2018-09-14 | 漳州立达信光电子科技有限公司 | Terminal device of network of things and the method for controlling multiple Internet of things device |
US11082141B2 (en) * | 2017-06-02 | 2021-08-03 | Sony Corporation | Wireless apparatus and wireless apparatus processing method |
US10637740B2 (en) * | 2017-07-07 | 2020-04-28 | Howard Pfeffer | Apparatus and methods for management, configuration and provisioning of communication devices in a distributed access architecture |
US10868623B2 (en) * | 2017-07-26 | 2020-12-15 | Aviat U.S., Inc. | Airframe timestamping technique for point-to-point radio links |
US10411986B2 (en) | 2017-07-26 | 2019-09-10 | Aviat U.S., Inc. | Distributed radio transparent clock over a wireless network |
US10574426B2 (en) * | 2017-08-28 | 2020-02-25 | Avago Technologies International Sales Pte. Limited | Full duplex ranging systems and methods |
US11018790B2 (en) | 2017-11-06 | 2021-05-25 | Arris Enterprises Llc | Timing adjustment for distributed network architecture |
US10812847B2 (en) * | 2017-12-20 | 2020-10-20 | Rovi Guides, Inc. | Systems and methods for avoiding spoilers in presenting recording prompts relating to a competition |
US10911171B2 (en) * | 2018-02-01 | 2021-02-02 | Anacapa Semiconductor, Inc. | High precision multi-chip clock synchronization |
GB2584046B (en) * | 2018-02-05 | 2022-12-28 | Harmonic Inc | Dynamic software architecture reconfiguration for converged cable access platform (CCAP) |
CN110224775B (en) * | 2018-03-01 | 2021-10-29 | 中兴通讯股份有限公司 | Method, device and equipment for determining time information |
US11480514B2 (en) * | 2018-05-25 | 2022-10-25 | Anacapa Semiconductor, Inc. | Fluorescence lifetime imaging (FLIM) and flow cytometry applications for a time synchronized sensor network |
US11546072B2 (en) * | 2018-12-14 | 2023-01-03 | Arris Enterprises Llc | Systems and methods to improve holdover performance in R-PHY network architectures |
US10841031B2 (en) * | 2018-12-14 | 2020-11-17 | Arris Enterprises Llc | Systems and methods to improve holdover performance in R-PHY network architectures |
CN113169806A (en) * | 2018-12-14 | 2021-07-23 | 艾锐势有限责任公司 | System and method for improving performance retention in R-PHY network architectures |
US11782880B2 (en) * | 2019-01-04 | 2023-10-10 | International Business Machines Corporation | Synchronizing log data within a cluster |
CN109728869B (en) * | 2019-01-08 | 2020-10-02 | 安徽建筑大学 | Time synchronization system and method between tap water pipe network monitoring nodes |
US11750415B1 (en) * | 2019-01-21 | 2023-09-05 | Harmonic, Inc. | Remote PHY narrowband digital return (NDR) |
GB201900789D0 (en) * | 2019-01-21 | 2019-03-06 | Hoptroff London Ltd | Method for testing time distribution |
US10944852B2 (en) * | 2019-04-23 | 2021-03-09 | Cisco Technology, Inc. | Computer network packet transmission timing |
DE102019217035B4 (en) | 2019-11-05 | 2021-11-25 | Continental Automotive Gmbh | Procedure for securing the time synchronization in a network against unauthorized changes |
WO2021108673A1 (en) * | 2019-11-26 | 2021-06-03 | Arris Enterprises Llc | R-phy map advance time measurement |
MX2022007049A (en) * | 2019-12-10 | 2022-07-11 | Arris Entpr Llc | Systems and methods for large phase correction in r-phy network architectures. |
CN111163021B (en) * | 2020-01-06 | 2022-05-27 | 厦门狄耐克智能科技股份有限公司 | Data conversion transmission equipment based on two lines |
EP4122171B1 (en) * | 2020-03-20 | 2024-05-01 | Arris Enterprises, Llc | Efficient remote phy dataplane management for a cable system |
EP4176541A1 (en) * | 2020-07-06 | 2023-05-10 | Arris Enterprises, Llc | Clock emulation in distributed access architectures |
WO2022052918A1 (en) * | 2020-09-11 | 2022-03-17 | 北京灵汐科技有限公司 | Signal transmission method and apparatus |
JP2023551520A (en) | 2020-12-01 | 2023-12-08 | アリス エンタープライジズ リミティド ライアビリティ カンパニー | Partial video asynchronous support using R-MACPHY devices |
US11533526B2 (en) * | 2021-02-01 | 2022-12-20 | Arris Enterprises Llc | Adaptive video slew rate for video delivery |
US11552890B2 (en) * | 2021-02-11 | 2023-01-10 | Cisco Technology, Inc. | Enhanced entropy for a converged interconnect network |
US20220263677A1 (en) * | 2021-02-18 | 2022-08-18 | Arris Enterprises Llc | Systems and methods for supporting phase adjustments over docsis |
US20220286323A1 (en) * | 2021-03-03 | 2022-09-08 | Arris Enterprises Llc | Scheduler-directed source multiplexing for return path noise mitigation |
US11811504B2 (en) | 2021-06-23 | 2023-11-07 | Arris Enterprises Llc | RPD UCD refresh for timestamp recovery |
US11888587B2 (en) * | 2021-07-15 | 2024-01-30 | Ciena Corporation | Tolerant PCS for accurate timestamping in disaggregated network elements and synchronization method |
US20230291597A1 (en) * | 2022-01-31 | 2023-09-14 | Arris Enterprises Llc | Systems and methods for r-macphy partial service support |
WO2023164301A2 (en) * | 2022-02-28 | 2023-08-31 | Arris Enterprises Llc | Method of measuring timing holdover performance in an r-phy system |
US11953939B2 (en) * | 2022-03-03 | 2024-04-09 | Oversec, Uab | Clock management systems and methods |
WO2024006571A1 (en) * | 2022-07-01 | 2024-01-04 | Arris Enterprises Llc | Method of measuring network jitter |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070242732A1 (en) * | 2006-03-24 | 2007-10-18 | Via Technologies, Inc. | Spread spectrum receiver and channel compensation method thereof |
US20090285233A1 (en) * | 2008-04-18 | 2009-11-19 | Arris | Multi-service phy box |
US20130070765A1 (en) * | 2011-09-16 | 2013-03-21 | Cisco Technology, Inc. | Modular headend architecture with downstream multicast |
US20150222449A1 (en) * | 2014-01-31 | 2015-08-06 | Comcast Cable Communications, Llc | Digital forward link in hybrid fiber-coax network |
Family Cites Families (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4815109A (en) * | 1987-06-25 | 1989-03-21 | Racal Data Communications Inc. | Sampling clock synchronization |
WO2000028712A2 (en) * | 1998-10-30 | 2000-05-18 | Broadcom Corporation | Cable modem system |
US6614799B1 (en) * | 1999-01-20 | 2003-09-02 | Cisco Technology, Inc. | Method and apparatus for dynamic adjustment of cable modem back-off parameters in a cable modem network |
US7933295B2 (en) * | 1999-04-13 | 2011-04-26 | Broadcom Corporation | Cable modem with voice processing capability |
US6785292B1 (en) * | 1999-05-28 | 2004-08-31 | 3Com Corporation | Method for detecting radio frequency impairments in a data-over-cable system |
US6529520B1 (en) * | 1999-09-01 | 2003-03-04 | Motorola, Inc. | Method and device for bandwidth allocation in multiple access protocols with contention-based reservation |
DE60036561T2 (en) * | 1999-11-02 | 2008-06-26 | Broadcom Corp., Irvine | METHOD AND DEVICE FOR DETECTING AND CLASSIFYING COLLISIONS IN A RF NETWORK WITH JOINT ACCESS |
US6744697B2 (en) | 2000-04-26 | 2004-06-01 | Juniper Networks, Inc. | Cable modem clock synchronization using software parsing with hardware assist |
JP2001340356A (en) * | 2000-05-31 | 2001-12-11 | Gc Corp | Capsule for tooth restoring material |
US6801537B1 (en) * | 2000-09-07 | 2004-10-05 | Nortel Networks Limited | Adaptive contention algorithm based on truncated binary exponential back-off |
US6742187B1 (en) * | 2000-09-15 | 2004-05-25 | 3Com Corporation | Upstream bandwidth allocation map (MAP)-initiated channel change method for data-over-cable systems |
US7104534B2 (en) | 2001-06-08 | 2006-09-12 | Broadcom Corporation | System and method for detecting collisions in a shared communications medium |
US7085287B1 (en) | 2001-06-27 | 2006-08-01 | Cisco Technology, Inc. | Map routing technique implemented in access networks |
US7164697B1 (en) * | 2001-08-21 | 2007-01-16 | Juniper Networks, Inc. | Receiver design for implementing virtual upstream channels in broadband communication systems |
US7443873B1 (en) | 2001-08-21 | 2008-10-28 | Juniper Networks, Inc. | Virtual upstream channel provisioning and utilization in broadband communication systems |
US7590145B2 (en) * | 2002-09-17 | 2009-09-15 | Scientific-Atlanta, Inc. | Multiplexing octets from a data flow over MPEG packets |
US8711878B2 (en) * | 2004-12-10 | 2014-04-29 | Broadcom Corporation | Upstream channel bonding in a cable communications system |
US8831024B2 (en) * | 2006-12-29 | 2014-09-09 | Broadcom Corporation | Dynamic header creation and flow control for a programmable communications processor, and applications thereof |
US9270944B2 (en) * | 2007-02-14 | 2016-02-23 | Time Warner Cable Enterprises Llc | Methods and apparatus for content delivery notification and management |
US8032184B2 (en) * | 2007-02-22 | 2011-10-04 | Cisco Technology, Inc. | Method for generating downlink beamforming weighting vectors |
US8179883B2 (en) * | 2008-06-17 | 2012-05-15 | General Instrument Corporation | Apparatus, method and system for managing session encapsulation information within an internet protocol content bypass architecture |
US8081659B2 (en) * | 2008-07-02 | 2011-12-20 | Cisco Technology, Inc. | Map message expediency monitoring and automatic delay adjustments in M-CMTS |
KR101113338B1 (en) * | 2008-11-24 | 2012-02-29 | 한국전자통신연구원 | Method and apparatus for scheduling bandwidth in cable network |
US7697654B1 (en) * | 2009-05-28 | 2010-04-13 | Cisco Technology, Inc. | Determining effective carrier-to-interference plus noise ratio in OFDMA systems |
US9344319B1 (en) * | 2010-06-30 | 2016-05-17 | Arris Enterprises, Inc. | Edge-QAM and M-CMTS core timing lock |
US8913485B2 (en) | 2011-09-16 | 2014-12-16 | Telefonaktiebolaget L M Ericsson (Publ) | Open shortest path first (OSPF) nonstop routing (NSR) with link derivation |
US11323337B2 (en) * | 2011-09-27 | 2022-05-03 | Comcast Cable Communications, Llc | Resource measurement and management |
US8774217B2 (en) * | 2011-11-03 | 2014-07-08 | Cisco Technology, Inc. | Time domain duplex between CMTS and cable modems |
US20130125194A1 (en) * | 2011-11-15 | 2013-05-16 | Harmonic Inc. | Converged Cable Access Platform for Provision of Video and Data Services |
US9742495B2 (en) * | 2012-10-25 | 2017-08-22 | Arris Enterprises Llc | Timing correction for a DOCSIS Edge-Qam |
US9692563B2 (en) | 2014-04-14 | 2017-06-27 | Cisco Technology, Inc. | Upstream contention measurement reporting and mitigation in DOCSIS remote PHY network environments |
-
2015
- 2015-04-07 US US14/680,873 patent/US9692563B2/en not_active Expired - Fee Related
- 2015-04-13 US US14/685,422 patent/US9660774B2/en not_active Expired - Fee Related
- 2015-04-13 US US14/685,452 patent/US9692564B2/en not_active Expired - Fee Related
- 2015-04-13 US US14/685,403 patent/US9722739B2/en not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070242732A1 (en) * | 2006-03-24 | 2007-10-18 | Via Technologies, Inc. | Spread spectrum receiver and channel compensation method thereof |
US7822107B2 (en) * | 2006-03-24 | 2010-10-26 | Via Technologies, Inc. | Spread spectrum receiver and channel compensation method thereof |
US20090285233A1 (en) * | 2008-04-18 | 2009-11-19 | Arris | Multi-service phy box |
US20130070765A1 (en) * | 2011-09-16 | 2013-03-21 | Cisco Technology, Inc. | Modular headend architecture with downstream multicast |
US20150222449A1 (en) * | 2014-01-31 | 2015-08-06 | Comcast Cable Communications, Llc | Digital forward link in hybrid fiber-coax network |
Non-Patent Citations (2)
Title |
---|
Data-over-cable Service Interface Specification DOCSIS 3.1, Cable Television Laboratories, Inc 2013 * |
Provisional application No. 61/934,419, filed on January 31, 2014 * |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9692563B2 (en) | 2014-04-14 | 2017-06-27 | Cisco Technology, Inc. | Upstream contention measurement reporting and mitigation in DOCSIS remote PHY network environments |
US9692564B2 (en) | 2014-04-14 | 2017-06-27 | Cisco Technology, Inc. | Downstream external physical interface transport in DOCSIS 3.1 network environments |
US9722739B2 (en) | 2014-04-14 | 2017-08-01 | Cisco Technology, Inc. | Managing time offset and frequency drift in asynchronous DOCSIS remote PHY network environments |
US11095407B2 (en) * | 2015-05-15 | 2021-08-17 | Huawei Technologies Co., Lid. | Signal processing method, apparatus, and system |
US9918326B2 (en) * | 2015-05-27 | 2018-03-13 | Comcast Cable Communications, Llc | Optimizing resources in data transmission |
US10582515B2 (en) | 2015-05-27 | 2020-03-03 | Comcast Cable Communications, Llc | Optimizing resources in data transmission |
US11758574B2 (en) | 2015-05-27 | 2023-09-12 | Comcast Cable Communications, Llc | Optimizing resources in data transmission |
US11191087B2 (en) | 2015-05-27 | 2021-11-30 | Comcast Cable Communications, Llc | Optimizing resources in data transmission |
US10608897B2 (en) * | 2016-11-10 | 2020-03-31 | Applied Broadband Inc. | Broadband profile management |
US10158423B2 (en) * | 2017-01-31 | 2018-12-18 | Arcom Digital, Llc | Communicating network maintenance data in a cable system |
US20180219621A1 (en) * | 2017-01-31 | 2018-08-02 | Arcom Digital, Llc | Communicating Network Maintenance Data in a Cable System |
US10616622B2 (en) | 2018-06-06 | 2020-04-07 | Arcom Digital Patent, Llc | Detection of CPD from signals captured at remote PHY device |
US11290761B2 (en) | 2018-06-06 | 2022-03-29 | Arcom Digital Patent, Llc | Detection of CPD from signals captured at remote PHY device |
US11303945B2 (en) | 2018-06-06 | 2022-04-12 | Arcom Digital Patent, Llc | Detection of CPD from signals captured at remote PHY device |
CN109218858A (en) * | 2018-09-11 | 2019-01-15 | 北京邮电大学 | Frequency spectrum distributing method, device and storage medium for space division multiplexing optical-fiber network |
US11456967B2 (en) * | 2019-03-04 | 2022-09-27 | Arris Enterprises Llc | System and method for increasing flexibility and high availability in remote network devices |
US20220407819A1 (en) * | 2019-03-04 | 2022-12-22 | Arris Enterprises Llc | System and method for increasing flexibility and high availability in remote network devices |
US11757791B2 (en) * | 2019-03-04 | 2023-09-12 | Arris Enterprises Llc | System and method for increasing flexibility and high availability in remote network devices |
US11283559B2 (en) | 2019-06-17 | 2022-03-22 | Casa Systems, Inc. | Methods and apparatus for generating and using dynamic profiles for cable transmission systems |
US11728956B2 (en) | 2019-06-17 | 2023-08-15 | Casa Systems, Inc. | Methods and apparatus for generating and using dynamic profiles for cable transmission systems |
US11082732B2 (en) | 2019-08-07 | 2021-08-03 | Arcom Digital Patent, Llc | Detection of CPD using leaked forward signal |
US11469938B1 (en) * | 2019-12-06 | 2022-10-11 | Harmonic, Inc. | Distributed scheduling in remote PHY |
US20220060864A1 (en) * | 2020-08-20 | 2022-02-24 | Rooster, LLC | Asset Tracking Systems and Methods |
US11589195B2 (en) * | 2020-08-20 | 2023-02-21 | Ip Co, Llc | Asset tracking systems and methods |
US11844001B2 (en) | 2020-08-20 | 2023-12-12 | Ip Co., Llc | Asset tracking systems and methods |
US20230090396A1 (en) * | 2021-09-17 | 2023-03-23 | Comcast Cable Communications, Llc | Network Management for Band Splits |
US11997050B2 (en) | 2023-06-14 | 2024-05-28 | Casa Systems, Inc. | Methods and apparatus for generating and using dynamic profiles for cable transmission systems |
Also Published As
Publication number | Publication date |
---|---|
US20150295746A1 (en) | 2015-10-15 |
US9660774B2 (en) | 2017-05-23 |
US20150295669A1 (en) | 2015-10-15 |
US20150295838A1 (en) | 2015-10-15 |
US9722739B2 (en) | 2017-08-01 |
US9692564B2 (en) | 2017-06-27 |
US9692563B2 (en) | 2017-06-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9660774B2 (en) | Determining and managing upstream profiles in DOCSIS 3.1 network environments | |
EP3389235B1 (en) | Full duplex resource allocation in cable network environment | |
CN108370586B (en) | Pilot signal transmission system and method | |
CN107925599B (en) | Apparatus and method for interference relationship representation in full duplex cable network environment | |
JP6719544B2 (en) | Full-duplex network architecture within a cable network environment | |
CN107925597B (en) | System and method for scheduling in a full duplex cable network environment | |
JP4654296B2 (en) | Apparatus and method for adaptive channel quality feedback in multi-carrier wireless networks | |
EP3382950B1 (en) | Signaling method for interference group discovery in cable modems | |
EP3308493B1 (en) | Allocation and scheduling for time and frequency division multiplexing system | |
Das et al. | Performance analysis of OFDM systems with adaptive sub carrier bandwidth | |
KR20180030179A (en) | Suppress interference in full-duplex cable network environments | |
CN111555851A (en) | OFDMA subcarrier allocation device and method in next generation Wi-Fi network | |
US11290247B2 (en) | Systems and methods for non-orthogonal multiple access over networks | |
JP2007503780A (en) | Subcarrier and bit allocation for real-time services in multi-user orthogonal frequency division multiplexing (OFDM) systems | |
US8989312B2 (en) | Apparatus and method for MMSE channel estimation in consideration of offset compensation in wireless communication system | |
Zhang et al. | Multi-service signal multiplexing and isolation for physical-layer network slicing (PNS) | |
US8547833B2 (en) | Systems and methods for determining bitloading | |
US8593992B2 (en) | System and method for throughput enhancement | |
WO2020069646A1 (en) | Computing cyclic prefix length and receiver windowing length using ingress conditions in an ofdm system | |
Das et al. | Design of cyclic prefix characteristic-based OFDM system for WiMAX technology | |
Macit et al. | Performance investigation of IEEE 802.11 af systems under realistic channel conditions | |
Kant et al. | Low-complexity OFDM spectral precoding | |
CN113785499A (en) | Distortion optimized transmission in hybrid fiber coaxial cable networks | |
Rawat et al. | An Overview: OFDM Technology an Emerging Trend in Wireless Communication | |
Homavazir et al. | Enhancement of System Capacity by Implementing Orthogonal Frequency Division Multiplexing (OFDM) in Wireless Digital Communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JIN, HANG;LIU, TONG;SOWINSKI, PAWEL PIOTR;SIGNING DATES FROM 20150409 TO 20150413;REEL/FRAME:035398/0237 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20210523 |