The main difference in distributed systems based on knowledge is the use of the service approach and ontologies in knowledge engineering. Semantic service acts as a software agent that regulates the interaction of all components of the system. Semantic service provides: semantic principle, which defines a formal description of information and allows you to define the following characteristics of services: scalability, semantic interoperability, formal models of services and ontologies; the principle of decision making; the principle of distribution, which allows you to aggregate the capabilities of several computing objects through cooperation. The communication and collaboration mechanism of the distributed systems based on knowledge covers the message transfer between services, information exchange between semantic service and distributed knowledge bases, and the semantic service behaviors in the entire process from request submission, request handle, to result return. The knowledge base is formed from three types of ontologies. The rules for recognizing performance problems are converted into ontology and the system knowledge base is placed. The working memory of a semantic service contains facts that correspond to simple events, composite events, and identified problems and recommendations. The algorithm for using semantic service is discussed in the article. To assess the performance of the SS attached, create an information system of two components: event trace generator and event trace analyzer.
Economic globalization and global networks have become the trend of world
development. Especially with the development of information technology and the
innovation of management theory, modern enterprises need to go beyond the boundaries of
traditional companies to achieve for a rapid and effective integration of resources on a
global scale, thus can produce high-quality products that meet the needs of the market
or provide services the customer need in a very short period of time [
In this case, a new distributed computer system in terms of development of modern
technologies put the emphasis on the properties of interoperability and scalability.
This direction is connected with the rapid growth of blockchain technology and the
Internet of things (IoT). As analysts predict that, by 2025, the share of block chain
apps will account for 10% of world gross domestic product [
At the moment in the literature there are a large number of definitions of the
concept of "distributed system". The most comprehensive definition proposed by AS
Tanenbaum [
On the one hand, DS are tools that allow solving a large number of complex tasks, most of which are not solved by other methods. DS can eliminate the main drawback of centralized systems - the limitations of increasing computing power. At the same time, the analysis revealed a number of problems that need to be solved. The limited use of DS is complicated by the use of equipment from different manufacturers with different types of architectures. Due to the wide variety of aspects of building computing systems, as well as the variety of existing operating systems, it becomes necessary to create methods for adaptive planning of distribution of flows in a distributed system, which will significantly speed up the processing of incoming requests for services and increase the overall system performance.
Modern representations of data are changing the ways and forms of
communication, production and consumption of information [
The formal model of the DKBS consists of a set of ontologies; lots of services; a set of events that describe the processes of the system; semantic service (SS); a set of composite services and knowledge base. The completeness and effectiveness of the system is determined by a multitude of ontologies. The main difference in DKBS is the use of the service approach and ontologies in knowledge engineering. SS acts as a software agent that regulates the interaction of all components of the system.
Software agents originally were discussed in the 70’s, and in the mid 90’s briefly
gained some momentum but then stalled. The ”software agent” term has found its
way into a number of technologies and has been widely used, for example, in artificial
intelligence, databases, operating systems and computer networks literature. Although
there is no single definition of an agent [
Decentralization and openness are inherent properties of multiagent systems (MAS). The technologies they provide are thus the right abstraction for developing Web-oriented applications. Moreover, different works have been proposed to use Semantic Web technologies (SWT) for representing various dimensions of MAS (e.g., interaction protocols, norms, organizations).
Consequently, recent research in MAS have seen an intensive use of Knowledge
representation together with increasing use of SWT. We envision that SWT will
ultimately play a central role in all parts of MAS. Thus far, work combining MAS and
SWT have only been concerned about addressing one dimension of MAS at a time.
Also, they were mostly tackling the agent [
The proposed architecture is based on services and is designed to support all the processes of the system life cycle. That is, the proposed architecture is meant to include all the concepts necessary to perform all activities related to the life cycle. We shall adopt a generic, knowledge-based architecture. The enterprise members are represented by autonomous agents, geographically scattered, which are able to cooperate to achieve a common business goal.
The various persons constituting the DKBS, in order to process distributed knowledge bases, assume the following roles: Knowledge Manager: is in the top of the hierarchy, and acts as a project manager, but in higher levels. It's like a knowledge strategist, cooperating, defining, and distributing the knowledge to coordinate all the other roles; Knowledge Provider: is the owner of human knowledge. It is typically an expert in the application domain, but could be another person in the organization who does not have the expert status; Knowledge Analyst: uses a range of methods and tools that make the analysis of a standard knowledge-intensive task relatively straightforward; Knowledge System Developer: is responsible for the design and implementation.
The developer must have a basic background of analysis methods. In knowledge system development, the main knowledge problems have been solved by the knowledge analyst. Therefore, this role must have some skills of software designers; Knowledge User: makes use, directly or indirectly, of a knowledge system. Its interaction with the knowledge base system is important for the project development and validation; Project Manager: manages the project, specially the knowledge engineer and the knowledge system developer.
In turn, the structure of the system based on knowledge, is shown in Fig. 1. The
main components are [
In addition to the agents representing the distributed knowledge base, a SS is introduced in the MAS community. This agent reacts by seizing deal opportunities present in the DKBS, and proceed thus to establish the corresponding virtual entities.
The principle of the Distributed Knowledge Base proposed in this paper is to depends on a number of ontologies that provide semantic principle: ontologies of events DKBS (Task Ontology); ontologies of services (Application Ontology); ontology specialized areas of data systems based on (Domain Ontology). (fig. 2).
DKBS can be represented as a model of interaction of the main artifacts: clients, services and SS. Each component in the system is associated with a specific ontology. SS provides: semantic principle, which defines a formal description of information and allows you to define the following characteristics of services: scalability, semantic interoperability, formal models of services and ontologies; the principle of decision making; the principle of distribution, which allows you to aggregate the capabilities of several computing objects through cooperation.
Considering all the types of ontologies [
Each ontology has its own expressive capabilities depending on their functional purpose. Ontology-oriented for subject area (Domain Ontology), describe the dictionary of terms concrete and formal set four end subsets: concepts, relations, axioms and interpretation functions. Task Ontology consists of a Glossary of terms, specialize tasks and actions in subject area. Every task has a different status and stages of its implementation. The main feature for all concepts of the ontology problem is the time. Application Ontology is the most specific ontology, in addition to all the basic concepts, contains specialized terms and instances subject area.
SS includes domain ontology and a set of modules to operate the services and their ontological description a lot of events we have formed as a set of claims that can be applied to DKBS and a set of axioms of their appearance. 4
In each interaction of the SS, the ontology functionality is necessarily preserved. Each function is characterized by the input (1) and output arguments (2). Correspondingly, each action SS (3) is characterized by a function of the work with the ontology, the values of its arguments when you call and the completion of the system.
f SS FAkIN ( fa1IN ,..., fakIN ); k 1,..., K.
f SS FAnOUT ( fa1OUT ,..., faKOUT ); k 1,..., K. aij { fk , FAvaliIN , FAval OjUT );i 1,..., K ; j 1,...K; fk F. (1) (2) (3)
In the DKBS, the communication and collaboration mechanism between services is a problem that must be well considered in the design of the SS structure. The communication and collaboration mechanism covers the message transfer between services, information exchange between SS and distributed knowledge bases, and the SS behaviors in the entire process from request submission, request handle, to result return. These procedures can be summarized as follows: SS deploys appropriate services on its local Knowledge Base, performs the registration on the knowledge bases; The retrieval request accesses the system periodically. SS gets retrieval requests and searches its Knowledge Base. SS returns the retrieval result to the system after the search finishes. The SS implies a classification and a sort order to the retrieval result according to its corresponding retrieval request. User views the retrieval results on the interface and selects the needed Knowledge.
With the information about the Knowledge Base embedded in the retrieval result, the user then contacts the relevant enterprise to obtain the Knowledge.
The principle of operation of the SS is illustrated in Fig. 3. The knowledge base is formed from three types of ontologies. The rules for recognizing performance problems are converted into ontology and the system knowledge base is placed. The working memory of a SS contains facts that correspond to simple events, composite events, and identified problems and recommendations. The algorithm for using SS to perform an analysis is as follows. The initial data is the sequence of events of the system, let's call it the trace. Trace contains simple events. E The algorithm processes the events of the route in the order of the time of their occurrence and performs the following cycle: 1. Read the next event from the trace E. 2. Convert it to the concept of ontology and add it to the working memory of the SS. 3. Start the SS. If the new event is a search query, then pick up the relevant answers in the knowledge base. For an indefinite concept of a simple event, the output engine consistently executes the rules for constructing composite events, for constructed fact-composite events, the rules for identifying performance problems. The result of triggering a SS can be: (a) adding a new fact-simple event to some of the constructed fact-composite events; (b) identification of fact-composite events of working memory for compliance or non-compliance with the performance problem; (c) delete or save a new event in the working memory; (d) search for a saved event. 4. Retrieve the search results from the working memory or offer recommendations to solve the problem. e f , et, EPval, t, d , cs , (4) where f F - action function; et - the type of event that sets its parameters et EP (ep1,..., epK ) ; EPval (v1,..., vK ) - event parameter values; t - time of the event; d - event duration; cs - service code.
The implementation scheme of the tracer generator is presented in fig. 4. The tracer generator consists of the following components: OntologyGenerator program converts messages into ontology concepts; library SM is designed to track messaging between services; library Timer provides functions for obtaining current system time with high accuracy; library TracerWriter saves simple events created by the tracer to a trace file.
Presumably all generator modules are implemented in the Java programming language.
The implementation scheme of the SS trace analyzer is shown in fig. 5. The trace analyzer consists of the following components: library UI implements the CC user interface. library TraceReader provides reading simple events from trace files. library Ontology implements event conversion to ontology concepts. library Query generates queries to the SS. Modern representations of data are changing the ways and forms of communication, production and consumption of information. The dominance of horizontal relations, structure-role of information decentralization of all types of data available at any time on every device. The user should not care about the specific technology used to provide computing capacity or data storage, so you can say that a user has some information about the remote resource. DKBS in order to study the data, their processing and use evolving technologies of the semantic web. The formal model of the DKBS consists of a set of ontologies; lots of services; a set of events that describe the processes of the system; SS, a set of composite services and knowledge base. The completeness and effectiveness of the system is determined by a multitude of ontologies. The main difference in DKBS is the use of the service approach and ontologies in knowledge engineering. SS acts as a software agent that regulates the interaction of all components of the system. SS provides: semantic principle, which defines a formal description of information and allows you to define the following characteristics of services: scalability, semantic interoperability, formal models of services and ontologies; the principle of decision making; the principle of distribution, which allows you to aggregate the capabilities of several computing objects through cooperation. The communication and collaboration mechanism of the DKBS covers the message transfer between services, information exchange between SS and distributed knowledge bases, and the SS behaviors in the entire process from request submission, request handle, to result return. The knowledge base is formed from three types of ontologies. The rules for recognizing performance problems are converted into ontology and the system knowledge base is placed. The working memory of a SS contains facts that correspond to simple events, composite events, and identified problems and recommendations. The algorithm for using SS is discussed in the article. To assess the performance of the SS attached, create an information system of two components: event trace generator and event trace analyzer.