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
A short note on LAP-B:What is LAP-B Protocol | Blinki Blog - 2 GB FREE
Home > Data communication and Networking > A short note on LAP-B:What is LAP-B Protocol

A short note on LAP-B:What is LAP-B Protocol

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

LAPB (Link Access Protocol Balanced) is a data link layer protocol that manages communication and packet framing between DTE and DCE devices. LAPB is a bit-oriented protocol that ensures that frames are correctly ordered and error-free.

LAPB uses three frame format types:

Information (I) frame- These frames carry upper-layer information and some control information (necessary for full-duplex operation). I-frame functions include sequencing, flow control, and error detection and recovery. I-frames carry send- and receive-sequence numbers.

Supervisory (S) frames- These frames provide control information. They request and suspend transmission, report on status, and acknowledge the receipt of I frames. They do not have an information field.

Unnumbered (U) frames- These frames are not sequenced. They are used for control purposes. For example, they can initiate a connection using standard or extended windowing (modulo 8 versus 128), disconnect the link, report a protocol error, or similar functions.

fig23

Ø Flag- Delimits the LAPB frame. Bit stuffing is used to ensure that the flag pattern does not occur within the body of the frame.

Ø Address- Indicates whether the frame carries a command or a response.

Ø Control- Provides further qualifications of command and response frames, and also indicates the frame format (U, I, or S), frame function (for example, receiver ready or disconnect), and the send/receive sequence number.

Ø Data- Carries upper-layer data. Its size and format vary depending on the Layer 3 packet type. The maximum length of this field is set by agreement between a PSN administrator and the subscriber at subscription time.

Ø Frame check sequence (FCS)- Ensures the integrity of the transmitted data.

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