Path:
Home >
GY/T >
Page3 > GY/T 200.2-2004
| Std ID | Version | USD | Buy | Deliver [PDF] in | Title (Description) |
| GY/T 200.2-2004 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Specification for HFC data transmission system Part 2: RF interface and protocol
|
Click to Preview a similar PDF
Basic data
| Standard ID | GY/T 200.2-2004 (GY/T200.2-2004) |
| Description (Translated English) | Specification for HFC data transmission system Part 2: RF interface and protocol |
| Sector / Industry | Radio, Film & TV Industry Standard (Recommended) |
| Classification of Chinese Standard | M63 |
| Word Count Estimation | 259,227 |
| Date of Issue | 2004-03-22 |
| Date of Implementation | 2004-05-01 |
| Quoted Standard | IEC 60728-11; ISO/IEC 10038; ITU-T Z.100; GB 13836-2000; GB/T 11595-1999; GB/T 15629.2-1995; GB/T 15629.3-1995; GB/T 16263-1996; GB/T 16646-1996; GB/T 17975.1-2000; GY/T 106-1999; GY/T 170-2001; GY/T 180-2001; YD/T 1076-2000, |
| Adopted Standard | IYU-T J.112, MOD |
| Summary | This standard specifies the physical layer of a two-way HFC network data transmission systems, data link layer and the network layer protocol. |
GY/T 200.2-2004: Specification for HFC data transmission system Part 2: RF interface and protocol
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Specification for HFC data transmission system Part 2. RF interface and protocol
People's Republic of China Radio, Film and Television Industry Standard
GY
Technical specifications of HFC network data transmission system
Part 2. RF interfaces and protocols
Specification for HFC data transmission system
Part 2. RF interface and protocol
(ITU-T J.112, Transmission Systems for Interactive
Cable Television Services, MOD)
Published on March 22,.2004
2004-05-01 Implementation
Published by the State Administration of Radio, Film and Television
Contents
Foreword ... II
Introduction ... III
1 Scope ... 1
2 Normative references ... 1
3 Terms, definitions and abbreviations ... 1
3.1 Terms and definitions ... 1
3.2 Acronyms ... 7
4 Communication protocol ... 8
4.1 Protocol Stack ... 8
4.2 MAC Forwarder ... 11
4.3 Network Layer ... 13
4.4 Above the network layer ... 14
4.5 Data link layer ... 14
4.6 Physical layer ... 15
5 Physical Media Compliance Sublayer (PMD) Specification ... 15
5.1 Uplink ... 16
5.2 Downstream ... 29
6 Downlink Transmission Convergence Sublayer ... 32
6.1 MPEG packet format ... 32
6.2 MPEG packet header for HFC data transmission ... 33
6.3 MPEG Payload ... 33
6.4 Interaction with the MAC sublayer ... 33
6.5 Interaction with the physical layer ... 34
6.6 MPEG packet header synchronization and recovery ... 34
7 Technical requirements for media access control ... 34
7.1 Introduction ... 34
7.2 MAC frame format ... 36
7.3 MAC Management Messages ... 49
8 Media Access Control Protocol Operation ... 78
8.1 Uplink Bandwidth Allocation ...
8.2 Multi-channel support ...
8.3 Timing and synchronization ...
8.4 Uplink transmission and contention resolution ... 84
8.5 Data link encryption support ... 86
9 Quality of service and segmentation ... 86
9.1 Operation principle ...
9.2 Upstream Service Flow Scheduling Service ...
9.3 Segmentation ...
9.4 Payload header suppression ...
10 CM-CMTS interaction ... 111
10.1 CMTS initialization ... 111
10.2 CM Initialization ...
10.3 Standard operation ...
10.4 Dynamic Services ...
10.5 Failure Detection and Recovery ... 173
11 Ability to support future new CMs ... 174
Appendix A (Normative Appendix) Common Addresses ... 176
Appendix B (Normative) Parameters and Constants ... 178
Appendix C (Normative Appendix) Common RF Interface Coding ... 181
Appendix D (Normative Appendix) CM Configuration Interface Specification ... 212
Appendix E (Informative) MAC Business Definition ... 217
Appendix F (informative) Examples of preamble sequences ... 224
Appendix G (informative) Multiple uplink channels ... 225
Appendix H (Normative Appendix) HFC Data Transmission Spanning Tree Protocol ... 230
Appendix I (Normative) Error Codes and Error Messages ... 233
Appendix J (informative) DOCSIS transmission and contention resolution ... 240
Appendix K (informative) Examples of IGMP ... 245
Appendix L (Informative) Active Authorization Services ... 247
References ... 252
Foreword
GY/T 200 "Technical Specifications for HFC Network Data Transmission System" is divided into the following two parts.
-Part 1. General requirements;
-Part 2. RF interface and protocol.
This part is the second part of GY/T 200.
This section adopts ITU-T J.112 "Transmission Systems for Interactive Cable Television
Services ", mainly adopting Appendix B (Data-over-cable radio frequency interface) of this proposal. This section is related to
The main difference of ITU-T J.112 Appendix B is that the dynamic QoS allocation mechanism has been expanded according to the advanced principles of the standard and China's actual situation.
And payload header suppression technology, delete the related content related to encryption in the original Recommendation, and its related content is separately stipulated in other standards.
Appendix A, Appendix B, Appendix C, Appendix D, Appendix H, and Appendix I of this section are normative appendixes, Appendix E, Appendix F, Appendix G, and Appendix
Record J, Appendix K, and Appendix L are informative appendices.
This section is under the jurisdiction of the National Radio and Television Standardization Technical Committee.
Drafting units of this section. Standardization Planning Research Institute of State Administration of Radio, Film and Television, State Administration of Radio, Film and Television Radio, Film and Television Information
Network Center, Gehua Cable Network Co., Ltd., Qingdao Cable TV Station, Huawei Technologies, Chengdu Kangte Electronic High-tech
Company, Institute of Acoustics, Chinese Academy of Sciences, Shanghai Broadcasting Corporation, Shenzhen Aolong Broadband Technology Co., Ltd., ZTE Corporation
Division, PCCW Hong Kong, Shenzhen Dike Information Technology Company, Guangdong Central Network Company, Skyworth Digital Technology Co., Ltd.
The main drafters of this section. Jin Guojun, Chen Jiaxing, Chen Luoguang, Cheng Weiyao, Li Yixing, Long Yongqing, Luo Xiaohong, Nie Feng, Shi Chi,
Wu Tao, Yang Binhua, Yu Qianru, Zeng Chun, Zeng Qingjun, Zeng Xuewen, and Zhang Chaoyang.
Introduction
From the perspective of the radio frequency interface, this part of the standard specifies compliance with GY/T 106-1999 Technical Specifications for Cable Television Broadcasting Systems.
The physical layer and link layer of the data transmission system on the network with GY/T 180-2001 "Technical Specifications for the Physical Transmission Channels of HFC Networks"
And network layer communication protocols, and detailed descriptions of QoS dynamic allocation mechanism, payload header suppression, and CMTS and CM interoperation.
It maintains ITU-T J.112/EuroDOCSIS 1.1 high-speed data transmission features and QoS extension functions, and is compatible with EuroDOCSIS 1.0.
Technical specifications of HFC network data transmission system
Part 2. RF interfaces and protocols
1 Scope
This section specifies the physical layer, data link layer, and network layer communication protocols for HFC network data bidirectional transmission systems.
This section applies to HFC network data two-way transmission system.
2 Normative references
The clauses in the following documents have become the clauses of this standard after being referenced. For dated references, all subsequent
Neither amendments (excluding errata) or revised versions are applicable to this standard, however, parties who have reached an agreement under this standard are encouraged to study
Is the latest version of these files available? For undated references, the latest version applies to this standard.
GB/T 11595-1999 Packet data terminal equipment (DTE) connected to the public data network with dedicated circuits and data circuit termination
Interface between devices (DCE)
GB 13836-2000 TV and sound signal cable distribution systems-Part 2. Electromagnetic compatibility of equipment
GB/T 15629.2-1995 Information processing system local area network Part 2. Logical link control
GB/T 15629.3-1995 Information processing system local area network Part 3. Carrier Sense Multiple Access with collision detection (CSMA/CD)
Access methods and physical layer specifications
GB/T 16263-1996 Information Processing System Open System Interconnection Abstract Syntax Notation-(ASN.1) Specification of Basic Encoding Rules
GB/T 16646-1996 Information Technology Open System Interconnection Local Area Network Media Access Control (MAC) Service Definition
GB/T 17975.1-2000 Information technology. Universal coding of moving pictures and associated audio information. Part 1. System
GY/T 106-1999 Technical Specification for Cable Television Broadcasting System
GY/T 170-2001 Cable Digital TV Broadcasting Channel Coding and Modulation Specification
GY/T 180-2001 Technical Specifications of Physical Transmission Channels for HFC Networks
YD/T 1076-2000 Access Network Technical Requirements--Cable Modem (CM)
ISO /IEC 10038 Information technology-Telecommunications and information exchange between systems-Local area network-Media access control (MAC) bridge
IEC 60728-11 TV and sound signal cable distribution systems-Part 11 Safety
ITU-T Z.100 Specification and Description Language (SDL)
3 Terms, definitions and abbreviations
3.1 Terms and definitions
The following terms and definitions apply to this section.
3.1.1
Active service flow
Obtain traffic flows from the CM to the CMTS that are available for packet transmission.
3.1.2
Address resolution protocol (ARP)
IETF protocol for network address translation to 48-bit Ethernet address.
3.1.3
Allowed service flow
A preset or dynamically notified service flow. The service flow has been authorized and reserved resources, but has not been activated.
3.1.4
Authorization module
An abstract module that enables the CMTS to contact this module to authorize traffic flows and classifiers. Authorization module notifies CMTS, requesting CM
Whether the requested resource authorization is obtained.
3.1.5
Availability
In cable television systems, availability is based on the assumed bit error rate (BER).
Ratio of time (expressed as a percentage).
3.1.6
Bandwidth allocation map
The CMTS is used to allocate MAC layer management messages to CMs.
3.1.7
Bridge protocol data unit (BPDU)
Spanning tree protocol messages according to ISO /IEC 10038.
3.1.8
Broadcast addresses
Indicate the intended destination address of all data network service access points.
3.1.9
Burst error second
Any error seconds including at least 100 errors.
3.1.10
Cable modem (CM)
User-side modem for data communication on a cable TV system.
3.1.11
Cable modem termination system (CMTS)
It is located at the front end of the cable television system or distribution hub. It provides complementary functions to the CM to establish a data connection with the WAN.
3.1.12
CMTS- network side interface cable modem termination system – network side interface (CMTS-NSI)
Interface between the CMTS and its network-side equipment.
3.1.13
Cable modem to CPE Interface (CMCI)
Interface between CM and CPE.
3.1.14
Classifier
A set of packet matching criteria based on TCP, UDP, IP, LLC, and/or 802.1P/Q packet fields. Classifier takes each number
Packets are mapped to a business flow. CMTS uses downlink classifier to distribute data packets to downstream service flows, CM uses uplink classifier to distribute data packets
Assigned to upstream traffic.
3.1.15
Customer premises equipment (CPE)
Device on the end user side.
3.1.16
Data link layer
In the second layer of the Open System Interconnection (OSI) structure, this layer provides services for transmitting data on the transmission link between open systems.
3.1.17
Distribution hub
Located in the cable television network, it performs front-end functions to local users in the area, and receives the front-end department from the main
Divide or all TV show sources.
3.1.18
Dynamic host configuration protocol (DHCP)
Internet protocol used to assign network layer (IP) addresses.
3.1.19
Dynamic range
The ratio of the maximum signal power to the minimum signal power. Maximum signal power refers to transmission on a multi-channel analog transmission system
Signal power due to distortion and other performance limitations. Minimum signal power refers to those that can be used without exceeding noise, bit error rate, and other performance limits
Signal power.
3.1.20
End user
A person, organization, or communication system that accesses a network for communication through services provided by the network.
3.1.21
Errored second
Any 1-second interval that includes at least one bit error.
3.1.22
Extended subsplit
A frequency division scheme that allows bidirectional transmission of signals over a single coaxial cable. The frequency of the upstream channel signal at the front end is 5MHz
To 65MHz, the frequency of the downlink channel signal at the front end is from 87MHz to the upper limit frequency.
3.1.23
Guard time
The minimum time allocated between bursts in the uplink. Its reference point is from the symbol center of the last symbol of a burst to the next
The symbol center of the first symbol of the burst. The guard time should be at least 5 symbols plus the maximum system timing error.
3.1.24
Frontend
At the heart of the cable television network, it is responsible for sending broadcast television signals and other signals in the downward direction. See also main front end or
Distribution center.
3.1.25
Information element
Domains that constitute a MAP, define individual authorizations, deferred authorizations, and so on.
3.1.26
Interval usage code
A field in MAP and UCD that is used to connect burst characteristics and authorization.
3.1.27
Latency
The time, expressed as the number of symbols, is used to indicate the time that a signal unit passes through a device.
3.1.28
Layer
A subdivision of the Open Systems Interconnection (OSI) structure, consisting of subsystems at the same level.
3.1.29
Logical link control (LLC) procedure
In a local area network or metropolitan area transmission network, a protocol for managing the assembly of data link layer frames and the data exchange between data stations.
It has nothing to do with how the transmission medium is shared.
3.1.30
Master headend
A front end, which collects TV program sources from different sources through satellite, microwave, optical fiber and other means, and divides these program sources into
To the distribution center (Hub) in the same city or region. In its immediate vicinity, a main front end may also perform distribution centers for customers
Functions.
3.1.31
Media address control (MAC) address
The built-in hardware address of a device connected to a shared medium.
3.1.32
Media access control (MAC) procedure
In a subnet, a protocol that manages access to a transmission medium that is independent of the physical characteristics of the medium, but in order to be able to exchange between nodes
Data, you need to consider the topology of the subnet. The MAC process includes framing, error protection, and the right to use the underlying transmission medium.
3.1.33
Media access control (MAC) sublayer
Part of the data link layer, which relies on topology functions and uses physical layer services to provide services to the logical link sublayer.
3.1.34
Mini-slot
A minislot is an integer multiple of 6.25µs increments. The relationship between mini-slots, bytes and time ticks is described in 8.3.4.
3.1.35
Multipoint access
A single network terminal supports user access from more than one terminal device.
3.1.36
Multipoint connection
A connection between two or more data network terminals.
3.1.37
Network layer
The third layer of the Open Systems Interconnection (OSI) structure provides services for establishing channels between open systems.
3.1.38
Network management
Functions related to the management of data link layer and physical layer resources and their stations on the data network supported by the HFC system.
3.1.39
Organizationally unique identifier (OUI)
Is an identifier of three 8-bit groups assigned by the IEEE. According to IEEE 802, a universal LAN MAC address and protocol identifier are generated to
For use in LAN and MAN applications.
3.1.40
Packet identifier (PID)
A unique integer value identifying the elementary stream of a program in the MPEG-2 stream of a single or multiple programs.
3.1.41
Partial grant
An authorization with less bandwidth than the CM requests.
3.1.42
Payload header suppression (PHS)
Header suppression in payload packets (for example, Ethernet header suppression in forwarded packets).
3.1.43
Payload unit start indicator (PUSI)
A flag in the MPEG header. A value of 1 indicates that the pointer field exists and is the first byte of the payload.
3.1.44
Physical (PHY) layer
The first layer of the Open Systems Interconnection (OSI) structure. This layer provides services on transmission links between open systems to transfer bits or
Bit groups, and this layer specifies the various electrical, mechanical, and handshake processes in detail.
3.1.45
Physical media dependent (PMD) sublayer
A sublayer of the physical layer, which involves the transmission of bits or groups of bits over specific transmission links between open systems, and this layer specifies the
Various electrical, mechanical, and handshake processes are defined.
3.1.46
Primary service flow
All CMs have a basic uplink service flow and a basic downlink service flow. They ensure that the CM is always manageable and
Forwarded packets that are not classified into any other service flow provide a default channel.
3.1.47
Provisioned service flow
A service flow has been preset as part of the registration process, but has not yet been activated or allowed. Before allowing it, it may
Can still need to exchange authorization with a policy module or external policy server.
3.1.48
QoS parameter set
A set of service flow codes describing the quality of service attributes of a service flow or a service category, see Appendix C.2.2.5.
3.1.49
Routing information protocol (RIP)
An IETF protocol is used to exchange routing information between IP networks and subnets.
3.1.50
Service access point (SAP)
The location of a point that provides services from a layer or sublayer to the immediately preceding layer.
3.1.51
Security association identifier
An encrypted security identifier between the CMTS and the CM
3.1.52
Service class
A set of queuing and scheduling attributes named and configured in the CMTS. Business categories are identified by business category names. One business category has
Related QoS parameter set.
3.1.53
Service class name
An ASCII string that references the business category in the CM configuration file and protocol exchange.
3.1.54
Service data unit (SDU)
Information transmitted as a unit between peer-to-peer service access points.
3.1.55
Service flow
A MAC layer transmission service.
• Provide one-way data packet transmission from upper-level business entities to RF;
• Shaping, policing, and prioritizing traffic based on the QoS traffic parameters defined for the service flow.
3.1.56
Service flow identifier (SFID)
The identifier assigned to the service flow by the CMTS. The length is 32 bits.
3.1.57
Service identifier (SID)
Assigned by the CMTS to an activated or permitted uplink service flow, a service flow identifier other than the service flow identifier (SFID), long
The degree is 14 bits.
3.1.58
Service flow reference
A message parameter in the configuration file and dynamic service MAC message, used to classify the classifier and other objects in the message with the requested service
The business flow coding of the business flow is linked.
3.1.59
Sublayer
Subdivision of a layer in the Open Systems Interconnection (OSI) reference model.
3.1.60
Subnetwork
It is the physical connection of adjacent nodes and transmission links.
3.1.61
Subnetwork access protocol (SNAP)
An extension of the LLC packet header so that 802-type networks can be used as IP networks.
3.1.62
Time tick
The 6.25µs time interval is used as a reference for the definition of the uplink microslot and the uplink transmission time.
3.1.63
Transit delay
The time difference between the first bit of a PDU passing a specified boundary and the last bit of the same PDU passing a second specified boundary.
3.1.64
Transmission convergence sublayer
A sublayer of the physical layer that provides the interface between the data link layer and the PMD sublayer.
3.1.65
Trivial file-transfer protocol (TFTP)
An Internet protocol used to transfer files without a username and password. Usually used for automatic data and software downloads.
3.1.66
Type/length/value (TLV)
A three-field encoding, where the first field refers to the type of information unit, the second field refers to the length of the information unit, and the third field refers to the information
The value of the interest unit.
3.1.67
Upstream channel descriptor (UCD)
The MAC management message is used to transmit the characteristic parameters of the uplink physical layer to the CM.
3.2 Acronyms
The following abbreviations apply to this section.
ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
BPDU Bridge Protocol Data Unit
CBR Constant Bit Rate
CCCM CPE controlled CM
CM Cable Modem
CMCI Cable Modem to CPE Interface
CMTS Cable Modem Termination System
CMTS-NSI Cable Modem Termination System-Network Side Interface
CNT Concatenation
CPE Customer Premises Equipment
CSO Composite Second Order Beat
CTB Composite Triple Beat
DHCP Dynamic Host Configuration Protocol
EHDR Extended Header
ELEN Extended Header length
FC Frame Control
FDDI Fiber Distributed Data Interface
HCS Header Check Sequence
ICMPInternet Control Message Protocol
IE Information Element
IEEE Institute of Electrical and Electronic Engineers
IETF Internet Engineering Task Force
IGMP Internet Group Management Protocol
IUC Interval Usage Code
LLC Logical Link Control Procedure
MAC Media Access Control
MSAP MAC Service Access Point
OSI Open System Interconnection
OUI Organizationally Unique Identifier
PDU Packeted Data Unit
PHS Payload Header Suppression
PHSF Payload Header Suppression Field
PHSI Payload Header Suppression Index
PHY Physical Layer
PID Packet Identifier
PMD Physical Media Dependent Sublayer
PUSI Payload Unit Start Indicator
REQ Request
RFI Radio Frequency Interface
SAID Security Association Identifier
SAP Service Access Point
SFID Service Flow Identifier
SID Service Identifier
SNAP Subnetwork Access Protocol
SNMP Simple Network Management Protocol
TFTP Trivial File-Transfer Protocol
TLV Type/Length/Value
UCC Upstream Channel Change
UCD Upstream Channel Descriptor
UDP User Datagram Protocol
XIDExchang Identification command
4 Communication protocol
This chapter briefly introduces the high-level communication protocols that should be used in HFC network data transmission systems. Related to physical media, downlink transmission and media
The detailed technical requirements of the access control sub-layer are explained in Chapter 5, Chapter 6, and Chapter 7, respectively.
4.1 protocol stack
CM and CMTS can operate as a forwarding agent or as an end system (host). Protocol stack used by different operating modes
A little different.
The main function of a cable modem system is to transparently transmit IP packets between the front end and the user end. The IP protocol also contains a certain
Some management functions. The protocol stack on the HFC network is shown in Figure 1.
4.1.1 CM and CMTS as Hosts
The CM and CMTS will operate as IP and LLC hosts in accordance with IEEE 802 and communicate over the HFC network. On CM and CMTS RF interfaces
The protocol stack is shown in Figure 1.
CM and CMTS should work as IP hosts. In this way, the CM and CMTS should support IP and ARP over DIX link layer framing (see DIX). CMTS
Frames smaller than the 64-byte minimum DIX should not be transmitted in the downlink channel. However, the CM can transmit less than the DIX minimum 64 in the uplink channel
Byte frame.
The CM and CMTS can also support IP and ARP over SNAP framing (see RFC-1042).
The CM and CMTS should also work as LLC hosts. Therefore, CM and CMTS should respond to TEST and XID requests appropriately in accordance with GB/T 15629.2.
begging.
Figure 1 Protocol stack on the RF interface
4.1.2 Data Forwarding via CM and CMTS
4.1.2.1 Overview
Data forwarding through the CMTS can be a transparent bridge method, or a network layer forwarding method (routing, IP switching) can also be used.
as shown in picture 2.
The data forwarding through the CM is a link layer transparent bridge method as shown in FIG. 2. Transmission rules are similar to the modified ISO /IEC 10038,
The modified content is introduced in 4.1.2.2 and 4.1.2.3. This allows support for multiple network layers.
Figure 2 Example of data forwarding through CM and CMTS
The CM and CMTS shall support the forwarding of IP services, and may also support other network layer protocols. Should have the ability to limit the network layer to a single protocol
(Eg IP).
The CM for residential areas can support the modified ISO /IEC 10038 802.1d spanning tree protocol as described in Appendix H. For business
The destination CM should support this version of spanning tree. The CM and CMTS shall have the ability to filter (and ignore) 802.1d BPDUs.
This section assumes that CMs used in residential areas will not be connected into a network loop structure as shown in Figure 3.
Figure 3 Example Network Loop
4.1.2.2 CMTS forwarding rules
In CMTS, if link-layer forwarding is used, it should follow the general 802.1d rul...
...
