Network system of conductive fiber area capable of role switching between network devices

Abstract

The present invention relates to a conductive fabric area network system. The conductive fabric area network system according to the present invention comprises: one main conductive fabric area network device having a plurality of nodes; and one or more sub-conductive fabric area network devices having a plurality of nodes. The respective network devices may be included in wearable devices different from each other, and communicate with each other by using at least one communication means of wired communication and wireless communication.

Description

A network system in the conductive fiber domain that allows role switching between network devices. The present invention relates to a network system in the conductive fiber region. One of the most exciting technological trends of the past decade has been the rapid development of wearable devices. From the first wearable computers like smartwatches to soft suits that help people walk again, smart textiles are beginning to appear as promising materials for creating wearable devices, such as stretch sensors that can track movement and detect body posture, or soft sensors for wearable robots and virtual reality. While body-area networks of wearable textiles still have challenges to overcome, they also have the potential to transform the way we live and work. Wired communications, such as conductive yarns or printed conductive inks, have been used in body-area networks since the late 2000s. However, wired communications have struggled with durability, data transmission rates, and cost as devices proliferate. Furthermore, integrating wireless communications into wearable devices could address these challenges. However, wireless channels can be vulnerable to eavesdroppers and interference, requiring robust protocols. Furthermore, establishing a wireless link between nodes requires each node's own battery, adding weight to the fiber per device. As the number of wearable devices increases and demand for smart services grows, it is crucial to develop protocols that simultaneously provide data and energy to reduce the number of cables and batteries per device and enhance security. Managing and controlling a network with multiple nodes on conductive fibers requires developing a conductive fiber area network protocol to exchange the necessary data and control commands. Additionally, conductive fiber area networks require robust system architectures and flexible designs that can adapt to new operating environments, standards, and markets. The purpose of the present invention is to provide a network system in a conductive fiber region capable of transmitting and receiving data through a conductive fiber layer. In addition, the present invention aims to provide a network system in a conductive fiber area, in which mutually disconnected parts of a garment including a conductive fiber network wirelessly transmit power and data to perform charging and data storage management, collect and store various information such as the physical condition of a garment wearer from a sensor connected to the conductive fiber network, and enable the wearer to check information or analysis results when necessary. The purpose of the present invention is not limited to the purposes mentioned above, and other purposes not mentioned will be clearly understood by those skilled in the art from the description below. A network system according to one embodiment of the present invention includes a main wired network device and a sub-wired network device. The main wired network device and the sub-wired network device communicate with each other using at least one of wired communication and wireless communication. In one embodiment of the present invention, the main wired network device and the sub wired network device may each be included in different wearable devices. In one embodiment of the present invention, the main wired network device may further include a power supply device. In this case, the main wired network device may wirelessly transmit power to the sub wired network device. In one embodiment of the present invention, the sub-wired network device may further include a capacitor using a conductive fiber layer as an electrode. In this case, the sub-wired network device may charge the capacitor with power received from the main wired network device, and transmit data to the main wired network device using the power charged in the capacitor. In one embodiment of the present invention, the capacitor may include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. In one embodiment of the present invention, the main wired network device includes a first master node and a repeater node, and the sub wired network device includes a second master node. The first master node transmits and receives data with the repeater node via a conductive fiber layer, and the repeater node wirelessly transmits and receives data with the second master node. In one embodiment of the present invention, the sub-wired network device may further include a slave node that collects sensor data. In this case, the slave node may transmit the sensor data to the second master node, and the second master node may wirelessly transmit the sensor data to the repeater node. In one embodiment of the present invention, data transmitted and received between the repeater node and the second master node may include an identifier of the main wired network device; an identifier of the sub wired network device; an identifier of a node that transmitted the data; and an identifier of a node that receives the data. In one embodiment of the present invention, the main wired network device may further include a power supply device. In this case, the first master node may transmit power supplied from the power supply device to the repeater node via a conductive fiber layer, and the repeater node may wirelessly transmit power to the second master node. In one embodiment of the present invention, the main wired network device may further include a power supply device. In addition, the sub-wired network device may further include a capacitor using a conductive fiber layer as an electrode. In this case, the first master node transmits power supplied from the power supply device to the repeater node through the conductive fiber layer, and the second master node charges the capacitor with the power received from the repeater node, and transmits data generated by the sub-wired network device to the repeater node using the power charged in the capacitor. In one embodiment of the present invention, the capacitor may include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. In one embodiment of the present invention, the repeater node may stop transmitting power to the second master node when the second master node transmits data to the repeater node. In one embodiment of the present invention, either or both of the main wired network device and the sub wired network device may be devices including a conductive fiber area network. And, a method for forming a connection between wired network devices according to one embodiment of the present invention includes a step in which a main wired network device wirelessly transmits a connection request message to a sub wired network device; a step in which the sub wired network device transmits a connection response message to the main wired network device; and a step in which the main wired network device transmits a connection acknowledgement message to the sub wired network device. In one embodiment of the present invention, the connection confirmation message may include an identifier of the main wired network device and a network identifier assigned by the main wired network device to the sub wired network device. In one embodiment of the present invention, the step of transmitting the connection request message may include a step in which a first master node included in the main wired network device transmits the connection request message to a second master node of the sub-wired network device through a repeater node of the main wired network device; and a step in which the second master node transmits the connection request message to a slave node of the sub-wired network device. In one embodiment of the present invention, the step of transmitting the connection response message may include a step in which the slave node transmits the connection response message to the second master node; a step in which the second master node transmits the connection response message to the repeater node; and a step in which the repeater node transmits the connection response message to the first master node. In one embodiment of the present invention, the step of transmitting the connection confirmation message may include a step in which the first master node transmits the connection confirmation message to the second master node via the repeater node; and a step in which the second master node transmits the connection confirmation message to the slave node. In this case, the connection confirmation message may include a node identifier assigned by the first master node to the slave node. And, a conductive fiber area network system according to one embodiment of the present invention includes one main conductive fiber area network device having a plurality of nodes and one or more sub-conductive fiber area network devices having a plurality of nodes. Each of the network devices is incorporated into a different garment or body mount and communicates with each other using at least one of wired and wireless communication means. And, a conductive fiber area network system according to one embodiment of the present invention includes a first wired network device equipped with a battery and a second wired network device equipped with a battery, wherein the first wired network device and the second wired network device communicate with each other using at least one communication means among wired communication and wireless communication, wherein the first wired network device and the second wired network device include a power supply device, wherein the first wired network device and the second wired network device determine one of the two devices as a main wired network device and determine the other device as a sub-wired network device through message exchange between the two devices, and wherein the main wired network device wirelessly transfers power to the sub-wired network device. A network system according to one embodiment of the present invention includes a first wired network device and a second wired network device. The first wired network device includes a first master node and a first repeater node, and the second wired network device includes a second master node and a second repeater node. The first repeater node and the second repeater node communicate via wireless communication. The first master node requests operation information for determining a main network from the second master node through the first repeater node and the second repeater node, and when receiving the operation information from the second master node, determines one of the first wired network device and the second wired network device as a main network device based on the operation information, and determines the other as a sub-network device. In one embodiment of the present invention, the operation information may be the remaining charge level of the battery mounted on the second wired network device. In this case, the first master node compares the remaining charge level of the battery mounted on the second wired network device with the remaining charge level of the battery mounted on the first wired network device, and determines the main network device based on the comparison result. In one embodiment of the present invention, the operation information may be the start time of operation of the second wired network device. In this case, the first master node compares the start time of operation of the second wired network device with the start time of operation of the first wired network device, and determines the main network device based on the comparison result. In one embodiment of the present invention, the repeater node of the main network device can wirelessly transmit power to the repeater node of the sub-network device. In one embodiment of the present invention, the repeater node of the sub-network device can transmit power to the master node of the sub-network device under the control of the master node of the sub-network device. In one embodiment of the present invention, the master node of the main network device can control the repeater node of the main network device not to transmit power to the repeater node of the sub-network device when data transmission is performed between the repeater node of the main network device and the repeater node of the sub-network device. In one embodiment of the present invention, the first wired network device may further include one or more first slave nodes. The first master node may adjust the impedances of the first master node and the first slave node in real time by applying a predetermined impedance matching technique when the first slave node is added to a network within the first wired network device. In one embodiment of the present invention, the impedance matching technique may be any one or a combination of a complex conjugate matching technique, an equal impedance matching technique, and a voltage maximization matching technique. In one embodiment of the present invention, the first wired network device and the second wired network device may be conductive fiber area network devices. A method of operating a network system according to one embodiment of the present invention is a method of operating a network system, comprising: a first wired network device including a first master node and a first repeater node; and a second wired network device including a second master node and a second repeater node, wherein the first repeater node and the second repeater node communicate with each other by wireless communication. The above operating method includes a step in which the first master node requests operation information for determining a main network from the second master node through the first repeater node and the second repeater node; a step in which the first master node receives the operation information from the second master node; and a main network device determination step in which the first master node determines one of the first wired network device and the second wired network device as a main network device and determines the other as a sub-network device based on the operation information. In one embodiment of the present invention, the operation information may be the remaining charge level of the battery mounted on the second wired network device. In this case, the main network device determination step may include the first master node comparing the remaining charge level of the battery mounted on the second wired network device with the remaining charge level of the battery mounted on the first wired network device, and determining the main network device based on the comparison result. In one embodiment of the present invention, the operation information may be the start time of operation of the second wired network device. In this case, the main network device determination step includes the first master node comparing the start time of operation of the second wired network device with the start time of operation of the first wired network device, and determining the main network device based on the comparison result. In one embodiment of the present invention, the operating method may further include a step of the repeater node of the main network device wirelessly transmitting power to the repeater node of the sub-network device. In one embodiment of the present invention, the operating method may further include a step of transmitting power by a repeater node of the sub-network device to a master node of the sub-network device under the control of the master node of the sub-network device. In one embodiment of the present invention, the operating method may further include a step of determining, by the master node of the main network device, whether data transmission occurs between a repeater node of the main network device and a repeater node of the sub-network device; and a step of controlling, by the master node of the main network device, the repeater node of the main network device not to transmit power to the repeater node of the sub-network device when data transmission occurs between the repeater node of the main network device and the repeater node of the sub-network device. In one embodiment of the present invention, the first wired network device may further include one or more first slave nodes. In this case, the operating method may further include: a step of the first master node checking whether the first slave node has been added to a network within the first wired network device; and a step of the first master node adjusting the impedances of the first master node and the first slave node in real time by applying a predetermined impedance matching technique when the first slave node has been added to a network within the first wired network device. In one embodiment of the present invention, the impedance matching technique may be any one or a combination of a complex conjugate matching technique, an equal impedance matching technique, and a voltage maximization matching technique. In one embodiment of the present invention, the first wired network device and the second wired network device may be conductive fiber area network devices. According to one embodiment of the present invention, multiple nodes on a conductive fiber network can be simply and efficiently controlled. Additionally, according to one embodiment of the present invention, a service can be provided to a multi-node and multi-conductive fiber area network through an effective communication-based time strategy mechanism. In addition, according to one embodiment of the present invention, wireless power transfer between multiple wearable devices is performed according to the battery status of the wearable devices, thereby efficiently operating power and thereby extending the usage time. The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below. Figure 1 is the superframe structure of CFAN. Figure 2 is a drawing showing the structure (physical elements) of CFAN. Figure 3 is a state diagram of CFAN-M. Figure 4 is a state diagram of CFAN-S. Figure 5 is a state diagram of CFAN-R. Figure 6 is a drawing showing a connection method of CFAN. Figure 7 is a drawing showing a connection method of an extended CFAN. Figure 8 is a drawing showing a separation method of CFAN. Figure 9 is a drawing showing a method for separating an extended CFAN. Figure 10 is a drawing showing a method for checking the connection status of CFAN. Figure 11 is a diagram showing a method for checking the connection status of an extended CFAN. Figure 12 is a diagram showing a data transmission method during the response section of CFAN. Figure 13 is a diagram showing a data transmission method during the response section of the extended CFAN. Figure 14 is a diagram showing a data transmission method during an autonomous section of CFAN. Figure 15 is a diagram showing a data transmission method during an autonomous section of an extended CFAN. Figure 16 is a diagram showing a group ID setup method. Figure 17 is a diagram showing a method for setting up a group ID of an extended CFAN. Figure 18 is a diagram regarding the physical layer frame format. Figure 19 is a diagram regarding the preamble format. Figure 20 is a drawing regarding the header format. Figure 21 is a diagram of an encoder of a header check sequence. Figure 22 is a drawing regarding the payload format. Figure 23 is a diagram regarding the definition of NRZ-L encoding. Figure 24 is a diagram related to ASK modulation. Figure 25 is a diagram related to GFSK modulation. Figure 26 is a diagram of the encoding and modulation process of a preamble. Figure 27 is a diagram of the encoding and modulation process of the header. Figure 28 is a diagram of the encoding and modulation process of the payload. Fig. 29 is a diagram of a GFSK modulation signal. Fig. 30 is a diagram of an ASK modulation signal. Figure 31 is a planar electronic fiber design drawing. Figure 32 is a linear yarn design drawing. Figure 33 is a drawing showing an example of a CFAN design using parallel arranged conductive materials. Figure 34 is a block diagram showing the configuration of a network system according to the first embodiment of the present invention. Figure 35 is a block diagram showing the configuration of a network system according to the second embodiment of the present invention. Figure 36 is a flowchart for explaining an operation method of a network system according to a second embodiment of the present invention. Figure 37 is a block diagram showing a computer system for implementing a method according to an embodiment of the present invention. The advantages and features of the present invention, and the methods for achieving them, will become clear with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and these embodiments are provided only to make the disclosure of the present invention complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Meanwhile, the terminology used in this specification is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural unless specifically stated in the phrase. The terms "comprises" and / or "comprising" as used in the specification do not exclude the presence or addition of one or more other components, steps, operations, and / or elements mentioned. Terms including ordinal numbers such as first, second, etc. may be used to describe various components, but the components should not be limited by the terms. In this specification, terms including ordinal numbers are used only for the purpose of distinguishing one component from another, and terms including ordinal numbers should not be construed as indicating an order, sequence, ranking, status, rank, etc. based on a specific standard. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components in between. Conversely, when a component is referred to as being "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between. Other expressions that describe the relationship between components, such as "between" and "directly between" or "adjacent to" and "directly adjacent to", should be interpreted similarly. In describing the present invention, if it is determined that a detailed description of a related known technology may unnecessarily obscure the gist of the present invention, the detailed description is omitted. The following are definitions of key terms used in this specification. Definition of terms WPT (Wireless power transfer) A method of transferring power between devices without wires using electromagnetic fields. CFAN (Conductive fabric area network) A network that provides reliable communication using conductive fibers. CFAN-M As the master node of CFAN, it is a device node that manages and establishes the connection of nodes in CFAN. CFAN-S As a slave node that constitutes CFAN, a device node excluding CFAN-M in CFAN CFAN-R A device node among CFAN-S that enables wireless power transfer and serves to extend the range of CFAN. It can be called a repeater node. The following are abbreviations and their formal names used in this specification. Full name of the abbreviation ARA: Association Response Acknowledgement ARQ: Association Request ARS: Association Response ASC: Association Status Confirmation ASRA: Association Status Response Acknowledgement ASRQ: Association Status Request ASRS: Association Status Response CFAN: Conductive Fabric Area Network CFAN-M: Conductive Fabric Area Network Master node CFAN-S: Conductive Fabric Area Network Slave node CFAN-R: Conductive Fabric Area Network Repeater node DA: Data Acknowledgement DARA: Disassociation Response Acknowledgement DARQ: Disassociation Request DARS: Disassociation Response DRA: Data Response Acknowledgement DRQ: Data Request DRRQ: Data Response Request DRS: Data Response FCS: Frame Check Sequence GSRQ: Group ID Set-up Request GSRS: Group ID Set-up Response HCS: Header Check Sequence LSB: Least Significant Bit MAC: Media Access Control NRZ-L: Non-Return-to-Zero Level RA: Response Acknowledgement RRQ: Response Request RSRA: Repeater Set-up Response Acknowledgement RSRQ: Repeater Set-up Request RSRS: Repeater Set-up Response TDMA: Time Division Multiple Access UID: Unique Identifier WPCN: Wireless Powered Communication Network WPT: Wireless Power Transfer range The present invention relates to a network system in a conductive fiber area. Protocols for the media access control layer and the physical layer of a conductive fiber network system for communicating with wearable sensors, actuators, processors, batteries, e-textiles, etc. are disclosed. The protocol establishes links and controls of multiple devices on one or more conductive fiber area networks for data and power transmission. The Media Access Control Layer protocol is designed to: - Configure a simple network topology for communication - Formation of a variable superframe structure for data transmission and flow control according to the channel - Resource allocation between nodes for time and power sharing Physical layer protocols are designed to: - Modulation for low-cost implementation and reduced error performance - Setting the frequency suitable for conductive fiber area networks outline The Conductive Fabric Area Network (CFAN) system according to the present invention is a communication system capable of transmitting and receiving data through a conductive fiber-based network. The system operates one or more Conductive Fabric Area Networks (hereinafter abbreviated as 'CFANs'). The CFAN is designed to utilize the characteristics of conductive fibers. The system uses a carrier frequency to secure stable communication and a wide conductive fiber area even in harsh environments, a simple and robust modulation method such as ASK and FSK to reduce implementation costs and error probability, and a coding technique for robustness against noise. In principle, a data transmission rate of several kbps is provided on the CFAN. Additionally, the system utilizes simple and efficient network topologies, such as star or tree topologies, for low power consumption. Dynamic address allocation is used for packet size management and efficient address management. Furthermore, the system utilizes variable data rates and adaptive link quality control. Devices on a CFAN are classified into one of three types of nodes: master node, slave node, and repeater node, depending on their roles. In the present invention, the master node may be denoted as CFAN-M, the slave node as CFAN-S, and the repeater node as CFAN-R. Basically, a CFAN is composed of one CFAN-M, multiple CFAN-S, and multiple pairs of CFAN-R. The conductive fiber area network system according to the present invention may have one or more CFANs. In this case, there may be one main CFAN having a main CFAN-M and one or more sub-CFANs, each having one sub-CFAN-M. When a slave node joins the network (CFAN), the master node, based on the slave node's request and the master node's judgment, directly or through CFAN-R, allocates a time slot to each device, i.e., the slave node. The conductive fiber area network system according to the present invention uses the TDMA (Time Division Multiple Access) method for transmitting and receiving data. CFANs can accommodate multiple wearable devices of various shapes, locations, sizes, and weights. These devices can be utilized in a variety of applications, services, and industries, including the following examples: - Health monitoring: detection, treatment, and response based on the patient's condition or treatment. - Sports and fitness: Improve awareness of your physical condition and ability to perform activities. - Smart clothing: Tracking and responding to physical activity using industrial or environmental sensors. - Military and soft suits: Smart fabrics capable of kinematic analysis and rapid situational response CFAN-S are systematically distributed throughout the conductive fiber area, and CFAN-M is placed at the center of the conductive fiber network. CFAN-R is positioned near the edge of the conductive fiber to interconnect the conductive fibers. When CFAN-S receives sensing data from sensors, it transmits the data to CFAN-M via the conductive fiber. CFAN-M can then transmit the data received from CFAN-S to the monitoring center via other physical media, such as wireless communication. Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present invention, the same reference numbers will be used for the same means regardless of the drawing numbers. Network components (1) General CFAN's main components are divided into time and physical elements. The time element refers to a superframe consisting of a request period, a response period, and a spontaneous period. The physical element refers to the network, which consists of CFAN-M, CFAN-R, and CFAN-S. CFAN-M manages CFANs, CFAN-R supports Wireless Power Transfer (WPT) and activates multiple CFANs, and CFAN-S communicates with CFAN-M. Figure 1 illustrates the structure of a superframe (time element), and Figure 2 illustrates the structure of a network (physical element). The first node to be determined in a CFAN is CFAN-M, and a superframe begins when CFAN-M transmits a request packet during the request period. CFAN-M is responsible for managing the association, disassociation, release, and scheduling of CFAN-R and CFAN-S. Meanwhile, the extended CFAN is composed of multiple CFANs. The CFANs included in the extended CFAN are divided into a main CFAN, a sub CFAN, and an inter CFAN. The main CFAN is a CFAN that has power and one or more CFAN-Rs, and the sub CFAN is a CFAN that must be supplied with power from the main CFAN and does not have a CFAN-R. In addition, the inter CFAN is a multi-point WPCN (Wireless Powered Communication Network) between the CFAN-R and the sub CFAN-M. The main CFAN-M manages the sub CFAN-M through the CFAN-R of the main CFAN. (2) Time factor The time element used in CFAN is a TDMA time slot. CFAN-M manages CFAN-R and CFAN-S, which can transmit data, and time slots are individually allocated to all nodes in the CFAN group selected by CFAN-M. CFAN's superframe structure consists of a request section, a response section, and an autonomous section, as shown in Figure 1, and the length of each section is variable. When multiple sub-CFANs are connected to the main CFAN and the CFAN is expanded, the superframe structure remains the same for all CFANs. The superframe is initiated by CFAN-M, which transmits a response request packet (RR packet) during the request period. The response request packet contains information about the ID of CFAN-R and the ID of CFAN-S, and CFAN-R and CFAN-S use the information in the response request packet to transmit response packets during the response period. When multiple CFANs exist (extended CFANs), a CFAN-R is assigned a time slot, just like other CFAN-Ss, if approved by the main CFAN-M. However, within a time slot, a CFAN-R must subdivide the time slot to transmit data from a sub-CFAN. In this case, the CFAN-R of the main CFAN connects to the CFAN-M and CFAN-S of the sub-CFANs that are not reachable from the main CFAN-M. The main CFAN and sub-CFANs can operate simultaneously. During the request period of the main CFAN, CFAN-M transmits a response request packet to CFAN-R and CFAN-S so that they can return the corresponding response packet during the response period. In the sub-CFAN, CFAN-M must transmit a response request packet to CFAN-S. In the inter-CFAN (WPCN), CFAN-R must transmit a response request packet to the associated sub-CFAN-M. In the response section of the main CFAN, CFAN-R and CFAN-S can transmit response packets according to the response request packets received from CFAN-M during the request section. The response section can be divided into multiple time slots depending on the number of CFAN-Rs and CFAN-Ss selected in the CFAN. The length of each time slot varies depending on the length of the response frame and the acknowledgment. CFAN-M reserves time slots for CFAN-R, CFAN-S, or a specific group to use the response section, and nodes in the assigned group independently transmit data frames in the response section. The slot number is determined by the number of time slots, otherwise the slot number is 0. During the response period of a sub-CFAN, a CFAN-S that has joined the sub-CFAN retransmits a response packet to its own CFAN-M based on the response request packet. The response period is divided into time slots according to the number of CFAN-Ss selected in the sub-CFAN. The length of each time slot varies depending on the length of the response packet and the acknowledgment packet. CFAN-Ss in the assigned group independently transmit data frames during the response period. In the response period of the inter-CFAN (WPCN), the sub-CFAN-M connected to the CFAN-R transmits a response back to the sub-CFAN-M based on the response request packet. The response period is divided into time slots according to the number of CFAN-S selected in the sub-CFAN. The length of each time slot varies depending on the length of the response packet and the acknowledgment packet. An autonomous period in a CFAN begins when no device returns a response packet for a certain period of time. During the autonomous period in the main CFAN, CFAN-R and CFAN-S can transmit data without a request from CFAN-M. During the autonomous period in the sub-CFAN, CFAN-S can transmit data without a request from CFAN-M. During the autonomous period in the inter-CFAN (WPCN), the sub-CFAN-M can transmit data on the main CFAN without a request from CFAN-R. The autonomous period continues until CFAN-M transmits a requested period. CFAN's superframe is divided into request, response, and autonomous sections. CFAN's CFAN-M, CFAN-R, and CFAN-S operate in each section as follows: [Request Section] In the request section of the main CFAN, the CFAN-M transmits a response request packet to the CFAN-R and CFAN-S. The CFAN-R or CFAN-S that receives the response request packet determines whether to transmit a response packet in the response section based on the response request packet. The CFAN-M can determine which CFAN-R and CFAN-S are selected from the group to transmit in the response section. In the sub CFAN, the CFAN-M transmits a response request packet to the CFAN-S, and determines whether to transmit a response packet in the response section after receiving the response request packet. The CFAN-M can determine which CFAN-S are grouped and transmitted in the response section. [Response Segment] The CFAN-R or CFAN-S selected by the CFAN-M can transmit a response packet in the response segment. When the CFAN-R or CFAN-S transmits a response packet in the response segment, the CFAN-M that receives the response packet transmits a response acknowledgment packet (RA packet). The CFAN-R or CFAN-S that has not received a response acknowledgment packet transmits a response packet every time slot until it receives a response acknowledgment packet from the CFAN-M or a timeout occurs. [Autonomous Segment] For the main CFAN or sub CFAN, if CFAN-R or CFAN-S does not transmit a response packet for a certain period of time, an autonomous segment is initiated and remains in effect until CFAN-M transmits a response request packet. In the autonomous segment, CFAN-R or CFAN-S can transmit data without a request from CFAN-M. (3) Physical factors The physical components that make up a CFAN are devices classified into CFAN-M, CFAN-R, and CFAN-S according to their roles. CFAN is a network that can transmit and receive data between CFAN-N, CFAN-R, and CFAN-S. CFAN-M manages the entire CFAN, and in principle, there is only one CFAN-M per network. CFAN-M controls CFAN-R and CFAN-S by broadcasting response request packets to all nodes at once. CFAN-R and CFAN-S must transmit and receive response packets under the control of CFAN-M. In the case of multiple CFANs, there should be only one main CFAN and multiple sub-CFANs. The main CFAN can have one or more CFAN-Rs, but sub-CFANs do not have CFAN-Rs. A CFAN can be configured as shown in Fig. 2. The main CFAN may have one or more power sources, while the sub-CFAN does not have a direct power source. The power source of the main CFAN may be a disposable battery using a pouch, while the power source of the sub-CFAN may be a flexible battery, such as a lithium-ion flexible battery or a lithium polymer flexible battery. Furthermore, the flexible battery may be a conductive fiber layer-based secondary battery in which a dielectric is interposed between conductive fiber layers that serve as electrodes forming a supercapacitor structure, as shown in FIG. 31. The secondary battery may have different charge capacities, charge rates, and charge times depending on the material that constitutes the dielectric. As a charging method for the sub-CFAN, the main CFAN may use an electromagnetic induction method or a photoelectric charging method. The CFAN-M (master node) is the node that manages the CFAN. In principle, there is only one CFAN-M per network, and the CFAN-M manages and controls the CFAN-R and CFAN-S using response request packets. If there are multiple CFANs, there can be only one main CFAN-M per main CFAN, and only one sub-CFAN-M per sub-CFAN. The sub-CFAN-M can communicate with the main CFAN-M through the CFAN-R associated with it. All sub-CFAN-Ms can collect energy and store it in a supercapacitor from the main CFAN through the CFAN-R. The sub-CFAN-M uses energy to power its own sub-CFAN and transmit data to the CFAN-R. CFAN-S (slave nodes) are nodes that make up a CFAN (excluding CFAN-M and CFAN-R). There can be up to 65,519 CFAN-Ss per network. They transmit response packets based on request packets transmitted by CFAN-Ms in the network. CFAN-R (repeater node) is a node corresponding to CFAN-S, and is a device of the main CFAN that can transmit and receive data with the sub CFAN-M of the sub CFAN. CFAN-R can perform WPT and transmit data to the sub CFAN-M at the same time. The sub CFAN-M can transmit data of all CFAN-S to CFAN-R at any given time, and CFAN-R waits until the corresponding time slot in the response section of the main CFAN to transmit data. CFAN-R enables connections between the main CFAN and multiple sub CFANs. (4) Address element CFAN uses CFAN ID, UID, group address, node address and other addressing system to identify each CFAN-R and CFAN-S. The CFAN ID is a unique ID that identifies each CFAN from other CFANs. This value is not repeated in other CFANs and remains constant as long as the CFAN exists. The CFAN ID is an 8-bit address ID assigned by CFAN-M. The CFAN ID is assigned to the source CFAN ID and the destination CFAN ID. As shown in Table 1 (Specified CFAN ID), a CFAN ID can be specified for broadcasting to all CFANs. CFAN IDContentRemarks0xFFAll CFANsWhen broadcasting to all CFANs0xF0-0xFEReserved- A UID is a 64-bit unique identifier. It can be composed of a group address, IC manufacturer code, and IC manufacturer serial number, as shown in Table 2 (UID Structure). CFAN-S is identified by its UID. 1 byte1 byte6 bytesGroup IDIC manufacturer's codeIC manufacturer's serial number The group ID is the identifier of the CFAN-R and CFAN-S groups classified in the CFAN. CFAN-M can request data transmission in groups during the request period. Groups are used depending on the application. Some group IDs can be designated as shown in Table 3 (Designated Group IDs). Group IDContentRemarks0xFFAll groupsWhen selecting all groups0xF0 - 0xFEReserved- A node ID is an 8-bit address assigned by CFAN-M that is used instead of a UID to identify each node. Node IDs can be assigned to source and destination addresses. Some node IDs can be assigned as shown in Table 4 (Designated Node IDs). Node IDContentRemarks0xFFAll nodesWhen broadcasting or transmitting to all nodes0xFEUnjoined CFAN-SDefault ID for CFAN-S0xFDUnjoined CFAN-RDefault ID for CFAN-R0xF0 - 0xFCReserved- Network status (1) General In CFAN, CFAN-R and CFAN-S obtain the active states of network configuration, network association, network disassociation, network connection verification, data transmission, and network release. (2) Network configuration CFAN-M forms a network by sending a request packet to CFAN-R and CFAN-S in the request section. The CFAN ID is included in the request packet so that CFAN-R or CFAN-S can identify the connected network. When CFAN-R or CFAN-S returns a response packet to CFAN-M, the primary network is established. The minimum network section refers to the case where only CFAN-M exists, and it consists only of the request section and the autonomous section. In an extended CFAN, a CFAN-R forms a network by sending a request packet containing the CFAN ID to a sub-CFAN-M. The extended network is formed when the sub-CFAN-M returns a response packet to the CFAN-R. (3) Network association When CFAN-M broadcasts an association request packet, CFAN-R and CFAN-S forward the association request packets received during the response period. Upon reception, CFAN-R and CFAN-S search for the received packets and connect to the network based on them. If CFAN-R and CFAN-S find the correct network, they send an association response packet to CFAN-M. CFAN-M sends a final acknowledgement to CFAN-R and CFAN-S, which, upon receiving this acknowledgement, completes the network connection in the main CFAN. In an extended CFAN, CFAN-M sends an association request packet to all CFAN-Rs, which in turn send association request packets to the sub-CFAN-Ms. The sub-CFAN-Ms respond to the received association request packets to CFAN-Rs, and CFAN-Rs forward this response packet to the main CFAN-M. Next, the main CFAN-M sends approval to the sub-CFAN-M via the CFAN-R. Finally, the CFAN-M sends a connection request packet to the CFAN-S belonging to the sub-CFAN via the CFAN-R and the sub-CFAN-M. The CFAN-S then responds with a connection response packet to the main CFAN-M, and the main CFAN-M sends a connection response confirmation packet. After the CFAN-S of the sub-CFAN receives approval, the extended network connection is completed. (4) Network disassociation A CFAN-S, CFAN-R, or sub-CFAN-M associated with a CFAN can be separated at the request of the CFAN-M or automatically. In an extended CFAN, node separation of a sub-CFAN is performed by the CFAN-R and sub-CFAN-M to reach the CFAN-S of the sub-CFAN. The main CFAN-M can send a separation request to the CFAN-S, CFAN-R, or sub-CFAN-M depending on the current network status or service type for forced separation. In case of voluntary separation, the main CFAN-M can know the separation status of the CFAN-S, CFAN-R, or sub-CFAN-M through the response result of the next connection request packet. (5) Network connection check The connection status of a CFAN-S, CFAN-R, or sub-CFAN-M in the network can be requested from the main CFAN-M. To check the network connection status, the main CFAN-M forwards a connection status request packet to the CFAN-S, CFAN-R, or sub-CFAN-M. The CFAN-S, CFAN-R, or sub-CFAN-M returns a connection status response packet to the main CFAN-M. When the acknowledgement packet is forwarded from the main CFAN-M to the CFAN-S, CFAN-R, or sub-CFAN-M through the same procedure, the network connection check is completed. When the main CFAN-M transmits and receives a connection status packet to and from the CFAN-S of the sub-CFAN in the extended CFAN, the packet goes through the CFAN-R and sub-CFAN-M. (6) Data transmission When the main CFAN-M transmits a data response request packet within the request section, the CFAN-S, CFAN-R, or sub CFAN-M responds with a data response packet to the main CFAN-M depending on the type of requested data. The main CFAN-M, which has received the data response packet, transmits a data confirmation packet, and the data transmission is completed after the CFAN-S, CFAN-R, or sub CFAN-M receives the data confirmation packet. In the extended CFAN, the main CFAN-M and the CFAN-S of the sub CFAN exchange data response packets through the CFAN-R and the sub CFAN-M. (7) Network release CFAN deactivation can be divided into normal deactivation upon request from the main CFAN-M and abnormal deactivation due to unexpected circumstances. Normal deactivation occurs when the main CFAN-M determines the deactivation status and distributes a request to all CFAN-S, CFAN-R, and sub-CFAN-Ms to cancel the network. Abnormal network deactivation occurs when all participating CFAN-S, CFAN-R, and sub-CFAN-Ms are simultaneously terminated. (8) Network node state (CFAN node state) CFAN node states include CFAN-M state, CFAN-S state, and CFAN-R state. When the main CFAN is powered on, the main CFAN-M switches to the request section. If there is no response, the CFAN-M remains in the request section. When the CFAN-M receives a response confirmation packet, its state changes to the response section. When the CFAN-R is powered on in the main CFAN, the CFAN-R can power on the nearby sub CFAN-M through WPT. Figure 3 is a state diagram of CFAN-M. The CFAN-M enters the Standby state when powered on via the wired power supply of the conductive fiber. If the CFAN-M is a sub-CFAN of an extended CFAN, it enters the Standby state when powered on via WPT. From the Standby state, when a superframe is initiated or an application sends a command, the CFAN-M enters the Packet Generation state. The CFAN-M generates a RR packet and transmits it to the CFAN-R and CFAN-S, and the CFAN-M returns to the Standby state. When CFAN-M receives a packet from CFAN-R or CFAN-S in standby mode, CFAN-M enters packet analysis mode. If the source ID and destination ID of the received packet belong to the current CFAN, CFAN-M enters packet generation mode. CFAN-M then generates an RA or DA packet and transmits it to CFAN-R or CFAN-S on the corresponding medium. CFAN-M then returns to standby mode. On the other hand, if CFAN-M receives an RA or DA packet in the packet analysis state, or if there is a mismatch or error in the data packet, the state of CFAN-M returns immediately to the waiting state. If there is a timeout, mismatch or error in the acknowledgement packet received in the waiting state, CFAN-M regenerates the packet in the packet generation state and retransmits it to CFAN-R and CFAN-S through the medium, and then returns to the waiting state. If these failures occur continuously, the packet retransmission procedure is repeated as many times as necessary (at most N times). In the (N+1) procedure, the state of CFAN-M remains in the waiting state. In the extended CFAN, when the CFAN-R is near the sub-CFAN-M, the sub-CFAN-M can receive wireless power from the CFAN-R and use it to power the sub-CFAN. When the main CFAN-M transmits a packet to the sub-CFAN, the CFAN-R transmits the packet to the sub-CFAN-M over the wireless channel, and the sub-CFAN-M moves from the standby state to the packet analysis state. If the destination CFAN ID corresponds to the sub-CFAN ID, the sub-CFAN-M moves to the packet generation state and transmits the packet to the corresponding CFAN-S or CFAN-S. The sub-CFAN-M then returns to the standby state. When the sub-CFAN transmits a packet to the main CFAN, the sub-CFAN-M moves from the standby state to the packet analysis state and receives the packet from the CFAN-S. If the destination CFAN ID corresponds to the main CFAN ID, the sub-CFAN-M moves to the packet generation state and transmits the packet to the CFAN-R over the wireless channel in the corresponding section. The sub-CFAN-M then returns to the standby state. CFAN-S enters the standby state immediately upon initiating operation. While in the standby state, when an application sends system data, CFAN-S enters the packet generation state. During the autonomous section, CFAN-S generates packets and transmits them to CFAN-M. CFAN-S then returns to the standby state. When CFAN-S receives a packet in standby mode, CFAN-S enters packet analysis mode and analyzes the received packet. If it is an RR packet and the destination ID matches, CFAN-S enters packet generation mode and transmits a response packet to CFAN-M. CFAN-S then returns to standby mode. Figure 4 is a state diagram of CFAN-S. If the packet received in the packet analysis of CFAN-S is an error packet or an RA or DA packet, CFAN-S enters the waiting state. If CFAN-S does not receive an RA or DA packet during the timeout period, the state of CFAN-S switches from the waiting state to the packet generation state. Then, CFAN-S regenerates a response packet and retransmits it to CFAN-M, and the state of CFAN-S switches from the packet generation state to the waiting state. The retransmission of the response packet is repeated as many times as necessary (up to N times). CFAN-S remains in the waiting state during the (N+1)th timeout period. Figure 5 is a state diagram of CFAN-R. When powered on, the CFAN-R enters the standby state. In this state, when the CFAN-R receives a packet, it enters the packet analysis state, where it analyzes the received packet. If the received packet is an RR packet and the destination ID matches, the CFAN-R enters the packet generation state, sending a response packet through the appropriate medium. The CFAN-R then transitions to the standby state. In the packet analysis state, if a packet received is a packet error, RA, or DA packet, CFAN-R enters the waiting state. If CFAN-R does not receive an RA packet or DA packet during the timeout period, CFAN-R switches from the waiting state to the packet generation state. Then, CFAN-R regenerates a response packet and retransmits it to CFAN-M, and CFAN-R enters the waiting state. Retransmission of the response packet is repeated as many times as necessary (at most N times). CFAN-R remains in the waiting state during the (N+1)th timeout period. In the extended CFAN, if the sub-CFAN-M is near the CFAN-R, the CFAN-R can supply power to the sub-CFAN through the sub-CFAN-M via wireless power transfer during the standby phase. When the main CFAN-M sends a packet to the sub-CFAN, the CFAN-R enters the packet analysis state from the standby state. If the destination CFAN ID corresponds to the sub-CFAN ID, the CFAN-R moves to the packet generation state and transmits the packet to the sub-CFAN-M via the wireless channel. Then, the CFAN-R returns to the standby state. When the sub-CFAN-M transmits a packet to the main CFAN via the wireless channel, the CFAN-R moves to the packet analysis state from the standby state and receives the packet. If the destination CFAN ID corresponds to the main CFAN ID, the CFAN-R moves to the packet generation state and transmits the packet to the main CFAN-M via the wired channel in the corresponding section. Then, the CFAN-R returns to the standby state. MAC layer frame format (1) General CFAN's MAC (Medium Access Control) frame format consists of a frame header and a frame body. The frame header contains information about data between CFAN-R and CFAN-S, and the frame body contains data for transmission between CFAN nodes. (2) Frame format All frame formats of MAC consist of a frame header and a frame body, as shown in Table 5. 2 bytes1 byte1 byte1 byte1 byte1 byteVariable2 bytesFrame controlSourceCFAN IDSourceaddressDestination CFAN IDDestination addressSequence numberPayloadFrame check sequenceFrame headerFrame body The frame header consists of a frame control, source CFAN ID, source address, destination CFAN ID, destination address, and sequence number. The frame header contains information for frame transmission, reception, and flow control. The frame header can be used for data transmission. The frame control field consists of frame type, acknowledgment policy, first fragment, last fragment, and protocol version, as shown in Table 6. The unit of row 1 in Table 6 is bit. 0-23-4567-89-15Frame typeAcknowledgement policyFirst fragmentLast fragmentProtocol versionReserved A description of each field included in the frame control field is as follows. 1) The frame type field consists of 3 bits. Details on the frame type are described later. 2) The Acknowledgement Policy field consists of two bits. If the received frame is an acknowledgment frame, it indicates the policy for the received acknowledgment frame. Otherwise, it indicates the policy for the acknowledgment frame for the destination node. Each item of the acknowledgment policy is described in detail below. a) No Acknowledgement: The destination node does not acknowledge the transmitted frame, and the source node considers the transmission successful regardless of the transmission result. This method can be used for frames transmitted for 1:1 or 1:N transmissions that do not require an ACK. b) Single Acknowledgement: The destination node that receives the frame sends an acknowledgment frame in response to the source node after SIFS. This acknowledgment policy can only be used for 1:1 transmissions. c) Multi-acknowledgment: The destination node that receives the frame transmits an acknowledgment frame in response to multiple source nodes after a SIFS. This acknowledgment policy can be used for 1:N transmissions. d) Data Acknowledgement: The destination node that receives the data frame sends a data acknowledgement frame in response to the source node after a SIFS. This acknowledgement policy can only be used for 1:1 data transfers. 3) The first fragment field is 1 bit. '1' indicates that the frame is the start of a request, response, or data packet from the upper layer, and '0' indicates that it is not the start. 4) The last fragment field is 1 bit. '1' indicates that the frame is the end of a request, response, or data packet from the upper layer, and '0' indicates that it is not the end. 5) The Protocol Version field consists of two bits, and its size and location are fixed regardless of the system's protocol version. Its current value is 0 and increases by 1 each time a new version is released. If a node receives a packet with a higher version than its own, it discards it without notifying the source node. 6) Reserve: A field prepared for future use. The CFAN ID field consists of 1 byte each and is used to identify the network, as shown in Table 5. In the frame, the source CFAN ID indicates the CFAN where the transmitting node is located, and the destination CFAN ID indicates the CFAN where the receiving node is located. Node IDs are used to identify nodes within each network. The source node ID and destination node ID each contain 1 byte. The sequence number field is 8 bits long and represents the frame sequence number. In a data frame, a sequence number between 0 and 255 is assigned through an incremental counter for each packet, and is reset to 0 when it reaches 255. The frame body consists of a payload containing data for transmission between CFAN nodes and a Frame Check Sequence (FCS) for checking for errors within the payload. Each payload has a different format depending on the frame type in the frame control field. The payload contains the transmission data between the main CFAN-M and each CFAN-S, CFAN-R, and sub CFAN-M, and has a variable length between 0 and 247. The Frame Check Sequence (FCS) is a 16-bit sequence used to verify that the frame body has been received without errors. The FCS is generated using a 16th-order standard generator polynomial, as shown in Equation 1. (3) Frame type Frame types are defined as four types: request frame, response frame, data frame, and confirmation frame. Table 7 shows the frame types, binary values, content, and time elements (intervals) for each frame type. Frame typeValue (Binary)ContentPeriodRequest frame000Request for the response of association, disassociation, association status, data transmission, and so on.RequestResponse frame001Response for the request of association, disassociation, association status, data transmission, and so on.ResponseData frame010Data transmission without a requestSpontaneousAcknowledgement frame011Acknowledgement of the response and data transmissionResponse, Spontaneous A request frame is used when a primary CFAN-M sends a request packet to a specific CFAN-S, CFAN-R, or sub-CFAN-M of the CFAN during a request period, or broadcasts information to all CFAN-S, CFAN-R, and sub-CFAN-Ms. In an extended CFAN, a request frame is used when a CFAN-R sends a request packet to a sub-CFAN-M during a request period. A request frame can be structured as shown in Table 8. The unit of row 1 of Table 8 is Byte. 8111L1L2...Ln2Frame headerGroup IDRequest codeLength(=∑Ln)Request block-1Request block-2...Request block-nFrame check sequenceRequest frame payloadFrame body The response frame is used when sending a response packet from a CFAN-S, CFAN-R, or sub-CFAN-M in the request period for a request from the main CFAN-M. The appropriate CFAN-S, CFAN-R, or sub-CFAN-M transmits a response packet between the request periods within a specified number of times until an acknowledgment packet is received. In the extended CFAN, the sub-CFAN-M transmits a response packet in the request period for a CFAN-R request. The response frame can be configured as shown in Table 9. The unit of row 1 in Table 9 is Byte. 8111L1L2...Ln2Frame headerGroup IDResponse codeLength(=∑Ln)Response block-1Response block-2...Response block-nFrame check sequenceResponse frame payloadFrame body A data frame is used when a CFAN-S, CFAN-R, or sub-CFAN-M transmits data to the main CFAN-M in the response section, regardless of whether the CFAN-M requests it. In an extended CFAN, the sub-CFAN-M transmits data to the CFAN-R. A data frame can be structured as shown in Table 10. The unit of the first row of Table 10 is a byte. 88L2Frame headerUIDDataFrame check sequenceData frame payloadFrame body There are two types of acknowledgment frames: RA (response acknowledgment) frames and DA (data acknowledgment) frames. In an RA frame, when the main CFAN-M transmits a request frame, the CFAN-S, CFAN-R, or sub CFAN-M receives the request packet and transmits a response packet. The main CFAN-M transmits the response packet and then transmits an RA packet. The RA data for the received response packet is recorded in the payload of the acknowledgment frame. The main CFAN-M, which has received an appropriate response frame, responds to the transmitting CFAN-S, CFAN-R, or sub CFAN-M by transmitting an RA frame after a short frame interval in the request period. The DA frame is an acknowledgment frame for the received data packet. The main CFAN-M responds to the CFAN-S, CFAN-R, or sub CFAN-M that transmitted the data packet by transmitting a DA frame after a short frame interval in the response period. In an extended CFAN, a CFAN-R responds to a sub-CFAN-M that has transmitted a response or data packet by transmitting an RA or DA frame in the response cycle. Table 11 shows an example of the format of a response confirmation frame. The unit of row 1 of Table 11 is Byte. 8111L1L2...Ln2FrameheaderGroup IDResponse Confirm-ation codeLength(=∑ Ln)Response Confirm-ation block-1Response Confirm-ation block-2...Response Confirm-ationblock-nFrame check sequenceAcknowledgement frame payloadFrame body Table 12 and the DA frame consist of a frame header and a frame body. If the destination CFAN ID is 0xFF and the destination node ID is 0xFE or 0xFD, they correspond to an unjoined CFAN-S ID and an unjoined CFAN-R ID, respectively, and in this case, the UID field must be included. 2 bytes1 byte1 byte1 byte1 byte1 byte8 (option)2 bytesFrame controlSourceCFAN IDSourceaddressDestin-ationCFAN IDDestin-ationaddressSequence numberUIDFrame check sequenceFrame headerFrame body (4) Payload format The payload format is generated differently depending on the frame type, including request frame, response frame, data frame, and acknowledgement frame. [Request Frame] Table 13 describes the payload format of a request frame. As shown in Table 13, the payload for a request frame consists of a group ID, a request code, a length, and one or more request blocks according to the request. The unit of row 1 in Table 13 is Byte. 111L1L2...LnGroup IDRequest codeLength(=∑ Ln)Request block-1Request block-2...Request block-n The Group ID field consists of 1 byte and is used to send a response request packet to a specific group. A Group ID of 0xFF indicates that CFAN-M requests responses from all CFAN-S, CFAN-R, and sub-CFAN-M groups. Details on the Group ID are described above. The request code in the payload of the request frame can be configured as shown in Table 14. CategoryRequest codeContentRemarksNetwork0x01Association requestRequest for association response to unjoined nodes0x02Disassociation requestRequest for disassociation response to joined nodes0x03Association status requestRequest for association status response to joined nodes0x04-0x0FRedserved-Data0x11Data requestRequest for data transmission to joined nodes0x12-0x1FRedserved-Configuration0x21Group ID set-upGroup ID change request to joined node0x22-0x2FRedserved-Reserved0x31-0xFFReserved- The length field consists of 1 byte. It indicates the total length of the request block, and the length field value varies depending on the length and number of request blocks. The data format of the request block varies depending on the request code, and one or more request blocks can be included in the payload of the request frame. Details about the data format of each request block are as follows: 1) Association request The ARQ block format can be configured as shown in Table 15 and consists of an 8-byte UID mask. This UID mask can be used to implement a binary search algorithm. 8 bytesUID mask 2) Disassociation request The block format of DARQ can be represented as Table 16. The first and second bytes are the CFAN ID and the node ID of the CFAN-S, CFAN-R, or sub-CFAN-M for DARQ, and the next byte is the slot number to be used for the response period. If the node ID is 0xFF, DARQ is transmitted to all CFAN-Rs and CFAN-S under the group ID. 1 byte1 byte1 byteCFAN IDNode IDSlot number 3) Association status request The block format of ASRQ can be expressed as Table 17. The first and second bytes are the CFAN ID and the node ID of the CFAN-S, CFAN-R, or sub-CFAN-M for ASRQ. If the CFAN ID is 0xFF and the node ID is 0xFF, ASRQ is requested to all CFAN-Rs and CFAN-Ss under the group ID. 1 byte1 byte1 byteCFAN IDNode IDSlot number 4) Data request The DRQ block format is shown in Table 18. The first and second bytes represent the CFAN ID and node ID, the next byte represents the slot number, and the final L byte represents the received data type. The data type is determined by the application. 1 byte1 byte1 byteL BytesCFAN IDNode IDSlot numberData 5) Group ID set-up request The block format of GSRQ can be represented as shown in Table 19. The first and second bytes are the CFAN ID and node ID, the next byte is the slot number, and the last byte is the group ID to be set. 1 byte1 byte1 byteL BytesCFAN IDNode IDSlot numberGroup ID [Response Frame] Table 20 shows the payload format of the response frame. The payload format of the response frame contains response information for the request of CFAN-M. In the extended CFAN, it contains response information for the request of CFAN-R. The first byte is the group ID, the second byte is the response code, the third byte is the response data length (L), and the next L bytes are the response data. The unit of the first row of Table 20 is Byte. 111L1L2...LnGroup IDResponsecodeLength(=∑ Ln)Response block-1Responseblock-2...Response block-n The Group Address field consists of one byte and is used to send a response request packet to a specific group. Details on the group ID are described above. Table 21 lists the response codes included in the response frame payload. Response code types can be configured as shown in Table 21. CategoryResponseContentRemarksNetwork0x01Association responseTransmission of node UID0x02Disassociation responseTransmission of node UID0x03Association status responseTransmission of node UID0x04 - 0x0FReserved-Data0x11Data responseTransmission of request data0x12 - 0x1FReserved-Set-up0x21Group ID set-up responseTransmission of UID and group ID after changes in group ID0x22 - 0x2FReserved-Reserved0x40 - 0xFFReserved- The length field consists of 1 byte and indicates the length of the response data. The length field varies depending on the response data. The response data format is divided into the following: 1) Association response The block format of ARS can be configured as shown in Table 22. ARS data consists of an 8-byte UID. 8 bytesUID 2) Disassociation response The block format of DARS can be configured as shown in Table 23. DARS data consists of an 8-byte UID. 8 bytesUID 3) Association status response The ASRS block format can be configured as shown in Table 24. ASRS data can be composed of an 8-byte UID and a 1-byte status value. Table 25 is a table regarding association status check values. 8 bytes1 byteUIDStatus value ValueContent0x00Disassociation status0x01Association status0x02 - 0xFFReserved 4) Data response The block format of DRS can be configured as shown in Table 26. DRS data consists of 1 byte for CFAN ID, 1 byte for node ID, and L bytes of requested data. 1 byte1 byteL BytesCFAN IDNode IDRequested Data 5) Group ID setup response The block format of GSRS can be configured as shown in Table 27. GSRS data consists of 8 bytes for the UID with the changed group ID and 1 byte for the changed group ID. 8 bytes1 byteUIDAssigned group ID [Data Frame] The payload of a data frame contains the data to be transmitted. Table 28 describes the payload format of a data frame. A data frame consists of an 8-byte UID and L bytes of data. 8 bytesL bytesUIDData [Confirmation Frame] The payload of the RA (response acknowledgment) frame contains data about the received response packet. Table 29 shows the payload format of the acknowledgment frame. The first byte is the group ID, the second byte is the response acknowledgment code, the third byte is the length (L), and the next L bytes are the response acknowledgment block. The unit of row 1 of Table 29 is Byte. 111L1L2...LnGroup IDResponse Confirmation codeLength(=∑ Ln)Response Confirmation block-1Response Confirmation block-2...Response Confirmation block-n The Group ID field consists of one byte and is used to send a response request packet to a specific group. Details on the Group ID are described above. Table 30 is a table of response verification codes. Response verification code types can be configured as shown in Table 30. CategoryReception confirmation codeContentRemarksNetwork0x01Association response confirmationUID and assigned node ID transmission of nodes0x02Disassociation response confirmationUID and node ID transmission of nodes0x03Association status response confirmationUID transmission of nodes0x04 - 0x0FReserved-Data0x11Data response confirmationConfirmation of data transmission to a joined node0x12 - 0x1FReserved-Set-up0x21Group ID set-up response confirmationUID and group ID transmission after group ID changes0x23 - 0x2FReserved-Reserved0x31 - 0xFFReserved- The length field consists of 1 byte. It indicates the length of the response confirmation data and varies depending on the response confirmation data. The response confirmation block format is divided as follows: 1) Association response confirmation The block format of the Acknowledgement (ARA) for ARS can be configured as shown in Table 31. The first 8 bytes are the UID, and the next 2 bytes are the assigned CFAN ID and the assigned node ID. If the assigned CFAN ID is 0xFF and the assigned node ID is 0xFE or 0xFD, these correspond to the addresses of the unjoined CFAN-S and unjoined CFAN-R, respectively, and mean that the ARQ has been rejected. 8 bytes1 byte1 byteUIDAssigned CFAN IDAssigned node ID 2) Disassociation response confirmation The block format of DARS Acknowledgement (DARA) can be configured as shown in Table 32. The first 8 bytes are the UID, and the next 2 bytes are the CFAN ID and node ID. The assigned CFAN ID and node ID are used if separation is not allowed. If separation is not allowed, the unjoined CFAN is recorded as 0xFF, and the unjoined CFAN-S ID or unjoined CFAN-R is recorded as 0xFE or 0xFD, respectively. 8 bytes1 byte1 byteUIDCFAN IDNode ID 3) Association status response confirmation The ASR Acknowledgement (ASRA) block format can be configured as shown in Table 33. The ASR Acknowledgement block consists of an 8-byte UID. 8 bytesUID 4) Data response confirmation The block format of DR Confirmation (DRA) can be configured as shown in Table 34. The first two bytes are the CFAN ID and node ID, and the next byte is reserved. 1 byte1 byte1 byteCFAN IDNode IDReserved 5) Group ID set-up response confirmation The GSR verification (GAIRA) block format can be configured as shown in Table 35. The GSRS verification block consists of an 8-byte UID and a 1-byte status check value (setting status value). 8 bytes1 byteUIDGroup ID set-up status value The group ID setting status value can be configured as shown in Table 36. ValueContent0x00Change completed0x01Change failed0x02-0xFFReserved MAC layer functions (1) General At the MAC layer of CFAN, the Association, Disassociation, and Association Status Confirmation (ASC) processes are used to manage the CFAN network. Data transmission can occur in the response or autonomous segment. Additionally, a group address initialization function is provided for managing CFAN-S, CFAN-R, and sub-CFAN-M groups. (2) Network connection and disconnection To communicate with a CFAN-M, a CFAN-R or CFAN-S must first connect to a CFAN. Each CFAN-R and CFAN-S searches for a pre-configured CFAN and, if successful, connects to that CFAN. In an extended CFAN, the sub-CFAN must be connected to the main CFAN. [association] Figure 6 is a diagram showing a CFAN connection method. When CFAN-M transmits an ARQ packet to CFAN-R or CFAN-S, which is not yet connected to the CFAN, during the request period, CFAN-R or CFAN-S transmits an ARS packet to CFAN-M during the response period. CFAN-M determines the connection status of the appropriate CFAN-R or CFAN-S with the CFAN and notifies the result through an ARA packet. If the connection is allowed, the assigned node address ID is included in the ARA packet, and if it is denied, the default CFAN ID and node ID are recorded accordingly. If CFAN-M does not receive an ARS packet or CFAN-R or CFAN-S cannot receive an ARA packet due to a data error in the ARA packet, CFAN-M continues to transmit ARS packets for each superframe until it receives an ARA packet. When CFAN-R or CFAN-S receives an ARA packet from CFAN-M, the connection is completed. Figure 7 is a diagram illustrating a connection method of an extended CFAN. In an extended CFAN, the main CFAN-M transmits an ARQ packet (connection request packet) to the CFAN-S of a sub-CFAN that is not yet connected to a CFAN through the CFAN-R and the sub-CFAN-M. Then, the CFAN-S transmits an ARS packet (connection response packet) to the main CFAN-M through the sub-CFAN-M and CFAN-R, and after receiving the connection response, the main CFAN-M determines the appropriate connection status of the CFAN-S to the CFAN. The result is notified through an ARA packet (connection response acknowledgement packet). If the connection is allowed, the assigned CFAN ID and the assigned node ID are included in the ARA packet, and if the connection is denied, the default CFAN ID and the default node ID are recorded accordingly. [disassociation] Figure 8 is a diagram illustrating a method for separating a CFAN. When a CFAN-M transmits a DARQ packet (separation request packet) to a CFAN-R or a CFAN-S connected to the CFAN during a request period, the CFAN-R or CFAN-S transmits a DARS packet (separation response packet) to the CFAN-M during a response period. The CFAN-M determines the separation status of the appropriate CFAN-R or CFAN-S from the CFAN and notifies the result through a DARA packet (separation response confirmation packet). If separation is allowed, the CFAN ID and node ID address of the DARA packet are recorded as the default CFAN ID and default node ID, and if separation is denied, the existing node ID address is recorded. If CFAN-M fails to receive a DARS packet, or if CFAN-R or CFAN-S attempting separation cannot receive the DARA packet due to a data error in the DARA packet transmitted by CFAN-M even though CFAN-M has received the DARS packet, the CFAN-R or CFAN-S continues to retransmit the DARS packet to CFAN-M every superframe until it receives the DARA packet. Then, separation is completed when CFAN-R or CFAN-S receives the DARA packet from CFAN-M. Figure 9 is a diagram illustrating a method for separating an extended CFAN. In the extended CFAN, the main CFAN-M transmits a DARQ packet to the CFAN-S of the sub-CFAN connected to the CFAN through the CFAN-R and the sub-CFAN-M. Then, the CFAN-S transmits a DARS packet to the main CFAN-M through the sub-CFAN-M and CFAN-R. After receiving the connection response, the main CFAN-M determines the appropriate separation status of the CFAN-S for the CFAN and notifies the result through a DARA packet. If separation is permitted, the CFAN ID and node ID address of the DARA packet are recorded as the default CFAN ID and default node ID. If separation is rejected, the original CFAN ID and node ID address are recorded. [Association status check] Fig. 10 is a diagram showing a method for checking the connection status of a CFAN. When a CFAN-M transmits an ASRQ packet (connection status request packet) to a CFAN-R or a CFAN-S associated with the CFAN during a request period, the CFAN-R or CFAN-S transmits an ASRS packet (connection status response packet) to the CFAN-M during a response period. The CFAN-M checks the connection status of the appropriate CFAN-R or CFAN-S with an ASRA packet (connection status response acknowledgement packet) and transmits it to the CFAN. If the CFAN-M does not receive the ASRS packet or the CFAN-R or CFAN-S trying to send the ASRS packet cannot receive the ASRA packet due to a data error in the ASRA packet, the CFAN-R or the CFAN-S continues to transmit ASRS packets to the CFAN-M every superframe until it receives an ASRA packet. And, when CFAN-R or CFAN-S receives an ASRA packet from CFAN-M, ASRS is completed. That is, when CFAN-R or CFAN-S receives an ASRA packet from CFAN-M, connection status check is completed. Figure 11 is a diagram illustrating a method for checking the connection status of an extended CFAN. In an extended CFAN, the main CFAN-M sends an ASRQ packet to the CFAN-S of the sub-CFAN via the CFAN-R and the sub-CFAN-M. Next, the CFAN-S transmits an ASRS packet to the main CFAN-M via the sub-CFAN-M and CFAN-R. After receiving the ASRS packet, the main CFAN-M determines the appropriate connection status of the CFAN-S to the CFAN and transmits the result via an ASRA packet. (3) Data transmission Data can be transmitted in CFAN during either the responsive or autonomous period. During the responsive period, data can be transmitted upon request from CFAN-M, while during the autonomous period, data can be transmitted without a request from CFAN-M. [Data transmission during the response period] Fig. 12 is a diagram showing a data transmission method during a response section of a CFAN. When a CFAN-M transmits a DRQ packet (data request packet) to a CFAN-R or CFAN-S connected to the CFAN during the request section, the CFAN-R or CFAN-S transmits a DRS packet (data response packet) during the response section. After receiving the DRS packet from the CFAN-R or CFAN-S, the CFAN-M transmits a DRA packet (data response acknowledgement packet). If the CFAN-M does not receive the DRS packet from the CFAN-R, or if the CFAN-R or CFAN-S does not receive the DRA packet due to a packet error, the CFAN-R or CFAN-S continues to transmit the DRS packet at every time slot until it receives the DRA packet. When the CFAN-R or CFAN-S receives the DRA packet from the CFAN-M, the data transmission procedure of the response section is completed. Figure 13 is a diagram illustrating a data transmission method during the response section of an extended CFAN. In the extended CFAN, the main CFAN-M transmits a DRQ packet to the CFAN-S of the sub CFAN via the CFAN-R and the sub CFAN-M. Then, the CFAN-S transmits a DRS packet to the main CFAN-M via the sub CFAN-M and CFAN-R, and the main CFAN-M, upon receiving the response, transmits a DRA packet to the CFAN-S. The data transmission procedure during the response section is completed when the CFAN-S receives the DRA packet from the CFAN-M. [Data transmission during autonomous section] Figure 14 is a diagram illustrating a data transmission method during the autonomous section of CFAN. The autonomous section begins when CFAN-R or CFAN-S does not transmit a response packet during the timeout period. The autonomous section continues until CFAN-M transmits an RR packet. CFAN-R or CFAN-S can transmit data without a request from CFAN-M during the autonomous section. If a system outage occurs, CFAN-R or CFAN-S can transmit data without a request from CFAN-M. If CFAN-M does not receive a data packet or CFAN-R or CFAN-S does not receive a DA packet due to a packet error, CFAN-S continues to transmit data packets to CFAN-M until it receives a DA packet. When CFAN-R or CFAN-S receives a DA packet (data confirmation packet) from CFAN-M, the data transmission procedure of the autonomous section is completed. Figure 15 is a diagram illustrating a data transmission method during an autonomous section of an extended CFAN. In an extended CFAN, a CFAN-S of a sub-CFAN can transmit data during the autonomous section without a request from the main CFAN-M. In the event of a system outage, a CFAN-S can transmit data without a request from the main CFAN-M. (4) Group ID setup Figure 16 is a diagram illustrating a group ID setup method. When CFAN-M sends a GAIRQ packet (group ID setup request packet) to CFAN-R or CFAN-S connected to CFAN during the request period, CFAN-R or CFAN-S transmits a GAIRR packet (group ID setup response packet) during the response period. CFAN-M confirms the group address initialization status of the corresponding CFAN-R or CFAN-S and then transmits a GAIRA packet (group ID setup response confirmation packet). Figure 17 is a diagram illustrating a group ID setup method of an extended CFAN. When the main CFAN-M sends a GAIRQ packet to the CFAN-S of a sub-CFAN connected to the CFAN during a request period in the extended CFAN, the CFAN-S transmits a GAIRR response packet via the sub-CFAN-M and CFAN-R. The main CFAN-M checks the group address initialization status of the corresponding CFAN-S and then transmits a GAIRA packet. PHY layer (1) PHY layer frame format [common] The physical layer (PHY layer) frame format of CFAN is described below. Figure 18 is a diagram of the physical layer frame format. Each physical layer frame consists of a preamble, a header, and a payload. As shown in Figure 18, the physical layer frame consists of three parts: a preamble, a header, and a payload. When transmitting a packet, the preamble is transmitted first, followed by the header, and finally the payload. Transmission and reception of a packet begins with the LSB. [preamble] Figure 19 is a diagram regarding the preamble format. As shown in Figure 19, the preamble consists of one part called a synchronization sequence. The 16-bit synchronization sequence consists of the 12-bit sequence [0000 0000 0000].

