PARLOG: parallel programming in logic
ACM Transactions on Programming Languages and Systems (TOPLAS) - The MIT Press scientific computation series
Concurrent Prolog: A Progress Report
Computer
The architecture of an active database management system
SIGMOD '89 Proceedings of the 1989 ACM SIGMOD international conference on Management of data
Conflicts in Policy-Based Distributed Systems Management
IEEE Transactions on Software Engineering
Conversion of control dependence to data dependence
POPL '83 Proceedings of the 10th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
Dependence graphs and compiler optimizations
POPL '81 Proceedings of the 8th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Towards A Role-Based Framework for DistributedSystems Management
Journal of Network and Systems Management
POLICY '02 Proceedings of the 3rd International Workshop on Policies for Distributed Systems and Networks (POLICY'02)
A proactive management algorithm for self-healing mobile ad hoc networks
International Journal of Network Management
Policy interoperability and network autonomics
WAC'04 Proceedings of the First international IFIP conference on Autonomic Communication
Hi-index | 0.00 |
We developed two rule-based building-block architectures, i.e., pipe-connection and label-connection architectures, for describing complex and structured policies, especially network QoS policies. This study focuses on the latter. The relationships or connections between building blocks are specified by the data flow and control flow between them. The data flow is specified by tags, including virtual flow labels (VFLs), which are data attached to “outside packets.” The control flow can be classified and specified by four control structures: concatenation, parallel application, selection, and repetition. We have designed fine-grained and coarse-grained building blocks and methods for specifying data flow and control flow in differentiated services (Diffserv), and implemented the coarse-grained ones in a policy server. Two cases of building-block use are described, and we concluded that there are five advantages of building-block-based policies, i.e., expressibility, uniform semantics, simplicity, flexibility, and management-task-oriented design. We also developed techniques for transforming building-block policies into executable ones, which are called policy division and fusion.