Internet Draft Stephen Bush Expires in June 1997 Sunil Jagannath <draft-bush-rdrn-mib-00.txt> ITTC January 13, 1997 The Definition of Managed Objects for the Configuration of Mobile Wire- less Beamformed GPS-Based Networks Status of this Memo This document is a submission by the Information and Telecommunica- tions Technologies Center (ITTC) at the University of Kansas. Com- ments should be submitted to sbush@tisl.ukans.edu. Distribution of this memo is unlimited. This document is an Internet-Draft. Internet-Drafts are working doc- uments of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute work- ing documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference mate- rial or to cite them other than as ``work in progress.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Rapidly Deployable Radio Network (RDRN) Network Control Protocol (NCP). The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: Bush & Jagannath Expires in June 1997 [Page 1]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 STD 16/RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. STD 16/RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. STD 17/RFC 1213 which defines MIB-II, the core set of managed objects for the Internet suite of protocols. STD 15/RFC 1157 which defines the SNMP, the protocol used for net- work access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Objects Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [3] defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. Format of Definitions Section 5 contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions specified in [5,6]. Overview Network Control Protocol Terminology This section defines some of the terminology used in the Description of the NCP operation. Bush & Jagannath Expires in June 1997 [Page 2]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 o "AX.25" Asynchronous X.25 Protocol (See [1]). o "Callsign" The packet radio callsign is assigned by the FCC and identifies the packet radio operator. o "Edge Switch" (ES) A node which either resides within the wireless network or at the edge of the fixed and wireless network and which serves as a base station. o "Global Positioning System" (GPS) Satellite system which provides location and time. o "Remote Node" (RN) A host with the ability to connect via a beamforming antenna to an edge switch (ES). Rapidly Deployable Radio Network Control Protocol The Rapidly Deployable Radio Network (RDRN) [8] and [9] consists of links formed by beamforming antennas. While beamforming allows improved spectrum usage through spatial reuse, it poses a challenge to configure. Each mobile node and base station contains a GPS receiver and is aware of its current location. This information is shared among nodes and an optimal topology for beamformed links is determined. The protocol which carries this information is known as the network control protocol (NCP) [11]. The NCP is carried over an omni-directional packet radio overlay network. See reference [12] for information about Virtual Network Configuration (VNC) and NCP. MIB Groups The definition of managed objects for the NCP is divided into eleven groups: Bush & Jagannath Expires in June 1997 [Page 3]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 (1) Initialization Group (2) Configuration Group (3) NCP AX.25 Connection Group (4) Edge Switch Group (5) Remote Node Group (6) GPS Specific Stats Group (7) Packet Radio Specific Stats Group (8) NCP Layer Specific Stats Group (9) ATM Stacks Group (10) Beam Coverage Group (11) NCP Status Group The initialization group objects pertain to the initial startup of the NCP enhanced mobile node. The configuration group objects control timing, encryption, and other configuration information for the NCP. The NCP AX.25 [10] group objects maintains a mapping of packet radio AX.25 streams to callsigns. This is useful for determining which AX.25 packet radio connections are currently established. The Edge Switch (ES) and Remote Node (RN) group objects manage information need by the beamforming algorithm to properly steer beams. The GPS, Packet Radio, and NCP Layer group objects manage GPS, NCP Packet Radio, and NCP information. The ATM Layer configuration objects are described in more detail in the next section. The Beam Coverage group objects provide access to information about the currently active beams. Finally, the NCP Status group objects pertain to timing information of interest to NCP. Virtual Network Configuration (VNC) [11] is managed by a separate MIB. ATM Configuration MIB Objects The ATM Stacks group objects manage the currently active ATM stacks on an ES or RN. As the orderwire network determines the topology of all nodes in the wireless segment (e.g., RNs, ESs) in our architec- ture, and establishes link connectivity among adjacent nodes, setup is still required of the actual ATM circuits on which wireless ATM are carried on the user data overlay network. This is accomplished by providing standard ATM signaling capabilities to RNs and ESs and using Classical IP over ATM to associate ATM VCs to IP addresses. The Classical IP over ATM implementation provided works for PVCs and SVCs (using ATMARP). Since an ES may connect to multiple RNs (wireless connections) or ATM Bush & Jagannath Expires in June 1997 [Page 4]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 switches (wired connections), it can be thought of as a software- based ATM switch. In this sense, an ES features ATM PNNI signaling while an RN features ATM UNI signaling. By default, an RN creates one wireless-ATM protocol stack and establishes an ATM VC signaling chan- nel on such a stack; however, the stack is initially in an inactive state (i.e., non-operational mode) since there is no link connectiv- ity to another node established yet. Likewise, an ES creates a pre- defined number of wireless-ATM protocol stacks -- acting like ports in an ATM switch -- and establishes ATM VC signaling channels on all configured stacks which are also initialized as inactive. Wireless- ATM protocol stacks are controlled by a daemon, called the adaptation manager, which acts on behalf of the orderwire network. The adapta- tion manager daemon not only controls the stacks by setting their state to either active or inactive (default), but also may modify configuration parameters of the stacks to provide dynamic adaptation to link conditions. Two possible scenarios illustrate the interactions between the order- wire network and the wireless-ATM network. In the first scenario the orderwire detects link connectivity between an adjacent pair of nodes (e.g., RN-ES or ES-ES). In this case, the orderwire network requests an inactive stack from the adaptation manager daemon at each end and associates them with a designated address. Upon establishment of link connectivity, a requested wireless stack has its state set to active and is ready to operate. Note that since the signaling channels are preconfigured on the stacks in question, users on the wireless estab- lish end-to-end connections exactly as if they were connected in a wired ATM network. The other scenario occurs when the orderwire network detects a broken connection, at the link level, between two connected nodes. This case is typical of an RN moving away from the connectivity range of an ES. The orderwire network thus contacts the adaptation manager daemon at each end to set the wireless stacks in question to inactive. Since a wireless stack is never destroyed, it can be reused in a future request from the orderwire to establish connectivity to another pair of nodes. Definitions Bush & Jagannath Expires in June 1997 [Page 5]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 RDRN-NCP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, enterprises, Counter32, Integer32, TimeTicks, Unsigned32 FROM SNMPv2-SMI DisplayString, RowStatus, DateAndTime, TruthValue, TimeStamp, TAddress FROM SNMPv2-TC; RdrnNcpMIB MODULE-IDENTITY ORGANIZATION "KU TISL" CONTACT-INFO " Steve Bush sbush@tisl.ukans.edu" DESCRIPTION "Experimental MIB modules for the Rapidly Deployable Radio Networks (RDRN) Project Network Control Protocol (NCP)." ::= { 1 3 6 1 3 ncp(75) 1 } ncp OBJECT IDENTIFIER ::= { ncp(75) 1 } -- -- NCP Initialization Group -- initialization OBJECT IDENTIFIER ::= { ncp 1 } initContact OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "NCP Agent Developer, but hopefully NOT maintainer." ::= { initialization 1 } initEntity OBJECT-TYPE SYNTAX INTEGER { edgeSwitch(0), remoteNode(1) } MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Describes the RDRN node component." Bush & Jagannath Expires in June 1997 [Page 6]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 ::= { initialization 2 } initDebug OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Logging level. Zero is off; the higher the number, the more logging is enabled." ::= { initialization 3 } initEncrypt OBJECT-TYPE SYNTAX INTEGER { clear(0), des(1) } MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates whether data encryption used. Both endpoints of a packet radio link MUST have this object set identically for proper communication." ::= { initialization 4 } initVNC OBJECT-TYPE SYNTAX INTEGER { VNCEnabled(1), Sequentional(0) } MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates whether this system is running using Virtual Network Configuration enhanced mode, or sequential operation." ::= { initialization 5 } initStacks OBJECT-TYPE SYNTAX INTEGER { noStacks(1), useStacks(0) } MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates whether link level stacks will be created. Primarily used for testing purposes." ::= { initialization 6 } Bush & Jagannath Expires in June 1997 [Page 7]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 initRadioPort OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates the packet radio tty port." ::= { initialization 7 } initGpsPort OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates the GPS tty port." ::= { initialization 8 } initSpeed OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates the assumed initial speed. Primarily used for simulated GPS." ::= { initialization 9 } initDirection OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates the assumed initial direction. Primarily used for simulated GPS." ::= { initialization 10 } initXPos OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates the assumed initial X axis position. Primarily used for simulated GPS." ::= { initialization 11 } initYPos OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION Bush & Jagannath Expires in June 1997 [Page 8]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 "Indicates the assumed initial Y axis position. Primarily used for simulated GPS." ::= { initialization 12 } initSimGps OBJECT-TYPE SYNTAX INTEGER { gpsReceiver(0), gpsSimulator(1) } MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates whether the GPS receiver is being read or the GPS simulation code is being used. This value can be set while running without harm. Changing from gpsReceiver to gpsSimulator will cause a smooth transition based on last known direction and speed. Transitioning from gps Simulator to gpsReceiver may cause a large jump in position." ::= { initialization 13 } initTcpEmulation OBJECT-TYPE SYNTAX INTEGER { packetRadio(2), tcpEmulation(1), packetRadio_and_tcpEmulation(3) } MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates whether packet radios or TCP-IP simulation of packet radios is currently in use. This value cannot be set because the tcp emulation requires knowledge of ip addresses of all hosts in the simulated RDRN system and all though this could be set on the fly through a MIB table, I don't feel it's worth the effort to develop at this point." ::= { initialization 14 } -- -- NCP Configuration Group -- configuration OBJECT IDENTIFIER ::= { ncp 2 } configTimeout OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write Bush & Jagannath Expires in June 1997 [Page 9]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 STATUS mandatory DESCRIPTION "Indicates the timeout during edge switch reconfiguration. Should be set long enough for all edge switches to respond." ::= { configuration 1 } configMaxVel OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the maximum of a uniformly distributed velocity for simulated GPS operation." ::= { configuration 2 } configSpeed OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the initial speed for simulated GPS operation. Same as initSpeed for historical reasons, e.g. this one set through a file while the other is set via arguments." ::= { configuration 3 } configDirection OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the initial direction in degrees for simulated GPS operation. Same as initDirection for historical reasons. This one is read from a file while the other is set as a program argument during startup." ::= { configuration 4 } configUseRealTopology OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates whether edge switch topology code is called. Currently this code uses MatLab and can be quite slow." ::= { configuration 5 } configCallsign OBJECT-TYPE SYNTAX DisplayString Bush & Jagannath Expires in June 1997 [Page 10]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates this nodes packet radio callsign." ::= { configuration 6 } configKey OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "Indicates the current DES key. Probably not secure to put this here, but useful for debugging." ::= { configuration 7 } configUserSwitch OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS mandatory DESCRIPTION "If this is a remote node, this is the associated edge switch." ::= { configuration 8 } configUpdatePeriod OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the remote node's user position update rate." ::= { configuration 9 } configDistanceTolerance OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the amount of movement allowed before beam angles must be recomputed." ::= { configuration 10 } configAntennaAngle OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the direction of the physical position of the linear array from pointing North." Bush & Jagannath Expires in June 1997 [Page 11]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 ::= { configuration 11 } -- -- Current NCP AX.25 Connection Group -- radioStreams OBJECT IDENTIFIER ::= { ncp 3 } radioStreamsTable OBJECT-TYPE SYNTAX SEQUENCE OF RadioStreamsEntry ACCESS read-only STATUS mandatory DESCRIPTION "Table of packet currently established packet radio streams and callsigns." ::= { radioStreams 1 } radioStreamsEntry OBJECT-TYPE SYNTAX RadioStreamsEntry ACCESS read-only STATUS mandatory ::= { radioStreamsTable 1 } RadioStreamsEntry ::= SEQUENCE { radioStreamsID DisplayString, radioStreamsCallsign DisplayString } radioStreamsID OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The Packet Radio stream identifier for this ARQ AX.25 connection." ::= { radioStreamsEntry 1 } radioStreamsCallsign OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "This is the callsign of the packet radio with the associated stream identifier." ::= { radioStreamsEntry 2 } Bush & Jagannath Expires in June 1997 [Page 12]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 -- -- Known Edge Switch Group -- edgeSwitchNetwork OBJECT IDENTIFIER ::= { ncp 4 } edgeSwitchTable OBJECT-TYPE SYNTAX SEQUENCE OF EdgeSwitchEntry ACCESS read-only STATUS mandatory DESCRIPTION "Table of RDRN edge switches known by this edge switch." ::= { edgeSwitchNetwork 1 } edgeSwitchEntry OBJECT-TYPE SYNTAX EdgeSwitchEntry ACCESS read-only STATUS mandatory ::= { edgeSwitchTable 1 } EdgeSwitchEntry ::= SEQUENCE { edgeSwitchCallsign DisplayString, edgeSwitchHostname DisplayString, edgeSwitchATMAddr DisplayString, edgeSwitchLatDeg DisplayString, edgeSwitchLatMin DisplayString, edgeSwitchLatDir DisplayString, edgeSwitchLonDeg DisplayString, edgeSwitchLonMin DisplayString, edgeSwitchLonDir DisplayString, edgeSwitchXPos DisplayString, edgeSwitchYPos DisplayString, edgeSwitchSpeed DisplayString, edgeSwitchDir DisplayString, edgeSwitchAvaliability Bush & Jagannath Expires in June 1997 [Page 13]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 INTEGER, edgeSwitchNSat INTEGER, edgeSwitchHDop INTEGER, edgeSwitchElevation DisplayString, edgeSwitchHeight DisplayString, edgeSwitchIndex DisplayString, edgeSwitchTime TimeTicks } edgeSwitchCallsign OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Callsign." ::= { edgeSwitchEntry 1 } edgeSwitchHostname OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch IP Hostname." ::= { edgeSwitchEntry 2 } edgeSwitchATMAddr OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch ATM Address." ::= { edgeSwitchEntry 3 } edgeSwitchLatDeg OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Latitude - degrees." ::= { edgeSwitchEntry 4 } edgeSwitchLatMin OBJECT-TYPE Bush & Jagannath Expires in June 1997 [Page 14]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Latitude - minutes." ::= { edgeSwitchEntry 5 } edgeSwitchLatDir OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Latitude Hemisphere." ::= { edgeSwitchEntry 6 } edgeSwitchLonDeg OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Longitude - degrees." ::= { edgeSwitchEntry 7 } edgeSwitchLonMin OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Longitude - minutes." ::= { edgeSwitchEntry 8 } edgeSwitchLonDir OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Longitude - Hemisphere." ::= { edgeSwitchEntry 9 } edgeSwitchXPos OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Cartesian X Coordinate. Units are meters." ::= { edgeSwitchEntry 10 } Bush & Jagannath Expires in June 1997 [Page 15]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 edgeSwitchYPos OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch Cartesian Y Coordinate. Units are meters." ::= { edgeSwitchEntry 11 } edgeSwitchSpeed OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch current speed." ::= { edgeSwitchEntry 12 } edgeSwitchDir OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch current direction in degrees 0 degrees is North." ::= { edgeSwitchEntry 13 } edgeSwitchAvaliability OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch GPS quality information. 0 - fix not available 1 - Non differential GPS fix available 2 - Differential GPS fix available." ::= { edgeSwitchEntry 14 } edgeSwitchNSat OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch GPS number of satellites in use. From 0 to 8 satellites." ::= { edgeSwitchEntry 15 } edgeSwitchHDop OBJECT-TYPE SYNTAX INTEGER Bush & Jagannath Expires in June 1997 [Page 16]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch GPS horizontal dilution of position. Varies from 1.0 to 99.9." ::= { edgeSwitchEntry 16 } edgeSwitchElevation OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch current height with respect to sea level in meters." ::= { edgeSwitchEntry 17 } edgeSwitchHeight OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Edge Switch current geoidal height in meters." ::= { edgeSwitchEntry 18 } edgeSwitchIndex OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Internal index for use in ES/RN associations." ::= { edgeSwitchEntry 19 } edgeSwitchTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "GPS time at which this information was valid." ::= { edgeSwitchEntry 20 } -- -- Associated Remote Nodes Group -- remoteNodeNetwork OBJECT IDENTIFIER ::= { ncp 5 } remoteNodeTable OBJECT-TYPE SYNTAX SEQUENCE OF RemoteNodeEntry Bush & Jagannath Expires in June 1997 [Page 17]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 ACCESS read-only STATUS mandatory DESCRIPTION "Table of RDRN remote nodes known by this edge switch." ::= { remoteNodeNetwork 1 } remoteNodeEntry OBJECT-TYPE SYNTAX EdgeSwitchEntry ACCESS read-only STATUS mandatory ::= { remoteNodeTable 1 } RemoteNodeEntry ::= SEQUENCE { remoteNodeCallsign DisplayString, remoteNodeHostname DisplayString, remoteNodeATMAddr DisplayString, remoteNodeLatDeg DisplayString, remoteNodeLatMin DisplayString, remoteNodeLatDir DisplayString, remoteNodeLonDeg DisplayString, remoteNodeLonMin DisplayString, remoteNodeLonDir DisplayString, remoteNodeXPos DisplayString, remoteNodeYPos DisplayString, remoteNodeSpeed DisplayString, remoteNodeDir DisplayString, remoteNodeAvaliability INTEGER, remoteNodeNSat INTEGER, remoteNodeHDop INTEGER, remoteNodeElevation DisplayString, remoteNodeHeight Bush & Jagannath Expires in June 1997 [Page 18]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 DisplayString, remoteNodeIndex DisplayString, remoteNodeTime TimeTicks, remoteNodeDistance DisplayString } remoteNodeCallsign OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Callsign." ::= { remoteNodeEntry 1 } remoteNodeHostname OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node IP hostname." ::= { remoteNodeEntry 2 } remoteNodeATMAddr OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node ATM Address." ::= { remoteNodeEntry 3 } remoteNodeLatDeg OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Latitude - degrees." ::= { remoteNodeEntry 4 } remoteNodeLatMin OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Latitude - minutes." ::= { remoteNodeEntry 5 } Bush & Jagannath Expires in June 1997 [Page 19]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 remoteNodeLatDir OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Latitude Hemisphere." ::= { remoteNodeEntry 6 } remoteNodeLonDeg OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Longitude - degrees." ::= { remoteNodeEntry 7 } remoteNodeLonMin OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Longitude - minutes." ::= { remoteNodeEntry 8 } remoteNodeLonDir OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Longitude - Hemisphere." ::= { remoteNodeEntry 9 } remoteNodeXPos OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Cartesian X Coordinate. Units are meters." ::= { remoteNodeEntry 10 } remoteNodeYPos OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node Cartesian Y Coordinate. Units are meters." Bush & Jagannath Expires in June 1997 [Page 20]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 ::= { remoteNodeEntry 11 } remoteNodeSpeed OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node current speed." ::= { remoteNodeEntry 12 } remoteNodeDir OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node current direction in degrees 0 degrees is North." ::= { remoteNodeEntry 13 } remoteNodeAvaliability OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node GPS quality information. 0 - fix not available 1 - Non differential GPS fix available 2 - Differential GPS fix available." ::= { remoteNodeEntry 14 } remoteNodeNSat OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node GPS number of satellites in use. From 0 to 8 satellites." ::= { remoteNodeEntry 15 } remoteNodeHDop OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node GPS horizontal dilution of position. Varies from 1.0 to 99.9." ::= { remoteNodeEntry 16 } Bush & Jagannath Expires in June 1997 [Page 21]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 remoteNodeElevation OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node current height with respect to sea level in meters." ::= { remoteNodeEntry 17 } remoteNodeHeight OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Remote Node current geoidal height in meters." ::= { remoteNodeEntry 18 } remoteNodeIndex OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Internal index for use in ES/RN associations." ::= { remoteNodeEntry 19 } remoteNodeTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "GPS time at which this information was valid." ::= { remoteNodeEntry 20 } remoteNodeDistance OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Distance of this remote node from its associated base station. A value of 0.0 means that no base station has been associated yet." ::= { remoteNodeEntry 21 } -- -- GPS Specific Stats Group -- gps OBJECT IDENTIFIER ::= { ncp 6 } Bush & Jagannath Expires in June 1997 [Page 22]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 gpsPosRead OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of GPS position records that have been read since initialization." ::= { gps 1 } -- -- Packet Radio Specific Stats Group -- packetRadio OBJECT IDENTIFIER ::= { ncp 7 } packetsIn OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of NCP packets which have been read since initialization." ::= { packetRadio 1 } packetsOut OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of NCP packets which have been written to the packet radio since initialization." ::= { packetRadio 2 } packetsBad OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of NCP packets which have been read and discarded as unreadable or incomplete since initialization." ::= { packetRadio 3 } -- -- NCP Level Specific Stats Group -- ncpLevel OBJECT IDENTIFIER ::= { ncp 8 } Bush & Jagannath Expires in June 1997 [Page 23]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 ncpHandoffs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number handoffs since since initialization." ::= { ncpLevel 1 } -- -- Existing ATM Stacks Group -- atmStacks OBJECT IDENTIFIER ::= { ncp 9 } atmStacksTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmStacksEntry ACCESS read-only STATUS mandatory ::= { atmStacks 1 } atmStacksEntry OBJECT-TYPE SYNTAX AtmStacksEntry ACCESS read-only STATUS mandatory DESCRIPTION "Table of currently active AHDLC stacks." ::= { atmStacksTable 1 } AtmStacksEntry ::= SEQUENCE { atmStacksBeam INTEGER, atmStacksSlot INTEGER, atmStacksATMaddr DisplayString, atmStacksAhdlcState INTEGER } atmStacksBeam OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The beam number for this AHDLC stack." ::= { atmStacksEntry 1 } atmStacksSlot OBJECT-TYPE Bush & Jagannath Expires in June 1997 [Page 24]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The slot number for this AHDLC stack." ::= { atmStacksEntry 2 } atmStacksATMaddr OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The ATM address of the current AHDLC stack." ::= { atmStacksEntry 3 } atmStacksAhdlcState OBJECT-TYPE SYNTAX INTEGER { down(0), up(1) } MAX-ACCESS read-only STATUS mandatory DESCRIPTION "This is the state of the AHDLC layer." ::= { atmStacksEntry 4 } -- -- The Beam Coverage Group -- beamCoverage OBJECT IDENTIFIER ::= { ncp 10 } beamCovTable OBJECT-TYPE SYNTAX SEQUENCE OF BeamCovEntry ACCESS read-only STATUS mandatory DESCRIPTION "Table of beam coverage information." ::= { beamCoverage 1 } beamCovEntry OBJECT-TYPE SYNTAX BeamCovEntry ACCESS read-only STATUS mandatory ::= { beamCovTable 1 } BeamCovEntry ::= SEQUENCE { beamCovAngle Bush & Jagannath Expires in June 1997 [Page 25]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 DisplayString, beamCovPower DisplayString, beamCovSIR DisplayString } beamCovAngle OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The beam angle of this beam." ::= { beamCovEntry 1 } beamCovPower OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The power level of this beam." ::= { beamCovEntry 2 } beamCovSIR OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The signal to interference ratio for this beam." ::= { beamCovEntry 3 } -- -- The NCP Status Group -- status OBJECT IDENTIFIER ::= { ncp 11 } statState OBJECT-TYPE SYNTAX INTEGER { down(0), configuring(1), associating(2), active(3), delay(4) } MAX-ACCESS read-only STATUS mandatory DESCRIPTION Bush & Jagannath Expires in June 1997 [Page 26]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 "Describes the NCP state of operation: down - node administratively idle. configuring - es-es topology configuration or initial startup. associating - handoff in process. active - other normal operation. delay - node is in a delay mode, e.g. remote node waiting between updates." ::= { status 1 } statAdminState OBJECT-TYPE SYNTAX INTEGER { idle(0), active(1) } MAX-ACCESS read-write STATUS mandatory DESCRIPTION "Indicates whether the process is in an idle mode or active. Setting this object to idle causes the NCP process to remain alive, but stop processing packets. A transition setting from idle to active causes the NCP process to re-initialize as though just started." ::= { status 2 } statTopologyTime OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The time in micro-seconds to do the last optimal topology calculation. A zero value means that the topology calculation has not been performed yet." ::= { status 3 } statBeamformTime OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The time in micro-seconds to do the last beamform. A zero values indicates that beamforming has not been performed yet." ::= { status 4 } Bush & Jagannath Expires in June 1997 [Page 27]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 statNcpTransferTime OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The time in micro-seconds of the last NCP packet transmission. A zero value means that no packet measurements are being taken." ::= { status 5 } END Security Considerations Clearly, the DES encryption key should not be accessible in the MIB, however, this remains in the MIB for debugging and testing purposes. Also, critical timing parameters are set-able from this MIB. Again this is useful for experimental purposes, but may not be desired for commercial use. References [1] Rose M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", STD 16, RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [2] McCloghrie K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", STD 17, RFC 1213, Performance Systems International, March 1991. [3] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International [4] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987. [5] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", STD 16, RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. [6] Rose, M., Editor, "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March Bush & Jagannath Expires in June 1997 [Page 28]
Internet-Draft Mobile Wireless GPS-Based Configuration 13 January 1997 1991. [7] McCloghrie, K., "Extensions to the Generic-Interface MIB", RFC 1229, Hughes LAN Systems, Inc., May 1991. [8] Stephen F. Bush, Sunil Jagannath, Joseph B. Evans, and Victor Frost, "A Control and Management Network for Wireless ATM Systems" in Proceedings of the International Communications Conference '96, p. 459,463 (1996 June). Online version available at: http://www.tisl.ukans.edu/~sbush/pspapers/icc96.ps [9] Stephen F. Bush, Sunil Jagannath, Ricardo Sanchez, Joseph B. Evans, Victor Frost, and K. Sam Shanmugan, Rapidly Deployable Radio Networks (RDRN) Network Architecture, Telecommunications Information Sciences Laboratory (1995 July). Online version available at: http://www.tisl.ukans.edu/~sbush/pspapers/network_arch.ps [10] AX.25 Amateur Packet Radio Link-Layer Protocol, IEEE October (1984). [11] Network Control Protocol for the Configuration of Mobile Wireless Beamformed GPS-Based Networks, <draft-bush-ncp-config-00.txt>, Stephen F. Bush, Sunil Jagannath. [12] The Definition of Managed Objects for Virtual Network Configuration, <draft-bush-vnc-mib-00.txt>, Stephen F. Bush, Sunil Jagannath. Author's Address Stephen F. Bush Sunil Jagannath Information and Telecommunications Technologies Center (ITTC) University of Kansas Lawrence, Kansas 66045 Phone: (913) 864-7761 EMail: sbush@tisl.ukans.edu Bush & Jagannath Expires in June 1997 [Page 29]