Communication

Communication
Chapter 2
Kyung Hee University
1/63
Agenda
1-Layered protocols 2-Remote Procedure 3-Remote Object Invocation 4-Message-Oriented Communication 5-Stream-Oriented Communication
2/63
1 - Layered Protocols
3/63
OSI Model
-OSI: Open Systems Interconnection
-Developed by the International Organization for Standardization (ISO) -Provides a generic framework to discuss the layers and functionalities of communication protocols.
Layers, interfaces, and protocols in the OSI model.

4/63
OSI Model (con.t)
2-2
A typical message as it appears on the network.

Kyung Hee University 5/63
OSI Protocol Layers

-Physical layer
+Deals with the transmission of bits +Physical interface between data transmission device (e.g. computer) and transmission medium or network Concerned with: Characteristics of transmission medium, Signal levels, Data rates
-Data link layer:

+Deals with detecting and correcting bit transmission errors +Bits are group into frames +Checksums are used for integrity
6/63
OSI Protocol Layers (con.t)

Discussion between a receiver and a sender in the data link layer.
7/63

-Network layer: +Performs multi-hop routing across multiple networks +Implemented in end systems and routers -Transport layer: +Packing of data
assign each one a sequence number and then send them)
+Reliable delivery of data (breaks message into pieces small enough, +Ordering of delivery Examples: TCP (connection-oriented) UDP (connectionless) RTP (Real-time Transport Protocol)
8/63

Client-Server TCP protocol
(a) Normal operation of TCP. (b) Transactional TCP.


-Session layer +Provide dialog control to keep track of which party is talking and it provides synchronization facilities -Presentation layer +Deals with non-uniform data representation and with compression and encryption -Application layer +Support for user applications e.g. HTTP, SMPT, FTP
10/63
Middleware Protocols
-Support high-level communication services -The session and presentation layers are merged into the middleware layer, Ex: Microsoft ODBC (Open Database Connectivity), OLE DB
An adapted reference model for networked communication.

2 - Remote Procedure Call
12/63
Remote Procedure call

-Basic idea: To execute a procedure at a remote site and ship the results back. -Goal: To make this operation as distribution transparent as possible (i.e., the remote procedure call should look like a local one to the calling procedure).
Example: read(fd, buf, nbytes)
13/63
Client and Server Stubs

Definition: Are additional functions which are added to the main functions in order to support for RPC
Client
count = doSomething();
Server
procedure doSomething();
Client Stub
Server Stub
OS
OS
14/63
Steps of a Remote Procedure Call

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Client procedure calls client stub in normal way Client stub builds message, calls local OS Client's OS sends message to remote OS Remote OS gives message to server stub Server stub unpacks parameters, calls server Server does work, returns result to the stub Server stub packs it in message, calls local OS Server's OS sends message to client's OS Client's OS gives message to client stub Stub unpacks result, returns to client
15/63
Passing Value Parameters (1)

2-8
Steps involved in doing remote computation through RPC

Passing Value Parameters (2)

In a large distributed system, multiple machine types are present Each machine has its own representation for number, characters, and others data items.
a) b) c)
Original message on the Pentium (little-endian) The message after receipt on the SPARC (big-endian ) The message after being inverted. The little numbers in boxes indicate the address of each byte
17/63
Parameter Specification
-Caller and callee agree on the format of message they exchange
Ex: word = 4 bytes float = 1 word character is the rightmost byte of word => the client stub must use this format and the server stub know that incoming message for foobar has this format
18/63
Asynchronous RPC (1)

-Avoids blocking of the client process. -Allows the client to proceed without getting the final result of the call.
2-12
a) b)
The interconnection between client and server in a traditional RPC The interaction using asynchronous RPC
19/63
Deferred Synchronous RPC(2)

One-way RPC model: client does not wait for an acknowledgement of the servers acceptance of the request.
2-13
A client and server interacting through two asynchronous RPCs

Example DCE RPC

-What is DCE ? (Distributed Computing Environment) DCE is a true middleware system in that it is designed to execute as a layer of abstraction between exiting (network) operating system and distributed application. -Goals of DCE RPC Makes it possible for client to access a remote service by simply calling a local procedure. -Components: +Languages +Libraries +Daemon +Utility programs +Others
21/63
Writing a Client and a Server

Generate a prototype IDL file containing an interface identify Filling in the names of remote procedure and their parameters IDL compiler is call to compile into three files
2-14
The steps in writing a client and a server in DCE RPC.

22/63
Binding a Client to a Server
2-15
Endpoint (port) is used by servers OS to distinguish incoming message
Client-to-server binding in DCE.

