CISCO-WAN-3G-MIB

INTEGER1 = cdma2 = gsm · Integer32

Cellular Standard: GSM (Global System for Mobile communications, 3GPP), CDMA (Code Division Multiple Access, 3GPP-2). GSM standard also include 4G-LTE technology mode

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

Cellular service capability. It currently includes the 2G, 3G and 4G-LTE standard.

INTEGER1 = unknown2 = up3 = down · Integer32

Cellular modem state, up(2) indicates modem can be detected and down(3) indicates modem can not be detected.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object indicates the previous service type when service type changes.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object indicates the current service type when service type changes.

INTEGER1 = unknown2 = roaming3 = home · Integer32

Cellular current roaming status.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Cellular current system time received from base station.

INTEGER1 = unknown2 = error3 = connecting4 = dormant5 = connected6 = disconnected7 = idle8 = active9 = inactive · Integer32

Indicates the current connection status.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object is used as one of the var-bind object when notification for RSSI or Ec/Io is generated. This object indicates which service generates the notification.

C3gRssiGeneric RSSI range. (-150..0) · Integer32

This object is used as one of the var-bind object when notification for RSSI is generated. The relevant RSSI will be copied into c3gNotifRssi which corresponds to the service indicated in c3gNotifRadioService object. This object will reflect the value of one of the following objects: c3gCurrent1xRttRssi, c3gCurrentEvDoRssi and c3gCurrentGsmRssi. User should not use this object to get the current RSSI value as this object is used to indicate the RSSI value that triggers c3gRssiOnsetNotif or c3gRssiAbateNotif notification.

C3gEcIoGeneric EcIo range. (-150..0) · Integer32

This object is used as one of the var-bind object when notification for Ec/Io is generated. The relevant Ec/Io will be copied into c3gNotifEcIo which corresponds to the service indicated in c3gNotifRadioService object. This object will reflect the value of one of the following objects: c3gCurrent1xRttEcIo, c3gCurrentEvDoEcIo and c3gCurrentGsmEcIo. User should not use this object to get the current Ec/Io value as this object is used to indicate the Ec/Io value that triggers c3gEcIoOnsetNotif or c3gEcIoAbateNotif notification.

C3gTemperatureGeneric temperature range. (-50..100) · Integer32 · degrees Celsius

The modem temperature.

C3gRssiGeneric RSSI range. (-150..0) · Integer32 · dBm

The RSSI onset threshold value. If RSSI goes below the threshold and the service bit in c3gRssiOnsetNotifFlag is set, the c3gRssiOnsetNotif notification for that service will be sent. The absolute value of c3gRssiAbateNotifThreshold should be less than or equal to the absolute value of c3gRssiOnsetNotifThreshold (|c3gRssiAbateNotifThreshold| <= |c3gRssiOnsetNotifThreshold|). e.g. setting c3gRssiAbateNotifThreshold to -115 dBm and then setting c3gRssiOnsetNotifThreshold to -110 dBm is not allowed and will be rejected.

C3gRssiGeneric RSSI range. (-150..0) · Integer32 · dBm

The RSSI abate threshold value. If RSSI goes above the threshold and the service bit in c3gRssiAbateNotifFlag is set, the c3gRssiAbateNotif notification for that service will be sent. The absolute value of c3gRssiAbateNotifThreshold should be less than or equal to the absolute value of c3gRssiOnsetNotifThreshold (|c3gRssiAbateNotifThreshold| <= |c3gRssiOnsetNotifThreshold|). e.g. setting c3gRssiAbateNotifThreshold to -115 dBm and then setting c3gRssiOnsetNotifThreshold to -110 dBm is not allowed and will be rejected.

C3gEcIoGeneric EcIo range. (-150..0) · Integer32 · dB

The EcIo onset threshold value. If EcIo goes below the threshold and the service bit in c3gEcIoOnsetNotifFlag is set, the c3gEcIoOnsetNotif notification for that service will be sent. The absolute value of c3gEcIoAbateNotifThreshold should be less than or equal to the absolute value of c3gEcIoOnsetNotifThreshold (|c3gEcIoAbateNotifThreshold| <= |c3gEcIoOnsetNotifThreshold|). e.g. setting c3gEcIoAbateNotifThreshold to -15 dB and then setting c3gEcIoOnsetNotifThreshold to -10 dB is not allowed and will be rejected.

C3gEcIoGeneric EcIo range. (-150..0) · Integer32 · dB

The threshold value that if EcIo goes above the threshold and the service bit in c3gEcIoAbateNotifFlag is set, the c3gEcIoAbateNotif notification for that service will be sent. The absolute value of c3gEcIoAbateNotifThreshold should be less than or equal to the absolute value of c3gEcIoOnsetNotifThreshold (|c3gEcIoAbateNotifThreshold| <= |c3gEcIoOnsetNotifThreshold|). e.g. setting c3gEcIoOnsetNotifThreshold to -15 dB and then setting c3gEcIoAbateNotifThreshold to -10 dB is not allowed and will be rejected.

C3gTemperatureGeneric temperature range. (-50..100) · Integer32 · degrees Celsius

The modem temperature onset threshold value. If modem temperature goes above the threshold and the value of c3gModemTemperOnsetNotifEnabled is 'true', the c3gModemTemperOnsetNotif notification will be sent. The value of c3gModemTemperAbateNotifThreshold should be less than or equal to the value of c3gModemTemperOnsetNotifThreshold. e.g. setting c3gModemTemperAbateNotifThreshold to 50 degree Celsius and then setting c3gModemTemperOnsetNotifThreshold to 40 degree Celsius is not allowed and will be rejected.

C3gTemperatureGeneric temperature range. (-50..100) · Integer32 · degrees Celsius

The modem temperature abate threshold value. If modem temperature goes below the threshold and the value of c3gModemTemperAbateNotifEnabled is 'true', the c3gModemTemperAbateNotif notification will be sent. The value of c3gModemTemperAbateNotifThreshold should be less than or equal to the value of c3gModemTemperOnsetNotifThreshold. e.g. setting c3gModemTemperAbateNotifThreshold to 50 degree Celsius and then setting c3gModemTemperOnsetNotifThreshold to 40 degree Celsius is not allowed and will be rejected.

INTEGER1 = reset2 = powerCycle · Integer32

This object is used to reset or power-cycle the modem.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable/disable the generation of modem up notification c3gModemUpNotif.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable/disable the generation of modem down notification c3gModemDownNotif.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable/disable the generation of service changed notification c3gServiceChangedNotif.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable/disable the generation of network changed notification c3gNetworkChangedNotif.

BITS

This object is the flag bitmap to control the generation of notification c3gConnectionStatusChangedNotif. e.g. setting bit 0 (error(0)) to 1 and bit 4 (disconnected(4)) to 1 will cause the notification c3gConnectionStatusChangedNotif to be generated when object c3gConnetionStatus changes the status to error or disconnected. The default value of this object is '00'H.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object is the flag bitmap to control the generation of notification c3gRssiOnsetNotif. Each bit represents a service as defined in C3gServiceCapability, set the bit value to 1 to enable (and 0 to disable) the generation of notification c3gRssiOnsetNotif for that service. The default value of this object is all bits are 0.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object is the flag bitmap to control the generation of notification c3gRssiAbateNotif. Each bit represents a service as defined in C3gServiceCapability, set the bit value to 1 to enable (and 0 to disable) the generation of notification c3gRssiAbateNotif for that service. The default value of this object is all bits are 0.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object is the flag bitmap to control the generation of notification c3gEcIoOnsetNotif. Each bit represents a service as defined in C3gServiceCapability, set the bit value to 1 to enable (and 0 to disable) the generation of notification c3gEcIoOnsetNotif for that service. The default value of this object is all bits are 0.

C3gServiceCapability3G service capability: oneXRtt(0) - 1xRTT evDoRel0(1) - EVDO Revision 0 evDoRelA(2) - EVDO Revision A evDoRelB(3) - EVDO Revision B gprs(4) - GPRS edge(5) - EDGE umtsWcdma(6) - UMTS/WCDMA hsdpa(7) - HSDPA hsupa(8) - HSUPA hspa(9) - HSPA hspaPlus(10) - HSPA Plus lteTdd(11) - LTE TDD lteFdd (12) - LTE FDD · BITS

This object is the flag bitmap to control the generation of notification c3gEcIoAbateNotif. Each bit represents a service as defined in C3gServiceCapability, set the bit value to 1 to enable (and 0 to disable) the generation of notification c3gEcIoAbateNotif for that service. The default value of this object is all bits are 0.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable/disable the generation of c3gModemTemperOnsetNotif notification.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable/disable the generation of c3gModemTemperAbateNotif notification.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to determine or enable/disable the GPS state.

Counter64 (0..18446744073709551615) · seconds

Total duration of all calls.

Counter64 (0..18446744073709551615) · bytes

Total data transmitted for all calls. It is the total amount of data transmitted by modem, not to be confused with the number of bytes transmitted through the interface.

Counter64 (0..18446744073709551615) · bytes

