---
title: byte-oriented protocol
slug: byte-oriented-protocol
qid: Q5004612
snapshot: byte-oriented-protocol-570985-03d849f273c8e481
content_hash: 03d849f273c8e481dc34b1d4d65ca1145c7c62fc2f6f5d265a65f0a3d3957dde
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1374163875
tags: [131300176, 22928855, 22999498, 23468805, 24043274, 26382118]
---

# byte-oriented protocol

> [!note] Provenance
> Snapshot `byte-oriented-protocol-570985-03d849f273c8e481` · content root `03d849f273c8e481…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1374163875> · Licensed CC BY-SA 4.0

Byte-oriented framing protocol is "a communications protocol in which full bytes are used as control codes. Also known as character-oriented protocol." For example UART communication is byte-oriented. The term "character-oriented" is deprecated, since the notion of character has changed. An ASCII character fits to one byte (octet) in terms of the amount of information. With the internationalization of computer software, wide characters became necessary, to handle texts in different languages. In particular, Unicode characters (or strictly speaking code points) can be 1, 2, 3 or 4 bytes in UTF-8, and other encodings of Unicode use two or four bytes per code point.

Byte-oriented framing protocol is "a communications protocol in which full bytes are used as control codes. Also known as character-oriented protocol." For example UART communication is byte-oriented. The term "character-oriented" is deprecated, since the notion of character has changed. An ASCII character fits to one byte (octet) in terms of the amount of information. With the internationalization of computer software, wide characters became necessary, to handle texts in different languages. In particular, Unicode characters (or strictly speaking code points) can be 1, 2, 3 or 4 bytes in UTF-8, and other encodings of Unicode use two or four bytes per code point. ==See also== Bit-oriented protocol ==References==
