Methods and devices for generating xml expressed management transactions

Abstract

New XML management transaction requests including XPath expressions are used, for example, to forward configuration changes on to a data network device. The generation and use of these new requests helps reduce the costs associated with designing or upgrading data network devices. These new requests may be generated in a novel command line interface that has been augmented to give a user access to more configuration functions. Complex management transactions may be executed substantially simultaneously by a central management module using the new requests and their associated XPath expressions. In addition to configuration changes, the new requests may be used to obtain the current configuration of data network devices.

1 . (canceled) 
   
   
       2 . (canceled) 
   
   
       3 . (canceled) 
   
   
       4 . (canceled) 
   
   
       5 . (canceled) 
   
   
       6 . (canceled) 
   
   
       7 . (canceled) 
   
   
       8 . (canceled) 
   
   
       9 . (canceled) 
   
   
       10 . (canceled) 
   
   
       11 . (canceled) 
   
   
       12 . (canceled) 
   
   
       13 . (canceled) 
   
   
       14 . (canceled) 
   
   
       15 . (canceled) 
   
   
       16 . (canceled) 
   
   
       17 . (canceled) 
   
   
       18 . (canceled) 
   
   
       19 . (canceled) 
   
   
       20 . (canceled) 
   
   
       21 . (canceled) 
   
   
       22 . (canceled) 
   
   
       23 . (canceled) 
   
   
       24 . (canceled) 
   
   
       25 . (canceled) 
   
   
       26 . (canceled) 
   
   
       27 . A CMM subsystem operable to:
 receive at least one XML expressed management transaction request including at least one target configuration element or state element; and   search a configuration and state information to determine whether there is a match for the at least one target configuration element or state element.   
   
   
       28 . The CMM subsystem as in  claim 27  further operable to return matching elements. 
   
   
       29 . The CMM subsystem as in  claim 27  wherein the request comprises an XPath expression. 
   
   
       30 . The CMM subsystem as in  claim 27  wherein the request comprises a programming language script. 
   
   
       31 . The CMM subsystem as in  claim 27  wherein the request comprises an XQuery expression. 
   
   
       32 . (canceled) 
   
   
       33 . (canceled) 
   
   
       34 . (canceled) 
   
   
       35 . (canceled) 
   
   
       36 . (canceled) 
   
   
       37 . (canceled) 
   
   
       38 . (canceled) 
   
   
       39 . (canceled) 
   
   
       40 . (canceled) 
   
   
       41 . (canceled) 
   
   
       42 . (canceled) 
   
   
       43 . (canceled) 
   
   
       44 . (canceled) 
   
   
       45 . (canceled) 
   
   
       46 . (canceled) 
   
   
       47 . (canceled) 
   
   
       48 . (canceled) 
   
   
       49 . (canceled) 
   
   
       50 . (canceled) 
   
   
       51 . (canceled) 
   
   
       52 . (canceled) 
   
   
       53 . (canceled) 
   
   
       54 . (canceled) 
   
   
       55 . (canceled) 
   
   
       56 . A method for identifying matches to a target configuration element within a subsystem comprising:
 receiving at least one XML expressed management transaction request including at least one target configuration element or state element; and   searching a configuration and state information to determine whether there is a match for the at least one target configuration element or state element.   
   
   
       57 . The method as in  claim 56  further comprising returning matching elements. 
   
   
       58 . The method as in  claim 56  wherein the request comprises an XPath expression. 
   
   
       59 . The method as in  claim 56  wherein the request comprises a programming language script. 
   
   
       60 . The method as in  claim 56  wherein the request comprises an XQuery expression.