Total data received for all calls. It is the total amount of data received by modem, not to be confused with the number of bytes received from the interface.

INTEGER1 = unknown2 = off3 = on4 = noChange · Integer32

HDR Data Dedicated Transmission Mode (DDTM) preference: unknown(1) - DDTM preference is unknown off(2) - DDTM preference set to OFF on(3) - DDTM preference set to ON noChange(4) - DDTM preference is no change

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Phone number of outgoing call.

INTEGER1 = unknown2 = inactive3 = acquisition4 = sync5 = idle6 = access7 = connected · Integer32

High Data Rate (HDR) Access Terminal (AT) state.

INTEGER1 = unknown2 = open3 = close4 = addressManagementProtocolSetup5 = atInitiated6 = anInitiated · Integer32

High Data Rate (HDR) session state.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Unicast Access Terminal Identifier (UATI), AT seeking access to the 1 times EV-DO system receives a UATI allocated from the system after setting up a radio traffic channel with a base station.

Unsigned32

Color code. A sync channel may be used by the base station to communicate administrative information to a mobile station. For example, a base station may transmit a base station ID to a user, a color code and administrative information identifying system status.

Unsigned32

Random Access Terminal Identifier (RATI). AT transmits a UATI request message to the ANC using the RATI to make a UATI allocation request.

Unsigned32 · milliseconds

HDR connection session duration. It is the duration between c3gHdrSessionStart and c3gHdrSessionEnd.

Unsigned32 · milliseconds

HDR connection session starting time.

Unsigned32 · milliseconds

HDR connection session ending time.

INTEGER1 = unknown2 = notAuthenticated3 = authenticated4 = failed5 = authenticationDisabled · Integer32

Connection authentication status: unknown(1) - authentication status is unknown notAuthenticated(2) - not yet authenticated. authenticated(3) - authenticated. failed(4) - authentication failed. authenticationDisabled(5) - authentication disabled

Unsigned32

High Data Rate (HDR) Data Rate Control (DRC). AT provides requests for data transmissions by sending a Data Rate Control, DRC, message via a specific channel referred to as the DRC channel.

Unsigned32

HDR DRC cover. The DRC cover is a coding applied to identify the sector from which the data is to be transmitted. In one embodiment, the DRC cover is a Walsh code applied to the DRC value, wherein a unique code corresponds to each sector in the Active Set of the AT.

INTEGER1 = unknown2 = pilotOnly3 = rri9dot6kbps4 = rri19dot2kbps5 = rri38dot4kbps6 = rri76dot8kbps7 = rri153dot6kbps · Integer32

HDR Rate Request Indicator (RRI). RRI provides the structure of a frame currently being transmitted when frames are transmitted at different rates. Services at different rates are reliably provided by the RRI: unknown(1) - RRI unknown pilotOnly(2) - pilot channel only rri9dot6kbps(3) - RRI is 9.6 Kbit/s rri19dot2kbps(4) - RRI is 19.2 Kbit/s rri38dot4kbps(5) - RRI is 38.4 Kbit/s rri76dot8kbps(6) - RRI is 76.8 Kbit/s rri153dot6kbps(7) - RRI is 153.6 Kbit/s

Integer32

Mobile IP error code (please refer to RFC 2002).

Counter64 (0..18446744073709551615) · bytes

Current number of bytes transmitted by modem for current connection.

Counter64 (0..18446744073709551615) · bytes

Current number of bytes received by modem for current connection.

INTEGER1 = unknown2 = error3 = connecting4 = dormant5 = connected6 = disconnected · Integer32

Current call status.

Unsigned32 · seconds

Current call duration.

INTEGER1 = unknown2 = asyncData3 = voiceCall4 = packet1xRttCall5 = atAsyncDataCall6 = atVoiceCall7 = atPacketCall8 = faxCall9 = smsCall10 = otaCall11 = testCall12 = callWaiting13 = positionDetermination14 = dormant15 = e911Call · Integer32

Current call type.

INTEGER1 = unknown2 = modemOffline3 = modemCdmaLocTilPowCyc4 = noService5 = abnormalCallEnd6 = baseStatIntercept7 = baseStatRelease8 = baseStatReleaseNoReas9 = baseStatReleaseSoRej10 = incomingCall11 = baseStatAlertStop12 = clientEndedCall13 = activationEndedOtasp14 = ndssFailure15 = maxAccesProbTransmit16 = persistTestFailure17 = ruimNotPresent18 = accessAttemptInProg19 = reasonUnspecified20 = recdRetryOrder21 = modemLocked22 = gpsCallEnded23 = smsCallEnded24 = noConcurrentService25 = noResponseFromBs26 = rejectedByBs27 = notCompatConcurServ28 = accessBlockedByBs29 = alreadyOnTraffChann30 = emergencyCall31 = dataCallEnded32 = busyHdr33 = billingOrAuthErrHdr34 = sysChangeDueToPrlHdr35 = hdrExitDueToPrl36 = noSessionHdr37 = callEndedHdr · Integer32

Last call disconnect reason: unknown(1) - Unknown modemOffline(2) - Modem offline modemCdmaLocTilPowCyc(3) - Modem CDMA locked till power cycle noService(4) - No service abnormalCallEnd(5) - Abnormal call end baseStatIntercept(6) - Base station intercept baseStatRelease(7) - Base station release baseStatReleaseNoReas(8) - Base station release (No reason) baseStatReleaseSoRej(9) - Base station release (SO reject) incomingCall(10) - Incoming call baseStatAlertStop(11) - Base station alert stop clientEndedCall(12) - Client ended call activationEndedOtasp(13) - Activation ended OTASP (Over- The-Air Service Provisioning) ndssFailure(14) - NDSS (Network and Distributed System Security) failure maxAccesProbTransmit(15) - Max access probes transmitted persistTestFailure(16) - Persistence test failure ruimNotPresent(17) - RUIM (Removable User Identity Module) not present accessAttemptInProg(18) - Access attempt in progress reasonUnspecified(19) - Reason unspecified recdRetryOrder(20) - Recd retry order modemLocked(21) - Modem Locked gpsCallEnded(22) - GPS call ended smsCallEnded(23) - SMS (Short Message Service) call ended noConcurrentService(24) - No concurrent service noResponseFromBs(25) - No response from BS (Base station) rejectedByBs(26) - Rejected by BS notCompatConcurServ(27) - Not compatible concurrent service accessBlockedByBs(28) - Access blocked by BS alreadyOnTraffChann(29) - Already on Traffic channel emergencyCall(30) - Emergency call dataCallEnded(31) - Data call ended busyHdr(32) - Busy (HDR) billingOrAuthErrHdr(33) - Billing or Auth error (HDR) sysChangeDueToPrlHdr(34) - System change due to PRL (HDR) hdrExitDueToPrl(35) - HDR exit due to PRL (HDR) noSessionHdr(36) - No Session (HDR) callEndedHdr(37) - Call ended (HDR)

INTEGER1 = none2 = invalidClientId3 = badCallType4 = badServiceType5 = expectingNumber6 = nullNumberBuffer7 = invalidDigits8 = outOfRangeNumber9 = nullAalphaBuffer10 = outOfRangeAlphaNumber11 = invalidOtaspActivatCode12 = modemOffline13 = modemLocked14 = unsupportedFlash15 = dialedNumberProhibited16 = onlyE911Calls17 = modemInUse18 = unsupportedServiceType19 = wrongCallType20 = invalidCommandCallState21 = invalidCommandModemState22 = noValidService23 = cannotAnswerIncomingCall24 = badPrivacySetting25 = noCommandBuffers26 = communicationProblem27 = unspecifiedError28 = invalidLastActiveNetwork29 = noCollocatedHdr30 = uimNotPresent · Integer32

Last connect error: none(1) - None invalidClientId(2) - Invalid client ID badCallType(3) - Bad call type badServiceType(4) - Bad service type expectingNumber(5) - Expecting number nullNumberBuffer(6) - Null number buffer invalidDigits(7) - Invalid digits outOfRangeNumber(8) - Out of range number nullAalphaBuffer(9) - Null alpha buffer outOfRangeAlphaNumber(10) - Out of range alpha number invalidOtaspActivatCode(11) - Invalid OTASP activation code modemOffline(12) - Modem offline modemLocked(13) - Modem locked unsupportedFlash(14) - Unsupported flash dialedNumberProhibited(15) - Dialed number prohibited onlyE911Calls(16) - Only E911 calls modemInUse(17) - Modem in use unsupportedServiceType(18) - Unsupported service type wrongCallType(19) - Wrong call type invalidCommandCallState(20) - Invalid command (call state) invalidCommandModemState(21) - Invalid command (modem state) noValidService(22) - No valid service cannotAnswerIncomingCall(23) - Cannot answer incoming call badPrivacySetting(24) - Bad privacy setting noCommandBuffers(25) - No command buffers communicationProblem(26) - Communication problem unspecifiedError(27) - Unspecified error invalidLastActiveNetwork(28) - Invalid last active network noCollocatedHdr(29) - No collocated HDR uimNotPresent(30) - UIM (User Identity Module) not present

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..128) · OCTET STRING · hint 255a

