Appeal 2007-1063
Application 09/881,594
node is retained and not deleted. In one embodiment of the invention, the
first device, residing behind the firewall, sends the keep-alive messages
through the firewall and NAT to the node (Specification 8:2-5).
Thomas
4. Thomas teaches repeated back-and-forth communication
between a client located on one side of a firewall and NAT, and a server
located on the other side (Para. [0014]).
5. Thomas teaches that, because a firewall rejects unsolicited
communication from devices located outside, the client device is designated
to initiate communication with the server (Para. [0014]).
6. Thomas teaches that the client sends an identifying message to
a node on the other side of the firewall / NAT; receiving a response from the
node, wherein the messages from the client and node cause creation of a
path through the firewall / NAT; and conducting repeated further
communication between the client behind the firewall and the node on the
other side of the firewall (Para. [0038]).
7. Thomas further teaches that if a communications session is
initiated by the MAPI client, a MAPI server will use the IP address in the
packet header to communicate with that MAPI client for the duration of that
session (Para. [0038]).
8. In Thomas, a communications session between the MAPI client
and the MAPI server can be initiated by the MAPI client at a periodic
interval, for example every thirty seconds, every minute, five minutes, ten
minutes, or other appropriate period for that MAPI client and network (Para.
[0039]).
5
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next
Last modified: September 9, 2013