3-Remote Object Invocation
24/63
Distributed Objects (1)

Objects separate their actual implementation from their interface Distributed object = an object which publishes its interface on other machines Remote object = a distributed object whose state is centralized
25/63
Distributed Objects (2)
2-16
Common organization of a remote object with client-side proxy.

Binding a Client to an Object (1)
When a client binds to a distributed object, an implementation of the object interface (proxy) is loaded into the clients address space
27/63
Binding a Client to an Object (2)

Distr_object* obj_ref; obj_ref = ; obj_ref-> do_something(); (a) Distr_object objPref; Local_object* obj_ptr; obj_ref = ; obj_ptr = bind(obj_ref); obj_ptr -> do_something(); (b) //Declare a systemwide object reference //Declare a pointer to local objects //Initialize the reference to a distributed object //Explicitly bind and obtain a pointer to the local proxy //Invoke a method on the local proxy //Declare a systemwide object reference // Initialize the reference to a distributed object // Implicitly bind and invoke a method
a) b)
An example with implicit binding using only global references An example with explicit binding using global and local references Problems: + Language dependent + Address of server an Object reference
Parameter Passing (2)

Pass remote object by reference Pass local object by value Local object = an object in the clients address space
29/63
Parameter Passing (2)
2-18
The situation when passing an object by reference or by value.

stream
30/63
Example: Java RMI (1)

Java Distributed-Object Model
Distributed objects integrated into the Language Goal is to achieve transparency! (keep as much of semantics of nondistributed objects as possible)
31/63
Java RMI (2)

Local vs. Remote object differences when 1. Cloning:
proxies Cloning the actual object only, and not its
2. Synchronizing
Synchronized methods Only proxy synchronization is allowed only
32/63
Java RMI (3)

Any serializable object type can be a parameter to an RMI
Platform dependent objects (e.g., sockets, file descriptors,etc) are not serializable
Local objects are passed by value, remote objects are passed by reference Proxy can be used as a reference to a remote object: Possible to serialize the proxy and send it Kyung Hee University server to another
33/63
Java RMI (4)
stream
34/63
4-Message-Oriented Communication
35/63
Persistence and Synchronicity in Communication

General organization of a communication system in which hosts are connected through a network
+Each host is connected to a single communication server. +Hosts and communication servers can have buffers.
36/63

Persistent communication of letters back in the days of the Pony Express
37/63
Persistence and Synchronicity in Communication Definition

-Persistent vs. Transient
Persistent messages are stored as long as necessary by the communication system (e.g., e-mail) Transient messages are discarded when they cannot be delivered (e.g., TCP/IP)
-Synchronous vs. Asynchronous

Asynchronous implies sender proceeds as soon as it sends the message no blocking Synchronous implies sender blocks till the receiving host buffers the message
38/63
(a) Persistent asynchronous communication (b) Persistent synchronous communication

39/63
(c) Transient asynchronous communication (d) Receipt-based transient synchronous communication

(e) Delivery-based transient synchronous communication at message delivery (f) Response-based transient synchronous communication
41/63
Message-Orient Transient Communication

u Berkeley Sockets:
u Socket: a communication endpoint to which an application can write data (be sent to network) and read incoming data.
Primitive Socket Bind Listen Accept Connect Send Receive Close Meaning Create a new communication endpoint Attach a local address to a socket Announce willingness to accept connections Block caller until a connection request arrives Actively attempt to establish a connection Send some data over the connection Receive some data over the connection Release the connection
Socket primitives for TCP/IP

42/63

u Berkeley Sockets:
Create a new endpoint Associate endpoint Reserve buffer Block waiting for reqs
Automatic binding after connection
Connection-oriented communication pattern using sockets


u Sockets ware deemed insufficient because:
u Support only send and receive primitives u Designed for communication using general-purpose protocol stacks such as TCP/IP
u ->The Message-Passing Interface (MPI)

u Designed for multiprocessor machines and high-performance parallel programming u Provides a high-level of abstraction than sockets u Support diverse forms of buffering and synchronization (over 100 functions)
44/63

u The Message-Passing Interface (MPI)
Primitive MPI_bsend MPI_send MPI_ssend MPI_sendrecv MPI_isend MPI_issend MPI_recv MPI_irecv Meaning Append outgoing message to a local send buffer Send a message and wait until copied to local or remote buffer Send a message and wait until receipt starts Send a message and wait for reply Pass reference to outgoing message, and continue Pass reference to outgoing message, and wait until receipt starts Receive a message; block if there are none Check if there is an incoming message, but do not block
Some of the most intuitive message-passing primitives of MPI.

Message-Orient Persistent Communication

