23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Industrial Internet 56-3<br />

A systematic solution for this problem should develop specific application scenarios, clearly identify<br />

technical requirements for the intended application functions, the features of the system component<br />

where the function will be implemented, and the location where the component is implemented<br />

inside the system. This may lead to different combinations. For all relevant combinations, the technical<br />

details of the information flows have to be specified and the requirements for the technologies have to be<br />

refined. This establishes a list of criteria by which the technologies have to be evaluated.<br />

56.3 technologies<br />

It is obvious that an evaluation process as the one mentioned above is not possible without knowing<br />

<strong>communication</strong> paradigms and technologies in detail. The most common <strong>communication</strong> paradigm<br />

used by Internet applications is client–server <strong>communication</strong>. The server provides the data, while the<br />

client retrieves the data and displays it. Typically, confirmed services are used. The sequence can be<br />

described by the well-known service primitives (see Figure 56.2). The client issues the request by invoking<br />

the service at an appropriate service access point (SAP)—service primitive—. req—the server is<br />

informed by an indication (.ind), executes the service, and prepares the answer. The server passes the<br />

answer to the client as response (.rsp). Finally, the client gets the answer together with the confirmation<br />

(.cnf) from the service, and can now use the data. Thus, from an architectural point of view, a client layer<br />

and a server layer can be distinguished in Industrial Internet <strong>systems</strong>.<br />

A further specialization of the functional components involved in the <strong>communication</strong> scenarios leads<br />

to more sophisticated architectures. The separation of application and data leads to the well-known<br />

three-tier-architecture (Figure 56.3), which can be further subdivided concerning application logic,<br />

data source, and <strong>communication</strong> server component (Figure 56.4). All types of architectural examples<br />

can be found in <strong>industrial</strong> applications. Thus, for the different functions the components of the architecture<br />

have to provide, different technologies exist—all assembled within the term Internet Technologies.<br />

Internet technologies can be grouped by function. The following functional clusters can be distinguished:<br />

• Transport and <strong>communication</strong> related technologies<br />

• Technologies for information description and presentation<br />

• Technologies for server-side and client-side functions<br />

Client<br />

e.g., Web browser<br />

.req<br />

Request<br />

Client layer<br />

.cnf<br />

Server<br />

e.g., Web server<br />

Documents<br />

Server layer<br />

Response<br />

.ind<br />

.rsp<br />

Application<br />

FIGURE 56.2<br />

Basic architecture and <strong>communication</strong> paradigm of Industrial Internet applications.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!