KR20040008102A - Control System for Home Appliance Network - Google Patents

Abstract

PURPOSE: A system for controlling a home appliance network is provided to implement an optimized home appliance network with a low price by realizing the network with the serial communication function of a low cost microcomputer. CONSTITUTION: A system for controlling a home appliance network includes a network, at least one home appliances and a network management device. The network operates in accordance with a predetermined control protocol. The home appliances are connected to the network. The network management device is connected to the network to control and monitor the home appliances. And, the control protocol includes an application layer for using the message, a network layer for using a predetermined packet, a data link layer and a physical layer.

Description

Home Appliance Network Control System

The present invention relates to a home appliance network control system, and more particularly, to an optimized home appliance network control system by applying a simplified and standardized protocol.

At present, home automation for automatically controlling home appliances in each home or remote is almost commercially available. In the early stages of home automation, each device was controlled separately using a telephone or an infrared ray, and there was no linkage between the devices, but now, a communication network is used to establish a network between home appliances and control the network. We are using a method that allows integrated management.

Many microcomputers currently applied to home appliances have a built-in serial communication function and are configured to communicate with other microcomputers or devices. Such microcomputers have various sizes of resources that can be used for communication, such as memory, depending on the characteristics of the product. In the case of multimedia products such as PC (Personal Computer) and TV or audio, a high-performance hardware specification is adopted to operate various basic functions, so a specification for a large amount of data and high speed communication is required.

On the other hand, refrigerators, washing machines, microwave ovens, lamps, gas alarms, stands or boilers are generally simpler than the functions of the PC or multimedia products described above. . In the case of home appliances employing such low-function microcomputers, basic remote control and operation status monitoring are the main communication targets. Therefore, a standard for communication using a small microcomputer resource is required.

However, in the case of communication protocols used or ongoing for the purpose of communication between home appliances, a separate communication module such as a modem is additionally installed in each device or used to use the high specification communication standards used in the PC or multimedia devices. It is attempting to modify some of the high specification communication standards.

The home appliance according to the prior art has to separately install a separate hardware communication module such as a modem for each device by applying a high specification communication standard used in a PC or a multimedia device. There is a problem of increased efficiency and cost.

Accordingly, the present invention has been made to solve the above-mentioned problems, and to provide a home appliance network control system that can satisfy the low cost / high efficiency characteristics of home appliances employing a low-function microcomputer used at home There is a purpose.

1 is a diagram illustrating a network of a home appliance.

2 is a view showing a communication structure between a master-slave master / slave combined device according to the present invention.

3 is a diagram illustrating a detailed configuration of a master-slave communication structure according to the present invention.

4 is a diagram illustrating a half duplex communication structure according to the present invention.

5 is a diagram illustrating a 1 request-1 response communication cycle.

6 is a diagram illustrating a communication cycle in case of a packet error.

7 is a diagram illustrating one request-multiple response communication cycle.

8 is a diagram illustrating one request communication cycle.

9 is a diagram illustrating a division form of a communication layer.

10 is a diagram illustrating an inter-layer packet communication structure.

11 is a diagram showing an entire packet structure.

12 is a diagram illustrating the structure of a request / notification packet.

13 is a diagram illustrating the structure of a response packet.

The home appliance network control system of the present invention comprises a network according to a predetermined control protocol, at least one or more home appliances connected to the network, and a network manager connected to the network for controlling and monitoring the existing home appliances. The control protocol includes at least an application layer using the message, a network layer using a predetermined packet, a data link layer and a physical layer.

In this case, the packet includes a header area including a header field for a function required for communication in the data link layer, a message header field for a function required for communication in the application layer, and a message field including the message. And a trailer area including a packet end (ELP) field indicating the end of the packet.

In addition, the header field includes a packet start (SLP) field indicating the start of a packet, a receiver address (RA) field indicating a receiver, a sender address (SA) field indicating a sender, and a packet length (PL) indicating a length of a packet. ) Field and a network layer control (NLC) field indicating control of the network layer.

In addition, the header field includes the fields sequentially.

The header area further includes a network code field.

The header field is 72 bits.

In addition, the packet start (SLP) field is 8 bits, the recipient address (RA) field is 16 bits, the sender address (SA) field is 16 bits, the packet length (PL) field is 8 bits, The Network Layer Control (NLC) field is 24 bits.

