(12) Ulllted States Patent
`Provino
`
`(10) Patent N0.:
`(45) Date of Patent:
`
`US 6,557,037 B1
`*Apr. 29, 2003
`
`USOO6557037B1
`
`(54) SYSTEM AND METHOD FOR EASING
`COMMUNICATIONS BETWEEN DEVICES
`CONNECTED RESPECTIVELY TO PUBLIC
`NETWORKS SUCH AS THE INTERNET AND
`T0 PRIVATE NETWORKS BY
`
`FOREIGN PATENT DOCUMENTS
`
`EP
`EP
`
`0 825 784 A2
`0 887 979 A2
`
`7/1997
`6/1998
`
`FACILITATING RESOLUTION OF HUMAN-
`READABLE ADDRESSES
`
`s cited by examine,
`
`(75)
`
`Inventor:
`
`Joseph E. Provino, Cambridge, MA
`(”5)
`
`(73) Assignee: Sun Microsystems, Palo Alto, CA (US)
`
`Primary Examiner—Dung C. Dinh
`Assistant Examiner—Abdullahi E. Salad
`(74) Attorney, Agent, or Firm—McCormick, Paulding &
`Huber LLP
`
`(57)
`
`ABSTRACT
`
`“
`
`.
`.
`.
`.
`A system [comprises] Includes a Virtual pnvate network
`and an external device interconnected by a digital network.
`The virtual private network has a firewall, at
`least one
`
`internal device and a nameserver each having a network
`address. The internal device also has a secondary address,
`and the nameserver is configured to provide an association
`between the secondary address and the network address. The
`firewall, in response to a request from the external device to
`establish a connection therebetween, provides the external
`
`device with the network address of the nameserver. The
`external device, in response to a request from an operator or
`the like, including the internal deviwys secondary address,
`requesting access to the internal device, generates a network
`address request message for transmission over the connec-
`tion to the firewall requesting resolution of the network
`address associated with the secondary address. The firewall
`provides the address resolution request to the nameserver,
`and the nameserver provides the network address associated
`with the secondary address to the firewall. The firewall, in
`turn, provides the network address in a network address
`response message for transmission over the connection to
`the external device. The external device can thereafter use
`the network address so provided in subsequent communi-
`-
`~
`~
`~
`.
`)3
`cations w1th the firewall Intended for the mtemal dev1ce.
`
`18 Claims, 1 Drawing Sheet
`
`(*) Notice:
`
`This patent issued on a continued pros-
`ecution application filed under 37 CFR
`1.53 d , and is sub'ect to the twent
`ear
`patefit) term provisions of 35 1);...SC
`154000).
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`11.5.0 154(1)) by 0 days,
`
`(21) Appl. N0.: 09/087,823
`
`(22)
`
`Filed:
`
`May 29, 1993
`
`7
`
`................................................ G06F 15/16
`Int. Cl.
`(51)
`(52) U-S- 0- ---------------------- 709/227; 7034222455709/228;
`7
`/
`’ 713/201
`(58) Field of Search ................................. 709/227, 228,
`709/250’ 245’ 225; 713/201
`
`(56)
`
`References Cited
`
`US- PATENT DOCUMENTS
`5
`5,805,803 A
`9/1998 Birrell a a].
`395/1870]
`5,826,029 A
`10/1998 Gore, Jr. et a].
`395/200.57
`2,322,333 2 :
`4/1399 WSSiiiger, JR let 31-
`-- 3957/33/73:
`.
`,
`,
`11/1 99 A I'a am eta.
`6,003,084 A * 12/1999 Green a a].
`709/227
`
`6,006,268 A * 12/1999 Colic et al.
`709/227
`
`6,119,234 A *
`9/2000 Aziz et al.
`713/201
`
`*,
`
`
`{{EWCE t2")
`DEVICE 120")
`TGIFROM
`ACCESSED
`
`
`DEVICES
`
`
`
`ACOESSED
`
` DEVICES
`
`
`
`Petitioner Apple Inc. - Ex. 1024, p. l
`
`Petitioner Apple Inc. - Ex. 1024, p. 1
`
`

`