This object indicates Electronic Serial Number (ESN).

INTEGER1 = unknown2 = activated3 = notActivated · Integer32

Modem activation status.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..128) · OCTET STRING · hint 255a

Modem account activation date.

INTEGER1 = unknown2 = home3 = affiliated4 = any · Integer32

This object indicates the roaming preference: unknown(1) - preference unknown home(2) - home networks only affiliated(3) - roaming on affiliated networks any(4) - roaming on any network

Unsigned32

Preferred Roaming List (PRL) version.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Mobile Directory Number (MDN), a dialable number assigned to a wireless phone.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Mobile Station Identifier (MSID), MSID is utilized to distinguish the mobile station being programmed from other mobile stations during messaging and paging processes, including the downloading of programming information to the mobile station.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Mobile Subscriber Lock (MSL).

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Current service status.

INTEGER1 = unknown2 = hybrid3 = evDoOnly4 = oneXRttOnly · Integer32

This object indicates the hybrid mode preference: unknown(1) - preference unknown hybrid(2) - connect to EV-DO/1xRTT services evDoOnly(3) - connect to only EV-DO service oneXRttOnly(4) - connect to only 1xRTT service

INTEGER1 = unknown2 = home3 = roamingWithSid4 = roamingWithoutSid · Integer32

Current 1xRTT roaming status, roaming is a general term in wireless telecommunications that refers to the extending of connectivity service in a location that is different from the home location where the service was registered: unknown(1) - roaming status is unknown. home(2) - connectivity service in home location. roamingWithSid(3) - roaming with SID. roamingWithoutSid(4) - roaming without SID

INTEGER1 = unknown2 = noService3 = amps4 = cdma5 = gsm6 = hdr7 = wcdma8 = gps9 = lte · Integer32

Current idle digital mode: unknown(1) - service is unknown noService(2) - no service amps(3) - Advanced Mobile Phone Service (AMPS) cdma(4) - Code Division Multiple Access (CDMA) gsm(5) - Global System for Mobile communications (GSM) hdr(6) - High Data Rate (HDR) wcdma(7) - Wideband Code-Division Multiple-Access (WCDMA) gps(8) - Global Positioning System (GPS) lte(9) - Long Term Evolution (LTE)

Integer32 (-1..32767)

Current System Identifier (SID), SID is a 15-bit numeric identifiers used by cellular systems to identify the home system of a cellular telephone and by the cellular telephone to determine its roaming status. Value of '-1' indicates SID is 'Not Applicable'.

Integer32 (-1..65535)

Current Network Identification (NID), NID is a 16-bit numeric identifiers used by cellular systems. Value of '-1' indicates NID is 'Not Applicable'.

INTEGER1 = unknown2 = simpleIpOnly3 = mobileIpPreferWithSipFallback4 = mobileIpOnly · Integer32

Current call setup mode. The 1xEV-DO system supports packet data connections to a public or private data network using either mobile IP or simple IP protocol. For simple IP protocol, moving from the coverage area of one PDSN to another PDSN constitutes a change in packet data session. For mobile IP protocol, a packet data session can span several PDSNs as long as the user continuously maintains mobility bindings at the Home Agent (the IP address is persistent). The modes are: unknown(1) - mode is unknown simpleIpOnly(2) - simple IP only mobileIpPreferWithSipFallback(3) - prefer mobile IP with simple IP as fallback mode mobileIpOnly(4) - mobile IP only

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Simple IP (SIP) user name.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Simple IP (SIP) password.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Longitude of the serving base station.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Latitude of the serving base station.

Unsigned32

The number of data profiles configurable.

Unsigned32

The current active data profile.

Integer32 (1..65535)

Profile index, combined with entPhysicalIndex to access the profile table c3gCdmaProfileTable.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Network Access Identifier (NAI). NAI is required to identify the mobile user and the network the mobile user intended to access. The NAI is provided by the mobile node to the dialed ISP during PPP authentication.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object indicates the password for AAA.

INTEGER1 = set2 = notSet · Integer32

Mobile Node (MN) Home Agent (HA) Shared Secret (SS) setting: set(1) - shared secret is set notSet(2) - shared secret is not set

Unsigned32

Mobile Node (MN) Home Agent (HA) Security Parameter Index (SPI).

INTEGER1 = set2 = notSet · Integer32

Mobile Node (MN) Authentication Authorization Accounting (AAA) Shared Secret (SS) setting: set(1) - shared secret is set notSet(2) - shared secret is not set

Unsigned32

Mobile Node (MN) Authentication Authorization Accounting (AAA) Security Parameter Index (SPI).

INTEGER1 = set2 = notSet · Integer32

Reverse tunnel preference.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

A value that represents the type of the IP Address stored in the object c3gHomeAddr.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

A unicast routable address assigned to a Mobile Node, used as the permanent address of the Mobile Node.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

A value that represents the type of the IP Address stored in the object c3gPriHaAddr.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

The primary home agent address.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

A value that represents the type of the IP Address stored in the object c3gSecHaAddr.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

The secondary home agent address.

C3gRssiGeneric RSSI range. (-150..0) · Integer32

Current 1xRTT RSSI value.

C3gEcIoGeneric EcIo range. (-150..0) · Integer32

Current 1xRTT Ec/Io value.

Integer32

Current 1xRTT channel number. Current channel number to which the modem is attached to the base station. Value of '-1' indicates 'No Service'.

INTEGER1 = unknown2 = notAcquired3 = acquired4 = scanning · Integer32

Current 1xRTT channel state. Indicates whether the modem is scanning or has acquired the channel.

Integer32 (1..32)

Band class index, combined with entPhysicalIndex to access the band class table.

Unsigned32

This object contains 1xRTT band class.

C3gRssiGeneric RSSI range. (-150..0) · Integer32

Current EV-DO RSSI value.

C3gEcIoGeneric EcIo range. (-150..0) · Integer32

Current EV-DO Ec/Io value.

Integer32

Current EV-DO channel number. Current channel number to which the modem is attached to the base station. Value of '-1' indicates 'No Service'.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Sector ID of the base station to which the modem is attached.

Unsigned32

Reference: 3GPP2 C.S0024-B v1.0

Subnet mask of the sector, not to be confused with the IP subnet mask.

Unsigned32

Reference: 3GPP2 C.S0024-B v1.0

Color code of the sector.

Unsigned32

Reference: 3GPP2 C.S0024-B v1.0

PN offset. PN offset is a time offset from the beginning of the well-known pseudo-random noise sequence that is used to spread the signal from the base station.

Integer32 · dBm

Received main gain control for the modem. value of '-1' indicates the received main gain control is unavailable.

Integer32 · dBm

Received diversity for the modem. value of '-1' indicates the received diversity is unavailable.

Integer32 · dBm

Transmit total power.

Integer32 · dBm

Transmit gain adjust.

Unsigned32

Carrier to interference ratio. Carrier-to-Interference ratio (C/I) is the ratio of power in an RF carrier to the interference power in the channel.

Unsigned32

This object contains EV-DO band class.

OCTET STRING SIZE (60) · -dBm

Per-second 1xRTT RSSI history. This object contains a per-second history of 1xRTT RSSI values for the last 60 seconds.

OCTET STRING SIZE (60) · -dBm

Per-minute 1xRTT weakest RSSI value history. This object contains a per-minute history of 1xRTT weakest RSSI values for the last 60 minutes. The octet in the string is the weakest RSSI value measured in a minute interval.

OCTET STRING SIZE (72) · -dBm

Per-hour 1xRTT weakest RSSI value history. This object contains a per-hour history of 1xRTT weakest RSSI values for the last 72 hours. The octet in the string is the weakest RSSI value measured in an hour interval.

OCTET STRING SIZE (60) · -dBm

Per-second EV-DO RSSI history. This object contains a per-second history of EV-DO RSSI values for the last 60 seconds.

OCTET STRING SIZE (60) · -dBm

Per-minute EV-DO weakest RSSI value history. This object contains a per-minute history of EV-DO weakest RSSI values for the last 60 minutes. The octet in the string is the weakest RSSI value measured in a minute interval.

OCTET STRING SIZE (72) · -dBm

Per-hour EV-DO weakest RSSI value history. This object contains a per-hour history of EV-DO weakest RSSI values for the last 72 hours. The octet in the string is the weakest RSSI value measured in an hour interval.

INTEGER1 = unknown2 = locked3 = unlocked · Integer32

CDMA Personal Identification Number (PIN) security: unknown(1) - PIN security unknown locked(2) - PIN security is locked unlocked(3) - PIN security is unlocked

INTEGER1 = unknown2 = enabled3 = disabled · Integer32

CDMA power up lock: unknown(1) - power up lock unknown enabled(2) - power up lock enabled disabled(3) - power up lock disabled

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

International Mobile Subscriber Identifier (IMSI), a unique 15-digit code used to identify an individual user on a GSM/LTE network.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