[1010] A 4-bit sequence follows the synchronization sequence. The synchronization sequence is used for packet acquisition, symbol timing, and carrier frequency estimation. The preamble is coded using TYPE 0, which will be described later. [header] Figure 20 is a diagram of the header format. The header is added after the preamble to convey information about the payload. As illustrated in Figure 20, the header consists of 24 bits. Bits 0-2 are the data rate and coding fields. Bits 3-10 are the payload data length fields. Bits 16-23 are the CRC-8 HCS (Header Check Sequence). The header is coded using TYPE 0, which will be described later. Table 37 is a table regarding the header definition of the physical layer. BitContentDescriptionb2-b0Data rate and codingSpecifies the data rate and coding at which the payload is received (see Table 38)b10-b3Payload data lengthSpecifies the number of octets in the payload (which does not include in FCS)b15-b11ReservedReserved and set to zerob23-b16Header check sequenceProvides a CRC-8 HCS (see description of header check sequence) Table 38 is a definition table for data rates, modulation, and encoding. Bits 0-2 can be set to the values ​​shown in Table 38, depending on the data rate and encoding. However, the data rates in Table 38 can be changed to other values. Details for TYPEs 0-7 are described below. TypeValue (b2 b1 b0)Data rateModulation and codingTYPE 000032 kbpsGFSK + NRZ-LTYPE 1001128 kbpsGFSK + NRZ-LTYPE 2010512 kbpsGFSK + NRZ-LTYPE 30111024 kbpsGFSK + NRZ-LTYPE 41001 kbpsASK + NRZ-LTYPE 51012 kbpsASK + NRZ-LTYPE 61104 kbpsASK + NRZ-LTYPE 71118 kbpsASK + NRZ-L The payload data length is represented as an unsigned 8-bit integer. The payload data length represents the number of octets in the payload, excluding the FCS. The payload data length ranges from 0x00 to a maximum of 0xFF bytes. The CRC-8 Header Check Sequence (HCS) is used to check for header errors. The HCS handles data rate and encoding, payload data rate, and reserved 5 bits. The primitive polynomial is given in Equation 2. Figure 21 is a diagram of an encoder for a header check sequence. The processing sequence for header check is as shown in Figure 21. All registers are initialized to 0. Data is accumulated while switch 'S' of Fig. 21 is at '1'. When the last bit is accumulated, switch S moves to '2' and D 7 HCS is transmitted from the register starting at . [payload] Figure 22 is a diagram of the payload format. As shown in Figure 22, the payload consists of variable-length data and a Frame Check Sequence (FCS). If the payload data length field in the header is 0, the FCS is not transmitted. [Frame Check Sequence (FCS)] The CRC-16 FCS defined in Table 39 is used to check for errors in the payload. The FCS handles variable-length data. The primitive polynomial is X 16 +X 12 +X 5 +1. All registers are initialized. The frame check sequence is obtained by inverting the computed CRC-16 bits. CRCLengthPolynomialPresetResidueISO / IEC 1323916 bitsX 16 +X 12 +X 5 +10xFFFF0x1D0F (2) Coding and modulation [coding] Figure 23 is a diagram regarding the definition of NRZ-L encoding. In NRZ-L (level), 0 is represented by frequency ω1 and 1 is represented by frequency ω2. [Data rate and encoding type] The physical layer supports eight types as shown in Table 38. The preamble and header are encoded as TYPE 0, but the payload is encoded using the appropriate data rate and encoding. The data rate and encoding type of the payload are specified in the Data Rate and Encoding fields of the header. [modulation] Communication between CFAN-M, CFAN-R and CFAN-S uses GFSK modulation or ASK modulation. Figure 24 is a diagram for ASK modulation. As shown in Figure 24, encoded serial input data is converted into a number representing one of two ASK constellation points. (ω cis the carrier frequency of CFAN) Figure 25 is a diagram of GFSK modulation. As shown in Figure 25, encoded serial input data is converted into a number representing one of two GFSK constellation points. (ω1 and ω2 are the modulation frequencies of CFAN.) [Encoding and Modulation Process] Figure 26 is a diagram of the preamble encoding and modulation process. The preamble sequence is encoded using TYPE 0. Figure 27 is a diagram illustrating the encoding and modulation process of the header. As illustrated in Figure 27, the header is formatted by adding data rate and encoding, payload data length, 5-bit 0, and HCS values. The resulting combination of these values ​​is encoded using TYPE 0 and then modulated using GFSK or ASK. Figure 28 is a diagram illustrating the encoding and modulation process of a payload. As shown in Figure 28, the payload is formatted by concatenating data and an FCS value. The FCS value is calculated for the data. The resulting combination is encoded using TYPE I (I = 0-7) and then modulated using GFSK or ASK. medium interface (1) Frequency The center frequency of CFAN is ω1 and ω2 with a maximum tolerance of ±20 ppm for GFSK, or the center frequency ω with a maximum tolerance of ±20 ppm for ASK. c am. (2) Signal waveform GFSK and ASK modulation are used for transmission between CFAN-M, CFAN-R and CFAN-S. Fig. 29 is a diagram of a GFSK modulated signal, and Fig. 30 is a diagram of an ASK modulated signal. As shown in Figs. 29 and 30, the transmitted signal is modulated by GFSK and ASK according to the envelope defined in this specification. Table 40 is an example of a table regarding envelope parameters of GFSK. ParameterSymbolMin.Max.PositivevariationM h 0Negative variationM I 0Rising timet r 0Falling timet f 0 Network Design (CFAN Implementation Example) Several examples of CFAN implementations according to the present invention are presented. This section describes the physical structure of a CFAN. CFAN can be implemented in various designs based on a structure with two conductive materials and a dielectric material between the conductors. For example, an e-textile can be designed with two conductive fiber layers separated by a dielectric layer, as shown in Figure 31. A CFAN can be implemented if one conductive fiber layer is Vcc and the other is ground. Therefore, power and data can be transmitted through a physical structure based on this layered design. In Figure 31, ① represents Vcc, ② represents ground, ③ represents dielectric, and ④ represents the e-textile. As another example, a CFAN capable of transmitting power and data can be designed based on a linear cable. A flexible coaxial cable can have multiple layers, consisting of inner and outer conductor layers and a dielectric layer between them, as shown in Figure 32. The design choices of the coaxial cable affect its size, data transmission, power attenuation, strength, flexibility, and cost. In Figure 32, ① represents Vcc, ② represents ground, ③ represents the dielectric, and ④ represents the coaxial cable. Additionally, CFANs can be designed using a non-conductive material (insulating material) and a conductive material arranged in parallel in two regions. The two regions can be configured to be parallel to each other. For the design of a CFAN incorporated into clothing, as shown in Fig. 33, conductive fibers can be used as the conductive material and general fabrics can be used as the insulating material. In Fig. 33, ① represents Vcc, ② represents ground, ③ represents general fabric, and ④ represents clothing. Figure 34 is a block diagram showing the configuration of a network system according to the first embodiment of the present invention. A network system (10) according to the first embodiment of the present invention includes a main wired network device (100) and a sub wired network device (200). There may be a plurality of sub wired network devices (200) included in the network system (10). The main wired network device (100) or the sub wired network device (200) may include a conductive fiber area network. It goes without saying that both the main wired network device (100) and the sub wired network device (200) may include a conductive fiber area network. The main wired network device (100) and the sub wired network device (200) can communicate with each other using at least one of wired communication and wireless communication. The main wired network device (100) and the sub wired network device (200) may each be included in different wearable devices. For example, the main wired network device (100) may be included in the upper garment, and the sub wired network device (200) may be included in the lower garment. In this specification, a wearable device refers to all devices that can be carried using the user's body or clothing, such as devices that can be worn in the form of clothing, as well as smartwatches, smart glasses, HMDs (Head-Mounted Displays), touch screens, eye trackers, devices that recognize the user's posture or movements, and auxiliary batteries. Although not shown in the drawing, the main wired network device (100) may further include a power supply device. The main wired network device (100) may wirelessly transmit power to the sub wired network device (200). Although not shown in the drawing, the sub-wired network device (200) may further include a capacitor using a conductive fiber layer as an electrode. The sub-wired network device (200) may charge the capacitor with power received from the main wired network device (100). In addition, the sub-wired network device (200) may transmit data collected from the outside or generated by itself to the main wired network device (100) using the power charged in the capacitor. A capacitor included in a sub-wired network device (200) may be configured to include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. The main wired network device (100) includes a first master node (110), a first slave node (120), and a repeater node (130). There may be multiple first slave nodes (120) or repeater nodes (130). The sub-wired network device (200) includes a second master node (210) and a second slave node (220). There may be multiple second slave nodes (220). When the main wired network device (100) includes a conductive fiber-based network, the first master node (110) transmits and receives data with the first slave node (120) and the repeater node (130) through the conductive fiber layer. The first slave node (120) may be a sensor capable of recognizing a user's bio-signals, posture, or motion, collects sensor data, and transmits the collected sensor data to the first master node (110) through the conductive fiber layer. When the sub-wired network device (200) includes a conductive fiber-based network, the second master node (210) transmits and receives data with the second slave node (220) through the conductive fiber layer. The second slave node (220) may be a sensor capable of recognizing a user's bio-signals, posture, or motion, collects sensor data, and transmits the collected sensor data to the second master node (210) through the conductive fiber layer. The repeater node (130) wirelessly transmits power to the second master node (210) and wirelessly transmits and receives data with the second master node (210). There is no limitation on the wireless communication method that the main wired network device (100) and the sub wired network device (200) can use. For example, the wireless communication method may be any one of Bluetooth, BLE (Bluetooth Low Energy), NFC (Near Field Communication), RFID (Radio Frequency Identification), Wi-Fi, Beacon, Zigbee communication, and UWB (Ultra Wide Band) communication, or a combination thereof. Meanwhile, there is no limitation on the method by which the main wired network device (100) wirelessly transmits power to the sub wired network device (200). For example, the main wired network device (100) may wirelessly transmit power to the sub wired network device (200) using a magnetic induction method or a magnetic resonance method. When the second slave node (220) transmits sensor data to the second master node (210), the second master node (210) can wirelessly transmit the sensor data to the repeater node (130). While the second master node (210) transmits data to the repeater node (130), the repeater node (130) can stop transmitting power to the second master node (210) to prevent interference from occurring during the data transmission process. Data transmitted and received between the repeater node (130) and the second master node (210) may include an identifier of the main wired network device (100), an identifier of the sub wired network device (200), an identifier of the node that sent the data (node ​​ID that serves as the source address), and an identifier of the node that receives the data (node ​​ID that serves as the destination address). For example, the node ID that serves as the source address may be an identifier of a sensor (220) included in the sub wired network device (200), and the node ID that serves as the destination address may be an identifier of a storage device (120) included in the main wired network device (100). When the main wired network device (100) includes a power supply device, the first master node (110) can transmit power supplied from the power supply device to a repeater node (130) through a conductive fiber layer. In addition, the repeater node (130) can wirelessly transmit power to the second master node (210). Although not shown in the drawing, the sub-wired network device (200) may include a capacitor using a conductive fiber layer as an electrode. In this case, the second master node (210) may charge the capacitor with power received from the repeater node (130). In addition, the second master node (210) may transmit data collected or generated by the sub-wired network device (200) to the repeater node (130) using the power charged in the capacitor. The capacitor included in the sub-wired network device (200) may be configured in a form that includes two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. Even if the content is omitted in the process of explaining the embodiment of Fig. 34, the content of Figs. 1 to 33 can be applied to the content of Fig. 34. In addition, the content of Fig. 34 can be applied to the content of Figs. 1 to 33. Embodiment of a network system in a conductive fiber region and a method for forming a connection between network devices in a conductive fiber region Hereinafter, an embodiment of a method for forming a connection between a network system and a network device according to the present invention is described. A network system according to one embodiment of the present invention includes a main wired network device and a sub-wired network device. The main wired network device and the sub-wired network device communicate with each other using at least one of wired communication and wireless communication. In one embodiment of the present invention, the main wired network device and the sub wired network device may each be included in different wearable devices. In one embodiment of the present invention, the main wired network device may further include a power supply device. In this case, the main wired network device may wirelessly transmit power to the sub wired network device. In one embodiment of the present invention, the sub-wired network device may further include a capacitor using a conductive fiber layer as an electrode. In this case, the sub-wired network device may charge the capacitor with power received from the main wired network device, and transmit data to the main wired network device using the power charged in the capacitor. In one embodiment of the present invention, the capacitor may include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. In one embodiment of the present invention, the main wired network device includes a first master node and a repeater node, and the sub wired network device includes a second master node. The first master node transmits and receives data with the repeater node via a conductive fiber layer, and the repeater node wirelessly transmits and receives data with the second master node. In one embodiment of the present invention, the sub-wired network device may further include a slave node that collects sensor data. In this case, the slave node may transmit the sensor data to the second master node, and the second master node may wirelessly transmit the sensor data to the repeater node. In one embodiment of the present invention, data transmitted and received between the repeater node and the second master node may include an identifier of the main wired network device; an identifier of the sub wired network device; an identifier of a node that transmitted the data; and an identifier of a node that receives the data. In one embodiment of the present invention, the main wired network device may further include a power supply device. In this case, the first master node may transmit power supplied from the power supply device to the repeater node via a conductive fiber layer, and the repeater node may wirelessly transmit power to the second master node. In one embodiment of the present invention, the main wired network device may further include a power supply device. In addition, the sub-wired network device may further include a capacitor using a conductive fiber layer as an electrode. In this case, the first master node transmits power supplied from the power supply device to the repeater node through the conductive fiber layer, and the second master node charges the capacitor with the power received from the repeater node, and transmits data generated by the sub-wired network device to the repeater node using the power charged in the capacitor. In one embodiment of the present invention, the capacitor may include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. In one embodiment of the present invention, the repeater node may stop transmitting power to the second master node when the second master node transmits data to the repeater node. In one embodiment of the present invention, either or both of the main wired network device and the sub wired network device may be devices including a conductive fiber area network. And, a method for forming a connection between wired network devices according to one embodiment of the present invention includes a step in which a main wired network device wirelessly transmits a connection request message to a sub wired network device; a step in which the sub wired network device transmits a connection response message to the main wired network device; and a step in which the main wired network device transmits a connection acknowledgement message to the sub wired network device. In one embodiment of the present invention, the connection confirmation message may include an identifier of the main wired network device and a network identifier assigned by the main wired network device to the sub wired network device. In one embodiment of the present invention, the step of transmitting the connection request message may include a step in which a first master node included in the main wired network device transmits the connection request message to a second master node of the sub-wired network device through a repeater node of the main wired network device; and a step in which the second master node transmits the connection request message to a slave node of the sub-wired network device. In one embodiment of the present invention, the step of transmitting the connection response message may include a step in which the slave node transmits the connection response message to the second master node; a step in which the second master node transmits the connection response message to the repeater node; and a step in which the repeater node transmits the connection response message to the first master node. In one embodiment of the present invention, the step of transmitting the connection confirmation message may include a step in which the first master node transmits the connection confirmation message to the second master node via the repeater node; and a step in which the second master node transmits the connection confirmation message to the slave node. In this case, the connection confirmation message may include a node identifier assigned by the first master node to the slave node. And, a conductive fiber area network system according to one embodiment of the present invention includes one main conductive fiber area network device having a plurality of nodes and one or more sub-conductive fiber area network devices having a plurality of nodes. Each of the network devices is incorporated into a different garment or body mount and communicates with each other using at least one of wired and wireless communication means. Modified embodiment of a network system in a conductive fiber region and a method for forming a connection between network devices in a conductive fiber region [1] Transition of the main network A conductive fiber area network system according to one embodiment of the present invention may be composed of a plurality of conductive fiber area network devices. For example, a single piece of body equipment, such as clothing or a wearable suit, may include multiple conductive fiber area network devices. For example, socks, gloves, a scarf, and a hat worn by a user, in addition to the top and bottom, may each form a new conductive fiber area network. In a conductive fiber area network system according to one embodiment of the present invention, when a plurality of conductive fiber area network devices are configured, each network device corresponds to a main wired network device or a sub-wired network device, and through message exchange between the network devices, the main wired network device can be converted into a sub-wired network device, or the sub-wired network device can be converted into a main wired network device. For reference, in this modified embodiment, it is assumed that the main wired network device is a device that wirelessly provides power to the sub-wired network device. That is, a conductive fiber area network system according to one embodiment of the present invention includes a first wired network device equipped with a battery and a second wired network device equipped with a battery, wherein the first wired network device and the second wired network device communicate with each other using at least one communication means among wired communication and wireless communication, wherein the first wired network device and the second wired network device include a power supply device, wherein the first wired network device and the second wired network device determine one of the two devices as a main wired network device and the other device as a sub-wired network device through message exchange between the two devices, and wherein the main wired network device wirelessly transfers power to the sub-wired network device. When each conductive fiber area network device is equipped with a battery, whether it is the main wired network device can be determined based on the battery's charge status or operating status. For example, even if a wired network device is equipped with a battery, if the battery is not operating, the wired network device can be set as a sub-wired network device. Furthermore, if the battery equipped in the sub-wired network device is fully charged, the sub-wired network device can be set as the main wired network device. Furthermore, if a battery is equipped in a sub-wired network device that was not equipped with a battery, the sub-wired network device can be set as the main wired network device. In another embodiment, a mobile device can be newly added to the conductive fiber area network system according to one embodiment of the present invention. For example, a smartphone can become a new wired network device in the network system, forming a connection with an existing wired network device to become the new main wired network device. In this case, the smartphone can serve as the main controller of the conductive fiber area network system, performing functions such as biosignal monitoring and network control. Meanwhile, in relation to the role change of the main wired network or sub wired network, a protocol for status change between networks (allocation of an identifier designating the main wired network) led by the existing main wired network according to the occurrence of an event resulting from a change in battery connection status or remaining battery level, and a data format (status value) included in the message used for the status change will be required. [2] Switching the function of the node [1] In relation to this, a conductive fiber area network device included in a conductive fiber area network system according to one embodiment of the present invention may include a node capable of operating as a master node and a repeater node in parallel. For example, assuming a situation in which two wired network devices are included in a conductive fiber area network system, when an existing main wired network device (the first device) is converted into a sub-wired network device and an existing sub-wired network device (the second device) is converted into a main wired network device, the repeater node of the first device must be able to receive power from the master node of the second device, and the master node of the second device must be able to transmit power to the repeater node of the first device. Therefore, the node responsible for the connection between the first device and the second device must be a node that can perform the roles of a repeater node and a master node in parallel. In other words, a node that can perform the roles of a repeater node and a master node in parallel is a node that can perform both the roles of a transmitter and a receiver of wireless power transfer. [3] Interconnectivity between power transmission and data transmission In a conductive fiber area network system according to one embodiment of the present invention, power and data transmission are performed between a repeater node of a main wired network and a master node of a sub-wired network. At this time, the master node of the main wired network performs scheduling to prevent power and data transmission from being performed simultaneously, and suspends data transmission while power transmission is being performed through communication with the sub-wired network, or transmits a message to the repeater node of the main wired network so that the repeater node of the main wired network suspends power transmission to the master node of the sub-wired network while the sub-wired network is transmitting data. The master node of the main wired network can determine the priority of power and data transmission. For example, the criteria for determining the priority may be the charge status of a battery installed in the sub-wired network, the charge status of a battery installed in the main wired network, or the importance of data to be transmitted. If a specific biosignal exceeds a threshold, the importance of the corresponding biosignal data may be increased. [4] Example where there are multiple main wired networks [1] In relation to [1], a conductive fiber area network system according to an embodiment of the present invention may include a plurality of main wired networks and a plurality of sub-wired networks. In this case, each main wired network manages the network area it is responsible for by distinguishing it. Each main wired network determines the sub-wired network it is responsible for through message exchanges between them. For example, the sub-wired network in charge may be determined through message exchanges regarding the battery connection status and battery charge status of each wired network and application of preset rules between the main wired networks. This modified embodiment operates in a manner in which a plurality of main wired network devices coexist in one conductive fiber area network system, and each main wired network device transmits power only to the sub-wired network corresponding to the area in charge. Figure 35 is a block diagram illustrating the configuration of a network system according to a second embodiment of the present invention. The network system according to the second embodiment differs from the first embodiment in that the main wired network device and the sub-wired network device are not determined in advance, but rather the main wired network device is determined through communication between the wired network devices. This feature allows for flexible power balance among the wired network devices included in the network system by changing the power supply source according to the charging status of each wired network device. A network system (20) according to a second embodiment of the present invention includes a first wired network device (300) and a second wired network device (400). The network system (20) may include a plurality of wired network devices. For example, the network system (20) may include three or more wired network devices. The first wired network device (300) and / or the second wired network device (400) may include a conductive fiber area network (CFAN). Therefore, the network system (20) may be applied with all of the above-described CFAN connection methods (Fig. 6) and extended CFAN connection methods (Fig. 7), as well as the connection methods and connection formation methods between the conductive fiber area network system and the conductive fiber area network devices described herein. That is, the first wired network device (300) and the second wired network device (400) may be conductive fiber area network devices. The first wired network device (300) and the second wired network device (400) can communicate with each other using at least one of wired communication and wireless communication. The first wired network device (300) and the second wired network device (400) may each be included in different wearable devices. For example, the first wired network device (300) may be included in an upper garment, and the second wired network device (400) may be included in a lower garment. In this specification, a wearable device refers to any device that can be carried by using the user's body or clothing, such as a device that can be worn in the form of clothing, as well as a smartwatch, smart glass, HMD (Head-Mounted Display), touch screen, eye tracker, a device that recognizes the user's posture or movement, and an auxiliary battery. Although not illustrated in the drawing, the first wired network device (300) and / or the second wired network device (400) may further include a power supply device. The first wired network device (300) and the second wired network device (400) may transmit power wirelessly in both directions. That is, either the first wired network device (300) or the second wired network device (400) may serve as a power supply source. Although not shown in the drawing, the first wired network device (300) and / or the second wired network device (400) may further include a capacitor having the conductive fiber layer as an electrode. The first wired network device (300) and / or the second wired network device (400) may charge the capacitor with the transmitted power. The capacitor may be configured to include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. And, either one of the first wired network device (300) and the second wired network device (400) can transmit data collected from the outside or generated by itself to the other wired network device using the power charged in the capacitor. As illustrated in FIG. 35, the first wired network device (300) includes a first master node (310), a first slave node (320), and a first repeater node (330). There may be a plurality of first slave nodes (320) and / or first repeater nodes (330). In addition, the second wired network device (400) includes a second master node (410), a second slave node (420), and a second repeater node (430). There may be a plurality of second slave nodes (420) and / or second repeater nodes (430). The nodes (310, 320, 330, 410, 420, 430) included in the network system (20) may include an impedance matching circuit, a battery, a processor, and a memory. For example, a node included in the network system (20) may be a smartphone or an IoT device. In addition, a repeater node (330, 430) included in the network system (20) may further include a wireless communication device (Wi-Fi, ZigBee, RF, etc.), an antenna, a coil, or a rectifier circuit. When a wired network device (300, 400) included in a network system (20) includes a conductive fiber-based network, a master node (310, 410) transmits and receives data with slave nodes (320, 420) and repeater nodes (330, 430) through a conductive fiber layer. The slave node (320, 420) may be a sensor capable of recognizing a user's bio-signals, posture, or motion, collects sensor data, and transmits the collected sensor data to the master node (310, 410) through the conductive fiber layer. Repeater nodes (330, 430) can wirelessly transfer power to each other or transmit and receive data via wireless communication. In addition, repeater nodes (330, 430) can transmit and receive data with the master node (310, 410). There is no limitation on the wireless communication method that the first wired network device (300) and the second wired network device (400) can use. For example, the wireless communication method can be any one of Bluetooth, BLE (Bluetooth Low Energy), NFC (Near Field Communication), RFID (Radio Frequency Identification), Wi-Fi, Beacon, Zigbee communication, and UWB (Ultra Wide Band) communication, or a combination thereof. Meanwhile, the present invention does not limit the method of wirelessly transferring power between wired network devices (300, 400). For example, a first wired network device (300) can wirelessly transmit power to a second wired network device (400) using magnetic induction or magnetic resonance, and vice versa. Meanwhile, if data transmission starts between the first wired network device (300) and the second wired network device (400) while power is being transmitted between the first wired network device (300) and the second wired network device (400), the power transmission may be interrupted during the data transmission time. For example, if data transmission starts between the first wired network device (300) and the second wired network device (400) while power is being transmitted from the first repeater node (330) to the second repeater node (430), the second slave node (420) may transmit sensor data to the second master node (410), and the second master node (410) may wirelessly transmit sensor data to the first repeater node (330) via the second repeater node (430). In order to prevent interference from occurring during the data transmission process before or while the second repeater node (430) transmits sensor data to the first repeater node (330), the first repeater node (330) may stop transmitting power to the second repeater node (430) by itself or under the control of the first master node (310). Data transmitted and received between repeater nodes (330, 430) may include an identifier of a wired network device (300, 400), an identifier of a node that transmitted the data (node ​​ID serving as a source address), and an identifier of a node that receives the data (node ​​ID serving as a destination address). For example, the node ID serving as a source address may be an identifier of a sensor that is one of the second slave nodes (420) included in the second wired network device (400), and the node ID serving as a destination address may be an identifier of a data storage device that is one of the first slave nodes (320) included in the first wired network device (300). When a wired network device (300, 400) includes or is connected to a separate power supply device, the master node (310, 410) can transmit power supplied from the power supply device to a slave node (320, 420) or a repeater node (330, 430) through a conductive fiber layer. In addition, the repeater node (330, 430) can wirelessly transmit power to the counterpart repeater node (430, 330). Although not shown in the drawing, the wired network device (300, 400) may include a capacitor using a conductive fiber layer as an electrode. In this case, the master node (310, 410) may charge the capacitor with power received from the repeater node (330, 430). In addition, the master node (310, 410) may transmit data collected or generated by the wired network device (300, 400) to the counterpart repeater node (430, 330) via the repeater node (330, 430) using the power charged in the capacitor. The above-described capacitor may be configured to include two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers. In a network system according to a second embodiment of the present invention, a main network device is determined from among a plurality of wired network devices. The main network device can be determined automatically or manually. The user can manually determine the main network device according to their own preferences, or determine the criteria (or "criteria information") used when automatically determining the main network device. The criteria (or "criteria information") may include remaining battery charge, the start time of operation, or the data transmission entity. In this specification, reference information corresponding to a specific wired network device is referred to as 'operation information'. The first wired network device (300) and the second wired network device (400) can determine one of the first wired network device (300) and the second wired network device (400) as the main network device based on the reference information of the main network device, and can determine the other device as the sub-network device. For example, the first master node (310) requests the second master node (410) for reference information for determining the main network through the first repeater node (330) and the second repeater node (430). The reference information may be the remaining charge level of the battery mounted on the second wired network device (400) or the operation start time of the second wired network device (400). The second master node (410) transmits the reference information for determining the main network to the first master node (310) through the second repeater node (430) and the first repeater node (330). When the first master node (310) receives the reference information for determining the main network from the second master node (410), the first master node (310) determines one of the first wired network device (300) and the second wired network device (400) as the main network device based on the reference information, and determines the other as the sub-network device. If the above reference information is the remaining battery charge, the first master node (310) determines the second wired network device (400) as the main network device and determines the first wired network device (300) as the sub-network device if the remaining battery charge of the battery mounted on the second wired network device (400) is greater than the remaining battery charge of the battery mounted on the first wired network device (300). In addition, as another example, if the above reference information is the operation start time, the first master node (310) determines the first wired network device (300) as the main network device if the operation start time of the first wired network device (300) is before the operation start time of the second wired network device (400). As another example, the reference information for determining the main network when automatically determining the main network device may be the data receiving entity. In this case, the wired network device that is the data transmitting entity may become the sub-network device, and the wired network device that is the data receiving entity (the wired network device that transmitted the data transmission request message) may become the main network device. For example, if the first wired network device (300) is the data transmitting entity and the remaining charge of the second wired network device (400) is equal to or greater than the set minimum remaining charge, the first wired network device (300) becomes the sub-network device, and the second wired network device (400) that will receive the data becomes the main network device. In this case, the second wired network device (400) transmits the power required for data transmission to the first wired network device (300), and the first wired network device (300) transmits power to the second wired network device (400) using the transmitted power. Meanwhile, the first wired network device (300) and the second wired network device (400) may perform impedance matching between internal nodes when the device is powered on, when a new device is added to the network, or at regular intervals. For example, in a conductive fiber area network where multiple nodes are interconnected, problems with signal integrity and power efficiency may arise as the node density increases. When impedance mismatch occurs between nodes, the performance of the wired network device significantly deteriorates and power consumption increases, so optimal impedance matching is necessary for a multi-node conductive fiber area network. For example, in a wired network device where each node is connected to a conductive fiber area network, the interaction between the conductive fiber and the node affects the network impedance, and a newly added node may change the overall impedance, thereby affecting signal integrity. Therefore, appropriate impedance matching is essential to minimize signal reflections and ensure network stability as the node density increases. The master node (310, 410) can perform impedance matching with one or more slave nodes (320, 420) or repeater nodes (330, 430) by applying a predetermined impedance matching technique. The above impedance matching technique can be any one of complex conjugate matching, equal impedance matching, and voltage maximization matching. Among these, complex conjugate matching is effective in minimizing reflections by creating a balanced network that facilitates energy flow. However, when many nodes are introduced into the network of wired network devices, it requires recalibration that changes the entire network impedance, which complicates the impedance matching process. Therefore, complex conjugate matching may be an impractical choice from the perspective of expanding wired network devices. Equal impedance matching is a method that standardizes impedances across all nodes in the network. Although it may not achieve an optimal power transmission rate, it is a suitable method for ensuring network stability and reliability in environments where node density frequently changes. In addition, voltage maximization matching is an impedance matching technique that aims to optimize voltage transmission to the receiver by finely adjusting the resistance of the transmitter and receiver, and the voltage of the receiver can be expressed as in mathematical equation 3. In mathematical expression 3, V R is the voltage at the receiver, and V T is the input voltage of the transmitter, and R R is the resistance of the receiver, R T is the resistance of the transmitting end, and N is the number of nodes of the receiving end. For example, the master node (310, 410) can perform impedance matching through voltage maximization matching by setting itself as the transmitting end of mathematical expression 3 and setting one or more as the receiving end of mathematical expression 3. The master node (310, 410) is R TImpedance matching can be achieved by gradually lowering the (transmitter resistance). This approach increases voltage transmission efficiency, making it effective in supporting high-density conductive fiber area networks with many nodes. Figure 36 is a flowchart illustrating an operating method of a network system according to a second embodiment of the present invention. The operating method can be performed by a network system (20). As illustrated in Figure 35, the network system (20) includes a first wired network device (300) and a second wired network device (400). Referring to FIG. 36, the operating method of a network system according to one embodiment of the present invention comprises steps S510 to S640. The operating method of the network system illustrated in FIG. 36 is according to one embodiment, and the steps of the operating method of the network system according to the present invention are not limited to the embodiment illustrated in FIG. 36, and may be added, changed, or deleted as needed. Steps S510 and S520 are impedance matching steps. When the first wired network device (300) and the second wired network device (400) are powered on, the first wired network device (300) and the second wired network device (400) check the nodes connected to the network inside each device, and perform impedance matching if a node is added. For example, the first master node (310) checks whether a new first slave node (320) has been added to the network of the first wired network device (300). If a new first slave node (320) has been added to the network within the first wired network device (300), the first master node (310) adjusts the impedance between the first master node (310) and all first slave nodes (320) in real time by applying a predetermined impedance matching technique. The impedance matching technique performed by the first master node (310) or the second master node (410) may be any one of complex conjugate matching, equal impedance matching, and voltage maximization matching. Step S530 is the connection step. The first master node (310) or the first slave node (320) can form a connection with the second master node (410) or the second slave node (420) via the first repeater node (330) and the second repeater node (430). Conversely, the second master node (410) or the second slave node (420) can also form a connection with the first master node (310) or the first slave node (320) via the second repeater node (430) and the first repeater node (330). This connection formation process can be performed according to the connection method of the extended CFAN of FIG. 7. For example, the second master node (410) transmits a connection request packet to the first master node (310) via the second repeater node (430) and the first repeater node (330), and the first master node (310) transmits the connection request packet to the first slave node (320). The first slave node (320) transmits a connection response packet to the first master node (310), and the first master node (310) transmits a connection response packet to the second master node (410) via the first repeater node (330) and the second repeater node (430). The determination of the main network device can be made automatically or manually, depending on the settings. If the determination of the main network device is made manually, steps S540 to S570 are omitted. If the determination of the main network device is set to be made automatically, the first master node (310) and the second master node (410) can determine a master node that will determine the main network device during this process. For example, the first master node (310) and the second master node (410) can determine a master node with an earlier (earlier) start time as the master node that will determine the main network device, based on the start time of operation (On). As another example, the first master node (310) and the second master node (410) can each randomly generate a number greater than or equal to 0 and less than 1, and determine the master node that generates a larger number as the master node that will determine the main network device. In this embodiment, it is assumed that the first master node (310) is determined as the master node that will determine the main network device. Step S540 is the step that requests reference information for main network decision. The first master node (310) requests the second master node (410) for reference information for main network decision through the first repeater node (330) and the second repeater node (430). The above-mentioned reference information may be the remaining charge level of the battery installed in the second wired network device (400), the start time of the operation of the second wired network device (400), or whether the second wired network device is the data transmitter (whether the second wired network device is the data transmitter). If the criterion for determining the main network is the 'data receiver', data transmission is given a higher priority than power transmission. In this case, it becomes a key task for the wired network device that is the data receiver to transmit the power required for the wired network device that is the data transmitter (e.g., enough power to transmit data without interruption). Step S550 is the step that transmits reference information for main network decision. The second master node (410) transmits the reference information for the main network decision to the first master node (310) through the second repeater node (430) and the first repeater node (330). Step S560 is the main network decision step. When the first master node (310) receives the reference information for determining the main network from the second master node (410), the first master node (310) determines one of the first wired network device (300) and the second wired network device (400) as the main network device based on the reference information, and determines the other as the sub-network device. For example, if the remaining charge of the battery mounted on the second wired network device (400) is greater than the remaining charge of the battery mounted on the first wired network device (300), the first master node (310) may determine the second wired network device (400) as the main network device and the first wired network device (300) as the sub-network device. As another example, the first master node (310) may determine the first wired network device (300) as the main network device if the operation start time of the first wired network device (300) is before the operation start time of the second wired network device (400). This embodiment assumes that the second wired network device (400) is determined as the main network device and the first wired network device (300) is determined as the sub-network device, and explains the subsequent steps. Step S570 is the step of transmitting a main network device decision completion message. The first master node (310) transmits a main network device determination completion message to the second master node (410) via the first repeater node (330) and the second repeater node (430). The message includes a determination result that the second wired network device (400) has been determined as the main network device. Step S580 is the step of transmitting a power transfer request message. The first master node (310) can check the remaining charge of the battery mounted on the first wired network device (300), and if the remaining charge is less than a predetermined threshold, can transmit a power transmission request message to the second master node (410) through the first repeater node (330) and the second repeater node (430). Step S590 is the step of transmitting a power transfer request approval message. The second master node (410) checks the remaining charge of the battery mounted on the second wired network device (400), and if the remaining charge is greater than a predetermined threshold, it can transmit a power transmission request approval message to the first master node (310) through the second repeater node (430) and the first repeater node (410). The approval message is a response message to the power transmission request message of step S580. The S600 stage is the power transfer stage. The second repeater node (430) wirelessly transmits power to the first repeater node (330). The first repeater node (330), which receives power from the second repeater node (430), transmits power to the first master node (310) or the first slave node (320) under the control of the first master node (310). Step S610 is the step of transmitting a data transmission request message. In this embodiment, it is assumed that a second slave node (420) requests data transmission to the first slave node (320). The second slave node (420) transmits the conditions of the data to be requested from the first slave node (320) (e.g., the type and period of the data - which may be a query) to the second master node (410), and the second master node (410) generates a data transmission request message based on the conditions. The second master node (410) transmits the data transmission request message to the first master node (310) through the second repeater node (430) and the first repeater node (330). Step S620 is the step of transmitting a data transmission request approval message. The first master node (310) determines whether to approve a data transmission request message through communication with the first slave node (320). For example, the data transmission request message may be a request message for an EEG signal for a specific time period, and the first master node (310) may determine whether to approve the message by confirming whether to provide an EEG signal for the time period through communication with the first slave node (320), which is a device storing EEG signals. For example, the first master node (310) may parse the data transmission request message to extract conditions of the requested data, and based on the extracted conditions, may query the first slave node (320) as to whether to provide data, and may determine whether to approve the message based on a response to the query. If the first master node (310) determines that the data transmission request message is approved, the first master node (310) transmits a data transmission request approval message to the second master node (410) via the first repeater node (330) and the second repeater node (430). That is, the data transmission request approval message is a response message to the data transmission request message. According to an additional embodiment of the present invention, the first master node (310) calculates the amount of data to be transmitted (or data transmission time) that the first repeater node (330) should transmit to the second repeater node (430) in response to the data transmission request message, and calculates the amount of power required for data transmission ('necessary power') based on the amount of data to be transmitted (or data transmission time) and a predetermined reference table (e.g., data sheet of a chipset manufacturer of a device corresponding to the repeater node). If the required power (C b ) is the remaining charge level (C) of the battery mounted on the first wired network device (300). a ) is greater than or equal to the required power (C c = C b - C a + α) and generates a power transmission request message including the required power amount. Here, α is a set value. The first master node (310) transmits a power transmission request message including the required power amount to the second master node (410) through the first repeater node (330) and the second repeater node (430). Thereafter, steps S580 to S600 are performed, and the first master node (310) checks whether power transmission equivalent to the required power amount has been performed, and if power transmission equivalent to the required power amount has been performed, steps S630 and S640 are performed. Meanwhile, depending on the amount of data transmitted, the data transmission time interval and power transmission time interval may be divided into multiple intervals. For example, if the amount of data transmitted is greater than a predetermined threshold (e.g., 100 MB), the data transmission amount may be transmitted over multiple power transmission time intervals and multiple data transmission time intervals. The number of time intervals may be determined by the master node of the main network device. For example, if the number of time intervals is 2, the power transmission time interval and the data transmission time interval are repeated twice each (power transmission - data transmission - power transmission - data transmission). Step S630 is the step where power transmission is stopped. The second master node (410), which is the master node of the second wired network device (400), which is the main network device, determines whether data transmission occurs between the second repeater node (430) and the first repeater node (330). If data transmission occurs between the second repeater node (430) and the first repeater node (330), the second master node (410) controls the second repeater node (430) not to transmit power to the first repeater node (330). For example, when the second master node (410) receives a data transmission request approval message transmitted by the first wired network device (300) from the second repeater node (430), the second master node (410) determines that data transmission is taking place between the second repeater node (430) and the first repeater node (330), and, in order to avoid interference, the second repeater node (430) can be controlled not to transmit power to the first repeater node (330) until the data transmission is completed. Step S640 is the data transfer step. When the first master node (310) determines that the first repeater node (330) is not receiving power, it collects data from the first slave node (320) and transmits the collected data to the second master node (410) via the first repeater node (330) and the second repeater node (430). The second master node (410) transmits the received data to the second slave node (420). Even if the content is omitted in the process of explaining the embodiments of FIGS. 35 and 36, the content of FIGS. 1 to 34 and FIG. 37 can be applied to the content of FIGS. 35 and 36. In addition, the content of FIGS. 35 and 36 can be applied to the content of FIGS. 1 to 34 and FIG. 37. The method of operation of the aforementioned network system has been described with reference to the flowchart presented in FIG. 36. For simplicity, the method has been depicted and described as a series of blocks; however, the present invention is not limited to the order of the blocks, and some blocks may occur in a different order or simultaneously with other blocks than depicted and described herein, and various other branches, flow paths, and block orders that achieve the same or similar results may be implemented. Furthermore, not all of the blocks depicted may be required to implement the method described herein. In the description with reference to FIG. 36, each step may be further divided into additional steps or combined into fewer steps, depending on the implementation of the present invention. Figure 37 is a block diagram illustrating a computer system for implementing a method according to an embodiment of the present invention. A network device or a node included in a network device according to an embodiment of the present invention may include the computer system of Figure 37. Referring to FIG. 37, a computer system (1000) may include at least one of a processor (1010), a memory (1030), an input interface device (1050), an output interface device (1060), and a storage device (1040) that communicate via a bus (1070). The computer system (1000) may further include a communication device (1020) coupled to a network. The processor (1010) may be a central processing unit (CPU), or a semiconductor device that executes instructions stored in the memory (1030) or the storage device (1040). The memory (1030) and the storage device (1040) may include various forms of volatile or non-volatile storage media. For example, the memory may include a read-only memory (ROM) and a random access memory (RAM). In embodiments of the present disclosure, the memory may be located internally or externally to the processor, and the memory may be connected to the processor via various known means. Memory is a variety of volatile or non-volatile storage media, and may include, for example, read-only memory (ROM) or random access memory (RAM). Accordingly, embodiments of the present invention may be implemented as a computer-implemented method or as a non-transitory computer-readable medium storing computer-executable instructions. In one embodiment, when executed by a processor, the computer-readable instructions may perform a method according to at least one aspect of the present disclosure. The communication device (1020) can transmit or receive wired or wireless signals. In addition, the method according to the embodiment of the present invention may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc., either singly or in combination. The program commands recorded on the computer-readable medium may be specially designed and configured for embodiments of the present invention, or may be known and usable by those skilled in the art of computer software. The computer-readable recording medium may include a hardware device configured to store and execute the program commands. For example, the computer-readable recording medium may be a magnetic medium such as a hard disk, a floppy disk, and a magnetic tape, an optical medium such as a CD-ROM or a DVD, a magneto-optical medium such as a floptical disk, a ROM, a RAM, a flash memory, etc. The program commands may include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer through an interpreter, etc. Although the present invention has been described above with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below.

