Appeal 2007-1317
Application 09/731,623
useful in conjunction with the authentication services. The
configuration file 127 allows multiple authentication services
109 to be stacked for authenticating a user, and further enables
unified login to such stacked authentication services 109 with a
single password, and unified logout with a single logout
command [emphasis added].
(Wu, col. 6, l. 63 - col. 7, l. 4).
Nevertheless, we note that Appellants specifically point out that Wu’s
stacking of authentication services is not done in response to a second user
authentication (see Br. 9). Appellants further argue that Wu’s stacking (i.e.,
aggregation) of authentication services is preexisting and independent of any
actual user authentication action (id.). We find the issue before us presents a
close question, given that the broad language of the claim does not require
actual human authentication. Thus, we disagree with Appellants’ sweeping
assertion that Wu’s stacking (i.e., aggregation) of authentication services is
independent of any actual user authentication action, because user action by
a human is not required when the language of the claim is accorded a broad
but reasonable interpretation consistent with the Specification, as discussed
supra (see Br. 9). However, after closely examining the Wu reference in its
entirety, we nevertheless find clear support for Appellants’ position that
Wu’s stacking (i.e., aggregation) of authentication services is preexisting
(i.e., prestored). Specifically, we find Wu discloses that the stacking (i.e.,
aggregation) of service associations (i.e., authentication services) is stored in
configuration file 127:
Generally, the configuration file 127 stores a set of service
associations. Each service association relates one system entry
service 107 with one or more selected account management
7
Page: Previous 1 2 3 4 5 6 7 8 9 10 Next
Last modified: September 9, 2013