MXPA01000537A - Subscriber creation and deletion interface between a customer administrative system and database network elements of a communications network - Google Patents

Abstract

A customer administrative system (14) is interfaced (22) with one or more database network elements (26) having unique subscriber creation or deletion policies. An agent (32) is included within the interface to process a received generic subscriber creation or deletion command originated by a customer administrative system. Responsive thereto, the one or ones of the database network elements implicated by the command are identified (42) and issued, in accordance with the appropriate unique policy for each identified database network element, the required individual database network element specific commands (46) necessary to effectuate the subscriber creation or deletion activity.

Description

INTERFACE OF CREATION AND ELIMINATION OF SUBSCRIBER BETWEEN A CUSTOMER ADMINISTRATOR AND NETWORK ELEMENTS SYSTEM DATABASE OF A COMMUNICATIONS NETWORK DESCRIPTION OF THE INVENTION Technical Field of the Invention The present invention relates to a communication network and in particular, to an improvement of the interface between a client administrator system and database network elements of a communication network for support a generic subscriber creation and deletion policy. Description of the Related Art Reference is now made to Figure 1, wherein a block diagram illustrating a portion of a communications network 10 implementing a transaction based interface of the prior art (IF) 12 between a client manager system (CAS) 14 and a plurality of database network elements (NE) 16. The client manager system interface 12, and the database elements 16 are interconnected using a network 18 preferably which comprises a network, such as an X.25 network, separated from the communication network 10. As an example, the communication network 10 may comprise a wireless telecommunications system (e.g., cellular) with each database network element 16, comprising, for example, a database that stores permanent and temporary wireless subscription data (e.g., an initial position record (HRL)). The permanent data stored in the database network element 16 comprises fixed information concerning the communication service subscribed for each subscriber. The temporary data stored in the database network element 16 comprises variable information concerning the actual location of each subscriber. The client administrator system 14 is used for coupling in transactions that refer to the management of the permanent data stored in each database network element 16. These administration activities, in general, refer to transactions executed for the purposes of creation or elimination of client (that is, subscriber), activation of service or similar, in relation to a specific client. More particularly, transactions refer to subscriber data manager tasks such as: - initiation / removal / subscription status, - subscriber activation / cancellation, - provision / withdrawal / activation / service stabilization, - definition of number C (transfer), - passcode changes, and - serial number changes. Transactions can also be related to authentication management tasks such as activation / change / deactivation / authentication status.

Additionally, the transaction refers to a numbering plan configuration that includes the number range assignment, the elimination of the numbering plan and the visualization of the numbering plan. By "transaction-based", it is implied that the interface 12 receives orders originated in the client manager system 14 and addressed (ie addressed) to a particular one of the database network elements 16, converts those commands into the appropriate format for communication to and compression of the addressed database network element, and routes the addressed database network element. Similarly, the interface 12 receives any response to the command from the addressed database network element 16, converts the response to a format suitable for communication 16 and / understanding the client administrator system 14 that originated the command, and routes it to the originating client administrator system. It is recognized that each of the database network elements 16 may have a single policy with respect to the procedures and transactions that will be increased in connection with the creation or deletion of subscribers., and also that these policies refer to identical creation or elimination activities that may differ from one element to another. Take, for example, the subscriber deletion activity. A database network element 16 can implement a policy for deletion of subscriber in which the following transactions must be executed (in that order): (1) delete each of the services assigned to the subscriber, and then (2) explicitly delete to the subscriber of those services. Another database network element 16 can implement a policy for deleting subscribers in which to execute the following transaction: eliminating each of the services operated to the subscriber, with the deletion of the subscriber of those services that occurs automatically after the elimination of All the services. Although another database network element 16 may implement a policy for deletion of subscriber in which the next transaction should be executed. Explicitly delete the subscriber, with the elimination of each of the services assigned to the subscriber that occurs automatically after the deletion of the subscriber. The database network element 16 based on difference and / or variations in policies with respect to the necessary transactions are applied to the creation of the subscriber. For example, a database network element 16 may implement a policy that allows a subscriber to be created without having to simultaneously assign any service to the subscriber. In such a situation, the subscriber's services can be defined at a later stage. Even another database network element 16 may require at least one service to be assigned at the time of creating the subscriber. In order to couple a subscriber creation or deletion activity, the service provider may first recognize the appropriate policy or policies to be used for the database element (s) involved 16, and secondly, merge the coupled transactions in accordance with the policy to complete the subscriber creation or deletion activity on those database elements. Take for example, a subscriber deletion activity in accordance with the aforementioned policy where the following transactions must be executed (in that order): (1) delete each of the services assigned to the subscriber, and then (2) explicitly delete to the subscriber of those services. In this scenario, first a command (comprising for example a subscriber deletion request) originates in the client manager system 14 for each of the subscribed services, with the commands directed through the interface 12 to the or particular database network elements 16 that support those services. The interface 12 operates in the manner described above to convert each of the commands to a suitable format for communication to and comprising the involved database network element 16 and routes the commands to that database network element. Next, a command (comprising, for example, a subscriber deletion request) originates in the client manager system 14, and is directed through the interface 12 to the particular database element (s) 16 that support previously deleted services. The interface 12 operates in the manner described above to convert the command to a suitable format for communication to and / comprising the involved network network element of the database 16 and routes the command to that database network element. The foregoing illustrates how the intensive management (i.e., the message) of the creation or deletion activity to the subscriber can be done with respect to the client manager system only for a single policy on an individual database network element. Additional complications for subscriber creation or deletion activity are introduced when the subscriber and its services are handled by plural database elements. In such a situation, it is possible that the plurality of involved database network elements each support different unique policies. The appropriate commands, in the proper order and in accordance with each of the unique policies, must be issued from the client administrator system 14 and processed through the interface 12 for the management of the database network element 16. There is a need for an improved interface between a client manager system and a plurality of database network elements that will support a generic policy for the creation or deletion of a subscriber.