International Mobile Equipment Identifier (IMEI), a unique 15 or 17 digit code used to identify an individual mobile station to a GSM, UMTS or LTE network.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object indicates the Integrated Circuit Card ID (ICCID). The ICCID is defined by the ITU-T recommendation E.118. ICCIDs are stored in the SIM cards and are also engraved or printed on the SIM card body during a process called personalization.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object indicates the Mobile Subscriber Integrated Services Digital Network Number (MSISDN). It is a number uniquely identifying a subscription in a GSM, UMTS or LTE mobile network. It represents the telephone number to the SIM card in a mobile/cellular phone.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Forward Sequence Number (FSN), a message acknowledgement method using sequence number in the forward direction.

INTEGER1 = unknown2 = offLine3 = onLine4 = lowPowerMode · Integer32

Modem status: unknown(1) - modem status is unknown offLine(2) - modem is off line onLine(3) - modem is on line lowPowerMode(4) - modem is in the low power mode

INTEGER1 = unknown2 = home3 = roaming · Integer32

This object indicates the roaming preference.

Unsigned32

Location Area Code (LAC), also called as Tracking Area Code (TAC) in LTE standard. LAC/TAC is given by the base station.

INTEGER1 = unknown2 = noService3 = normal4 = emergencyOnly · Integer32

Current Service Status: unknown(1) - current service status is unknown noService(2) - no service normal(3) - service status is normal emergencyOnly(4) - emergency service only

INTEGER1 = unknown2 = none3 = imsiUnknownInHlr4 = illegalMs5 = imsiUnknownInVlr6 = imeiNotAccepted7 = illegalMe8 = gprsServNotAllowed9 = gprsNonGprsServNotAllow10 = msIdentUnknown11 = implicitlyDetached12 = plmnNotAllowed13 = lacNotAllowed14 = roamingNotAllowed15 = gprsServNotAllowInPlmn16 = noSuitableCellInLa17 = mscTempNotReachable18 = networkFailure19 = macFailure20 = synchFailure21 = congestion22 = gsmAuthenNotAccept23 = servOptionNotSupport24 = reqServOptionNotSub25 = servOptionOutOfOrder26 = callCannotIdentified27 = noPdpContextActivated28 = invalidMandatInfo29 = unpsecProtErr · Integer32

Current service error: unknown(1) - Unknown none(2) - None imsiUnknownInHlr(3) - IMSI unknown in HLR (Home Location Register) illegalMs(4) - Illegal MS (Mobile Station) imsiUnknownInVlr(5) - IMSI unknown in VLR (Visitor Location Register) imeiNotAccepted(6) - IMEI not accepted illegalMe(7) - Illegal ME (Mobile Entity) gprsServNotAllowed(8) - GPRS services not allowed gprsNonGprsServNotAllow(9) - GPRS and non-GPRS services not allowed msIdentUnknown(10) - MS identity unknown implicitlyDetached(11) - Implicitly detached plmnNotAllowed(12) - PLMN not allowed lacNotAllowed(13) - LAC not allowed roamingNotAllowed(14) - Roaming not allowed gprsServNotAllowInPlmn(15) - GPRS services not allowed in this PLMN noSuitableCellInLa(16) - No suitable cells in LA (Location Area) mscTempNotReachable(17) - MSC (Mobile Switching Center) temporarily not reachable networkFailure(18) - Network failure macFailure(19) - MAC failure synchFailure(20) - Synch failure congestion(21) - Congestion gsmAuthenNotAccept(22) - GSM/LTE Authentication not accepted servOptionNotSupport(23) - Service option not supported reqServOptionNotSub(24) - Requested service option not subscribed servOptionOutOfOrder(25) - Service option out of order callCannotIdentified(26) - Call cannot be identified noPdpContextActivated(27) - No PDP context activated invalidMandatInfo(28) - Invalid mandatory info unpsecProtErr(29) - Unspecified protocol error

INTEGER1 = unknown2 = invalid3 = circuitSwitched4 = packetSwitched5 = combined · Integer32

Current service type: unknown(1) - service type is unknown invalid(2) - no service circuitSwitched(3) - circuit switched service packetSwitched(4) - packet switched service combined(5) - combination of circuit and packet switched service

INTEGER1 = unknown2 = none3 = gprs4 = edge5 = umtsWcdma6 = hsdpa7 = hsupa8 = hspa9 = hspaPlus10 = lte · Integer32

Packet Service type: unknown(1) - service type is unknown. none(2) - no service. gprs(3) - General Packet Radio Service (GPRS). edge(4) - Enhanced Data rates for GSM Evolution (EDGE). umtsWcdma(5) - Universal Mobile Telecommunications System (UMTS) / Wideband Code-Division Multiple-Access (W-CDMA). hsdpa(6) - High-Speed Downlink Packet Access (HSDPA) hsdpa(7) - High-Speed Uplink Packet Access (HSUPA) hspa(8) - High-Speed Packet Access (HSPA) hspaPlus(9) - High-Speed Packet Access (HSPA) Plus lte(10) - Long Term Evolution

INTEGER1 = unknown2 = roaming3 = home · Integer32

This object indicates whether the modem is in the home network or is roaming.

INTEGER1 = unknown2 = automatic3 = manual · Integer32

Network selection mode. Can be manual selection mode or automatic selection mode. Set to automatic by default.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Country code. Country code string is given by the base station.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Network code. Network Code string is given by the base station.

Integer32

Mobile Country Code (MCC). Value of '-1' indicates MCC is 'Not Applicable'.

Integer32

Mobile Network Code (MNC). Value of '-1' indicates MNC is 'Not Applicable'.

Unsigned32

Routing Area Code (RAC). RAC is given by the base station.

Unsigned32

Cell Identifier of current cell. Cell ID is given by the base station.

Unsigned32

Primary scrambling code of current cell. The primary scrambling code is typically identified through symbol-by-symbol correlation over the CPICH (Common Pilot Channel) with all codes within the code group, after the primary scrambling code has been identified, the Primary CCPCH can be detected and the system and cell specific BCH information can be read.

INTEGER1 = unknown2 = manual3 = automatic · Integer32

Public Land Mobile Network (PLMN) selection. Can be manual selection mode or automatic selection mode. Set to automatic by default.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Registered PLMN.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

PLMN abbreviated number.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Service provider.

Counter64 (0..18446744073709551615) · bytes

Total number of bytes transmitted for all calls. It is the total number of bytes transmitted by modem, not to be confused with the number of bytes transmitted through the interface.

Counter64 (0..18446744073709551615) · bytes

Total number of bytes received for all calls. It is the total number of bytes received by modem, not to be confused with the number of bytes received from the interface.

Integer32 (1..1000)

Profile index, combined with entPhysicalIndex to access profile table.

C3gPdpType1 = unknown2 = ipV43 = ppp4 = ipV65 = ipV4V6Generic PDP type. · Integer32

This object indicates configured Packet Data Protocol (PDP) type.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Configured PDP/EPS Bearer address. PDP type is defined in c3gGsmPdpProfileType.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object indicates profile Access Point Name (APN). This information is provided by the service provider.

INTEGER1 = unknown2 = none3 = chap4 = pap · Integer32

This object indicates PDP authentication type supported. CHAP and PAP are supported in GSM. The type of authentication to be used is provided by the service provider.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object indicates the username to be used for PDP authentication. This information is provided by the service provider.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object indicates the password to be used for PDP authentication. This information is provided by the service provider.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table.

INTEGER1 = unknown2 = active3 = inactive · Integer32

This object indicates PDP session status of the profile. This is active when the call is established and PDP contextr has become active.

C3gPdpType1 = unknown2 = ipV43 = ppp4 = ipV65 = ipV4V6Generic PDP type. · Integer32

This object indicates current session PDP type.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

Current session PDP context/EPS Bearer address. PDP type is obtained from c3gGsmPdpType.

C3gUmtsQosTrafficClass1 = subscription2 = conversational3 = streaming4 = interactive5 = backgroundUMTS QoS traffic classes: subscription(1) - based on user's subscription conversational(2) - conversational streaming(3) - streaming interactive(4) - interactive background(5) - background · Integer32

Request UMTS QoS traffic classes.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Request UMTS QoS maximum uplink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Request UMTS QoS maximum downlink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Request UMTS QoS guaranteed uplink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Request UMTS QoS guaranteed downlink bit rate.

C3gUmtsQosOrder1 = subscription2 = withDeliverOrder3 = withoutDeliverOrderUMTS QoS delivery order: subscription(1) - based on user's subscription withDeliverOrder(2) - with delivery order withoutDeliverOrder(3) - without delivery order · Integer32

Request UMTS QoS deliver order.

C3gUmtsQosErroneousSdu1 = subscription2 = noDetect3 = errSduDeliver4 = errSduNotDeliverUMTS QoS Delivery of Erroneous Service Data Unit(SDU): subscription(1) - based on user's subscription noDetect(2) - no detect errSduDeliver(3) - erroneous SDUs are delivered errSduNotDeliver(4) - erroneous SDUs are not delivered · Integer32

Request UMTS QoS Delivery of Erroneous SDU.