In addition, the NLC field may include a priority (SP) field indicating a priority regarding processing of the message, a packet header length (PHL) field indicating a length of a packet header, and a version of the control protocol. A protocol version (PV) field to indicate, a packet type (PT) field to indicate the type of packet, a transmission counter (TC) field to prevent duplication of the same message when a communication error occurs, and to prevent message duplication Packet number (PN) field.

The NLC field also includes the fields sequentially.

The priority (SP) field is 3 bits, the packet header length (PHL) field is 5 bits, the protocol version (PV) field is 8 bits, and the packet type (PT) field is 4 bits. The Transmission Counter (TC) field is 2 bits and the Packet Number (PN) field is 2 bits.

Also, the priority (SP) field is a first code for transmitting an emergency message, a second code for transmitting a large amount of data through message division, a third code for transmitting general data, and an event message. A fourth code for transmission is set, the first code is '0', the second code is '1', the third code is '2', and the fourth code is '3'.

In addition, the packet type (PT) field is set to a first code for a request packet, a second code for a successful response packet, a third code for a failed response packet, a fourth code for a notification packet, The first code is '0', the second code is '4', the third code is '5', and the fourth code is '8'.

In addition, the transmission counter (TC) field is set to a first code indicating the initial transmission time, the first code is set to increase by a predetermined size when the request for retransmission, the first code is '0', The size is '1'.

Further, the packet number PN is set to increase by a predetermined size each time a new packet is transmitted, and to maintain the previous value when retransmitting the same packet, and the size is '1'.

The message header field also includes a message length (ML) field, a message header length (MHL) field, and a message option (MO) field for extending the message set.

The message header field also includes the fields sequentially.

In addition, the message length (ML) field is 8 bits, the message header length (MHL) field is 8 bits, and the message option (MO) field is 8 bits.

The message field also includes a command code (CC) field and an argument (ARG) field.

The message field also includes the fields sequentially.

In addition, the command code (CC) is 8 bits, and the argument (ARG) field has a variable size according to the command code (CC).

The trailer area further includes a cyclic margin check (CRC) field for error detection.

In addition, the trailer area sequentially includes the cyclic margin check (CRC) field and the packet end (ELP) field.

In addition, the cyclic redundancy check (CRC) field is 16 bits, and the packet end (ELP) field is 8 bits.

Hereinafter, a preferred embodiment of a home appliance network control system according to the present invention with reference to the accompanying drawings in detail as follows.

First, referring to the network of the present invention, as shown in FIG. 1, multimedia device products such as TV and audio connected to an A / V network through a gateway connected to an external Internet network, a printer, a scanner, a PC camera connected to a PC network, etc. Its sub-products include products such as refrigerators, air conditioners, washing machines, vacuum cleaners, microwave ovens, humidifiers, lights, stands, and gas alarms, connected via a network manager to a living network. In this case, the network manager may be a separate management device or a user's PC.

Looking at such a home appliance network control system of the present invention.

First, the present invention is applied to the master (slave) method. In other words, all communication cycles are initiated by the master and terminated by the master device. Any device can be a master, but in order to do so, it must have a function to control the flow of data on a communication line and have information and control codes for products connected to a network. Therefore, only a device with a user interface function such as a PC is equipped with all the functions of the master, and other devices can only serve as masters of limited functions such as communication with a predetermined slave or communication by a simple control code.

In addition, while maintaining the basic master-slave communication method as described above, a device in which the master and the slave logically coexist so as to enable direct communication between devices, that is, peer-to-peer communication. That is, as shown in FIG. 2, a device (hereinafter, referred to as a P2P device) that is physically one device but logically independent of a master and a slave is defined.

All products connected to the network are based on P2P devices, but, as shown in FIG. 3, may be defined as master, slave, transmit only, or receive only due to the hardware characteristics of the product.

That is, the master has a function of starting and terminating communication with the corresponding slave when a communication start event occurs due to a change of state in the end user or device in order to start a new communication cycle.

In case of slave, it is always in standby state and cannot request communication from other device by itself.

In case of P2P device, the master and slave logically coexist inside (ie, hybrid device). When communication start event occurs due to end user or device internal status change, it acts as master and leads the communication cycle. After that, it operates as a slave and enters a standby state.

In the case of a transmission-only device, only a transmission is possible due to hardware characteristics. An infrared remote controller corresponds to this.

Receiving-only device is a device capable of receiving only due to the hardware characteristics, and this includes a product that is equipped with an infrared receiver and is operated by a battery.

Next, the home appliance network control system according to the present invention performs signal transmission in a half-duplex method using one bus, as shown in FIG. 4.