Claims

1. Including a first wired network device and a second wired network device, The above first wired network device, Contains a first master node and a first repeater node, The above second wired network device, Includes a second master node and a second repeater node, The above first repeater node and the above second repeater node communicate via wireless communication, The above first master node, Requesting operation information for determining a main network to the second master node through the first repeater node and the second repeater node, and when receiving the operation information from the second master node, determining one of the first wired network device and the second wired network device as a main network device and determining the other as a sub-network device based on the operation information. In network system.

2. In paragraph 1, The above operation information is, The remaining charge of the battery mounted on the above second wired network device, The above first master node, Determining the main network device based on the result of comparing the remaining charge of the battery mounted on the second wired network device with the remaining charge of the battery mounted on the first wired network device. In network system.

3. In paragraph 1, The above operation information is, The start time of operation of the above second wired network device, The first master node determines the main network device based on the result of comparing the start time of operation of the second wired network device and the start time of operation of the first wired network device. In network system.

4. In paragraph 1, The repeater node of the above main network device wirelessly transmits power to the repeater node of the above sub-network device. In network system.

5. In paragraph 4, The repeater node of the above sub-network device transmits power to the master node of the above sub-network device under the control of the master node of the above sub-network device. In network system.

6. In paragraph 4, The master node of the above main network device is, When data is transmitted between the repeater node of the main network device and the repeater node of the sub-network device, Controlling the repeater node of the above main network device so that it does not transmit power to the repeater node of the above sub-network device In network system.

7. In paragraph 1, The above first wired network device, further comprising one or more first slave nodes, The above first master node, When the first slave node is added to the network within the first wired network device, the impedance of the first master node and the first slave node is adjusted in real time by applying a predetermined impedance matching technique. In network system.

8. In the 7th paragraph, the impedance matching technique is, Voltage maximization matching technique In network system.

9. In paragraph 1, The above first wired network device and the above second wired network device, Conductive Fiber Area Network Devices In network system.

10. A method for operating a network system, comprising: a first wired network device including a first master node and a first repeater node; and a second wired network device including a second master node and a second repeater node, wherein the first repeater node and the second repeater node communicate in a wireless communication manner. A step in which the first master node requests operation information for determining the main network to the second master node through the first repeater node and the second repeater node; The step of the first master node receiving the operation information from the second master node; and A main network device determination step in which the first master node determines one of the first wired network device and the second wired network device as the main network device and the other as the sub-network device based on the operation information; A method of operating a network system including:

11. In paragraph 10, The above operation information is, The remaining charge of the battery mounted on the above second wired network device, The above main network device determination step is: The first master node determines the main network device based on the result of comparing the remaining charge of the battery mounted on the second wired network device with the remaining charge of the battery mounted on the first wired network device. How the network system works.

12. In paragraph 10, The above operation information is, The start time of operation of the above second wired network device, The above main network device determination step is: The first master node comprises comparing the start time of operation of the second wired network device with the start time of operation of the first wired network device, and determining the main network device based on the comparison result. How the network system works.

13. In paragraph 10, The repeater node of the main network device further comprises a step of wirelessly transmitting power to the repeater node of the sub-network device. How network systems work.

14. In paragraph 13, A step in which a repeater node of the sub-network device transmits power to a master node of the sub-network device under the control of the master node of the sub-network device; A method of operating a network system further comprising:

15. In paragraph 13, A step of determining whether data transmission is taking place between a master node of the main network device and a repeater node of the sub-network device; and A step of controlling, by the master node of the main network device, the repeater node of the main network device not to transmit power to the repeater node of the sub-network device when data transmission occurs between the repeater node of the main network device and the repeater node of the sub-network device; A method of operating a network system further comprising:

16. In paragraph 10, The first wired network device further comprises one or more first slave nodes, The method of operation of the above network system is as follows: The step of the first master node checking whether the first slave node has been added to the network within the first wired network device; and When the first slave node is added to the network within the first wired network device, the first master node further includes a step of adjusting the impedance of the first master node and the first slave node in real time by applying a predetermined impedance matching technique. How the network system works.

17. In the 16th paragraph, the impedance matching technique is, Voltage maximization matching technique How the network system works.

18. In paragraph 10, The above first wired network device and the above second wired network device, Conductive Fiber Area Network Devices How the network system works.

Images