Unsigned32 (0..1520) · bytes

Request UMTS QoS maximum SDU size, the valid range is between 1 and 1520 bytes. Value of '0' indicates the maximum SDU size is unspecified.

C3gUmtsQosSer1 = subscription2 = oneExpMinus23 = sevenExpMinus34 = oneExpMinus35 = oneExpMinus46 = oneExpMinus57 = oneExpMinus68 = oneExpMinus1UMTS QoS SDU error ratio: subscription(1) - based on user's subscription oneExpMinus2(2) - 1E-2 sevenExpMinus3(3) - 7E-3 oneExpMinus3(4) - 1E-3 oneExpMinus4(5) - 1E-4 oneExpMinus5(6) - 1E-5 oneExpMinus6(7) - 1E-6 oneExpMinus1(8) - 1E-1 · Integer32

Request UMTS QoS SDU error ratio.

C3gUmtsQosBer1 = subscription2 = fiveExpMinus23 = oneExpMinus24 = fiveExpMinus35 = fourExpMinus36 = oneExpMinus37 = oneExpMinus48 = oneExpMinus59 = oneExpMinus610 = sixExpMinus8UMTS QoS residual bit error ratio (BER): subscription(1) - based on user's subscription fiveExpMinus2(2) - 5E-2 oneExpMinus2(3) - 1E-2 fiveExpMinus3(4) - 5E-3 fourExpMinus3(5) - 4E-3 oneExpMinus3(6) - 1E-3 oneExpMinus4(7) - 1E-4 oneExpMinus5(8) - 1E-5 oneExpMinus6(9) - 1E-6 sixExpMinus8(10) - 6E-8 · Integer32

Request UMTS QoS residual bit error ratio.

Unsigned32 (0..4000) · milliseconds

Request UMTS QoS transfer delay in ms, the valid range is between 1 and 4000 ms. Value of '0' indicates the QoS delay is unspecified.

C3gUmtsQosPriority1 = subscription2 = level13 = level24 = level3UMTS QoS traffic handling priority: subscription(1) - based on user's subscription level1(2) - priority level 1 level2(3) - priority level 2 level3(4) - priority level 3 · Integer32

Request UMTS QoS traffic handling priority.

C3gUmtsQosSrcStatDescriptor1 = unknown2 = speechUMTS QoS source statistics descriptor: unknown(1) - unknown speech(2) - speech · Integer32

Request UMTS QoS source statistics descriptor.

C3gUmtsQosSignalIndication1 = notOptimized2 = optimizedUMTS QoS signalling indication: notOptimized(1) - not optimized for signalling traffic optimized(2) - optimized for signalling traffic · Integer32

Request UMTS QoS signalling indication.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table.

C3gUmtsQosTrafficClass1 = subscription2 = conversational3 = streaming4 = interactive5 = backgroundUMTS QoS traffic classes: subscription(1) - based on user's subscription conversational(2) - conversational streaming(3) - streaming interactive(4) - interactive background(5) - background · Integer32

Minimum UMTS QoS traffic classes.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Minimum UMTS QoS maximum uplink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Minimum UMTS QoS maximum downlink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Minimum UMTS QoS guaranteed uplink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Minimum UMTS QoS guaranteed downlink bit rate.

C3gUmtsQosOrder1 = subscription2 = withDeliverOrder3 = withoutDeliverOrderUMTS QoS delivery order: subscription(1) - based on user's subscription withDeliverOrder(2) - with delivery order withoutDeliverOrder(3) - without delivery order · Integer32

Minimum UMTS QoS deliver order.

C3gUmtsQosErroneousSdu1 = subscription2 = noDetect3 = errSduDeliver4 = errSduNotDeliverUMTS QoS Delivery of Erroneous Service Data Unit(SDU): subscription(1) - based on user's subscription noDetect(2) - no detect errSduDeliver(3) - erroneous SDUs are delivered errSduNotDeliver(4) - erroneous SDUs are not delivered · Integer32

Minimum UMTS QoS Delivery of Erroneous SDU.

Unsigned32 (0..1520) · bytes

Minimum UMTS maximum SDU size, the valid range is between 1 and 1520 bytes. Value of '0' indicates the maximum SDU size is unspecified.

C3gUmtsQosSer1 = subscription2 = oneExpMinus23 = sevenExpMinus34 = oneExpMinus35 = oneExpMinus46 = oneExpMinus57 = oneExpMinus68 = oneExpMinus1UMTS QoS SDU error ratio: subscription(1) - based on user's subscription oneExpMinus2(2) - 1E-2 sevenExpMinus3(3) - 7E-3 oneExpMinus3(4) - 1E-3 oneExpMinus4(5) - 1E-4 oneExpMinus5(6) - 1E-5 oneExpMinus6(7) - 1E-6 oneExpMinus1(8) - 1E-1 · Integer32

Minimum UMTS QoS SDU error ratio.

C3gUmtsQosBer1 = subscription2 = fiveExpMinus23 = oneExpMinus24 = fiveExpMinus35 = fourExpMinus36 = oneExpMinus37 = oneExpMinus48 = oneExpMinus59 = oneExpMinus610 = sixExpMinus8UMTS QoS residual bit error ratio (BER): subscription(1) - based on user's subscription fiveExpMinus2(2) - 5E-2 oneExpMinus2(3) - 1E-2 fiveExpMinus3(4) - 5E-3 fourExpMinus3(5) - 4E-3 oneExpMinus3(6) - 1E-3 oneExpMinus4(7) - 1E-4 oneExpMinus5(8) - 1E-5 oneExpMinus6(9) - 1E-6 sixExpMinus8(10) - 6E-8 · Integer32

Minimum UMTS residual bit error ratio.

Unsigned32 (0..4000) · milliseconds

Minimum UMTS transfer delay in ms, the valid range is between 1 and 4000 ms. Value of '0' indicates the QoS delay is unspecified.

C3gUmtsQosPriority1 = subscription2 = level13 = level24 = level3UMTS QoS traffic handling priority: subscription(1) - based on user's subscription level1(2) - priority level 1 level2(3) - priority level 2 level3(4) - priority level 3 · Integer32

Minimum UMTS QoS traffic handling priority.

C3gUmtsQosSrcStatDescriptor1 = unknown2 = speechUMTS QoS source statistics descriptor: unknown(1) - unknown speech(2) - speech · Integer32

Minimum UMTS QoS source statistics descriptor.

C3gUmtsQosSignalIndication1 = notOptimized2 = optimizedUMTS QoS signalling indication: notOptimized(1) - not optimized for signalling traffic optimized(2) - optimized for signalling traffic · Integer32

Minimum UMTS QoS signalling indication.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table.

C3gUmtsQosTrafficClass1 = subscription2 = conversational3 = streaming4 = interactive5 = backgroundUMTS QoS traffic classes: subscription(1) - based on user's subscription conversational(2) - conversational streaming(3) - streaming interactive(4) - interactive background(5) - background · Integer32

Negotiated UMTS QoS traffic classes.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Negotiated UMTS QoS maximum uplink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Negotiated UMTS QoS maximum downlink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Negotiated UMTS QoS guaranteed uplink bit rate.

C3gUmtsQosLinkBitRate1 = subscription2 = rate16kbps3 = rate32kbps4 = rate64kbps5 = rate128kbps6 = rate256kbps7 = rate384kbps8 = rate1dot8mbps9 = rate3dot6mbps10 = rate7dot2mbps11 = rate14dot4mbps12 = rate56kbps13 = rate1dot15mbps14 = rate1dot6mbps15 = rate2dot1mbps16 = rate2dot8mbps17 = rate4dot2mbps18 = rate8dot4mbpsUMTS QoS link bit rate: subscription(1) - based on user's subscription rate16kbps(2) - 16 Kbps rate32kbps(3) - 32 Kbps rate64kbps(4) - 64 Kbps rate128kbps(5) - 128 Kbps rate256kbps(6) - 256 Kbps rate384kbps(7) - 384 Kbps rate1dot8mbps(8) - 1.8 Mbps rate3dot6mbps(9) - 3.6 Mbps rate7dot2mbps(10) - 7.2 Mbps rate14dot4mbps(11) - 14.4 Mbps rate56kbps(12) - 56 Kbps rate1dot15mbps(13) - 1.15 Mbps rate1dot6mbps(14) - 1.6 Mbps rate2dot1mbps(15) - 2.1 Mbps rate2dot8mbps(16) - 2.8 Mbps rate4dot2mbps(17) - 4.2 Mbps rate8dot4mbps(18) - 8.4 Mbps · Integer32

Negotiated UMTS QoS guaranteed downlink bit rate.

C3gUmtsQosOrder1 = subscription2 = withDeliverOrder3 = withoutDeliverOrderUMTS QoS delivery order: subscription(1) - based on user's subscription withDeliverOrder(2) - with delivery order withoutDeliverOrder(3) - without delivery order · Integer32

Negotiated UMTS QoS deliver order.