In other words, data is not received from another device at the time of transmission, and data is not transmitted to the other device at the time of reception. This is to minimize the use of memory for communication, and at the same time to correspond to a network composed of one bus using a serial communication function, such as the home appliance network of the present invention.

Therefore, both the master and slave can share the memory for transmission and reception. In the case of P2P devices, since the master and slave do not operate at the same time, the memory for transmission and reception can be shared as one. This eliminates the need for Interupt, which increases programming freedom on the product side.

Next, the home appliance network system according to the present invention performs communication in a one-cycle manner. The 1-cycle method may be divided into a 1 request-1 response method, a 1 request-multi response method, and a 1 request method.

In this case, the 1 request-1 response method is a method in which one master transmits only one packet to one slave and the slave receives one packet in response to the master, and the master receives and terminates it. And, as shown in FIG. 7, in the one request-multi-response scheme, one master transmits one packet to multiple slaves, and each slave transmits one packet in response thereto, and the master continues to wait for a response and then sets a predetermined maximum. The communication is terminated when the reception time elapses. As shown in FIG. 8, the one request method is a method in which one master transmits one packet to one or more slaves and terminates communication without waiting for a response. At this time, if there is data transmission composed of several packets, the master divides the packet into the size of the corresponding slave and transmits the data in one packet unit. Meanwhile, FIG. 6 illustrates a method in which a response is resent when a response error occurs in a slave and communication is terminated by receiving a response accordingly.

Next, the home appliance network control system according to the present invention has a protocol consisting of a physical layer, a data link layer, and an application layer.

In the case of the TCP / IP protocol currently used as an Internet protocol, the communication layer is divided into an application layer, a transport layer, a network layer, a data link layer, and a physical layer. Other protocols for home appliances or factory automation also include an application layer, a data link layer, and a physical layer, and additionally, a transport layer or a network layer. However, since the present invention is intended to correspond to the above-described communication method for home appliances of low specification, it has a communication layer consisting of only a physical layer, a data link layer, and an application layer, and loads of a microcomputer to fit into a master-slave method and a half duplex method. Minimize the physical and data link layers as much as possible and allocate a large portion of the product's operation to the application layer.

Referring to the detailed configuration of the above-described communication layer, as shown in FIG. 9, first, in the case of a slave, an application layer consisting of application software, message configuration, message execution, message combination, and message duplication check area, packet configuration, and packet transmission And a data link layer consisting of a CSMA / CD, a packet check, an address check, and a packet data receiving area, and a physical layer consisting of a UART. In this case, the physical layer may include an adapter selected when power line communication is used.

In the case of the master, the application layer consists of application software, message composition, message partitioning, and message combination areas, and data link consisting of packet configuration, packet transmission, packet transmission confirmation, CSMA / CD, packet check, address check, and packet data reception area. It consists of a layer and a physical layer consisting of a UART. The physical layer of the master may include an adapter that is selected when using power line communication like the slave.

At this time, the physical layer is configured to receive the bit signals on the communication line to form a packet or to send the packet received from the data link layer as a bit signal on the communication line.

The data link link layer configures a packet using data received from the application layer and transmits the packet to the physical layer, or processes the packet received from the physical layer and hands it over to the application layer. The data link layer has a slightly different role between the master and the slave. The master includes a process for ensuring packet transmission to the physical layer. The physical layer and the data connection layer have the same structure as the product acting as a slave.

The application layer consists of a message set and is responsible for interpreting and processing messages. In the product acting as a slave, the message includes methods such as load control and memory control, and in the master, the slave manages the slave or controls the entire network by using the result of processing the message. The application layer therefore contains different content for different products. The application layer of the master also includes a role of a transport layer that divides and transmits a packet when there is more data to transmit than one packet range, or combines and processes a packet when the divided packet is received. The distinction between transport layers is included in the application layer because the splitting and combining of packets is done only for a specific message and not all messages.

Such a packet communication structure between communication layers is shown in FIG. In other words, the application layer and the data connection layer are interfaced in a message unit, and the data connection layer and physical layer are interfaced in a full packet unit. When communicating between the data connection layer and the physical layer, each packet is communicated in a full packet unit so that the packet can be used as it is without having to configure a packet for each layer. However, since the length of the header to be added in the data connection layer and the physical layer is not known at the application layer, it is difficult to interface in the full packet unit. Instead, data to be transferred from the application layer to the data connection layer is transmitted in message units. The packet should contain all the information you want to communicate with, and it should be structured to cope with future extended communication.

