US8155002B2 - Method for automatically inflating the receive window size in TCP connections - Google Patents
Method for automatically inflating the receive window size in TCP connections Download PDFInfo
- Publication number
- US8155002B2 US8155002B2 US11/859,574 US85957407A US8155002B2 US 8155002 B2 US8155002 B2 US 8155002B2 US 85957407 A US85957407 A US 85957407A US 8155002 B2 US8155002 B2 US 8155002B2
- Authority
- US
- United States
- Prior art keywords
- tcp
- segment
- value
- receive window
- altered
- 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.)
- Expired - Fee Related, expires
Links
- 238000000034 method Methods 0.000 title claims description 40
- 230000005540 biological transmission Effects 0.000 claims description 9
- 230000001105 regulatory effect Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 claims 4
- 230000004075 alteration Effects 0.000 claims 3
- 238000004891 communication Methods 0.000 description 16
- 239000000872 buffer Substances 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000013341 scale-up Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- 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
-
- 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
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
Definitions
- This invention relates, generally, to communication networks and, more particularly, to automatically increasing the size of a receive window over a TCP connection.
- the bandwidth utilized by a TCP session is primarily regulated by the TCP protocol itself.
- the protocol employs a number of techniques to self-limit the bandwidth it consumes, one of which is Window Size Advertisements.
- the sending host includes the current size of its Receive Window in bytes. This value reflects the number of bytes available at the host to store incoming session data.
- the TCP peer at the other end of the connection is responsible for limiting the amount of data it transmits such that the total number of unacknowledged bytes in transit is less than or equal to this advertised Receive Window. This mechanism is intended to guarantee that a transmitting host never overflows the receive buffers of its peer.
- the Receive Window field in the TCP header is 16 bits wide allowing for a maximum advertised Receive Window size of 64K.
- a host may include a Window Scale Option in the initial “SYN” packet sent during session initiation to “scale up” all advertised Receive Window values.
- LFPs long fat pipes
- TCP connections Consumer broadband connections are usually long fat pipes (LFPs)—high bandwidth TCP connections.
- LFPs which may comprise multiple channels ‘bonded’ together to carry program information for a single stream, typically have with large round-tip delays.
- LFPs a host's advertised Receive Window often unnecessarily limits the overall session bandwidth.
- a transmitting host Once a connection is established over an LFP, a transmitting host will typically source a Receive Window's worth of data into the network and halt transmission while the data propagates through the LFP to the receiver. The transmitter will not resume transmission until a TCP ACK containing a new Receive Window advertisement is received from its peer. This on-again, off-again behavior at the transmitter severely reduces overall session throughput.
- One remedy for poor LFP performance is to use the Window Scale Option at the receiving host to advertise a larger Receive Window to the transmitter.
- the increase in advertised Receive Window size accounts for the in-flight data propagating over the LFP and allows the transmitter to source more data into the network before halting transmission.
- the resulting reduction in the transmitters “off time” increases the connection throughput.
- Two examples of methods that facilitate automatic adjustment at a network device of the receive window for a receiving device include a) modifying a SYN packet and b) modifying every TCP packet.
- An edge router/switch may intercept “SYN” packets sent from a subscriber during TCP connection establishment and add or adjust the Window Scale Option before forwarding the SYN packets on to their destinations.
- the value of the added/adjusted Window Scale Option can be tuned to account for the propagation delay of the LFP between the subscriber and the far host.
- an edge router may intercept every TCP packet sent from a subscriber and increase the Receive Window in the TCP header to account for the propagation delay of the LFP between the subscriber and the far host.
- the Receive Window increment can be tuned to account for the propagation delay of the LFP between the subscriber and the far host.
- a method for adjusting the receive window size (SEG.WND) value in a TCP segment would perform the steps of intercepting on an intermediate network element (e.g., a router) a TCP segment that was originally transmitted from a TCP client and is destined to a TCP server. The method would determine whether the receive window size value in the intercepted TCP segment is less than a predetermined value and would alter the receive window size value in the intercepted TCP segment according to a predetermined formula to create an altered TCP segment. Then, the method would correct any required checksums associated with the altered TCP segment to account for the altered received window size value to create a corrected TCP segment and forward it on toward the TCP server.
- an intermediate network element e.g., a router
- a method for adjusting the extended receive window size value in a TCP segment would perform the steps of intercepting on an intermediate network element (e.g., a router) a TCP segment that was originally transmitted from a TCP client and is destined to a TCP server.
- the method would determine whether the intercepted TCP segment is a SYN segment (typically a SYN bit is set) that can support the TCP Window Scaling Option (the SYN segment has a 3-byte Window Scaling Option field). If so, the method would alter the Window Scaling Option value in die intercepted TCP SYN segment with support for the Window Scaling Option according to a predetermined formula to create an altered TCP SYN segment with support for the Window Scaling Option.
- an intermediate network element e.g., a router
- the method would then typically correct checksums associated with the altered TCP SYN segment with support for the Window Scaling Option to account for the altered Window Scaling Option value to create a corrected TCP SYN segment with support for the Window Scaling Option.
- the method would then forward the altered and corrected TCP SYN segment with support for the Window Scaling Option on toward the TCP server.
- FIG. 1 illustrates a communication system for altering communication segments at an intermediate communication device.
- FIG. 2 illustrates a flow chart for a method for adjusting a receive window value by modifying a SYN packet.
- FIG. 3 illustrates a flow chart for a method for adjusting a receive window value by modifying a TCP packets.
- FIG. 1 illustrates a communication system 2 for altering communication segments at an intermediate communication device.
- a client device 4 communicates over a communication network 6 , such as a hybrid fiber coaxial cable (“HFC”) network, with a server device 8 .
- Communications between client 4 and server 8 typically are processed by a centrally located intermediate network element, or device, 10 , such as a router, a CMTS, a switch, or other device that processes and directs network traffic.
- client 4 may refer to a consumer's home personal computer (“PC”) and server 8 may refer to a web site operator's web server.
- PC personal computer
- client 4 or server 8 can be coupled to element 10 via network 6 as shown, or may be coupled to the intermediate network element from another network connection, such as an Ethernet connection to the internet or a connection to a public switched telephony network.
- Server 8 and client 4 communication may communication using internet protocol (“IP”) and related protocols, such as transmission control protocol (“TCP”), which is a core protocol of the internet protocol suite, as known in the alt.
- IP internet protocol
- TCP transmission control protocol
- Communication information and data is typically carried in packets, or segments, from one user device to another user device.
- a user device requesting information is typically referred to as a client and the device that the information is requested of is typically referred to as a server.
- client device 4 initiates a TCP session and sends a synchronization segment 12 A, or SYN segment, toward server 8 .
- SYN segment 12 A may include a SYN bit 14 , that is set (set is represented in the figure as a value of ‘1’) to indicate to another network device that it is indeed a SYN segment.
- SYN segment 12 A may also include a receive window scaling option field 16 .
- the receive window scale option field 16 is typically a three-byte field in segment 12 A and not only provides a window scale value, but also indicates that the TCP sending device, in this case client 4 , is prepared and ready to perform receive window scaling in both the send and receive directions.
- CMTS intermediate network device 10
- item 10 may also refers to other types of centrally located network devices that couple the client and server.
- CMTS 10 evaluates the segment to determine whether it is a SYN segment and if so, whether it indicates that receive window scaling is enabled at client 4 . If the result of both evaluations is true, then the CMTS inserts a value retrieved from a memory 18 at the CMTS that stores a scaling value.
- the value retrieved from memory 18 and inserted into the SYN segment replaces the receive window size value stored in portion 16 of segment 12 A.
- the result of the replacement is that the altered SYN segment, now shown as segment 12 B, includes the original SYN bit set in portion 14 , but field 16 now contains a ‘4’ rather than ‘1’ as was in SYN segment 12 A sent from client 4 .
- the SYN segment structure is depicted in the figure for clarity and simplicity of illustration, and may not be representative of the structure of an actual segment. Indeed, a typical TCP segment, including a SYN segment, would have SYN bit portion 14 , and receive window size value portion 16 at the beginning bytes that precede a segment's payload.
- the receive window size scale value from portion 14 is stored to memory 20 .
- the value stored as value 22 is then used to scale all receive window size values in TCP segments received subsequent to receiving SYN segment 12 B.
- FIG. 1 depicts CMTS 18 altering a TCP segment sent from client 4 when the CMTS intercepts the segment before forwarding it to the destination server 8 .
- a typical non-SYN TCP packet 22 A contains a receive window value in a predetermined sixteen-bit receive window value portion 24 .
- This receive window value is typically based on the current capacity of a receive buffer at client 4 when the client sends TCP packet 22 A, or segment. In the example shown in the figure, the current capacity of the buffer at server 4 can support receiving 30K bytes of data.
- the receive window size value can be artificially increased at the CMTS. This provides the advantage that server 8 will send more segments back to client 4 that the receive window value in portion 24 indicates, thus making efficient use of the buffer's increased capacity that will be available when the return segments are received at the client. It will be appreciated that typically after network element 10 alters a segment, or packet, it connects checksums associated with the altered segment.
- the figure depicts TCP segment 22 A as sent from client 4 with a receive window size value of 30K, but after being intercepted at CMTS 10 , the CMTS replaces the value in portion 24 with a value determined according to a predetermined formula if the value in segment 22 A is less than a predetermined amount.
- the predetermined value is 64 Kbytes (the maximum that can be represented by the sixteen-bit portion 24 )
- CMTS 10 replaces the value in portion 24 of segment 22 A with a binary value representing 64K
- altered segment 22 B is the result, having a value of 64K in its portion 24 .
- server 8 will always send a minimum number of segments at each transmission during the session.
- the predetermined value and predetermined formula may be stored on memory 18 along with the receive window scale factor value discussed above.
- the receive window scales factor value aspect and the replacing of the receive window size value aspect may both be used to increase the number and size of TCP segments sent from server 8 to client 4 .
- the scale factor is 4, as discussed above and the receive window value is changed from 30K to 64K bytes, then server 8 would receive segment 22 B and scale it by the scale factor stored at memory 20 .
- CMTS 10 altered the SYN segment and subsequent TCP segment so that server 8 will send segments totaling 1 megabyte to client 4 after receiving altered segment 22 B.
- the second aspect of altering the value in the portion 24 of a TCP segment with the scaling aspect prevents a no-send situation which would occur if the value in the receive window size value was zero in the TCP segment (scaling zero results in zero).
- network element 10 typically after network element 10 alters a segment, or packet, it corrects checksums associated with the altered segment.
- FIG. 2 the figure illustrates a flow diagram of a method 200 for adjusting a scalable receive window size value for regulating transmission of TCP segments.
- Method 210 starts at step 205 .
- a TCP client begins setting up a TCP session with a TCP server.
- the TCP client may be, for example, a personal computer coupled to a network device, such as a cable modem, DSL modem, dial up modem, network interfaced card, etc.
- the TCP server may be, for example, a web server hosting a web site, a video program server, a media gateway, or other communication device.
- the client generates a SYN message that is sent to the server as know in the art related to TCP networking, as detailed in RFC-1323, for example, which is incorporated herein by reference in its entirety.
- the SYN message, or segment, as referred to in RFC-1323 (segments may also be commonly referred to as packets) is sent from the TCP client to the TCP server.
- the TCP client may be coupled to a communication device that interfaces with a communication network, such as, for example, a cable network, a DSL network, a telephony network or a local area network, in the case of the network device being a cable modem, a DSL modem, a dial up modem or a network interface card, respectively.
- a communication network such as, for example, a cable network, a DSL network, a telephony network or a local area network, in the case of the network device being a cable modem, a DSL modem, a dial up modem or a network interface card, respectively.
- the network devices typically couple to a central device, such as, for example, a cable modem termination system (“CMTS”) in a cable network, which is sometimes referred to as a hybrid fiber coaxial (“HFC”) network.
- CMTS cable modem termination system
- HFC hybrid fiber coaxial
- the CMTS receives, or intercepts, the SYN segment.
- a determination is made at step 217 whether the intercepted segment is a SYN segment by evaluating whether a SYN bit position/SYN flag within the SYN segment is set. If the determination at step 217 is that the segment is not a SYN segment, then method 210 ends at step 240 .
- the TCP server receives the SYN segment, extracts the scale factor value from the SYN segment and stores the scale factor value to a memory at the server.
- the memory could be any memory known to those skilled in the alt, including RAM, hard drive, flash memory, etc.
- a receive window value as known in the art and as described in RFC 1323, is evaluated. Although described in RFC-1323, briefly, a receive window size value is used to inform a server how much memory capacity a client has to receive segments. According to the TCP protocol, the largest value that the sixteen-bit receive window value corresponds to is 64K bytes.
- the scale factor is applied to the receive window size value at step 230 .
- Method 200 ends at step 240 .
- FIG. 3 a flow diagram illustrates a method 300 for adjusting the size of the receive window value at an intermediate network device.
- Method 300 starts at step 305 .
- an intermediate network element/device intercepts a TCP segment at step 310 from a TCP client.
- the segment is evaluated at step 320 and a determination is made whether the receive window size value—referred to in RFC-1323 as receive window size (SEG.WND) value—in the TCP segment is less than a predetermined number.
- the predetermined number is preferably 64K bytes, but can be another value as chosen by the operator of the intermediate network device. If the value of the receive window size is not less that the predetermined number, then method 300 forwards the segment to the TCP server at step 340 .
- the intermediate network device adjusts the receive window size value in the TCP packet according to a predetermined formula.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (13)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/859,574 US8155002B2 (en) | 2006-09-21 | 2007-09-21 | Method for automatically inflating the receive window size in TCP connections |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US84639006P | 2006-09-21 | 2006-09-21 | |
US11/859,574 US8155002B2 (en) | 2006-09-21 | 2007-09-21 | Method for automatically inflating the receive window size in TCP connections |
Publications (2)
Publication Number | Publication Date |
---|---|
US20080075000A1 US20080075000A1 (en) | 2008-03-27 |
US8155002B2 true US8155002B2 (en) | 2012-04-10 |
Family
ID=39224803
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/859,574 Expired - Fee Related US8155002B2 (en) | 2006-09-21 | 2007-09-21 | Method for automatically inflating the receive window size in TCP connections |
Country Status (1)
Country | Link |
---|---|
US (1) | US8155002B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8433808B1 (en) * | 2011-02-01 | 2013-04-30 | Juniper Networks, Inc. | Learning values of transmission control protocol (TCP) options |
US8619558B1 (en) * | 2008-07-21 | 2013-12-31 | Qlogic, Corporation | Memory management in a network adapter |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7406527B2 (en) * | 2001-11-02 | 2008-07-29 | Microsoft Corporation | Method for advance negotiation of computer settings |
US20080273547A1 (en) * | 2007-05-01 | 2008-11-06 | Honeywell International, Inc. | Apparatus and method for acknowledging successful transmissions in a wireless communication system |
US7933240B2 (en) * | 2007-07-19 | 2011-04-26 | Honeywell International Inc. | Apparatus and method for redundant connectivity and multi-channel operation of wireless devices |
US8681676B2 (en) * | 2007-10-30 | 2014-03-25 | Honeywell International Inc. | System and method for providing simultaneous connectivity between devices in an industrial control and automation or other system |
DE102008018937A1 (en) * | 2008-04-15 | 2009-10-29 | Siemens Aktiengesellschaft | Device and method for transporting objects over intersecting transport paths |
US7817631B1 (en) * | 2008-07-09 | 2010-10-19 | Google Inc. | Network transfer protocol |
US8964543B1 (en) | 2010-02-16 | 2015-02-24 | Google Inc. | System and method of reducing latency by transmitting duplicate packets over a network |
US8325623B1 (en) | 2010-02-16 | 2012-12-04 | Google Inc. | System and method for reducing latency during data transmissions over a network |
US8730799B2 (en) * | 2010-03-03 | 2014-05-20 | Akamai Technologies, Inc. | Dynamic adjustment of receive window utilized by a transmitting device |
US8468196B1 (en) | 2010-05-20 | 2013-06-18 | Google Inc. | System and method of reducing latency using adaptive retransmission timeouts |
US8239532B1 (en) | 2010-06-24 | 2012-08-07 | Google Inc. | System and method of reducing latency using adaptive DNS resolution |
US8576711B1 (en) | 2010-09-28 | 2013-11-05 | Google Inc. | System and method for reducing latency via client side dynamic acknowledgements |
US9100236B1 (en) * | 2012-09-30 | 2015-08-04 | Juniper Networks, Inc. | TCP proxying of network sessions mid-flow |
WO2014130807A1 (en) * | 2013-02-21 | 2014-08-28 | Fastly Inc. | Dynamic secure packet block sizing |
US9609524B2 (en) | 2014-05-30 | 2017-03-28 | Honeywell International Inc. | Apparatus and method for planning and validating a wireless network |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020136231A1 (en) * | 2001-03-12 | 2002-09-26 | Leatherbury Ryan M. | Time division multiple access over broadband modulation method and apparatus |
US20030128711A1 (en) * | 2001-09-26 | 2003-07-10 | Gabriel Olariu | Method and system for improvement of network performance over asymmetic links |
US20060248582A1 (en) * | 2005-04-28 | 2006-11-02 | Panjwani Dileep K | One-way proxy system |
US7500010B2 (en) * | 2005-04-07 | 2009-03-03 | Jeffrey Paul Harrang | Adaptive file delivery system and method |
-
2007
- 2007-09-21 US US11/859,574 patent/US8155002B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020136231A1 (en) * | 2001-03-12 | 2002-09-26 | Leatherbury Ryan M. | Time division multiple access over broadband modulation method and apparatus |
US20030128711A1 (en) * | 2001-09-26 | 2003-07-10 | Gabriel Olariu | Method and system for improvement of network performance over asymmetic links |
US7500010B2 (en) * | 2005-04-07 | 2009-03-03 | Jeffrey Paul Harrang | Adaptive file delivery system and method |
US20060248582A1 (en) * | 2005-04-28 | 2006-11-02 | Panjwani Dileep K | One-way proxy system |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8619558B1 (en) * | 2008-07-21 | 2013-12-31 | Qlogic, Corporation | Memory management in a network adapter |
US8433808B1 (en) * | 2011-02-01 | 2013-04-30 | Juniper Networks, Inc. | Learning values of transmission control protocol (TCP) options |
US9356989B2 (en) | 2011-02-01 | 2016-05-31 | Juniper Networks, Inc. | Learning values of transmission control protocol (TCP) options |
Also Published As
Publication number | Publication date |
---|---|
US20080075000A1 (en) | 2008-03-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8155002B2 (en) | Method for automatically inflating the receive window size in TCP connections | |
CA2316884C (en) | Apparatus and method for optimizing congestion control information in a multi-protocol network | |
US6304578B1 (en) | Packet routing and queuing at the headend of shared data channel | |
EP1538796B1 (en) | Priming data packet for avoiding transmission delay | |
US8010668B1 (en) | Selective compression for network connections | |
US7042907B2 (en) | Packet transfer apparatus and method | |
EP1771742B1 (en) | High performance tcp for systems with infrequent ack | |
EP3780542B1 (en) | Data transmission method and device | |
US20080056256A1 (en) | Client-server emulation supporting multicast transmissions of media objects | |
US20100005178A1 (en) | Method and system for firewall friendly real-time communication | |
JP5807710B2 (en) | Content distribution system, content distribution method and program | |
WO2016095568A1 (en) | Data transmission method and apparatus | |
US20040017773A1 (en) | Method and system for controlling the rate of transmission for data packets over a computer network | |
WO2012116541A1 (en) | Method for inserting and unloading tcp proxy and service gateway device | |
EP1668870A1 (en) | System, method and computer program product for increasing throughput in bi-directional communications | |
JP2004520725A (en) | Internet via satellite | |
US9986010B2 (en) | System and method for controlling video and/or audio streams in a web browser | |
KR102450226B1 (en) | Method and apparatus for controlling send buffer of transport control protocol in communication system | |
US20040100979A1 (en) | Protocol performance using ACK filtering | |
US7986694B2 (en) | Method for fragmenting an incoming packet into a first outgoing packet and a second outgoing packet | |
US6195348B1 (en) | Dynamic realtime protocol for facsimile and the like | |
US20080304437A1 (en) | TCP Start Protocol For High-Latency Networks | |
US20070153828A1 (en) | System and method to negotiate the addition or deletion of a PPP link without data loss | |
Kumar et al. | Modified TCP for time critical applications | |
Lee et al. | TCP-SuperCharger: A New Approach to High-Throughput Satellite Data Transfer |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ARRIS GROUP, INC., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROBBINS, MAX LEO;REEL/FRAME:020006/0238 Effective date: 20071009 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: ARRIS ENTERPRISES, INC., GEORGIA Free format text: MERGER;ASSIGNOR:ARRIS GROUP, INC.;REEL/FRAME:030223/0244 Effective date: 20130416 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, IL Free format text: SECURITY AGREEMENT;ASSIGNORS:ARRIS GROUP, INC.;ARRIS ENTERPRISES, INC.;ARRIS SOLUTIONS, INC.;AND OTHERS;REEL/FRAME:030498/0023 Effective date: 20130417 Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY AGREEMENT;ASSIGNORS:ARRIS GROUP, INC.;ARRIS ENTERPRISES, INC.;ARRIS SOLUTIONS, INC.;AND OTHERS;REEL/FRAME:030498/0023 Effective date: 20130417 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: ARRIS ENTERPRISES LLC, PENNSYLVANIA Free format text: CHANGE OF NAME;ASSIGNOR:ARRIS ENTERPRISES INC;REEL/FRAME:041995/0031 Effective date: 20151231 |
|
AS | Assignment |
Owner name: AEROCAST, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: NETOPIA, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: POWER GUARD, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: MODULUS VIDEO, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ARRIS SOLUTIONS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ARRIS HOLDINGS CORP. OF ILLINOIS, INC., PENNSYLVAN Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ACADIA AIC, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GENERAL INSTRUMENT CORPORATION, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: QUANTUM BRIDGE COMMUNICATIONS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ARRIS ENTERPRISES, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GIC INTERNATIONAL CAPITAL LLC, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: BIG BAND NETWORKS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: LEAPSTONE SYSTEMS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: IMEDIA CORPORATION, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: THE GI REALTY TRUST 1996, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: MOTOROLA WIRELINE NETWORKS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: 4HOME, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: SUNUP DESIGN SYSTEMS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GENERAL INSTRUMENT AUTHORIZATION SERVICES, INC., P Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: UCENTRIC SYSTEMS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: SETJAM, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GIC INTERNATIONAL HOLDCO LLC, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: TEXSCAN CORPORATION, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: NEXTLEVEL SYSTEMS (PUERTO RICO), INC., PENNSYLVANI Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GENERAL INSTRUMENT INTERNATIONAL HOLDINGS, INC., P Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: BROADBUS TECHNOLOGIES, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ARRIS KOREA, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: JERROLD DC RADIO, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: CCE SOFTWARE LLC, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ARRIS GROUP, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GENERAL INSTRUMENT AUTHORIZATION SERVICES, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: GENERAL INSTRUMENT INTERNATIONAL HOLDINGS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: NEXTLEVEL SYSTEMS (PUERTO RICO), INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 Owner name: ARRIS HOLDINGS CORP. OF ILLINOIS, INC., PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048825/0294 Effective date: 20190404 |
|
AS | Assignment |
Owner name: ARRIS ENTERPRISES LLC, GEORGIA Free format text: CHANGE OF NAME;ASSIGNOR:ARRIS ENTERPRISES, INC.;REEL/FRAME:049586/0470 Effective date: 20151231 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATE Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:ARRIS ENTERPRISES LLC;REEL/FRAME:049820/0495 Effective date: 20190404 Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: TERM LOAN SECURITY AGREEMENT;ASSIGNORS:COMMSCOPE, INC. OF NORTH CAROLINA;COMMSCOPE TECHNOLOGIES LLC;ARRIS ENTERPRISES LLC;AND OTHERS;REEL/FRAME:049905/0504 Effective date: 20190404 Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: ABL SECURITY AGREEMENT;ASSIGNORS:COMMSCOPE, INC. OF NORTH CAROLINA;COMMSCOPE TECHNOLOGIES LLC;ARRIS ENTERPRISES LLC;AND OTHERS;REEL/FRAME:049892/0396 Effective date: 20190404 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CONNECTICUT Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:ARRIS ENTERPRISES LLC;REEL/FRAME:049820/0495 Effective date: 20190404 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, DELAWARE Free format text: SECURITY INTEREST;ASSIGNORS:ARRIS SOLUTIONS, INC.;ARRIS ENTERPRISES LLC;COMMSCOPE TECHNOLOGIES LLC;AND OTHERS;REEL/FRAME:060752/0001 Effective date: 20211115 |
|
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 |