Conductive fabric area network system

Abstract

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

Description

Technical Field

[0001] The present invention relates to a conductive fabric area network system. Background Art

[0002] The rapid development of wearable devices has been one of the most exciting technological trends in the past decade. From the initial wearable computers such as smartwatches to soft suits that help people walk again, smart textiles have begun to become promising materials for manufacturing wearable devices such as stretch sensors that can track movement and detect body posture or soft sensors for wearable robots and virtual reality. The body area network of wearable textiles still has challenges to overcome, but it also has the potential to change the way we live and work.

[0003] Since the late 2000s, wired communications such as conductive yarns or printed conductive inks have been used for body area networks. However, as the number of devices increases, wired communications face challenges in terms of durability, data rate, and cost. In addition, these problems can be solved by integrating wireless communications into wearable devices. However, wireless channels may be vulnerable to eavesdroppers and interference, so robust protocols are needed, and each node requires its own battery to establish a wireless link between nodes, thus increasing the fabric weight of each device.

[0004] With the increase in the number of wearable devices and the increase in the demand for intelligent services, it is very important to develop protocols that can provide both data and energy at the same time to reduce the number of cables and battery supplies around each device and improve security. To manage and control a network with multiple nodes on a conductive fabric, a conductive fabric area network protocol should be created to exchange necessary data and control commands.

[0005] In addition, the conductive fabric area network requires a robust system architecture and flexible design to adapt to new operating environments, standards, and markets. Summary of the Invention

[0006] Technical Problem

[0007] The present invention provides a conductive fabric area network system capable of sending and receiving data through a conductive fabric layer.

[0008] In addition, the present invention provides a conductive fabric area network system, in which mutually disconnected parts of clothing including a conductive fabric network wirelessly transmit power and data to perform charging and data storage management, collect various types of information such as the physical condition of a clothing wearer from sensors connected to the conductive fabric network and store the information, and allow the wearer to check the information or confirm the analysis result when necessary.

[0009] Aspects of the present disclosure are not limited to the above aspects. That is, based on the following description, those skilled in the art can clearly understand other aspects not mentioned.

[0010] Technical solution

[0011] According to an embodiment of the present invention, a network system 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.

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

[0013] In an embodiment of the present invention, the main wired network device may further include a power supply device. In this case, the main wired network device can wirelessly transmit power to the sub-wired network device.

[0014] In an embodiment of the present invention, the sub-wired network device may further include a capacitor having an electrode using a conductive fabric layer. In this case, the sub-wired network device can charge the capacitor with the power provided from the main wired network device and use the power charged in the capacitor to send data to the main wired network device.

[0015] In an embodiment of the present invention, the capacitor may use two separate conductive fabric layers as electrodes and include a dielectric layer interposed between the two conductive fabric layers.

[0016] In an embodiment of the present invention, the main wired network device may include a first main node and a repeater node, and the sub-wired network device may include a second main node. The first main node can send data to the repeater node through the conductive fabric layer and receive data from the repeater node, and the repeater node can wirelessly send data to the second main node and receive data from the second main node.

[0017] In an embodiment of the present invention, the sub-wired network device may further include a slave node that collects sensor data. In this case, the slave node can send the sensor data to the second main node, and the second main node can wirelessly send the sensor data to the repeater node.

[0018] In an embodiment of the present invention, the data sent and received between the repeater node and the second main node may include an identifier of the main wired network device, an identifier of the sub-wired network device, an identifier of the node sending the data, and an identifier of the node receiving the data.

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

[0020] In one embodiment of the present invention, the main wired network device may further include a power supply device. The sub-wired network device may further include a capacitor having electrodes using a conductive fabric layer. In this case, the first master node may transmit the power supplied from the power supply device to the repeater node through the conductive fabric layer, and the second master node may charge the capacitor with the power supplied from the repeater node and transmit the data generated by the sub-wired network device to the repeater node using the power charged in the capacitor.

[0021] In one embodiment of the present invention, the capacitor may use two separate conductive fabric layers as electrodes and include a dielectric layer interposed between the two conductive fabric layers.

[0022] In one embodiment of the present invention, when the second master node sends data to the repeater node, the repeater node may not transmit power to the second master node.

[0023] In one embodiment of the present invention, any one or both of the main wired network device and the sub-wired network device may be a device including a conductive fabric area network.

[0024] According to one embodiment of the present invention, a method for establishing a connection between wired network devices includes the following steps: wirelessly sending an association request message from the main wired network device to the sub-wired network device; sending an association response message from the sub-wired network device to the main wired network device; and sending an association confirmation message from the main wired network device to the sub-wired network device.

[0025] In one embodiment of the present invention, the association 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.

[0026] In one embodiment of the present invention, the sending of the association request message may include: sending the association request message from the first master node included in the main wired network device to the second master node of the sub-wired network device through the repeater node of the main wired network device; and sending the association request message from the second master node to the slave node of the sub-wired network device.

[0027] In one embodiment of the present invention, the sending of the association response message may include: sending an association response message from a slave node to a second master node; sending the association response message from the second master node to a repeater node; and sending the association response message from the repeater node to a first master node.

[0028] In one embodiment of the present invention, the sending of the association confirmation message may include: sending the association confirmation message from the first master node to the second master node through the repeater node; and sending the association confirmation message from the second master node to the slave node. In this case, the association confirmation message may include a node identifier assigned by the first master node to the slave node.

[0029] According to one embodiment of the present invention, a conductive fabric area network system includes a main conductive fabric area network device having a plurality of nodes and one or more sub-conductive fabric area network devices having a plurality of nodes. The network devices may be included in different garments or body mounts and communicate with each other using at least one of wired communication and wireless communication.

[0030] Advantageous Effects

[0031] According to one embodiment of the present invention, several nodes in the conductive fabric network can be simply and effectively controlled.

[0032] Furthermore, according to one embodiment of the present invention, services can be provided to multiple nodes and multiple conductive fabric area networks through an effective communication-based time policy mechanism.

[0033] The effects that can be achieved by the present invention are not limited to the above effects. That is, other purposes not described can be clearly understood by those skilled in the art to which the present invention pertains based on the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a superframe structure of a conductive fabric area network (CFAN).

[0035] Figure 2 is a diagram showing the structure (physical elements) of a CFAN.

[0036] Figure 3 is a state diagram of a conductive fabric area network master node (CFAN-M).

[0037] Figure 4 is a state diagram of a conductive fabric area network slave node (CFAN-S).

[0038] Figure 5 is a state diagram of a conductive fabric area network repeater node (CFAN-R).

[0039] Figure 6This is a diagram showing a method for associating a CFAN.

[0040] Figure 7 This is a diagram showing a method for associating an extended CFAN.

[0041] Figure 8 This is a diagram showing a method for disassociating a CFAN.

[0042] Figure 9 This is a diagram showing a method for disassociating an extended CFAN.

[0043] Figure 10 This is a diagram showing a method for confirming the association status of a CFAN.

[0044] Figure 11 This is a diagram showing a method for confirming the association status of an extended CFAN.

[0045] Figure 12 This is a diagram showing a method for data transmission of a CFAN during the response period.

[0046] Figure 13 This is a diagram showing a method for data transmission of an extended CFAN during the response period.

[0047] Figure 14 This is a diagram showing a method for data transmission of a CFAN during the spontaneous period.

[0048] Figure 15 This is a diagram showing a method for data transmission of an extended CFAN during the spontaneous period.

[0049] Figure 16 This is a diagram showing a method for setting a group ID.

[0050] Figure 17 This is a diagram showing a method for setting the group ID of an extended CFAN.

[0051] Figure 18 This is a diagram showing the physical layer frame format.

[0052] Figure 19 This is a diagram showing the preamble format.

[0053] Figure 20 This is a diagram showing the header format.

[0054] Figure 21 This is a diagram showing the encoder of the header check sequence.

[0055] Figure 22 This is a diagram showing the payload format.

[0056] Figure 23 This is a diagram showing the definition of non-return-to-zero level (NRZ-L) coding.

[0057] Figure 24 It is a diagram showing amplitude shift keying (ASK) modulation.

[0058] Figure 25 It is a schematic diagram of Gaussian frequency shift keying (GFSK) modulation.

[0059] Figure 26 It is a diagram of the encoding and modulation process of the preamble.

[0060] Figure 27 It is a diagram of the encoding and modulation process of the header.

[0061] Figure 28 It is a diagram of the encoding and modulation process of the payload.

[0062] Figure 29 It is a diagram of the GFSK modulation signal.

[0063] Figure 30 It is a diagram of the ASK modulation signal.

[0064] Figure 31 It is a design diagram of planar electronic textiles.

[0065] Figure 32 It is a design diagram of linear yarns.

[0066] Figure 33 It is a diagram showing an example of designing a CFAN using parallel conductive materials.

[0067] Figure 34 It is a block diagram showing a network system according to an embodiment of the present invention.

[0068] Figure 35 It is a block diagram showing a computer system for implementing a method according to an embodiment of the present invention. Detailed Embodiments

[0069] The advantages and features of the present disclosure and the methods for realizing them will be clarified from the embodiments described in detail below with reference to the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and can be implemented in various different forms. These embodiments are provided only to make the present disclosure complete and to allow those of ordinary skill in the art to fully recognize the scope of the present disclosure, and the present disclosure will be defined by the scope of the claims. At the same time, the terms used in this specification are used to explain the exemplary embodiments and do not limit the present disclosure. Unless there is a clear contrary description, in this specification, the singular form includes the plural form. The terms "including" and / or "comprising" used herein do not exclude the presence or addition of one or more other components, steps, operations, and / or elements in addition to the above components, steps, operations, and / or elements.

[0070] Terms such as "first" and "second" may be used to describe various components, but the interpretation of these components is not limited to these terms. These terms may be used to distinguish one component from other components. For example, without departing from the scope of the present invention, a "first" component may be named a "second" component, and a "second" component may similarly be named a "first" component.