`US. Patent
`
`Apr. 29, 2003
`
`US 6,557,037 B1
`
`-.
`
`IIIIIIIIIIIIIIIIL
`
`mz<z
`
`CE352
`
`
`
`mh<>_mm
`
`NGNR
`
`.F
`
`a.
`
`29E?
`
`E15
`
`mam;
`
` _8389.—E_zomkoh_I__8_4.2;"6v5mm>mmmk-mmm.Wmw.»-
`
` uuuuuuuuuuuuuuuu.2xmozfimz_.2355"ummm>mmw_m=2<zza>"mmosmo
`.l_8u8uI_‘_3|uE_mmoSmo_8332
`almtmmE1.qu
`(:5mm>mmw"zoEEF
`soak?_Etmm>mmm
`Vim-Ahmzmmhz
`
`5:5
`
`mam.
`
`VII-A
`
`:.
`
`.mJ3EnmmoSoE
`
`moSmwm
`
`..|
`
`Ea85%
`
`Eamosmo
`
`
`
`25$mosmm.
`
`Petitioner Apple Inc. - EX. 1024, p. 2
`
`Petitioner Apple Inc. - Ex. 1024, p. 2
`
`
`
`

`

`US 6,557,037 B1
`
`1
`SYSTEM AND METHOD FOR EASING
`COMMUNICATIONS BETWEEN DEVICES
`CONNECTED RESPECTIVELY TO PUBLIC
`NETWORKS SUCH AS THE INTERNET AND
`TO PRIVATE NETWORKS BY
`FACILITATING RESOLUTION OF HUMAN-
`READABLE ADDRESSES
`
`FIELD OF THE INVENTION
`
`The invention relates generally to the field of digital
`communications systems and methods, and more particu-
`larly to systems and methods for easing communications
`between devices connected to public networks such as the
`Internet and devices connected to private networks.
`BACKGROUND OF THE INVENTION
`
`Digital networks have been developed to facilitate the
`transfer of information, including data and programs, among
`digital computer systems and other digital devices. Avariety
`of types of networks have been developed and implemented,
`including so—called “wide-area networks” (WAN’S) and
`“local area networks” (LAN’s), which transfer information
`using diverse information transfer methodologies.
`Generally, LAN’s are implemented over relatively small
`geographical areas, such as within an individual office
`facility or the like, for transferring information within a
`particular office, company or similar type of organization.
`On the other hand, WAN’s are generally implemented over
`relatively large geographical areas, and may be used to
`transfer information between LAN’s as well as between
`devices that are not connected to LAN’s. WAN’s also
`include public networks, such as the Internet, which can
`carry information for a number of companies.
`Several problems have arisen in connection with commu~
`nication over a network, particularly a large public WAN
`such as the Internet. Generally, information is transferred
`over a network in message packets, which are transferred
`from one device, as a source device, to another device as a
`destination device, through one or more routers or switching
`nodes (generally, switching nodes) in the network. Each
`message packet includes a destination address which the
`switching nodes use to route the respective message packet
`to the appropriate destination device. Addresses over the
`Internet are in the form of an “n”-bit integer (where “It” may
`be thirty two or 128), which are diflicult for a person to
`remember and enter when he or she wishes to enable a
`message packet to be transmitted. To relieve a user of the
`necessity of remembering and entering specific integer Inter—
`net addresses,
`the Internet provides second addressing
`mechanism which is more easily utilized by human opera-
`tors of the respective devices. In that addressng mechanism,
`Internet domains, such as LAN’5, Internet service providers
`(“ISP’s”) and the like which are connected in the Internet,
`are identified by relatively human-readable names. To
`accommodate the use of human-readable names,
`nameservers, also referred to as DNS servers, are provided
`to resolve the human—readable names to the appropriate
`Internet addresses. When an operator at one device, wishing
`to transmit a message packet to another device, enters the
`other device’s human-readable name, the device will ini-
`tially contact a nameserver. Generally, the nameserver may
`be part of the ISP itself or it may be a particular device which
`is accessible through the ISP over the Internet; in any case,
`the ISP will identify the nameserver to be used to the device
`when the device logs in to the ISP. If, after being contacted
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`by the device, the nameserver has or can obtain an integer
`Internet address for the human-readable domain name, it
`(that is, the nameserver) will provide the integer Internet
`address corresponding to the human—readable domain name
`to the operator’s device. The device, in turn, can thereafter
`include the integer Internet address returned by the
`nameserver in the message packet and provide the message
`packet to the ISP for transmission over the Internet in a
`conventional manner. The Internet switching nodes use the
`integer Internet address to route the message packet to the
`intended destination device.
`Other problems arise, in particular, in connection with the
`transfer of information over a public WAN such as the
`Internet. One problem is to ensure that information trans-
`ferred over the WAN that the source device and the desti-
`nation device wish to maintain confidential, in fact, remains
`confidential as against possible eavesdroppers which may
`intercept the information. To maintain confidentiality, vari-
`ous forms of encryption have been developed and are used
`to encrypt the information prior to transfer by the source
`device, and to decrypt
`the information after it has been
`received by the destination device. If it is desired that, for
`example, all information transferred between a particular
`source device and a particular destination device is main-
`tained confidential,
`the devices can establish a “secure
`tunnel” therebetween, which essentially ensures that all
`information to be transferred by the source device to the
`destination device is encrypted (except for certain protocol
`information, such as address information, which controls the
`flow of network packets through the network between the
`source and destination devices) prior to transfer, and that the
`encrypted information will be decrypted prior to utilization
`by the destination device. The source and destination
`devices may themselves perform the encryption and
`decryption, respectively, or the encryption and decryption
`may be performed by other devices prior to the message
`packets being transferred over the lutemet.
`A further problem that arises in particular in connection
`with companies, government agencies, and private organi—
`zations whose private networks, which may be LAN ’s,
`WAN’s or any combination thereof, are connected to public
`WAN’s such as the Internet, is to ensure that their private
`networks are secure against others whom the companies do
`not wish to have access thereto, or to regulate and control
`access by others whom the respective organizations may
`wish to have limited access. To accommodate that,
`the
`organizations typically connect their private networks to the
`public WAN’5 through a limited number of gateways some-
`times referred to as “firewalls,” through which all network
`traffic between the internal and public networks pass.
`Typically, network addresses of domains and devices in the
`private network “behind” the firewall are known to
`nameservers which are provided in the private network, but
`are not available to nameservers or other devices outside of
`the private network, making communication between a
`device outside of the private network and a device inside of
`the private network diflicult.
`SUMMARY OF THE INVENTION
`
`The invention provides a new and improved system and
`method for easing communications between devices con-
`nected to public networks such as the lntemet and devices
`connected to private networks by facilitating resolution of
`secondary addresses, such as the Internet’s human-readable
`addresses, to network addresses by nameservers or the like
`connected to the private networks.
`In brief summary, the invention provides a system com-
`prising a virtual private network and an external device
`
`Petitioner Apple Inc. - EX. 1024, p. 3
`
`Petitioner Apple Inc. - Ex. 1024, p. 3
`
`

