Deprecated: Assigning the return value of new by reference is deprecated in /home/freehos1/public_html/blinki/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /home/freehos1/public_html/blinki/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /home/freehos1/public_html/blinki/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /home/freehos1/public_html/blinki/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /home/freehos1/public_html/blinki/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /home/freehos1/public_html/blinki/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/freehos1/public_html/blinki/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/freehos1/public_html/blinki/wp-includes/comment-template.php on line 0

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/freehos1/public_html/blinki/wp-includes/comment-template.php on line 0

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/comment-template.php on line 0

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /home/freehos1/public_html/blinki/wp-includes/comment-template.php on line 0

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/freehos1/public_html/blinki/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /home/freehos1/public_html/blinki/wp-includes/http.php on line 61

Strict Standards: Redefining already defined constructor for class SimpleGoogleSitemap in /home/freehos1/public_html/blinki/wp-content/plugins/simple-google-sitemap/simple-google-sitemap.php on line 46
X.25 Interface and related | Blinki Blog - 2 GB FREE
Home > Data communication and Networking > X.25 Interface and related

X.25 Interface and related

February 10th, 2011 Remo Leave a comment Go to comments

What is X.25 interface? Define DTE & DCE

The X.25 software and hardware allow the router to communicate over a public X.25 network. The X.25 network interface complies with CCITT 1980 and 1984 specifications for X.25 interfaces by offering multiplexed channels and reliable end-to-end data transfer across a WAN. Layer 1 X.25 defines the electrical and mechanical procedures for activating and deactivating the physical medium connecting the DTE and the DCE. This relationship is shown below:

dde

DTE: DTE or Data terminal equipment devices are end systems that communicate across the X.25 network. They are usually terminals, personal computers, or network hosts, and are located on the premises of individual subscribers.

DCE: DCE or Data circuit-terminating equipment are communications devices, such as modems and packet switches that provide the interface between DTE devices and a PSE (Packet-switching exchange), and are generally located in the carrier’s facilities.

Briefly describe multiplexing service of X.25. How flow control & error control is being achieved in X.25

Multiplexing of virtual circuits takes place at layer 3.The traditional approach to packet switching makes use of X.25, which not only determine the user network interface but also influences the internal design of the network. Today’s networks employ reliable digital transmission technology over high quality, reliable transmission links, many of which are optical fiber. Thus multiplexing of X.25 makes its more reliable & easily operable.

Flow control is generally based on the start & waits technique and is achieved by using an acknowledgement (ACK) for error free frames & a negative acknowledgement (Nak) for frames containing error. Ack0 & Ack1 are usually used alternately for detecting sequence errors, which are caused by either, duplicated or lost frames.

Error control is achieved by 16-bit CRC or FCS algorithm. In the event of an error frame, the sender retransmits the frame to the receiver.


  1. No comments yet.
  1. No trackbacks yet.
You must be logged in to post a comment.