[0071] It should be understood that when it is stated that a component is "connected" or "coupled" to another component, a component may be directly connected or directly coupled to another component, or connected or coupled to another component with another component interposed therebetween. On the other hand, it should be understood that when it is stated that a component is "directly connected to" or "directly coupled to" another component, the one component may be connected or coupled to the other component without another component interposed therebetween. Other expressions describing the relationship between components, namely "between", "directly between", "adjacent to", "directly adjacent to", etc., should also be interpreted similarly.

[0072] When it is determined that a detailed description of the known art related to the present invention may unnecessarily obscure the gist of the present invention, its detailed description will be omitted.

[0073] The following are the definitions of the key terms used in this specification.

[0074] Definition of Terms

[0075] Wireless Power Transfer (WPT)

[0076] A method of transferring power between devices without a wired connection using an electromagnetic field.

[0077] Conductive Fabric Area Network (CFAN)

[0078] A network that uses conductive fabric to provide reliable communication.

[0079] CFAN-M

[0080] The master node of the CFAN, a device node that manages and establishes associations between nodes in the CFAN.

[0081] CFAN-S

[0082] As a slave node constituting the CFAN, it is a device node other than the CFAN-M in the CFAN.

[0083] CFAN-R

[0084] A device node in the CFAN-S that supports WPT and is used to extend the range of the CFAN. It may be referred to as a repeater node.

[0085] The following are the abbreviations used in this specification and their formal names.

[0086] Full Name of Abbreviations

[0087] ARA: Association Response Acknowledgment

[0088] ARQ: Association Request

[0089] ARS: Association Response

[0090] ASC: Association Status Confirmation

[0091] ASRA: Association Status Response Acknowledgment

[0092] ASRQ: Association Status Request

[0093] ASRS: Association Status Response

[0094] CFAN: Conductive Fabric Area Network

[0095] CFAN-M: Conductive Fabric Area Network Master Node

[0096] CFAN-S: Conductive Fabric Area Network Slave Node

[0097] CFAN-R: Conductive Fabric Area Network Repeater Node

[0098] DA: Data Acknowledgment

[0099] DARA: Disassociation Response Acknowledgment

[0100] DARQ: Disassociation Request

[0101] DARS: Disassociation Response

[0102] DRA: Data Response Acknowledgment

[0103] DRQ: Data Request

[0104] DRRQ: Data Response Request

[0105] DRS: Data Response

[0106] FCS: Frame Check Sequence

[0107] GSRQ: Group ID Setup Request

[0108] GSRS: Group ID Setup Response

[0109] HCS: Header Check Sequence

[0110] LSB: Least Significant Bit

[0111] MAC: Media Access Control

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

[0113] RA: Response Acknowledgment

[0114] RRQ: Response Request

[0115] RSRA: Repeater Setup Response Acknowledgment

[0116] RSRQ: Repeater Setup Request

[0117] RSRS: Repeater Setup Response

[0118] TDMA: Time Division Multiple Access

[0119] UID: Unique Identifier

[0120] WPCN: Wireless Powered Communication Network

[0121] WPT: Wireless Power Transfer

[0122] Range

[0123] The present invention relates to a CFAN system. A protocol for a media access control layer and a physical layer of a conductive fabric network system for communicating with wearable sensors, actuators, processors, batteries, e-textiles, etc. is disclosed. The protocol establishes links and controls for multiple devices on one or more CFANs for data and power transfer.

[0124] The media access control layer protocol is designed to perform the following tasks:

[0125] - Configure a simple network topology for communication

[0126] - Form a variable superframe structure for data transmission and flow control based on channels

[0127] - Allocate resources between nodes to achieve time and power sharing

[0128] The physical layer protocol is designed to perform the following tasks:

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

[0130] - Set a frequency suitable for CFAN

[0131] Overview

[0132] The CFAN system according to the present invention is a communication system capable of sending and receiving data through a network based on conductive fabric. The system operates one or more conductive fabric area networks (hereinafter simply referred to as "CFAN"). CFAN is designed using the characteristics of conductive fabric. The system uses carrier frequencies to ensure stable communication and a wide conductive fabric area even in harsh environments, uses simple and robust modulation methods such as amplitude shift keying (ASK) and frequency shift keying (FSK) to reduce implementation costs and error probabilities, and uses coding techniques to improve the robustness against noise. In principle, a data rate of thousands of bits per second (kbps) is provided in CFAN.

[0133] In addition, the system uses simple and efficient network topologies such as star or tree topologies to achieve low power consumption. Dynamic address allocation is used for packet size and efficient address management. The system uses variable data rates and adaptive link quality control.

[0134] Devices on CFAN are classified into one of three nodes according to their roles, such as a master node, a slave node, and a repeater node. In the present invention, the master node can be represented as CFAN-M, the slave node can be represented as CFAN-S, and the repeater node can be represented as CFAN-R. Basically, CFAN is configured to include one CFAN-M, multiple CFAN-S, and multiple pairs of CFAN-R.

[0135] The CFAN system according to the present invention may have one or more CFANs. In this case, there may be one main CFAN with a main CFAN-M and one or more sub-CFANs, each having a sub-CFAN-M.

[0136] When a slave node subscribes to the network (CFAN), the master node directly or through CFAN-R assigns time slots for each device (i.e., the slave node) according to the request of the slave node and the determination of the master node. The CFAN system according to the present invention uses a time division multiple access (TDMA) method to send and receive data.

[0137] Multiple wearable devices with various shapes, positions, sizes, and weights can be installed in CFAN. The devices can be used for various applications, services, and industries, including the following examples:

[0138] - Health monitoring: Detecting, processing, and responding according to the patient's condition or treatment

[0139] - Sports and fitness: Identifying physical conditions and improving mobility

[0140] - Smart clothing: Using industrial sensors or environmental sensors to track and respond to body activities

[0141] - Military and soft suit: Smart textiles capable of kinematic analysis and rapid situation response

[0142] CFAN-S is systematically distributed throughout the conductive fabric area, and CFAN-M is arranged at the center of CFAN. CFAN-R is located near the edge of the conductive fabric to interconnect the conductive fabric. When CFAN-S receives sensing data from the sensor, CFAN-S sends the received data to CFAN-M through the conductive fabric. CFAN-M can send the data received by CFAN-S to the monitoring center through other physical media such as wireless communication.

[0143] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Throughout the drawings, the same devices will be denoted by the same reference numerals to facilitate an overall understanding of the present invention in describing the present invention.

[0144] Network Components

[0145] (1) Overview

[0146] The main components of CFAN are divided into a time element and a physical element. The time element refers to a superframe composed of a request period, a response period, and a spontaneous period. The physical element refers to a network composed of CFAN-M, CFAN-R, and CFAN-S. CFAN-M manages CFAN, CFAN-R supports WPT and activates multiple CFANs, and CFAN-S communicates with CFAN-M.

[0147] Figure 1 The structure of the superframe (time element) is shown, Figure 2 The structure of the network (physical element) is shown. The node that should be determined first in CFAN is CFAN-M. When CFAN-M sends a request data packet during the request period, the superframe starts. CFAN-M manages the association, disassociation, release, and scheduling of CFAN-R and CFAN-S.

[0148] Meanwhile, the extended CFAN is composed of multiple CFANs. The CFANs included in the extended CFAN are divided into a main CFAN, a sub-CFAN, and an inter CFAN. The main CFAN is a CFAN having a power source and one or more CFAN-Rs, and the sub-CFAN is a CFAN that needs to obtain energy from the main CFAN and has no CFAN-R. In addition, the inter CFAN constitutes a multi-point-to-point wireless power supply communication network (WPCN) between CFAN-R and sub-CFAN-M. The main CFAN-M manages the sub-CFAN-M through the main CFAN-R.

[0149] (2) Time element

[0150] The time element used in CFAN is the time slot of the TDMA method. CFAN-M manages CFAN-R and CFAN-S that can send data, and time slots are assigned one-to-one to all nodes of the CFAN group selected by CFAN-M. The superframe structure of CFAN is composed of a request period, a response period, and a spontaneous period as shown in Figure 1 and the length of the period is variable.

[0151] When several sub-CFANs are associated with the main CFAN and thus expand the CFAN, the superframe structure of all CFANs remains unchanged. The superframe starts with CFAN-M, and CFAN-M sends a response request packet (RR packet) during the request period. The RR packet has information about the ID of CFAN-R and the ID of CFAN-S, and CFAN-R and CFAN-S use the information in the RR packet to send response packets during the response period.

[0152] In the case of multiple CFANs (expanded CFANs), when the main CFAN-M confirms, CFAN-R is assigned a time slot, like other CFAN-S. However, within this time slot, CFAN-R needs to further divide the time slot to send data from the sub-CFAN. In this case, the CFAN-R of the main CFAN is associated with the sub-CFAN-M and CFAN-S that cannot be reached by the main CFAN-M. The main CFAN and the sub-CFAN can operate simultaneously.

[0153] During the request period of the main CFAN, CFAN-M can send RR packets to CFAN-R and CFAN-S so as to return corresponding response packets during the response period. In the sub-CFAN, CFAN-M should send the RR packet to CFAN-S. In the interconnected CFAN (WPCN), CFAN-R needs to send the RR packet to the associated sub-CFAN-M.

[0154] During the response period of the main CFAN, CFAN-R and CFAN-S can send response packets according to the RR packets of CFAN-M received during the request period. The response period can be divided into several time slots according to the number of CFAN-R and CFAN-S selected in the CFAN. The length of each time slot varies according to the length of the response frame and the acknowledgment response. CFAN-M reserves time slots for CFAN-R, CFAN-S, or a specific group using the response period, and the nodes of the assigned group independently send data frames during the response period. The time slot number is determined by the number of time slots, otherwise the time slot number is 0.