C3gUmtsQosErroneousSdu1 = subscription2 = noDetect3 = errSduDeliver4 = errSduNotDeliverUMTS QoS Delivery of Erroneous Service Data Unit(SDU): subscription(1) - based on user's subscription noDetect(2) - no detect errSduDeliver(3) - erroneous SDUs are delivered errSduNotDeliver(4) - erroneous SDUs are not delivered · Integer32

Negotiated UMTS QoS Delivery of Erroneous SDU.

Unsigned32 (0..1520) · bytes

Negotiated UMTS QoS maximum SDU size, the valid range is between 1 and 1520 bytes. Value of '0' indicates the maximum SDU size is subscribed.

C3gUmtsQosSer1 = subscription2 = oneExpMinus23 = sevenExpMinus34 = oneExpMinus35 = oneExpMinus46 = oneExpMinus57 = oneExpMinus68 = oneExpMinus1UMTS QoS SDU error ratio: subscription(1) - based on user's subscription oneExpMinus2(2) - 1E-2 sevenExpMinus3(3) - 7E-3 oneExpMinus3(4) - 1E-3 oneExpMinus4(5) - 1E-4 oneExpMinus5(6) - 1E-5 oneExpMinus6(7) - 1E-6 oneExpMinus1(8) - 1E-1 · Integer32

Negotiated UMTS QoS SDU error ratio.

C3gUmtsQosBer1 = subscription2 = fiveExpMinus23 = oneExpMinus24 = fiveExpMinus35 = fourExpMinus36 = oneExpMinus37 = oneExpMinus48 = oneExpMinus59 = oneExpMinus610 = sixExpMinus8UMTS QoS residual bit error ratio (BER): subscription(1) - based on user's subscription fiveExpMinus2(2) - 5E-2 oneExpMinus2(3) - 1E-2 fiveExpMinus3(4) - 5E-3 fourExpMinus3(5) - 4E-3 oneExpMinus3(6) - 1E-3 oneExpMinus4(7) - 1E-4 oneExpMinus5(8) - 1E-5 oneExpMinus6(9) - 1E-6 sixExpMinus8(10) - 6E-8 · Integer32

Negotiated UMTS QoS residual bit error ratio.

Unsigned32 (0..4000) · milliseconds

Negotiated UMTS QoS transfer delay in ms, the valid range is between 1 and 4000 ms. Value of '0' indicates the QoS delay is subscribed.

C3gUmtsQosPriority1 = subscription2 = level13 = level24 = level3UMTS QoS traffic handling priority: subscription(1) - based on user's subscription level1(2) - priority level 1 level2(3) - priority level 2 level3(4) - priority level 3 · Integer32

Negotiated UMTS QoS traffic handling priority.

C3gUmtsQosSrcStatDescriptor1 = unknown2 = speechUMTS QoS source statistics descriptor: unknown(1) - unknown speech(2) - speech · Integer32

Negotiated UMTS QoS source statistics descriptor.

C3gUmtsQosSignalIndication1 = notOptimized2 = optimizedUMTS QoS signalling indication: notOptimized(1) - not optimized for signalling traffic optimized(2) - optimized for signalling traffic · Integer32

Negotiated UMTS QoS signalling indication.

C3gGprsQosPrecedence1 = subscription2 = highPriority3 = normalPriority4 = lowPriorityGPRS QoS precedence: subscription(1) - based on user's subscription highPriority(2) - high priority normalPriority(3) - normal priority lowPriority(4) - low priority · Integer32

Request GPRS QoS precedence.

C3gGprsQosDelay1 = subscription2 = delayClass13 = delayClass24 = delayClass35 = delayClass4GPRS QoS delay classes: subscription(1) - based on user's subscription delayClass1(2) - delay class 1 delayClass2(3) - delay class 2 delayClass3(4) - delay class 3 delayClass4(5) - delay class 4 · Integer32

Request GPRS QoS delay classes.

C3gGprsQosReliability1 = subscription2 = ackGtpLlcRlcProtData3 = unAckGtpAckLlcRlcProtData4 = unAckGtpLlcAckRlcProtData5 = unAckGtpLlcRlcProtData6 = unAckGtpLlcRlcUnProtDataGPRS QoS reliability: subscription(1) - based on user's subscription ackGtpLlcRlcProtData(2) - acknowledged GTP, LLC, and RLC; protected data unAckGtpAckLlcRlcProtData(3) - unacknowledged GTP, acknowledged LLC and RLC; protected data unAckGtpLlcAckRlcProtData(4) - unacknowledged GTP and LLC, acknowledged RLC; protected data unAckGtpLlcRlcProtData(5) - unacknowledged GTP, LLC, and RLC; protected data unAckGtpLlcRlcUnProtData(6) - unacknowledged GTP, LLC, and RLC; unprotected data · Integer32

Request GPRS QoS reliability.

C3gGprsQosPeakRate1 = subscription2 = upTo1kops3 = upTo2kops4 = upTo4kops5 = upTo8kops6 = upTo16kops7 = upTo32kops8 = upTo64kops9 = upTo128kops10 = upTo256kopsGPRS QoS peak rate: subscription(1) - based on user's subscription upTo1kops(2) - up to 1000 octet/second upTo2kops(3) - up to 2000 octet/second upTo4kops(4) - up to 4000 octet/second upTo8kops(5) - up to 8000 octet/second upTo16kops(6) - up to 16000 octet/second upTo32kops(7) - up to 32000 octet/second upTo64kops(8) - up to 64000 octet/second upTo128kops(9) - up to 128000 octet/second upTo256kops(10) - up to 256000 octet/second · Integer32

Request GPRS QoS peak rate.

C3gGprsQosMeanRate1 = subscription2 = rate1003 = rate2004 = rate5005 = rate1k6 = rate2k7 = rate5k8 = rate10k9 = rate20k10 = rate50k11 = rate100k12 = rate200k13 = rate500k14 = rate1m15 = rate2m16 = rate5m17 = rate10m18 = rate20m19 = rate50m20 = resv121 = resv222 = resv323 = resv424 = resv525 = resv626 = resv727 = resv828 = resv929 = resv1030 = resv1131 = resv1232 = bestEffortGPRS QoS mean rate: subscription(1) - based on user's subscription rate100(2) - 100 octet/hour rate200(3) - 200 octet/hour rate500(4) - 500 octet/hour rate1k(5) - 1000 octet/hour rate2k(6) - 2000 octet/hour rate5k(7) - 5000 octet/hour rate10k(8) - 10000 octet/hour rate20k(9) - 20000 octet/hour rate50k(10) - 50000 octet/hour rate100k(11) - 100000 octet/hour rate200k(12) - 200000 octet/hour rate500k(13) - 500000 octet/hour rate1m(14) - 1000000 octet/hour rate2m(15) - 2000000 octet/hour rate5m(16) - 5000000 octet/hour rate10m(17) - 10000000 octet/hour rate20m(18) - 20000000 octet/hour rate50m(19) - 50000000 octet/hour resv1(20) - reserved 1 (for future use) resv2(21) - reserved 2 (for future use) resv3(22) - reserved 3 (for future use) resv4(23) - reserved 4 (for future use) resv5(24) - reserved 5 (for future use) resv6(25) - reserved 6 (for future use) resv7(26) - reserved 7 (for future use) resv8(27) - reserved 8 (for future use) resv9(28) - reserved 9 (for future use) resv10(29) - reserved 10 (for future use) resv11(30) - reserved 11 (for future use) resv12(31) - reserved 12 (for future use) bestEffort(32) - best effort · Integer32 · octet-per-hour

Request GPRS QoS mean rate.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table.

C3gGprsQosPrecedence1 = subscription2 = highPriority3 = normalPriority4 = lowPriorityGPRS QoS precedence: subscription(1) - based on user's subscription highPriority(2) - high priority normalPriority(3) - normal priority lowPriority(4) - low priority · Integer32

Minimum GPRS QoS precedence.

C3gGprsQosDelay1 = subscription2 = delayClass13 = delayClass24 = delayClass35 = delayClass4GPRS QoS delay classes: subscription(1) - based on user's subscription delayClass1(2) - delay class 1 delayClass2(3) - delay class 2 delayClass3(4) - delay class 3 delayClass4(5) - delay class 4 · Integer32

Minimum GPRS QoS delay classes.

C3gGprsQosReliability1 = subscription2 = ackGtpLlcRlcProtData3 = unAckGtpAckLlcRlcProtData4 = unAckGtpLlcAckRlcProtData5 = unAckGtpLlcRlcProtData6 = unAckGtpLlcRlcUnProtDataGPRS QoS reliability: subscription(1) - based on user's subscription ackGtpLlcRlcProtData(2) - acknowledged GTP, LLC, and RLC; protected data unAckGtpAckLlcRlcProtData(3) - unacknowledged GTP, acknowledged LLC and RLC; protected data unAckGtpLlcAckRlcProtData(4) - unacknowledged GTP and LLC, acknowledged RLC; protected data unAckGtpLlcRlcProtData(5) - unacknowledged GTP, LLC, and RLC; protected data unAckGtpLlcRlcUnProtData(6) - unacknowledged GTP, LLC, and RLC; unprotected data · Integer32