BRIEF DESCRIPTION OF THE INVENTION An interface is provided between a client manager system and one or more database network elements that have unique subscricreation or deletion policies. The interface includes an agent that supports a generic subscricreation or deletion policy. The agent operates in response to a generic subscricreation or deletion command received and which was originated by a client administrator system to identify one or some of the database network elements that are involved by the command. The agent then generates, in accordance with the appropriate single policy for each identified database network element, the required individual database network element commands required to perform the subscricreation or deletion activity. The specific commands are then routed to the appropriate database network elements to process until the subscricreation or deletion activity specified by the generic command is terminated.

BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the method and apparatus of the present invention can be acquired by reference to the following detailed description when taken in conjunction with the accompanying drawings in which: Figure 1, previously described, is a diagram block of a portion of a communications network that implements a prior art transaction based interface between a client manager system and a plurality of database network elements; Figure 2 is a block diagram of a portion of a communication network with an interface of the present invention between a client manager system and a plurality of database network elements where the interface supports a generic policy for the subscricreation and deletion activities; Figure 3 is a nodal operation and signal flow diagram illustrating the interface operation for handling generic commands of the client manager system for the creation and deletion of the subscri Figure 4 is a block diagram of a plurality of communication networks with a multiple layer interface of the present invention between a client manager system and a plurality of database network elements where the multiple layer interface supports a generic policy for subscricreation and deletion activities; Figure 5 is a nodal operation and signal flow diagram illustrating the operation of the multiple layer interface for handling generic commands in a client manager system for subscricreation and deletion.