As shown in FIG. 11, a packet basically includes a header area consisting of a packet header field and a field (field) for future packet function addition, a body consisting of a message header field, a future message function addition field, and a message field. It consists of a zone and a trailer zone.

The detailed configuration of the request / notification packet used in the master of the packet is composed of 8 bits of SLP indicating the start of the packet and 16 bits, as shown in FIG. Receiver address (RA), 16-bit Sander address (SA) for indicating the sender, 8-bit Packet Length (PL) for indicating the length of the packet, 3 bits Service Priority (SP) for indicating transmission priority, consisting of 5 bits, Packet Header Length (PHL) for indicating the length of packet header, and indicating the version of the protocol consisting of 8 bits. Protocol Version (PV), consisting of 4 bits, Packet Type (PT) to indicate packet type, consisting of 2 bits A Transmission Counter (TC) for indicating the number of transmissions, a Packet Number (PN) for indicating a new packet transmission consisting of 2 bits, a Message Length (ML) of 8 bits, The home appliance network control system, characterized by consisting of an 8-bit message header length (MHL) and an 8-bit message option (MO). An 8-bit Command Code (CC) and an Argument (ARG) with variable number of bits, 16-bit error check (CRC), and 8-bit ELP for marking the end of the packet. Including, it consists of minimum 17-byte and maximum 255-Byte. The packet may further include a home code (HC) for identifying homes formed of 8 bits. Here, the service priority (SP), the packet header length (PHL), the protocol version (PV), the packet type (PT), the transmission counter (TC) and the packet number (PN) are packets at the network layer. Fields for network layer control (NLC).

In addition, the response packet used by the slave is the same as the request / notification packet except that an 8-bit ACK / NAK is included in the body part as shown in FIG. 13.

SLP (0x02) is a field indicating the start of a packet and is a redundant field for detecting an error of the packet.

The receiver address RA is located in front of the sander address SA in order to early determine whether the receiver will continue to receive or ignore the packet when it begins to receive the packet. In order from the upper bit, 2Bit classifies the network type, 6Bit classifies products with independent functions such as washing machine and refrigerator, and the lower 8Bit class is allocated to distinguish each other when there are many products of the same type.

The packet length (PL) is composed of 1-byte that stores the number of bytes calculated from the home code to the ELP. After receiving the packet length (PL) data value, the receiver receives only this much data and processes subsequent steps. Therefore, the packet length (PL) value is used to know in advance the size of the buffer required for reception and to detect errors in the received packet data. That is, after reading the last byte of the packet, if the value is not ELP, it can be determined as a packet error.

Service Priority (SP) prioritizes messages that should be prioritized for transmission, such as packets that require an urgent message at the application layer, packets that have failed to be transmitted, or need to be retransmitted, or messages that are less important than normal communication. Field indicating the priority of transmission to perform / CD function. This field is meaningful when the adapter performing the CSMA / CD function can transmit according to priority. Otherwise, this field is ignored. The service priority value according to each communication case is as follows.

0: Retransmission due to collision or emergency

1: When sending bulk data through message segmentation

2: normal communication

3: Report network connection status (in case of conflict, Priority is kept at 3)

The packet header length (PHL) is a field for scalability of the packet header. When the extension field is added to the current packet header, the packet header length (PHL) is changed accordingly. If there is no change, it is 9 bytes and can be extended up to 32 bytes.

The protocol version (PV) is a 1 byte field indicating the version of the adopted protocol. Versions and subversions take values from 0 to 15 in order in which they are updated.

The packet type (PT) is a 4Bit field value specified when transmitting a packet, and is divided into a request packet, a response packet, and a notification packet. The response packet is divided into a successful response and a failed response. The master should be set to the request packet and the slave to the response packet. When the device operates only as a slave, it should only process request packets. The reason for splitting the response packet into two is to see only the packet type (PT) field in the packet header even if the data link layer does not know the message contents, and to retransmit the packet immediately without sending the packet to the application layer when the failed response is failed. Notification packets indicate packets that do not require a response. An arrayed packet is used to send a large amount of data at high speed when transferring all the data without sending a response to each packet. The nucleus value is as follows.

0: request packet

1 to 3: Reserved

4: Successful response packet

5: Failed response packet

6 to 7: Reserved

8: Broadcast Notification packet

9: Arrayed packet

10: End packet of arrayed data

11-15: Reserved

