(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2002/0067742 A1
`Or et al.
`(43) Pub. Date:
`Jun. 6, 2002
`
`US 2002OO67742A1
`
`(54) MANAGEMENT OF WAP GATEWAY
`THROUGH SNMP
`(76) Inventors: Alexander Or, Nesher (IL); Arcady
`Chernyak, Rosh-HaAin (IL); Haim
`Rochberger, Tel-Mond (IL)
`Correspondence Address:
`SUGHRUE, MION, ZINN, MACPEAK &
`SEAS, PLLC
`2100 PENNSYLVANIAAVENUE, N.W.
`WASHINGTON, DC 20037-3213 (US)
`(21) Appl. No.:
`09/729,234
`
`(22) Filed:
`
`Dec. 5, 2000
`
`Publication Classification
`
`(51) Int. Cl." .............................. H04J 11/00; H04J 3/16;
`HO4J 3/22
`(52) U.S. Cl. ............................................ 370/466; 370/203
`(57)
`ABSTRACT
`A System and method for managing a WAP gateway through
`SNMP, by using a MIB. The MIB of the present invention
`contains a number of different details about the WAP gate
`way, and enables various operational parameters of the WAP
`gateway to be monitored and controlled.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`WAP gateway device
`(12)
`
`SNMP agent
`(14)
`
`
`
`local MIB (16)
`
`central server (22)
`
`management process
`(18)
`
`central MIB (Set of
`MIBs) (24)
`
`
`
`MIB browser (26)
`
`20
`
`Adobe - Exhibit 1024, page 1
`
`