DETAILED DESCRIPTION OF THE DRAWINGS Referring now to Figure 2, where a block diagram of a portion of a communications network 20 is shown implementing an interface of the present invention (IF) 22 between a client management system (CAS) 24 and a plurality of database network elements (NE) 26 wherein the interface supports a generic policy for subscricreation or deletion activities. In this regard, the database network elements 26 each implement a unique policy for subscricreation or deletion activities. Examples of such policies have been previously described. In some situations, these unique policies may differ from one element to another through the plurality of database network elements 26 within the same network 20. The client administrator system 24, the interface 22 and the network elements of database 26 are interconnected using a network 28 which preferably comprises a network, such as an X.25 network separate and apart from the communications network 20. As an example, the communication network 20 may comprise a wireless communication system (for example, cellular), with each database network element 26 then comprising a database that stores permanent and temporary wireless subscriber data (e.g., an initial position register (HLR)) as previously described. Thus, the database network elements 26 store permanent data comprising subscriber communications service information, and temporary data comprising the current location of each subscriber. The communication network 20 may comprise another communication network that provides services such as, for example, a data communication network such as the Internet. The interface 22 supports the same processing based on conventional transaction as the interface of the prior art 12 illustrated in Figure 1 and previously described. These transactions involve the operation of the client manager system 24 in the management of the permanent data stored in each database network element 26. As an additional feature, the interface 22 further includes a generic subscriber creation and deletion agent 32 This agent 32 is responsible for the implementation of subscriber creation and deletion activities in the database network elements 26 in response to a single generic subscriber creation or deletion command issued by the client manager system 24 and according to the unique policies of each database network element. The agent 32 functions to (a) identify each generic subscriber creation or deletion command received from one or more database network elements 26 that are accepted by the command (i.e., the database network elements that they support the subscription of a certain subscriber identified within the command), (b) identify the activation or particular management actions (arranged in the proper order, if appropriate) that are to be taken by each element of the base network of data in relation to that generic command and in accordance with the single subscriber creation or deletion policy for the identified database network element, (c) identify the individual element specific commands needed for the identified actions, (d) generate each of the individual element specific commands in an appropriate format (ie adapter) and in the appropriate order, where appropriate, for communication n to and / comprising the identified database network elements, and (e) issuing the individual element specific commands for each of those elements in accordance with its single subscriber creation or deletion policy. To support this operation, the agent 32 keeps track of the unique subscriber creation or deletion policies for each database network element 26, as well as an identification of the subscription or subscriptions owned by each subscriber together with the subscriber elements. database network that supports those subscriptions. This policy and information related to the subscriber / subscription can be entered and changed when necessary (not shown) for (and for storage in) the agent 32 through an appropriate user interface device 34 (such as a terminal). data). The agent 32 accordingly recognizes each identified subscriber, based on its subscription, which of the plural database elements 26 needs to communicate in order to perform a subscriber activation or deletion activity. For each generic subscriber creation or deletion command received, the appropriate plural database network element (s) 26 is identified and the individual element specific commands appropriately formatted in accordance with the single subscriber creation or deletion policy are issued. for each database network element. The agent 32 further receives any response for the individual element specific commands of the network elements 26, converts the response (if necessary) to an individual response in an appropriate format for communication to and / or comprising the client administrator system 24 that originated the generic command, and routes (if necessary) the appropriately formatted response to that source client administrator system. The generic subscriber creation or deletion command can also specify the scope of the subscriber creation or deletion activity to be executed. By this it is implied that a specification can be made for a limited subscriber creation or deletion activity instead of a normal activity. Accordingly, the specified subscriber creation or deletion activity can be selectively selected and implemented with respect to only some database network elements 26 within the network 20. Reference is now made in addition to Figure 3 wherein a nodal operation and signal flow diagram illustrating the interface 22, the operation of the agent 32 for managing the client manager system 24 and the subscriber creation or deletion activities specified by specific command are shown. The client manager system 24 sends a generic subscriber creation or deletion command independent of the machine and the policy (ie generic for the machine) 40 (with a specified scope) to the interface 22. The attached agent 32 processes the command received in action 42 to determine which elements of the plurality of database network 26 need to be accessed in order to complete the subscriber creation or deletion activity. To support the process of identification of the action 42, the agent 32 keeps track of the relationships between each subscriber and their subscription or subscriptions together with an identification of the database network element (s) 26 that supports that subscription or subscriptions. The agent 32 consequently recognizes each subscriber identified within the generic service creation or deletion command that the plural database network elements 26 need to communicate in order to perform the designated activity. The following identification of those database network elements involved 26, the interface 22 then identifies in action 44 the particular actions (arranged in the proper order, (if appropriate) to be taken by each element of the database network in relation to that generic command 40 and in accordance with the single subscriber creation or deletion policy for the identified database network element The interface 22 then identifies in the action 46 the commands specific elements that are necessary to perform those actions through each of the database network elements 26.

Those element-specific commands are sorted, when appropriate, according to the relevant single subscriber creation or deletion policy, and are formatted according to a certain format and protocol associated with each of the database network elements identified 26 (such as a machine-dependent language). As an example, the original machine independent generic command 40 is translated into a plurality of machine dependent commands 48 adapted for the identified database network elements and which adhere to the single subscriber creation or deletion policy for the identified database network element. The interface 22 then outputs the device-specific commands suitably formatted (and ordered) 48 for each of the database network elements involved 26. Once it has been issued, the appropriately formatted command 48 has been received by one of the the database network elements 26, that element processes the commands in action 50 to perform the required action in relation to the specified subscriber creation or deletion activity. Once the action has been terminated, the database network element 26 sends a confirmation message 52 back to the interface 22. Meanwhile, the interface 22 monitors the receipt of the confirmation messages 52 in action 54 with relation to each command issued 58 to determine whether all actions have been terminated or not by the database network elements 26. If yes, the subscriber creation or deletion activity has been successfully achieved. In the event that not all confirmations are received within a certain period, it is assumed that the actions required for the creation or removal of the service were not completed. The response to the determination of monitoring in action 54, a return message 56 is sent by the interface 22 that informs the originating client administrator system 24 if the generic command 40 that refers to the activation or deletion of the subscriber is successfully terminated or not. Referring now to Figure 4, where a block diagram of a plurality of communication networks 120 with a multiple layer interface of the present invention (FI) 122 between a client manager system (CAS) 124 and a plurality of database network elements (NE) 126 located within networks 120 where the multiple layer interface supports a generic policy for subscriber creation or deletion activities. In this regard, the database network elements 126 each implement a unique policy for subscriber creation or deletion activities. The examples of those policies have been previously described. In some situations, those unique policies may differ from one element to another through the plurality of database network elements 126. The multiple layer interface 122, the client manager system 124 and the database network elements 126 ( within networks 120) are connected using a network 128 preferably comprising a network, such as an X.25 network separate and apart from communications network 120. As an example, one of communication networks 120 (1) it can comprise a data communications network of the Internet type, and the other of the networks 120 (2) may comprise a wireless communications system (for example, cellular). With respect to the communications network 120 (1), each of the database network elements 126 comprises a service node that stores the subscriber data of the data communications service. With respect to the communication network 120 (1), each of the database network elements 126 comprises a database that stores the permanent and temporary wireless subscriber (e.g., an initial position register (HLR)) of data. It is of course understood that in some cases the functionalities performed by the network elements 126 and the secondary interface 122s can be contained within an individual node of the network 120. The multiple layer interface 122 supports the same processing on a transaction basis. conventional than the interface of the prior art 12 illustrated in Figure 1 and previously described. These transactions involve the client manager system 124, the operation in the administration of the stored data of the database network element 126. As an attached feature, the multiple layer interface 122 may further include an agent for the creation and deletion of data. generic subscriber 132. This agent 132 is responsible for implementing subscriber creation and deletion activities through networks 120 and in database network elements 126 in response to a single generic subscriber creation or deletion command issued by the client administrator system 124 and in accordance with the subscriber creation and removal policies of the database network elements. The agent 132 functions to (a) identify each generic subscriber creation or deletion command received from one or more database network elements 126 that are affected by the command (i.e., the database network elements that support the subscriptions of a certain subscriber identified within the command), (b) identify the activation or particular management actions (arranged in the appropriate order, if appropriate) that are to be taken by each element of the base network of data identified in relation to that generic command and in accordance with the single subscriber creation or deletion policy for the identified database network element, (c) identify the specific element-specific commands necessary to achieve the identified actions, ( d) generate each of the specific commands of the individual element in a suitable format (ie adapted) and in the appropriate order, when appropriate, for common and (e) issue the individual element specific commands for each of these elements in accordance with its single subscriber creation or deletion policy. To support this operation, the agent 132 keeps track of the subscriber creation or deletion policies for each database network element 126, as well as an identification of the subscription or subscriptions belonging to each subscriber together with the subscriber elements. database network that supports one or more subscriptions. This policy and the information related to the subscriber / subscription can be introduced and changed when necessary (not shown) for (and for storage in) the agent 132 through an appropriate user interface device 134 (such as a data terminal). The agent 132 accordingly recognizes for each subscriber, based on its subscriptions, which of the plural database elements 126 needs to be communicated in order to perform a subscriber activation or deletion activity. For each generic subscriber creation or deletion command, the appropriate plural database network elements 126 are identified and the individual element specific commands are properly formatted according to the single subscriber creation or deletion policy for each element of database network. The agent 132 further receives any response for the individual element-specific commands from the network elements 126, converts the response (if necessary) to an individual response in a format suitable for communication to and comprising the client administrator system 124 that originated the generic command, and routes (if necessary) the appropriately formatted response to that administrator system. client of origin. With respect to this multi-layer interface architecture 32 it is noted that the primary phase interface layer 122p is implemented to facilitate communications with the client manager system 124 concerning subscriber creation and deletion activities. It is also noted that a secondary interface layer 122s is implemented within each of the plural networks 120 to facilitate communications in each of the networks 120 with the database network elements 126. Each interface 122p or 122s includes the agent functionality 132 to support a generic policy for subscriber creation or deletion activities. Of course, it is understood that the interface 122 in a plural network system 120 can alternatively be implemented as an individual layer interface 22 in the manner illustrated in Figure 2 and described above. In the illustrated multiple layer structure, a user (not shown) can enter the appropriate policy and information related to the subscriber / subscription through the user interface 134 to store in the agent 132 of each primary layer 122p and the secondary interface layer 122s. The generic subscriber creation or deletion command can also specify the scope of the subscriber creation or deletion activity to be executed. By this it is implied that a specification can be made for a limited subscriber creation or deletion activity rather than a global activity. Accordingly, the specified subscriber creation or deletion activity can be selectively selected and implemented with respect to only some of the database network elements 126 within the network 120. In addition, the subscriber creation or deletion activity can be selectively selected and implemented with respect to certain database network elements 126 only within some of the networks 120. Referring now in addition to FIG. 5, where a flow diagram of nodal operation and signal illustrating the multiple layer interface 122, the agent 132, the operation for managing the client administrator system 124, the creation and deletion activities of the generic command subscriber. The client manager system 124 sends a machine-independent (ie generic for machine) generic policy subscriber creation or deletion command 140 (with a specified scope) to the primary interface 122p. The primary agent 132 within the primary phase layer 122p processes the command received in the action 142 to identify which plural networks 120 need to be accessed to complete the requested subscriber creation or deletion activity. The received command is then sent (with a minor modification required) in the command 144 over the secondary interface 122s within each of the networks 120. The secondary agent 132 within each of the secondary interface layers 122s processes the sent command 144 in action 146 to identify which of the plurality of database network elements 126 need to be accessed in order to complete the requested subscriber creation or deletion activity. To support the identification process of the action 146, the secondary agent 132 keeps track of the relationships between the subscriber and its subscriptions together with the database network element 126 that supports those subscriptions. The secondary agent 132 accordingly recognizes for each subscriber identified within the generic service creation or deletion command sent 144 which elements of the plural database network 126 need to be communicated in order to effect, the designated activity. After the identification of those involved database network elements 126, the secondary interface layer 122s identifies in action 148 the particular actions (arranged in the proper order, if appropriate) that are to be taken by each database network element in relation to that generic command sent 144 and in accordance with the single subscriber creation or deletion policy for the identified database network element. The secondary interface layer 122s identifies in action 150 the element-specific commands that are necessary to perform those actions by each of the database network elements 126. Those element-specific commands are ordered, when appropriate , in accordance with the relevant single subscriber creation or deletion policy, and are formatted according to a certain format and protocol associated with each of the identified database network elements 126 (such as a machine-dependent language) . As an example, the original machine independent sent command 144 is translated into a plurality of machine dependent commands 152 adapted for the identified database network elements and which adhere to the single subscriber creation or deletion policy for the identified database network element. The secondary layer layer 122s then outputs the properly formatted (and ordered) device specific commands 52 for each of the involved database network elements 126. Once a properly formatted and issued command 152 has been received by one of the identified database network elements 126, that element processes the command in action 154 to perform the required action in relation to the specified subscriber creation or deletion activity. Once the action has been terminated, the database network element 126 sends a confirmation message 156 back to the secondary interface layer 122s. Meanwhile, the secondary interface layer 122s monitors the reception of the confirmation messages 154 in the action 158 in relation to each issued command 152 to determine whether all actions have been completed by the database network elements 126. In case In the affirmative, the subscriber creation or deletion activity in that network 120 has been successfully completed. In the event that all confirmations are not received within a certain period, it is assumed that the actions required for the creation or removal of service were not completed. The response to the determination of the monitoring in action 158, a return message 160 is sent by the secondary interface layer 122s informing the primary interface layer 122p of whether the activation or deletion of subscriber in that network 120 was successfully completed or not. Meanwhile, the primary interface layer 122p monitors the reception of return messages 158 in action 162 in relation to each command sent 144 to determine whether the subscriber creation or deletion activities were successfully completed or not in each network 120. In In the affirmative case, the generic message 140 specified the subscriber creation or deletion activity that has been successfully completed. If the affirmative confirmations (messages 158) were not received from the secondary interface layer 122s within a certain period, it is assumed that the required creation or deletion of service activities were not completed. In response to the monitoring determination in action 162, a return message 1643 is sent by the primary interface layer 122p to the originating client manager system 124 to determine whether or not the generic command 140 concerned was successfully completed. to the activation or deletion of subscriber. Although the preferred embodiments of the method and apparatus of the present invention are illustrated in the accompanying drawings and have been described in the above detailed description, it will be understood that the invention is not limited to the embodiments described, but is capable of numerous rearrangements, modifications and substitutions without departing from the spirit of the invention as set forth and defined by the following claims.

Claims (13)

1. CLAIMS 1. A system comprising: a client administrator system that operates to issue an individual generic command concerning the subscriber creation or deletion activity; a plurality of database network elements of a communication system, each database network element having a unique policy for subscriber creation or deletion; and an interface between the client manager system and each of the plurality of elements or database network, the interface that includes an agent functionality that responds to the generic command to identify the database network elements that support a subscriber subscription implied by the command, and the issuing device-specific commands for each of the database network elements identified in accordance with its unique policy for subscriber creation or deletion, wherein the device-specific commands emitted specify the processing actions that are going to be taken by the identified database network elements to perform the subscriber creation or deletion activity specified by the generic command. The system according to claim 1, characterized in that the communication network comprises a wireless telecommunications network and the database network elements comprise initial position records of the wireless telecommunications network. The system according to claim 2, characterized in that the communication network further comprises an Internet data communications network and the database network elements comprise Internet service nodes of the data communications network of the Internet. Internet. 4. An interface between a client manager system and a plurality of database network elements of a communication network, the interface that includes an agent that functions to: receive an individual generic task command concerning a creation activity or deletion of subscriber; identify some of the database network elements that support a subscriber subscription involved by the generic command; generate implementation commands for each of those database network elements identified in accordance with its unique policy for subscriber creation or deletion, in each of the generated implementation commands are specifically adapted to be understood by some of the elements network database; and issuing the generated implementation commands for some of the identified database network elements, where the issued impiementation commands specify the processing actions to be taken by some of the database network elements identified for perform the subscriber creation or deletion activity specified by the generic command. The interface according to claim 4, characterized in that the communication network comprises a wireless telecommunications network and the database network elements comprise initial position records of the wireless telecommunications network. The interface according to claim 5, characterized in that the communication network further comprises an Internet data communications network and the database network elements comprise Internet service nodes of the data communication network of the Internet. Internet. The interface according to claim 4, characterized in that the agent functions to generate additional functions to generate each implementation command in a machine-dependent language for some of the identified database network elements. The interface according to claim 4, characterized in that the agent function generates additional functions for translating the generic command from a machine-independent language into a plurality of implementation commands each having a machine-dependent language for some of them. the identified database network elements. 9. A method for interfacing a client manager system and a plurality of database network elements of a communication network, the method comprising the steps of: receiving an individual generic command from the client administrator system with regard to to the subscriber creation or deletion activity; identifying some of the plurality of database network elements that support a subscriber subscription implied by the generic command; generate implementation commands for each of the database network elements identified in accordance with its unique policy for subscriber creation or deletion, where each of the generated implementation commands is specifically adapted to be understood by one of the identified database network elements; and issuing the generated implementation commands for some of the identified database network elements, where the issued implementation commands specify the processing actions to be taken by some of the database network elements identified for perform the subscriber creation or deletion activity specified by the generic command. The method according to claim 9, characterized in that the communication network comprises a wireless telecommunications network and the database network elements comprise initial position records of the wireless telecommunications network. The method according to claim 10, characterized in that the communication network further comprises an Internet data communications network and the database network elements comprise Internet service nodes of the data communications network of the Internet. Internet. The method according to claim 9, characterized in that the generation step further comprises the step of generating each implementation command in a machine-dependent language for some of the identified database network elements. The method according to claim 9, characterized in that the generation step further comprises the step of translating the generic command from a machine-independent language into a plurality of implementation commands each having a machine-dependent language for some of the identified database network elements.