The transmission count TC is a 2Bit field value for preventing duplication of the same message when a communication error occurs. The master can resend up to 3 times if the received response packet contains a CRC error code, or if the received packet is a CRC error or a received byte time over. Initially, it is set to '0'. Increases by. The slave is always one transmission.

The packet number PN is also a 2Bit field value for preventing duplication of the same message when a communication error occurs. The master increments the packet number by 1 each time a new packet is transmitted, and maintains the same packet number when retransmitting the same packet. Therefore, the slave memorizes the packet number and the transmission address of the previous message, and if the same message is received again, the slave ignores the duplicate message and performs the difference if it is different. When the slave responds to the received message, the slave constructs a response packet by copying the packet number of the received message.

In this case, the home code (HC) is a code for logically classifying households configured with a network, and is used within the range of nucleus values 0x03 to 0xFE to distinguish each household, especially when a transmission line between households such as a power line is connected without distinction. do.

The message length (ML) is information for knowing this because the length of the message field is variable. Therefore, the application layer handles the length of the message field by looking at the message length.

The message header length (MHL) is a field for future expansion of the message field and may add a message header in the case of encryption of the message field, change of an application protocol, and the like.

The message option (MO) is a field for extending the message set, and can classify the message set by port. Message sets can be placed per port for version-up of message sets or compatibility with other application protocols.

The message consists of command code to request the master to perform a function, input parameters required to execute this command, and parameters sent to the master after the slave executes the command. In addition, it should be configured and defined to facilitate program work in 8-bit microcomputer. In other words, modular programming should be possible to easily reflect the message even if it is corrected. To do this, every message must have an independent function for each. This means that every message cannot contain a subordinate message, and there is no causal relationship between the routines in the S / W implementation. If the messages have functions that are independent of each other, the messages can be combined to extend the functions for controlling and monitoring the product. If the slave executes the command normally, the arguments sent to the master are {ACK + Return arguments}, otherwise it is {NAK + error code}. Each device can have up to 256 Commands and is included. Input Arguments and Return Arguments are determined according to the command code and the number of bytes.

The data format of Arguments is as follows.

boolean: 1Byte

char, unsigned char: 1Byte

int, unsigned int, short int, unsigned short int: 2 Byte

long, undigned long: 4Byte

string: Send and receive including NULL.

In addition, the following basic concepts are used to classify the Command code.

All products use 256 command codes (0x00 ~ 0xFF) independently, but the commands commonly used in all products use common code. Incorporate the product's functions into a generalized structure to facilitate item addition. All Command codes are classified as mandatory and optional. Essential are the basic information of the device and the commands necessary for communication. Functionally, it is divided into instantaneous command (indicated by I) and program command (indicated by P). Instant Command can be executed immediately by Slave and Program Command needs Sequence to execute. Command codes in the Algorithm Area are not specified by standard codes for all products. Since the same type of product can communicate using different algorithms depending on the model name or product manufacturer, different functions can be performed using the same command code. Therefore, all Command codes in this area should be given as a unique number of the product model and included as arguments. In addition, the message is a protocol for processing at the application layer. The structure of the message is different from that transmitted from the master and when the slave responds to the master. When transmitting from the master, it consists of a command code and an input argument (ARG) to perform it. The number of arguments and their data types depend on the Command code. When a slave receives one packet from the master, the message structure is divided into two types, one with an error and the other with no error. If there is no error in the packet received from the master and the command code is normally executed, the message structure consists of the command code, the ACK, and the result of performing the command code (ARG). The number and data types of the result arguments also depend on the Command code. If an error occurs in a packet received from the master, it consists of a command code, a NAK, and a packet error code. If the packet is normal but an error occurred during the execution of the command code, it consists of a command code, a NAK, and an error code.

CRC is a value that detects an error in a received packet or allows a receiver to detect a packet error in transmission. CRC is processed by 16-Bit, and its value is generated by using data from ELP to byte just before CRC field or error is detected.

ELP (0x03) is a communication character that indicates the end of a packet, and provides a method of detecting a packet error without using a CRC with a packet length field at the time of reception. That is, when receiving the byte length of the packet length, it can be determined as a packet error if the last byte is not ELP. In this case, the packet error check using the CRC may be omitted.

The present invention of such a configuration is a master-slave, 1-cycle and half-duplex communication system, and a low-function microcomputer serial used in home appliances by applying a simplified and standardized protocol compared to the conventional method. Since the network is implemented using a communication function, an optimized home appliance network can be implemented at low cost.