[0155] During the response period of the sub-CFAN, the CFAN-S in the sub-CFAN retransmits the response packet to its own CFAN-M according to the RR packet. The response period is divided into time slots according to the number of CFAN-S selected in the sub-CFAN. The length of each time slot varies according to the lengths of the response packet and the acknowledgment packet. The CFAN-S in the assigned group independently sends data frames during the response period.

[0156] During the response period of the Wireless Powered Communication Network (WPCN), the sub-CFAN-M associated with the CFAN-R sends back a response to the sub-CFAN-M based on the RR packet. The response period is divided into time slots according to the number of CFAN-S selected in the sub-CFAN. The length of each time slot varies according to the lengths of the response packet and the acknowledgment packet.

[0157] When no device returns a response packet within a specific period, the spontaneous period of the CFAN starts. During the spontaneous period of the main CFAN, the CFAN-R and CFAN-S can send data without a request from the CFAN-M. During the spontaneous period of the sub-CFAN, the CFAN-S can send data without a request from the CFAN-M. During the spontaneous period of the Wireless Powered Communication Network (WPCN), the sub-CFAN-M can send data through the main CFAN without a request from the CFAN-R. The spontaneous period continues until the CFAN-M sends a request period.

[0158] The superframe of the CFAN is divided into a request period, a response period, and a spontaneous period. The CFAN-M, CFAN-R, and CFAN-S of the CFAN operate as follows in each period.

[0159] [Request Period] During the request period of the main CFAN, the CFAN-M sends RR packets to the CFAN-R and CFAN-S. Based on the RR packet, the receiving CFAN-R or CFAN-S determines whether to send a response packet during the response period. The CFAN-M can determine which CFAN-R and CFAN-S to select from the group that will send during the response period. In the sub-CFAN, the CFAN-M sends RR packets to the CFAN-S and determines whether to send a response packet during the response period after receiving the RR packet. The CFAN-M can determine which CFAN-S to group and send during the response period.

[0160] [Response Period] The selected CFAN-R or CFAN-S of CFAN-M can send a response data packet during the response period. When CFAN-R or CFAN-S sends a response data packet during the response period, the CFAN-M that receives the response data packet sends a response confirmation data packet (RA packet). CFAN-R or CFAN-S that does not receive the RA packet sends a response data packet to each time slot until CFAN-R or CFAN-S receives the RA packet from CFAN-M or a timeout occurs.

[0161] [Spontaneous Period] In the case of the main CFAN or sub-CFAN, when CFAN-R or CFAN-S does not send a response data packet within a specific period, the spontaneous period starts and is maintained until the CFAN-M sends an RR packet. During the spontaneous period, CFAN-R or CFAN-S can send data without a request from CFAN-M.

[0162] (3) Physical Elements

[0163] The physical elements constituting CFAN refer to the devices that are classified into CFAN-M, CFAN-R, and CFAN-S according to their functions. CFAN is a network that can send and receive data between CFAN-N, CFAN-R, and CFAN-S. CFAN-M manages the entire CFAN, and in principle, there is only one CFAN-M in each network. CFAN-M broadcasts an RR packet to all nodes at once to control CFAN-R and CFAN-S. CFAN-R and CFAN-S need to send and receive response data packets under the control of CFAN-M. When there are various CFANs, there should be only one main CFAN and several sub-CFANs. The main CFAN can have one or more CFAN-Rs, but the sub-CFAN does not have a CFAN-R. CFAN can be configured as Figure 2 shown.

[0164] The main CFAN can have one or more power sources, while the sub-CFAN does not directly have a power source. The power source of the main CFAN can be a disposable battery using a bag, and the power source of the sub-CFAN can be a flexible battery, such as a lithium-ion flexible battery or a lithium polymer flexible battery. In addition, as Figure 31 shown, the flexible battery can be a secondary battery based on a conductive fabric layer, where a dielectric is interposed between the conductive fabric layers serving as electrodes forming a supercapacitor structure. Depending on the material constituting the dielectric, the secondary battery can have different charging amounts, different charging speeds, and different charging times. As a method of charging the sub-CFAN, the main CFAN can use the electromagnetic induction method or the optical charging method.

[0165] CFAN-M (Master Node) is the node that manages CFAN. In principle, there is only one CFAN-M in each network, and CFAN-M uses RR packets to manage and control CFAN-R and CFAN-S. In the case of multiple CFANs, there may be only one master CFAN-M in the master CFAN, and there may be only one sub-CFAN-M in each sub-CFAN. The sub-CFAN-M can communicate with the master CFAN-M through the CFAN-R associated with the sub-CFAN-M. All sub-CFAN-Ms can collect energy and store the collected energy in the supercapacitor through the CFAN-R in the master CFAN. The sub-CFAN-M uses the energy to power its own sub-CFAN and sends data to the CFAN-R.

[0166] CFAN-S (Slave Node) is the node that constitutes CFAN (except for CFAN-M and CFAN-R). Each network can have a maximum of 65,519 CFAN-Ss. The response packet is transmitted according to the request packet sent by CFAN-M in the network.

[0167] CFAN-R (Repeater Node) is the node corresponding to CFAN-S and is a device of the master CFAN that can send data to the sub-CFAN-M of the sub-CFAN and receive data from the sub-CFAN-M of the sub-CFAN. CFAN-R can send data to the sub-CFAN-M while performing WPT. The sub-CFAN-M can send all the data of CFAN-S to CFAN-R at any given time, and CFAN-R waits for its corresponding time slot to send data during the response period of the master CFAN. CFAN-R realizes the association between the master CFAN and several sub-CFANs.

[0168] (4) Address Element

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

[0170] CFAN ID is the unique ID that distinguishes each CFAN from other CFANs. This value does not repeat in other CFANs and remains unchanged as long as the CFAN exists. CFAN ID is an 8-bit address ID assigned by CFAN-M. CFAN ID is assigned to the source CFAN ID and the destination CFAN ID. The CFAN ID used for broadcasting to all CFANs can be specified as shown in Table 1 (Specified CFAN ID).

[0171] [Table 1]

[0172] CFAN ID Content Remarks 0xFF All CFANs When Broadcasting to All CFANs 0xF0 - 0xFE Reserved -

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

[0174] [Table 2]

[0175] 1 byte 1 byte 6 bytes Group ID Code of IC Manufacturer Serial Number of IC Manufacturer

[0176] The group ID is an identifier for the CFAN-R group and the CFAN-S group classified in the CFAN. The CFAN-M can request data transmission in units of groups during the request period. The group unit is used according to the application. As shown in Table 3 (Specified group ID), some group IDs can be specified.

[0177] [Table 3]

[0178] Group ID Content Remarks 0xFF All Groups When Selecting All Groups 0xF0 - 0xFE Reserved -

[0179] The node ID is an 8-bit address assigned by the CFAN-M as an identifier to identify each node, rather than the UID. The node ID can be assigned to the source address and the destination address. As shown in Table 4 (Specified group ID), some node IDs can be specified.

[0180] [Table 4]

[0181] Node ID Content Remarks 0xFF All Nodes When Broadcasting or Sending to All Nodes 0xFE Unjoined CFAN-S Default ID of CFAN-S 0xFD Unjoined CFAN-R Default ID of CFAN-R 0xF0 - 0xFC Reserved -

[0182] Network Status

[0183] (1) Overview

[0184] In the CFAN, the CFAN-R and the CFAN-S obtain the active states of network configuration, network association, network disassociation, network association confirmation, data transmission, and network release.

[0185] (2) Network Configuration

[0186] The CFAN-M forms a network by sending a request packet to the CFAN-R and the CFAN-S during the request period. The CFAN ID is included in the request packet so that the CFAN-R or the CFAN-S can identify the associated network. When the CFAN-R or the CFAN-S returns a response packet to the CFAN-M, the main network is formed. The minimum network period refers to the case where there is only the CFAN-M and it consists only of the request period and the spontaneous period.

[0187] In the extended CFAN, the CFAN-R forms a network by sending a request packet containing the CFAN ID to the sub CFAN-M. When the sub CFAN-M returns a response packet to the CFAN-R, the extended network is configured.

[0188] (3) Network Association

[0189] When CFAN-M broadcasts an association request data packet, CFAN-R and CFAN-S transmit the association request data packet received during the response period. Upon reception, CFAN-R and CFAN-S search for the received data packet and associate with the network based on the found data packet. When CFAN-R and CFAN-S find the correct network, CFAN-R and CFAN-S send an association response data packet to CFAN-M. CFAN-M sends a final confirmation to CFAN-R and CFAN-S, and when CFAN-R and CFAN-S receive the final confirmation, network association is completed in the main CFAN. In the extended CFAN, CFAN-M sends an association request data packet to all CFAN-Rs, and CFAN-R accordingly sends the association request data packet to the sub-CFAN-M. The sub-CFAN-M responds to CFAN-R with respect to the received association request data packet, and CFAN-R sends the response data packet to the main CFAN-M. Then, the main CFAN-M sends a confirmation to the sub-CFAN-M through CFAN-R. Finally, CFAN-S sends an association request data packet to the CFAN-S belonging to the sub-CFAN through CFAN-R and the sub-CFAN-M. Subsequently, CFAN-S responds to the main CFAN-R with an association response data packet, and the main CFAN-M sends an association response confirmation data packet. After the CFAN-S of the sub-CFAN receives the confirmation, the extended network association is completed.

[0190] (4) Network Disassociation

[0191] The CFAN-S, CFAN-R, or sub-CFAN-M associated with the CFAN can follow the request of CFAN-M or can automatically disassociate. In the extended CFAN, the node association of the sub-CFAN is performed by CFAN-R and the sub-CFAN-M to reach the CFAN-S of the sub-CFAN-S. The main CFAN-M can send a disassociation request to the CFAN-S, CFAN-R, or sub-CFAN-M according to the current network state or the type of service for forced disassociation. In the case of voluntary disassociation, the main CFAN-M can identify the disassociation status of the CFAN-S, CFAN-R, or sub-CFAN-M through the response result of the next association request data packet.

[0192] (5) Network Association Check

[0193] The association status of CFAN-S, CFAN-R, or sub-CFAN-M in the network can be requested by the master CFAN-M. To check the network association status, the master CFAN-M sends an association status request data packet to CFAN-S, CFAN-R, or sub-CFAN-M. CFAN-S, CFAN-R, or sub-CFAN-M returns an association status response data packet to the master CFAN-S. When the confirmation data packet is sent from the master CFAN-M to CFAN-S, CFAN-R, or sub-CFAN-M in the same process, the network association check is completed. When the master CFAN-M sends an association status data packet to the CFAN-S of the sub-CFAN in the extended CFAN and receives an association status data packet from it, the data packet passes through CFAN-R and sub-CFAN-M.

[0194] (6) Data transmission

[0195] When the master CFAN-M sends a data RR data packet during the request period, CFAN-S, CFAN-R, or sub-CFAN-M responds to the data response data packet of the master CFAN-M according to the type of the requested data. The master CFAN-M that receives the data response data packet sends a data confirmation data packet, and after CFAN-S, CFAN-R, or sub-CFAN-M receives the data confirmation data packet, the data transmission is completed. In the extended CFAN, the master CFAN-M and the CFAN-S of the sub-CFAN exchange data confirmation data packets through CFAN-R and sub-CFAN-M.

[0196] (7) Network release

[0197] CFAN release can be divided into normal release and abnormal release due to emergencies according to the request of the master CFAN-M. Normal release is achieved by the master CFAN-M determining the release status and distributing the request to all CFAN-S, CFAN-R, and sub-CFAN-M to cancel the network. Abnormal network release refers to the situation where all participating CFAN-S, CFAN-R, and sub-CFAN-M terminate simultaneously.

[0198] (8) Network node status (CFAN node status)

[0199] CFAN node status includes CFAN-M status, CFAN-S status, and CFAN-R status. When the master CFAN is turned on, the master CFAN-M switches to the request period. When there is no response, CFAN-M remains in the request period. When CFAN-M receives a response confirmation data packet, the status changes to the response period. When CFAN-R is turned on in the master CFAN, CFAN-R can turn on the nearby sub-CFAN-M through WPT.

[0200] Figure 3It is the state diagram of CFAN-M.

[0201] When the power is turned on by the wired power supply through the conductive fabric, the state of CFAN-M is in the standby state. When CFAN-M is a sub-CFAN that expands CFAN and the power is turned on through WPT, CFAN-M will be in the standby state. In the standby state, when a superframe starts or an application sends a command, the state of CFAN-M is in the data packet generation state. CFAN-M generates RR data packets and sends the generated RR data packets to CFAN-R and CFAN-S, and the state of CFAN-M returns to the standby state.

[0202] When CFAN-M receives a data packet from CFAN-R or CFAN-S in the standby state, the state of CFAN-M is in the data packet analysis state. When the source ID and destination ID of the received data packet belong to the current CFAN, the state of CFAN-M is in the data packet generation state. Then, CFAN-M generates RA or DA data packets and sends the generated RA or DA data packets to CFAN-R or CFAN-S of the corresponding medium. After that, the state of CFAN-M returns to the standby state.

[0203] On the other hand, when CFAN-M receives an RA or DA data packet in the data packet analysis state, or there are mismatches or errors in the data packet, the state of CFAN-M immediately returns to the standby state. When there is a timeout, mismatch, or error in the confirmation data packet received in the standby state, CFAN-M regenerates a data packet in the data packet generation state and re-sends the regenerated data packet to CFAN-R and CFAN-S through the medium, and then the state of CFAN-M returns to the standby state. When these failures occur continuously, the data packet retransmission process is repeated as needed (up to N times). During the (N + 1) process, the state of CFAN-M remains in the standby state.

[0204] In the extended CFAN, when the CFAN-R approaches the sub-CFAN-M, the sub-CFAN-M can receive wireless power from the CFAN-R and use it to supply the received wireless power to the sub-CFAN. When the main CFAN-M sends a data packet to the sub-CFAN, the CFAN-R sends the data packet to the sub-CFAN-M through the wireless channel, and the sub-CFAN-M switches from the standby state to the data packet analysis state. When the destination CFAN ID corresponds to the sub-CFAN ID, the sub-CFAN-M switches to the data packet generation state and sends the data packet to the corresponding CFAN-S or CFAN-S. Then, the sub-CFAN-M returns to the standby state. When the sub-CFAN sends a data packet to the main CFAN, the sub-CFAN-M switches from the standby state to the data packet analysis state and receives the data packet from the CFAN-S. When the destination CFAN ID corresponds to the main CFAN ID, the sub-CFAN-M switches to the data packet generation state and sends the data packet to the CFAN-R through the wireless channel within the corresponding period. Subsequently, the sub-CFAN-M returns to the standby state.

[0205] Once the CFAN-S starts running, it returns to the standby state. When the application sends system data in the standby state, the state of the CFAN-S is in the data packet generation state. The CFAN-S generates a data packet during the spontaneous period and sends the generated data packet to the CFAN-M. Then, the state of the CFAN-S returns to the standby state.

[0206] When the CFAN-S receives a data packet in the standby state, the CFAN-S returns to the data packet analysis state and analyzes the received data packet. When the received data packet is an RR data packet and the destination ID matches, the state of the CFAN-S is in the data packet generation state, and the CFAN-S sends a response data packet to the CFAN-M. Then, the state of the CFAN-S returns to the standby state.

[0207] Figure 4 is the state diagram of the CFAN-S. When the data packet analyzed by the CFAN-S received is an error data packet or an RA or DA data packet, the CFAN-S is in the standby state. When the CFAN-S does not receive an RA or DA data packet during the timeout period, the state of the CFAN-S changes from the standby state to the data packet generation state. Then, the CFAN-S regenerates the response data packet and re-sends the regenerated response data packet to the CFAN-M, and the state of the CFAN-S switches from the data packet generation state to the standby state. The retransmission of the response data packet is repeated multiple times (up to N times) as needed. During the (N + 1)th timeout period, the CFAN-S remains in the standby state.

[0208] Figure 5It is the state diagram of CFAN-R.

[0209] When the power is turned on, the state of CFAN-R is in the standby state. When CFAN-R receives a data packet in the standby state, CFAN-R is in the data packet analysis state and analyzes the received data packet. When the received data packet is an RR data packet and the destination ID matches, the state of CFAN-R is in the data packet generation state, and a response data packet is sent through an appropriate medium. Then, the state of CFAN-R switches to the standby state.

[0210] When the received data packet in the data packet analysis state is a data packet error or an RA or DA data packet, CFAN-R is in the standby state. When CFAN-R does not receive an RA data packet or a DA data packet during the timeout period, CFAN-R switches from the standby state to the data packet generation state. Then CFAN-R regenerates the response data packet and re-sends the regenerated response data packet to CFAN-M, and the state of CFAN-R is in the standby state. The retransmission of the response data packet is repeated as needed (up to N times). During the (N + 1)th timeout period, CFAN-S remains in the standby state.

[0211] In the extended CFAN, when the sub-CFAN-M approaches CFAN-R, CFAN-R can supply power to the sub-CFAN through WPT in the standby state. When the main CFAN-M sends a data packet to the sub-CFAN, CFAN-R switches from the standby state to the data packet analysis state. When the destination CFAN ID corresponds to the sub-CFAN ID, CFAN-R switches to the data packet generation state and sends a data packet to the sub-CFAN-M through the wireless channel. Then, CFAN-R returns to the standby state. When the sub-CFAN-M sends a data packet to the main CFAN through the wireless channel, CFAN-R switches from the standby state to the data packet analysis state to receive the data packet. When the destination CFAN ID corresponds to the main CFAN ID, CFAN-R switches to the data packet generation state and sends a data packet to the main CFAN-M through the wired channel within the corresponding period. Then, CFAN-R returns to the standby state.

[0212] MAC Layer Frame Format

[0213] (1) Overview

[0214] The media access control (MAC) frame format of CFAN consists of a frame header and a frame body. The frame header has information about the data related to the association between CFAN-R and CFAN-S, and the frame body has the data to be transmitted between CFAN nodes.

[0215] (2) Frame Format

[0216] All frame formats of the MAC are composed of a frame header and a frame body, as shown in Table 5.

[0217] [Table 5]

[0218]

[0219] The frame header consists of a frame control, a source CFAN ID, a source address, a destination CFAN ID, a destination address, and a sequence number. The frame header has information for frame transmission / reception and flow control. The frame header can be used for data transmission.

[0220] The frame control field consists of a frame type, an acknowledgment policy, a first fragment, a last fragment, and a protocol version, as shown in Table 6. The unit in the first row of Table 6 is bits.

[0221] [Table 6]

[0222] 0-2 3-4 5 6 7-8 9-15 Frame Type Acknowledgment Strategy First Fragment Last Fragment Protocol Version Reserved

[0223] The description of each field included in the frame control field is as follows:

[0224] 1) The frame type field consists of 3 bits. The frame type field will be described in detail below.

[0225] 2) The acknowledgment policy field consists of 2 bits. When the received frame is an acknowledgment frame, the received frame indicates the policy of the received acknowledgment frame; otherwise, the received frame indicates the acknowledgment frame policy of the destination node. Each item of the acknowledgment policy will be described in detail below.

[0226] a) No acknowledgment: The destination node does not acknowledge the transmitted frame. The source node considers the transmission successful regardless of the transmission result. This method can be used for frames in 1:1 or 1:N transmissions that do not require an ACK.

[0227] b) Single acknowledgment: The destination node of the received frame sends an acknowledgment frame to the source node as a response after a short inter-frame space (SIFS). This acknowledgment policy can only be used for 1:1 transmissions.

[0228] c) Multiple acknowledgments: The destination node of the received frame sends acknowledgment frames to multiple source nodes as a response after SIFS. This acknowledgment policy can be used for 1:N transmissions.

[0229] d) Data acknowledgment: The destination node of the received data frame sends a data acknowledgment frame to the source node as a response after SIFS. This acknowledgment policy can only be used for 1:1 data transmissions.

[0230] 3) The first fragment field consists of 1 bit. "1" indicates that the frame refers to the start of a higher-level request, response, or data packet, and "0" indicates that the frame does not refer to the start.

[0231] 4) The last fragment field consists of 1 bit. A value of "1" indicates that the frame refers to the end of a higher-level request, response, or packet, and a value of "0" indicates that the frame does not refer to the end.

[0232] 5) The protocol version field consists of 2 bits. Its size and position are fixed and independent of the protocol version of the system. The current value is 0, and this value is incremented by 1 whenever a new version is released. When a node receives a packet with a version higher than its own, the packet is discarded without notifying the source node.

[0233] 6) Reserved: This field is ready for future use.

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

[0235] The node ID is used to identify nodes in each network. Both the source node ID and the destination ID consist of 1 byte.

[0236] The sequence number field is 8 bits long and represents the frame sequence number. In data frames, a sequence number between 0 and 255 is assigned to each packet by incrementing a counter, and the sequence number is reset to 0 again when it reaches 255.

[0237] The frame body consists of a payload and a Frame Check Sequence (FCS). The payload includes the data to be transmitted between CFAN nodes, and the frame check sequence is used to check for errors in the payload. Depending on the frame type in the frame control field, each payload has a different format.

[0238] The payload has data to be sent between each of the main CFAN-M and CFAN-S, CFAN-R and sub-CFAN-M. The length of the payload is a variable value between 0 and 247.

[0239] The Frame Check Sequence (FCS) is 16 bits long and is used to confirm that the frame body has been received without error. The FCS is generated using the 16th-order standard generating polynomial provided in Equation 1.

[0240] [Equation 1]

[0241] G(x) = x 16 +x 12 +x 5 +1

[0242] (3) Frame Type

[0243] The frame types are defined as a total of four types: request frame, response frame, data frame, and acknowledgment frame. Table 7 shows the frame types and the binary values, contents, and time elements (time periods) for each frame type.

[0244] [Table 7]

[0245]

[0246] The request frame is used when the main CFAN-M sends a request packet to a specific CFAN-S, CFAN-R, or sub CFAN-M of the CFAN during the request period, or broadcasts information to all CFAN-S, CFAN-R, and sub CFAN-M. In an extended CFAN, the request frame is used when the CFAN-R sends a request packet to the sub CFAN-R during the request period. The request frame can be configured as shown in Table 8. The unit in the first row of Table 8 is bytes.

[0247] [Table 8]

[0248]

[0249] The response frame is used when the CFAN-S, CFAN-R, or sub CFAN-M sends a response packet during the request period of a request from the main CFAN-M. The appropriate CFAN-S, CFAN-R, or sub CFAN-M sends the response packet a specified number of times during the request period until the CFAN-S, CFAN-R, or sub CFAN-M receives an acknowledgment packet. In an extended CFAN, the sub CFAN-M sends a response packet during the request period of a CFAN-R request. The response frame can be configured as shown in Table 9. The unit in the first row of Table 9 is bytes.

[0250] [Table 9]

[0251]

[0252] The data frame is used when the CFAN-S, CFAN-R, or sub CFAN-M sends data to the main CFAN-M during the response period, regardless of whether there is a request from the CFAN-M. In an extended CFAN, the sub CFAN-M sends data to the CFAN-R. The data frame can be configured as shown in Table 10. The unit in the first row of Table 10 is bytes.

[0253] [Table 10]

[0254]

[0255] The types of confirmation frames include Response Acknowledgment (RA) frames and Data Acknowledgment (DA) frames. When the master CFAN-M sends a request frame in an RA frame, the CFAN-S, CFAN-R, or sub CFAN-M receives the request data packet and sends a response data packet, and the master CFAN-M sends the response data packet and an RA data packet. The RA data of the received response data packet is recorded on the payload of the confirmation frame. The master CFAN-M that receives the appropriate response frame sends an RA frame after the short frame interval in the request period to respond to the CFAN-S, CFAN-R, or sub CFAN-M that sent it. The DA frame is an acknowledgment frame for the received data packet. The master CFAN-M sends a DA frame after the short frame interval in the response period to respond to the CFAN-S, CFAN-R, or sub CFAN-M that sent the data packet. In an extended CFAN, the CFAN-R responds to the sub CFAN-M that sent a response or data packet by sending an RA or DA frame within the response loop. Table 11 is an example of the format of the response acknowledgment frame. The unit in the first row of Table 11 is bytes.

[0256] [Table 11]

[0257]

[0258] Table 12 and the DA frame consist of a frame header and a frame body. When the destination CFAN ID is 0xFF and the destination node ID is 0xFE or 0xFD, the destination CFAN ID and the destination node ID correspond to the unjoined CFAN-SID and the unjoined CFAN-RID respectively. In this case, the destination CFAN ID and the destination node ID should include the UID field.

[0259] [Table 12]

[0260]

[0261] (4) Payload Format

[0262] The payload format is generated in different ways according to the frame types including request frames, response frames, data frames, confirmation frames, etc.

[0263] [Request Frame]

[0264] Table 13 relates to the payload format of the request frame. As shown in Table 13, the payload of the request frame consists of a group ID, a request code, a length, and one or more request blocks according to the request. The unit in the first row of Table 13 is bytes.

[0265] [Table 13]

[0266]

[0267] The group ID field consists of 1 byte and is used to send RR data packets to a specific group. When the group ID is 0xFF, the group ID indicates that the CFAN-M requests responses from all CFAN-S, CFAN-R, and sub-CFAN-M groups. Details related to the group ID are as described above.

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

[0269] [Table 14]

[0270]

[0271] The length field consists of 1 byte. The length field represents the total length of the request block, and the length field value varies according to the length and number of request blocks.

[0272] The data format of the request block is configured differently according to the request code, and one or more request blocks can be included in the payload of the request frame.

[0273] Details of the data format of each request block are as follows.

[0274] 1) Association request

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

[0276] [Table 15]

[0277] 8 bytes UID Mask

[0278] 2) Disassociation request

[0279] The block format of the DARQ can be configured as shown in Table 16. The first byte and the second byte constitute the CFAN ID and node ID of the CFAN-S, CFAN-R, or sub-CFAN-M of the DARQ, and the next 1 byte constitutes the time slot number for the response period. When the node ID is 0xFF, the DARQ is sent to all CFAN-R and CFAN-S within the group ID.

[0280] [Table 16]

[0281] 1 byte 1 byte 1 byte CFAN ID Node ID Time Slot Number

[0282] 3) Association status request

[0283] The block format of ASRQ can be configured as shown in Table 17. The first byte and the second byte constitute the CFAN ID of CFAN-S, CFAN-R, or sub-CFAN-M of ASRQ and the node ID. When the CFAN ID is 0xFF and the node ID is 0xFF, ASRQ is requested from all CFAN-Rs and CFAN-Ss within the group ID.

[0284] [Table 17]

[0285] 1 byte 1 byte 1 byte CFAN ID Node ID Time Slot Number

[0286] 4) Data Request

[0287] The block format of DRQ can be configured as shown in Table 18. The first byte and the second byte constitute the CFAN ID and the node ID, the next 1 byte constitutes the time slot number, and the last L bytes constitute the received data type. The data type is determined according to the application product.

[0288] [Table 18]

[0289] 1 byte 1 byte 1 byte L bytes CFAN ID Node ID Time Slot Number Data

[0290] 5) Group ID Setting Request

[0291] The block format of GSRQ can be configured as shown in Table 19. The first byte and the second byte constitute the CFAN ID and the node ID, the next 1 byte constitutes the time slot number, and the last byte constitutes the group ID to be set.

[0292] [Table 19]

[0293] 1 byte 1 byte 1 byte L bytes CFAN ID Node ID Time Slot Number Group ID

[0294] [Response Frame]

[0295] Table 20 relates to the payload format of the response frame. The payload format of the response frame has the response information of the request of CFAN-M. In the extended CFAN, the payload format has the response message of the request of CFAN-R. The first byte constitutes the group ID, the second byte constitutes the response code, the third byte constitutes the response data length L, and the next L bytes constitute the response data. The unit in the first row of Table 20 is byte.

[0296] [Table 20]

[0297]

[0298] The group address field consists of 1 byte and is used to send the RR data packet to a specific group. The details of the group ID are as described above.

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

[0300] [Table 21]

[0301]

[0302] The length field consists of 1 byte and represents the length of the response data. The length field varies according to the response data.

[0303] The response data format is divided as follows:

[0304] 1) Association response

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

[0306] [Table 22]

[0307] 8 bytes UID

[0308] 2) Disassociation response

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

[0310] [Table 23]

[0311] 8 bytes UID

[0312] 3) Association status response

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

[0314] [Table 24]

[0315] 8 bytes 1 byte UID Status Value

[0316] [Table 25]

[0317] Value Content 0x00 Disassociation Status 0x01 Association Status 0x02 – 0xFF Reserved

[0318] 4) Data response

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

[0320] [Table 26]

[0321] 1 byte 1 byte L bytes CFAN ID Node ID Requested Data

[0322] 5) Group ID Setting Response

[0323] The block format of GSRS can be configured as shown in Table 27. GSRS data consists of an 8-byte UID and a 1-byte change group ID.

[0324] [Table 27]

[0325] 8 bytes 1 byte UID Assigned Group ID

[0326] [Data Frame]

[0327] The payload of the data frame includes the data to be transmitted. Table 28 relates to the payload format of the data frame. The data frame consists of an 8-byte UID and L bytes of data.

[0328] [Table 28]

[0329] 8 bytes L bytes UID Data

[0330] [Acknowledgment Frame]

[0331] The payload of the RA frame includes data related to the received response packet. Table 29 is a table regarding the payload format of the acknowledgment frame. The first byte constitutes the group ID, the second byte constitutes the response acknowledgment code, the third byte constitutes the length L, and the next L bytes constitute the response acknowledgment block. The unit in the first row of Table 29 is a byte.

[0332] [Table 29]

[0333]

[0334] The group ID field consists of 1 byte and is used to send RR packets to a specific group. The details of the group ID are as described above.

[0335] Table 30 is a table regarding the response acknowledgment code. The response acknowledgment code type can be configured as shown in Table 30.

[0336] [Table 30]

[0337]

[0338] The length field consists of 1 byte. The length field indicates the length of the response acknowledgment data and varies according to the response acknowledgment data.

[0339] The response acknowledgment block format is classified as follows.

[0340] 1) Association Response Acknowledgment

[0341] The block format of the ARS confirmation (ARA) can be configured as shown in Table 31. The first 8 bytes constitute the UID, and the next 2 bytes constitute the allocated CFAN ID and the allocated node ID. When the allocated CFAN ID is 0xFF and the allocated node ID is 0xFE or 0xFD, the allocated CFAN-ID and the allocated node ID correspond to the addresses of the unjoined CFAN-S and the unjoined CFAN-R respectively, which means the ARQ is rejected.

[0342] [Table 31]

[0343] 8 bytes 1 byte 1 byte UID Assigned CFAN ID Assigned Node ID

[0344] 2) Disassociation response confirmation

[0345] The block format of the DARS confirmation (DARA) can be configured as shown in Table 32. The first 8 bytes constitute the UID, and the last 2 bytes constitute the CFAN ID and the node ID. If disassociation is not allowed, the allocated CFAN ID and the node ID are used. When disassociation is not allowed, 0xFF is recorded for the unjoined CFAN, and 0xFE or 0xFD is recorded for the unjoined CFAN-S ID or the unjoined CFAN-R respectively.

[0346] [Table 32]

[0347] 8 bytes 1 byte 1 byte UID CFAN ID Node ID

[0348] 3) Association status response confirmation

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

[0350] [Table 33]

[0351] 8 bytes UID

[0352] 4) Data response confirmation

[0353] The block format of the DR confirmation (DRA) can be configured as shown in Table 34. The first two bytes constitute the CFAN ID and the node ID, and the next byte is reserved.

[0354] [Table 34]

[0355] 1 byte 1 byte 1 byte CFAN ID Node ID Reserved

[0356] 5) Group ID setting response confirmation

[0357] The block format of GSR confirmation (GAIRA) 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 (set status value).

[0358] [Table 35]

[0359] 8 bytes 1 byte UID Group ID Setting Status Value

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

[0361] [Table 36]

[0362] Value Content 0x00 Change Completed 0x01 Change Failed 0x02 - 0xFF Reserved

[0363] MAC Layer Functions

[0364] (1) Overview

[0365] In the MAC layer of CFAN, the association, disassociation, and ASC processes are used to manage the CFAN network. Data transmission may occur during the response period or the spontaneous period. In addition, a group address initialization function is provided to manage the CFAN-S group, CFAN-R group, and sub-CFAN-M group.

[0366] (2) Network Association and Disassociation

[0367] To enable CFAN-R or CFAN-S to communicate with CFAN-M, CFAN-R or CFAN-S should first be associated with CFAN. Each CFAN-R and CFAN-S searches for a previously formed CFAN, and when the search is successful, they are associated with the corresponding CFAN. In an extended CFAN, the sub-CFAN should be associated with the main CFAN.

[0368] [Association]

[0369] Figure 6It is a diagram showing a method for associating CFAN. When CFAN-M sends an ARQ packet that has not been associated with CFAN to CFAN-R or CFAN-S during a request period, CFAN-R or CFAN-S sends an ARS packet to CFAN-M during a response period. CFAN-M determines the association status of CFAN with the appropriate CFAN-R or CFAN-S and notifies the result via an RA packet. When association is permitted, the assigned node address ID is included in the RA packet. When association is denied, the default CFAN ID and node ID are recorded accordingly. CFAN-M continues to send ARS packets in each superframe until CFAN-M receives an ARA packet, at which time CFAN-M may be unable to receive the ARS packet due to a data error in the RA packet or CFAN-R or CFAN-S may be unable to receive the RA packet. When CFAN-R or CFAN-S receives the RA packet from CFAN-M, the association is completed.

[0370] Figure 7 It is a diagram showing a method for associating an extended CFAN. In an extended CFAN, the main CFAN-M sends an association request packet (ARQ packet) to CFAN-S of a sub-CFAN that has not been associated with CFAN through CFAN-R and the sub-CFAN-M. Then, CFAN-S sends an association response packet (ARS packet) to the main CFAN-M through the sub-CFAN-M and CFAN-R. After receiving the association response, the main CFAN-M determines the appropriate association status of CFAN-S with CFAN and notifies the result via an ARA packet. When association is permitted, the assigned CFAN ID and the assigned node ID are included in the ARA packet. When association is denied, the default CFAN ID and the default node ID are recorded accordingly.

[0371] [Disassociation]

[0372] Figure 8FIG. is a diagram showing a method of releasing the association of CFAN. When CFAN-M sends a disassociation request packet (DARQ packet) to CFAN-R or CFAN-S associated with CFAN during the request period, CFAN-R or CFAN-S sends a disassociation response packet (DARS packet) to CFAN-M during the response period. CFAN-M determines the disassociation status of the appropriate CFAN-R or CFAN-S from CFAN and notifies the result through a disassociation response confirmation packet (DARA packet). When disassociation is allowed, the CFAN ID and node ID address of the DARA packet are recorded as the default CFAN ID and the default node ID, and when disassociation is rejected, the existing node ID address is recorded. When CFAN-M does not receive the DARS packet, or when CFAN-R or CFAN-S may not be able to receive the DARA packet due to a data error in the DARA packet sent by CFAN-M, even if CFAN-M has received the DARS packet, CFAN-R or CFAN-S will continue to re-send the DARS packet to CFAN-M in each superframe until it receives the DARA packet. When CFAN-R or CFAN-S receives the DARA packet from CFAN-M, the association is completed.

[0373] Figure 9 FIG. is a diagram showing a method of releasing the association of an extended CFAN. In an extended CFAN, the main CFAN-M sends a DARQ packet to CFAN-S of the sub-CFAN associated with CFAN through CFAN-R and the sub-CFAN-M. Then, CFAN-S sends the DARS packet to the main CFAN-M through the sub-CFAN-M and CFAN-R. After receiving the association response, the main CFAN-M determines the appropriate disassociation status of CFAN-S from CFAN and notifies the result through the DARA packet. When disassociation is allowed, the CFAN ID and node ID address of the DARA packet are recorded as the default CFAN ID and the default node ID, and when disassociation is rejected, the existing CFAN ID and node ID address are recorded.

[0374] [Association Status Check]

[0375] Figure 10This is a diagram showing the method for confirming the association status of CFAN. During the request period, CFAN-M sends an Association Status Request Packet (ASRQ packet) to CFAN-R or CFAN-S associated with CFAN. CFAN-R or CFAN-S sends an Association Status Response Packet (ASRR packet) to CFAN-M during the response period. CFAN-M checks the association status of the appropriate CFAN-R or CFAN-S in the Association Status Response Acknowledgment Packet (ASRA packet) and sends the checked Association Status Response Acknowledgment Packet to CFAN. When CFAN-M may be unable to receive the ASRS packet, or due to data errors in the ASRA packet, CFAN-R or CFAN-S attempting to send the ASRS packet may be unable to receive the ASRA packet, CFAN-R or CFAN-S continues to send the ASRS packet to CFAN-M in each superframe until CFAN-R and CFAN-S receive the ASRS packet. When CFAN-R or CFAN-S receives the ASRA packet from CFAN-M, the ASRS is completed. That is, when CFAN-R or CFAN-S receives the ASRA packet from CFAN-M, the association status check is completed.

[0376] Figure 11 This is a diagram showing the method for confirming the association status of extended CFAN. In extended CFAN, the main CFAN-M sends the ASRQ packet to CFAN-S of the sub-CFAN through CFAN-R and the sub-CFAN-M. Next, CFAN-S sends the ASRS packet to the main CFAN-M through the sub-CFAN-M and CFAN-R. After receiving the ASRS packet, the main CFAN-M determines the appropriate association status of CFAN-S relative to CFAN and sends the result through the ASRA packet.

[0377] (3) Data Transmission

[0378] The time when data can be sent in CFAN is the response period or the spontaneous period. During the response period, data can be sent according to a request from CFAN-M, while during the spontaneous period, data can be sent without a request from CFAN-M.

[0379] [Data Transmission during the Response Period]

[0380] Figure 12It is a diagram showing the data transmission method of CFAN during the response period. When CFAN-M sends a data request packet (DRQ packet) to CFAN-R or CFAN-S associated with CFAN during the request period, CFAN-R or CFAN-S sends a data response packet (DRS packet) during the response period. CFAN-M receives the DRS packet from CFAN-R or CFAN-S and then sends a data response acknowledgment packet (DRA packet). When CFAN-M does not receive the DRS packet from CFAN-R or CFAN-R or CFAN-S does not receive the DRA packet due to a packet error, CFAN-R or CFAN-S continues to send the DRS packet in each time slot until CFAN-R and CFAN-S receive the DRAM packet. When CFAN-R or CFAN-S receives the DRA packet from CFAN-M, the data transmission process during the response period is completed.

[0381] Figure 13 It is a diagram showing the data transmission method of extended CFAN during the response period. In extended CFAN, the main CFAN-M sends a DRQ packet to CFAN-S of the sub-CFAN through CFAN-R and the sub-CFAN-M. Then, CFAN-S sends the DRS packet to the main CFAN-M through the sub-CFAN-M and CFAN-R, and the main CFAN-M that receives the response sends the DRA packet to CFAN-S. When CFAN-S receives the DRA packet from CFAN-M, the data transmission process during the response period is completed.

[0382] [Data Transmission During the Spontaneous Period]

[0383] Figure 14 It is a diagram showing the data transmission method of CFAN during the spontaneous period. When CFAN-R or CFAN-S does not send a response packet during the timeout period, the spontaneous period starts. The spontaneous period continues until CFAN-M sends an RR packet. CFAN-R or CFAN-S can send data without a request from CFAN-M during the spontaneous period. When a system interruption occurs, CFAN-R or CFAN-S can send data without a request from CFAN-M. When CFAN-M does not receive a packet due to a packet error or CFAN-R or CFAN-S does not receive a DA packet, CFAP-S continues to send packets to CFAN-M until CFAN-S receives the DA packet. When CFAN-R or CFAN-S receives the DA packet from CFAN-M, the data transmission process during the spontaneous period is completed.

[0384] Figure 15Figure showing a method of data transmission for an extended CFAN during a spontaneous period. In the extended CFAN, the CFAN-S of the sub-CFAN can transmit data during the spontaneous period without a request from the main CFAN-M. When a system interruption occurs, the CFAN-S can transmit data without a request from the main CFAN-M.

[0385] (4) Group ID setting

[0386] Figure 16 Figure showing a method of group ID setting. When the CFAN-M sends a group ID setting request packet (GAIRQ packet) to the CFAN-R or CFAN-S associated with the CFAN during the request period, the CFAN-R or CFAN-S sends a group ID setting response packet (GAIRR packet) during the response period. The CFAN-M confirms the group address initialization status of the corresponding CFAN-R or CFAN-S and then sends a group ID setting response confirmation packet (GAIRA packet).

[0387] Figure 17 Figure showing a method of group ID setting for an extended CFAN. When the main CFAN-M sends a GAIRQ packet to the CFAN-S of the sub-CFAN associated with the CFAN in the extended CFAN during the request period, the CFAN-S sends 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 sends a GAIRA packet.

[0388] Physical Layer

[0389] (1) PHY layer frame format

[0390] [Overview]

[0391] The physical layer (PHY layer) frame format of the CFAN will be described below. Figure 18 Figure showing the physical layer frame format. Each physical layer frame consists of a preamble, a header, and a payload. As Figure 18 shown, the physical layer frame consists of three parts such as a preamble, a header, and a payload. When transmitting a data packet, the preamble is sent first, the header is sent next, and the payload is sent last. The transmission and reception of the data packet start from the LSB.

[0392] [Preamble]

[0393] Figure 19 Figure showing the preamble format. As Figure 19As shown, the preamble consists of a part called the synchronization sequence. The 16-bit synchronization sequence consists of a 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.

[0394] The preamble is encoded using TYPE 0, which will be described later.

[0395] [Header]

[0396] Figure 20 is a diagram showing the header format. The header is added after the preamble to send information related to the payload. As Figure 20 shown, the header consists of 24 bits. Bits 0 to 2 constitute the data rate and coding field. Bits 3 to 10 constitute the payload data length field. Bits 16 to 23 constitute the Cyclic Redundancy Check-8 Header Check Sequence (CRC-8HCS). The header is encoded using TYPE 0, which will be described later. Table 37 is a table regarding the header definition of the physical layer.

[0397] [Table 37]

[0398]

[0399] Table 38 is a definition table regarding data rate, modulation, and coding. According to the data rate and coding, bits 0 to 2 can be set to the values shown in Table 38. However, the data rate in Table 38 can be changed to other values. The details of Types 0 to 7 will be described below.

[0400] [Table 38]

[0401] Type Value (b2 b1 b0) Data Rate Modulation and Coding Type 0 000 32 kbps GFSK + NRZ-L Type 1 001 128 kbps GFSK + NRZ-L Type 2 010 512 kbps GFSK + NRZ-L Type 3 011 1024 kbps GFSK + NRZ-L Type 4 100 1 kbps ASK + NRZ-L Type 5 101 2 kbps ASK + NRZ-L Type 6 110 4 kbps ASK + NRZ-L Type 7 111 8 kbps ASK + NRZ-L

[0402] The payload data length is represented by an unsigned 8-bit integer. The payload data length represents the number of octets of the payload excluding the FCS. The range of the payload data length is from 0x00 to 0xFF bytes.

[0403] CRC-8HCS is used to check for errors in the header. The HCS processes the data rate and coding, the payload data rate, and 5 reserved bits. The original polynomial is as shown in Equation 2.

[0404] [Equation 2]

[0405] g(D)=(1 + D)(1 = D 2 + D 3 + D 4 + D 7 ) = 1 + D + D 2 + D 5 + D 7+D 8

[0406] Figure 21 This is a diagram of an encoder that shows the header check sequence. The processing order of the header check is as Figure 21 shown. All registers are initialized to 0.

[0407] When Figure 21 the switch “S” is in “1”, the data is accumulated. When the last bit is accumulated, the switch S moves to “2”, and the HCS is sent from the register starting from D7.

[0408] [Payload]

[0409] Figure 22 This is a diagram that shows the payload format. As Figure 22 shown, the payload consists of variable-length data and FCS. When the payload data length field in the header is 0, the FCS is not sent.

[0410] [Frame Check Sequence (FCS)]

[0411] The CRC-16 FCS defined in Table 39 is used to check for errors in the payload. The FCS processes variable-length data. The original polynomial is X 16 +X 12 +X 5 +1. All registers are initialized to 1. The frame check sequence is obtained by inverting the calculated CRC-16 bits.

[0412] [Table 39]

[0413] CRC Length Polynomial Preset Residue ISO / IEC 13239 16 bits <![CDATA[X 16 +X 12 +X 5 +l]]> 0xFFFF 0x1D0F

[0414] (2) Encoding and Modulation

[0415] [Encoding]

[0416] Figure 23 This is a diagram that shows the definition of non-return-to-zero level (NRZ-L) encoding. In NRZ-L (level), 0 is represented by frequency ω 1 and 1 is represented by frequency ω 2 .

[0417] [Data Rate and Encoding Type]

[0418] The physical layer supports 8 types, as shown in Table 38.

[0419] The preamble and header are encoded using TYPE 0, but the payload is encoded using an appropriate data rate and encoding. The data rate and encoding type of the payload are specified in the data rate and encoding field of the header.

[0420] [Modulation]

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

[0422] Figure 24 is a diagram showing amplitude shift keying (ASK) modulation. As Figure 24 shown, the encoded serial input data is converted to a number representing one of two ASK constellation points. (ω c represents the carrier frequency of CFAN)

[0423] Figure 25 is a diagram of GFSK modulation. As Figure 25 shown, the encoded serial input data is converted to a number representing one of two GFSK constellation points. (ω 1 and ω 2 represent the modulation frequency of CFAN.)

[0424] [Encoding and Modulation Process]

[0425] Figure 26 is a diagram of the encoding and modulation process of the preamble. The preamble sequence is encoded using TYPE 0.

[0426] Figure 27 is a diagram of the encoding and modulation process of the header. As Figure 27 shown, the header is formatted by adding the data rate and encoding, the payload data length, five 0s, and the HCS value. The resulting value combination is encoded using TYPE 0 and then modulated by GFSK or ASK.

[0427] Figure 28 is a diagram of the encoding and modulation process of the payload. As Figure 28 shown, the payload is formatted by appending data and the FCS value. The FCS value is a value calculated for the data. The resulting combination is encoded using TYPE 1 and then modulated by GFSK or ASK.

[0428] Media interface

[0429] (1) Frequency

[0430] The center frequency of CFAN is ω with a maximum allowable error of ±20 ppm for GFSK 1 and ω 2 or ω with a maximum allowable deviation of ±20 ppm for ASK c .

[0431] (2) Signal Waveform

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

[0433] Figure 29 is a diagram of the GFSK modulation signal, Figure 30 is a diagram of the ASK modulation signal. As Figure 29 and Figure 30 shown, the transmitted signal is modulated by GFSK and ASK according to the envelope defined in this specification. Table 40 is an example of a table of envelope parameters for GFSK.

[0434] [Table 40]

