Claim Terms That Third-Parties Previously Proposed As Being Subject 35 U.S.C. § 112, Sixth Paragraph1
`
`Claim
`
`’099
`claim 1
`
`’099
`claim 1
`
`’099
`claim 1
`
`’099
`claim 1
`
`Term
`
`“a parser subsystem … the parser subsystem configured
`to examine the packet accepted by the buffer, extract
`selected portions of the accepted packet, and form a
`function of the selected portions sufficient to identify that
`the accepted packet is part of a conversational flow-
`sequence”
`
`“a lookup engine … configured to determine using at least
`some of the selected portions of the accepted packet if there
`is an entry in the flow-entry database for the conversational
`flow sequence of the accepted packet”
`“a protocol/state identification mechanism … the
`protocol/state identification engine configured to determine
`the protocol and state of the conversational flow of the
`packet”
`“a state processor … the state processor, configured to
`carry out any state operations specified in the state
`patterns/operations memory for the protocol and state of the
`flow of the packet, the carrying out of the state operations
`furthering the process of identifying which application
`program is associated with the conversational flow-
`sequence of the packet, the state processor progressing
`through a series of states and state operations until there are
`no more state operations to perform for the accepted packet,
`in which case the state processor updates the flow- entry, or
`
`Previously-Proposed Corresponding Structure/Act
`Pattern recognition engine 1006, extraction engine
`(slicer) 1007, and parser output buffer memory 1010 of
`the hardware parser subsystem of Fig. 10, as described at
`21:60-67 and 22:14-63 of ’099 Patent
`
`Lookup/update engine (LUE) 1107 of Fig. 11, as
`described at 23:29-62 of ’099 Patent
`
`state processor instruction database 326 and hardware or
`processor running the algorithm, as described at 14:38-46
`of ’099 Patent
`
`State processor (SP) 1108 of Figs. 11 and 13, as
`described at 25:3-26:44 of ’099 Patent
`
`1 Ex. 1077 (Ericsson Case Joint Claim Construction and Prehearing Statement), 18-31; Ex. 1078 (Patentee’s Opening Claim
`Construction Brief in Cisco Case), 33-34.
`
`EX. 1081 Page 1
`
`

`

`Claim
`
`Term
`
`Previously-Proposed Corresponding Structure/Act
`
`’646
`claim 1
`
`’646
`claim 1
`
`until a final state is reached that indicates that no more
`analysis of the flow is required, in which case the result of
`the analysis is announced”
`“a lookup engine … configured to lookup whether a
`received packet belongs to a flow-entry in the flow- entry
`database, to looking up being the cache subsystem”
`
`“a state processor … the state processor being to perform
`any state operations specified for the state of the flow
`starting from the last encountered state of the flow in the
`case that the packet is from an existing flow, and to perform
`any state operations required for the initial state of the new
`flow in the case that the packet is from an existing flow”
`
`’646
`claim 2
`
`“a parser subsystem … the parser subsystem configured to
`extract identifying information from a received packet”
`
`’646
`claim 7
`
`“a parser subsystem … the parsing subsystem configured to
`extract selected portions of the accepted packet and to
`output a parser record containing the selected portions…
`wherein the operation of the parser subsystem depends on
`one or more of the protocols to which the packet conforms”
`
`Lookup/update engine (LUE) 1107 of Fig. 11, as
`described at 19:10-43 of ’646 Patent
`
`State processor (SP) 1108 of Figs. 11 and 13, as
`described at 20:49-22:20 of ’646 Patent
`
`Pattern recognition engine (PRE) 1006, extraction engine
`(slicer) 1007, and parser output buffer memory 1010 of
`the hardware parser subsystem of Fig. 10, as described at
`17:43-51 and 17:64-18:43 of ’646 Patent
`
`Pattern recognition engine (PRE) 1006, extraction engine
`(slicer) 1007, and parser output buffer memory 1010 of
`the hardware parser subsystem of Fig. 10, as described at
`17:43-51 and 17:64-18:43 of ’646 Patent
`
`2
`
`EX. 1081 Page 2
`
`

`

`Claim
`
`’646
`claim 7
`
`’646
`claim 7
`
`“a lookup engine … configured to lookup whether the
`particular packet whose parser record is output by the
`parser subsystem has a matching flow- entry, the looking
`up using at least some of the selected packet portions and
`determining if the packet is of an existing flow… the
`lookup engine configured such that if the packet is of an
`existing flow, the monitor classifies the packet as belonging
`to the found existing flow”
`“a flow insertion engine … configured to create a flow-
`entry in the flow-entry database, the flow-entry including
`identifying information for future packets to be identified
`with the new flow-entry”
`
`’646
`claim 16
`
`“performing one or more parsing/extraction operations on
`the packet to create a parser record comprising a function of
`selected portions of the packet”
`
`’751
`claim 17
`
`’789
`
`“an analyzer subsystem … configured to lookup for each
`received packet whether a received packet belongs to a
`flow-entry in the flow-entry database, to update the flow-
`entry of the existing flow including storing one or more
`statistical measures kept in the flow-entry in the case that
`the packet is of an existing flow, and to store a new flow-
`entry for the new flow in the flow-entry database, including
`storing one or more statistical measures kept in the flow-
`entry if the packet is of a new flow”
`“performing one or more parsing/extraction operations on
`the packet to create a parser record comprising a function of
`
`3
`
`Term
`
`Previously-Proposed Corresponding Structure/Act
`
`Lookup/update engine (LUE) 1107 of Fig. 11, as
`described at 19:10-43 of ’646 Patent
`
`Flow insertion/deletion engine (FIDE) 1110 of Figs. 11-
`12, as described at 19:30-35 and 22:21-23:17 of ’646
`Patent
`
`Acts of processing packet components (steps 503-512),
`extracting packet components and building a packet
`signature (steps 603-610), and hashing signature buffer
`element based on hash elements in pattern node of
`element database (steps 703-708) of Figs. 5-7, as
`described at 3:48-57 and 14:40-15:64 of ’646 Patent
`UFKB buffer, a lookup/update engine (LUE), a state
`processor (SP), a flow insertion and deletion engine
`(FIDE), a memory for storing the database of flows, a
`cache coupled to the memory containing the flow
`database, and a host bus interface, as described in 2:30-
`43, 20:18-53 of ’751 Patent
`
`Acts of processing packet components (steps 503-512),
`extracting packet components and building a packet
`
`EX. 1081 Page 3
`
`

`

`Claim
`
`Term
`
`claim 1
`
`selected portions of the packet”
`
`’789
`claim 19
`
`’789
`claim 19
`
`’789
`claim 19
`
`“a parser subsystem … the parsing subsystem configured to
`extract selected portions of the accepted packet and to
`output a parser record containing the selected portions …
`wherein the operation of the parser subsystem depends on
`one or more of the protocols to which the packet conforms”
`“a lookup engine … configured to lookup whether the
`particular packet whose parser record is output by the
`parser subsystem has a matching flow- entry, the looking
`up using at least some of the selected packet portions and
`determining if the packet is of an existing flow… the
`lookup engine configured such that if the packet is of an
`existing flow, the monitor classifies the packet as belonging
`to the found existing flow”
`
`“a flow insertion engine … configured to create a flow-
`entry in the flow-entry database, the flow-entry including
`identifying information for future packets to be identified
`with the new flow-entry … if the packet is of a new flow,
`the flow insertion engine stores a new flow-entry for the
`new flow in the flow-entry database, including identifying
`information for future packets to be identified with the new
`flow-entry”
`
`Previously-Proposed Corresponding Structure/Act
`
`signature (steps 603-610), and hashing signature buffer
`element based on hash elements in pattern node of
`element database (steps 703-708) of Figs. 5-7, as
`described at 7:65-8:6 and 18:61-20:20 of ’789 Patent
`Pattern recognition engine (PRE) 1006, extraction engine
`(slicer) 1007, and parser output buffer memory 1010 of
`the hardware parser subsystem of Fig. 10, as described at
`22:2-8 and 22:22-23:3 of ’789 Patent
`
`Lookup/update engine (LUE) 1107 of Fig. 11, as
`described at 23:38-24:3 of ’789 Patent
`
`Flow insertion/deletion engine (FIDE) 1110 of Figs. 11-
`12, as described at 23:58-63 and 26:53-27:50 of ’789
`Patent
`
`4
`
`EX. 1081 Page 4
`
`