Claims (27)

A network according to a predetermined control protocol; At least one home appliance connected with the network; A network manager connected to the network for controlling and monitoring the home appliance, wherein the control protocol comprises an application layer using the message, a network layer using predetermined packets, a data link layer and a physical layer. A home appliance network control system comprising at least. The message of claim 1, wherein the packet includes a header area including a header field for a function required for communication at the network layer, a message header field for a function required for communication at the application layer, and the message. And a trailer area including a body area including a field and a packet end (ELP) field indicating the end of a packet. 3. The header field of claim 2, wherein the header field indicates a packet start (SLP) field indicating a start of a packet, a receiver address field indicating a receiver, a sender address field indicating a sender, and a length of a packet. And a packet length (PL) field and a network layer control (NLC) field indicating control of the network layer. 4. The home appliance network control system according to claim 3, wherein the header field includes the fields sequentially. The home appliance network control system according to claim 2, wherein the header area further includes a network code field. The home appliance network control system according to claim 2, wherein the header field is 72 bits. 7. The method according to claim 3 or 6, wherein the packet initiation (SLP) field is 8 bits, the receiver address (RA) field is 16 bits, the sender address (SA) field is 16 bits, and the packet length ( PL) field is 8 bits, and the network layer control (NLC) field is 24 bits. 4. The NLC field of claim 3, wherein the NLC field comprises a priority field indicating a priority regarding processing of the message, a packet header length field indicating a length of a packet header, and the control. A protocol version (PV) field indicating the protocol version, a packet type (PT) field indicating the type of packet, a transmission counter (TC) field for preventing duplicate processing of the same message when a communication error occurs, and message duplication A home appliance network control system comprising a packet number (PN) field for preventing processing. 9. The home appliance network control system according to claim 8, wherein the NLC field comprises the fields sequentially. 9. The method of claim 8, wherein the priority (SP) field is 3 bits, the packet header length (PHL) field is 5 bits, the protocol version (PV) field is 8 bits, and the packet type (PT) field Is 4 bits, the transmission counter (TC) field is 2 bits, and the packet number (PN) field is 2 bits. The method of claim 8 or 10, wherein the priority (SP) field is a first code for transmitting an emergency message, a second code for transmitting a large amount of data through message division, and for transmitting general data And a third code, the fourth code for transmitting an event message. The home appliance of claim 11, wherein the first code is '0', the second code is '1', the third code is '2', and the fourth code is '3'. Network control system. 11. The method of claim 8 or 10, wherein the packet type (PT) field is a first code for a request packet, a second code for a successful response packet, a third code for a failed response packet, and a notification packet. Household appliance network control system, characterized in that the fourth code is set for. The household appliance of claim 13, wherein the first code is '0', the second code is '4', the third code is '5', and the fourth code is '8'. Instrument network control system. 11. The method according to claim 8 or 10, wherein the transmission counter (TC) field is set to a first code indicating an initial transmission time, and the first code is increased and set by a predetermined size when requesting retransmission. Home appliance network control system. 16. The system of claim 15, wherein the first code is '0' and the size is '1'. The household electrical appliance according to claim 8 or 10, wherein the packet number (PN) is set to increase by a predetermined size each time a new packet is transmitted and to maintain the previous value when retransmitting the same packet. Network control system. 18. The system of claim 17, wherein the size is '1'. The home appliance network control according to claim 2, wherein the message header field comprises a message length (ML) field, a message header length (MHL) field, and a message option (MO) field for extending a message set. system. 20. The system of claim 19, wherein the message header field includes the fields sequentially. The home appliance network control according to claim 19, wherein the message length (ML) field is 8 bits, the message header length (MHL) field is 8 bits, and the message option (MO) field is 8 bits. system. 3. The home appliance network control system according to claim 2, wherein the message field includes a command code (CC) field and an argument (ARG) field. 23. The system of claim 22, wherein said message field comprises said fields sequentially. The home appliance network control system according to claim 22, wherein the command code (CC) is 8 bits and the argument (ARG) field has a variable size according to the command code (CC). 3. The home appliance network control system according to claim 2, wherein the trailer area further includes a cyclic margin check (CRC) field for error detection. 26. The system of claim 2 or 25, wherein the trailer area sequentially includes the cyclic margin check (CRC) field and the packet end (ELP) field. The home appliance network control system according to claim 2 or 25, wherein the cyclic redundancy check (CRC) field is 16 bits and the packet end (ELP) field is 8 bits.