u Message-Queue Model
u Apps communicate by inserting messages in specific queues u Loosely-couple communication u Support for: u Persistent asynchronous communication u Longer message transfers (e.g., e-mail systems) Four combinations for loosely-coupled communications using queues.
46/63

u General Architecture of a Message-Queuing System
u Messages can only be put and received from local queues. u The message-queuing system is responsible for transmitting the messages between the source queues and destination queues, meanwhile storing the messages as long as necessary. u Each queue is maintained by a queue manager. Example
The relationship between queue-level addressing and network-level addressing.


u General Architecture of a Message-Queuing System
u Queue managers are not only responsible for directly interacting with applications but are also responsible for acting as relays (or routers).
Queue managers form an overlay network, acting as routers
48/63

u Generalpurpose System
u u u u
of
Message-Queuing
Enable persistent communication between processes Handling access to database Perform computation In wide range of application, include: -Email -Workflow -Groupware -Batch processing
49/63

u Message Brokers
The general organization of a message broker in a message-queuing system
end
50/63
5-Stream-Oriented Communication
51/63
52/63
* Relationship between substreams are also timedependent Kyung Hee University
53/63
Data Stream (1)

Setting up a stream between two processes across a network.
Setting up a stream directly between two devices.
54/63
Data Stream (2)
An example of multicasting a stream to several receivers.

Client Traffic Shaping
56/63
Specifying QoS (1)

Characteristics of the Input maximum data unit size (bytes) Token bucket rate (bytes/sec) Toke bucket size (bytes) Maximum transmission rate (bytes/sec) Service Required Loss sensitivity (bytes) Loss interval (sec) Burst loss sensitivity (data units) Minimum delay noticed (sec) Maximum delay variation (sec) Quality of guarantee
A flow specification. Question: who specifies the flow?

Specifying QoS (2)
The principle of a token bucket algorithm.
58/63
Resource ReSerVation Protocol (RSVP)

A transport-level control protocol
Used to provide QoS for continuous data streams by reserving resources {Bandwidth, buffers, and processing capacity} Issue: how to translate QoS parameters to resource usage?
2 ways to translate
RSVP translates QoS parameters into data link layer parameters
Data link layer provides its own set of parameters (as in ATM)
59/63
Setting Up a Stream (1)
The basic organization of RSVP for resource reservation in a distributed system.

60/63
61/63
62/63
63/63
64/63
Synchronization Mechanisms (1)
The principle of explicit synchronization on the level data units.

Synchronization Mechanisms (2)
2-41
The principle of synchronization as supported by high-level interfaces.

message
66/63
END OF CHAPTER 2
THANK YOU FOR JOINING US!


Communication

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Communication

Uploaded by

Copyright:

Available Formats

Communication

Kyung Hee University

Kyung Hee University

Kyung Hee University

Kyung Hee University

Layers, interfaces, and protocols in the OSI model.

OSI Model (con.t)

A typical message as it appears on the network.

OSI Protocol Layers

-Data link layer:

Kyung Hee University

OSI Protocol Layers (con.t)

Kyung Hee University

OSI Protocol Layers (con.t)

Kyung Hee University

OSI Protocol Layers (con.t)

(a) Normal operation of TCP. (b) Transactional TCP.

OSI Protocol Layers (con.t)

Kyung Hee University

An adapted reference model for networked communication.

2 - Remote Procedure Call

Kyung Hee University

Remote Procedure call

Example: read(fd, buf, nbytes)

Kyung Hee University

Client and Server Stubs

Kyung Hee University

Steps of a Remote Procedure Call

Kyung Hee University

Passing Value Parameters (1)

Steps involved in doing remote computation through RPC

Passing Value Parameters (2)

Kyung Hee University

Kyung Hee University

Asynchronous RPC (1)

Kyung Hee University

Deferred Synchronous RPC(2)

A client and server interacting through two asynchronous RPCs

Example DCE RPC

Kyung Hee University

Writing a Client and a Server

Kyung Hee University

The steps in writing a client and a server in DCE RPC.

Binding a Client to a Server

Endpoint (port) is used by servers OS to distinguish incoming message

Client-to-server binding in DCE.

3-Remote Object Invocation

Kyung Hee University

Distributed Objects (1)

Kyung Hee University

Distributed Objects (2)

Common organization of a remote object with client-side proxy.

Binding a Client to an Object (1)

Kyung Hee University

Binding a Client to an Object (2)

Parameter Passing (2)

Kyung Hee University

Parameter Passing (2)

The situation when passing an object by reference or by value.

Example: Java RMI (1)

Kyung Hee University

Java RMI (2)

Kyung Hee University