Confidentiality of context information 141 2. Context-Aware Security Policy Requirements 139 D. Security Policy and Context-Awareness 137 3. Context Awareness in Service Discovery 133 A. Impact of a DoS Attack for a Protected and non Protected System 129 4. Evaluation of the Impact of DoS Attacks on System Performances 128 1. Service Time Duration of a Request in the System 125 5. Average Number of Users in the System 124 4. Fault Tolerance and Crash Robustness 112 3. A Performance Analysis of Secure Service Discovery Solutions 111 A. Architecture for a Secure Distributed Registry-Based Service Discovery 106 H. Anonymizing Publish / Request Messages for the Service Discovery 104 G. Securing the Access to Distributed Registries 103 1. Algorithms for inter-registry Indexing and Data Retrieval 102 F. A Scalable Distributed Registry-Based Model 101 1. Secure Service Discovery with Distributed Registries 97 A. Secure Service Discovery Middleware 91 1. Algorithm for a Secure Centralized Service Discovery 90 F. Architecture for a Registry-Based Secure Service Discovery 89 E. Choosing a Service Discovery Policy 88 D. Securing Registry-Based Service Discovery 86 A. MAGICDRAW UML REPEATED ATTRIBUTE OFFLINEPrivate Key Generation: Online Vs Offline 77 3. Requesting Private Keys from an Online PKG 76 2. Algorithms for Decentralized Secure Service Discovery System 75 E. Applying Attribute Based Encryption 73 D. Enabling Secure Service Discovery with Attribute Based Encryption 72 1. Private Key Generation: Online Vs Offline 71 C. Securing Decentralized Service Discovery 69 A. Registry-less Architecture 67 Chapter II. Privacy Issues for the Service Discovery 67 4. Approaches Secure Service Discovery 66 1. Security Requirements for Service Discovery 64 H. Context Awareness and Service Discovery 59 G. Service Discovery in Ad-Hoc Networks 58 E. MAGICDRAW UML REPEATED ATTRIBUTE BLUETOOTHService Discovery Protocol (SDP): Bluetooth 57 8. Service Discovery Components Design 52 D. Security requirement in Pervasive Systems 46 H. Service Oriented Architecture (SOA) 44 D. In this paper, we explore the benefits provided by using the proof construction approach to specify open distributed System in the enterprise viewpoint focusing on the specification of actions and the behavioral policies conditioning them.Ībstract 5 Table of Contents 31 List of Figures 35 List of Tables 37 List of Publications 38 Introduction 41 A. The Event-B method is being defined as a formal notation. An important point to take into account is the incorporation of the many proofs which have to be performed in order to be sure that the final system will be indeed "correct by construction". Formal notations provide precise and unambiguous system specifications. The use of formal methods in the design process of ODP systems is explicitly required. The enterprise viewpoint focuses on the roles and policies on the enterprise that the system is meant to support. Each viewpoint language defines concepts and rules for specifying ODP systems from the corresponding viewpoint. The Reference Model for Open Distributed Processing (RM-ODP) defines a framework for the development of Open Distributed Processing (ODP) systems in terms of five viewpoints: information, enterprise, computational, technology and engineering.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |