Conductive fiber network system

Abstract

The present invention relates to a conductive fiber area network system. The conductive fiber area network system according to the present invention includes a 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 may be included in a different wearable device, and they communicate with each other using at least one of wired communication and wireless communication.

Description

[Technical Field]

[0001] The present invention relates to a network system of conductive textile regions. [Background technology]

[0002] One of the most exciting technology trends over the past decade has been the rapid development of wearable devices. From the first wearable computers like smartwatches to soft shoes that help people walk again, smart textiles have emerged as a promising material for creating wearable devices like stretch sensors that can track movement and sense body posture, or soft sensors for wearable robots and virtual reality. While body area networks in wearable textiles still have challenges to overcome, they also have the potential to change the way we live and work.

[0003] Wired communication, such as conductive yarn or printed conductive ink, has been used in body area networks since the late 2000s. However, wired communication has faced challenges in terms of durability, data transmission rate, and cost due to the proliferation of devices. Wireless communication can also be integrated into wearable devices to solve these issues. Nevertheless, wireless channels can be vulnerable to eavesdroppers and interference, requiring strong protocols, and setting up wireless links between nodes requires every node to have its own battery, adding weight to the fabric per device.

[0004] As the number of wearable devices increases and the demand for smart services grows, it is important to develop protocols that simultaneously provide data and energy to reduce the number of cables and battery supplies around the body per device and enhance security. To manage and control a network with many nodes in conductive textiles, a conductive textile domain network protocol must be created to exchange the necessary data and control instructions.

[0005] Additionally, conductive textile area networks require a robust system architecture and flexible design that can adapt to new operating environments, standards, and markets. Summary of the Invention [Problem to be solved by the invention]

[0006] The present invention provides a network system of conductive fiber regions that can transmit and receive data through a conductive fiber layer.

[0007] Another object of the present invention is to provide a network system of a conductive fiber region in which the interconnected parts of a garment including a conductive fiber network transmit power and data wirelessly to perform charging and data storage management, and sensors connected to the conductive fiber network collect and store various information such as the physical condition of the garment wearer, allowing the wearer to query the information or check the analysis results whenever necessary.

[0008] The objects of the present invention are not limited to those mentioned above, and other objects not mentioned will be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0009] A network system according to an embodiment of the present invention includes a main wired network device and a sub wired network device, and 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.

[0010] In one embodiment of the present invention, the main wired network device and the sub wired network device may be included in different wearable devices.

[0011] In one embodiment of the present invention, the main wired network device may further include a power supply device, in which case the main wired network device may wirelessly transmit power to the sub wired network device.

[0012] In one embodiment of the present invention, the sub-wired network device may further include a capacitor having a conductive fiber layer as an electrode, in which case the sub-wired network device may charge the capacitor with power transmitted from the main wired network device and transmit data to the main wired network device using the power charged in the capacitor.

[0013] 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.

[0014] 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, where the first master node transmits and receives data to and from the repeater node through a conductive fabric layer, and the repeater node transmits and receives data to and from the second master node wirelessly.

[0015] In one embodiment of the present invention, the sub-wired network device may further include a slave node that collects sensor data, in which 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.

[0016] In one embodiment of the present invention, the 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 the node that sent the data; and an identifier of the node that receives the data.

[0017] In one embodiment of the present invention, the main wired network device may further include a power supply device, in which case the first master node may transmit power supplied from the power supply device to the repeater node through a conductive fabric layer, and the repeater node may wirelessly transmit power to the second master node.

[0018] In one embodiment of the present invention, the main wired network device may further include a power supply device, and the sub wired network device may further include a capacitor using a conductive fabric 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 fabric layer, and the second master node charges the capacitor with power transmitted 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.

[0019] 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.

[0020] In one embodiment of the present invention, the repeater node may suspend the operation of transmitting power to the second master node when the second master node transmits data to the repeater node.

[0021] In one embodiment of the present invention, any one or all of the main wired network device and the sub wired network device may be a device including a conductive fiber area network.

[0022] A method for establishing a connection between wired network devices according to one embodiment of the present invention includes a step of a main wired network device wirelessly transmitting a connection request message to a sub wired network device; a step of the sub wired network device transmitting a connection response message to the main wired network device; and a step of the main wired network device transmitting a connection acknowledgement message to the sub wired network device.

[0023] 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.

[0024] In one embodiment of the present invention, the step of transmitting the connection request message may include a step of a first master node included in the main wired network device transmitting 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 of the second master node transmitting the connection request message to a slave node of the sub wired network device.

[0025] In one embodiment of the present invention, the step of transmitting the connection response message may include the steps of: the slave node transmitting a connection response message to the second master node; the second master node transmitting the connection response message to the repeater node; and the repeater node transmitting the connection response message to the first master node.

[0026] In one embodiment of the present invention, the step of transmitting the connection confirmation message may include the steps of: the first master node transmitting the connection confirmation message to the second master node through the repeater node; and the second master node transmitting the connection confirmation message to the slave node. In this case, the connection confirmation message may include a node identifier assigned to the slave node by the first master node.

[0027] The conductive fiber area network system according to one embodiment of the present invention includes a 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 which is included in a different garment or body-worn device and communicates with the other using at least one of wired communication and wireless communication. [Effects of the Invention]

[0028] According to one embodiment of the present invention, many nodes on a conductive textile network can be controlled simply and efficiently.

[0029] Furthermore, according to one embodiment of the present invention, it is possible to provide services to multiple nodes and multiple conductive fiber area networks through an efficient time strategy mechanism of the communication infrastructure.

[0030] The effects that can be obtained by the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief explanation of the drawings]

[0031] [Figure 1] This is the superframe structure of CFAN. [Figure 2] 1 is a diagram showing the structure (physical elements) of a CFAN. [Figure 3] CFAN-M state diagram. [Figure 4] This is a state diagram of CFAN-S. [Figure 5] This is a state diagram of CFAN-R. [Figure 6] 1 is a diagram showing a method for connecting CFANs. [Figure 7] 10 is a diagram showing a method of connecting an extended CFAN. [Figure 8] 1 is a diagram showing a method for separating CFAN. [Figure 9] 10 is a diagram showing a method for separating an extended CFAN. [Figure 10] 1 is a diagram showing a method for checking the connection status of a CFAN. [Figure 11] 10 is a diagram illustrating a method for checking the connection status of an extended CFAN. [Figure 12] 1 is a diagram illustrating a data transmission method during a response interval of a CFAN. [Figure 13] 1 is a diagram illustrating a data transmission method during a response interval of an extended CFAN. [Figure 14] 1 is a diagram showing a data transmission method in an autonomous section of a CFAN. [Figure 15] 1 is a diagram illustrating a data transmission method in an autonomous section of an extended CFAN. [Figure 16] 10 is a diagram illustrating a group ID setup method. [Figure 17] 1 is a diagram showing a group ID setup method for an extended CFAN. [Figure 18] 1 is a diagram illustrating a physical layer frame format. [Figure 19] 1 is a diagram relating to a preamble format. [Figure 20] 1 is a diagram relating to a header format. [Figure 21] 10 is a diagram of an encoder of a header check sequence. [Figure 22] 1 is a diagram relating to a payload format. [Figure 23] 1 is a diagram regarding the definition of NRZ-L coding. [Figure 24] 1 is a diagram relating to ASK modulation. [Figure 25] 1 is a diagram relating to GFSK modulation. [Figure 26] 1 is a diagram of a preamble encoding and modulation process. [Figure 27] 1 is a diagram of a header encoding and modulation process. [Figure 28] 1 is a diagram of the payload encoding and modulation process. [Figure 29] 1 is a diagram relating to a GFSK modulated signal. [Figure 30] 1 is a diagram relating to an ASK modulated signal. [Figure 31] This is a design drawing of a flat smart textile. [Figure 32] This is a design drawing of a linear yarn. [Figure 33] 1 is a diagram showing an example of a CFAN designed using parallel-arranged conductive materials. [Figure 34] 1 is a block diagram illustrating a network system according to an embodiment of the present invention. [Figure 35] FIG. 1 is a block diagram illustrating a computer system for implementing a method according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0032] The advantages and features of the present invention, as well as methods for achieving them, will become clearer with reference to the following detailed description of the embodiments in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be embodied in various different forms. These embodiments are provided so that this disclosure will be complete and will fully convey the scope of the invention to those skilled in the art. The present invention is defined solely by the scope of the claims. Meanwhile, the terms used in this specification are for the purpose of describing the embodiments and are not intended to limit the present invention. In this specification, the singular forms "a," "an," and "an" also include the plural forms unless otherwise stated. As used in the specification, "comprises" and / or "comprising" do not exclude the presence or addition of one or more other components, steps, operations, and / or elements to a referenced component, step, operation, and / or element.

[0033] Terms such as "first," "second," etc. may be used to describe various components, but the components should not be limited by these terms. These terms may be used to distinguish one component from another. For example, a first component may be designated a "second component," and similarly, a second component may be designated a "first component," without departing from the scope of the present invention.

[0034] When a component is referred to as being "coupled" or "connected" to another component, it should be understood that it may be directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is referred to as being "directly coupled" or "directly connected" to another component, it should be understood that there are no other components in between. Other expressions describing the relationship between components, such as "between" and "immediately between," or "adjacent to" and "directly adjacent to," should be interpreted similarly.

[0035] In describing the present invention, if it is determined that a detailed description of related prior art may unnecessarily obscure the gist of the present invention, the detailed description will be omitted.

[0036] The following are definitions of key terms used in this specification:

[0037] Definition of Terms

[0038] WPT (Wireless power transfer)

[0039] A method for transferring power between devices without wires using electromagnetic fields

[0040] CFAN (Conductive fabric area network)

[0041] A network that uses conductive fibers to provide reliable communications

[0042] CFAN-M

[0043] A master node of CFAN, which is a device node that manages and sets up node connections in CFAN.

[0044] CFAN-S

[0045] A slave node that configures a CFAN, and is a device node in a CFAN excluding CFAN-M

[0046] CFAN-R

[0047] A device node within CFAN-S that is capable of wireless power transmission and plays a role in extending the range of CFAN. It can also be called a repeater node.

[0048] The following are abbreviations and their full names used in this specification:

[0049] Full name of the abbreviation

[0050] ARA: Association Response Acknowledgement

[0051] ARQ: Association Request

[0052] ARS: Association Response

[0053] ASC: Association Status Confirmation

[0054] ASRA: Association Status Response Acknowledgement

[0055] ASRQ: Association Status Request

[0056] ASRS: Association Status Response

[0057] CFAN: Conductive Fabric Area Network

[0058] CFAN-M: Conductive Fabric Area Network Master node

[0059] CFAN-S: Conductive Fabric Area Network Slave node

[0060] CFAN-R: Conductive Fabric Area Network Repeater node

[0061] DA: Data Acknowledgement

[0062] DARA: Disassociation Response Acknowledgement

[0063] DARQ: Disassociation Request

[0064] DARS: Disassociation Response

[0065] DRA: Data Response Acknowledgement

[0066] DRQ: Data Request

[0067] DRRQ: Data Response Request

[0068] DRS: Data Response

[0069] FCS: Frame Check Sequence

[0070] GSRQ: Group ID Set-up Request

[0071] GSRS: Group ID Set-up Response

[0072] HCS: Header Check Sequence

[0073] LSB: Least Significant Bit

[0074] MAC:Media Access Control

[0075] NRZ-L:Non-Return-to-Zero Level

[0076] RA: Response Acknowledgement

[0077] RRQ: Response Request

[0078] RSRA: Repeater Setup Response Acknowledgement

[0079] RSRQ: Repeater Setup Request

[0080] RSRS: Repeater Setup Response

[0081] TDMA: Time Division Multiple Access

[0082] UID: Unique Identifier

[0083] WPCN: Wireless Powered Communication Network

[0084] WPT: Wireless Power Transfer

[0085] range

[0086] The present invention relates to a conductive textile network system. Media access control layer and physical layer protocols of the conductive textile network system are disclosed for communicating with wearable sensors, actuators, processors, batteries, smart textiles (e-textiles), etc. The protocols establish linking and control of various devices on one or more conductive textile networks for data and power transmission.

[0087] The Media Access Control Layer Protocol is designed to:

[0088] -Easy network topology configuration for communication

[0089] - Variable superframe structure formation for data transmission and flow control according to the channel

[0090] - Resource allocation between nodes for time and power sharing

[0091] The physical layer protocols are designed to:

[0092] - Modulation for low cost implementation and reduced error performance

[0093] -Frequency setting adapted to the conductive fiber area network

[0094] overview

[0095] The Conductive Fabric Area Network system (CFAN system) according to the present invention is a communication system capable of transmitting and receiving data through a conductive fabric-based network. The system operates one or more Conductive Fabric Area Networks (hereinafter abbreviated as "CFAN"). CFANs are designed to take advantage of the characteristics of conductive fabrics. The system uses a carrier frequency to ensure stable communication and a wide conductive fabric area even in harsh environments, simple and robust modulation methods such as ASK and FSK to reduce implementation costs and error probability, and coding techniques for noise robustness. In principle, a data transmission rate of several kbps is provided over a CFAN.

[0096] The system also uses simple and efficient network topologies such as star or tree topologies for low power consumption, dynamic address allocation for packet size and efficient address management, and variable data transmission rates and adaptive link quality control.

[0097] Devices on a CFAN are classified into one of three types of nodes depending on their role: master node, slave node, and repeater node. In this invention, a master node can be referred to as a CFAN-M, a slave node as a CFAN-S, and a repeater node as a CFAN-R. Basically, a CFAN is composed of one CFAN-M, multiple CFAN-S, and multiple pairs of CFAN-R.

[0098] The conductive fiber region network system according to the present invention may have one or more CFANs, in which case there may be one main CFAN with a main CFAN-M and one or more sub-CFANs, each with its own sub-CFAN-M.

[0099] When a slave node joins the network (CFAN), the master node allocates a time slot to each device, i.e., slave node, directly or through the CFAN-R at the request of the slave node and at the master node's discretion. The conductive fiber area network system according to the present invention uses a TDMA (Time Division Multiple Access) method for transmitting and receiving data.

[0100] A CFAN can accommodate multiple wearable devices of various shapes, positions, sizes, and weights. The devices can be utilized for a variety of applications, services, and industries, including but not limited to the following:

[0101] -Health monitoring: detecting, treating and responding to patient conditions or treatments

[0102] -Sports and fitness: Increased awareness of physical condition and activity capacity

[0103] -Smart clothing: Physical activity tracking and response using industrial or environmental sensors

[0104] -Military and Soft Shoot: Smart textiles capable of kinematic analysis and rapid situational response

[0105] CFAN-S are strategically distributed throughout the conductive fiber area, and CFAN-M is located at the center of the conductive fiber area network. CFAN-R is located near the edges of the conductive fibers to connect them to each other. When CFAN-S receives sensing data from the sensor, it transmits the received data to CFAN-M through the conductive fibers. CFAN-M can transmit the data received by CFAN-S to the monitoring center through other physical media, such as wireless communication.

[0106] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, the same reference numerals will be used to refer to the same elements regardless of the drawing numbers in order to facilitate overall understanding.

[0107] Network Components

[0108] (1) General

[0109] The main components of a CFAN are divided into a time element and a physical element. The time element refers to a superframe consisting of a request period, a response period, and an autonomous period. The physical element refers to a network consisting 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.

[0110] Figure 1 shows the superframe structure (time element), and Figure 2 shows the network structure (physical element). The node that must be determined first in a CFAN is the CFAN-M, and the superframe begins when the CFAN-M sends a request packet during the request period. The CFAN-M is responsible for managing the association, disassociation, release, and scheduling of CFAN-R and CFAN-S.

[0111] On the other hand, an extended CFAN is composed of multiple CFANs. The CFANs included in an extended CFAN are divided into a main CFAN, sub CFANs, and inter CFANs. A main CFAN is a CFAN that has a power source and one or more CFAN-Rs, while a sub CFAN is a CFAN that must receive energy from the main CFAN and does not have a CFAN-R. An inter CFAN is a multipoint-to-point Wireless Powered Communication Network (WPCN) between a CFAN-R and a sub CFAN-M. The main CFAN-M manages the sub CFAN-Ms through the main CFAN's CFAN-R.

[0112] (2) Time element

[0113] The time element used in CFAN is a TDMA time slot. CFAN-M manages CFAN-R and CFAN-S that can transmit data, and time slots are individually assigned to all nodes in the CFAN group selected by CFAN-M. The superframe structure of CFAN consists of a request section, a response section, and an autonomous section as shown in Figure 1, and the length of the section is variable.

[0114] When multiple sub-CFANs are connected to a main CFAN to expand the CFAN, the superframe structure remains the same for all CFANs. The superframe begins with the CFAN-M, which transmits a response request packet (RR packet) during the request period. The response request packet contains information about the CFAN-R ID and the CFAN-S ID, and the CFAN-R and CFAN-S transmit response packets during the response period using the information in the response request packet.

[0115] When multiple CFANs exist (extended CFAN), if a CFAN-R is approved by the main CFAN-M, it is assigned a time slot just like other CFAN-S. However, within the time slot, the CFAN-R must subdivide it again to transmit data to the sub-CFAN. In this case, the main CFAN's CFAN-R is connected to the sub-CFANs CFAN-M and CFAN-S that cannot be reached by the main CFAN-M. The main CFAN and sub-CFAN can operate simultaneously.

[0116] During the request period of the main CFAN, the CFAN-M transmits a response request packet to the CFAN-R and CFAN-S, and during the response period, the corresponding response packet is returned. In a sub-CFAN, the CFAN-M must transmit a response request packet to the CFAN-S. In an inter-CFAN (WPCN), the CFAN-R must transmit a response request packet to the associated sub-CFAN-M.

[0117] During the response interval of the main CFAN, CFAN-R and CFAN-S can transmit response packets in response to the response request packet received from CFAN-M during the request interval. The response interval can be divided into multiple time slots depending on the number of CFAN-Rs and CFAN-Ss selected from the CFAN. The length of each time slot varies depending on the length of the response frame and the acknowledgment. CFAN-M reserves a time slot for CFAN-R, CFAN-S, or a specific group to use the response interval, and nodes in the assigned group transmit data frames independently during the response interval. The slot number is determined by the number of time slots; otherwise, the slot number is 0.

[0118] During the response interval of the sub-CFAN, the CFAN-S that join the sub-CFAN transmits a response packet to its own CFAN-M again based on the response request packet. The response interval is divided into time slots according to the number of CFAN-S selected from the sub-CFAN. The length of each time slot is variable depending on the length of the response packet and acknowledgment packet. The CFAN-S of the assigned group transmit data frames independently during the response interval.

[0119] During the response interval of the inter-CFAN (WPCN), the sub-CFAN-M connected to the CFAN-R transmits a response to the sub-CFAN-M based on the response request packet. The response interval is divided into time slots according to the number of CFAN-S selected from the sub-CFAN. The length of each time slot is variable depending on the length of the response packet and the acknowledgement packet.

[0120] An autonomous section of a CFAN begins when no device returns a response packet for a certain period of time. During an autonomous section of the main CFAN, CFAN-R and CFAN-S can transmit data without a request from CFAN-M. During an autonomous section of a sub-CFAN, CFAN-S can transmit data without a request from CFAN-M. During an autonomous section of an inter-CFAN (WPCN), sub-CFAN-M can transmit data on the main CFAN without a request from CFAN-R. The autonomous section lasts until CFAN-M transmits a requested section.

[0121] The CFAN superframe is divided into a request section, a response section, and an autonomous section. CFAN-M, CFAN-R, and CFAN-S operate in each section as follows:

[0122] [Request section] During 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 decides whether to transmit a response packet in the response section based on the response request packet. The CFAN-M can decide which CFAN-R and CFAN-S will be 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, after receiving the response request packet, decides whether to transmit a response packet in the response section. The CFAN-M can decide which CFAN-S will be grouped together to transmit in the response section.

[0123] [Response Section] The CFAN-R or CFAN-S selected by the CFAN-M can transmit a response packet in the response section. When the CFAN-R or CFAN-S transmits a response packet in the response section, the CFAN-M that receives the response packet transmits a response acknowledgement packet (RA packet). If the CFAN-R or CFAN-S does not receive a response acknowledgement packet, it transmits a response packet every time slot until it receives a response acknowledgement packet from the CFAN-M or a timeout occurs.

[0124] [Autonomous section] In the case of a main CFAN or a sub CFAN, an autonomous section begins when the CFAN-R or CFAN-S does not transmit a response packet for a certain period of time, and this section continues until the CFAN-M transmits a response request packet. In the autonomous section, the CFAN-R or CFAN-S can transmit data without a request from the CFAN-M.

[0125] (3) Physical elements

[0126] The physical elements that make up a CFAN are devices categorized into CFAN-M, CFAN-R, and CFAN-S according to their roles. A CFAN is a network that can send and receive data between CFAN-N, CFAN-R, and CFAN-S. The CFAN-M manages the entire CFAN, and in principle, there is only one CFAN-M per network. The CFAN-M controls CFAN-R and CFAN-S by broadcasting a response request packet to all nodes at once. CFAN-R and CFAN-S must send and receive response packets under the control of the CFAN-M. When there are multiple CFANs, there can only be one main CFAN and multiple sub-CFANs. A 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 Figure 2.

[0127] While the main CFAN can have one or more power sources, the sub-CFAN does not have a direct power source. The power source for the main CFAN can be a disposable battery that uses a pouch, while the power source for the sub-CFAN can be a flexible battery, such as a lithium-ion flexible battery or a lithium polymer flexible battery. A flexible battery can also be a conductive fiber layer-based secondary battery, with a dielectric interposed between conductive fiber layers that act as electrodes to form a supercapacitor structure, as shown in Figure 31. The charge amount, charging speed, and charging time of a secondary battery can vary depending on the material that makes up the dielectric. The main CFAN can use either an electromagnetic induction method or a photocharging method to charge the sub-CFAN.

[0128] CFAN-M (master node) is the node that manages CFAN. As a rule, there can be only one CFAN-M per network, and the CFAN-M manages and controls CFAN-R and CFAN-S using response request packets. When there are multiple CFANs, there can be only one main CFAN-M per main CFAN, and only one sub-CFAN-M per sub-CFAN. Sub-CFAN-Ms can communicate with the main CFAN-M through the CFAN-R associated with the sub-CFAN-M. All sub-CFAN-Ms can collect energy and store it in supercapacitors through the CFAN-R on the main CFAN. Sub-CFAN-Ms use energy to power their own sub-CFANs and transmit data to CFAN-R.

[0129] CFAN-S (slave nodes) are the nodes that make up the CFAN (excluding CFAN-M and CFAN-R), and there can be a maximum of 65,519 CFAN-S per network. CFAN-S transmits response packets in response to request packets transmitted by CFAN-M in the network.

[0130] The CFAN-R (repeater node) is a node corresponding to the CFAN-S and is a device of the main CFAN that can send and receive data with the sub-CFAN-M of the sub-CFAN. The CFAN-R performs WPT and can also transmit data to the sub-CFAN-M. The sub-CFAN-M can transmit data from all CFAN-S to the CFAN-R at any given time, and the CFAN-R waits for the corresponding time slot in the response section of the main CFAN to transmit data. The CFAN-R enables connections between the main CFAN and multiple sub-CFANs.

[0131] (4) Address elements

[0132] CFAN uses a CFAN ID, UID, group address, node address and other address systems to identify each CFAN-R and CFAN-S.

[0133] The CFAN ID is a unique ID that distinguishes each CFAN from other CFANs. This value is not repeated on other CFANs and is maintained as long as the CFAN exists. The CFAN ID is an 8-bit address ID assigned by the CFAN-M. The CFAN ID is assigned to a source CFAN ID and a target CFAN ID. As shown in Table 1 (Specified CFAN ID), a CFAN ID can be specified for broadcasting to all CFANs.

[0134] [Table 1] The UID is a unique identifier consisting of 64 bits. The UID can be composed of a group address, IC manufacturer code, and IC manufacturer serial number as shown in Table 2 (UID structure). The CFAN-S is identified by the UID.

[0135] [Table 2]

[0136] Group ID is an identifier for CFAN-R and CFAN-S groups classified by CFAN. CFAN-M can request data transmission in groups during the request period. The group unit is used depending on the application. Some group IDs can be designated as shown in Table 3 (Designated Group IDs).

[0137] [Table 3] The node ID is an identifier used instead of the UID to identify each node and is an 8-bit address assigned by CFAN-M. The node ID can be assigned to the origin address and destination address. Some node IDs can be assigned as shown in Table 4 (Assigned Node IDs).

[0138] [Table 4]

[0139] Network Status

[0140] (1) General

[0141] In CFAN, CFAN-R and CFAN-S acquire the active state of network configuration, network association, network disassociation, network connection confirmation, data transmission, and network disconnection.

[0142] (2) Network configuration

[0143] CFAN-M forms a network by sending a request packet to CFAN-R and CFAN-S during 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 main network is formed. The minimum network section refers to the case where only CFAN-M exists, and consists of only the request section and autonomous section.

[0144] In an extended CFAN, the CFAN-R sends a request packet containing the CFAN ID to the sub-CFAN-M to form a network. The sub-CFAN-M returns a response packet to the CFAN-R, forming an extended network.

[0145] (3) Network association

[0146] When CFAN-M broadcasts an association request packet, CFAN-R and CFAN-S transmit the received association request packet during the response period. Upon reception, CFAN-R and CFAN-S search for the received packet and connect to the network based on it. If CFAN-R and CFAN-S find the correct network, they transmit an association response packet to CFAN-M. When CFAN-M transmits a final acknowledgement to CFAN-R and CFAN-S and receives it, network association is completed in the main CFAN. In the extended CFAN, CFAN-M transmits an association request packet to all CFAN-Rs, which in turn transmit association request packets to sub-CFAN-Ms. The sub-CFAN-Ms respond with the received association request packet to CFAN-R, and CFAN-R transmits this response packet to the main CFAN-M. The main CFAN-M then transmits an acknowledgement to the sub-CFAN-Ms via 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 sends 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 is approved, the extended network connection is completed.

[0147] (4) Network disassociation

[0148] A CFAN-S, CFAN-R, or sub-CFAN-M associated with a CFAN can be separated automatically or at the request of the CFAN-M. In an extended CFAN, node separation of a sub-CFAN is performed by the CFAN-R and sub-CFAN-M to reach the sub-CFAN's CFAN-S. For forced separation, 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. In the case of voluntary separation, the main CFAN-M can determine the separation status of the CFAN-S, CFAN-R, or sub-CFAN-M from the response result of the next connection request packet.

[0149] (5) Network connection test

[0150] The connection status of a CFAN-S, CFAN-R, or sub-CFAN-M in the network can be requested by the main CFAN-M. To check the network connection status, the main CFAN-M transmits 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 an acknowledgement packet is transmitted from the main CFAN-M to the CFAN-S, CFAN-R, or sub-CFAN-M using the same procedure, the network connection check is completed. In an extended CFAN, when the main CFAN-M sends or receives a connection status packet with the sub-CFAN's CFAN-S, the packet passes through the CFAN-R and sub-CFAN-M.

[0151] (6) Data transmission

[0152] When the main CFAN-M transmits a data response request packet within the request period, the CFAN-S, CFAN-R, or sub CFAN-M responds with a data response packet to the main CFAN-M according to the type of requested data. After receiving the data response packet, the main CFAN-M transmits a data confirmation packet, and data transmission is completed after the CFAN-S, CFAN-R, or sub CFAN-M receives the data confirmation packet. In an extended CFAN, the main CFAN-M and the sub CFAN's CFAN-S exchange data response packets through the CFAN-R and sub CFAN-M.

[0153] (7) Network release

[0154] CFAN termination can be divided into normal termination at the request of the main CFAN-M and abnormal termination due to unexpected circumstances.Normal termination occurs when the main CFAN-M determines the termination status and distributes a request to all CFAN-S, CFAN-R, and sub-CFAN-M to terminate the network.Abnormal network termination occurs when all participating CFAN-S, CFAN-R, and sub-CFAN-M terminate simultaneously.

[0155] (8) Network node state (CFAN node state)

[0156] 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 moves to the request period. If there is no response, the CFAN-M remains in the request period. When the CFAN-M receives a response confirmation packet, its state changes to the response period. When the CFAN-R powers on as the main CFAN, it can power on nearby sub-CFAN-Ms via WPT.

[0157] Figure 3 is a state diagram of CFAN-M.

[0158] The CFAN-M enters standby mode when powered on through the conductive fiber wired power supply. If the CFAN-M is a sub-CFAN of an extended CFAN, it enters standby mode when powered on through WPT. When a superframe begins or an application program sends a command in standby mode, the CFAN-M enters packet generation mode. The CFAN-M generates an RR packet and transmits it to the CFAN-R and CFAN-S, and the CFAN-M returns to standby mode.

[0159] When a CFAN-M receives a packet from a CFAN-R or CFAN-S in standby mode, the CFAN-M enters the packet analysis state. If the source ID and destination ID of the received packet belong to the current CFAN, the CFAN-M enters the packet generation state. The CFAN-M then generates an RA or DA packet and transmits it to the CFAN-R or CFAN-S of the corresponding medium. The CFAN-M then returns to the standby state.

[0160] On the other hand, if the 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 CFAN-M state immediately returns to the standby state. If a timeout, mismatch, or error occurs in the confirmation packet received in the standby state, the CFAN-M regenerates the packet in the packet generation state and retransmits it to the CFAN-R and CFAN-S through the corresponding medium, and then returns to the standby state. If such a failure occurs continuously, the packet retransmission procedure is repeated as many times as necessary (maximum N times). In the (N+1) procedure, the CFAN-M state remains in the standby state.

[0161] In an extended CFAN, if a CFAN-R is near a 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 transitions from standby to packet analysis state. If the destination CFAN ID corresponds to the sub-CFAN ID, the sub-CFAN-M transitions to packet generation state and transmits the packet to the corresponding CFAN-S or CFAN-S. The sub-CFAN-M then returns to standby state. When the sub-CFAN transmits a packet to the main CFAN, the sub-CFAN-M transitions from standby to 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 transitions to packet generation state and transmits the packet to the CFAN-R over the wireless channel for the corresponding section. The sub-CFAN-M then returns to standby state.

[0162] When CFAN-S starts operation, it immediately enters standby mode. When an application program sends system data in standby mode, CFAN-S enters packet generation mode. CFAN-S generates packets during the autonomous section and transmits them to CFAN-M. After that, CFAN-S returns to standby mode.

[0163] When CFAN-S receives a packet in the standby state, it enters the packet analysis state and analyzes the received packet. If it is a RR packet and the destination ID matches, the CFAN-S state changes to the packet generation state and sends a response packet to CFAN-M. Then, the CFAN-S state returns to the standby state.

[0164] Figure 4 is a state diagram of the CFAN-S. If the packet received during CFAN-S packet analysis is an error packet or an RA or DA packet, the CFAN-S enters a standby state. If the CFAN-S does not receive an RA or DA packet within the timeout interval, the CFAN-S state transitions from the standby state to the packet generation state. If this occurs, the CFAN-S regenerates a response packet and retransmits it to the CFAN-M, and the CFAN-S state transitions from the packet generation state to the standby state. The response packet is retransmitted as many times as necessary (up to N times). The CFAN-S remains in the standby state for the (N+1)th timeout interval.

[0165] Figure 5 is a state diagram of the CFAN-R.

[0166] When the CFAN-R is powered on, it enters the standby state. When the CFAN-R receives a packet in the standby state, it enters the packet analysis state and 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 and sends a response packet through the appropriate medium. Then, the CFAN-R enters the standby state.

[0167] If the packet received in the packet analysis state is a packet error, RA or DA packet, the CFAN-R enters standby state. If the CFAN-R does not receive an RA or DA packet for the timeout period, the CFAN-R switches from standby state to packet generation state. The CFAN-R then regenerates the response packet and retransmits it to the CFAN-M, and the CFAN-R enters standby state. The response packet is retransmitted as many times as necessary (maximum N times). The CFAN-R remains in standby state for the (N+1)th timeout period.

[0168] In an extended CFAN, if a sub CFAN-M is near a CFAN-R, the CFAN-R can supply power to the sub CFAN through the sub CFAN-M via wireless power transmission while in standby mode. When the main CFAN-M sends a packet to the sub CFAN, the CFAN-R switches from standby mode to packet analysis mode. If the destination CFAN ID matches the sub CFAN ID, the CFAN-R switches to packet generation mode and transmits the packet to the sub CFAN-M over the wireless channel. The CFAN-R then returns to standby mode. When the sub CFAN-M transmits a packet to the main CFAN over the wireless channel, the CFAN-R switches from standby mode to packet analysis mode and receives the packet. If the destination CFAN ID matches the main CFAN ID, the CFAN-R switches to packet generation mode and transmits the packet to the main CFAN-M over the wired channel for the corresponding section. The CFAN-R then returns to standby mode.

[0169] MAC Layer Frame Format

[0170] (1) General

[0171] The CFAN 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.

[0172] (2) Frame format

[0173] All MAC frame formats consist of a frame header and a frame body as shown in Table 5.

[0174] [Table 5]

[0175] The frame header consists of frame control, source CFAN ID, source address, target CFAN ID, target address, and sequence number. The frame header contains information for frame transmission and flow control. The frame header can be used for data transmission.

[0176] The frame control field consists of the frame type, acknowledgement policy, first fragment, last fragment, and protocol version as shown in Table 6. The unit of one line in Table 6 is Bit.

[0177] [Table 6]

[0178] The following is a description of each field included in the frame control field.

[0179] 1) The frame type field consists of 3 bits. Details of frame types will be described later.

[0180] 2) The confirmation policy field consists of 2 bits. If the received frame is an acknowledgement frame, it indicates the policy of the received acknowledgement frame. If not, it indicates the policy of the acknowledgement frame for the destination node. Each item of the confirmation policy is explained in detail below.

[0181] 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 transmission, which does not require ACK.

[0182] b) Single Acknowledgment: The destination node that receives the frame transmits an acknowledgment frame to the source node after SIFS. This acknowledgment policy can only be used for 1:1 transmission.

[0183] c) Multiple Acknowledgments: A destination node that receives a frame transmits an acknowledgement frame in response to multiple source nodes after SIFS. This acknowledgement policy can be used for 1:N transmission.

[0184] d) Data Acknowledgement: After receiving a data frame, the destination node transmits a data acknowledgement frame to the source node as a response after SIFS. This acknowledgement policy can only be used for 1:1 data transmission.

[0185] 3) The first fragment field is 1 bit: '1' indicates that the frame is a higher layer request, response, or the start of a data packet, and '0' indicates that it is not the start.

[0186] 4) The last fragment field is 1 bit. A '1' indicates that the frame is the end of a higher layer request, response, or data packet, and a '0' indicates that it is not the end.

[0187] 5) The protocol version field consists of 2 bits, and its size and position are fixed regardless of the system protocol version. The current value is 0 and increases by 1 each time a new version is released. If a node receives a packet with a version higher than its own, it discards it without notifying the source node.

[0188] 6) Reserve: A field prepared for future use.

[0189] Each CFAN ID field consists of one byte and is used to identify the network as shown in Table 5. In a frame, the source CFAN ID indicates the CFAN where the sending node is located, and the destination CFAN ID indicates the CFAN where the receiving node is located.

[0190] Node IDs are used to identify nodes within each network. The source node ID and target node ID are each 1 byte.

[0191] The sequence number field is 8 bits long and indicates the frame sequence number. In a data frame, a sequence number between 0 and 255 is assigned via an incrementing counter for each packet, and when it reaches 255, it is reset to 0 again.

[0192] 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 of the frame control field.

[0193] The payload contains data transmitted between the main CFAN-M and each CFAN-S, CFAN-R, and sub-CFAN-M, and its length has a variable value between 0 and 247.

[0194] The FCS (Frame Check Sequence) is 16 bits long and is used to verify whether the frame body is received without errors. The FCS is generated using the 16th order standard generator polynomial shown in Equation 1 below.

[0195]

number

[0196] (3) Frame type

[0197] There are four frame types defined: request frame, response frame, data frame, and confirmation frame. Table 7 shows the frame types, binary values, contents, and time elements (sections) for each frame type.

[0198] [Table 7] The request frame is used when the primary CFAN-M transmits a request packet to a specific CFAN-S, CFAN-R, or sub-CFAN-M in the CFAN during the request period, or when broadcasting information to all CFAN-S, CFAN-R, and sub-CFAN-Ms. In an extended CFAN, the request frame is used when the CFAN-R sends a request packet to a sub-CFAN-M during the request period. The request frame can be configured as shown in Table 8. The unit of one line in Table 8 is Byte.

[0199] [Table 8]

[0200] The response frame is used to send a response packet from a CFAN-S, CFAN-R, or sub-CFAN-M during the request period in response to a request from the main CFAN-M. The appropriate CFAN-S, CFAN-R, or sub-CFAN-M transmits the response packet during the request period within the specified number of attempts until it receives a confirmation packet. In an extended CFAN, a sub-CFAN-M transmits a response packet during the request period in response to a CFAN-R request. The response frame can be configured as shown in Table 9. The unit of one line in Table 9 is Byte.

[0201] [Table 9]

[0202] The data frame is used when a CFAN-S, CFAN-R, or sub-CFAN-M transmits data to a main CFAN-M during the response period regardless of whether the CFAN-M has requested it. In an extended CFAN, a sub-CFAN-M transmits data to a CFAN-R. The data frame can be configured as shown in Table 10. The unit of one line in Table 10 is Byte.

[0203] [Table 10]

[0204] Acknowledgement frames are classified into two types: RA (response acknowledgement) and DA (data acknowledgement). When the main CFAN-M transmits a request frame using an RA frame, the CFAN-S, CFAN-R, or sub-CFAN-M receives the request packet and transmits a response packet, and 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 acknowledgement frame. When the main CFAN-M receives an appropriate response frame, it 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. A DA frame is an acknowledgement frame for a received data packet. The main CFAN-M responds to the transmitting CFAN-S, CFAN-R, or sub-CFAN-M by transmitting a DA frame after a short frame interval in the response period. In an extended CFAN, the CFAN-R responds to the transmitting sub-CFAN-M by transmitting an RA or DA frame in the response period. Table 11 shows an example of the format of a response confirmation frame. Each line in Table 11 is in bytes.

[0205] [Table 11]

[0206] The DA frame in Table 12 consists of a frame header and a frame body. If the destination CFAN ID is 0xFF and the destination node ID is 0xFE or 0xFD, it corresponds to the unjoined CFAN-S ID and the unjoined CFAN-R ID, respectively. In this case, the UID field must be included.

[0207] [Table 12]

[0208] (4) Payload Format

[0209] The payload format is generated differently depending on the frame type, including a request frame, a response frame, a data frame, an acknowledgement frame, and the like.

[0210] [Request Frame]

[0211] Table 13 shows the payload format of the request frame. As shown in Table 13, the payload for the request frame consists of a group ID, a request code, a length, and one or more request blocks depending on the request. The unit of one line in Table 13 is Byte.

[0212] [Table 13]

[0213] The Group ID field consists of one byte and is used to send a response request packet to a specific group. If the Group ID is 0xFF, it indicates that the CFAN-M requests responses from all CFAN-S, CFAN-R, and sub-CFAN-M groups. Details about Group IDs are described above.

[0214] The request code in the payload of the request frame can be configured as shown in Table 14.

[0215] [Table 14] The length field consists of 1 byte. It indicates the total length of the request block, and the value of the length field varies depending on the length and number of request blocks.

[0216] The data format of a request block varies depending on the request code, and one or more request blocks can be included in the payload of a request frame.

[0217] Detailed information on the data format of each request block is as follows:

[0218] 1) Association request

[0219] The ARQ block format can be configured as shown in Table 15 and consists of an 8-byte UID mask, which can be used to implement a binary search algorithm.

[0220] [Table 15]

[0221] 2) Disassociation Request

[0222] The DARQ block format is shown in 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 the DARQ, and the next byte is the slot number used for the response section. If the node ID is 0xFF, the DARQ is transmitted to all CFAN-Rs and CFAN-Ss under the group ID.

[0223] [Table 16]

[0224] 3) Association status request

[0225] The ASRQ block format is shown in 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 the ASRQ. If the CFAN ID is 0xFF and the node ID is 0xFF, the ASRQ is requested to all CFAN-Rs and CFAN-Ss under the group ID.

[0226] [Table 17]

[0227] 4) Data request

[0228] The DRQ block format is shown in Table 18. The first and second bytes are the CFAN ID and node ID, the next byte is the slot number, and the last L bytes are the received data type. The data type is determined by the application.

[0229] [Table 18]

[0230] 5) Group ID setup request

[0231] The GSRQ block format can be 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.

[0232] [Table 19]

[0233] [Response Frame]

[0234] Table 20 relates to the payload format of the response frame. The payload format of the response frame contains response information to a CFAN-M request. In an extended CFAN, it contains response information to a CFAN-R request. 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 one line in Table 20 is Byte.

[0235] [Table 20]

[0236] The group address field consists of one byte and is used to send a response request packet to a specific group. Details about group IDs are described above.

[0237] Table 21 shows the response code included in the response frame payload. The response code type can be configured as shown in Table 21.

[0238] [Table 21]

[0239] The length field consists of one byte and indicates the length of the response data. The length field is variable depending on the response data.

[0240] Response data formats are classified as follows:

[0241] 2) Association response

[0242] The ARS block format can be configured as shown in Table 22. ARS data consists of an 8-byte UID.

[0243] [Table 22]

[0244] 2) Disassociation response

[0245] The DARS block format can be configured as shown in Table 23. DARS data consists of an 8-byte UID.

[0246] [Table 23]

[0247] 3) Association Status Response

[0248] The ASRS block format can be configured as shown in Table 24. ASRS data can be configured with an 8-byte UID and a 1-byte status value. Table 25 is a table for association status check values.

[0249] [Table 24]

[0250] [Table 25]

[0251] 4) Data response

[0252] The DRS block format can be configured as shown in Table 26. The DRS data consists of 1 byte for the CFAN ID, 1 byte for the node ID, and L bytes of requested data.

[0253] [Table 26]

[0254] 5) Group ID setup response

[0255] The GSRS block format can be configured as shown in Table 27. The GSRS data consists of 8 bytes for the UID with the changed group ID and 1 byte for the changed group ID.

[0256] [Table 27]

[0257] [Data Frame]

[0258] The payload of a data frame contains the data to be transmitted. Table 28 shows the payload format of a data frame. A data frame consists of an 8-byte UID and L bytes of data.

[0259] [Table 28]

[0260] [Confirmation Frame]

[0261] The payload of the RA (response acknowledgment) frame contains data for the received response packet. Table 29 shows the payload format of the acknowledgement 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 one line in Table 29 is Byte.

[0262] [Table 29]

[0263] The group ID field consists of 1 byte and is used to send a response request packet to a specific group. Details about group IDs are described above.

[0264] Table 30 is a table related to response confirmation codes. The response confirmation code type can be configured as shown in Table 30.

[0265] [Table 30] The length field consists of 1 byte. It indicates the length of the acknowledgement data and is variable depending on the acknowledgement data.

[0266] The response confirmation block format is classified as follows:

[0267] 1) Association Response Confirmation

[0268] The block format of the ARS acknowledgement (ARA) 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 assigned node ID. If the assigned CFAN ID is 0xFF and the assigned node ID is 0xFE or 0xFD, it corresponds to the address of an unjoined CFAN-S and an unjoined CFAN-R, respectively, and means that the ARQ has been rejected.

[0269] [Table 31]

[0270] 2) Disassociation Response Confirmation

[0271] The DARS Acknowledgment (DARA) block format 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, 0xFF is recorded for unjoined CFANs, and 0xFE or 0xFD is recorded for unjoined CFAN-S ID or unjoined CFAN-R, respectively.

[0272] [Table 32]

[0273] 3) Association Status Response Confirmation

[0274] The ASR Acknowledgement (ASRA) block format can be configured as shown in Table 33. The ASR Acknowledgement block consists of an 8-byte UID.

[0275] [Table 33]

[0276] 4) Data Response Confirmation

[0277] The block format of the DR acknowledgement (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.

[0278] [Table 34]

[0279] 5) Group ID setup response confirmation

[0280] The GSR confirmation (GAIRA) block format can be configured as shown in Table 35. The GSRS confirmation block consists of an 8-byte UID and a 1-byte status check value (setting status value).

[0281] [Table 35]

[0282] The group ID setting status value can be configured as shown in Table 36.

[0283] [Table 36]

[0284] MAC Layer Functions

[0285] (1) General

[0286] In the CFAN MAC layer, association, disassociation, and ASC (Association Status Confirmation) processes are used to manage the CFAN network. Data transmission can occur in the response section or the autonomous section. A group address initialization function is also provided for managing CFAN-S, CFAN-R, and sub-CFAN-M groups.

[0287] (2) Network connection and separation

[0288] For a CFAN-R or CFAN-S to communicate with a CFAN-M, it must first connect to the CFAN. Each CFAN-R and CFAN-S searches for a pre-configured CFAN, and if the search is successful, it connects to that CFAN. In an extended CFAN, a sub-CFAN must be connected to the main CFAN.

[0289] [association]

[0290] Figure 6 illustrates the CFAN connection method. When a CFAN-M transmits an ARQ packet to a CFAN-R or CFAN-S that is not yet connected to a CFAN during the request period, the CFAN-R or CFAN-S transmits an ARS packet to the CFAN during the response period. The CFAN-M determines the connection status of the appropriate CFAN-R or CFAN-S and CFAN and notifies the result via an ARA packet. If the connection is permitted, the assigned node address ID is included in the ARA packet; if the connection is rejected, the basic CFAN ID and node ID are recorded accordingly. If the CFAN-M cannot receive an ARS packet or if the CFAN-R or CFAN-S cannot receive the ARA packet due to a data error in the ARA packet, it continues to transmit ARS packets every superframe until it receives an ARA packet. The connection is completed when the CFAN-R or CFAN-S receives an ARA packet from the CFAN-M.

[0291] Figure 7 illustrates the connection method for 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 the CFAN via the CFAN-R and sub-CFAN-M. The CFAN-S then transmits an ARS packet (connection response packet) to the main CFAN-M via the sub-CFAN-M and CFAN-R. After receiving the connection response, the main CFAN-M determines the appropriate connection status of the CFAN-S to the CFAN. The result is reported via an ARA packet (connection response acknowledgement packet). If the connection is permitted, the assigned CFAN ID and assigned node ID are included in the ARA packet. If the connection is denied, the primary CFAN ID and primary node ID are recorded accordingly.

[0292] [disassociation]

[0293] Figure 8 illustrates the separation method for a CFAN. During the request period, a CFAN-M transmits a DARQ packet (separation request packet) to a CFAN-R or a CFAN-S connected to the CFAN. The CFAN-R or CFAN-S transmits a DARS packet (separation response packet) to the CFAN-M during the response period. The CFAN-M determines the separation status of the appropriate CFAN-R or CFAN-S from the CFAN and notifies the result via a DARA packet (separation response acknowledgement packet). If separation is permitted, the CFAN ID and node ID address in the DARA packet are recorded as the primary CFAN ID and primary node ID. If separation is denied, the existing node ID address is recorded. If the CFAN-M fails to receive a DARS packet, or if the CFAN-M receives a DARS packet but the CFAN-R or CFAN-S attempting separation fails to receive the DARA packet due to a data error in the DARA packet transmitted by the CFAN-M, the CFAN-R or CFAN-S continues to retransmit the DARS packet to the CFAN-M every superframe until it receives a DARA packet. When the CFAN-R or CFAN-S receives a DARA packet from the CFAN-M, separation is complete.

[0294] Figure 9 illustrates the separation method for an extended CFAN. In an 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 sub-CFAN-M. The CFAN-S then transmits a DARS packet to the main CFAN-M through the sub-CFAN-M and CFAN-R. After receiving a connection response, the main CFAN-M determines the appropriate separation state of the CFAN-S for the CFAN and notifies the result through a DARA packet. If separation is allowed, the CFAN ID and node ID address in the DARA packet are recorded as the primary CFAN ID and primary node ID. If separation is denied, the existing CFAN ID and node ID address are recorded.

[0295] [Association status check]

[0296] Figure 10 illustrates a method for checking the connection status of a CFAN. During the request period, a CFAN-M transmits an ASRQ packet (Connection Status Request packet) to a CFAN-R or a CFAN-S associated with the CFAN. The CFAN-R or CFAN-S transmits an ASRS packet (Connection Status Response packet) to the CFAN-M during the response period. The CFAN-M then checks the appropriate ASRA packet (Connection Status Response Acknowledgement packet) for the connection status of the CFAN-R or CFAN-S and transmits it to the CFAN. If the CFAN-M fails to receive an ASRS packet or if the CFAN-R or CFAN-S attempting to send an ASRS packet fails to receive the ASRA packet due to a data error in the ASRA packet, the CFAN-R or CFAN-S continues to transmit ASRS packets to the CFAN-M every superframe until it receives an ASRA packet. When the CFAN-R or CFAN-S receives the ASRA packet from the CFAN-M, the ASRS is completed. That is, when the CFAN-R or CFAN-S receives an ASRA packet from the CFAN-M, the connection status check is completed.

[0297] Figure 11 shows 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 sub-CFAN's CFAN-S via the CFAN-R and sub-CFAN-M. The CFAN-S then 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 for the CFAN and transmits the result via an ASRA packet.

[0298] (3) Data transmission

[0299] CFAN can transmit data in the response section or autonomous section. In the response section, data can be transmitted at the request of CFAN-M, and in the autonomous section, data can be transmitted without the request of CFAN-M.

[0300] [Data transmission during response period]

[0301] Figure 12 illustrates a data transmission method during the response interval of a CFAN. During the request interval, a CFAN-M transmits a DRQ packet (data request packet) to a CFAN-R or CFAN-S connected to the CFAN. The CFAN-R or CFAN-S transmits a DRS packet (data response packet) during the response interval. After receiving a DRS packet from the CFAN-M, the CFAN-M transmits a DRA packet (data response acknowledgement packet). If the CFAN-M fails to receive the DRS packet from the CFAN-R or if the CFAN-R or CFAN-S fails to receive the DRA packet due to a packet error, the CFAN-R or CFAN-S continues to transmit DRS packets in every time slot until it receives a DRA packet. When the CFAN-R or CFAN-S receives a DRA packet from the CFAN-M, the data transmission procedure for the response interval is completed.

[0302] 13 shows the data transmission method during the response period of an extended CFAN. In an extended CFAN, the main CFAN-M transmits a DRQ packet to the sub-CFAN's CFAN-S via the CFAN-R and sub-CFAN-M. The CFAN-S then transmits a DRS packet to the main CFAN-M via the sub-CFAN-M and CFAN-R. Upon receiving the response, the main CFAN-M transmits a DRA packet to the CFAN-S. The data transmission procedure during the response period is completed when the CFAN-S receives the DRA packet from the CFAN-M.

[0303] [Data transmission within the autonomous section]

[0304] Figure 14 illustrates the data transmission method within a CFAN autonomous section. An autonomous section begins when the CFAN-R or CFAN-S does not transmit a response packet during the timeout period. The autonomous section is maintained until the CFAN-M transmits an RR packet. The CFAN-R or CFAN-S can transmit data during the autonomous section without a request from the CFAN-M. If a system interruption occurs, the CFAN-R or CFAN-S can transmit data without a request from the CFAN-M. If the CFAN-M fails to receive a data packet or if the CFAN-R or CFAN-S fails to receive a DA packet due to a packet error, the CFAN-S continues to transmit data packets to the CFAN-M until it receives a DA packet. The data transmission procedure for the autonomous section is completed when the CFAN-R or CFAN-S receives a DA packet (data confirmation packet) from the CFAN-M.

[0305] Figure 15 shows a data transmission method within an autonomous section of an extended CFAN. In an extended CFAN, a sub-CFAN (CFAN-S) can transmit data within an autonomous section without a request from the main CFAN-M. If a system interruption occurs, the CFAN-S can transmit data without a request from the main CFAN-M.

[0306] (4) Group ID setup

[0307] Figure 16 shows the group ID setup method. During the request period, a CFAN-M sends a GAIRQ packet (group ID setup request packet) to a CFAN-R or CFAN-S connected to the CFAN. The CFAN-R or CFAN-S transmits a GAIRR packet (group ID setup response packet) during the response period. After checking the group address initialization status of the corresponding CFAN-R or CFAN-S, the CFAN-M transmits a GAIRA packet (group ID setup response acknowledgement packet).

[0308] Figure 17 shows the group ID setup method for an extended CFAN. During the request period in an extended CFAN, when the main CFAN-M sends a GAIRQ packet to the CFAN-S of the sub CFAN connected to the CFAN, the CFAN-S transmits a GAIRR response packet through 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.

[0309] PHY hierarchy

[0310] (1) PHY Layer Frame Format

[0311] [General]

[0312] The CFAN physical layer (PHY layer) frame format is described below. Figure 18 shows the PHY layer frame format. Each PHY layer frame consists of a preamble, a header, and a payload. As shown in Figure 18, a PHY 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. Packet transmission and reception starts with the LSB.

[0313] [preamble]

[0314] Figure 19 is a diagram of the preamble format. As shown in Figure 19, the preamble consists of one part called the synchronization sequence. The 16-bit synchronization sequence consists of the 12-bit sequence [0000 0000 0000]. A 4-bit sequence of

[1010] follows the synchronization sequence. The synchronization sequence is used for packet acquisition, symbol timing, and carrier frequency estimation.

[0315] The preamble is coded using TYPE 0, which is described below.

[0316] [Header]

[0317] Figure 20 shows the header format. The header is added after the preamble to convey information about the payload. As shown in Figure 20, the header consists of 24 bits. Bits 0-2 are the data transmission rate and coding field. Bits 3-10 are the payload data length field. 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 shows the definition of the physical layer header.

[0318] [Table 37]

[0319] Table 38 is a definition table for data rate, modulation, and coding. Bits 0-2 can be set to the values ​​shown in Table 38 depending on the data rate and coding. However, the data rates in Table 38 can be changed to different values. Details of TYPEs 0-7 will be described later.

[0320] [Table 38] The payload data length is an unsigned 8-bit integer. The payload data length indicates the number of octets in the payload, not including the FCS. The payload data length ranges from 0x00 to a maximum of 0xFF bytes.

[0321] CRC-8 HCS (Header Check Sequence) is used to check for header errors. HCS handles data transmission rate and coding, payload data transmission rate, and 5 reserved bits. The primitive polynomial is given by Equation 2 below.

[0322]

number

[0323] Figure 21 is a diagram of the header inspection sequence encoder. The processing order of the header inspection is as shown in Figure 21. All registers are initialized to 0.

[0324] Data is accumulated while switch "S" in Figure 21 is at "1". When the last bit is accumulated, switch S moves to "2" and D 7 HCS is transmitted in registers starting from .

[0325] [payload]

[0326] Figure 22 shows 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, no FCS is transmitted.

[0327] Frame Check Sequence (FCS)

[0328] The CRC-16 FCS defined in Table 39 is used to check the payload for errors. The FCS handles variable length data. The primitive polynomial is X16 +X 12 +X 5 +1. The registers are initialized to all ones. The frame check sequence is obtained by inverting the calculated CRC-16 bits.

[0329] [Table 39]

[0330] (2) Coding and modulation

[0331] [coding]

[0332] 23 is a diagram showing the definition of NRZ-L coding. In NRZ-L (level), 0 is represented by frequency ω1 and 1 is represented by frequency ω2.

[0333] [Data rate and encoding type]

[0334] The physical layer supports eight types as shown in Table 38.

[0335] The preamble and header are encoded using TYPE 0, while the payload is encoded using the appropriate data rate and coding. The data rate and coding type of the payload are specified in the data rate and coding field of the header.

[0336] [modulation]

[0337] Communication between CFAN-M, CFAN-R and CFAN-S uses GFSK or ASK modulation.

[0338] FIG. 24 is a diagram illustrating ASK modulation. As shown in FIG. 24, the encoded serial input data is converted into a number indicating one of two ASK constellation points. (ω c is the carrier frequency of the CFAN)

[0339] Figure 25 shows a diagram of GFSK modulation. As shown in Figure 25, the encoded serial input data is converted into a number representing one of two GFSK constellation points (ω1 and ω2 are the modulation frequencies of the CFAN).

[0340] [Encoding and modulation process]

[0341] Figure 26 shows the preamble encoding and modulation process. The preamble sequence is encoded using TYPE 0.

[0342] Figure 27 shows the header encoding and modulation process. As shown in Figure 27, the header format is specified by adding the data rate and encoding, payload data length, 5 bits 0, and HCS value. The resulting combination of values ​​is encoded using TYPE 0 and then modulated by GFSK or ASK.

[0343] Figure 28 shows the payload encoding and modulation process. As shown in Figure 28, the payload is formatted with data and an FCS value. The FCS value is calculated for the data. The resulting combination is encoded using TYPE I (I = 0 to 7) and then modulated by GFSK or ASK.

[0344] medium interface

[0345] (1) Frequency

[0346] The center frequencies of the CFAN are ω1 and ω2 with a maximum tolerance of ±20 ppm for GFSK, or ω with a maximum tolerance of ±20 ppm for ASK. c is.

[0347] (2) Signal waveform

[0348] GFSK and ASK modulation are used for transmission between CFAN-M, CFAN-R and CFAN-S.

[0349] Figure 29 is a diagram for a GFSK modulated signal, and Figure 30 is a diagram for an ASK modulated signal. As shown in Figures 29 and 30, the transmitted signal is modulated by GFSK and ASK according to the envelopes defined herein. Table 40 is an example table for GFSK envelope parameters.

[0350] [Table 40]

[0351] Network design (CFAN example)

[0352] Several examples of CFAN implementations according to the present invention are presented.

[0353] The physical structure of a CFAN is explained below. A CFAN can be implemented in various designs based on a structure with two conductor materials and a dielectric material between the conductors. For example, a smart textile (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 layer is ground. Therefore, power and data can be transmitted through this hierarchical physical structure. In Figure 31, (1) represents Vcc, (2) represents ground, (3) represents the dielectric, and (4) represents the smart textile.

[0354] As another example, a CFAN capable of transmitting power and data can be designed based on a linear cable. Flexible coaxial yarns can have multiple layers, consisting of inner and outer conductor layers and dielectric layers between them, as shown in Figure 32. The choice of coaxial yarn design affects size, data transmission, power attenuation, strength, flexibility, and cost. In Figure 32, (1) represents Vcc, (2) represents ground, (3) represents the dielectric, and (4) represents the coaxial yarn.

[0355] CFANs can also 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 parallel to each other. For a CFAN design that is included in clothing, as shown in Figure 33, conductive fiber can be used as the conductive material and regular fabric can be used as the insulating material. In Figure 33, (1) represents Vcc, (2) represents ground, (3) represents regular fiber, and (4) represents clothing.

[0356] FIG. 34 is a block diagram showing a network system according to an embodiment of the present invention.

[0357] The network system 10 according to an embodiment of the present invention includes a main wired network device 100 and a sub-wired network device 200. The network system 10 may include a plurality of sub-wired network devices 200.

[0358] The main wired network device 100 or the sub wired network device 200 may include a conductive fiber area network, and it is obvious that the main wired network device 100 and the sub wired network device 200 may all include a conductive fiber area network.

[0359] 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.

[0360] The main wired network device 100 and the sub wired network device 200 may be included in different wearable devices. For example, the main wired network device 100 may be included in an upper garment, and the sub wired network device 200 may be included in a lower garment. In this specification, the term "wearable device" refers to not only devices that can be worn in the form of clothing, but also all devices that can be carried on a user's body or clothing, such as a smartwatch, smart glasses, a head-mounted display (HMD), a touch screen, an eye tracker, a device that recognizes a user's posture or movement, and an auxiliary battery.

[0361] Although not shown in the drawings, the main wired network device 100 may further include a power supply device, and the main wired network device 100 may transmit power to the sub wired network device 200 wirelessly.

[0362] Although not shown in the drawings, the sub-wired network device 200 may further include a capacitor with a conductive fabric layer as an electrode. The sub-wired network device 200 can charge the capacitor with power transmitted from the main wired network device 100. The sub-wired network device 200 can then transmit data collected externally or generated by itself to the main wired network device 100 using the power charged in the capacitor.

[0363] The capacitor included in the sub-wired network device 200 may be configured to include two separated conductive fabric layers as electrodes and a dielectric layer interposed between the two conductive fabric layers.

[0364] 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 a plurality of first slave nodes 120 or a plurality of repeater nodes 130.

[0365] The sub-wired network device 200 includes a second master node 210 and a second slave node 220. There may be a plurality of second slave nodes 220.

[0366] When the main wired network device 100 includes a conductive fabric-based network, the first master node 110 transmits and receives data to and from the first slave node 120 and the repeater node 130 through the conductive fabric layer. The first slave node 120 may be a sensor capable of recognizing a user's biosignal, posture, or movement, collects sensor data, and transmits the collected sensor data to the first master node 110 through the conductive fabric layer.

[0367] If the sub-wired network device 200 includes a conductive fabric-based network, the second master node 210 transmits and receives data to and from the second slave node 220 through the conductive fabric layer. The second slave node 220 may be a sensor capable of recognizing a user's biosignal, posture, or movement, collects sensor data, and transmits the collected sensor data to the second master node 210 through the conductive fabric layer.

[0368] The repeater node 130 wirelessly transmits power to the second master node 210 and wirelessly transmits and receives data to and from 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 can be any one or combination of Bluetooth, Bluetooth Low Energy (BLE), Near Field Communication (NFC), Radio Frequency Identification (RFID), Wi-Fi, beacon, Zigbee communication, and Ultra Wide Band (UWB) communication. 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 can wirelessly transmit power to the sub wired network device 200 using a magnetic induction method or a magnetic resonance method.

[0369] When the second slave node 220 transmits sensor data to the second master node 210, the second master node 210 may 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 may suspend the operation of transmitting power to the second master node 210 to prevent interference during the data transmission process.

[0370] The 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 (a node ID that becomes a source address), and an identifier of the node that receives the data (a node ID that becomes a destination address). For example, the node ID that becomes a source address may be an identifier of the sensor 220 included in the sub wired network device 200, and the node ID that becomes a destination address may be an identifier of the storage device 120 included in the main wired network device 100.

[0371] If 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 the repeater node 130 through the conductive fabric layer, and the repeater node 130 can transmit power to the second master node 210 wirelessly.

[0372] Although not shown in the drawings, the sub-wired network device 200 may include a capacitor with a conductive fiber layer as an electrode. In this case, the second master node 210 can charge the capacitor with power transmitted from the repeater node 130. In addition, the second master node 210 can transmit data collected or generated by the sub-wired network device 200 to the repeater node 130 using the power charged in the capacitor.

[0373] The capacitor included in the sub-wired network device 200 may be configured to include two separated conductive fabric layers as electrodes and a dielectric layer interposed between the two conductive fabric layers.

[0374] Even if the content is omitted in the process of explaining the embodiment of Fig. 34, the content of Fig. 1 to Fig. 33 can be applied to the content of Fig. 34. Furthermore, the content of Fig. 34 can be applied to the content of Fig. 1 to Fig. 33.

[0375] FIG. 35 is a block diagram illustrating a computer system for implementing a method according to an embodiment of the present invention.

[0376] Referring to FIG. 35, 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, all of which communicate via a bus 1070. The computer system 1000 may also 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 types 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 the described embodiments, the memory may be located inside or outside the processor, and may be connected to the processor through various means known in the art. The memory may be various types of volatile or non-volatile storage media, for example, the memory may include a read-only memory (ROM) or a random access memory (RAM).

[0377] Accordingly, embodiments of the present invention may be embodied as a computer-implemented method or as a non-transitory computer-readable medium having computer-executable instructions stored thereon. In one embodiment, the computer-readable instructions, when executed by a processor, can perform a method according to at least one aspect of the present disclosure.

[0378] The communication device 1020 can transmit or receive wired or wireless signals.

[0379] Furthermore, the methods according to the embodiments of the present invention may be embodied in the form of program instructions that can be executed by various computer means and recorded on a computer-readable medium.

[0380] The computer-readable medium may include, alone or in combination with other programs, data files, data structures, and the like. The program instructions recorded on the computer-readable medium may be specially designed and constructed for embodiments of the present invention, or may be readily available to those of ordinary skill in the computer software arts. The computer-readable medium may include a hardware device configured to store and execute program instructions. For example, the computer-readable medium may be a magnetic medium such as a hard disk, floppy disk, or magnetic tape, an optical medium such as a CD-ROM or DVD, a magneto-optical medium such as a floptical disk, a ROM, a RAM, or a flash memory. The program instructions may include not only machine code, such as that produced by a compiler, but also high-level language code that can be executed by a computer through an interpreter, etc.

[0381] Although the present invention has been described above with reference to preferred embodiments, it will be understood by those skilled in the art that various modifications and variations of the present invention may be made without departing from the spirit and scope of the present invention as set forth in the following claims.

Claims

1. The network 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.

2. The network system according to claim 1 , wherein the main wired network device and the sub wired network device are included in different wearable devices.

3. The main wired network device further includes a power supply device; 2. The network system according to claim 1, wherein the main wired network device wirelessly transmits power to the sub wired network device.

4. The sub-wired network device further includes a capacitor having the conductive fiber layer as an electrode; the sub-wired network device charges the capacitor with power transmitted from the main wired network device; 4. The network system according to claim 3, wherein the power stored in the capacitor is used to transmit data to the main wired network device.

5. The capacitor is 5. The network system according to claim 4, comprising two separated conductive fiber layers as electrodes, and a dielectric layer interposed between the two conductive fiber layers.

6. 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; 2. The network system according to claim 1, wherein the first master node transmits and receives data to and from the repeater node through a conductive fabric layer, and the repeater node transmits and receives data to and from the second master node wirelessly.

7. The sub-wired network device further includes a slave node that collects sensor data; 7. The network system according to claim 6, wherein the slave node transmits the sensor data to the second master node, and the second master node wirelessly transmits the sensor data to the repeater node.

8. The data transmitted and received between the repeater node and the second master node is an identifier of the main wired network device; an identifier of the sub-wired network device; the identifier of the node that originated the data; and 7. The network system of claim 6, wherein the data includes an identifier of a node that receives the data.

9. The main wired network device further includes a power supply device; The first master node transmits the power supplied from the power supply device to the repeater node through a conductive fabric layer; The network system according to claim 6 , wherein the repeater node wirelessly transmits power to the second master node.

10. The main wired network device further includes a power supply device; The sub-wired network device further includes a capacitor having the conductive fiber layer as an electrode; The first master node transmits the power supplied from the power supply device to the repeater node through a conductive fabric layer; 7. The network system of claim 6, wherein the second master node charges the capacitor with power transmitted 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.

11. The capacitor is 11. The network system according to claim 10, comprising two separated conductive fiber layers as electrodes and a dielectric layer interposed between the two conductive fiber layers.

12. The repeater node When the second master node transmits data to the repeater node, The network system according to claim 10, wherein power is not transmitted to the second master node.

13. Any one or all of the main wired network device and the sub wired network device 10. The in-network system of claim 1, which is a device including a network of conductive fiber regions.

14. a main wired network device wirelessly transmitting a connection request message to a sub wired network device; the sub wired network device sending a connection response message to the main wired network device; and A method for establishing a connection between wired network devices, comprising: the main wired network device transmitting a connection acknowledgement message to the sub wired network device.

15. The connection confirmation message 15. The method of claim 14, wherein the identifier of the main wired network device and a network identifier assigned by the main wired network device to the sub wired network device are included.

16. The step of transmitting a connection request message comprises: a first master node included in the main wired network device transmitting 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 15. The method of claim 14, further comprising the step of: the second master node transmitting the connection request message to the slave node of the sub-wired network device.

17. The step of transmitting the connection response message comprises: the slave node transmitting a connection response message to the second master node; the second master node transmitting the connection response message to the repeater node; and 17. The method of claim 16, further comprising the step of: the repeater node transmitting the connection response message to the first master node.

18. the step of transmitting a connection confirmation message The first master node transmits the connection confirmation message to the second master node through the repeater node; and The second master node transmits the connection confirmation message to the slave node, The connection confirmation message 17. The method of claim 16, wherein the node identifier assigned by the first master node to the slave node includes a node identifier.

Images