Minimum GPRS QoS reliability.

C3gGprsQosPeakRate1 = subscription2 = upTo1kops3 = upTo2kops4 = upTo4kops5 = upTo8kops6 = upTo16kops7 = upTo32kops8 = upTo64kops9 = upTo128kops10 = upTo256kopsGPRS QoS peak rate: subscription(1) - based on user's subscription upTo1kops(2) - up to 1000 octet/second upTo2kops(3) - up to 2000 octet/second upTo4kops(4) - up to 4000 octet/second upTo8kops(5) - up to 8000 octet/second upTo16kops(6) - up to 16000 octet/second upTo32kops(7) - up to 32000 octet/second upTo64kops(8) - up to 64000 octet/second upTo128kops(9) - up to 128000 octet/second upTo256kops(10) - up to 256000 octet/second · Integer32

Minimum GPRS QoS peak rate.

C3gGprsQosMeanRate1 = subscription2 = rate1003 = rate2004 = rate5005 = rate1k6 = rate2k7 = rate5k8 = rate10k9 = rate20k10 = rate50k11 = rate100k12 = rate200k13 = rate500k14 = rate1m15 = rate2m16 = rate5m17 = rate10m18 = rate20m19 = rate50m20 = resv121 = resv222 = resv323 = resv424 = resv525 = resv626 = resv727 = resv828 = resv929 = resv1030 = resv1131 = resv1232 = bestEffortGPRS QoS mean rate: subscription(1) - based on user's subscription rate100(2) - 100 octet/hour rate200(3) - 200 octet/hour rate500(4) - 500 octet/hour rate1k(5) - 1000 octet/hour rate2k(6) - 2000 octet/hour rate5k(7) - 5000 octet/hour rate10k(8) - 10000 octet/hour rate20k(9) - 20000 octet/hour rate50k(10) - 50000 octet/hour rate100k(11) - 100000 octet/hour rate200k(12) - 200000 octet/hour rate500k(13) - 500000 octet/hour rate1m(14) - 1000000 octet/hour rate2m(15) - 2000000 octet/hour rate5m(16) - 5000000 octet/hour rate10m(17) - 10000000 octet/hour rate20m(18) - 20000000 octet/hour rate50m(19) - 50000000 octet/hour resv1(20) - reserved 1 (for future use) resv2(21) - reserved 2 (for future use) resv3(22) - reserved 3 (for future use) resv4(23) - reserved 4 (for future use) resv5(24) - reserved 5 (for future use) resv6(25) - reserved 6 (for future use) resv7(26) - reserved 7 (for future use) resv8(27) - reserved 8 (for future use) resv9(28) - reserved 9 (for future use) resv10(29) - reserved 10 (for future use) resv11(30) - reserved 11 (for future use) resv12(31) - reserved 12 (for future use) bestEffort(32) - best effort · Integer32 · octet-per-hour

Minimum GPRS QoS mean rate.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table.

C3gGprsQosPrecedence1 = subscription2 = highPriority3 = normalPriority4 = lowPriorityGPRS QoS precedence: subscription(1) - based on user's subscription highPriority(2) - high priority normalPriority(3) - normal priority lowPriority(4) - low priority · Integer32

Negotiated GPRS QoS precedence.

C3gGprsQosDelay1 = subscription2 = delayClass13 = delayClass24 = delayClass35 = delayClass4GPRS QoS delay classes: subscription(1) - based on user's subscription delayClass1(2) - delay class 1 delayClass2(3) - delay class 2 delayClass3(4) - delay class 3 delayClass4(5) - delay class 4 · Integer32

Negotiated GPRS QoS delay classes.

C3gGprsQosReliability1 = subscription2 = ackGtpLlcRlcProtData3 = unAckGtpAckLlcRlcProtData4 = unAckGtpLlcAckRlcProtData5 = unAckGtpLlcRlcProtData6 = unAckGtpLlcRlcUnProtDataGPRS QoS reliability: subscription(1) - based on user's subscription ackGtpLlcRlcProtData(2) - acknowledged GTP, LLC, and RLC; protected data unAckGtpAckLlcRlcProtData(3) - unacknowledged GTP, acknowledged LLC and RLC; protected data unAckGtpLlcAckRlcProtData(4) - unacknowledged GTP and LLC, acknowledged RLC; protected data unAckGtpLlcRlcProtData(5) - unacknowledged GTP, LLC, and RLC; protected data unAckGtpLlcRlcUnProtData(6) - unacknowledged GTP, LLC, and RLC; unprotected data · Integer32

Negotiated GPRS QoS reliability.

C3gGprsQosPeakRate1 = subscription2 = upTo1kops3 = upTo2kops4 = upTo4kops5 = upTo8kops6 = upTo16kops7 = upTo32kops8 = upTo64kops9 = upTo128kops10 = upTo256kopsGPRS QoS peak rate: subscription(1) - based on user's subscription upTo1kops(2) - up to 1000 octet/second upTo2kops(3) - up to 2000 octet/second upTo4kops(4) - up to 4000 octet/second upTo8kops(5) - up to 8000 octet/second upTo16kops(6) - up to 16000 octet/second upTo32kops(7) - up to 32000 octet/second upTo64kops(8) - up to 64000 octet/second upTo128kops(9) - up to 128000 octet/second upTo256kops(10) - up to 256000 octet/second · Integer32

Negotiated GPRS QoS peak rate.

C3gGprsQosMeanRate1 = subscription2 = rate1003 = rate2004 = rate5005 = rate1k6 = rate2k7 = rate5k8 = rate10k9 = rate20k10 = rate50k11 = rate100k12 = rate200k13 = rate500k14 = rate1m15 = rate2m16 = rate5m17 = rate10m18 = rate20m19 = rate50m20 = resv121 = resv222 = resv323 = resv424 = resv525 = resv626 = resv727 = resv828 = resv929 = resv1030 = resv1131 = resv1232 = bestEffortGPRS QoS mean rate: subscription(1) - based on user's subscription rate100(2) - 100 octet/hour rate200(3) - 200 octet/hour rate500(4) - 500 octet/hour rate1k(5) - 1000 octet/hour rate2k(6) - 2000 octet/hour rate5k(7) - 5000 octet/hour rate10k(8) - 10000 octet/hour rate20k(9) - 20000 octet/hour rate50k(10) - 50000 octet/hour rate100k(11) - 100000 octet/hour rate200k(12) - 200000 octet/hour rate500k(13) - 500000 octet/hour rate1m(14) - 1000000 octet/hour rate2m(15) - 2000000 octet/hour rate5m(16) - 5000000 octet/hour rate10m(17) - 10000000 octet/hour rate20m(18) - 20000000 octet/hour rate50m(19) - 50000000 octet/hour resv1(20) - reserved 1 (for future use) resv2(21) - reserved 2 (for future use) resv3(22) - reserved 3 (for future use) resv4(23) - reserved 4 (for future use) resv5(24) - reserved 5 (for future use) resv6(25) - reserved 6 (for future use) resv7(26) - reserved 7 (for future use) resv8(27) - reserved 8 (for future use) resv9(28) - reserved 9 (for future use) resv10(29) - reserved 10 (for future use) resv11(30) - reserved 11 (for future use) resv12(31) - reserved 12 (for future use) bestEffort(32) - best effort · Integer32 · octet-per-hour

Negotiated GPRS QoS mean rate.

C3gRssiGeneric RSSI range. (-150..0) · Integer32

The GPRS/UMTS/LTE RSSI value.

C3gEcIoGeneric EcIo range. (-150..0) · Integer32

The GPRS, UMTS or LTE Ec/Io value.

INTEGER1 = unknown2 = invalid3 = none4 = gsm8505 = gsm9006 = gsm18007 = gsm19008 = wcdma8009 = wcdma85010 = wcdma190011 = wcdma210012 = lteBand · Integer32

GPRS/UMTS/LTE band to which the modem is attached. Refer CISCO-WAN-CELL-EXT-MIB for LTE band number when in LTE mode.

Unsigned32

Channel number to which the modem is attached. This is only applicable in 3G technology mode. Refer CISCO-WAN-CELL-EXT-MIB for the LTE uplink and downlink channel values

Unsigned32

This object indicates the current total number of nearby cell in the c3gGsmNearbyCellTable. User can poll this object to get the total number of nearby cell before polling c3gGsmNearbyCellTable.

Integer32 (1..100)

Nearby cell index, combined with entPhysicalIndex to access the Nearby cell table c3gGsmNearbyCellTable.

Unsigned32

Nearby cell primary scrambling code.

Integer32 (-150..0) · dB

Nearby cell Received Signal Code Power (RSCP).

C3gEcIoGeneric EcIo range. (-150..0) · Integer32 · dB

Nearby cell Ec/Io measurement.

OCTET STRING SIZE (60) · -dBm

Per-second RSSI history. This object contains a per-second history of RSSI values for the last 60 seconds.

OCTET STRING SIZE (60) · -dBm