`

`Patent Application Publication
`
`Jun. 6, 2002
`
`US 2002/0067742 A1
`
`Figure 1
`
`
`
`
`
`
`
`WAP gateway device
`(12)
`
`SNMP agent
`(14)
`
`local MIB (16)
`
`
`
`
`
`
`
`
`
`central server (22)
`
`management process
`(18)
`
`central MIB (Set of
`MIBs) (24)
`
`MIB browser (26)
`
`20
`
`Adobe - Exhibit 1024, page 2
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`MANAGEMENT OF WAP GATEWAY THROUGH
`SNMP
`
`FIELD AND BACKGROUND OF THE
`INVENTION
`0001. The present invention is of a method and a system
`for managing a WAP (wireless application protocol) gate
`way through SNMP (Simple Network Management Proto
`col), and in particular, of Such a System and method for
`management with SNMP in which the necessary details of
`the WAP gateway are stored in a MIB (Management Infor
`mation Base).
`0002 Cellular telephones are becoming increasingly
`popular for portable telephone use, particularly for users
`who are interested in rapid, mobile data communication. AS
`the amount of computational power and memory Space
`which are available in Such Small, portable electronic
`devices becomes increased, a demand has arisen for different
`types of communication Services through Such devices. In
`particular, users have demanded that cellular telephones
`receive many different types of multimedia data, including
`e-mail (electronic mail) messages and Web pages.
`0003. In response to such demands, and to extend the
`power and efficacy of operation of portable, wireless elec
`tronic communication devices, the WAP (wireless applica
`tion protocol) standard has been developed. WAP is now the
`Standard for the presentation and delivery of wireless data,
`including multimedia and other information, and telephony
`Services, on mobile telephones and other types of wireleSS
`communication devices. WAP is designed to efficiently
`provide both multimedia and telephony Services to Such
`wireleSS communication devices, given the limitations of
`wireleSS networks and of the electronic devices themselves.
`In particular, WAP is able to connect a cellular telephone to
`the Internet through a wireleSS network, Such that the
`cellular telephone becomes another computational device on
`the Internet.
`0004. The WAP gateway is the most important element
`for building a network in order to access the Internet from
`a cellular telephone. The WAP gateway is required as a
`mediator and translator between the protocols and function
`ality of the Internet, and the protocols and functionality of
`the cellular telephone. In particular, the limitations of the
`cellular telephone in terms of both hardware components
`and capability of executing Software result in a requirement
`for protocols which are adjusted for the cellular telephone,
`and which therefore differ from the protocols provided
`through the Internet. For example, the WAP protocol itself is
`binary, while Internet protocols are character-based. The
`WAP gateway must therefore be able to translate the WAP
`protocol to WML, which is XML compliant.
`0005. The corresponding WAP-based standards above
`define the functionality of WAP gateway in many respects,
`for example with regard to protocol translation, Security,
`access authentication, operation with different types of basic
`communication protocols such as GSM, CDMA, TDMA and
`So forth. But none of these Standards regulates management
`
`of WAP gateways, possible because most WAP gateway
`(translation) devices are implemented as a proxy server,
`which are usually not managed by SNMP But, in order to
`Support the amount of traffic which is required, a router is
`more Suitable and more robust as infrastructure for the WAP
`gateway (translation) device. All routers are managed using
`SNMP, as these devices are part of the Internet infrastruc
`ture, and SNMP is a standard management tool for such
`infrastructure devices.
`0006 The best way to define the management system for
`Internet network devices Such as routers or gateways is to
`define the specified Management Information Base (MIB) of
`that device according to Simple Network Management Pro
`tocol (SNMP, as described in RFC 1157, Simple Network
`Management Protocol (SNMP). J. D. Case, M. Fedor, M. L.
`Schoffstall, C. Davin. May 1, 1990). SNMP is a widely used
`mechanism to manage networks and network devices of
`different types. SNMP is a connectionless protocol, which is
`designed to operate over UDP (User Datagram Protocol, as
`described in RFC 768, J. Postel, August 1980). It is typically
`implemented with an agent process (or “SNMP agent”),
`which collects Specific types of data and information about
`the network device which is being managed according to
`SNMP, and a management process for managing the net
`work device. The local data is collected by the management
`process through the use of two commands: GET (and the
`corresponding command, GET-NEXT), which enables the
`management process to retrieve object values from the
`SNMP agent; and SET, which enables the management
`process to set these object values. In addition, the TRAP
`command enables the SNMP agent to report an event to the
`management proceSS. The SNMP agent must also Send a
`RESPONSE to the management process upon receiving one
`of the first two management process commands.
`0007. The collected data is then stored in a central
`database by the management process. The management
`process is then able to perform various actions and to collect
`and report the data according to a central MIB, which
`therefore enables network operators to manage and control
`the functions of each network device. The MIB actually
`defines the data which can be collected about the network
`according to SNMP. The MIB itself is structured like a tree,
`which the most general information available at the root of
`the tree, with more detailed information at each branch, and
`finally information about each network device is determined
`at a leaf or node of the MIB tree.
`0008. In particular, the use of the MIB enables the
`network operators to perform Such functions as configuring
`network devices, determining the State of network devices,
`collecting and reviewing performance Statistics of network
`devices, changing one or more important parameters,
`whether “on the fly” or on a non-realtime basis; and reboo
`ting a network device which is exhibiting Suspicious behav
`ior. Of course other such functions would also be possible if
`WAP gateways could be managed by using SNMP with an
`associated MIB. Unfortunately, no standard exists for
`enabling WAP gateways to be managed with an MIB
`through SNMP.
`
`Adobe - Exhibit 1024, page 3
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`0009. There is therefore a need for, and it would be useful
`to have, a System and a method for managing and controlling
`the operation of WAP gateways and other WAP network
`devices through SNMP, by providing an associated MIB for
`the WAP gateway, thereby enabling the WAP gateway to be
`maintained and operated through a set of Standard protocols
`which are shared by other types of network devices.
`
`SUMMARY OF THE INVENTION
`0.010 The present invention is of a system and method
`for managing a WAP gateway and optionally other WAP
`network devices through SNMP, by using a MIB. The MIB
`of the present invention contains a number of different
`details about the WAP gateway, as described in greater detail
`below, and enables various operational parameters of the
`WAP gateway to be monitored and controlled.
`0.011 The MIB according to the present invention is
`preferably based on the WAP standard 1.3 layered stack, and
`is based on features and/or elements which are required at
`that layer in the WAP standard. More preferably, the MIB is
`adjusted and/or altered as necessary in parallel to the WAP
`standard, so the MIB is able to provide management of the
`new features of the WAP standard.
`0012. According to the present invention, there is pro
`Vided a System for managing a WAP gateway device, the
`WAP gateway device being connected to a network, the
`System comprising: (a) a management process for managing
`the network, the management proceSS Sending commands to
`the WAP device according to SNMP; (b) an SNMP agent at
`the WAP gateway device for receiving the commands; and
`(c) a local MIB for containing a plurality of commands for
`the WAP gateway device, the local MIB being located at the
`WAP gateway device, such that the SNMP agent sends a
`response to the management process according to the local
`MIB.
`0013. According to another embodiment of the present
`invention, there is provided a method for managing a WAP
`device through SNMP, the method comprising the steps of:
`(a) providing a MIB for containing a plurality of commands
`for interacting with the WAP device, the MIB being installed
`at the WAP device; (b) sending at least one command to the
`WAP device; (c) receiving a response from the WAP device
`according to an entry in the MIB; and (d) managing the WAP
`device according to the response.
`0.014.
`Hereinafter, the term “wireless device” refers to
`any type of electronic device which permits data transmis
`Sion through a wireleSS channel, for example through trans
`mission of radio waves. Hereinafter, the term "cellular
`phone' is a wireleSS device designed for the transmission of
`Voice data and/or other data, optionally through a connection
`to the PSTN (public switched telephone network) system.
`0.015. Hereinafter, the term “network” refers to a connec
`tion between any two or more computational devices which
`permits the transmission of data.
`0016. Hereinafter, the term “computational device”
`includes, but is not limited to, personal computers (PC)
`
`having an operating system such as DOS, WindowsTM,
`OS/2TM or Linux; MacintoshTM computers; computers hav
`ing JAVATM-OS as the operating system; graphical work
`stations such as the computers of Sun Microsystems TM and
`Silicon Graphics TM, and other computers having some ver
`sion of the UNIX operating system such as AIXTM or
`SOLARISTM of Sun MicrosystemsTM; Palm OS(R); or any
`other known and available operating System, or any device,
`including but not limited to: laptops, hand-held computers,
`PDA (personal data assistant) devices, cellular telephones,
`any type of WAP (wireless application protocol) enabled
`device, wearable computers of any Sort, which can be
`connected to a network as previously defined and which has
`an operating system. Hereinafter, the term “WindowsTM'
`includes but is not limited to Windows95TM, Windows 3.XTM
`in which “X” is an integer such as “1”, Windows NTTM,
`Windows98TM, Windows CETM, Windows2000TM, and any
`upgraded versions of these operating Systems by MicroSoft
`Corp. (USA).
`0017 For the implementation of the present invention, a
`Software application could be written in Substantially any
`Suitable programming language, which could easily be
`Selected by one of ordinary skill in the art. The programming
`language chosen should be compatible with the computing
`platform according to which the Software application is
`executed. Examples of Suitable programming languages
`include, but are not limited to, C, C++ and Java.
`0018. In addition, the present invention could also be
`implemented as firmware or hardware. Hereinafter, the term
`“firmware” is defined as any combination of software and
`hardware, Such as Software instructions permanently burnt
`onto a ROM (read-only memory) device. As hardware, the
`present invention could be implemented as Substantially any
`type of chip or other electronic device capable of performing
`the functions described herein.
`0019. In any case, the present invention can be described
`as a plurality of instructions being executed by a data
`processor, in which the data processor is understood to be
`implemented according to whether the present invention is
`implemented as Software, hardware or firmware.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0020. The invention is herein described, by way of
`example only, with reference to the accompanying drawings,
`wherein:
`0021
`FIG. 1 is a schematic block diagram showing an
`exemplary System according to the present invention for
`managing a WAP gateway through SNMP.
`
`DESCRIPTION OF THE PREFERRED
`EMBODIMENTS
`0022. The present invention is of a system and method
`for managing a WAP (Wireless Application Protocol) gate
`way, and optionally other WAP-enabled network devices,
`through SNMP (Simple Network Management Protocol), by
`using a MIB (management information base). The MIB of
`
`Adobe - Exhibit 1024, page 4
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`the present invention contains a number of different details
`about the WAP gateway, as described in greater detail below,
`and enables various operational parameters of the WAP
`gateway to be monitored and controlled. The present inven
`tion is particularly Suitable for management and control of
`WAP network devices which act as translation gateways, for
`handling protocol translations between Internet protocols
`such as HTTP (HyperText Transfer Protocol) for example,
`and the corresponding WAP protocols such as WTP for
`example.
`0023 The MIB according to the present invention may
`optionally be used for any management purposes as for
`standard SNMP management of other network devices, such
`as routers for example. The MIB, which is used at the
`network device, is preferably implemented as an SNMP
`agent, which would more preferably be a component of the
`software for the WAP gateway (translation) device. Most
`preferably, the MIB would be provided in a standard Sup
`plied package as a plain text file. This text file must be
`compiled by any SNMP MIB compiler, after which it can be
`used as a management mechanism by using one of a number
`of commercial available MIB browsers. Examples of Such
`MIB browsers include, but are not limited to, Netview-6000
`(IBM Corp. USA), HP Open View (Hewlett-Packard Corp.,
`USA), and SNMPC (Castle Rock Corp., USA)
`0024. The MIB of the present invention may optionally
`be implemented for management purposes on any WAP
`network, and particularly for WAP gateway and/or WAP
`translation devices, although the particularly preferred
`implementation according to the present invention is for a
`WAP gateway device for translation between WAP-based
`protocols and Internet-based protocols.
`0.025 The MIB of the present invention is designed to be
`used in addition to the standard MIB-IL defined in RFC
`1213 K. McCloghrie, M. Rose, Management Information
`Base for Network Management of TCP/IP-based internets:
`MIB-II, March 1991). The standard MIB-II must be sup
`ported for all devices based on TCP/IP. Therefore, since
`WAP is based on the IP datagram service, each WAP
`gateway must Support the operation of the MIB-II, at least
`with regard to the main IP tables of this database, such as the
`tables for system parameters, interface table, ARP table, IP
`tables (for configuration and statistics), and UDP table.
`Thus, some of the parameters for the WAP gateway may be
`managed by this MIB-II, which is preferably recognized and
`used by the System and method of the present invention.
`Unfortunately, network devices, such as the WAP gateway
`(translation) and devices for providing access by mobile
`users to the Internet which are able to only use MIB-II have
`Some major disadvantages. For example, MIB-II cannot
`reflect the dynamic character of the System, in which active
`users enter and leave the system. Also, MIB-II is not
`configurable according to Specific WAP parameters. Further
`more, MIB-IL cannot show statistics related to such impor
`tant issueS as user authentication and accounting, the func
`tionality of the WAP gateway through any kind of proxy and
`so forth. Also, MIB-II does not provide statistics through a
`basic configuration on different aspects of Security issues.
`
`0026. One additional significant drawback of the ability
`to use only MIB-II functions is that these functions are
`provided only in order to be able to comply with the standard
`for IP datagrams. Therefore, current WAP implementations
`do not provide Sufficient Support for management of the
`WAP gateway through MIB-II, as the functionality which is
`Supported does not enable independent management of the
`gateway through SNMP.
`0027 Generally, the main WAP gateway functions can be
`defined as follows: WAP translation; WAP security; WAP
`rerouting; WAP user access over RADIUS protocol; and
`network characteristics and parameters. Of these functions,
`the last Set, network parameters and characteristics, may
`optionally be managed by standard MIB-II.
`0028. In order to provide extended functionality and
`greater control over the management of the WAP gateway
`and the functions thereof, the MIB of the present invention
`has additional components and therefore more comprehen
`Sive management functions. The proposed MIB configura
`tion according to the present invention features the follow
`ing components: WAP configuration; WAP statistics; WAP
`Security configuration; and WAP Security Statistics.
`0029. Since any SNMP MIB is built as a tree, and all
`definitions of the current invention are preferably con
`structed as a full sub-tree of the MIB, the point (node tree)
`at which the sub-tree of the present invention is to be
`connected to the existing MIB should therefore also prefer
`ably be defined. More preferably, this point is chosen to be
`the node “wapForum', which is defined as “enter
`prises. 7777", where instead of “7777", a WAP Forum num
`ber from IANA (Internet Assigned Numbers Authority inter
`national organization) must be so defined and ordered. The
`“enterprises' node is defined in standard MIB-II on ASN-1
`Standard transcription as:
`0030)
`iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).
`Of course, another insertion point to the standard MIB-II
`could alternatively be Selected.
`0031. The principles and operation of a method and a
`System according to the present invention may be better
`understood with reference to the drawings and the accom
`panying description.
`0032 Referring now to the drawings, FIG. 1 shows an
`exemplary implementation of a System 10 according to the
`present invention for managing a WAP gateway through
`SNMP System 10 features a WAP device 12, for which a
`non-limiting example is a WAP gateway, more preferably a
`WAP gateway device for translation, although of course any
`other WAP gateway device could be substituted for WAP
`device 12. WAP device 12 operates an SNMP agent 14 based
`on the standard TCP/IP stack in part of UDP, which may
`optionally be implemented as a Software component,
`although of course other implementations are possible under
`the present invention. SNMP agent 14 has an associated
`local MIB 16, which is optionally and more preferably
`provided as a plaintext file. Local MIB 16, along with SNMP
`
`Adobe - Exhibit 1024, page 5
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`agent 14, are provided through the present invention. These
`two components enable the following functions of WAP
`gateway device 12 to be managed as a network device: WAP
`configuration; WAP statistics; WAP security configuration;
`user functions; and WAP security statistics.
`0033. The functions of WAP device 12 are determined
`according to the components of the WAP architecture, which
`is described in “Wireless Application Protocol Architecture
`Specification” (version of Apr. 30, 1998; incorporated herein
`by reference, available at http://www.wapforum.org). Cer
`tain features of this architecture are described with regard to
`the functions of local MIB 16 according to the present
`invention, for demonstrating Some of the new features of
`local MIB 16 which clearly differentiate the MIB according
`to the present invention from currently available background
`art MIB's. An example of the MIB itself is given in the
`Appendix, at the end of the Specification.
`0034) The seven layers of the WAP architecture include
`the lowest level layer, the transport layer (WDP, Wireless
`Datagram Protocol), which operates above the data transport
`services provided by the network. It is equivalent to UDP
`(User Datagram Protocol) for the Internet protocols. Local
`MIB 16 contains definitions and information related to UDP
`and to equivalent connections which are to be made at this
`level to WAP device 12. For example, the command:
`0035) wfConnType OBJECT TYPE
`0036 SYNTAX WFConnType
`0037 ACCESS read-only
`0038 STATUS mandatory
`0039) DESCRIPTION
`0040 “Type of the existing connection: con
`nection oriented (TCP)-WAP,
`0041 or connection-less (UDP)-transparent, or
`undefined.”
`0042 ::={wfConnectionEntry 1}
`gives information related to the type of the existing
`0.043
`connection to WAP device 12. For example, such a connec
`tion could optionally be made by an additional network
`device (not shown).
`0044 Above this lowest layer is the security layer
`(WTLS, Wireless Transport Layer Security), which is a
`Security protocol based on the Standard Transport Layer
`Security (TLS) protocol. Local MIB 16 contains definitions
`and information related to security of WAP device 12, as
`previously mentioned, and can also optionally and prefer
`ably be used for management of Security functions. For
`example, the human network operator could Select a par
`ticular security Scheme, according to which WAP device 12
`is permitted to communicate with other network devices (not
`shown). Such a security scheme would then be stored in
`local MIB 16. The information related to this scheme would
`be retrieved during a handshake procedure between WAP
`device 12 and another network device, Such as a client
`
`WAP-enabled cellular telephone (not shown). WAP device
`12 would then preferably inform the other network device of
`the predetermined Scheme during the handshake procedure,
`Such that communication between WAP device 12 and the
`other network device would preferably be performed
`according to the predetermined Security Scheme as Stored in
`local MIB 16.
`0045. As a specific example of a security-related instruc
`tion, the command:
`0046) wfSecurity WilsEnable OBJECT TYPE
`0047 SYNTAX EnableDisableType
`0048 ACCESS read-write
`0049 STATUS mandatory
`0050. DESCRIPTION
`0051) “Enable Wireless Transport Layer
`Security (WTLS)
`0052
`connections in WAP translation unit.”
`0053) DEFVAL (disable
`0054) ::={wfWilsconfig 1}
`0055 determines whether connections according to a
`particular secure protocol should be permitted for WAP
`device 12.
`0056. The above examples concern different illustrative
`functions of local MIB 16 with regard to exemplary WAP
`related features and functions, as previously described. In
`addition, local MIB 16 also contains commands and infor
`mation related to users. One example of Such a command is
`as follows:
`0057 wifActiveUsersNumber OBJECT TYPE
`0.058 SYNTAX Counter
`0059 ACCESS read-only
`0060 STATUS mandatory
`0061 DESCRIPTION
`0062) “Number of currently active users.”
`0063) ::={wfStatCommon User 5}
`0064 which, as shown above, gives the number of cur
`rently active users for WAP device 12.
`0065 Optionally, if the client WAP-enabled cellular tele
`phone has a particular limitation or other characteristic,
`WAP device 12 can retrieve one or more instructions for
`handling Such a limitation and/or other characteristic from
`local MIB 16, Such that the interaction between WAP device
`12 and the client WAP-enabled cellular telephone and/or
`other network device can preferably be optimized according
`to information stored in local MIB 16. This preferred
`embodiment has the advantage of enabling different types
`and/or brands of client WAP-enabled cellular telephones to
`be correctly handled by WAP device 12 according to the
`specific instructions of local MIB 16. Such a requirement for
`
`Adobe - Exhibit 1024, page 6
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`handling these different types of network devices further
`differentiates local MIB 16 from background art MIB imple
`mentations, which are not required to handle Such different
`types of WAP-enabled devices.
`0.066
`Additional detailed examples of specific features of
`local MIB 16 are provided below.
`0067. WAP device 12 is in communication with a man
`agement process 18 through a network 20. Typically, man
`agement proceSS 18 is operated by a central Server 22,
`through which management Services are provided to a
`plurality of WAP devices 12 (not shown). Management
`process 18 more preferably controls a set of MIB’s, prefer
`ably including central MIB 24 according to the background
`art. Management process 18 also preferably supports a MIB
`browser 26, according to the background art, for enabling a
`human network operator to manage System 10 including
`WAP device 12.
`0068 For example, management process 18 is able to
`send the “GET' command to WAP device 12, and more
`specifically to SNMP agent 14, in order to retrieve infor
`mation about the operation of WAP device 12. The response
`of SNMP agent 14 is determined according to local MIB 16.
`The portion of local MIB 16 which is particularly relevant
`to the present invention is preferably contained in a Sub-tree
`of the standard MIB, specified for WAP devices and in
`particular for WAP gateway (translation) devices.
`0069. Examples of the commands available through local
`MIB 16 include commands for determining which version of
`WAP is being supported by local MIB 16, as follows:
`0070) wfSupported Version OBJECT TYPE
`0071 SYNTAX WapSupported Version
`0072 ACCESS read-only
`0073 STATUS mandatory
`0074) DESCRIPTION
`0075) “The WAP version supported in trans
`lation.
`0076 Now WAP translation may be done for
`WAP version 1.1.
`0077. The WAP translation unit supports
`translation for
`0078 WAP version 1.1”
`0079) ::={wfConfigCommon 1}
`
`0080 A general command, which is useful for determin
`ing the size of the buffer provided for WAP devices, par
`ticularly for translation devices, is given as follows:
`0081 wifBufferTranslateSize OBJECT TYPE
`I0082) SYNTAX INTEGER (4096.65535)
`0083) ACCESS read-write
`0084 STATUS mandatory
`0085) DESCRIPTION
`0086) “Size of buffer that used for WAP
`translation.
`0087 Must be large enough to contain as
`WAP packet of maximum size as HTTP
`packet of maximum size.
`0088 Currently must be larger than 4096
`and less than 65536 bytes.
`0089. Have to be set in compliance with
`System memory requirements.”
`::={wfConfigCommon 4
`0090)
`0091. A more specific command, which is useful for
`determining the WAP homepage for a particular brand of
`cellular telephone (which could not otherwise have Such a
`determined homepage), is given as follows:
`0092 wif|DefaultHomepage OBJECT TYPE
`0093 SYNTAX DisplayString (SIZE (1.255))
`0094 ACCESS read-write
`0.095 STATUS mandatory
`0096 DESCRIPTION
`0097) “Limitations of the Motorola WAP
`phone do not allow Setting of a default home
`page, therefore this parameter allows you to
`set the Motorola Timeport homepage URL.”
`::={wfConfigCommon 2}
`0098)
`0099 Thus, clearly these different commands and types
`of information from local MIB 16 enable the human network
`operator to manage and control the behavior of WAP device
`12, and through WAP device 12, to manage the overall
`behavior of network 20.
`0100. It will be appreciated that the above descriptions
`are intended only to Serve as examples, and that many other
`embodiments are possible within the Spirit and the Scope of
`the present invention.
`
`Adobe - Exhibit 1024, page 7
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`APPENDIX
`
`Full Version of Exemplary MIB
`
`WapForum-MIB
`
`WAP Forum
`SNMP MTBs for Wireless Application Protocol support
`-- Rev: 1.0
`-- Date: 29/10/2000
`-- FileName: WapForum.mib
`
`-- General Model
`
`-- All WAP Forum private MIB extensions will be contained in a sub-tree of
`-- the mib under:
`
`-- iso(1).org(3).dod(6).internet(1).private(4).enterprises(1). WapForum (7777)
`
`- FORMAT of DEFINITIONS
`
`-- The following sections contain the specification of all object types
`-- contain The object types are defined using the conventions defined in
`-- the SMI (RFC 1156) as amended by the extensions specified in "Towards
`-- Concise MIB Definitions".
`
`DEFINITIONS ::= BEGIN
`
`IMPORTS
`Counter, enterprises, TimeTicks, IpAddress
`DisplayString, PhysAddress
`OBJECT-TYPE
`TRAP-TYPE
`MODULE-IDENTITY, Integer32
`ROWStatus, InstancePointer
`
`FROM RFC 1155-SM
`FROMRFC 1213-MB
`FROM RFC-1212
`FROM RFC 215
`FROM SNMPv2-SMI
`FROM SNMPV2-TC
`
`YesNoType ::=
`INTEGER {
`yes(1),
`no(2)
`
`Adobe - Exhibit 1024, page 8
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`TrueFalseType ::=
`INTEGER {
`true(1),
`false(2)
`
`EnableDisableType ::=
`INTEGER {
`enable(1),
`disable(2)
`
`}
`
`WFConnType ::=
`INTEGER {
`Wap(2),
`transparent(3)
`
`}
`WFProtocolType ::=
`INTEGER {
`top (6),
`udp (17)
`
`}
`
`WapSupported Version ::=
`INTEGER {
`ver11 (11),
`ver12(12),
`ver13 (13),
`ver14(14),
`ver15(15),
`ver20020),
`ver21 (21),
`ver22(22),
`ver23(23),
`ver24(24)
`
`AuthentHeaderEncoding ::=
`INTEGER {
`ip(1),
`msisdn(2),
`original(3),
`xidEncoding(4)
`
`}
`
`wapForum
`OBJECT IDENTIFIER::= { enterprises 7777 }
`wapForumMib MODULE-IDENTITY
`
`Adobe - Exhibit 1024, page 9
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`LAST-UPDATED "OO291O1456Z"
`ORGANIZATION "WAP Forum"
`CONTACT-INFO "Haim Rochberger Gicom verse.com
`Alexander OrGicom verse.com"
`DESCRIPTION
`"This is private WAP Forum mib containing definition
`for WAP configuration and performance measurement."
`::= { wapForum 1 }
`wfWap
`OBJECT IDENTIFIER::= { wifSubsystems 1 }
`wfSecurity
`OBJECT IDENTIFIER::= { wfSubsystems 2 }
`wfWapConfig
`OBJECT IDENTIFIER::= { wfWap 1 }
`wfWapStatistic
`OBJECTIDENTIFIER::= { wfWap 2 }
`wfConfigCommon
`OBJECTIDENTIFIER::= { wfWapConfig 1 }
`wfConfigVerlx
`OBJECT IDENTIFIER::= { wif WapConfig 2 }
`wfConfigDnsCache
`OBJECT IDENTIFIER::= { wifWapConfig 3 }
`wfConfigWebCache
`OBJECTIDENTIFIER::= { wif WapConfig 4}
`wfStatCommonser
`OBJECTIDENTIFIER::= { wif WapStatistic 1 }
`wfConnections
`OBJECT IDENTIFIER::= { w fWapStatistic 2 }
`wfActiveUsers
`OBJECTIDENTIFIER::= { wfWapStatistic 3 }
`wfStatPacket
`OBJECTIDENTIFIER::= { wfWapStatistic 4}
`wfStatWsp2Http
`OBJECT IDENTIFIER::= { wfWapStatistic 5 }
`wfStatHttp
`OBJECTIDENTIFIER::= { wfWapStatistic 6 }
`wfStatWmITransl2Wmlc OBJECT IDENTIFIER::= { wfWapStatistic 7 }
`wfStatSecurity
`OBJECTIDENTIFIER::= { wfWapStatistic 8 }
`wfStatDnsCache
`OBJECT DENTIFIER::= { wif WapStatistic 9 }
`wfStatWebCache
`OBJECTIDENTIFIER::= { wif WapStatistic 10 }
`wfSslConfig
`OBJECTIDENTIFIER::= { wifSecurity 1 }
`wfSSIStatistic
`OBJECT IDENTIFIER::= { wifSecurity 2 }
`wfWtlsConfig
`OBJECT IDENTIFIER::= { wifSecurity 3 }
`wfWtsStatistic
`OBJECT IDENTIFIER::= { wfSecurity 4 }
`
`-- Configuration
`-- WAP configuration
`-- WAP Common configuration
`wfSupported Version OBJECT TYPE
`SYNTAX WapSupported Version
`ACCESS read-only
`STATUS mandatory
`DESCRIPTION
`"The WAP version supported in translation.
`Now WAP translation may be done for WAP version 1.1.
`The WAP translation unit supports translation for
`WAP version 1.1"
`::= { wfconfigCommon 1 }
`
`wfDefaultHomepage OBJECT-TYPE
`SYNTAX DisplayString (SIZE (1.255))
`ACCESS read-write
`STATUS mandatory
`DESCRIPTION
`
`Adobe - Exhibit 1024, page 10
`
`

`

`US 2002/OO67742 A1
`
`Jun. 6, 2002
`
`"Limitations of the Motorola WAP phone do not allow setting of a default
`homepage, therefore this parameter allows you to set the Motorola Timeport
`homepage URL."
`::= { wfConfigCommon 2)
`
`wfHttpAuthentHeaderEncoding OBJECT-TYPE
`SYNTAX AuthentHeaderEncoding
`ACCE