[0435] Parameter Symbol Minimum value Maximum value Positive variation <![CDATA[M h > 0 Negative variation <![CDATA[M I > 0 Rise time <![CDATA[t r > 0 Fall time <![CDATA[t f > 0

[0436] Network design (CFAN implementation example)

[0437] Several examples of the CFAN implementation according to the present invention are given.

[0438] The physical structure of CFAN will be described. CFAN can be implemented in various designs based on a structure having two conductive materials and a dielectric material between the conductors. For example, as Figure 31 shown, an e-textile can be designed to have two conductive fabric layers separated by a dielectric layer. When one conductive fabric layer is Vcc and the other is ground, CFAN can be implemented. Thus, according to this layer design, power and data can be transmitted through the physical structure. In Figure 31 , ① represents Vcc, ② represents ground, ③ represents the dielectric, and ④ represents the e-textile.

[0439] As another example, a CFAN capable of transmitting power and data can be designed based on a linear cable. As Figure 32 shown, a flexible coaxial cable can have multiple layers consisting of an inner and an outer conductive layer and a dielectric material layer therebetween. The design choices of the coaxial cable affect size, data transmission, power attenuation, strength, flexibility, and cost. In Figure 32 , ① represents Vcc, ② represents ground, ③ represents the dielectric, and ④ represents the coaxial cable.

[0440] In addition, CFAN can be designed using non-conductive materials (insulating materials) and conductive materials arranged in parallel in two regions. These two regions can be configured to be parallel to each other. For the design of CFAN included in clothes as Figure 33 shown, a conductive fabric can be used as the conductive material, while ordinary fabric can be used as the insulating material. In Figure 33 , ① represents Vcc, ② represents ground, ③ represents ordinary optical fiber, and ④ represents the clothes.

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

[0442] 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. Multiple sub-wired network devices 200 may be included in the network system 10.

[0443] The main wired network device 100 or the sub-wired network device 200 may include a CFAN. Obviously, the main wired network device 100 or the sub-wired network device 200 may include a CFAN.

[0444] The main wired network device 100 and the sub-wired network device 200 may communicate with each other using at least one of wired communication and wireless communication means.

[0445] The main wired network device 100 and the sub-wired network device 200 may be respectively included in different wearable devices. For example, the main wired network device 100 may be included in an upper garment, while the sub-wired network device 200 may be included in lower garments. In this specification, a wearable device refers to all devices that can be carried by utilizing a user's body or clothing, such as smart watches, smart glasses, head-mounted displays (HMDs), touchscreens, eye trackers, devices for recognizing a user's posture or movement, auxiliary batteries, and devices that can be worn in the form of clothing.

[0446] Although not shown in the figure, the main wired network device 100 may further include a power supply device. The main wired network device 100 may wirelessly transmit power to the sub-wired network device 200.

[0447] Although not shown in the figure, the sub-wired network device 200 may further include a capacitor having electrodes using a conductive fabric layer. The sub-wired network device 200 may charge the capacitor with the power provided from the main wired network device 100. The sub-wired network device 200 may use the power charged in the capacitor to transmit data collected from the outside or generated by itself to the main wired network device 100.

[0448] The capacitor included in the sub-wired network device 200 may include two separated conductive fabric layers as electrodes and a dielectric layer disposed between the two conductive fabrics.

[0449] The main wired network device 100 includes a first main node 110, a first slave node 120, and a repeater node 130. There may be multiple first slave nodes 120 or repeater nodes 130.

[0450] The sub-wired network device 200 includes a second main node 210 and a second slave node 220. There may be multiple second slave nodes 220.

[0451] When the main wired network device 100 includes a conductive fabric-based network, the first master node 110 sends data to the first slave node 120 and the repeater node 130 through the conductive fabric layer and receives data from the first slave node 120 and the repeater node 130. The first slave node 120 can be a sensor capable of recognizing a user's bio-signal, posture, or movement, collect sensor data, and transmit the collected sensor data to the first master node 110 through the conductive fabric layer.

[0452] When the sub-wired network device 200 includes a conductive fabric-based network, the second master node 210 sends data to the second slave node 220 through the conductive fabric layer and receives data from the second slave node 220. The second slave node 220 can be a sensor capable of recognizing a user's bio-signal, posture, or movement, collect sensor data, and transmit the collected sensor data to the second master node 210 through the conductive fabric layer.

[0453] The repeater node 130 wirelessly transmits power to the second master node 210, and wirelessly sends data to the second master node 210 and wirelessly receives data from the second master node 210. There is no limitation on the wireless communication method that can be used for the main wired network device 100 and the sub-wired network device 200. For example, the wireless communication method can be one or a combination of Bluetooth Low Energy (BLE), Near Field Communication (NFC), Radio Frequency Identification (RFID), Wi-Fi, beacon, Zigbee communication, and Ultra-Wideband (UWB) communication. At the same time, there is no limitation on the method for the main wired network device 100 to wirelessly transmit power to the sub-wired network device 200. For example, the main wired network device 100 can use the magnetic induction method or the magnetic resonance method to wirelessly transmit power to the sub-wired network device 200.

[0454] When the second slave node 220 sends sensor data to the second master node 210, the second master node 210 can wirelessly send the sensor data to the repeater node 130. When the second master node 210 sends data to the repeater node 130, the repeater node 130 can stop transmitting power to the second master node 210 to prevent interference during data transmission.

[0455] The data sent and received between the repeater node 130 and the second master node 210 can include the identifier of the main wired network device 100, the identifier of the sub-wired network device 200, the identifier of the node sending the data (the node ID that becomes the source address), and the identifier of the node receiving the data (the node ID that becomes the destination address). For example, the node ID that becomes the source address can be the identifier of the sensor included in the sub-wired network device 200, and the node ID that becomes the destination address can be the identifier of the storage device 1040 included in the main wired network device 100.

[0456] When the main wired network device 100 includes a power supply device, the first main node 110 can transmit the power supplied from the power supply device to the repeater node 130 through the conductive fabric layer. The repeater node 130 can wirelessly transmit the power to the second main node 210.

[0457] Although not shown in the figures, the sub-wired network device 200 may include a capacitor having electrodes using a conductive fabric layer. In this case, the second main node 210 can charge the capacitor with the power supplied from the repeater node 130. In addition, the second main node 210 can use the power charged in the capacitor to send the data collected or generated by the sub-wired network device 200 to the repeater node 130.

[0458] The capacitor included in the sub-wired network device 200 may include two separate conductive fabric layers as electrodes and a dielectric layer disposed between the two conductive fabrics.

[0459] Even if the description is omitted during the description Figure 34 of the embodiments, Figures 1 to 33 the description can also be applied to Figure 34 the description. In addition, Figure 34 the description can be applied to Figures 1 to 33 the description.

[0460] Figure 35 is a block diagram showing a computer system for implementing a method according to an embodiment of the present invention.

[0461] Referring to Figure 35 FIG., the computer system 1000 may include at least one of a processor 1010, a memory 1030, an input interface device 1050, an output interface device 1060, and a storage device 1040 that communicate through 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 an embodiment of the present disclosure, the memory may be located inside or outside the processing unit, and the memory may be connected to the processing unit in various known ways. The memory may be various types of volatile or non-volatile storage media, and the memory may include, for example, ROM or RAM.

[0462] Accordingly, embodiments of the present invention can be implemented as a computer-implemented method or as a non-transitory computer-readable medium storing computer-executable instructions. In one embodiment, when executed by a processing unit, the computer-readable instructions can perform a method according to at least one aspect of the present disclosure.

[0463] The communication device 1020 can send or receive wired or wireless signals.

[0464] In addition, the method according to an embodiment of the present invention can be implemented in the form of program instructions, which can be executed by various computer devices and can be recorded on a computer-readable recording medium.

[0465] The computer-readable recording medium can include program commands, data files, data structures, etc. alone or in combination. The program instructions recorded on the computer-readable recording medium can be configured by being specifically designed for embodiments of the present invention or can be used as known to those skilled in the art of computer software. The computer-readable recording medium can include a hardware device configured to store and execute program instructions. Examples of the computer-readable recording medium can include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as compact disc read-only memory (CD-ROM) or digital versatile disc (DVD), magneto-optical media such as floppy disks, ROM, RAM, flash memory, etc. Examples of program instructions can include high-level language codes that can be executed by a computer using an interpreter, etc., and machine language codes written by a compiler.

[0466] Although the exemplary embodiments of the present invention have been disclosed above, those skilled in the art can understand that various modifications and changes can be made to the present invention without departing from the scope and spirit of the present invention as described in the appended claims.

Claims

1. A network system, the network system comprises: a main wired network device; and a sub - wired network device, wherein, 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 network system according to claim 1, wherein, the main wired network device further includes a power supply device, and the main wired network device wirelessly transmits power to the sub - wired network device.

4. The network system according to claim 3, wherein, the sub - wired network device further includes a capacitor having electrodes using a conductive fabric layer, and the sub - wired network device charges the capacitor with the power provided by the main wired network device and uses the power charged in the capacitor to send data to the main wired network device.

5. The network system according to claim 4, wherein, the capacitor uses two separate conductive fabric layers as electrodes and includes a dielectric layer interposed between the two conductive fabric layers.

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

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

8. The network system according to claim 6, wherein, the data sent and received between the repeater node and the second master node includes: the identifier of the main wired network device; the identifier of the sub - wired network device; the identifier of the node sending the data; and the identifier of the node receiving the data.

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

10. The network system according to claim 6, wherein, the main wired network device further includes a power supply device, the sub - wired network device further includes a capacitor having electrodes using a conductive fabric layer, the first master node transmits the power provided by the power supply device to the repeater node through a conductive fabric layer, and The second master node charges the capacitor with the power supplied from the repeater node, and uses the power stored in the capacitor to send the data generated by the sub-wired network device to the repeater node.

11. The network system according to claim 10, wherein, the capacitor uses two separate conductive fabric layers as electrodes, and includes a dielectric layer interposed between the two conductive fabric layers.

12. The network system according to claim 10, wherein, when the second master node sends data to the repeater node, the repeater node does not transmit power to the second master node.

13. The network system according to claim 1, wherein, either or both of the main wired network device and the sub-wired network device are devices including a conductive fabric area network.

14. A method for establishing an association between wired network devices, the method comprising the steps of: wirelessly sending an association request message from a main wired network device to a sub-wired network device; sending an association response message from the sub-wired network device to the main wired network device; and sending an association confirmation message from the main wired network device to the sub-wired network device.

15. The method according to claim 14, wherein, the association confirmation message includes 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.

16. The method according to claim 14, wherein, the sending of the association request message includes: sending the association request message from a first master node included in the main wired network device to a second master node of the sub-wired network device through a repeater node of the main wired network device; and sending the association request message from the second master node to a slave node of the sub-wired network device.

17. The method according to claim 16, wherein, the step of sending the association response message includes: sending an association response message from the slave node to the second master node; sending the association response message from the second master node to the repeater node; and sending the association response message from the repeater node to the first master node.

18. The method according to claim 16, wherein, the step of sending the association confirmation message includes: sending the association confirmation message from the first master node to the second master node through the repeater node; and sending the association confirmation message from the second master node to the slave node, and the association confirmation message includes a node identifier assigned by the first master node to the slave node.

Images