Per-minute weakest RSSI value history. This object contains a per-minute history of weakest RSSI values for the last 60 minutes. The octet in the string is the weakest RSSI value measured in a minute interval.

OCTET STRING SIZE (72) · -dBm

Per-hour weakest RSSI value history. This object contains a per-hour history of weakest RSSI values for the last 72 hours. The octet in the string is the weakest RSSI value measured in an hour interval.

INTEGER1 = unknown2 = disabled3 = enabled · Integer32

Card Holder Verification 1 (CHV1), if enabled, the PIN will be verified, if disabled, the PIN will not be verified.

INTEGER1 = unknown2 = ok3 = notInserted4 = removed5 = initFailure6 = generalFailure7 = locked8 = chv1Blocked9 = chv2Blocked10 = chv1Rejected11 = chv2Rejected12 = mepLocked13 = networkRejected · Integer32

SIM status. Indicates whether the SIM is present or removed from the SIM socket, and its current status.

INTEGER1 = unknown2 = none3 = enterChv14 = enterChv25 = enterUnblockChv16 = enterUnblockChv27 = enterMepCode · Integer32

If the SIM is protected (for example, because of CHV1 enabled), it will indicate the type of user operation required.

Unsigned32

Indicates the number of attempts remaining in case the SIM is locked. If the number of retries becomes zero, the SIM is blocked and becomes unusable.

INTEGER1 = unKnown2 = standAlone3 = msBased4 = msAssist5 = reserved · Integer32

Mode of Location base service selected. unKnown - mode selection unkown standAlone - Standalone mode msBased - MS-Based mode msAssist - MS-Assist mode reserved - reserved for future use

INTEGER1 = gpsDisabled2 = gpsAcquiring3 = gpsEnabled4 = gpsLocError · Integer32

Location base service state. gpsDisabled - GPS is disabled gpsEnabled - GPS is enabled gpsLocError - GPS encounters error gpsAcquiring - GPS is acquiring fix

INTEGER1 = offline2 = noService3 = noConnection4 = noData5 = sessionBusy6 = reserved7 = gpsDisabled8 = connectionFailed9 = errorState10 = clientEnded11 = uiEnded12 = networkEnded13 = timeout14 = privacyLevel15 = networkAccessError16 = fixError17 = pdeRejected18 = trafficChannelExited19 = e91120 = serverError21 = staleBSinformation22 = resourceContention23 = authenticationParameterFailed24 = authenticationFailedLocal25 = authenticationFailedNetwork26 = vxLcsAgentAuthFail27 = unknownSystemError28 = unsupportedService29 = subscriptionViolation30 = desiredFixMethodFailed31 = antennaSwitch32 = noTxConfirmationReceived33 = normalEndOfSession34 = noErrorFromNetwork35 = noResourcesLeftOnNetwork36 = positionServerNotAvailable37 = unsupportedProtocolVersion38 = ssmolrErrorSystemFailure39 = ssmolrErrorUnexpectedDataValue40 = ssmolrErrorDataMissing41 = ssmolrErrorFacilityNotSupported42 = ssmolrErrorSsSubscriptionViolation43 = ssmolrErrorPositionMethodFailure44 = ssmolrErrorUndefined45 = smlcTimeout46 = mtGguardTimeExpired47 = additionalAssistanceNeeded48 = noFixError · Integer32

Reference: Refer to the following documents for the error code's full definitions. Sierra Wireless CDMA EVDO CnS Reference_1.2.pdf under Location Based Services section.

Location base service fix error code.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Location base service Latitude.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Location base service longitude.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Location base service timestamp.

Unsigned32 · degrees

GPS Uncertainty parameter Angle, in degrees for the Uncertainty info returned by the GPS device while doing a location fix.

Unsigned32 · meters

GPS Uncertainty parameter A, value in meters for the Uncertainty info returned by the GPS device while doing a location fix.

Unsigned32 · meters

GPS Uncertainty parameter position, value in meters for the Uncertainty info returned by the GPS device while doing a location fix.

INTEGER1 = none2 = twoDimension3 = threeDimension · Integer32

The type of location fix in Location Base service. none - default case, while LBS is not enabled. twoDimension - 2D location fix. threeDimension - 3D location fix.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether the height returned by the GPS device is valid during location fix.

Integer32 (-500..500) · meters

This object indicates the GPS height parameter returned by the GPS device while performing location fix.

Unsigned32 · meters

GPS parameter vertical velocity parameter returned by the GPS device while performing location fix.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether the Velocity value returned by the GPS device is valid.

Unsigned32 · degrees

The compass direction toward which the GPS receiver is (or should be) moving.

Unsigned32 · meters per second

Horizontal Velocity in meters per second the GPS device is heading. This is the value returned by the GPS satellite relative to the last horizontal location of the GPS device. If at Time X satellite sees the location of GPS device is L1 and then at Time Y satellite sees the location is L2 then speed is (L2 - L1) / ( Y - X).

Unsigned32 · meters per second

Vertical Velocity in meters per second the GPS device is heading. This is the value returned by the GPS satellite relative to the last vertical location of the GPS device. If at Time X satellite sees the location of GPS device is L1 and then at Time Y satellite sees the location is L2 then speed is (L2 - L1) / ( Y - X).

Unsigned32 · centimeters

Horizontal Estimated Position Error returned by the GPS satellite for current position of the GPS device.

Gauge32

Number of GPS satellites in vision to the modem while GPS tracking is on.

Integer32 (1..1000)

An index that is assigned to each satellite under a modem and in combination with entPhysicalIndex uniquely identify it. This index is assigned arbitrarily by the engine and is not saved over reboots.

Integer32

Reference: Refer to the following documents for detailed information of Satellites. Sierra Wireless CDMA EVDO CnS Reference_1.2.pdf under Location Based Services section

Each Satellite is assigned a unique number within this device.This object can be used to locate a particular satellite under a modem.

Integer32 · degrees

Reference: Refer to the following documents for detailed information of Satellites elevation. Sierra Wireless CDMA EVDO CnS Reference_1.2.pdf under Location Based Services section

Angle of Elevation between the GPS antenna pointing direction, directly towards the satellite, and the local horizontal plane. It is the up-down angle

Integer32 · degrees

Reference: Refer to the following documents for detailed information of Satellites Azimuth. Sierra Wireless CDMA EVDO CnS Reference_1.2.pdf under Location Based Services section

Azimuth of the current satellite in context referenced by the Satellite InfoIndex. Azimuth is the degree of rotation of the satellites dish on its vertical plane.

Integer32 · db

Reference: Refer to the following documents for detailed information of signal to noise ration in LBS. Sierra Wireless CDMA EVDO CnS Reference_1.2.pdf under Location Based Services section

Signal to Noise Ratio(SNR) of received GPS signal. SNR is refered to as the signal strength in GPS standards.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Is this satellite in line of sight to the modem used in calculating the GPS location?

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates the availability of SMS Service.

Counter32 · msgs

Number of SMS messages which have been sent successfully.

Counter32 · msgs

Number of SMS message that could not be sent.

Gauge32 · msgs

Number of SMS message records space used in the Incoming SMS message storage. One standard SMS message (cdma or gsm) occupies 1 unit of record storage space. A big SMS message can span 'n' sms record space but still be called as 1 SMS message. Storage used can be greater than or equal to total number of Incoming SMS received.

Gauge32 · msgs

The number of SMS messages record space left unused in the Incoming SMS message storage. This is equal to c3gSmsInSmsStorageMax - c3gSmsInSmsStorageUsed.

Gauge32 · msgs

Number of successful archive of Incoming SMS messages since router reload. Each SMS message occupies x bytes of space. So if the incoming message is huge, then it is archived as multiple of x bytes but still called as one SMS message. This is the difference between c3gSmsInSmsArchiveCount and c3gSmsInSmsArchived.

Gauge32 · msgs

The number of Incoming SMS messages that could not be archived since device was reloaded.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

URL of the sms archive directory on the ftp server. The url will be of this format ftp://x.y.z.k/user/dirname

INTEGER1 = unknown2 = success3 = copySmsHeader4 = copySmsBody5 = sent6 = receivedSentNotification7 = receivedOutMsgNumber8 = receivedOutMsgStatus · Integer32

Status of the last send operation of outgoing SMS message to the network.

Counter32

Number of SMS messages which have been received successfully and stored in router. These SMS's are a mirror copy of SMS stored in Modem or SIM

Counter32

Number of SMS messages which have been deleted since router boot up. This does not include SMS messages that are already archived.

Counter64 (0..18446744073709551615) · msgs

Number of SMS message records space allocated in the router's DRAM to store Incoming SMS messages.

Counter32 · msgs

Number of incoming SMS messages that triggered callback.

Gauge32 · msgs

Number of outgoing SMS messages that are in pending queue of the router.

Gauge32 · msgs

Number of successfull archive of outgoing SMS messages since router reload.

Gauge32 · msgs

Number of failed archive of outgoing SMS messages since router reload.

Gauge32 · msgs

Number of Incoming SMS messages that are successfully archived since router reload.