`DOCSIS 1.1
`
`Radio Frequency Interface Specification
`
`CM-SP-RFIv1.1-C01-050907
`
`CLOSED
`SPECIFICATION
`
`Notice
`
`This document is a cooperative effort undertaken at the direction
`of Cable Television Laboratories, Inc. for the benefit of the cable
`industry in general. Neither CableLabs nor any member company
`is responsible for any liability of any nature whatsoever resulting
`from or arising out of use or reliance upon this specification by
`any party. This document is furnished on an “AS IS” basis and
`neither CableLabs nor its members provides any representation
`or warranty, express or
`implied, regarding
`its accuracy,
`completeness, or fitness for a particular purpose.
`
`© Copyright 1999-2005 Cable Television Laboratories, Inc.
`All rights reserved.
`
`Petitioner
`Ex. 1008 - Page 1
`
`
`
`CM-SP-RFIv1.1-C01-050907
`
`Data-Over-Cable Service Interface Specifications
`
`Document Status Sheet
`
`Document Control Number: CM-SP-RFIv1.1-C01-050907
`
`Reference: Radio Frequency Interface Specification
`
`Revision History:
`
`I01 — First Issued Release, March 11, 1999
`I02 — Second Issued Release, July 31, 1999
`I03 — Third Issued Release, November 5, 1999
`I04 — Fourth Issued Release, April 7, 2000
`I05 — Fifth Issued Release, July 14, 2000
`I06 — Sixth Issued Release, December 15, 2000
`I07 — Seventh Issued Release, August 29, 2001
`I08 — Eighth Issued Release, March 1, 2002
`I09 — Ninth Issued Release, August 30, 2002
`I10 — Tenth Issued Release, July 30, 2003
`C01— Closed this specification on September 7, 2005
`Date: September 7, 2005
`
`Status Code: Work in
`Process
`
`Draft
`
`Issued
`
`Closed
`
`Distribution Restrictions: CableLabs
`only
`
`CL
`Reviewers
`
`CL
`Vendor
`
`Public
`
`Key to Document Status Codes
`
`Work in Process An incomplete document, designed to guide discussion and generate feedback,
`that may include several alternative requirements for consideration.
`
`Draft
`
`Issued
`
`Closed
`
`Trademarks:
`
`A document in specification format considered largely complete, but lacking
`review by cable industry and vendors. Drafts are susceptible to substantial
`change during the review process.
`
`A stable document, which has undergone rigorous member and vendor review
`and is suitable for product design and development, cross-vendor interoperability,
`and for certification testing.
`
`A static document, reviewed, tested, validated, and closed to further engineering
`change requests to the specification through CableLabs.
`
`DOCSIS®, eDOCSIS™, PacketCable™, CableHome™, OpenCable™, and CableLabs® are trademarks of Cable
`Television Laboratories, Inc.
`
`ii
`
`Petitioner
`Ex. 1008 - Page 2
`
`
`
`Radio Frequency Interface Specification
`
`CM-SP-RFIv1.1-C01-050907
`
`5 Downstream Transmission Convergence Sublayer
`
`5.1 Introduction
`
`This section applies to the first technology option referred to in Section 1.1(Scope). For the second option, refer
`to Appendix N.
`
`In order to improve demodulation robustness, facilitate common receiving hardware for both video and data, and
`provide an opportunity for the possible future multiplexing of video and data over the PMD sublayer bitstream
`defined in Section 4, a sublayer is interposed between the downstream PMD sublayer and the Data-Over-Cable
`MAC sublayer.
`
`The downstream bitstream is defined as a continuous series of 188-byte MPEG [ITU-T H.222.0] packets. These
`packets consist of a 4-byte header followed by 184 bytes of payload. The header identifies the payload as
`belonging to the Data-Over-Cable MAC. Other values of the header may indicate other payloads. The mixture of
`MAC payloads and those of other services is optional and is controlled by the CMTS.
`
`Figure 5-1 illustrates the interleaving of Data-Over-Cable (DOC) MAC bytes with other digital information
`(digital video in the example shown).
`
`header=DOC
`
`header=video
`
`header=video
`
`header=DOC
`
`header=video
`
`header=DOC
`
`header=video
`
`header=video
`
`header=video
`
`DOC MAC payload
`
`digital video payload
`
`digital video payload
`
`DOC MAC payload
`
`digital video payload
`
`DOC MAC payload
`
`digital video payload
`
`digital video payload
`
`digital video payload
`
`Figure 5-1. Example of Interleaving MPEG Packets in Downstream
`
`5.2 MPEG Packet Format
`
`The format of an MPEG Packet carrying DOCSIS data is shown in Figure 5-2. The packet consists of a 4-byte
`MPEG Header, a pointer_field (not present in all packets) and the DOCSIS Payload.
`
`47
`
`Petitioner
`Ex. 1008 - Page 3
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
