Abstract:
A system and method for creating and modifying intelligent telephone network call processing logic trees which can be customized for individual customers and created in a user-friendly visual environment (10, 15, FIG. 3-5). Service primitives are defined as logical graph nodes (20, FIG. 2, FIG. 3) which can be visually assembled into logic trees (FIG. 5) which represent the service logic flow and which provide default values for all service options. Higher level nodes, assembled from a plurality of service primitives, can likewise be defined and stored (12, 13, 19) for later use as entities in defining yet further call processing logic trees. These call processing logic trees are interpreted to allow the service control point computers (17) to implement the services in the switched telephone network (18) by sequentially executing the specified call processing primitives. A library (12, 13, 19) of defined nodes and defined node assemblies which represent service features can thus be made available to permit graphical manipulation into complete logic trees representing new services. These logic trees are then interpreted by generic programs in the service control point to actually provide the described services.

Description:
TECHNICAL FIELD 
     This invention relates to the creation and the provisioning of special customized telephone network services for telephone subscribers and, more particularly, to a portable, visually programmed call processing logic interface for creating and provisioning such customized services. 
     BACKGROUND OF THE INVENTION 
     New telephone services are continually being developed by telephone service providers in order to meet the needs of their customers. As such services become available, the telephone companies, subscribers and the users seek yet further improvements in these services. Special services such as 800 service, 900 service, and Private Virtual Networks (PVN) are only a few of the possible services being offered. Other services might well be conceived and might well find extensive use. Unfortunately, however, new telephone services have heretofore required long and expensive design, testing and deployment activities. Such special telecommunications services are typically provided in the public telephone network by computer program call processing sequences residing in digital switches. A typical approach to providing such special services is the introduction into the telephone network of a service implementing network element which interacts with the telephone network so as to implement the telephone services. Such service implementing network elements are variously called Service Adjuncts (SAs), Service Switching Points (SSPs) and Service Control Points (SCPs). One such Service Adjunct is disclosed in S. M. Lin and J. F. Rizzo U.S. Pat. No. 4,878,240, granted Oct. 31, 1989. A typical Service Switching Point is disclosed in J. J. Bernardis U.S. Pat. No. 4,782,517, granted Nov. 1, 1988. Finally, a typical Service Control Point is disclosed in J. O. Boese et al. application Ser. No. 453,042, filed Dec. 12, 1989. Each such service implementing network element is equipped with a set of software-implemented service primitives which can be combined in various ways to implement a number of telephone services. A set of such primitives for a Service Adjunct is disclosed in the above-mentioned Lin et al. patent. Another set of primitives for a Service Switching Point is disclosed in the above-mentioned Bernardis et al. patent. Yet another set of such primitives for a Service Control Point is disclosed in &#34;Business Services Database (BSDB): A Service Control Point (SCP) Application Designed to Support Private Virtual Network (PVN) Service, &#34;Technical Advisory TA-TSY-000460, Issue 2, February 1988, published by Bell Communications Research, Inc., Red Bank, N.J. All of these sets of service-implementing primitives are, as a group, generally equivalent, although each is implemented in a slightly different way. 
     A telecommunications network including such programmable special service implementing components is called an &#34;intelligent network.&#34; Such networks make it possible to offer useful and profitable new services such as 800 service, Alternate Billing service and Private Virtual Network service. Intelligent Network Call Processing Logic (INCPL) is the name given to the software that &#34;stitches together&#34; the appropriate service primitives to enable the Intelligent Network mechanism to implement and customize such services without the need for new switch software or hardware. Currently, this INCPL is custom-developed for each new service by a service designer, usually associated with the service provider, installed in the intelligent network service implementing component and supported by a service management system for that service. Thus, instead of the software to support a new service coming from a switch vendor, it can now come from a service vendor, making it possible to reduce the interval between service concept and service offering. Unfortunately, a great deal of time is still required to design custom and implement each new service. Moreover, since such service designs are not highly portable, further delays arise due to the need to provide widely distributed software elements to support the new service in a wide variety of different environments. 
     SUMMARY OF THE INVENTION 
     In accordance with the illustrative embodiment of the present invention, these and other problems are overcome by providing a user-friendly environment in which intelligent network service primitives can be assembled into telephone services utilizing the graphic capabilities of a computer workstation. If a complete telephone service is analyzed as a graph consisting of nodes and edges, the nodes represent the intelligent network service primitives executable by the service implementing components and the edges represent the order of execution of these primitives. Both action nodes and decision nodes can be defined in terms of the available service primitives and stored for later use in designing a new telephone service. Moreover, with this representation, the new telephone service can be displayed as a &#34;tree&#34; of such node. Such a tree display can be manipulated graphically to create and alter the logic of a service. An interpretor program, designed for a particular service implementing component, implements such display representations with the available adjunct service primitives. In accordance with this invention, telephone services can be created, manipulated and altered by simple, user-friendly graphical manipulation. Not only can intelligent network service primitives be assembled graphically into new services, but service features can be defined as assemblies of such intelligent network service primitives and, once designed, stored in a library as a single node to be invoked and reused as a single entity in designing a plurality of future services. 
     More particularly, graphical images or icons on a display screen are used to represent a reusable library of user-defined telephone service primitives. These images or icons can be manipulated graphically so as to assemble the images into logical trees representing new services or new service features. Once fully assembled, the electronic representation of the graphical service tree or service feature tree can be interpreted so as to actually implement the service or service feature. In this way, new telephone services can be designed and implemented much more quickly than in the prior art and thus save much of the expense previously associated with telephone service design and deployment. In addition, the extremely high level representation of telephone services implicit in the graphical service trees is an extremely portable mechanism for quickly and easily deploying such services without extensive reworking of service implementing code. Indeed, the simplicity, speed and flexiblity of telephone service design and implementation provided with the present invention can be exploited to allow each individual telephone user to custom design telephone services exactly matching the needs of the customer. 
     The present invention makes possible dynamic graphical creation, customization and provisioning of new call processing services. Using both simple nodes, hereinto called primitive nodes and consisting of, primitives and complex nodes that are user-defined constructed nodes and are called user defined service feature nodes, new services can be defined rapidly and with great ease. A new service is created visually as a logic tree with nodes defined to represent a high-level abstraction of the primitive call processing actions or call processing decision points or combinations of such primitive actions and decision points. This tree, or the electronic representation of the tree, is called a Call Processing Record (CPR) since it defines exhaustively the processing necessary to provide an individual call with the defined service. Service providers, as well as subscribers themselves, can customize and provision the graphically defined service to satisfy specific customer needs by dynamically modifying and parameterizing the relevant graphical call processing record trees. The thus provisioned call processing records representing the service can then be translated from the user-friendly visual format to a rigorous program-generating format which can be generically interpreted by existing service implementing components. The distribution and installation of such call processing records to appropriate service implementing components in an intelligent network enables the thus-described service to become instantly available to telephone subscribers. 
     There are three steps in this service specification process: 1) defining the nodes, 2) establishing which nodes can be used in a particular service, and, 3) creating call processing records defining a particular service using the nodes that have been defined, and to which can be added the customer-specific parameters necessary to completely specify the service. These three steps can be iterated interactively to improve the quality of the resulting service, to remove &#34;bugs,&#34; or to provide new features and capabilities. 
     Other aspects of a service creation and provisioning system are disclosed and claimed in the copending applications of D. L. Babson, J. A. Bajzath, Jr. and T. C. Ely, Ser. Nos. 629,371, 629,389, 629,390 and 629,447, all filed of even date herewith and assigned to applicants&#39; assignee. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     A complete understanding of the present invention may be gained by considering the following detailed description in conjunction with the accompanying drawings, in which: 
     FIG. 1/shows a block diagram of an intelligent telephone network including a graphical telephone service design and deployment system in accordance with the present invention; 
     FIG. 2 shows a flowchart of the service definition, provisioning and implementation processes taking place in the system of FIG. 1; 
     FIG. 3 is a graphical representation of a display screen used to define new telephone service primitives in the system of FIG. 1; 
     FIG. 4 is a graphical representation of a display screen used to define the allowable subset of telephone service nodes which are used to design and implement a particular advanced telephone service in the system of FIG. 1; and 
     FIG. 5 is a graphical representation of a display screen used to customize a logical tree template of service primitives by specifying all of the customer-dependent variables required to implement a particular new service for a particular customer in the system of FIG. 1. 
    
    
     To facilitate reader understanding, identical reference numerals are used to designate elements common to the figures. 
     DETAILED DESCRIPTION 
     Referring more particularly to FIG. 1 of the drawings, there is shown a general block diagram of an intelligent network telephone service design and deployment system comprising a workstation 10 for designing new telephone services in accordance with the present invention. As will be described hereinafter, workstation 10 includes graphical facilities for defining customer special service nodes in terms of service control point primitives, bounding new special services in terms of the thus defined nodes which can be used for that service, and assembling these telephone service nodes into templates or assemblies of call processing logic units capable of providing the new telephone special services. Service creation process 11 provides the software for supporting these facilities and includes standard window processing capability as well as mouse or other visual selection apparatus support, and is typically stored in the program memory of workstation 10. Storage device 12 stores a library of the electronic representations of all of the nodes previously specified, both simple primitive nodes and more complex, user-defined service feature nodes. Storage device 13 stores the definitions of all of the services defined at workstation 10, where a service definition is simply the specification of which of the defined nodes (primitives) can be used to implement a particular service. Storage device 19 stores templates of multinode fully designed services as call processing records. In the present application, a &#34;template&#34; is a fully designed service, but without all of the variable parameters which are dependent on the actual customer using the service. Although shown as separate storage devices, stores 12, 13 and 19 can be contained in a single storage device. 
     The present invention contemplates three steps in creating new services, defining graphical nodes from which services can be assembled (node definition), prescribing which nodes can be used in a particular service (service definition) and prescribing the logical interrelationships of the various nodes necessary to produce the desired service (call processing record creation). As new nodes are defined, they are stored in node library 12 for later retrieval and reuse. Once a new service is fully defined in terms of primitive or complex service nodes, a representation of that service definition is stored in a service definition storage facility 13. Once the service nodes are assembled into a service logic tree or template, that template is stored as a call processing record (CPR) in call processing record template library 19. The templates in library 19 require only the specification of certain customer-dependent variables required to fully implement the service for a particular customer. 
     A services management system 14 provides administrative control over a plurality of service control points such as service control point 17 which actually implement the new services by exchanging network control messages with the switched telephone network 18. The details of the service control point 17, along with its interaction with the switched telephone network 18, are detailed in the aforementioned copending application of J. O. Boese et al. Since the structure and operation of the service control point 17 and the switched telephone system 18 comprise well-known telephone facilities, they will not be further described here. Sufficient to note that these elements are able to implement telephone network service primitives which can be utilized to realize telephone services and which are similar or identical to those disclosed in the aforementioned J. J. Bernardis and S. M. Lin patents and BSDB publication. 
     Associated with the services management system 14 is a customer data base 16 which contains detailed information concerning the customers utilizing telephone network 18. Also associated with services management system 14 is a further computer workstation 15 which can be used to add customer preferences and other customer specific data to the call processing record templates defined in store 19. This addition of the customer specific data to a call processing record template is called &#34;service provisioning&#34; and permits the service templates passed to service control point 17 to be customized for a particular customer or set of customers using network 18. Workstation 15 can, of course, be combined with workstation 10 if the two workstations are at the same location. 
     The workstations 10 and 15 can be any modern workstation supporting graphical manipulation capability. One such workstation is the SUN 3/160 terminal running under the SUN operating system and using the SUNVIEW® graphics environment. This environment provides window support, mouse control, and graphic creation and manipulation capability adequate to implement the present invention. Many other modern workstations, however, would likewise support implementations of the present invention. 
     The present invention will be better understood by considering the flowchart of FIG. 2. In FIG. 2 there is shown a flowchart of the process for designing and deploying new services for telephone subscribers in accordance with the present invention. Three major steps are involved, node definition, service definition and call processing record creation. These steps will be taken up individually below. 
     The intended user of the process of FIG. 2 is the service creator, typically the telephone service provider. As suggested in box 20 of FIG. 2, this person must create the nodes to be used in new services. The new nodes are created dynamically by specifying the following properties of the new node. 
     1. Node Name 
     2. Node Type 
     3. Data Type 
     4. Node Rules 
     5. &#34;Other&#34; Allowed 
     6. Node Error Message 
     7. Notes 
     As is shown in detail in FIG. 3, a node definition screen can be used to capture the node properties as data items. The &#34;Load,&#34; &#34;Validate,&#34; &#34;Store,&#34; &#34;Delete,&#34; &#34;Browse,&#34; &#34;Help,&#34; and &#34;Quit&#34; command buttons are utilized to access and process nodes as entities. The data acquisition fields are used to define new nodes by specifying the node name and the node properties. Using these properties, a node can be administered by the service management system 14 of FIG. 1 and implemented by the service control point 17 of FIG. 1 without the necessity of writing new service implementing code. As illustrated in FIG. 3, the user is presented with an on-screen form which requires that the user specify the values for each of these properties. The cursor initially is located at the first data field (NODE NAME:) and advances to successive data fields as the &lt;enter&gt; or &lt;return&gt; key is depressed. Once these properties have been specified, the user can store the completed node definition for the newly created node in a node library in store 12 (FIG. 1), using the command keys identified in the top portion of the screen display of FIG. 3. 
     The properties captured by the node definition screen of FIG. 3 contain key information about the new node and, when necessary, can be translated and sent to the service control point 17 of FIG. 1 to drive a generic Call Processing Record (CPR) interpreter (such as that disclosed in the aforementioned Bernardis patent), so that it can support the use of this new node in any call processing records that are created and provisioned for services. Additional or supplemental properties, such as associated service control point call variables, node connection rules and node translation rules, can be added to the node library at a later time to completely characterize the meaning and intent of these operations at a particular services management system 14 and a particular service control point 17 (FIG. 1) in a generic manner. More particularly, a specific identification of the service implementing primitive in one or more service implementing network components which can be used to realize the node can be explicitly added to the node definition. The presence of such an identification of the actual code sequence in the service control point would substantially simplify the design of the interpretor program which translates the call processing record into actual service implementation. In this sense, the nodes become elements of an extendible, high level programming language for specifying telephone services. 
     In response to the NODE NAME prompt, the user supplies any unique name chosen for the new node. This name will hereafter be used to identify the node. This new node name can be thought of as a higher-level abstraction representing a specific operation using pre-defined call processing variables. Nodes can be either decision nodes or action nodes. The following node types, supplied in response to the NODE TYPE prompt, are possible: 
     
                       TABLE 1______________________________________NODE TYPESACTION             DECISIONNODES              NODES______________________________________Assignment Action  Branch DecisionBoolean Operation Action              Integer DecisionCollect Action     Percent DecisionConnect Action     String DecisionConcatenate ActionCPR Access ActionDiagnostic ActionReturn ActionTable Access ActionTemporary Hand Over ActionTerminate Action______________________________________ 
    
     The node type selected provides information that can be used during call processing record validation and call processing record code generation. These node types correspond to all of the basic types of actions and decisions that might be utilized in providing telephone special services. They are already programmed or programmable into prior art service implementing network components such as service control point 17. Should a new type of node be required, however, it is necessary to specify the new type, and to provide generic implementation of the activity of the new node type in the service control point 17. 
     The node types have particular meaning to service control point 17, which must execute the call processing record in real time. Specifically, the node type informs service control point 17 what functions or call primitives are to be invoked. These node types thus represent the &#34;programmed capabilities&#34; of service control point 17, which, when combined with the node name, representing a particular pre-defined call variable in the service control point call processing execution environment, enable service control point 17 to actually perform the requested operations using the correct data. 
     The DATA TYPE field specifies the format of the data that will be acceptable as input values for this node when this node is used in a call processing record. The data formats allowed are decimal numbers, alphanumeric text, telephone numbers, trunk identifiers, variable data, and billing information. The data type is used during call processing record validation at the time the call processing record is &#34;provisioned&#34; by the specification of customer-dependent data values. 
     To administer a call processing record, services management system 14 of FIG. 1 must be able to determine whether valid values have been entered for the nodes in the call processing record tree. Therefore the user must specify the rules to be used when validating the input values for this node when this node is used in a call processing record. In accordance with the present invention, a regular expression can be used to represent the validation rules. Moreover, such validation rules can be entered dynamically in the node definition as opposed to hard coding them in a program. For example, to specify the validations for a queuing node, the user can specify the regular expression &#34; (lifo|fifo)$&#34;. This expression states that the node can accept either &#34;last in, first out&#34; or &#34;first in, first out&#34; queue behavior as input values. 
     In response to the OTHER ALLOWED, prompt, the user must specify whether the node can accept the word &#34;other&#34; as an input value. For example, if a day of the week node were defined and available for a particular service, a call processing record would be constructed with the day of the week node in the tree. If the input values for the day of the week node were specified as &#34;Monday and Tuesday,&#34; then a second branch would need to be created to cover what should be done on Saturday, Sunday, Wednesday, Thursday and Friday. Rather than spell out the remaining days, the string &#34;other&#34; could be used. For some nodes &#34;other&#34; is not a sensible value. Therefore, during node definition, the user must indicate whether &#34;other&#34; is a valid input value or whether entering &#34;other&#34; should result in a validation error. 
     In response to the NODE ERROR MESSAGE prompt, the user enters a string to be printed when an inappropriate input value is specified for a node during the provisioning of a call processing record. This allows &#34;on the fly&#34; validation of data entries during all succeeding uses of this node definition. 
     The NOTES prompt permits a convenience field for the user. It can be used to note limitations on the node behavior, a general functional description of the node or any other information the user wishes to associate with the node definition. 
     Also shown at the top of screen 30 of FIG. 3 are a series of command light buttons labeled &#34;Load,&#34; &#34;Validate,&#34; &#34;Store,&#34; &#34;Delete,&#34; &#34;Browse,&#34; &#34;Help,&#34; and &#34;Quit.&#34; These command buttons are operated, for example, by a mouse-driven cursor, to accomplish the associated screen display control functions. For example, &#34;Load&#34; will load any particular previously existing node definition (e.g., for editing) simply by giving the node name and evoking the &#34;Load&#34; command. Similarly, &#34;Validate&#34; performs the validation on the data entries made in response to the prompts. &#34;Store&#34; stores the newly defined node in the node library 12 of FIG. 1. The &#34;Delete&#34; command deletes the identified node definition from library 12. &#34;Browse&#34; allows the user to browse through all of the previously defined nodes, &#34;Help&#34; provides screens of useful ancillary information likely to be of assistance to the user during the node definition activity, and &#34;Quit&#34; allows the user to terminate the node definition activity. The implementation of these so-called &#34;command buttons&#34; are well-known in the art and will not be further described here. 
     Returning to FIG. 2, the second box 21 represents the activity of defining a new service in terms of previously defined nodes. In this context, a &#34;record&#34; is a service definition and box 21 includes &#34;Load,&#34; &#34;Validate&#34; and &#34;Store&#34; commands for these service definition records. In addition, box 21 includes &#34;Canvas&#34; commands. These commands permit the visual and graphical manipulation of previously defined nodes into service definitions. As can be better seen in FIG. 4, the left half of the screen 40 is the drawing area where visual representations of previously defined nodes can be assembled into service definitions. The &#34;Canvas&#34; commands include &#34;Clear&#34; (to clear the canvas area), &#34;Draw&#34; (to prepare for manipulating items on the canvas), &#34;Help&#34; (to obtain screens of useful information to assist in the use of the system), and &#34;Quit&#34; (to terminate the service definition session). In addition, individual items in the canvas area can be manipulated with the commands &#34;Select&#34; (to select a particular node), &#34;Add&#34; (to add a selected node to the service definition), &#34;View&#34; (to view the node definition of the selected node), and &#34;Delete&#34; (to delete a node from the service definition). 
     The intended user of the service definition process is the service creator. This creator utilizes the service definition process to define the subset of nodes in the node library that are to be used in a specific service. The user is presented with the form shown in FIG. 4 which enables the user to specify the nodes from the node library that are allowed for use by a specific service with a certain qualifier. A qualifier could, for example, be a specific area of service in the service provider&#39;s territory. With the functions described above, the use of any particular node in a service can be defined by a service creator and administered by the service management system 14. Once the allowable node names for a particular service have been specified, using the screen 40 of FIG. 4, the user can store the service definition for the new service in service definition library 13 (FIG. 1). These service definitions can thereafter be edited, augmented or deleted from the service definition library 13 whenever desired. 
     The service creation user can distribute the node library and the service definition library in store 13 to the generic service management system 14 for use in administering the new service. Services management system 14 will permit the use of only the specified subset of nodes in all call processing records that are created and provisioned for this particular service. Additional properties, such as service-specific node connection rules and node translation rules, can be added to the service definition tables at this time to completely and generically characterize the meaning and intent of these operations for the service management system 14. 
     Returning to FIG. 2, the box 22 represents the procedures for &#34;provisioning&#34; the service defined in box 21. In this regard, the term &#34;provisioning&#34; means creating the logic tree representing the new service and customizing the defined service in terms of node parameter values. The screen 50 of FIG. 5 illustrates a mechanism for carrying out this process. The service creator can use this process to define a default representation of the service offering as a template of nodes interconnected in a call processing record tree format. The allowed nodes for a particular service are the ones specified through the service definition process. The service provisioning user can use this process to customize the default service template and to provision the service with node parameter values. The user is presented with the visual programming tool illustrated in FIG. 5 to enable a graphical, user-friendly specification and input of the appropriate service customization and provisioning information, based on service, qualifier and customer key information. The qualifier could be, for example, a specific area of service in the service provider&#39;s territory. The screen of FIG. 5 provides record manipulation functions (Load Record, Validate Record, Store Record, and Translate Record), node manipulation functions (Place, Connect, Move, Edit, Disconnect, and Remove), and draw commands (Select, Clear, Help, Quit, and Redraw). 
     With the above described functions, the user can define a service template of nodes interconnected in a call processing record tree format as a default representation of the service offering. Furthermore, the true power of the present invention becomes evident when it is realized that the service creator can define modular templates of common reusable node-based logic as service features, which can then be added to the node library as nodes for reuse by other features and services. In effect, the present invention provides a mechanism for using the set of &#34;programmable capabilities&#34; available at the service control point 17 and define reusable, user-friendly and high-level modules that enable easier and faster visual programming of the call processing logic. 
     It should be noted that assemblies of low level nodes can be associated together into a higher level capability which, once given a name, can be retrieved, manipulated and used in creating new services just like a low level node. In this way, as time proceeds, the creation of new services becomes easier and easier since ever higher levels of service primitives become available for assembly into the new services. 
     Once the default service template has been specified, the user can store the service template definition for the new service in service template definition store 19. The user can thereafter distribute these service template definition tables to the generic services management system 14 for use in administering the new service, providing a default service logic flow for the purpose of provisioning. Furthermore, the availability of service node definitions in store 13 will ensure that provisioning will support the use of only the creator-specified subset of nodes in any call processing records that are customized and provisioned for this particular service. 
     The service provider or the subscriber can also use the process illustrated in FIG. 5 to customize the default service template and to provision the service by providing node parameter values. At this stage, the node values supplied are validated dynamically by invoking the node validation rules specified for each node name in the node library. Additional node and service definition properties, such as node connection rules and node translation rules, can be specified to drive the validation and translation operations at the services management system 14 in a generic manner. 
     The attached Appendix provides psuedocode for implementing the flowchart of FIG. 2. With this pseudocode and the description herein provided, any person of ordinary skill in the programming art is able to fully implement the present invention. 
     It should also be clear to those skilled in the art that further embodiments of the present invention may be made by those skilled in the art without departing from the teachings of the present invention. 
     
         ______________________________________APPENDIXPseudocode______________________________________Node Definition Process Pseudocodeinvoke (&#39;node.sub.-- definition&#39;)do until (invoke (&#39;quit&#39;)) if (view (node.sub.-- definition))  then input (node.sub.-- name)   invoke (&#39;load&#39;)   if (node.sub.-- definition (node.sub.-- name) in library    then    retrieve (node.sub.-- definition (node.sub.-- name))    display (node.sub.-- definition (node.sub.-- name))    else    create (node.sub.-- definition.sub.-- window (node.sub.-- name))    display (node.sub.-- definition.sub.-- window (node.sub.-- name))   endif   end.sub.-- invoke endif if (specify (node.sub.-- properties))  then   set.sub.-- default (field.sub.-- values (node.sub.-- name))   enter (field.sub.-- values (node.sub.-- name))  else   if (modify (node.sub.-- properties))    then update (field.sub.-- values (node.sub.-- name))   endif endif if (validation.sub.-- check (node.sub.-- name))  then   invoke (&#39;validate&#39;)    verify (node.sub.-- name, field.sub.-- entries, field.sub.-- entry.sub.--    combinations)   end.sub.-- invoke endif if (store (node.sub.-- definition))  then   invoke (&#39;store&#39;)    retrieve (node.sub.-- definition (node.sub.-- name))    overlay (node.sub.-- definition, node.sub.-- properties)    store (overlay (node.sub.-- name))   end.sub.-- invoke endif if (delete (node.sub.-- definition))  then   invoke (&#39;delete&#39;)    retrieve (node.sub.-- definition (node.sub.-- name))    delete (node.sub.-- definition (node name))   end.sub.-- invoke endif if (browse (node.sub.-- definition)  then   invoke (&#39;browse&#39;)    display (node.sub.-- properties)    retrieve (node.sub.-- definitions)    display (node.sub.-- definitions)   end.sub.-- invoke endifend.sub.-- doService Definition Process Pseudocodeinvoke (&#39;service.sub.-- definition&#39;)do until (invoke (&#39;quit&#39;)) if view (service.sub.-- definition)  then   input (service.sub.-- name, service.sub.-- qualifier)   invoke (&#39;load&#39;)    retrieve (service.sub.-- definition (service.sub.-- name,service.sub.--    qualifier))    display (node.sub.-- name.sub.-- list)   end.sub.-- invoke endif if view (all.sub.-- nodes)  then   invoke (&#39;select&#39;)    generate (menu (all.sub.-- nodes))   end.sub.-- invoke endif if (select.sub.-- node)  then   invoke (&#39;select&#39;)    select (desired.sub.-- node, menu (all.sub.-- nodes))    display (desired.sub.-- node, current.sub.-- node.sub.-- display)   end.sub.-- invoke endif if use (current.sub.-- node)  then   invoke (&#39;add&#39;)    position (current.sub.-- node, canvas)    add (current.sub.-- node, service.sub.-- definition)   end.sub.-- invoke endif if disallow (current.sub.-- node)  then   invoke (&#39;delect&#39;)    select (current.sub.-- node)    delete (selected.sub.-- node)   end.sub.-- invoke endif if view (current.sub.-- node.sub.-- definition)  then   invoke (&#39;view&#39;)    select (current.sub.-- node)    display (node.sub.-- definition, current.sub.-- node)   end.sub.-- invoke endif if validate (service.sub.-- definition)  then   invoke (&#39;validate&#39;)    verify (field.sub.-- entries, service.sub.-- definition)    verify (field.sub.-- entry.sub.-- combinations, service.sub. --definitions)   end.sub.-- invoke endif if store (service.sub.-- definition)  then   invoke (&#39;store&#39;)    retrieve (service.sub.-- definition (service.sub.-- name,service.sub.--    qualifier))    overlay (service.sub.-- definition (service.sub.-- name,service.sub.-- qualifer), canvas.sub.-- nodes))    store (service.sub.-- definition (service.sub.-- name, service.sub.--qualifier))   end.sub.-- invoke endif if clear (canvas.sub.-- area)  then   invoke (&#39;clear&#39;)    clear (all.sub.-- nodes, canvas.sub.-- area)   end.sub.-- invoke endif if redraw (canvas.sub.-- area)  then   invoke (&#39;draw&#39;)    clear (all.sub.-- nodes, canvas.sub.-- area)    auto.sub.-- invoke (&#39;load&#39;)   end.sub.-- invoke endif end.sub.-- doCPR Input Process Pseudocodeinvoke (&#39;CPR.sub.-- input&#39;)do until invoke (&#39;quit&#39;) if view (existing.sub.-- CPR.sub.-- tree)  then   input (service.sub.-- name, qualifier.sub.-- name, customer.sub.--name)   invoke (&#39;load&#39;)    retrieve (node.sub.-- names (service.sub.-- name, service.sub.--qualifier))    retrieve (node.sub.-- definitions (node.sub.-- names)    retrieve (CPR.sub.-- tree (service.sub.-- name, service.sub.-- qualifier, customer.sub.-- name))    display CPR.sub.-- tree (service.sub.-- name, serice.sub.-- qualifer, customer.sub.-- name))  end.sub.-- invoke endif if view (allowed.sub.-- nodes (service.sub.-- name, service.sub.--qualifier))  then   invoke (&#39;select&#39;)    generate (menu (allowed.sub.-- node.sub.-- names))   end.sub.-- invoke endif if select (allowed.sub.-- node)  then   invoke (&#39;select&#39;)    identify (desired.sub.-- node)    display (desired.sub.-- node, current.sub.-- node)   end.sub.-- invoke endif if add (current.sub.-- code, CPR.sub.-- canvas)  then   invoke (&#39;place&#39;)    position (current.sub.-- node, CPR.sub.-- canvas)    place (current.sub.-- node, CPR.sub.-- canvas)   end.sub.-- invoke endif if connect (node.sub.-- name1, node.sub.-- name2, CPR.sub.-- canvas)  then   invoke (connect)    select (from.sub.-- node)    select (to.sub.-- node)    draw.sub.-- line (from.sub.-- node, to.sub.-- node   end.sub.-- invoke endif if move (node.sub.-- name)  then   invoke (move)    erase (node.sub.-- name, old.sub.-- location    redraw (connections, old.sub.-- location, new.sub.-- location)   end.sub.-- invoke endif if edit (node.sub.-- name.sub.-- node.sub.-- value)  then   invoke (&#39;edit&#39;)    select (node.sub.-- name)    display (edit.sub.-- menu)    input (node.sub.-- value)    invoke (&#39;enter&#39;)erase (old.sub.-- value)display (new.sub.-- value)    end.sub.-- invoke   end.sub.-- invoke endif if disconnect (node.sub.-- name)  then   invoke (&#39;disconnect&#39;)    select (node.sub.-- name)    erase.sub.-- connection (node.sub.-- name, node.sub.-- parent)   end.sub.-- invoke endif if remove (node.sub.-- name)  then   invoke (&#39;remove&#39;)    select (node.sub.-- name)    remove (node.sub.-- name, children, connections)   end.sub.-- invoke endif if validate (CPR.sub.-- node)  then   invoke (&#39;validate&#39;)    for (each node in CPR.sub.-- tree)    dovalidate (node.sub.-- value, node.sub.-- rule)    end.sub.-- do    display (error.sub.-- messages)    correct (node.sub.-- values, connections)   end.sub.-- invoke endif if store (CPR.sub.-- tree)  then   invoke (&#39;store&#39;)    retrieve (CPR.sub.-- tree (service.sub.-- name, service.sub.--qualifier, customer.sub.-- name))    overlay (CPR.sub.-- tree (service.sub.-- name, service.sub.--qualifier, customer.sub.-- name), CPR.sub.-- tree (canvas.sub.-- area))    store (CPR.sub.-- tree, overlay)   end.sub.-- invoke endif if clear (canvas.sub.-- area)  then   invoke (&#39; clear&#39;)    erase (canvas.sub.-- area)   end.sub.-- invoke endif if redraw (canvas.sub.-- area)  then   invoke (&#39;redraw&#39;)    erase (canvas.sub.-- area)    auto.sub.-- invoke (&#39;load&#39;)   end.sub.-- invoke endifend.sub.-- do______________________________________