`

`US 6,557,037 B1
`
`3
`interconnected by a digital network. The virtual private
`network has a firewall, at least one internal device and a
`nameserver each having a network address. The internal
`device also has a secondary address, and the nameserver is
`configured to provide an association between the secondary
`address and the network address. The firewall, in response to
`a request from the external device to establish a connection
`therebetween, provides the external device with the network
`address of the nameserver. The external device, in response
`to a request from an operator or the like, including the
`internal device’s secondary address, requesting access to the
`internal device, generates a network address request mes-
`sage for transmission over the connection to the firewall
`requesting resolution of the network address associated with
`the secondary address. The firewall provides the address
`resolution request to the nameserver, and the nameserver
`provides the network address associated with the secondary
`address to the firewall. The firewall, in turn, provides the
`network address in a network address response message for
`transmission over the connection to the external device. The
`external device can thereafter use the network address so
`provided in subsequent communications with the firewall
`intended for the internal device.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`This invention is pointed out with particularity in the
`appended claims. The above and further advantages of this
`invention may be better understood by referring to the
`following description taken in conjunction with the accom—
`panying drawing, in which:
`FIG. 1 is a functional block diagram of a network con-
`structed in accordance with the invention.
`
`DETAILED DESCRIPTION OF AN
`ILLUSTRATIVE EMBODIMENT
`
`FIG. 1 is a functional block diagram of a network 10
`constructed in accordance with the invention. The network
`10 as depicted in FIG. 1 includes an Internet service provider
`(“ISP”) 11 which facilitates the transfer of message packets
`among one or more devices 12(1) through 12(M) (generally
`identified by reference numeral 12(m)) connected to ISP 11,
`and other devices, generally identified by reference numeral
`13, over the Internet 14, thereby to facilitate the transfer of
`information in message packets among the devices 12(m)
`and 13. The ISP 11 connects to the Internet 14 over one or
`more logical connections or gateways or the like (generally
`referred to herein as “connections”) generally identified by
`reference numeral 41. The ISP 11 may be a public ISP, in
`which case it connects to devices 12(m) which may be
`controlled by operators who are members of the general
`public to provide access by those operators to the Internet.
`Alternatively, ISP 11 may be a private ISP, in which case the
`devices 12(m) connected thereto are generally operated by,
`for example, employees of a particular company or govem-
`mental agency, members of a private organization or the
`like, to provide access by those employees or members to
`the Internet.
`
`the Internet comprises a mesh of
`As is conventional,
`switching nodes (not separately shown) which interconnect
`ISP’s 11 and devices 13 to facilitate the transfer of message
`packets thereamong. The message packets transferred over
`the Internet 14 conform to that defined by the so-called
`Internet protocol “IP” and include a header portion, a data
`portion, and may include a error detection and/or correction
`portion. The header portion includes information used to
`transfer the message packet
`through the Internet 14,
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`45
`
`50
`
`55
`
`60
`
`6S
`
`4
`including, for example, a destination address that identifies
`the device that is to receive the message packet as the
`destination device and a source address that identifies the
`device which generated the message packet. For each mes-
`sage packet, the destination and source addresses are each in
`the form of an integer that uniquely identifies the respective
`destination and source devices. The switching nodes com-
`prising the Internet 14 use at least the destination address of
`each respective message packet
`to route it (that
`is,
`the
`respective message packet) to the destination device, if the
`destination device is connected to the Internet, or to an ISP
`11 or other device connected to the Internet 14, which, in
`turn, will forward the message packet to the appropriate
`destination. The data portion of each message packet
`includes the data to be transferred in the message packet, and
`the error detection and/or correction portion contains error
`detection and/or correction information which may be used
`to verify that the message packet was correctly transferred
`from the source to the destination device (in the case of error
`detection information), and correct selected types of errors
`if the message packet was not correctly transferred (in the
`case of error correction information).
`The devices 12(m) connected to ISP 11 may comprise any
`of a number of types of devices which communicate over the
`Internet 14,
`including, for example, personal computers,
`computer workstations, and the like, with other devices 13.
`Each device 12(m) communicates with the ISP 11 to transfer
`message packets thereto for transfer over the Internet 14, or
`to receive message packets therefrom received by the ISP 11
`over the Internet 14, using any convenient protocol such as
`the well—known point-to-point protocol (“PPP”) if the device
`12(m) is connected to the ISP 11 using a point-to-point link,
`any conventional multi-drop network protocol if the device
`12(m) is connected to the ISP 11 over a multi-drop network
`such as the Ethernet, or the like. The devices 12(m) are
`generally constructed according to the conventional stored-
`program computer architecture, including, for example, a
`system unit, a video display unit and operator input devices
`such as a keyboard and mouse. A system unit generally
`includes processing, memory, mass storage devices such as
`disk and/or tape storage elements and other elements (not
`separately shown),
`including network and/or telephony
`interface devices for interfacing the respective device to the
`ISP 11. The processing devices process programs, including
`application programs, under control of an operating system,
`to generate processed data. The video display unit permits
`the device to display processed data and processing status to
`the user, and the operator input device enables the user to
`input data and control processing.
`These elements of device 12(m), along with suitable
`programming, cooperate to provide device 12(m) with a
`number of functional elements including, for example, an
`operator interface 20, a network interface 21, a message
`packet generator 22, a message packet receiver and proces-
`sor 23, an ISP log-on control 24, an Internet parameter store
`25 and, in connection with the invention, a secure message
`packet processor 26. The operator interface 20 facilitates
`reception by the device 12(m) of input information from the
`operator input device(s) of device 12(m) and the display of
`output
`information to the operator on the video display
`device(s) of the device 12(m). The network interface 21
`facilitates connection of the device 12(m) to the ISP 11 using
`the appropriate PPP or network protocol, to transmit mes-
`sage packets to the ISP 11 and receive message packets
`therefrom. The network interface 21 may facilitate connec-
`tion to the ISP 11 over the public telephone network to allow
`for dial—up networking of the device 12(m) over the public
`
`Petitioner Apple Inc. - EX. 1024, p. 4
`
`Petitioner Apple Inc. - Ex. 1024, p. 4
`
`

`

`US 6,557,037 B1
`
`5
`telephone system. Alternatively or in addition, the network
`interface 21 may facilitate connection through the ISP 11
`over, for example, a conventional LAN such as the Ethernet.
`The ISP log on control 24, in response to input provided by
`the operator interface 20 and/or in response to requests from
`programs (not shown) being processed by the device 12(m),
`communicates through the network interface 21 to facilitate
`the initialization (“log-on”) of a communications session
`between the device 12(m) and the ISP 11, during which
`communications session the device 12(m) will be able to
`transfer information, in the form of, message packets with
`other devices over the Internet 14, as well as other devices
`12(m') (m'~m) connected to the ISP 11 or to other ISP’s.
`During a log-on operation,
`the ISP log—on control 24
`receives the Internet protocol (“IP”) parameters which will
`be used in connection with message packet generation
`during the communications session.
`During a communications session, the message packet
`generator 22, in response to input provided by the operator
`through the operator interface 20, and/or in response to
`requests from programs (not separately shown) being pro-
`cessed by the device 12(m), generates message packets for
`transmission through the network interface 21. The network
`interface 21 also receives message packets from the ISP 11
`and provides them to message packet receiver and processor
`23 for processing and provision to the operator interface 20
`and/or other programs (not shown) being processed by the
`device 12(m),
`If the received message packets contain
`information, such as Web pages or the like, which is to be
`displayed to the operator, the information can be provided to
`the operator interface 20 to enable the information to be
`displayed on the device’s video display unit. In addition or
`alternatively,
`the information may be provided to other
`programs (not shown) being processed by the device 12(m)
`for processing.
`Generally, elements such as the operator interface 20,
`message packet generator 22, message packet receiver and
`processor 23, ISP log—on control 24 and Internet parameter
`store 25 may comprise elements of a conventional Internet
`browser, such as Mosaic, Netscape Navigator and Microsoft
`Internet Explorer.
`In connection with the invention, as noted above the
`device 12(m) also includes a secure message packet proces-
`sor 26. The secure message packet processor 26 facilitates
`the establishment and use of a “secure tunnel,” which will be
`described below, between the device 12(m) and another
`device 12 (m’) (m'~m) or 13. Generally, in a secure tunnel,
`information in at least the data portion of message packets
`transferred between device 12(m) and a specific other device
`12(m') (m'~m) or 13 is maintained in secret by, for example,
`encrypting the data portion prior to transmission by the
`source device. Information in other portions of such mes-
`sage packets may also be maintained in secret, except for the
`information that is required to facilitate the transfer of the
`respective message packet between the devices, including,
`for example, at least the destination information, so as to
`allow the lnternet’s switching nodes and ISP’s to identify
`the device that is to receive the message packet.
`In addition to ISP 11, a number of other ISP’s may
`connect to the Internet, as represented by arrows 16, facili-
`tating communications between devices which are con-
`nected to those other ISP’s with other devices over the
`Internet, which may include the devices 12(n) connected to
`ISP 11.
`
`The devices 13 which devices 12(m) access and commu-
`nicate with may also be any of a number of types of devices,
`
`6
`including personal computers, computer workstations, and
`the like, and also including mini-and mainframe computers,
`mass storage systems, compute servers, local area networks
`(“LAN’s”) and wide area networks (“WAN’S”) including
`such devices and numerous other types of devices which
`may be connected directly or indirectly to the networks. In
`connection with the invention, at least one of the devices
`will include at least one private network, identified as virtual
`private network 15, which may be in the form of a LAN or
`WAN. The virtual private network 15 may comprise any of
`the devices 12(m') (m’~m) (thereby connecting to the Inter-
`net 14 through an ISP) or 13 (thereby connecting directly to
`the Internet 14);
`in the illustrative embodiment described
`herein, the virtual private network 15 will be assumed to
`comprise a device 13. The virtual private network 15 itself
`includes a plurality of devices, identified herein as a firewall
`30, a plurality of servers 31(1) through 31(5) (generally
`identified by reference numeral 31(5)) and a nameserver 32,
`all interconnected by a communication link 33. The firewall
`30 and servers 31(5) maybe similar to any of the various
`types of devices 12(m) and 13 described herein, and thus
`may include, for example, personal computers, computer
`workstations, and the like, and also including mini-and
`mainframe computers, mass storage systems, compute
`servers, local area networks (“LAN’s”) and wide area net-
`works (“WAN’s”) including such devices and numerous
`other types of devices which may be connected directly or
`indirectly to the networks.
`As noted above, the devices, including devices 12(m) and
`devices 13, communicate by transferring message packets
`over the Internet. The devices 12(m) and 13 can transfer
`information in a “peer-to-peer" manner, in a “client-server”
`manner, or both. Generally,
`in a “peer-to-peer" message
`packet transfer, a device merely transfers information in one
`or more message packets to another device. On the other
`hand, in a “client-server” manner, a device, operating as a
`client, can transfer a message packet to another device,
`operating as a server to for example, initiate service by the
`other device. A number of types of such services will be
`appreciated by those skilled in the art,
`including,
`for
`example, the retrieval of information from the other device,
`to enable the other device to perform processing operations,
`and the like. If the server is to provide information to the
`client, it (that is, the server) may generally be referred to as
`a storage server. On the other hand, if the server is to perform
`processing operations at the request of the client, it (that is,
`the server) may generally be referred to as a compute server.
`Other types of servers, for performing other types of services
`and operations at the request of clients, will be appreciated
`by those skilled in the art.
`In a client/server arrangement, device 12(m) requiring
`service by, for example, a device 13, generates one or more
`request message packets requesting the required service, for
`transfer to the device 13. The request message packet
`includes the Internet address of the device 13 that is, as the
`destination device, to receive the message packet and per-
`form the service. The device 12(m) transfers the request
`message packet(s) to the ISP 11. The ISP 11, in turn, will
`transfer the message packet over the Internet to the device
`13. If the device 13 is in the form of a WAN or LAN, the
`WAN or LAN will receive the message packet(s) and direct
`it (them) to a specific device connected therein which is to
`provide the requested service.
`In any case, after the device 13 which is to provide the
`requested service receives the request message packet(s), it
`will process the request. If the device 12(m) which generated
`the request message packet(s), or its operator, has the
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`45
`
`50
`
`55
`
`60
`
`65
`
`Petitioner Apple Inc. - Ex. 1024, p. 5
`
`Petitioner Apple Inc. - Ex. 1024, p. 5
`
`

`

`US 6,557,037 B1
`
`7
`required permissions to request the service from the device
`13 which generated the request message packet,
`if the
`requested service is to initiate the transfer of information
`from the device 13 as a storage server to the device 12(m)
`as client, the device 13 will generate one or more response
`message packets including the requested information, and
`transmit the packet(s) over the Internet 14 to the ISP 11. The
`ISP, 11, in turn, will transfer the message packet(s) to the
`device 12(m). On the other hand, if the requested service is
`to initiate processing by the device 13 as a compute server,
`the device 13 will perform the requested computation
`service(s). In addition, if the device 13 is to return processed
`data generated during the computations to the device 12(m)
`as client, the device 13 will generate one or more response
`message packet(s) including the processed data and transmit
`the packet(s) over the Internet 14 to the ISP 11. The ISP 11,
`in turn, will transfer the message packet(s) to the device
`12(m). Corresponding operations may be performed by the
`devices 12(m) and 13, ISP 11 and Internet 14 in connection
`with other types of services which may be provided by the
`server devices 13.
`
`As noted above, each message packet that is generated by
`devices 12(m) and 13 for transmission over the Internet 14
`includes a destination address, which the switching nodes
`use to route the respective message packet to the appropriate
`destination device. Addresses over the Internet are in the
`
`form of an “n"-bit integer (where “11” currently may be thirty
`two or 128). To relieve, in particular, an operator of a device
`12(m) of the necessity of remembering specific integer
`Internet addresses and providing them to the device 12(m) to
`initiate generation of a message packet for transmission over
`the Internet,
`the Internet provides a second addressing
`mechanism which is more easily utilized by human opera-
`tors of the respective devices. In that addressing mechanism,
`Internet domains, such as LAN’s, Internet service providers
`(“ISP’s”) and the like which are connected in the Internet,
`are identified by relatively human-readable names. To
`accommodate human-readable domain names, ISP 11 is
`associated with a nameserver 17 (which may also be referred
`to as a DNS servers), which can resolve the human-readable
`domain names to provide the appropriate Internet address
`for the destination referred to in the respective human-
`readable name. Generally, the nameserver may be part of or
`connected directly to the ISP 11, as shown in FIG. 1, or it
`may be a particular device which is accessible through the
`ISP over the Internet. In any case, as noted above, when the
`device 12(m) logs on to the ISP 11 during a communications
`session,
`the ISP 11 will assign various Internet protocol
`(“IP”) parameters which the device 12(m) is to use during
`the communications session, which will be stored in the
`Internet parameter store 25. These IP parameters include
`such information as
`
`(a) an Internet address for the device 12(m) which will
`identify the device 12(m) during the communications
`session, and
`(b) the identification of a nameserver 17 that the device
`12(m) is to use during the communications session.
`The device 12(m), when it generates message packets for
`transfer, will include its Internet address (item (a) above) as
`the source address. The device(s) 13 which receives the
`respective message packets can use the source address from
`message packets received from the device 12(m) in message
`packets which they (that
`is, device(s) 13) generate for
`transmission to the device 12(m),
`thereby to enable the
`Internet
`to route the message packets generated by the
`respective device 13 to the device 12(m). If the device 12(m)
`is to access the nameserver 17 over the Internet 14, the
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`nameserver identification provided by the ISP 11 (item (b)
`above) will be in the form of an integer Internet address
`which will allow the device 12(m) to generate messages to
`the nameserver 17 requesting resolution of human-readable
`Internet addresses into integer Internet addresses. The ISP 11
`may also assign other IP parameters to the device 12(m)
`when it logs on to the ISP 11, including, for example, the
`identification of a connection to the lntemet 14 that is to be
`used for messages transmitted by the device 12(m), particu-
`larly if the ISP 11 has multiple gateways. Generally, the
`device 12(m) will store the Internet parameters in the
`Internet parameter store 25 for use during the communica-
`tions session.
`
`When an operator operating device 12(m) wishes to
`enable the device 12(m) to transmit a message packet to a
`device 13, he or she provides the Internet address for the
`device 13 to the device 12(m), through the operator interface
`20, and information, or the identification of information
`maintained by the device 12(m) that is to be transmitted in
`the message. The operator interface 20, in turn, will enable
`the packet generator 22 to the required packets for trans-
`mission through the ISP 11 over the Internet 11. If
`(i) the operator has provided the integer Internet address,
`or
`
`(ii) the operator has provided the human-readable lntemet
`address, but the packet generator 22 already has the
`integer lntemet address which corresponds to the
`human-readable Internet address provided by the
`operator,
`the packet generator 22 may generate the packets directly
`upon being enabled by the operator interface 20, and provide
`them to the network interface 21 for transmission to the ISP
`11.
`
`However, if the operator has provided the human-readable
`Internet address for the device 13 to which the packets are
`to be transferred, and if the packet generator 22 does not
`already have the corresponding integer Internet address
`therefor, the packet generator 22 will enable the network
`address to be obtained from the nameserver 17 identified in
`the IP parameter store 25.
`In that operation,
`the packet
`generator 22 will initially contact nameserver 17 to attempt
`to obtain the appropriate integer lntemet address from the
`nameserver 17. In these operations, the device 12(m) will
`generate appropriate message packets for transmission to the
`nameserver 17, using the nameserver’s integer lntemet
`address as provided by the ISP 11 when it (that is, the device
`12(m)) logs on at
`the beginning of the communications
`session. In any case, if the nameserver 17 has or can obtain
`the integer Internet address for the h