idnits 2.17.1 draft-ahmed-csmimib-mib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 72 longer pages, the longest (page 32) being 96 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 73 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 13. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 471 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [MHz], [13], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1146 has weird spacing: '...product pro...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'MHz' on line 726 looks like a reference -- Missing reference section? '11' on line 3352 looks like a reference -- Missing reference section? '1' on line 3293 looks like a reference -- Missing reference section? '2' on line 3299 looks like a reference -- Missing reference section? '3' on line 3304 looks like a reference -- Missing reference section? '4' on line 3310 looks like a reference -- Missing reference section? '5' on line 3316 looks like a reference -- Missing reference section? '6' on line 3322 looks like a reference -- Missing reference section? '7' on line 3327 looks like a reference -- Missing reference section? '8' on line 3333 looks like a reference -- Missing reference section? '9' on line 3342 looks like a reference -- Missing reference section? '10' on line 3347 looks like a reference -- Missing reference section? '12' on line 3355 looks like a reference -- Missing reference section? '13' on line 3360 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 4 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT 2 Expire in six months 4 Common Spectrum Management Interface MIB June 13,1996 6 Definitions of Managed Objects 7 for HFC RF Spectrum Management 9 June 13,1996 11 draft-ahmed-csmimib-mib-00.txt 13 Masuma Ahmed 14 mxa@cablelabs.com 15 Mario P. Vecchi 16 mario.vecchi@twcable.com 18 1. Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are 20 working documents of the Internet Engineering Task Force 21 (IETF), its areas, and its working groups. Note that other 22 groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of 26 six months and may be updated, replaced, or obsoleted by 27 other documents at any time. It is inappropriate to use 28 Internet-Drafts as reference material or to cite them other 29 than as "work in progress." 31 To learn the current status of any Internet-Draft, please 32 check the "lid-abstracts.txt" listing contained in the 33 Internet-Drafts Shadow Directories on ds.internic.net 34 (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US 35 West Coast), or munnari.oz.au (Pacific Rim). 37 2. Abstract 39 This document was issued by Time Warner Cable to the 40 industry on December 24, 1995 as a private extension 41 to the SNMPv1 MIB. As issued by Time Warner, this 42 memo defined a private portion of 43 the Management Information Base (MIB) for use 44 with network management protocols 45 in the Internet community. It described objects used 46 for managing Radio Frequency (RF) spectrum and the 47 related configuration parameters allocated to 48 different vendors' products in Hybrid Fiber Coax (HFC) 49 networks. 51 This document is submitted as it is for information 52 purposes only and the authors plan to update the 53 document consistent with the guidelines and structure 54 of the Internet Drafts as specified in RFC 1543. 55 The authors also plan to specify this MIB module 56 in a manner that is both compliant to the SNMPv2 57 SMI, and semantically identical to the existing 58 SNMPv1-based definitions. 60 This memo does not specify a standard for the Internet 61 community. It is presented for discussion purposes 62 only. 64 Common Spectrum Management Interface MIB June 13,1996 66 3. The Network Management Framework 68 The Internet-standard Network Management Framework consists of 69 three 70 components. They are: 72 RFC 1155 which defines the SMI, the mechanisms used for 73 describing and naming objects for the purpose of management. 74 RFC 1212 defines a more concise description mechanism, 75 which is wholly consistent with the SMI. 77 RFC 1156 which defines MIB-I, the core set of managed objects 78 for the Internet suite of protocols. RFC 1213, defines 79 MIB-II, an evolution of MIB-I based on implementation 80 experience and new operational requirements. 82 RFC 1157 which defines the SNMP, the protocol used for 83 network access to managed objects. 85 The Framework permits new objects to be defined for the purpose of 86 experimentation and evaluation. 88 4. Conventions 90 The following conventions are used in this document with the 91 exception of Section 10. 93 o Requirement - A feature or function that is required to be 94 necessary to support the RF Spectrum Management. A 95 Requirement contains the word "Shall" and is identified 96 by the word "Requirement" in the left margin. 98 o Objective - A feature or function that is desirable and may 99 be required to support the RF Spectrum Management. An 100 Objective contains the word "Should" and is identified by the 101 word "Objective" in the left margin. 103 5. Objects 105 Managed objects are accessed via a virtual information store, 106 termed the Management Information Base or MIB. Objects in the 107 MIB are defined using the subset of Abstract Syntax Notation 108 One (ASN.1) defined in the SMI. In particular, each object 110 Common Spectrum Management Interface MIB June 13,1996 112 type is named by an OBJECT IDENTIFIER, an administratively 113 assigned name. The object type together with an object 114 instance serves to uniquely identify a specific instantiation 115 of the object. For human convenience, we often use a textual 116 string, termed the descriptor, to also refer to the object 117 type. 119 5.1. Format of Definitions 121 Section 10 contains the specification of all object types 122 contained in this MIB module. The object types are defined 123 using the conventions defined in the SMI, as amended by the 124 extension specified in RFC 1212 and RFC 1215. 126 Common Spectrum Management Interface MIB June 13,1996 128 6. RF Access Network Architecture Overview 130 The Radio Frequency (RF) reference access network architecture 131 consisting of Distribution Hub (DH) or Head End (HE), Fiber 132 Node (FN), and fiber optics and coaxial distribution plants is 133 shown in Figure 1. 135 To other<---//----| 136 DH or ---//--->|| ________ |<---------> 137 HE || | | |Co-axial 500 138 || |------|Fiber |----|Distribution= 139 homes 140 ______||______ Fiber Optics| |--->|Node | |<---------> 141 passed 142 | |<-----//-----| | |______| 143 |Distribution|------//-------| 144 |Hub (DH) | |<----------> 145 |or | ________ | 146 |Head End | Fiber Optics | |---|<-----Co-axial 147 500 148 |(HE) |<-------//-------|Fiber | Distribution 149 homes 150 |____________|------//-------->|Node |---|<----------> 151 passed 152 || Up to |______| |<----------> 153 || 20,000 154 To other <--//--|| homes passed Up to 40 155 DH or --//--->| Fiber Nodes 156 HE 158 Figure 1: RF Reference Access Architecture, HFC Distribution Plant 160 The backbone of a typical large metropolitan network 161 interconnects the Primary HE with the DHs using multiple fiber 162 optic links, in most cases completing bi-directional rings. 163 This fiber optic backbone network is not of interest as far as 164 the management of RF spectrum allocation is concerned. 166 From each DH ( or the HE), the Hybrid Fiber Coax (HFC) 167 subnetworks provide connectivity to the subscriber premises. 168 This document addresses the allocation of RF spectrum in these 169 HFC subnetworks. 171 An HFC subnetwork consists of optical fibers from the DH to 172 each Fiber Node (FN), and then a coaxial distribution plant 174 Common Spectrum Management Interface MIB June 13,1996 176 from each FN to the subscriber premises. Two separate optical 177 fibers between the DH and each of the FNs carry the downstream 178 RF spectrum (typically, 50 to 550 or 750 MHz) and the upstream RF 179 spectrum (typically, 5 to 40 MHz). At the FNs, electrical to 180 optical conversion occurs, and the electrical RF spectrum of 181 the downstream and upstream signals are combined onto a single 182 coaxial cable distribution plant. Diplex filters and bi- 183 directional RF amplifiers allow a single coaxial cable to 184 carry bi-directional traffic separated in the frequency 185 domain. It is the limited RF spectrum available in the 186 coaxial distribution plant that motivates spectrum management 187 across the HFC subnetworks. 189 The RF spectrum allocation in the coaxial distribution network 190 typically places the downstream traffic in the 50-750 MHz 191 region, and the upstream traffic in the 5-40 MHz region. 192 Other options are possible, such as planning the return 193 spectrum in the high frequency range, 900-1000 MHz, for 194 instance. The downstream traffic represents the RF signal 195 going towards the subscribers premises and consists of 196 multiple analog channels of NTSC entertainment video, each 6 197 MHz wide, as well as digital traffic modulated over RF 198 carriers. The upstream traffic represents the return signals 199 from the subscribers, digitally-modulated RF carriers for bi- 200 directional services such as pay-per-view (ppv) activation, 201 telephony, and high-speed data services. 203 It should be noted that in many implementations the downstream 204 signals from several Fiber Nodes (typically 3 to 5) are 205 obtained from an optical splitter that feeds from a single 206 modulated laser. This implies that the same physical signals 207 could be sent downstream to 3-5 nodes, even though in the 208 upstream direction all the Fiber Nodes are independent. It is 209 important, therefore, to recognize the inherent asymmetry of 210 Hybrid Fiber Coax networks, not only in the total bandwidth, 211 but also in the physical aggregation of signals to (and from) 212 the different Fiber Nodes. If two or more Fiber Nodes are 213 supported by a single optical transmitter (or receiver) at the 214 DH (or HE) then for RF spectrum management purposes they are 215 considered as one HFC subnetwork. This is because the same 216 physical signal occupying the same RF spectrum is sent to 217 multiple Fiber Nodes. 219 In some HFC subnetwork designs, to provide greater upstream 220 frequency bandwidth, the service area of a Fiber Node is split 222 Common Spectrum Management Interface MIB June 13,1996 224 into smaller areas (e.g., a 500 home neighborhood may be split 225 into four 125 home areas), each of which is served by a 226 separate co-axial trunk, and hence, has independent upstream 227 channel spectrum. To support this method, known as block 228 conversion, the upstream channel received over the coax trunks 229 are frequency shifted (as shown in Figure 2) and combined at 230 the FN before transmission back to the Distribution Hub (or 231 HE). For the purpose of RF spectrum management, each block 232 convertor is considered as a separate HFC subnetwork in the 233 upstream direction. 235 Co-axial 236 Distribution 237 __________ _____ 238 | |<------25 MHZ----------|BC |-<--25 MHz------ | 239 | | |___| | 240 | Fiber | _____ | 241 | Node |<------50 MHz----------|BC |-<--25 MHz------ 500 242 | | |___| 243 homes 244 | | _____ 245 passed 246 | |<------75 MHz----------|BC |-<--25 MHz------ | 247 | | |___| | 248 | | _____ | 249 |________|<------100 MHz---------|BC |-<--25 MHz------ | 250 |___| 252 BC - Block Converter 254 Figure 2: Block Conversion of Upstream Frequency Spectrum 256 The goal of the spectrum management functions is to control 257 the RF spectrum in both upstream and downstream directions 258 allocated to different vendors' products to provide digital 259 services. The assignment of non-overlapping RF spectra in the 260 HFC broadband network enables the co-existence of many 261 different vendors' products supporting digital services in a 262 single physical HFC subnetwork. Different vendors' products 263 may support different modulation techniques. By managing the 264 RF spectrum (and the related parameters) of each physical HFC 266 Common Spectrum Management Interface MIB June 13,1996 268 subnetwork, one can create many independent logical HFC 269 subnetworks each of which supports a number of products. 270 Thus, RF spectrum management allows co-existence of different 271 vendor technologies in a single physical HFC subnetwork. 272 Therefore, logical HFC subnetwork is conceptually a portion of 273 the shared physical HFC subnetwork resources that is dedicated 274 to a single vendor equipments supporting a number of products 275 to provide digital services to subscribers. Each vendor 276 technology can operate independently of all other vendors' 277 technologies as long as it remains within its assigned range 278 of the RF spectrum and the related configuration parameters 279 such as signal power levels. The equipments to be installed 280 will require the capability to stay within the spectrum (and 281 the other related parameters) boundary in response to the 282 request received from the spectrum management application, in 283 a manner consistent with the RF spectrum management MIB 284 structure described in the following sections. 286 7. RF Spectrum Management Architecture 288 The network management architecture supporting RF Spectrum 289 Management consists of the following components: 291 - Spectrum Management Application (SMA) 292 - Spectrum Management Proxy Agents (SMPAs) 293 - Logical RF access networks 294 - Logical HFC subnetworks 296 As mentioned earlier, several logical RF access networks can 297 be supported in a single physical RF access network, each 298 supported by a different vendor. Vendors' logical RF access 299 networks are used for supporting different products to provide 300 digital services such as digital telephony service, high speed 301 data service, and interactive multi-media service in the same 302 physical Hybrid Fiber Coax (HFC) subnetwork. A logical RF 303 access network will use the physical HFC subnetwork subtended 304 on a given DH, including multiple FNs (typically 40) and their 305 respective multiple co-axial plants. 307 A logical HFC access subnetwork will use the physical HFC 308 subnetwork associated with a single FN (or multiple FNs 309 depending on the architecture lay-out), including the fiber 310 links (from the DH to the FN), and the co-axial plant. The 312 Common Spectrum Management Interface MIB June 13,1996 314 products supporting digital services in logical HFC 315 subnetworks overlaid over a single physical HFC subnetwork 316 will all share the same RF spectrum range associated with that 317 physical HFC subnetwork. 319 The network management architecture supporting SMA, SMPAs and 320 logical RF access networks is shown in Figure 3. Each logical 321 RF access network is required to support an SMPA and the 322 common spectrum management interface (csmi) to the SMA. 324 o Requirement(1) - The logical RF access network provided by a 325 vendor shall support a Spectrum Management= 326 Proxy 327 Agent (SMPA) and the common spectrum management 328 (csmi) interface to the Spectrum Management 329 Application (SMA). 331 Common Spectrum Management Interface MIB June 13,1996 333 _____________ 334 | | 335 |Spectrum | 336 |Management | 337 |Application| 338 | (SMA) | 339 |___________| 340 | | 341 csmi --|-- ---|--- csmi (SNMPv1) 342 |--------| | 343 /--------------|----------/= 344 /---|---------------------------------/ 345 / _____|_________ / / __|____________ ________= 346 / 347 / |(SMPA) | / / | (SMPA) | /Logical= 348 / / 349 /Logical |Distribution | / / |Distribution | /HFC sub/ 350 / 351 / RF |Hub | / / |Hub |------/network/ 352 / 353 / Access |Equipment | / / |Equipment | /_3_____/ 354 / 355 / Network1 |(DHE) | / / |(DHE) | 356 / 357 / |_____________| / / |_____________| 358 / 359 / | | / / | | Logical 360 / 361 / ____| | / / | | RF 362 / 363 / __|_____ ___|____ / / _|______ |----| Access 364 / 365 / /Logical / /Logical/ / / /Logical/ ___|____ Network2= 366 / 367 / /HFC sub / /HFC sub/ / / /HFC sub/ /Logical/ 368 / 369 / /network / /network/ / //network/ /HFC sub/ 370 / 371 / /_1______/ /__2____/ / /__1____/ /network/ 372 / 373 /--------------------------- / / /_2_____/ 374 / 376 /----------------------------------/ 378 csmi - common spectrum management interface 379 HFC - Hybrid Fiber Coax 380 SMPA - Spectrum Management Proxy Agent 382 Figure 3: RF Spectrum Management Reference Architecture 384 Common Spectrum Management Interface MIB June 13,1996 386 As shown in Figure 3, the vendor's logical RF access network 387 consists of a Distribution Hub Equipment (DHE) and multiple 388 logical HFC subnetworks. As shown, the vendor's DHE will 389 support more than one logical HFC subnetworks in a star 390 configuration. Also, the logical HFC subnetworks such as HFC 391 subnetworks 1 and 2 may be supported over a common physical 392 plant even though these two logical HFC subnetworks may be 393 provided and managed independently by two different vendors' 394 network equipments. 396 An example physical RF access network supporting three logical 397 RF access networks (DHE 1, DHE 2, and DHE 3), each provided by 398 a different vendor is shown in Figure 4. In this simplified 399 example, there is only one physical HFC subnetwork subtended 400 by the DH, and hence there are three logical HFC subnetworks 401 which share the RF spectrum range across the same physical HFC 402 subnetwork. 404 Common Spectrum Management Interface MIB June 13,1996 406 Distribution Hub (DH) 407 -------------------------- 408 | ________ | 409 | |DHE 1 |450MHz | 410 | |______|--------->| | 411 | | | 412 | ________ ___|____RF Combiner 413 | |DHE 2 |500MHz | |-> || 414 | |______|-----> |----->|----> 415 | | |-->|| | 416 | ________ |__|___|| | 417 | |DHE 3 |550MHz | | | 418 | |______|--------->| | | /-----------------------= 419 --------------/ 420 | | | / 421 / 422 | ______|________/_ Forward Spectrum______ 423 /-----/ / 424 | | HF/Optical Tx|____//________>= 425 /Fiber/----/Co-axial// 426 | |_______________| /Node /-----/Plant= 427 // 428 | | LF/Optical Rx|<______//_____/_____/----- / 429 / / 430 | |_______________| 431 /------/ / 432 | | / Reverse Spectrum 433 / 434 | ________ | | 435 /--------------------------------------/ 436 | |DHE 1 |20MHz | | Physical HFC Subnetwork 437 | |______|<---------| | | 438 | ____|___ | | 439 | | | | | | 440 | _______ 25MHz | |<-| | | 441 | |DHE 2|<------|<-----|-<---| 442 | |_____| | |<-| | 443 | |___|__|RF Splitter 444 | ________ | | 445 | |DHE 3 |30MHz | | 446 | |______|<---------| | 447 |------------------------| 449 DHE - Distribution Hub Equipment ------------ Electrical 450 HF - High Pass Filter ____________ Optical 451 LF - Low Pass Filter 452 Optical Tx - Optical Transmitter 453 Optical Rx - Optical Receiver 455 Figure 4: Three Logical RF Access Networks in a Physical RF Access Network 457 Common Spectrum Management Interface MIB June 13,1996 459 7.1. Spectrum Management Application (SMA) 461 The SMA co-ordinates and manages the RF spectrum (and the 462 related configuration parameters) across several different 463 logical HFC access subnetworks overlaid over a single physical 464 HFC access subnetwork. 466 o Requirement(2) - The Spectrum Management Application (SMA) 467 shall co-ordinate and manage the RF spectrum 468 and the related configuration parameters 469 across several different logical HFC 470 subnetworks provided by different vendors' 471 equipments and supported over a single physical 472 HFC access subnetwork. 474 Each logical RF access network that belongs to a specific 475 vendor's network equipments may support more than one products 476 to provide digital services such as digital telephony service, 477 high speed data service, and digital video service. It is 478 also possible that more than one logical RF access network in 479 the same physical RF access network will support products to 480 provide the same digital service such as digital telephony 481 service. All products that are supported by the logical HFC 482 subnetworks share the RF spectrum (and the related 483 configuration parameters) associated with the underlying 484 physical HFC subnetwork. 486 As mentioned, the SMA allocates and manages via a common 487 spectrum management interface (csmi), the RF spectrum (and the 488 related configuration parameters) to different vendors' 489 products that are used to support digital services such as 490 high speed data service, digital telephony service, 491 Asynchronous Transfer Mode (ATM) service, and interactive 492 multimedia service in the same physical HFC access subnetwork. 493 In the context of RF spectrum management, products supporting 494 services are primarily distinguished by the underlying 495 technology used. For example, products supporting POTS and 496 products supporting ATM service are distinguished by the 497 transport technology used even though both POTS and the ATM 498 products may both support voice service. 500 csmi provides an SNMPv1 interface between the SMA and SMPA. 502 o Requirement(3) - The common spectrum management interface (csmi) 503 shall support an SNMPv1 interface between the 505 Common Spectrum Management Interface MIB June 13,1996 507 Spectrum Management Application (SMA) and the 508 Spectrum Management Proxy Agent (SMPA) to= 509 manage 510 the RF spectrum and the related parameters 511 of the HFC access subnetworks. 513 o Requirement(4) - The SMPA shall support an RF spectrum= 514 management 515 MIB containing objects on vendor's different 516 product classes that shall be supported in the 517 logical HFC subnetworks in order for the SMA 518 to manage the RF spectrum and the related 519 configuration parameters of the logical 520 HFC subnetworks. 522 o Objective(1) - The common spectrum management interface (csmi) 523 between the SMA and SMPA should be able to evolve 524 to SNMPv2 in the future. 526 The SMA provides and maintains the global view of the RF 527 spectrum (and the related configuration parameters) allocation 528 across all logical HFC subnetworks in the same physical HFC 529 subnetwork. The SMA therefore has the ability to coordinate, 530 manage and allocate RF spectrum and the related parameters 531 associated with the physical HFC subnetwork to all products 532 providing services that are supported using multiple logical 533 HFC subnetworks in the same physical HFC subnetwork. In 534 addition, the SMA retrieves the performance and utilization 535 data on each logical HFC subnetwork from the appropriate 536 performance and traffic management systems. Based on the 537 performance and utilization data, the SMA may allocate, de- 538 allocate, or reconfigure the RF spectrum channels. 540 In addition, as a backup spectrum, the SMA may allocate 541 additional RF spectrum to a vendor's product supporting 542 digital services in a logical HFC subnetwork. Backup spectrum 543 may be needed to accommodate service performance objectives of 544 some vendor's products in a logical HFC subnetwork. The 545 backup spectrum may be used to maintain the service quality 546 for situations when allocated RF channels exceed their 547 capacity or degrade in performance. The SMA may also allocate 548 additional spectrum on an needed basis, e.g., upon receiving a 549 request from a logical HFC subnetwork. Such requests may be 550 generated by the SMPA using SNMP traps. 552 Common Spectrum Management Interface MIB June 13,1996 554 The SMA does not perform call processing, dynamic bandwidth 555 management, connection management, or even protection 556 switching. These capabilities require real-time control, 557 management and allocation of network resources and are 558 therefore supported using call processing or dynamic bandwidth 559 management entities in the vendor's network equipments. 561 As mentioned in Section 6, a single optical transmitter or 562 receiver at the DH (or HE) could be used to support multiple 563 Fiber Nodes and thus multiple HFC subnetworks. For RF 564 spectrum management purposes, the physical HFC subnetworks 565 supported by a single optical transmitter (or receiver) at the 566 DH (or HE) is considered as one physical HFC subnetwork (and 567 thus one logical HFC subnetwork) in the downstream (or 568 upstream) direction. Similarly, for an HFC subnetwork 569 supporting block conversion, each block convertor is 570 considered as a separate HFC subnetwork. It is assumed that 571 the appropriate configuration management system will contain 572 detailed information on the network lay-out including the 573 number of HFC subnetworks supported per optical transmitter or 574 receiver at the DH (or HE). To allocate and manage RF spectrum 575 efficiently, the SMA will retrieve the HFC physical network 576 configuration information for both upstream and downstream 577 directions from the configuration management system. 579 Because of the inherent HFC asymmetry in the upstream and 580 downstream directions, the upstream and downstream HFC 581 subnetworks are treated as separate networks in the RF 582 spectrum management MIB. The SMA maintains the correlation 583 between the upstream and downstream RF channels and their 584 relationship to the specific product class. 586 As mentioned, to manage and co-ordinate the RF spectrum across 587 different logical HFC subnetworks, SMA communicates with the 588 appropriate network management systems such as configuration 589 management system, performance and traffic management system, 590 and fault management system of the cable network. Since these 591 management systems belong to and operated by a single cable 592 network provider, the SMA may communicate with these 593 management systems using a proprietary network management 594 protocol. Wherever these management systems are not 595 available, the SMA may manually obtain the required management 596 data to manage RF spectrum across different logical HFC 597 subnetworks. Also to manage the RF spectrum, the SMA needs to 598 retrieve information on the physical lay-out (e.g., the number 599 of active amplifiers, taps, homes passed in the network, 600 number of Fiber Nodes supported by a single transmitter or 601 receiver at the distribution hub) and physical characteristics 602 (e.g., distortion ratios, forward and return path loss ratios, 604 Common Spectrum Management Interface MIB June 13,1996 606 signal level variation, and attenuation ratios) of the HFC 607 subnetworks from the appropriate management systems (see 608 reference 12). 610 This MIB increases the exposure of the network to unauthorized 611 SNMP managers in that units could be reconfigured to use 612 frequencies which impact other services. A standard solution will= 614 become possible by extending to the use of SNMPv2. It is possible 615 in the first deployments to provide ad-hoc standard security 616 approaches. For instance, key parameters are read only to SNMP. 617 One could require a reset to change these at which time the units 618 read a parameter file from a server. In any event, the interaction 619 between the SMA and the SMPA will be secured physically and any 620 exchanges between the SMPA and the end devices needs to be= 621 secured. 623 In summary, the SMA performs the following functions: 625 - maintains a map of those logical HFC subnetworks 626 (belonging to different logical RF access networks, 627 each supported by a different vendor) that belong 628 to the same physical HFC subnetwork. For example, 629 the SMA maintains the association between the logical 630 HFC subnetworks (numbered as 1) in the logical 631 RF access networks 1 and 2 in Figure 3 and the physical 632 HFC subnetwork to which they belong. 634 - co-ordinates, manages and allocates RF spectrum (and the 635 related configuration parameters) of the physical HFC 636 subnetwork to multiple vendors' products supporting digital 637 services. These products are supported using multiple logical 638 HFC subnetworks in the same physical HFC subnetwork. 639 The logical HFC=CAsubnetwork map is used by the SMA to manage 640 and allocate RF spectrum of the physical HFC subnetwork to 641 the products supported in the logical HFC subnetworks 642 (e.g., logical HFC subnetworks numbered as 1 in logical 643 RF access networks 1 and 2). 645 - maintains the correlation between the upstream and downstream 646 RF channels and their relationship to a specific product class. 648 - communicates with network management systems such as 649 configuration management system, performance and traffic 650 management system, and fault management system to determine 651 the configuration and performance of the physical HFC 652 subnetwork and the logical HFC subnetworks in order to 653 manage and co-ordinate the RF spectrum allocation. 655 From the above discussion, it is clear that the SMA is the 656 management entity that possesses the intelligence and the 657 ability to manage RF spectrum (and the related configuration 659 Common Spectrum Management Interface MIB June 13,1996 661 parameters) of several logical HFC subnetworks that belong to 662 the same physical HFC subnetwork via the csmi. 664 7.2. Spectrum Management Proxy Agent (SMPA) 666 The SMPA supported by each logical RF access network acts as a 667 proxy agent and supports the RF spectrum management MIB to 668 manage the RF spectrum (and the related configuration 669 parameters) in the SMPA's logical HFC subnetworks. Initially, 670 the management interface between the SMPA and the logical HFC 671 subnetworks may be a vendor proprietary interface. However, 672 in the future, it is possible that the interface may support a 673 standard management protocol such as SNMP. Note that the SMPA 674 has knowledge of the allocation of RF spectrum to the products 675 providing digital services in its own logical RF access 676 network only. The SMPA does not have any information on RF 677 spectrum allocated to other logical RF access networks even 678 though these logical networks may also be supported in the 679 same physical RF access network. 681 As noted above, the SMPA has a local view of the RF spectrum 682 (and the related configuration parameters) that is allocated 683 to products providing services in its own logical subnetworks 684 only. In order for the SMA to manage RF spectrum (and the 685 related configuration parameters) across several logical HFC 686 subnetworks, the spectrum management MIB supported by each 687 SMPA must provide local RF configuration information of its 688 logical HFC subnetworks such as RF modulation techniques, RF 689 spectrum frequency agility, and the RF power levels. 691 8. RF Spectrum Terminology 693 Some basic RF spectrum terminologies are described in this 694 section to facilitate defining the RF spectrum management 695 managed objects. 697 8.1. Forward and Reverse RF Spectrum 699 Forward RF spectrum refers to the bandwidth (in Hz) allocated 700 in the network to subscriber direction for transmitting 701 information from the network to the subscriber. Similarly, the 702 reverse RF spectrum refers to the bandwidth (in Hz) allocated 704 Common Spectrum Management Interface MIB June 13,1996 706 in the subscriber to network direction for transmitting 707 information from the subscriber to the network. The forward 708 and reverse spectrum are also referred to as downstream and 709 upstream spectrum respectively. An example forward and 710 reverse RF spectrum allocation across an HFC subnetwork is 711 shown in Figure 5. Most of the existing HFC subnetworks use 712 sub-split system which uses 5 to 40 MHz for the reverse RF 713 spectrum. Upgraded HFC subnetworks typically support forward 714 RF spectrum in the 50 to 750 MHz range. A transition band 715 between upstream and downstream spectra is unused due to the 716 roll-off behavior of the diplex filters. 718 |forward spectrum 719 |-----------------> 720 | 721 _____________ |______________________________ 722 | | | | 724 <------|-----------|--|-----------------------------|----------> 725 5 40 50 750 726 | | Frequency [MHz] 727 <---------------| | 728 reverse spectrum| | 730 Figure 5: An Example Forward and Reverse RF Spectrum Allocation 732 8.2. RF Modulation Techniques 734 Digital modulation is the process by which digital symbols are 735 transformed into sinusoidal waveforms that are compatible with 736 the characteristics of the RF channel. Modulation allows the 737 amplitude, frequency, or phase of an RF carrier wave (or a 738 combination of them) to be varied in accordance with the 739 information to be transmitted on that carrier. 741 Different modulation techniques are used to achieve different 742 spectral efficiency and to minimize interference effects. The 743 spectral efficiency is measured in terms of bits per second 744 per Hz of transmission. The commonly used modulation 745 techniques are Quaternary Phase Shift Keying (QPSK), 746 Quadrature Amplitude Modulation (QAM), Frequency Shift Keying 747 (FSK), and Vestigial Side Band (VSB) modulation. The primary 749 Common Spectrum Management Interface MIB June 13,1996 751 objective of spectrally efficient modulation technique is to 752 maximize the bandwidth efficiency, i.e., to maximize the bits 753 per second per Hz transmission. Higher spectral efficiency 754 can be achieved using higher order modulation techniques but 755 there is a trade-off with the error performance. For example, 756 256 QAM may be used instead of 32QAM to obtain higher spectral 757 efficiency (e.g., providing 6.4 bits per second per Hz 758 compared to 3.2 bits per second per Hz spectral efficiency) 759 with a different trade-off between bit error rate, 760 transmission power and cost. Sometimes, spectral efficiency 761 is reduced (e.g., to transmit information in a hostile RF 762 environment such as the reverse RF spectrum) to form a 763 compromise between bit error rate, power and cost. In those 764 cases, lower order modulation technique such as QPSK 765 modulation technique may be used. Also, depending on the 766 reverse plant requirements, robust modulation techniques 767 such as spread spectrum modulation technique may be used. 769 In order to support different modulation techniques in the 770 same physical HFC subnetwork, the different modulation 771 techniques must use non-overlapping RF frequency spectrum with 772 the exception of the non-synchronous spread spectrum modulation 773 techniques such as non-synchronous Direct Sequence Spread 774 Spectrum (DSSS) modulation techniques. If non-synchronous 775 spread spectrum modulation technique is used, it is important 776 that the power level setting for spread spectrum 777 modulation technique is low compared to the other modulation 778 techniques. Note that the synchronous spread spectrum 779 technology does not have this issue associated with it. 780 For detailed discussions on modulation techniques, 781 see reference [11]. 783 8.3. RF Channel 785 Radio Frequency (RF) Channel is defined as the minimum radio 786 frequency band that is used by a given modulation technique to 787 support a given product class. For example, a specific 788 modulation technique may use a 6 MHz channel. For the purpose 789 of the present document, it should be noted that the 790 definition of channel bandwidth includes both usable and guard 791 bandwidths. The position of an RF channel is defined as the 792 center of the RF carrier frequency. Example RF channels and 793 the respective carrier frequencies are shown in Figure 6. RF 794 channels can be frequency agile or fixed. In case of a fixed 795 frequency RF channel, the position of the RF channel cannot be 796 changed to another RF carrier. On the other hand, the 797 position of a frequency agile RF channel can be moved to a 798 different RF carrier. For a given modulation technique, the 799 RF channel width is independent of the modulation order if the 800 same symbol rate is supported for all modulation orders. 802 Common Spectrum Management Interface MIB June 13,1996 804 | | | | 805 | | | | 806 | | | | 807 ---------|-|----------------|---|-------------- 808 2 MHz channel 6 MHz channel 809 ^ ^ 810 | | 811 at 32 MHz at 260 MHz 813 Figure 6: Example Radio Frequency Spectrum Channels 815 8.4. RF Spectrum Slice 817 For the purpose of RF spectrum management, RF Spectrum Slice 818 is defined as the RF spectrum interval associated with a group 819 of fine-grained modulators. An RF spectrum slice supports one 820 or more RF spectrum channels of the same type allocated to a 821 given product class to provide digital services (e.g., 822 multiple telephony voice channels in a POTS service). The 823 position of the RF spectrum slice is defined by two 824 parameters: upper frequency and lower frequency. The upper 825 and lower frequencies are defined as the upper and the lower 826 frequency limits of the RF spectrum slice. The RF spectrum 827 slice can be frequency agile or fixed depending on the 828 behavior of the RF channels that make up the RF spectrum 829 slice. 831 Common Spectrum Management Interface MIB June 13,1996 833 (lower frequency) (upper frequency) 835 20MHz 30MHz 836 | | | | | | | | | 837 | | | | | | | | | 838 | | | | | | | | | 839 -------|--|--|--|--|--|--|--|--|--------- 840 | RF channels | 842 <------10 MHz Slice-----> 844 Figure 7: An Example Radio Frequency Spectrum Slice 846 8.4.1. RF Spectrum Slice Edge Characterization 848 In order to efficiently stack RF spectrum slices in the same 849 physical HFC subnetwork belonging to different product 850 classes, the SMA needs to know the spectral roll-off 851 characteristics of the typical RF spectrum slice supported by 852 each product class. Vendors may support different product 853 classes using different modulation techniques and hence 854 different RF channel types. Since RF spectrum slices 855 belonging to different product classes may be stacked at 856 different points in the RF spectrum and may have different 857 frequency widths, it is important that the spectral roll-off 858 characteristics provided for a typical spectrum slice of each 859 product class take into considerations of these parameters. 860 Also, the slice spectral roll-off characterization should be 861 closely related to the spectral roll-off characteristics of 862 the RF channels composing the slice. Figure 8 shows the 863 spectral characteristics of a typical RF channel. 865 Common Spectrum Management Interface MIB June 13,1996 867 central channel 868 Pc ________________ 869 | | | 870 | | | 871 |<-RF Channel->| 872 | | | 873 Pc-Ab - -_| - - -| |_ 874 / | | | \ 875 / | | | \ 876 / | | | \ 877 / | | | \skirt 878 / | | | \ 879 / | | | \ 880 Pc-Af / | | | \ floor 881 --------------------------------------------- 882 | | | 883 | | | 884 -------------------|------|-------|---------------------- 885 Fc-B/2 Fc Fc+B/2 887 Figure 8: An Example RF Channel Spectral Envelope 889 In Figure 8, Fc is the carrier frequency of the RF channel and 890 B is the nominal bandwidth of the central channel (or the pass 891 band). The central channel is the region which has flat gain 892 and is characterized by three parameters; the signal power 893 level Pc, carrier frequency Fc, and the channel bandwidth B. 894 Beyond the central channel, is the "skirt" (also referred to 895 as transition band) of the channel's spectral characteristic. 896 The skirt details the spectral roll-off characteristics 897 between the central channel and the "floor" (also referred to 898 as stop band). The skirt is typically convex in shape. Ab is 899 the spectral attenuation at the band of the central channel's 900 band edge. It is measured relative to the power level of the 901 central channel. Note that all attenuations and power levels 902 refer to the power measured in a small band, typically less 903 than 10 kHz and whose center frequency is placed at the 904 frequency of interest. For instance, the power measured in a 905 5 kHz band centered at the Fc+B/2 will be Ab dB below Pc, the 906 power measured in the same 5 kHz band centered at the carrier 907 frequency. Af is the attenuation of the "floor" relative to 908 the power measured in the central or pass band. 910 Common Spectrum Management Interface MIB June 13,1996 912 The RF spectrum slice edge characterization is based on the 913 typical RF channel spectral envelope. The RF slice spectral 914 envelope is approximated by three points; one in the skirt 915 region to provide a better spectral fit to a typical RF 916 spectral roll-off characteristics and the other two points to 917 approximate the spectral envelope from the slice edge to the 918 floor. The parameters used to specify this spectral envelope 919 are shown in Figure 9 and are described in Table 1. 921 P_______//________ 922 | | 923 | | 924 |<-RF Spectrum->| 925 | Slice | 926 | | 927 | | 928 P-Ae ---->----------------- 929 /| |\ 930 / | | \ 931 | | | | 932 P-Am ---> ----------------------- 933 /| | | |\ 934 / | | | | \ 935 / | | | | \ 936 / | | | | \ 937 / | | | | \ 938 | | | | | | 939 P-Af ---> ---------------------------------- 940 | | | | | | 941 | | | | | | 942 ---------------------------------------------------- 943 Fl-Ff Fl-Fm Fl Fu Fu+Fm Fu+Ff 945 Figure 9: RF Spectrum Slice Edge Envelope 947 It is assumed that the shape of the spectral slice envelope 948 does not change with the position of the slice in the RF 949 spectrum and the slice bandwidth. It is also assumed that all 950 possible skirt widths will be taken into considerations when 951 defining the edge envelope parameters for the reference 952 spectrum slice. 954 Common Spectrum Management Interface MIB June 13,1996 956 Table 1 - RF Spectrum Slice Edge Envelope Parameters 958 _____________________________________________________________ 959 | | | | 960 | Parameter | Description |Units | 961 |_____________|____________________________________|________| 962 |_____________|____________________________________|________| 963 | | | | 964 | Ae |The relative attenuation measured at| dB | 965 | |the RF spectrum slice pass band | | 966 | |edge*. | | 967 |___________________________________________________________| 968 | | | | 969 | Am |The relative attenuation measured at| dB | 970 | |the midpoint of the spectral skirt*.| | 971 |___________________________________________________________| 972 | | | | 973 | Fm |The skirt midwidth. The absolute | Hz | 974 | |frequency difference from the slice | | 975 | |edge frequency to the skirt's | | 976 | |midpoint. | | 977 |___________________________________________________________| 978 | | | | 979 | Af |The relative attenuation measured at| | 980 | |the RF spectrum slice skirt's edge*.| dB | 981 |___________________________________________________________| 982 | | | | 983 | Ff |The skirt width. The absolute | Hz | 984 | |frequency difference from the slice | | 985 | |edge frequency to the beginning of | | 986 | |the spectral floor. | | 987 |___________________________________________________________| 989 *All spectral powers are measured in a band no wider than 990 10 kHz whose center frequency is at the frequency of interest. 992 The attenuations at the slice spectral edge are measured 993 relative to the signal power level P of the pass band of the 994 typical spectral slice. The slice pass band is assumed to 995 operate in the region that has flat gain. The SMA will 996 allocate the transmit power level P to different vendors' 997 products based on the power budget of each physical HFC 998 subnetwork and the technical specifications provided by each 999 vendor. In addition, the SMA will use the slice spectral 1001 Common Spectrum Management Interface MIB June 13,1996 1003 roll-off characteristics information provided in the MIB 1004 (e.g., via the parameters in Table 1) to efficiently stack 1005 different spectral slices (belonging to different product 1006 classes) in the HFC subnetworks. Note that the relative power 1007 tolerance of neighboring slices will depend on the parameters 1008 listed in Table 1 as well as the absolute power levels at 1009 which the vendor's products will be operating. 1011 Please note that this document or the csmi MIB definition does 1012 not specify the test procedures and the product acceptance 1013 policies that will be required from the vendors. If needed, 1014 this information may be provided in a separate document. 1016 8.5. Product Classes 1018 A physical HFC subnetwork supports both analog and digital 1019 services. Different vendors' products are used to provide 1020 analog and digital services over HFC subnetworks. A vendor 1021 product used to provide digital services is referred to as 1022 digital product class. Digital product classes may support 1023 broadcast one-way, and switched (Connectionless (CNLS) and 1024 Connection-Oriented (CON)) two-way symmetric and asymmetric, 1025 digital services in the HFC subnetwork. SMA allocates RF 1026 spectrum to different digital product classes in a physical 1027 HFC subnetwork via the csmi. Examples of product classes 1028 supporting digital services include digital telephony product, 1029 High Speed Cable Data Service (HSCDS) product, switched 1030 digital service (e.g., Integrated Services Digital Network 1031 (ISDN) services) product, and interactive multimedia service 1032 product. As mentioned earlier, in the context of RF spectrum 1033 management, product classes are distinguished by the transport 1034 technology used. For example, even though both POTS and the 1035 ATM service products may support voice service, product 1036 supporting POTS is distinguished from the ATM service product 1037 by the transport technology used. 1039 Each digital product class supported by a logical HFC 1040 subnetwork may be allocated either an RF spectrum slice or an 1041 RF channel depending on the modulation techniques or the RF 1042 channel types used for that product class. Different RF 1043 spectrum slices (or RF channels) are allocated in the forward 1044 and reverse directions. Therefore, different types of RF 1045 spectrum slices (or RF channels) may be allocated to a given 1046 product class in the forward and reverse directions of a 1048 Common Spectrum Management Interface MIB June 13,1996 1050 logical HFC subnetwork (i.e., RF channels and the modulation 1051 techniques may be different in the two directions). As an 1052 example, digital telephony product may be supported using the 1053 64 QAM modulation technique in the forward RF channels and the 1054 QPSK modulation technique in the reverse RF channels. 1056 As mentioned above, depending on product class requirements, 1057 different digital product classes may be supported using 1058 different modulation techniques. Also, different vendors' 1059 logical RF access networks may use different modulation 1060 techniques for their product classes to provide the same 1061 digital service, such as digital video service. An example 1062 network access architecture supporting multiple products using 1063 different modulation techniques is shown in Figure 10. 1065 Common Spectrum Management Interface MIB June 13,1996 1067 | 1068 |UPSTREAM |/| DOWNSTREAM (Forward) 1069 |(Reverse) |/| 1070 | |/| 1071 | |/| 64 QAM 1072 | |/| AM-VSB Digital 64 QAM QPSK 1073 | |/| Analog Video Data Digital Video Telephony 1074 | |/| Product Product Product Product 1075 | |/|-----------------------|-----|-------------|---------| 1076 | |/| | | | | 1077 | |/| | | | | 1078 | |/| | | | | 1079 | |/| | | | | 1080 | |/| | | | | 1082 ----|----------|/|-----------------------|-----|-------------|---------|---= 1083 ----> 1084 0 50 550 560 700 750 1085 MHz 1086 | | 1087 | | 1088 | | 1089 | | | 1090 | |--------------------------------------| 1091 | 1092 | 1093 | 16 QAM QPSK QPSK | 1094 | Digital Data Telephony | 1095 | Video Product Product Product | 1096 | |---| |----------|-------------| 1097 | | | | | | 1098 | | | | | | 1099 | | | | | | 1100 ----|-------|---|------------|----------|-------------|--------> 1101 0 6 8 10 25 40 MHz 1103 AM-VSB - Amplitude Modulated Vestigial Side Band 1104 QAM - Quadrature Amplitude Modulated 1105 QPSK - Quaternary Phase Shift Keying 1107 Figure 10 : An Example of RF Frequency Assignment Over a Physical HFC= 1108 Subnetwork 1110 Common Spectrum Management Interface MIB June 13,1996 1112 9. RF Spectrum Management MIB Overview 1114 RF spectrum management objects are used to manage RF spectrum 1115 allocation to different product classes in the logical HFC 1116 subnetworks via the csmi. This section provides an overview 1117 and background of how to use this MIB and other potential MIBs 1118 for this purpose. This section also describes the RF spectrum 1119 management architecture hierarchy that is used to structure 1120 the MIB. 1122 In addition to the MIB module defined in this memo, MIB II 1123 (RFC 1213) is also used for RF spectrum management. 1125 9.1. RF Spectrum Management Architecture Hierarchy 1127 The RF spectrum management architecture hierarchy shown in 1128 Figure 11 is used to structure the RF spectrum management MIB. 1130 Logical RF Access Network (provided by a vendor) 1131 | 1132 | 1133 | 1134 ---------------------------------- 1135 | | | 1136 | | | 1137 logical HFC logical HFC logical HFC 1138 subnetwork subnetwork subnetwork 1139 (forward or reverse) (forward or reverse) (forward or= 1140 reverse) 1141 | 1142 | 1143 ----------------------- 1144 | | | 1145 | | | 1146 product product product 1147 class class class 1148 | 1149 | 1150 ------------------- 1151 | | 1152 | | 1153 RF spectrum RF spectrum 1154 slice slice 1156 Figure 11: RF Spectrum Management Architecture Hierarchy 1158 Common Spectrum Management Interface MIB June 13,1996 1160 As shown in Figure 11, the RF spectrum management architecture 1161 consists of the following hierarchy: 1163 - a logical RF access network supported by a specific vendor's 1164 equipments 1166 - logical HFC subnetworks supported by the logical RF access 1167 network overlaid over a physical HFC subnetwork. Logical 1168 HFC subnetworks in the forward and reverse directions are 1169 considered as separate networks. 1171 - product classes supported by a logical HFC subnetwork to= 1172 provide 1173 digital services 1175 - RF spectrum slices supported for each product class 1177 9.2. Application of MIB II to Spectrum Management 1179 9.2.1. The System Group 1181 Use the System Group to apply to the SNMP proxy-agent, SMPA. 1182 Each logical RF access network implements an SMPA to support 1183 RF spectrum allocation to services in its logical HFC 1184 subnetworks. System Group applies to only one system. This 1185 group is not instantiated. 1187 o Requirement(5) - The System Group from MIB II (RFC 1213) shall 1188 apply to the Spectrum Management Proxy Agent 1189 (SMPA). 1191 Object Descriptions 1192 3D=3D=3D=3D=3D=3D 3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 1193 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1195 sysDescr: ASCII string describing the SNMP proxy-agent 1196 (i.e., the SMPA). 1197 Can be up to 255 characters long. This field is 1198 generally used to indicate the full name and version 1199 identification of the system supported. In addition, 1200 the description may include information on the 1201 vendor's RF access network including the vendor's 1202 name. 1204 Common Spectrum Management Interface MIB June 13,1996 1206 sysObjectID: Unique OBJECT IDENTIFIER (OID) for the SNMP= 1207 proxy-agent. 1209 sysUpTime: Clock in the SNMP proxy-agent; TimeTicks in 1/100s 1210 of a second. Elapsed type since the proxy-agent 1211 came on line. 1213 sysContact: Contact for the SNMP proxy-agent. ASCII string of 1214 up to 255 characters. 1216 sysName: Domain name of the SNMP proxy-agent, for example, 1217 acme.com 1219 sysLocation: Location of the SNMP proxy-agent. ASCII string of 1220 up to 255 characters. 1222 sysServices: Services supported by the RF access networks. 1223 Since the RF access networks may simultaneously 1224 support a number of services at different protocol 1225 layers of the Open Systems Interconnection (OSI) 1226 protocol stack (e.g., POTS, cable data service, 1227 digital broadcast video), the value "0" is used 1228 for RF spectrum management purposes. 1230 In addition, the SMPA must support coldStart and 1231 authenticationFailure traps from RFC1157 to indicate 1232 respectively the SMPA restart after a failure and the SNMP 1233 message received by the SMPA that did not pass authentication 1234 verification. 1236 o Requirement(6) - The Spectrum Management Proxy Agent (SMPA)= 1237 shall 1238 support coldStart and authenticationFailure= 1239 traps 1240 from RFC 1157 to indicate respectively the SMPA 1241 restart (e.g., after a failure), and that the= 1242 SNMP 1243 messages did not pass the authentication 1244 verification. 1246 9.3. Structure of the RF Spectrum Management MIB 1248 The managed objects are arranged into the following SNMP 1249 tables: 1251 (1) Logical HFC subnetwork table 1252 (2) Product class table 1253 (3) RF spectrum slice configuration table 1255 Common Spectrum Management Interface MIB June 13,1996 1257 There is a one-to-one map between the logical HFC subnetworks 1258 in a logical RF access network and the physical HFC 1259 subnetworks. Therefore, the logical HFC subnetworks in a 1260 logical RF access network managed by the SMPA may be indexed 1261 the same way as the physical HFC subnetworks. The SMA 1262 maintains the relationship between the logical RF access 1263 networks provided by different vendors' network equipments and 1264 the physical HFC subnetworks. For RF spectrum management 1265 purposes, the HFC subnetworks supported by a single optical 1266 transmitter (or receiver) at the DH (or HE) are considered as 1267 a single physical HFC subnetwork in the forward (or reverse 1268 direction). The logical HFC subnetworks may be supported in 1269 the future using the ifTable in MIB II (RFC 1213). 1271 The logical HFC subnetwork table and the product class table 1272 contain respectively the descriptions of the logical HFC 1273 subnetworks and the product classes that are supported in the 1274 logical HFC subnetworks. The logical HFC subnetwork table also 1275 contains descriptions of the physical HFC subnetworks to which 1276 a vendor's logical HFC subnetworks belong. The product class 1277 table also contains description of the RF technology supported 1278 by a vendor for each type of product class. 1280 The SMA can use the RF spectrum slice configuration table to 1281 create, delete, or modify RF spectrum slices containing single 1282 or multiple RF channels depending on the vendor's RF 1283 technology. To configure or reconfigure an RF spectrum slice, 1284 the SMA uses the RF information template provided in the 1285 product class table for each product class. 1287 As mentioned earlier, frequency block conversion method is 1288 used for efficiently utilizing the reverse RF spectrum. In 1289 the future, frequency block conversion may also be used in the 1290 forward direction. Each block converter is modeled as a 1291 separate physical HFC subnetwork (and therefore as a separate 1292 logical HFC subnetwork). 1294 Some vendor technologies may support RF channels as dynamic 1295 resources and assign an RF channel to a subscriber on a 1296 dynamic basis via session establishments. For example, some 1297 vendor technologies may use RF channels of very narrow band 1298 such as 50 kHz, using Frequency Division Multiplexing (FDM) 1299 technique. In contrast, other vendor technologies may support 1300 allocation of a portion of the RF channel bandwidth (e.g., 1301 DS0s within a 6 MHz RF channel) to a subscriber on a session 1303 Common Spectrum Management Interface MIB June 13,1996 1305 by session basis (e.g., by using Time Division Multiplexing 1306 (TDM) technique and subchannel configurations). Therefore, 1307 the RF spectrum slice table can be used to configure an RF 1308 spectrum slice containing either a single or multiple RF 1309 channels depending on the RF technology supported for a 1310 specific product class. Therefore, an RF spectrum slice may 1311 contain a single RF carrier or multiple RF carriers. 1313 Therefore, SMA can allocate RF spectrum to a product in the 1314 following fashions: 1316 - single or multiple non-contiguous RF channels (each 1317 RF channel containing a single RF carrier) 1319 - single or multiple non-contiguous RF spectrum slices (each= 1320 slice 1321 containing multiple RF channels, i.e., multiple RF carriers) 1323 For example, SMA may allocate RF frequency spectrum to a 1324 product class in two different RF spectrum slices (e.g., one 1325 from 10-14 MHz and the other from 26-30 MHz) using four RF 1326 channels of each 1 MHz size (allocated to each RF spectrum 1327 slice), as shown in Figure 12. Note that RF channels can be 1328 moved to a different carrier frequency within the slice if a 1329 portion of the slice becomes unusable. 1331 4 RF Channels 4 RF Channels 1332 ^ ^ ^ ^ ^ ^ ^ ^ 1333 | | | | | | | | | | | | 1334 | | | | | | | | | | | | 1336 ---------|-|-|-|-|-|-|-|-|--------|-|-|-|-|-|-|-|-|-------- 1337 | | | | 1338 10MHz<--------->14MHz 26MHz<---------->30MHz 1339 Slice 1 Slice 2 1341 Figure 12: An Example of RF Spectrum Slice Allocation 1343 Table 2 lists the objects that are relevant for RF spectrum 1344 management. The table also shows the RF spectrum 1345 configuration parameters that are configurable via the csmi. 1347 Common Spectrum Management Interface MIB June 13,1996 1349 Table 2 - RF Spectrum Management Objects 1351 _________________________________________________________________________ 1352 | | | 1353 | 1354 | Management | Managed Objects |Note 1355 | 1356 | Information | | 1357 | 1359 |___________________|_________________________________|_________________| 1361 |___________________|_________________________________|_________________| 1362 |Logical HFC |(1)logical subnetwork address | 1363 | 1364 |subnetwork |(2)logical subnetwork description| 1365 | 1366 |information |(3)physical network description | 1367 | 1368 | |(4)block conversion support | 1369 | 1371 |_______________________________________________________________________| 1372 |Product class/RF |(1)product class type | 1373 | 1374 |channel information|(2)product class description | 1375 | 1376 | |(3)RF modulation technique | 1377 | 1378 | |(5)RF channel data rate | 1379 | 1380 | |(6) minimum modulation order | 1381 | 1382 | |(7) maximum modulation order | 1383 | 1384 | |(8) modulation order step size | 1385 | 1386 | |(9)RF channel minimum frequency | 1387 | 1388 | |(10)RF channel maximum frequency | 1389 | 1390 | |(11)RF channel frequency step | 1391 | 1392 | | size | 1393 | 1394 | |(12)RF channel minimum power | 1395 | 1396 | | level | 1397 | 1398 | |(13)RF channel maximum power | 1399 | 1400 | | level | 1401 | 1402 | |(14)RF channel power level step | 1403 | 1404 | | size | 1405 | 1406 | |(15)RF channel desired modulation| 1407 | 1408 | | order | 1409 | 1410 | |(16)RF slice skirt transmit | 1411 | 1412 | | attenuation | 1413 | 1414 | |(17)RF slice skirt edge transmit | 1415 | 1416 | | attenuation | 1417 | 1418 | |(18)RF slice skirt bandwidth | 1419 | 1420 | |(19)RF slice skirt midbandwidth | 1421 | 1423 |_____________________________________________________|_________________| 1425 Common Spectrum Management Interface MIB June 13,1996 1427 Table 2 - RF Spectrum Management Objects (cont.) 1429 _________________________________________________________________________ 1430 | | | 1431 | 1432 | Management | Managed Objects |Note 1433 | 1434 | Information | | 1435 | 1437 |___________________|_________________________________|_________________| 1439 |___________________|_________________________________|_________________| 1440 | |(20)RF slice envelope edge | 1441 | 1442 | | transmit attenuation | 1443 | 1444 | |(21)RF slice received sensitivity| 1445 | 1446 | | level from adjacent slices' | 1447 | 1448 | | skirts | 1449 | 1450 | |(22)RF slice edge received | 1451 | 1452 | | sensitivity level | 1453 | 1454 | | | 1455 | 1457 |_____________________________________________________|_________________| 1458 |RF spectrum slice |(1)RF spectrum slice identifier |The parameters= 1459 5,| 1460 |(or RF channel) |(2)Operational status |6,7, & 8 are 1461 | 1462 |configurable |(3)Administrative status |configurable= 1463 per | 1464 |parameters |(4)Last change status |RF slice or RF= 1465 | 1466 | |(5)Slice modulation order |channel= 1467 depending| 1468 | |(6)Slice upper frequency |on the RF= 1469 techno-| 1470 | |(7)Slice lower frequency |logy used for= 1471 a | 1472 | |(8)Slice transmit power level |specific= 1473 product | 1474 | | |class. 1475 | 1477 |___________________|_________________________________|_________________| 1479 Common Spectrum Management Interface MIB June 13,1996 1481 10. Definitions 1483 COMMON-SPECTRUM-MANAGEMENT-INTERFACE-MIB DEFINITIONS ::=3D= 1484 BEGIN 1486 IMPORTS 1487 OBJECT-TYPE 1488 FROM RFC-1212 1489 enterprises, TimeTicks 1490 FROM RFC1155-SMI 1491 DisplayString 1492 FROM RFC1213-MIB 1493 EntryStatus 1494 FROM RFC1271-MIB 1495 TRAP-TYPE 1496 FROM RFC-1215; 1498 -- This MIB module uses the extended OBJECT-TYPE macro as 1499 -- defined in RFC1212 and the TRAP-TYPE macro as defined 1500 -- in RFC 1215. 1502 -- This is the MIB module to manage Radio Frequency (RF) spectrum 1503 -- of the logical Hybrid Fiber Coax (HFC) subnetworks via the 1504 -- common spectrum management interface (csmi). 1506 twcable OBJECT IDENTIFIER ::=3D {enterprises 1174} 1508 requirements OBJECT IDENTIFIER ::=3D {twcable 1 } 1510 csmirequirements OBJECT IDENTIFIER ::=3D {requirements 1 } 1512 csmiMIB OBJECT IDENTIFIER ::=3D {csmirequirements 1} 1514 csmiMIBObjects OBJECT IDENTIFIER ::=3D {csmiMIB 1} 1516 -- This MIB module contains logical Hybrid Fiber Coax (HFC)= 1517 subnetwork 1518 -- group, product class group, and the RF spectrum slice group. 1519 -- The logical HFC subnetwork group contains descriptions of 1520 -- the logical HFC subnetworks and the associated physical HFC 1521 -- subnetworks. 1522 -- The product class group contains descriptions of different 1523 -- vendors' products supporting digital services and the 1524 -- associated RF channel types. 1526 Common Spectrum Management Interface MIB June 13,1996 1528 -- The RF spectrum slice group consists of the RF spectrum= 1529 slice 1530 -- configuration table which is used for creating, deleting, 1531 -- and modifying RF spectrum slices containing a single or 1532 -- multiple RF channels. 1534 Common Spectrum Management Interface MIB June 13,1996 1536 csmiProductClassTypes OBJECT IDENTIFIER ::=3D= 1537 {csmiMIBObjects 1} 1539 -- The following values are defined for use as 1540 -- possible values of the digital product class types that= 1541 will 1542 -- be supported in the hybrid fiber coax systems. Examples 1543 -- of digital product classes include telephony service 1544 -- product, high speed data service product, and 1545 -- interactive multi-media service product. 1546 -- In the context of RF spectrum management, the product 1547 -- classes are distinguished by the technology used 1548 -- and not by the services supported by these product= 1549 classes. 1550 -- For example, POTS product class is distinguished 1551 -- from the ATM product class by the transport technology= 1552 used 1553 -- even though both POTS and the ATM product classes 1554 -- may support voice service. 1556 csmiNoProduct OBJECT IDENTIFIER ::=3D {= 1557 csmiProductClassTypes 1} 1558 -- No product class. 1560 csmiUnknownProduct OBJECT IDENTIFIER ::=3D 1561 { csmiProductClassTypes 2} 1562 -- An unknown product class. 1564 csmiPOTSProduct OBJECT IDENTIFIER ::=3D {= 1565 csmiProductClassTypes 3} 1566 -- Plain Old Telephone Service Product. 1568 csmiHighSpeedCableDataServiceProduct OBJECT IDENTIFIER ::=3D 1569 { csmiProductClassTypes= 1570 4} 1571 -- High speed cable data service product class. 1573 csmiSwitchedDigitalServiceProduct OBJECT IDENTIFIER ::=3D 1574 { csmiProductClassTypes 5} 1575 -- Switched digitial service product class may include 1576 -- Integrated Digital Service Network (ISDN) service 1577 -- products and other voice service products. 1579 csmiUtilityCommunicationsServiceProduct OBJECT IDENTIFIER= 1580 ::=3D 1581 { csmiProductClassTypes= 1582 6} 1583 -- Utility communications service product 1584 -- supporting services such as telemetry service. 1586 csmiConverterStatusMonitoringProduct OBJECT IDENTIFIER ::=3D 1587 { csmiProductClassTypes 7} 1588 -- Network Interface Unit (NIU) status monitoring 1589 -- product class. 1591 csmiInteractiveMultimediaServiceProduct OBJECT IDENTIFIER= 1592 ::=3D 1593 { csmiProductClassTypes= 1594 8} 1595 -- Interactive multimedia service product class 1596 -- supporting services such as interactive 1598 Common Spectrum Management Interface MIB June 13,1996 1600 -- game/shopping/education service. 1602 csmiVideoOnDemandServiceProduct OBJECT IDENTIFIER ::=3D 1603 { csmiProductClassTypes 9} 1604 -- Video on demand service product class. 1606 csmiTransponderCommunicationsProduct OBJECT IDENTIFIER ::=3D 1607 { csmiProductClassTypes= 1608 10} 1609 -- Transponder communications product class 1610 -- supporting services such as satellite digital 1611 -- broadcast service. 1613 csmiIEEE80214Product OBJECT IDENTIFIER ::=3D 1614 { csmiProductClassTypes 11} 1615 -- An IEEE 802.14 based product class 1616 -- which supports a number of services 1617 -- such as voice, video and data based on IEEE 802.14= 1618 standards. 1620 csmiATMProduct OBJECT IDENTIFIER ::=3D {= 1621 csmiProductClassTypes 12} 1622 -- ATM product class. 1624 csmiVendorSpecificProduct OBJECT IDENTIFIER ::=3D 1625 { csmiProductClassTypes= 1626 13} 1627 -- A vendor specific product class which supports 1628 -- vendor specific services. 1630 Common Spectrum Management Interface MIB June 13,1996 1632 csmiModulationTypes OBJECT IDENTIFIER ::=3D {csmiMIBObjects= 1633 2} 1635 -- The following values are defined for use as 1636 -- possible values of the modulation techniques that may be 1637 -- supported in the hybrid fiber coax systems. Examples 1638 -- of different modulation techniques include QAM, PSK, 1639 -- QPR, spread spectrum, and VSB. 1641 csmiNoModulation OBJECT IDENTIFIER ::=3D 1642 { csmiModulationTypes 1} 1643 -- No modulation technique. 1645 csmiUnknownmodulation OBJECT IDENTIFIER ::=3D 1646 { csmiModulationTypes 2} 1647 -- Modulation technique that is not known. 1649 csmiQAMmodulation OBJECT IDENTIFIER ::=3D 1650 { csmiModulationTypes 3} 1651 -- Quadrature amplitude modulation (QAM) technique 1653 csmiVSBmodulation OBJECT IDENTIFIER ::=3D 1654 { csmiModulationTypes 4} 1655 -- Vestigial Side Band (VSB) modulation technique 1657 csmiPSKmodulation OBJECT IDENTIFIER ::=3D 1658 { csmiModulationTypes 5} 1659 -- Phase shift key (PSK) modulation technique 1661 csmiDPSKmodulation OBJECT IDENTIFIER ::=3D 1662 { csmiModulationTypes 6} 1663 -- Differential phase shift key (DPSK) modulation technique 1665 csmiOFDMmodulation OBJECT IDENTIFIER ::=3D 1666 { csmiModulationTypes 7} 1667 -- Orthogonal frequency division modulation (OFDM) technique 1669 csmiQPRmodulation OBJECT IDENTIFIER ::=3D 1670 { csmiModulationTypes 8} 1671 -- Quadrature partial response (QPR) modulation technique 1673 csmiQPSKmodulation OBJECT IDENTIFIER ::=3D 1674 { csmiModulationTypes 9} 1675 -- Quaternary phase shift key (QPSK) modulation technique 1677 csmiDQPSKmodulation OBJECT IDENTIFIER ::=3D 1678 { csmiModulationTypes 10} 1679 -- Differential quaternary phase shift key (DQPSK) 1680 -- modulation technique 1682 csmiFSKmodulation OBJECT IDENTIFIER ::=3D 1683 { csmiModulationTypes 11} 1684 -- Frequency shift key (FSK) modulation technique 1686 csmiASKmodulation OBJECT IDENTIFIER ::=3D 1687 { csmiModulationTypes 12} 1688 -- Amplitude shift key (ASK) modulation technique 1690 Common Spectrum Management Interface MIB June 13,1996 1692 csmiOPSKmodulation OBJECT IDENTIFIER ::=3D 1693 { csmiModulationTypes 13} 1694 -- Offset phase shift key (OPSK) modulation technique 1696 csmiNonSynSpreadSpectrummodulation OBJECT IDENTIFIER ::=3D 1697 { csmiModulationTypes 14} 1698 -- Non-synchronous spread spectrum modulation technique 1700 csmiSynchSpreadSpectrummodulation OBJECT IDENTIFIER ::=3D 1701 { csmiModulationTypes 15} 1702 -- Synchronous spread spectrum modulation technique 1704 Common Spectrum Management Interface MIB June 13,1996 1706 -- Logical HFC Subnetwork Configuration Table 1708 -- This table contains descriptions of the logical 1709 -- Hybrid Fiber Coax (HFC) subnetworks that are supported 1710 -- by the RF Spectrum Management Proxy Agent (SMPA). 1711 -- Note that the address and description=CAfields for a 1712 -- subnetwork will be set by the SMA, but the direction 1713 -- and block converter shift fields are read only. 1714 -- The SMPA should communicate if the direction is forward 1715 -- or reverse, as well determine the block conversion 1716 -- frequencies (if any) by interactions with the network 1717 -- and the terminal devices of each product. 1719 -- Implementation of this group is mandatory if 1720 -- providing RF spectrum management. 1722 logicalHfcSubnetworkTable OBJECT-TYPE 1723 SYNTAX SEQUENCE OF LogicalHfcSubnetworkEntry 1724 ACCESS not-accessible 1725 STATUS mandatory 1726 DESCRIPTION 1727 "This table contains information on the logical 1728 HFC subnetworks that are supported by the SMPA. 1729 Logical HFC subnetworks in the forward direction, 1730 i.e., in the network-to-subscriber direction and 1731 in the reverse direction, i.e., in the 1732 subscriber-to-network direction are modeled as 1733 two separate HFC sub networks." 1734 ::=3D { csmiMIBObjects 3 } 1736 logicalHfcSubnetworkEntry OBJECT-TYPE 1737 SYNTAX LogicalHfcSubnetworkEntry 1738 ACCESS not-accessible 1739 STATUS mandatory 1740 DESCRIPTION 1741 "This list contains logical HFC subnetwork= 1742 information." 1743 INDEX { logicalHfcSubnetworkIndex } 1744 ::=3D { logicalHfcSubnetworkTable 1} 1746 LogicalHfcSubnetworkEntry ::=3D SEQUENCE { 1747 logicalHfcSubnetworkIndex 1748 INTEGER, 1749 logicalHfcSubnetworkDirection 1750 INTEGER, 1751 logicalHfcSubnetworkAddress 1752 OCTET STRING, 1753 logicalHfcSubnetworkDescription 1754 DisplayString, 1755 physicalHfcSubnetworkDescription 1757 Common Spectrum Management Interface MIB June 13,1996 1759 DisplayString, 1760 hfcBlockConversionFrequencyShift 1761 INTEGER 1762 } 1764 logicalHfcSubnetworkIndex OBJECT-TYPE 1765 SYNTAX INTEGER (1..65535) 1766 ACCESS read-only 1767 STATUS mandatory 1768 DESCRIPTION 1769 "The value of this object identifies the logical 1770 HFC subnetwork for which this entry contains= 1771 the 1772 HFC subnetwork information." 1773 ::=3D { logicalHfcSubnetworkEntry 1} 1775 logicalHfcSubnetworkDirection OBJECT-TYPE 1776 SYNTAX INTEGER { 1777 forward(1), 1778 reverse(2) 1779 } 1780 ACCESS read-only 1781 STATUS mandatory 1782 DESCRIPTION 1783 "The value of this object indicates whether the 1784 RF spectrum supported by this logical HFC 1785 subnetwork apply to the forward or reverse 1786 direction. The 1787 forward(1) refers to the RF spectrum apply to 1788 the subscriber-to-network direction and the= 1789 value 1790 reverse(2) refers to the RF spectrum apply to= 1791 the 1792 network-to-subscriber direction." 1793 ::=3D { logicalHfcSubnetworkEntry 2} 1795 logicalHfcSubnetworkAddress OBJECT-TYPE 1796 SYNTAX OCTET STRING (SIZE(0..255)) 1797 ACCESS read-write 1798 STATUS mandatory 1799 DESCRIPTION 1800 "An address assigned to the logical HFC= 1801 subnetwork 1802 for administrative purposes. If no address is 1803 assigned, then this is an octet string of zero 1804 length." 1805 ::=3D { logicalHfcSubnetworkEntry 3} 1807 logicalHfcSubnetworkDescription OBJECT-TYPE 1809 Common Spectrum Management Interface MIB June 13,1996 1811 SYNTAX DisplayString (SIZE (0..255)) 1812 ACCESS read-write 1813 STATUS mandatory 1814 DESCRIPTION 1815 "Description of the logical HFC subnetwork. 1816 The description may include vendor's name, the 1817 Distribution Hub Equipment (DHE) name, and the 1818 version identification." 1819 ::=3D { logicalHfcSubnetworkEntry 4} 1821 physicalHfcSubnetworkDescription OBJECT-TYPE 1822 SYNTAX DisplayString (SIZE (0..255)) 1823 ACCESS read-write 1824 STATUS mandatory 1825 DESCRIPTION 1826 "Description of the physical HFC subnetwork 1827 to which this logical HFC subnetwork 1828 belongs. The description may include 1829 full name, number of fiber nodes supported 1830 per optical receiver or transmitter at the 1831 Distribution Hub (DH) or Head End (HE), and 1832 geographic locations of the fiber nodes or 1833 the HFC subnetworks." 1834 ::=3D { logicalHfcSubnetworkEntry 5} 1836 hfcBlockConversionFrequencyShift OBJECT-TYPE 1837 SYNTAX INTEGER 1838 ACCESS read-only 1839 STATUS mandatory 1840 DESCRIPTION 1841 "This object identifies the amount of frequency 1842 shift supported by the block conversion method 1843 from the frequency supported on the co-axial= 1844 part. 1845 The value can be 0, positive or negative. 1846 The value 0 indicates that either block 1847 conversion is not supported in the 1848 HFC subnetwork or block conversion supports 1849 fixed frequency shift only (current HFC 1850 implementations). The positive value 1851 indicates that the frequency is shifted upward 1852 from the one supported in the co-axial part of= 1854 the HFC subnetwork and the value negative 1855 indicates that the 1856 frequency is shifted downward (possibly future 1857 HFC implementations using broadband receiver 1858 at the Distribution Hub). The value is= 1859 expressed 1861 Common Spectrum Management Interface MIB June 13,1996 1863 in units of kHz." 1864 ::=3D { logicalHfcSubnetworkEntry 6} 1866 Common Spectrum Management Interface MIB June 13,1996 1868 -- Product Class Table 1870 -- This table contains descriptions and configuration 1871 -- parameters of the digital product classes and the 1872 -- associated Radio Frequency (RF) channel types 1873 -- that are supported in logical Hybrid Fiber 1874 -- Coax (HFC) subnetworks. 1876 -- This table also provides information on the 1877 -- RF channel types (forward or reverse) 1878 -- supported for the given digital product class. 1879 -- The digital product classes are modeled as one-way 1880 -- products using either forward or reverse RF channels. 1882 -- An RF channel associated with a given digital product 1883 -- class in a logical HFC subnetwork is defined 1884 -- as the minimum radio frequency used in a 1885 -- given modulation technique. 1887 -- The SMA uses the rfSpectrumSliceConfigTable 1888 -- to create, delete or modify an RF spectrum 1889 -- slice (containing a single or multiple RF 1890 -- channels) and the related configurable 1891 -- parameters using the RF channel information 1892 -- provided for a given digital product class 1893 -- in this table. 1895 -- It is possible that different digital product classes 1896 -- may be supported using the same RF channel type. 1898 -- Implementation of this group is mandatory if 1899 -- providing RF spectrum management. 1901 productClassTable OBJECT-TYPE 1902 SYNTAX SEQUENCE OF ProductClassEntry 1903 ACCESS not-accessible 1904 STATUS mandatory 1905 DESCRIPTION 1906 "This table contains information on the digital 1907 product classes and the associated RF channels 1908 that are supported in the logical 1909 HFC subnetworks." 1910 ::=3D { csmiMIBObjects 4 } 1912 productClassEntry OBJECT-TYPE 1914 Common Spectrum Management Interface MIB June 13,1996 1916 SYNTAX ProductClassEntry 1917 ACCESS not-accessible 1918 STATUS mandatory 1919 DESCRIPTION 1920 "This list contains digital product class and the 1921 associated RF channel parameters and= 1922 descriptions." 1923 INDEX { productHfcNetworkIndex, productClassIndex } 1924 ::=3D { productClassTable 1} 1926 ProductClassEntry ::=3D SEQUENCE { 1927 productHfcNetworkIndex 1928 INTEGER, 1929 productClassIndex 1930 INTEGER, 1931 productClassType 1932 OBJECT IDENTIFIER, 1933 productClassDescription 1934 DisplayString, 1935 rfChannelSize 1936 INTEGER, 1937 rfChannelDataRate 1938 INTEGER, 1939 rfChannelModulationType 1940 OBJECT IDENTIFIER, 1941 rfChannelDesiredModulationOrder 1942 INTEGER, 1943 rfChannelModulationMinOrder 1944 INTEGER, 1945 rfChannelModulationMaxOrder 1946 INTEGER, 1947 rfChannelModulationOrderStepSize 1948 INTEGER, 1949 rfChannelMinFrequency 1950 INTEGER, 1951 rfChannelMaxFrequency 1952 INTEGER, 1953 rfChannelFrequencySpectrumStepSize 1954 INTEGER, 1955 rfChannelMinimumPowerLevel 1956 INTEGER, 1957 rfChannelMaximumPowerLevel 1958 INTEGER, 1959 rfChannelPowerLevelStepSize 1960 INTEGER, 1962 Common Spectrum Management Interface MIB June 13,1996 1964 rfSliceBandEdgeAttenuation 1965 INTEGER, 1966 rfSliceSkirtAttenuation 1967 INTEGER, 1968 rfSliceEnvelopeEdgeAttenuation 1969 INTEGER, 1970 rfSliceSkirtMidBandwidth 1971 INTEGER, 1972 rfSliceSkirtBandwidth 1973 INTEGER, 1974 rfSliceSkirtSensitivity 1975 INTEGER, 1976 rfSliceEdgeSensitivity 1977 INTEGER 1978 } 1980 productHfcNetworkIndex OBJECT-TYPE 1981 SYNTAX INTEGER (1..65535) 1982 ACCESS read-only 1983 STATUS mandatory 1984 DESCRIPTION 1985 "The value of this object identifies the logical 1986 HFC subnetwork for which this entry contains= 1987 the 1988 digital product class information. The value 1989 of this object for a specific logical HFC 1990 subnetwork has the 1991 same value as the logicalHfcSubnetworkIndex= 1992 defined 1993 in logicalHfcSubnetworkTable for the same= 1994 logical 1995 HFC subnetwork." 1996 ::=3D { productClassEntry 1} 1998 productClassIndex OBJECT-TYPE 1999 SYNTAX INTEGER (1..65535) 2000 ACCESS read-only 2001 STATUS mandatory 2002 DESCRIPTION 2003 "The value of this object identifies the 2004 digital product class entries for this logical= 2005 HFC 2006 subnetwork." 2007 ::=3D { productClassEntry 2} 2009 productClassType OBJECT-TYPE 2010 SYNTAX OBJECT IDENTIFIER 2011 ACCESS read-only 2012 STATUS mandatory 2014 Common Spectrum Management Interface MIB June 13,1996 2016 DESCRIPTION 2017 "The value of this object identifies the type of 2018 digital product class being supported for this= 2020 logical HFC subnetwork. For example, for 2021 telephony service product, the digital 2022 product class type may indicate 2023 'csmiPOTSProduct' for this entry." 2024 ::=3D { productClassEntry 3} 2026 productClassDescription OBJECT-TYPE 2027 SYNTAX DisplayString (SIZE (0..255)) 2028 ACCESS read-only 2029 STATUS mandatory 2030 DESCRIPTION 2031 "Description of the digital product being= 2032 provided 2033 for this logical HFC subnetwork. The= 2034 description 2035 may include full name, the protocol layer and= 2036 the 2037 transport technology used, and version 2038 identification 2039 of the digital product class." 2040 ::=3D { productClassEntry 4} 2042 rfChannelSize OBJECT-TYPE 2043 SYNTAX INTEGER (1..4294967295) 2044 ACCESS read-only 2045 STATUS mandatory 2046 DESCRIPTION 2047 "The value of this object identifies the RF= 2048 channel 2049 size supported for this product class. The= 2050 value is 2051 expressed in kHz. An RF channel size is defined= 2052 as 2053 the occupied RF bandwidth plus guard RF= 2054 bandwidth 2055 for a single modulated carrier. For example, 2056 the RF channel size may be 6,000 kHz. 2057 The RF channel size is fixed for a given 2058 modulation technique and digital product= 2059 class." 2060 ::=3D { productClassEntry 5 } 2062 rfChannelDataRate OBJECT-TYPE 2063 SYNTAX INTEGER (0..4294967295) 2064 ACCESS read-only 2065 STATUS mandatory 2066 DESCRIPTION 2067 "The value of this object provides the computed= 2068 data 2069 rate of the RF channel supported for this= 2070 product 2071 class based on the modulation technique and 2072 the modulation order used for the RF channel= 2073 type. 2074 The value is specified in bits per second which 2076 Common Spectrum Management Interface MIB June 13,1996 2078 is computed from the spectral efficiency 2079 defined in bits per second per Hz and the= 2080 channel 2081 size defined in Hz. For example, 2082 the 64QAM modulation 2083 technique may support approximately 27 Mbps 2084 channel data rate for a 6,000 kHz RF channel. 2085 The value of this object is fixed for a given= 2086 order 2087 of the modulation technique." 2088 ::=3D { productClassEntry 6} 2090 rfChannelModulationType OBJECT-TYPE 2091 SYNTAX OBJECT IDENTIFIER 2092 ACCESS read-only 2093 STATUS mandatory 2094 DESCRIPTION 2095 "The value of this object identifies the type 2096 of RF channel modulation technique used for= 2097 this 2098 digital product class. For example, the 2099 RF modulation technique supported for this= 2100 product 2101 class is QPSK. The value of this object is 2102 fixed for a given 2103 RF channel type associated with a given 2104 digital product class." 2105 ::=3D { productClassEntry 7 } 2107 rfChannelDesiredModulationOrder OBJECT-TYPE 2108 SYNTAX INTEGER (0..65535) 2109 ACCESS read-only 2110 STATUS mandatory 2111 DESCRIPTION 2112 "The value of this object identifies the desired 2113 modulation order for the RF channel supported= 2114 for 2115 this product class. The value is expressed 2116 as the exponent of a power of two. For= 2117 example, 2118 the desired modulation order for the RF channel 2119 may be 8 (e.g. 64QAM)." 2120 ::=3D { productClassEntry 8} 2122 rfChannelModulationMinOrder OBJECT-TYPE 2123 SYNTAX INTEGER (0..65535) 2124 ACCESS read-only 2125 STATUS mandatory 2126 DESCRIPTION 2127 "The value of this object identifies the minimum 2128 modulation order supported for the RF channel 2129 associated with the digital product class. 2130 For example, the minimum Quadrature Amplitude 2132 Common Spectrum Management Interface MIB June 13,1996 2134 Modulation (QAM) order that may be supported= 2135 for 2136 this RF channel is 16QAM. The 2137 rfChannelModulationMinOrder 2138 and the rfChannelModulationMaxOrder have the= 2139 same 2140 values when the modulation order cannot changed 2141 for this RF channel type. The value of this 2142 object is fixed for a given RF channel type 2143 associated with a digital product class." 2144 ::=3D { productClassEntry 9 } 2146 rfChannelModulationMaxOrder OBJECT-TYPE 2147 SYNTAX INTEGER (0..65535) 2148 ACCESS read-only 2149 STATUS mandatory 2150 DESCRIPTION 2151 "The value of this object identifies the maximum 2152 modulation order supported for the RF channel 2153 associated with the digital product class. 2154 For example, the maximum Quadrature Amplitude 2155 Modulation (QAM) order that may be supported= 2156 for 2157 this RF channel is 256QAM. The= 2158 rfChannelModulationMinOrder 2159 and the rfChannelModulationMaxOrder have the= 2160 same 2161 values when the modulation order cannot be= 2162 changed 2163 for this RF channel type. The value of this 2164 object is fixed for a given RF channel type 2165 associated with a digital product class." 2166 ::=3D { productClassEntry 10 } 2168 rfChannelModulationOrderStepSize OBJECT-TYPE 2169 SYNTAX INTEGER (0..65535) 2170 ACCESS read-only 2171 STATUS mandatory 2172 DESCRIPTION 2173 "The value of this object identifies the minimum 2174 step size supported for modifying the RF 2175 modulation order. The value is expressed 2176 as the exponent of a power of two. For= 2177 example, 2178 the minimum step size that may be used to= 2179 change an 2180 existing modulation order (e.g., 32QAM) is 4. 2181 Thus, in this case, the modulation order may be= 2182 changed 2183 to 16QAM, 64QAM or 256QAM." 2184 ::=3D { productClassEntry 11 } 2186 Common Spectrum Management Interface MIB June 13,1996 2188 rfChannelMinFrequency OBJECT-TYPE 2189 SYNTAX INTEGER (0..4294967295) 2190 ACCESS read-only 2191 STATUS mandatory 2192 DESCRIPTION 2193 "The value of this object identifies the minimum 2194 radio carrier frequency supported for the RF 2195 spectrum channel associated with the digital 2196 product class. 2197 The value of this object is specified in kHz. 2198 For example, the minimum RF carrier frequency 2199 that may be supported for the RF spectrum= 2200 channel 2201 is 54,000 kHz. The rfChannelMaxFrequency and= 2202 the 2203 rfChannelMinFrequency have the same values when 2204 the carrier frequency cannot be changed for= 2205 this RF 2206 channel type. The value of this object is fixed= 2207 for 2208 a given RF channel type associated with a= 2209 digital 2210 product class." 2211 ::=3D { productClassEntry 12 } 2213 rfChannelMaxFrequency OBJECT-TYPE 2214 SYNTAX INTEGER (0..4294967295) 2215 ACCESS read-only 2216 STATUS mandatory 2217 DESCRIPTION 2218 "The value of this object identifies the maximum 2219 radio carrier frequency supported for the RF 2220 spectrum channel associated with the digital 2221 product class. 2222 The value of this object is specified in kHz. 2223 For example, the maximum RF carrier frequency 2224 that may be supported for the RF spectrum= 2225 channel 2226 is 750,000 kHz. The rfChannelMaxFrequency and= 2227 the 2228 rfChannelMinFrequency have the same values when= 2229 the 2230 carrier frequency cannot be changed for this RF 2231 channel type. The value of this object is fixed 2232 for a given RF channel type associated 2233 with a digital product class." 2234 ::=3D { productClassEntry 13 } 2236 rfChannelFrequencySpectrumStepSize OBJECT-TYPE 2237 SYNTAX INTEGER (0..4294967295) 2238 ACCESS read-only 2239 STATUS mandatory 2240 DESCRIPTION 2241 "The value of this object identifies the minimum 2242 step size that can be used to change the 2243 carrier frequency 2245 Common Spectrum Management Interface MIB June 13,1996 2247 of the RF channel associated with the digital 2248 product class. The value is expressed in kHz. 2249 Typically, the step size is less than 250 kHz 2250 in the forward direction, i.e., in the 2251 network-to-subscriber direction and less 2252 than 100 kHz in the reverse direction, 2253 i.e., in the subscriber-to-network 2254 direction." 2255 ::=3D { productClassEntry 14 } 2257 rfChannelMinimumPowerLevel OBJECT-TYPE 2258 SYNTAX INTEGER 2259 ACCESS read-only 2260 STATUS mandatory 2261 DESCRIPTION 2262 "The value of this object indicates the minimum 2263 transmit power level setting allowed for the RF 2264 channel associated with the digital product 2265 class. The power level is expressed in dBmV. 2266 For example, the minimum power level that may 2267 be supported for the RF channel is 20 dBmV. 2268 If the rfChannelMinimumPowerLevel and 2269 rfChannelMaximumPowerLevel have the same 2270 values then the power level is fixed for this= 2271 RF 2272 channel and cannot be changed by the SMA. For= 2273 the 2274 forward RF spectrum direction, the value of= 2275 this 2276 object indicates the minimum transmit power= 2277 level 2278 measured at the Distribution Hub Equipment in= 2279 the HFC 2280 subnetwork. For the reverse RF spectrum= 2281 direction, 2282 the value of this object indicates the minimum 2283 transmit power level measured at the cable= 2284 modem at 2285 the subscriber's premises. The value of this= 2286 object 2287 is fixed for a given RF channel associated with= 2288 a 2289 digital product class." 2290 ::=3D { productClassEntry 15} 2292 rfChannelMaximumPowerLevel OBJECT-TYPE 2293 SYNTAX INTEGER 2294 ACCESS read-only 2295 STATUS mandatory 2296 DESCRIPTION 2297 "The value of this object indicates the maximum 2298 transmit power level setting allowed for the RF 2299 channel associated with a given digital product 2300 class. The power level is expressed in dBmV. 2302 Common Spectrum Management Interface MIB June 13,1996 2304 For example, the maximum power level that may 2305 be supported for this RF channel is 20 dBmV. 2306 If the rfChannelMinimumPowerLevel and 2307 rfChannelMaximumPowerLevel have the same 2308 values then the power level is fixed and 2309 cannot be adjusted for this RF channel. For the 2310 forward RF spectrum direction, the value of= 2311 this 2312 object indicates the maximum transmit power= 2313 level 2314 measured at the Distribution Hub Equipment in= 2315 the 2316 HFC subnetwork. For the reverse 2317 RF spectrum direction, 2318 the value of this object indicates the maximum 2319 transmit power level measured at the cable= 2320 modem at 2321 the subscriber's premises. The value of this= 2322 object 2323 is fixed for a given RF channel associated with= 2324 a 2325 digital product class." 2326 ::=3D { productClassEntry 16 } 2328 rfChannelPowerLevelStepSize OBJECT-TYPE 2329 SYNTAX INTEGER (0..65535) 2330 ACCESS read-only 2331 STATUS mandatory 2332 DESCRIPTION 2333 "The value of this object indicates the minimum 2334 step size (in absolute value) supported for the 2335 power level setting. The value is 2336 expressed in dBmV. For example, the step size 2337 may be 1 dBmV by which the power level may be 2338 changed." 2339 ::=3D { productClassEntry 17 } 2341 rfSliceBandEdgeAttenuation OBJECT-TYPE 2342 SYNTAX INTEGER (0..65535) 2343 ACCESS read-only 2344 STATUS mandatory 2345 DESCRIPTION 2346 "The value of this object indicates the relative= 2348 power at the edge of the RF spectrum slice pass 2349 bandwidth. The power level is measured= 2350 relative 2351 to the transmit power level of the slice pass= 2352 band. 2353 The value is expressed in dB. The value of this 2354 object is assumed to be independent of the pass= 2356 band of the typical RF spectrum slice supported 2357 for this digital product class. The value of 2358 this object should be measured in 2359 a 10 kHz band whose center frequency is at the= 2361 frequency of interest. For example, the power 2362 measured in a 10 kHz band centered at the 30 MHz 2364 Common Spectrum Management Interface MIB June 13,1996 2366 is 20 dB below transmit the power measured in= 2367 the 2368 same 10 kHz band centered at the slice pass= 2369 band 2370 center frequency of 27 MHz." 2371 ::=3D { productClassEntry 18 } 2373 rfSliceSkirtAttenuation OBJECT-TYPE 2374 SYNTAX INTEGER (0..65535) 2375 ACCESS read-only 2376 STATUS mandatory 2377 DESCRIPTION 2378 "The value of this object indicates the power 2379 level at the midpoint in the RF spectrum slice 2380 skirt or transition band relative to the= 2381 transmit 2382 power level at the slice pass band. The skirt= 2384 details the roll-off characteristics between= 2385 the 2386 central portion of the RF spectrum slice and= 2387 the 2388 edge of the slice. The value is expressed in= 2389 dB. 2390 The value of this object is assumed to be 2391 independent of the position of the RF spectrum 2392 slice in the RF spectrum. The value of this 2393 object should be measured in a 10 2394 kHz band whose center frequency is at 2395 the frequency of interest. For example, 2396 the power measured in a 10 kHz band centered 2397 at thefrequency such as 32 MHz is 40 dB below 2398 the transmit power measured in the same 2399 10 kHz band centered at the slice pass 2400 band center frequency of 27 MHz." 2401 ::=3D { productClassEntry 19 } 2403 rfSliceEnvelopeEdgeAttenuation OBJECT-TYPE 2404 SYNTAX INTEGER (0..65535) 2405 ACCESS read-only 2406 STATUS mandatory 2407 DESCRIPTION 2408 "The value of this object indicates the power 2409 level at the edge of the RF spectrum slice 2410 envelope relative to the transmit power level 2411 at the slice pass band. The value is expressed= 2412 in 2413 dB. The value of the object is assumed to be 2414 independent of the position of the RF spectrum 2415 slice on the RF spectrum. The value of this 2416 object should be measured in a 10 kHz band= 2417 center 2418 frequency is at the frequency of interest. 2419 For example, the power measured in a 10 kHz 2420 band centered at the frequency 2421 such as 35 MHz is 60 dB below the transmit= 2422 power 2423 measured in the same 10 kHz band centered at= 2424 the 2425 slice pass band center frequency of 27 MHz." 2427 Common Spectrum Management Interface MIB June 13,1996 2429 ::=3D { productClassEntry 20 } 2431 rfSliceSkirtMidBandwidth OBJECT-TYPE 2432 SYNTAX INTEGER (0..65535) 2433 ACCESS read-only 2434 STATUS mandatory 2435 DESCRIPTION 2436 "The value of this object indicates the= 2437 bandwidth 2438 of the mid point of the RF spectrum slice skirt 2439 (also referred to as transition band). It is= 2440 the 2441 absolute frequency difference between the slice 2442 edge frequency and the skirt's midpoint= 2443 frequency. 2444 The skirt details the roll-off characteristics 2445 between the central portion of the RF spectrum= 2447 slice and the edge of the slice. The value 2448 is expressed in kHz. For example, 2449 the value may be 2,000 kHz." 2450 ::=3D { productClassEntry 21 } 2452 rfSliceSkirtBandwidth OBJECT-TYPE 2453 SYNTAX INTEGER (0..65535) 2454 ACCESS read-only 2455 STATUS mandatory 2456 DESCRIPTION 2457 "The value of this object indicates the= 2458 bandwidth 2459 of the skirt at the edge of the RF spectrum= 2460 slice 2461 envelope. It is the absolute frequency= 2462 difference 2463 between the slice edge frequency and the= 2464 beginning 2465 of the spectrum slice floor (also referred to= 2466 as 2467 stop band). The value is expressed in kHz. 2468 For example, the value may be 5,000 kHz." 2469 ::=3D { productClassEntry 22 } 2471 rfSliceSkirtSensitivity OBJECT-TYPE 2472 SYNTAX INTEGER (0..65535) 2473 ACCESS read-only 2474 STATUS mandatory 2475 DESCRIPTION 2476 "The value of this object indicates the relative 2477 power level sensitivity of the typical RF= 2478 spectrum 2479 slice associated with the digital product= 2480 class. 2481 It provides the tolerance of the slice to the= 2482 power 2483 received from all interfering signals from the= 2485 skirts of the adjacent spectrum slices 2486 associated with 2488 Common Spectrum Management Interface MIB June 13,1996 2490 different product classes measured relative to= 2491 the 2492 receive power level of the slice pass band. 2493 The 2494 value is expressed in dB. The value of this= 2495 object 2496 is assumed to be independent of the position 2497 of the RF slice in the RF spectrum. 2498 The value of this object 2499 should be measured in a 10 kHz band whose= 2500 center 2501 frequency is at the frequency of interest. For= 2503 example, the power measured in a 10 kHz 2504 band centered at 32 MHz is 30 dB below the 2505 receive power measured in the same 10 kHz 2506 band centered at the slice pass 2507 band frequency at 27 MHz." 2508 ::=3D { productClassEntry 23 } 2510 rfSliceEdgeSensitivity OBJECT-TYPE 2511 SYNTAX INTEGER (0..65535) 2512 ACCESS read-only 2513 STATUS mandatory 2514 DESCRIPTION 2515 "The value of this object indicates the relative 2516 power level sensitivity of the RF spectrum= 2517 slice 2518 associated with this digital product class. 2519 It provides the tolerance level of the slice= 2520 from 2521 the power received from all interfering signals 2522 from the adjacent spectrum slices associated= 2523 with 2524 different product classes measured relative 2525 to the receive signal power level of the slice= 2526 pass 2527 band. The value is expressed in dB. The value= 2528 of 2529 this object is assumed to be independent of the 2530 position of the RF spectrum slice in the RF 2531 spectrum. The value of this object should be 2532 measured in a 10 kHz band whose center= 2533 frequency 2534 is at the frequency of interest. For example, 2535 the power measured in a 10 kHz band centered 2536 at 35 MHz is 60 dB below the receive power 2537 measured in the same 10 kHz band 2538 centered at the slice pass band 2539 frequency at 27 MHz." 2540 ::=3D { productClassEntry 24 } 2542 Common Spectrum Management Interface MIB June 13,1996 2544 -- RF Spectrum Slice Configuration Table 2546 -- This table contains the configuration and state 2547 -- information of a Radio Frequency (RF) spectrum slice 2548 -- associated with a given digital product class supported 2549 -- in the logical Hybrid Fiber Coax (HFC) subnetwork. 2551 -- For the purpose of RF spectrum management, RF spectrum 2552 -- slice is defined as the RF frequency spectrum interval 2553 -- associated with a group of fine-grained modulators. 2554 -- An RF spectrum slice contains a single or multiple 2555 -- RF channels of the same type allocated to a given product 2556 -- class such as multiple voice telephony channels in a 2557 -- POTS product class. 2559 -- This table can be used to create, delete or modify 2560 -- a uni-directional RF spectrum slice 2561 -- and the related configurable parameters for a given 2562 -- digital product class supported in a logical 2563 -- HFC subnetwork. In order to create, delete or modify 2564 -- an RF spectrum slice, this table uses the RF channel 2565 -- configuration information associated with a given digital 2566 -- product class provided in the productClassTable to= 2567 determine 2568 -- the configuration parameter consistency and the 2569 -- allowed ranges of RF channel configuration parameters. 2571 -- This table can be used to configure an RF spectrum 2572 -- slice containing a single RF channel (i.e., a 2573 -- single RF carrier) or multiple RF channels (i.e., 2574 -- multiple RF carriers) depending on the RF technology 2575 -- supported for a given digital product class. 2577 -- Implementation of this group is mandatory 2578 -- if providing RF spectrum management. 2580 rfSpectrumSliceConfigTable OBJECT-TYPE 2581 SYNTAX SEQUENCE OF RfSpectrumSliceConfigEntry 2582 ACCESS not-accessible 2583 STATUS mandatory 2584 DESCRIPTION 2585 "This table contains configuration and state 2586 information of the RF spectrum slice or RF= 2587 channel 2588 depending on the RF technology supported for a= 2589 given 2591 Common Spectrum Management Interface MIB June 13,1996 2593 digital product class in the logical HFC= 2594 subnetwork." 2595 ::=3D { csmiMIBObjects 7 } 2597 rfSpectrumSliceConfigEntry OBJECT-TYPE 2598 SYNTAX RfSpectrumSliceConfigEntry 2599 ACCESS not-accessible 2600 STATUS mandatory 2601 DESCRIPTION 2602 "An entry in the RF spectrum slice configuration 2603 table. This entry is used to model a= 2604 uni-directional 2605 RF spectrum slice containing a single or multiple 2606 RF channels. To create, delete or modify an RF 2607 spectrum slice associated with a given digital 2608 product class in a logical HFC subnetwork, 2609 the following procedures are used: 2611 RF spectrum slice establishment 2613 (1)The Spectrum Management Application (SMA)= 2614 creates 2615 an RF spectrum slice entry in the 2616 rfSpectrumSliceConfigTable 2617 by initially setting rfSpectrumSliceEntryStatus= 2618 to 2619 createRequest. The requested entry is checked 2620 for consistency against the RF channel= 2621 parameters 2622 defined in the productClassTable for a given 2623 digital 2624 product class. The create request may fail for 2625 the following reasons: 2626 - The requested RF spectrum slice is already 2627 in use. 2628 - The frequency spectrum of the requested RF 2629 spectrum slice overlaps with or very close 2630 to an existing RF spectrum slice. 2631 - The requested RF spectrum is unavailable. 2632 - The requested RF spectrum slice configuration 2633 is not supported by the Spectrum 2634 Management Proxy Agent (SMPA). 2635 Otherwise, the SMPA creates a row and reserves 2636 the RF spectrum slice for a given digital= 2637 product 2638 class on the specific logical HFC subnetwork. 2639 The SMA may use the RF channel configuration 2640 parameter values such as the desired modulation= 2642 order, carrier frequency, and power level= 2643 values 2644 defined in the productClassTable for a given 2645 digital product. 2646 (2)The SMA activates the RF spectrum slice by= 2647 setting 2648 the rfSpectrumSliceEntrystatus to valid(1). 2649 If 2650 this set is successful, the SMPA has reserved= 2651 the 2652 resources to satisfy the requested RF spectrum 2653 slice configuration parameters. 2655 Common Spectrum Management Interface MIB June 13,1996 2657 (3)The SMA turns on the= 2658 rfSpectrumSliceAdminStatus 2659 to up(1) enabling the RF spectrum slice 2660 associated with a given digital product class 2661 for use. 2663 RF spectrum slice retirement 2665 An RF spectrum slice is released by setting the 2666 rfSpectrumSliceEntrysStatus to invalid(4), and the 2667 SMPA may release all associated resources= 2668 associated 2669 with that RF spectrum slice in the logical HFC 2670 subnetwork. 2672 RF spectrum slice reconfiguration 2674 (1)The SMA modifies an RF spectrum slice= 2675 configuration 2676 parameter(s) by initially setting the 2677 rfSpectrumSliceAdminStatus to down(2) and then= 2679 setting the configuration parameter(s) such as= 2680 the 2681 rfSpectrumSliceUpperFrequency to the desired 2682 value(s). The configuration change request may= 2684 fail for the following reasons: 2685 - The requested RF spectrum slice configuration= 2686 is 2687 not supported by the SMPA. 2688 - The requested configuration change interferes 2689 with an existing RF spectrum slice= 2690 configuration 2691 (e.g., the requested upper frequency overlaps 2692 with an existing RF spectrum slice or RF= 2693 channel 2694 position). Otherwise, the SMPA makes the desired= 2696 configuration changes. 2697 (2)The SMA then sets the= 2698 rfSpectrumSliceAdminStatus to 2699 up(1) enabling the modified RF spectrum slice= 2701 associated with a given digital product class= 2702 for 2703 use." 2704 INDEX {rfSpectrumSliceHfcNetworkIndex, 2705 rfSpectrumSliceProductClassIndex, 2706 rfSpectrumSliceConfigIndex } 2707 ::=3D { rfSpectrumSliceConfigTable 1} 2709 RfSpectrumSliceConfigEntry ::=3D SEQUENCE { 2710 rfSpectrumSliceHfcNetworkIndex 2711 INTEGER, 2712 rfSpectrumSliceProductClassIndex 2713 INTEGER, 2714 rfSpectrumSliceConfigIndex 2715 INTEGER, 2716 rfSpectrumSliceOperStatus 2718 Common Spectrum Management Interface MIB June 13,1996 2720 INTEGER, 2721 rfSpectrumSliceAdminStatus 2722 INTEGER, 2723 rfSpectrumSliceLastChange 2724 TimeTicks, 2725 rfSpectrumSliceModulationOrder 2726 INTEGER, 2727 rfSpectrumSliceUpperFrequency 2728 INTEGER, 2729 rfSpectrumSliceLowerFrequency 2730 INTEGER, 2731 rfSpectrumSlicePowerLevel 2732 INTEGER, 2733 rfSpectrumSliceEntryStatus 2734 EntryStatus 2735 } 2737 rfSpectrumSliceHfcNetworkIndex OBJECT-TYPE 2738 SYNTAX INTEGER (1..65535) 2739 ACCESS read-only 2740 STATUS mandatory 2741 DESCRIPTION 2742 "The value of this object identifies the logical 2743 HFC subnetwork for which this entry contains 2744 RF spectrum slice information. The value of= 2745 this 2746 object for a specific logical HFC subnetwork 2747 has the same value as the= 2748 logicalHfcSubnetworkIndex 2749 defined in logicalHfcSubnetworkTable for 2750 the same logical HFC subnetwork." 2751 ::=3D { rfSpectrumSliceConfigEntry 1} 2753 rfSpectrumSliceProductClassIndex OBJECT-TYPE 2754 SYNTAX INTEGER (1..65535) 2755 ACCESS read-only 2756 STATUS mandatory 2757 DESCRIPTION 2758 "The value of this object identifies the product 2759 class type supported in a specific logical HFC 2760 subnetwork for which this entry contains 2761 RF spectrum slice information. The value of= 2762 this 2763 object for a specific product class type has= 2764 the 2765 same value as the productClassIndex defined in= 2767 productClassTable for the same product class= 2768 type 2769 supported in the logical HFC subnetwork." 2770 ::=3D { rfSpectrumSliceConfigEntry 2} 2772 Common Spectrum Management Interface MIB June 13,1996 2774 rfSpectrumSliceConfigIndex OBJECT-TYPE 2775 SYNTAX INTEGER (1..4294967295) 2776 ACCESS read-only 2777 STATUS mandatory 2778 DESCRIPTION 2779 "The value of this object identifies the RF 2780 spectrum slice used for the digital product= 2781 class 2782 supported in the logical HFC subnetwork. 2783 The RF spectrum slice is configured as a uni- 2784 directional slice." 2785 ::=3D { rfSpectrumSliceConfigEntry 3} 2787 rfSpectrumSliceOperStatus OBJECT-TYPE 2788 SYNTAX INTEGER { 2789 up(1), 2790 down(2), 2791 unknown(3) 2792 } 2793 ACCESS read-only 2794 STATUS mandatory 2795 DESCRIPTION 2796 "The value of this object indicates the current 2797 operational status of this RF spectrum slice. 2798 The value up(1) indicates that the portion or= 2799 all 2800 of the RF spectrum slice is currently= 2801 operational. 2802 The value down(2) indicates all of the RF= 2803 spectrum 2804 slice is not operational. Therefore, for the 2805 RF spectrum slice containing multiple 2806 RF channels, the value down(2) indicates that= 2807 all 2808 RF channels contained in the RF spectrum slice 2809 are not operational and the value up(1)= 2810 indicates 2811 that either all or at least one of the RF= 2812 channels 2813 are operational. The unknown state indicates 2814 that the status of this RF spectrum slice= 2815 cannot 2816 be determined." 2817 ::=3D { rfSpectrumSliceConfigEntry 4} 2819 rfSpectrumSliceAdminStatus OBJECT-TYPE 2820 SYNTAX INTEGER { 2821 up(1), 2822 down(2), 2823 testing(3) 2824 } 2825 ACCESS read-write 2827 Common Spectrum Management Interface MIB June 13,1996 2829 STATUS mandatory 2830 DESCRIPTION 2831 "The value of this object indicates the 2832 desired administrative status of this 2833 RF spectrum slice. The value up(1) indicates 2834 that this RF spectrum slice is enabled and the 2835 value down(2) indicates that it is disabled. 2836 Therefore, for the RF spectrum slice containing= 2838 multiple RF channels, the value down(2)= 2839 indicates 2840 that all RF channels contained in the RF= 2841 spectrum 2842 slice are disabled. The value up(1) indicates 2843 that either all or at least one of the RF= 2844 channels 2845 are made operational. The value 2846 testing(3) indicates that one or few of the RF= 2848 channels contained in this RF spectrum slice is 2849 undergoing testing." 2850 DEFVAL { down } 2851 ::=3D { rfSpectrumSliceConfigEntry 5} 2853 rfSpectrumSliceLastChange OBJECT-TYPE 2854 SYNTAX TimeTicks 2855 ACCESS read-only 2856 STATUS mandatory 2857 DESCRIPTION 2858 "The value of MIB II's sysUpTime object 2859 at the time this RF spectrum slice entered its 2860 current operational state. If the current 2861 state was entered prior to the last 2862 re-initialization of the Spectrum Management 2863 Proxy Agent (SMPA), then this object contains 2864 a zero value." 2865 ::=3D { rfSpectrumSliceConfigEntry 6} 2867 rfSpectrumSliceModulationOrder OBJECT-TYPE 2868 SYNTAX INTEGER (0..65535) 2869 ACCESS read-write 2870 STATUS mandatory 2871 DESCRIPTION 2872 "This object is used to configure the modulation 2873 order for the RF channels in the RF spectrum= 2874 slice. 2875 The modulation order may be the same as the 2876 rfChannelDesiredModulationOrder in the 2877 productClassTable. The value of the 2878 rfSpectrumSliceModulationOrder must lie between 2879 the values of the rfChannelModulationMinOrder 2880 and the rfChannelModulationMaxOrder defined in 2882 Common Spectrum Management Interface MIB June 13,1996 2884 productClassTable for the RF channel supported= 2885 for 2886 the same digital product class in the same= 2887 logical 2888 HFC subnetwork. When the agent configures the= 2890 modulation order, it recomputes the RF channel 2891 data rate and modifies the rfChannelDataRate 2892 value in the productClassTable." 2893 ::=3D { rfSpectrumSliceConfigEntry 7 } 2895 rfSpectrumSliceUpperFrequency OBJECT-TYPE 2896 SYNTAX INTEGER (0..4294967295) 2897 ACCESS read-write 2898 STATUS mandatory 2899 DESCRIPTION 2900 "This object is used to configure the upper 2901 frequency bound of the RF spectrum slice. 2902 The value of the rfSpectrumSliceUpperFrequency= 2904 must lie between the values of the 2905 rfChannelMinFrequency and the 2906 rfChannelMaxFrequency defined in= 2907 productClassTable 2908 for the RF channel supported for the same= 2909 digital 2910 product class in the same logical HFC= 2911 subnetwork. 2912 The difference between the value of this object= 2913 and 2914 the value of rfSpectrumSliceLowerFrequency must= 2915 be 2916 equal to or greater than the value of= 2917 rfChannelSize 2918 defined in productClassTable for the RF channel= 2920 supported for the same digital product class in= 2921 the 2922 same logical HFC subnetwork." 2923 ::=3D { rfSpectrumSliceConfigEntry 8} 2925 rfSpectrumSliceLowerFrequency OBJECT-TYPE 2926 SYNTAX INTEGER (0..4294967295) 2927 ACCESS read-write 2928 STATUS mandatory 2929 DESCRIPTION 2930 "This object is used to configure the lower 2931 frequency bound of the RF spectrum slice. 2932 The value of the 2933 rfSpectrumSliceLowerFrequency must lie between 2934 the values of the rfChannelMinFrequency and 2935 the rfChannelMaxFrequency defined in 2936 productClassTable for the RF channel 2937 supported for the same digital product class in= 2938 the 2939 same logical HFC subnetwork. 2940 The difference between the value of this object= 2941 and 2942 the value of rfSpectrumSliceUpperFrequency must= 2943 be 2945 Common Spectrum Management Interface MIB June 13,1996 2947 equal to or greater than the value of= 2948 rfChannelSize 2949 defined in productClassTable for the RF channel= 2951 supported for the same digital product class in= 2952 the 2953 same logical HFC subnetwork." 2954 ::=3D { rfSpectrumSliceConfigEntry 9} 2956 rfSpectrumSlicePowerLevel OBJECT-TYPE 2957 SYNTAX INTEGER 2958 ACCESS read-write 2959 STATUS mandatory 2960 DESCRIPTION 2961 "This object is used to configure the absolute= 2962 RF 2963 power level of the RF channels contained within= 2964 the 2965 RF spectrum slice. The value is expressed 2966 in units of dBmV. This object is used for= 2967 coarse 2968 adjustment of the RF power level, and it is 2969 not intended to override the finetuning of 2970 the automatic power level adjustments of 2971 the equipment. 2972 The value of the rfSpectrumSlicePowerLevel must 2973 lie between the values of the 2974 rfChannelMinimumPowerLevel 2975 and the rfChannelMaximumPowerLevel defined in 2976 the productClassTable for the RF channel 2977 type supported for the same digital product= 2978 class 2979 in the same logical HFC subnetwork. For the 2980 forward RF 2981 spectrum slice, this object is used to= 2982 configure 2983 the power level of the transmitter at the 2984 Distribution Hub Equipment and for the reverse= 2986 RF spectrum slice, this object is used to 2987 configure the power level of the transmitter 2988 at the subscriber's premises." 2989 ::=3D { rfSpectrumSliceConfigEntry 10} 2991 rfSpectrumSliceEntryStatus OBJECT-TYPE 2992 SYNTAX EntryStatus 2993 ACCESS read-write 2994 STATUS mandatory 2995 DESCRIPTION 2996 "This object is used to create, delete or 2997 modify a row in this table. To create a 2998 a new RF spectrum slice, this object is= 2999 initially 3000 set to 'createRequest'. After completion of= 3001 the 3002 configuration of the new entry, the spectrum 3003 manager must set the appropriate instance 3004 of this object to the value valid(1) or 3005 aborts, setting this object to invalid(4). 3006 This object must not be set to 3007 'active' unless the following columnar objects 3009 Common Spectrum Management Interface MIB June 13,1996 3011 exist in this row: 3012 rfSpectrumSliceAdminStatus, 3013 rfSpectrumSliceModulationOrder, 3014 rfSpectrumSliceUpperFrequency, 3015 rfSpectrumSliceLowerFrequency 3016 rfSpectrumSlicePowerLevel. 3017 To enable an RF spectrum slice for use, the 3018 rfSpectrumSliceAdminStatus is set to 'up'. 3019 To delete an existing entry in this table, 3020 the manager must set the appropriate 3021 instance of this object to the value= 3022 invalid(4). 3023 Creation of an instance of this object has the 3024 effect of creating the supplemental object 3025 instances to complete the conceptual row. 3026 An existing instance of this entry cannot 3027 be created. If circumstances occur which 3028 cause an entry to become invalid, the agent 3029 modifies the value of the appropriate instance= 3031 of this object to invalid(4). Whenever, 3032 the value of this object for a particular 3033 entry becomes invalid(4), the conceptual 3034 row for that instance may be removed from 3035 the table at any time, either 3036 immediately or subsequently." 3037 DEFVAL { valid } 3038 ::=3D { rfSpectrumSliceConfigEntry 11} 3040 Common Spectrum Management Interface MIB June 13,1996 3042 -- The RF Spectrum Management MIB Trap Module 3044 -- Enterprise-specific traps for use with the 3045 -- RF spectrum management. 3047 -- Trap definitions that follow are specified compliant with 3048 -- the SMI RFC1155, as amended by the extensions specified 3049 -- for concise MIB specifications RFC1212 and 3050 -- using the conventions 3051 -- for defining event notifications RFC1215. 3053 -- Implementation of these traps are mandatory 3054 -- if providing RF spectrum management. 3056 rfSpectrumChannelStatusChange TRAP-TYPE 3057 ENTERPRISE twcable 3058 VARIABLES {rfSpectrumSliceHfcNetworkIndex, 3059 rfSpectrumSliceProductClassIndex, 3060 rfSpectrumSliceConfigIndex, 3061 rfSpectrumSliceOperStatus, 3062 rfSpectrumSliceAdminStatus } 3063 DESCRIPTION 3064 "An rfSpectrumChannelStatusChange trap indicates= 3065 the 3066 change in the operational status of the RF= 3067 spectrum 3068 channel associated with a given product class in a= 3070 logical HFC subnetwork. This trap is used for= 3071 those RF 3072 spectrum slices containing a single RF channel= 3073 only. 3074 Therefore, this trap indicates the status of an RF= 3076 channel only. The trap may indicate an RF channel 3077 failure." 3078 ::=3D 1 3080 rfSpectrumSliceConfigTableEntryStatus TRAP-TYPE 3081 ENTERPRISE twcable 3082 VARIABLES 3083 {rfSpectrumSliceHfcNetworkIndex, 3085 rfSpectrumSliceProductClassIndex, 3086 rfSpectrumSliceConfigIndex, 3087 rfSpectrumSliceUpperFrequency, 3088 rfSpectrumSliceLowerFrequency, 3090 rfSpectrumSliceModulationOrder, 3091 rfSpectrumSlicePowerLevel, 3092 rfSpectrumSliceOperStatus, 3093 rfSpectrumSliceAdminStatus, 3094 rfSpectrumSliceEntryStatus 3096 Common Spectrum Management Interface MIB June 13,1996 3098 } 3099 DESCRIPTION 3100 "An rfSpectrumSliceConfigTableEntryStatus trap 3101 indicates that an RF spectrum slice is created, 3102 deleted, or modified for a given product class 3103 at this logical HFC subnetwork. The variables 3104 included in the trap identify the new, deleted, 3105 or modified RF spectrum slice and the associated 3106 configuration parameters for a given digital 3107 service class in a logical HFC subnetwork." 3108 ::=3D 2 3110 rfSpectrumSliceBandwidthRequest TRAP-TYPE 3111 ENTERPRISE twcable 3112 VARIABLES 3113 {rfSpectrumSliceHfcNetworkIndex, 3115 rfSpectrumSliceProductClassIndex, 3116 rfSpectrumSliceConfigIndex, 3117 rfSpectrumSliceUpperFrequency, 3118 rfSpectrumSliceLowerFrequency, 3120 rfSpectrumSliceModulationOrder, 3121 rfSpectrumSlicePowerLevel, 3122 rfSpectrumSliceOperStatus, 3123 rfSpectrumSliceAdminStatus, 3124 rfSpectrumSliceEntryStatus 3125 } 3126 DESCRIPTION 3127 "An rfSpectrumSliceBandwidthRequest trap indicates= 3128 that 3129 more bandwidth is needed to support the given= 3130 product 3131 class at this logical HFC subnetwork. The= 3132 variables 3133 included in the trap identify the RF spectrum= 3134 slice 3135 which needs more bandwidth. It is up to the= 3136 discretion 3137 of the SMA to allocate more bandwidth to a given 3138 product class supported in the logical 3139 HFC subnetwork." 3140 ::=3D 3 3142 rfSpectrumSliceShiftToUpperFrequency TRAP-TYPE 3143 ENTERPRISE twcable 3144 VARIABLES 3145 {rfSpectrumSliceHfcNetworkIndex, 3147 rfSpectrumSliceProductClassIndex, 3148 rfSpectrumSliceConfigIndex, 3149 rfSpectrumSliceUpperFrequency, 3150 rfSpectrumSliceLowerFrequency, 3152 rfSpectrumSliceModulationOrder, 3153 rfSpectrumSlicePowerLevel, 3154 rfSpectrumSliceOperStatus, 3155 rfSpectrumSliceAdminStatus, 3156 rfSpectrumSliceEntryStatus 3157 } 3159 Common Spectrum Management Interface MIB June 13,1996 3161 DESCRIPTION 3162 "An rfSpectrumSliceShiftToUpperFrequency trap= 3163 indicates 3164 that the RF spectrum slice upper frequency needs= 3165 to be 3166 shifted to a higher frequency. This may be because= 3167 of 3168 the performance degradation experienced by 3169 existing RF spectrum slice. The variables included= 3170 in 3171 the trap identify the RF spectrum slice whose= 3172 upper 3173 frequency needs to be shifted. It is up to the 3174 discretion of the SMA to reconfigure the RF= 3175 spectrum 3176 slice for a given product class supported in the 3177 logical HFC subnetwork." 3178 ::=3D 4 3180 rfSpectrumSliceShiftToLowerFrequency TRAP-TYPE 3181 ENTERPRISE twcable 3182 VARIABLES 3183 {rfSpectrumSliceHfcNetworkIndex, 3185 rfSpectrumSliceProductClassIndex, 3186 rfSpectrumSliceConfigIndex, 3187 rfSpectrumSliceUpperFrequency, 3188 rfSpectrumSliceLowerFrequency, 3190 rfSpectrumSliceModulationOrder, 3191 rfSpectrumSlicePowerLevel, 3192 rfSpectrumSliceOperStatus, 3193 rfSpectrumSliceAdminStatus, 3194 rfSpectrumSliceEntryStatus 3195 } 3196 DESCRIPTION 3197 "An rfSpectrumSliceShiftTo=C2owerFrequency trap= 3198 indicates 3199 that the RF spectrum slice lower frequency needs= 3200 to be 3201 shifted to a lower frequency. This may be because= 3202 of 3203 the performance degradation experienced by 3204 existing RF spectrum slice. The variables included= 3205 in 3206 the trap identify the RF spectrum slice whose= 3207 lower 3208 frequency needs to be shifted. It is up to the 3209 discretion of the SMA to reconfigure the RF= 3210 spectrum 3211 slice for a given product class supported in the 3212 logical HFC subnetwork." 3213 ::=3D 5 3215 END 3217 Common Spectrum Management Interface MIB June 13,1996 3219 11. Acknowledgments 3221 This document follows Time Warner Cable's "Spectrum Management 3222 Agent, Request for Information", sent out to vendors last 3223 September 14, 1994. The final draft (v 4.00) was completed on 3224 June 15, 1995, and it has been available for review and comments 3225 leading to the current version. 3227 It was produced by the HFC Spectrum Management Team from 3228 Cablelabs, Time Warner Cable, and Time Warner Communications: 3230 Masuma Ahmed, Chris Barnhouse, Gregory Haberl, Jay Vaughan, 3231 and Mario Vecchi. 3233 Special thanks to Gerry White of LANCity for the review of the 3234 final manuscript and many valuable comments, to Tom Williams of 3235 CableLabs for helpful discussions on RF issues especially on RF 3236 modulation techniques; to David Bartlett of Time Warner 3237 Communications for helpful review of the early draft; and to 3238 Gordon Bechtel of AT&T, Bill Corley of LANCity, Ken Craft of 3239 Tellabs, and Hal Roberts and Rob Cooper of ADC Telecommunications 3240 for their valuable contributions to the RF spectrum slice envelope 3241 characterization. 3243 Special thanks to the following individuals for their valuable 3244 technical input in the process to define this interface, 3245 including comments on the earlier drafts of this document. 3247 ADC Telecom: Rob Cooper, Hal Roberts, Greg Machler, Greg Anderson 3249 Anderson Consulting: Thomas Lotocki 3251 Antec: Michael Pritz 3253 AT&T: Gordon Bechtel, Mark Klerer, Jeff Fishburn, 3254 Mike Kaus, Paul Bezdek 3256 Com21: Mark Laubach, Randy Miyazaki 3258 Convergence Systems Incorporated: Terry Wright 3260 General Instruments: Geoff Woods, Pete Cona 3262 Hewlett Packard (HP): Ilja Bedner 3264 Integrated Network Corporation: Idris Vasiz 3266 LANCity: Gerry White, Bill Corley 3268 Common Spectrum Management Interface MIB June 13,1996 3270 Motorola: Eva Labowicz, Larry Lloyd, Mort Stern 3272 Northern Telecom/Bell Northern Research: Wade Carter, Colleen= 3273 Reichert 3275 Objective Systems Integrator: Andrew Lee, Terry Poindexter 3277 Phillips Broadband: Al Kernes, Goyo Strkic 3279 Scientific Atlanta: Andrew Meyer, Scott Hardin 3281 Toshiba: Steve Rasmussen, Steve Hori 3283 Tellabs: Larry Goldman, Ken Craft 3285 Time Warner: Ray Buckner, Paul Gemme, Louis Williamson 3287 Zenith Electronics: David Lin 3289 Common Spectrum Management Interface MIB June 13,1996 3291 12. References 3293 [1] V. Cerf,"IAB Recommendations for the Development of 3294 Internet Network Management Standards. Internet Working 3295 Group Request for Comments 1052". Network Information 3296 Center, SRI International, Menlo Park, California, April 3297 1988. 3299 [2] V. Cerf,"Report of the Second Ad Hoc Network Management 3300 Review Group, Internet Working Group Request for Comments 3301 1052". Network Information Center, SRI International, 3302 Menlo Park, California, August 1989. 3304 [3] McCloghrie, K., and M. Rose, Editors, "Structure and 3305 Identification of Management Information for TCP/IP-based 3306 internets, Internet Working Group Request for Comments 3307 1155". Network Information Center, SRI International, 3308 Menlo Park, California, May 1990. 3310 [4] McCloghrie, K., and M. Rose, Editors, "Management 3311 Information Base for TCP/IP-based internets, Internet 3312 Working Group Request for Comments 1156". Network 3313 Information Center, SRI International, Menlo Park, 3314 California, May 1990. 3316 [5] J. Case, F. Fedor, M. Schoffstall, and J. Davin, 3317 Editors, "Simple Network Management Protocol, Internet 3318 Working Group Request for Comments 1157". Network 3319 Information Center, SRI International, Menlo Park, 3320 California, May 1990. 3322 [6] McCloghrie, K., and M. Rose, Editors, "Management 3323 Information Base for Network Management of TCP/IP-based 3324 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 3325 Performance Systems International, March 1991. 3327 [7] Information Processing Systems - Open Systems 3328 Interconnection - Specification of Abstract Syntax 3329 Notation One (ASN.1), International Organization for 3330 Standardization. International Standard 8824, December 3331 1987. 3333 [8] Information Processing Systems - Open Systems 3334 Interconnection - Specification of Basic Encoding Rules 3335 for Abstract Syntax Notation One (ASN.1), International 3337 Common Spectrum Management Interface MIB June 13,1996 3339 Organization for Standardization. International Standard 3340 8825, December 1987. 3342 [9] McCloghrie, K., and M. Rose, Editors, "concise MIB 3343 Definitions, Internet Working Group Request for Comments 3344 1212". Network Information Center, SRI International, 3345 Menlo Park, California, March 1991. 3347 [10] M. Rose, Editors, "A Convention for Defining Traps for 3348 use with SNMP, Internet Working Group Request for 3349 Comments 1215". Network Information Center, SRI 3350 International, Menlo Park, California, March 1991. 3352 [11] B. Sklar, "Digital Communications Fundamentals and 3353 Applications". Prentice Hall, New Jersey, 1988. 3355 [12] Vecchi, M., and M. Fahim, "Architectural Model: The 3356 Spectrum Management Application (SMA) and the Common 3357 Spectrum Management Interface (csmi)". White Paper, Time 3358 Warner Cable, May 30, 1995. 3360 [13] Postel, J., "Instructions to RFC Authors, Internet 3361 Working Group Request For Comments 1543", October 1993. 3363 Common Spectrum Management Interface MIB June 13,1996 3365 13. Security Considerations 3367 Security issues are not discussed in this memo. 3369 14. Authors' Addresses 3371 Mario P. Vecchi 3372 Time Warner Cable 3373 168 Inverness Drive West 3374 Englewood, CO, 80112 3375 Phone: (303) 799-5540 3376 Fax: (303) 661-5651 3377 EMail: mario.vecchi@twcable.com 3379 Masuma Ahmed(*) 3380 Cable Television Laboratories, Inc. 3381 400 Centennial Parkway 3382 Louisville, CO 80027 3383 Phone: (303) 661-3782 3384 Fax: (303) 661-9199 3385 EMail: mxa@cablelabs.com 3387 (*)new address at: 3388 Terayon Corporation 3389 2952 Bunker Hill Lane 3390 Santa Clara, CA 95054 3391 Phone: (408) 486-5207 3392 EMail: mxa@terayon.com 3394 Common Spectrum Management Interface MIB June 13,1996 3396 Table of Contents 3398 1 Status of this Memo ................................... 1 3399 2 Abstract .............................................. 1 3400 3 The Network Management Framework ...................... 2 3401 4 Conventions ........................................... 2 3402 5 Objects ............................................... 2 3403 5.1 Format of Definitions ............................... 3 3404 6 RF Access Network Architecture Overview ............... 4 3405 7 RF Spectrum Management Architecture ................... 7 3406 7.1 Spectrum Management Application (SMA) ............... 12 3407 7.2 Spectrum Management Proxy Agent (SMPA) .............. 16 3408 8 RF Spectrum Terminology ............................... 16 3409 8.1 Forward and Reverse RF Spectrum ..................... 16 3410 8.2 RF Modulation Techniques ............................ 17 3411 8.3 RF Channel .......................................... 18 3412 8.4 RF Spectrum Slice ................................... 19 3413 8.4.1 RF Spectrum Slice Edge Characterization ........... 20 3414 8.5 Product Classes ..................................... 24 3415 9 RF Spectrum Management MIB Overview ................... 27 3416 9.1 RF Spectrum Management Architecture Hierarchy ....... 27 3417 9.2 Application of MIB II to Spectrum Management ........ 28 3418 9.2.1 The System Group .................................. 28 3419 9.3 Structure of the RF Spectrum Management MIB ......... 29 3420 10 Definitions .......................................... 34 3421 11 Acknowledgments ...................................... 68 3422 12 References ........................................... 70 3423 13 Security Considerations .............................. 72 3424 14 Authors' Addresses ................................... 72