KR20230106314A - Method of configuring sensor network for monitoring a patient with sensor nodes - Google Patents

Abstract

The present invention relates to a method for constructing a patient monitoring sensor network that facilitates the addition, deletion, and change of sensor nodes, and more particularly, in constructing, maintaining, and repairing a wireless sensor network for monitoring patients in hospitals, etc. Easy to add, delete, and change sensor nodes that prevent confusion with surrounding sensor networks while registering, deleting, or changing sensor nodes more easily than centralized or server-based methods of configuring, registering, and deleting sensor node information It relates to a method for configuring a patient monitoring sensor network to do so.
According to the present invention, by assigning a unique network ID according to the unique number of the monitor or portable receiver installed in the protection facility, confusion with other networks can be avoided, a large number of small groups can be formed in an adjacent area, and the installation location Since information and group information are stored in the sensor node, it is easy to add, delete, and change sensor nodes, so it is very convenient to operate compared to existing systems when used in situations where patients move and change frequently, such as in hospitals. .

Description

A method for configuring a patient monitoring sensor network that facilitates adding, deleting, and changing sensor nodes {METHOD OF CONFIGURING SENSOR NETWORK FOR MONITORING A PATIENT WITH SENSOR NODES}

The present invention relates to a method for constructing a patient monitoring sensor network that facilitates the addition, deletion, and change of sensor nodes, and more particularly, in constructing, maintaining, and repairing a wireless sensor network for monitoring patients in hospitals, etc. Easy to add, delete, and change sensor nodes that prevent confusion with surrounding sensor networks while registering, deleting, or changing sensor nodes more easily than centralized or server-based methods of configuring, registering, and deleting sensor node information It relates to a method for configuring a patient monitoring sensor network to do so.

Sensor networks are currently used for various purposes in various fields, such as fire detection in buildings, observation of livestock biometric information, and hospital patient monitoring. Such a sensor network is implemented by using a public network or a private network using a separate AP (Access Pointer) depending on the purpose of use. In particular, in hospitals, monitoring for multiple patients to prevent falls and loitering For this purpose, installation and operation using a private wireless sensor network system is common. In this case, due to the nature of the hospital, new sensor nodes are frequently added, deleted, or changed according to the hospitalization and discharge of patients and the movement of hospital rooms. In addition, maintenance work such as deleting a failed sensor node occurs frequently, so convenience of maintenance is an essential element.

1 is a conceptual diagram showing the configuration of a patient monitoring sensor network according to the prior art, FIG. 2 is a block diagram showing the connection relationship between components included in the sensor network of FIG. 1, and FIG. 3 is a diagram showing components of a portable receiver. Block diagram, Figure 4 is a block diagram showing the components of the sensor node.

A patient monitoring sensor network system is used in hospitals to monitor patients at risk of accidents due to falls or wandering. 1 is a configuration diagram of a patient monitoring system, showing a reception monitor 110, a portable receiver 120, and a sensor node 130.

The sensor node 130 is installed above or below the bed to detect a situation in which the patient gets up from the bed or comes down from the bed and transmits the signal to the portable receiver 120 or the reception monitor 110 to inform the caregiver or nurse. do.

The portable receiver 120 is a device that can be carried by a caregiver or a nurse and serves to display contents transmitted from the sensor node 130 .

The reception monitor 110 is a device installed on a desk or wall to display the contents transmitted from the sensor node 130 as an image. This patient monitoring sensor system enables early recognition and quick action when a patient at risk of falling suddenly tries to move.

2 shows a patient monitoring sensor network system from a network perspective. As a method of configuring a network used for patient monitoring, an N-to-N structure using wireless is common. That is, one or more sensor nodes 130 are configured to be connected to one or more receiving monitors 110 and one or more portable receivers 120.

Each sensor node 130 transmits sensor information (ward number and bed number, etc.) to all receiving monitors 110 and portable receivers 120 that are already registered and capable of receiving, and all receiving monitors that have received the sensor information ( 110) and the portable receiver 120 display the received information to the user.

As can be seen in FIG. 2 , the sensor node 130 is registered with the reception monitor 110 and the portable receiver 120 and can transmit sensor information to the reception monitor 110 and the portable receiver 120 .

A method of registering the sensor node 130 to the reception monitor 110 and the portable receiver 120 according to a conventional method in the sensor network configured as described above will be described.

First, in order to register the sensor node 130 with the portable receiver 120, the sensor node 130 and the portable receiver 120 are set to a registration mode. In the registration mode, the portable receiver 120 is used to input installation information such as the number of the hospital room where the sensor node 130 is installed and the number of the bed, and transmits the unique number of the sensor node 130 through wireless communication to detect the inside of the portable receiver. It is stored with installation information in memory.

Through this process, the portable receiver 120 can distinguish the registered sensor node 130 from unregistered sensor nodes. That is, data transmitted from unregistered sensor nodes 130 may be ignored and only data transmitted from registered sensor nodes 130 may be displayed.

3 and 4 show internal structures of the portable receiver 120 and the sensor node 130, respectively. Although the configurations of the portable receiver 120 and the sensor node 130 are different, the configurations for signal processing, wireless communication network connection, and program and data storage are the same. separate and explain.

The information of the registered sensor node 130 is stored in the first non-volatile memory 124 rather than in the first data memory 123, which is a volatile memory, because it must be memorized even if the power of the portable receiver 120 is cut off. . The information of the sensor node 130 stored in the first non-volatile memory 124 will be maintained until an operation such as deleting the information of the portable receiver 120 is performed.

Next, in order to register the sensor node 130 in the reception monitor 110, the same method as the registration in the portable receiver 120 should be repeated, and the information of the registered sensor node 130 is provided in the reception monitor 110. stored in non-volatile memory.

If the installation information (room number and bed number) of the sensor node 130 registered in the receiving monitor 110 and the portable receiver 120 is changed, all registered devices (receiving monitor, portable receiver). If the sensor node 130 is unusable due to a failure or the like, it must be deleted as a separate operation from all registered devices.

When data is not deleted, a part of the data storage area of the first nonvolatile memory 124 and the second nonvolatile memory 134, which are nonvolatile memory devices, is continuously occupied. Since non-volatile memory has a limited capacity, memory capacity problems may occur if the deleted sensor node information is not deleted. In addition, if there is a lot of stored sensor node information, it takes a long time to search the non-volatile memory to determine data received from normally registered sensor nodes.

Problems that may appear in the conventional method of storing sensor node information and installation information in a non-volatile memory of a portable receiver or reception monitor through a registration process are as follows.

1) A storage device composed of a non-volatile memory is a device with a limitation in its size, and when storing information on a large number of sensor nodes, it has a limitation according to the size of the memory. In addition, when receiving sensor information from a sensor node to determine whether a reception monitor or a portable receiver is a normal sensor node, a non-volatile memory device search is required, and a large number of sensor nodes are registered or unused sensor nodes. If the information remains without being erased, it puts a burden on the retrieval.

2) If a sensor node that has already been installed and stored is lost or malfunctions, the memory will continue to be occupied unnecessarily unless the registration information of the sensor node is deleted from the memory in the reception monitor or portable receiver.

3) If you want to use additional receiving monitors or portable receivers as the size of the facility expands, all new receiving monitors or portable receivers that want to copy all sensor node information registered in the existing device or add all sensor nodes in use must register in

4) If you want to add a new sensor node in a situation where multiple receiving monitors or portable receivers are used, you must add a sensor node to each receiving monitor or portable receiver.

5) Problems #3 and #4 also occur when information such as the installation location of the sensor node is changed. That is, when a change in a hospital room or a change in hospitalization or discharge of a patient occurs, the changed information must be registered in all receiving monitors and portable receivers being used.

KR 10-2035665 B1

In order to solve the above problems, the present invention easily configures an independent network in constructing a sensor network for patient monitoring such as detection of a patient's fall and wandering in a patient protection facility such as a hospital or nursing home, and devices installed around the It is an object of the present invention to provide a method for configuring a patient monitoring sensor network that facilitates addition, deletion, and change of sensor nodes, which prevents confusion with and facilitates maintenance.

In addition, the storage of the installation location information and registration information of the sensor node is transferred to the sensor node, a unique ID is given to each sensor network, and all communication within the sensor network is encrypted using this unique ID, and the header of the transmission packet It is an object of the present invention to provide a method for configuring a patient monitoring sensor network that facilitates adding, deleting, and changing sensor nodes that can easily distinguish unregistered sensor information transmitted from other sensor networks.

In addition, another object of the present invention is to provide a method for configuring a patient monitoring sensor network that groups sensor nodes registered in this process and makes it easy to add, delete, and change sensor nodes so that each group can operate separately.

In addition, in order to distinguish data transmitted from normally registered sensor nodes, network ID and encryption method using network ID are used. An object of the present invention is to provide a method for configuring a patient monitoring sensor network that facilitates adding, deleting, and changing sensor nodes without the need to store and retrieve sensor node information in a non-volatile memory device.

In addition, in order to simplify sensor node changes (change of installation location, addition and deletion), sensor node installation information is transmitted from a portable receiver or reception monitor to the sensor node at the time of registration and stored, and the sensor node is assigned By saving your own installation information and transmitting it when sensor information is transmitted, there is no need to store the installation information of the sensor node in the portable receiver and receiving monitor, and it is possible to change the installation information simply by re-entering the installation information in the sensor node. An object of the present invention is to provide a method for configuring a patient monitoring sensor network that facilitates adding, deleting, and changing sensor nodes.

The present invention, devised to solve the above problems, is a method of configuring a sensor network by registering one or more sensor nodes 130 with one or more reception monitors 110 or one or more portable receivers 120, wherein the portable receiver ( 120) a first step of generating a network ID; a second step of inputting, into the portable receiver 120, sensor node installation information including information on a place where the sensor node 130 to be registered is to be installed; a third step in which the sensor node 130 transmits a registration request packet to the portable receiver 120; a fourth step of decrypting the registration request packet by the portable receiver 120 having received the registration request packet using an encryption key for registration request; a fifth step of transmitting, by the portable receiver 120, the network ID and sensor node installation information to the sensor node 130 when the registration request packet is verified as a legitimate registration request; The sensor node 130 stores the network ID and the sensor node installation information transmitted from the portable receiver 120 in the second non-volatile memory 134, and transmits a confirmation packet for confirming reception to the portable receiver ( 120) in the sixth step; A seventh step of the sensor node 130 transmitting a sensor information transmission packet including the sensor node installation information to the portable receiver 120;

In the second step, the portable receiver 120 stores the sensor node installation information in the first data memory 123 as a temporary memory.

The network ID generated in the first step is a unique ID that distinguishes the portable receiver 120 from other networks configured around it, and is a random value generated by a random function using the unique number of the portable receiver 120. It is characterized in that it is created by adding.

The sensor information transmission packet includes a 1-byte group ID, and devices included in the sensor network are set to transmit/receive data between devices set to the same group ID.

When the group ID is 0, data can be transmitted to all devices and data can be received from all devices.

According to the present invention, by assigning a unique network ID according to the unique number of the monitor or portable receiver installed in the protection facility, confusion with other networks can be avoided, a large number of small groups can be formed in an adjacent area, and the installation location Since information and group information are stored in the sensor node, it is easy to add, delete, and change sensor nodes, so it is very convenient to operate compared to existing systems when used in situations where patients move and change frequently, such as in hospitals. .

In addition, in order to separate information transmitted from other nearby networks, such as unregistered sensor nodes, without scanning the unique number stored inside the monitor or portable receiver, the network ID or packet encryption method is used to separate the information from unregistered sensor nodes. The transmitted data can be ignored, and the group ID information set at the time of sensor node registration has the effect of subdividing each sensor node into groups for operation.

1 is a conceptual diagram showing the configuration of a patient monitoring sensor network according to the prior art.
2 is a block diagram showing a connection relationship between components included in the sensor network of FIG. 1;
3 is a block diagram showing components of a portable receiver;
4 is a block diagram showing the components of a sensor node;
5 is a flowchart illustrating a process of registering settings of sensor nodes included in a sensor network according to an embodiment of the present invention.
6 is a block diagram showing the structure of a registration request packet;
7 is a block diagram showing the structure of a registration request response packet;
Fig. 8 is a block diagram showing the structure of a sensor information transmission packet;
9 is a block diagram showing how sensor nodes are connected according to group IDs;

Hereinafter, a "method of configuring a patient monitoring sensor network that facilitates adding, deleting, and changing sensor nodes" according to an embodiment of the present invention will be described with reference to the drawings.

5 is a flowchart illustrating a process of registering settings of sensor nodes included in a sensor network according to an embodiment of the present invention, FIG. 6 is a block diagram showing the structure of a registration request packet, and FIG. 7 is a structure of a registration request response packet. 8 is a block diagram showing the structure of a sensor information transmission packet, and FIG. 9 is a block diagram showing how sensor nodes are connected according to group IDs.

5 shows the configuration of the new sensor network 100 to which the present invention is applied, that is, the process of registering the sensor node 130 to the portable receiver 120 for the first time in order to use the sensor node 130 and the portable receiver 120. explain The reception monitor 110, the portable receiver 120, and the sensor node 130 of the present invention may be one or more.

In the present invention, the sensor node 130 generates and transmits information on the patient's behavioral characteristics, and the reception monitor 110 and the portable receiver 120 process, store, and display the information transmitted from the sensor node 130. . Reflecting this, the reception monitor 110 and the portable receiver 120 may be collectively referred to as a "receiver". In the detailed description of the present invention, the structure and functions of the portable receiver 120 are mainly described, but these structures and functions can be equally applied to the reception monitor 110.

First, to configure an independent network, a network ID is generated by adding a random value generated by a random function while using the unique number of the portable receiver 120 (S102).

This network ID is a unique ID that distinguishes it from other networks that may be configured around it. This network ID is used to encrypt all communications after registration is completed or to determine the legitimacy of the registered sensor node 130 .

Next, the user inputs and sets the location where the sensor node 130 will be installed, that is, hospital room information and bed information (S104). This sensor node installation information is stored in the first data memory, which is a temporary memory of the portable receiver 120 123, and the portable receiver 120 waits for a registration request from the sensor node 130 to transmit this information to the sensor node 130.

Now, the user transmits the registration request from the sensor node 130 to the portable receiver 120 (S106). The user manipulates a button or switch (not shown) provided on the sensor node 130 to monitor the reception monitor installed nearby. A registration request may be made to (110) or the portable receiver (120).

In this case, the sensor node 130 transmits a registration request packet after encrypting only its own ID using an encryption key for registration request.

6 to 8 show types and configurations of packets transmitted and received between the portable receiver 120 and the sensor node 130, which will be described later.

The portable receiver 120 decrypts the received registration request packet using its own registration request encryption key in order to verify the legitimacy of the received registration request (S108). Depending on the case, transmission from other networks around In order to ignore the registered request, the strength of the received signal may be measured and only a signal having a certain strength or higher may be determined as a valid request.

If the received registration request packet is verified as a legitimate registration request, the portable receiver 120 transmits the network ID and sensor node installation information generated in the first step to the sensor node 130 (S110, S112).

The sensor node 130 stores the network ID and sensor node installation information transmitted from the portable receiver 120 in the second non-volatile memory 134 (S114) and sends a confirmation packet to confirm reception to the portable receiver 120. ). (S116)

The portable receiver 120 completes the network configuration and registration of the sensor node 130 (S118). The important point here is that the ID and installation information of the sensor node 130 are stored in the non-volatile memory device of the portable receiver 120. Because it is not stored, it does not use the resources of the non-volatile memory device. In addition, security can be enhanced by encrypting all data between the portable receiver 120 and the sensor node 130 using a registration-only encryption key before transmission.

When network configuration and registration are completed, the sensor node 130 may transmit sensor information to the portable receiver 120 . The sensor node 130 transmits the sensor information transmission packet including the installation information to the portable receiver 120 (S120). In this case, the key used for encryption is not the encryption key used exclusively for registration, and the ID of the sensor network is encrypted using The information transmitted by the sensor node 130 is the ID of the sensor node 130, installation information (room and bed information, etc.) stored at the time of registration, and may further include a group ID for forming a small group within the same network. .

The structure of a packet used in the present invention is shown in FIGS. 6 to 8.

6 shows the structure of a registration request packet, FIG. 7 shows the structure of a registration request response packet, and FIG. 8 shows the structure of a sensor information transmission packet.

The registration request packet is a packet transmitted by the sensor node 130 and received by the portable receiver 120 . The first 1 byte indicates the type of packet being transmitted. In this case, the packet type is "registration request packet". Second, a 4-byte 'network ID for registration' is recorded. This ID is used only when requesting and responding to registration, and can be set separately for each set at the time of product shipment. The third 1-byte 'sensor node type' is used to inform various types of sensor nodes for each purpose, such as sensor pads for beds, sensor mats for floors, and sensor mats for entrances. Fourthly, a 3-byte 'sensor node ID' for identifying the sensor node 130 requesting registration is recorded, and a 1-byte 'checksum' is recorded fifthly to check errors for all of them. It is preferable that the entire packet is encrypted and transmitted through a separate registration-only encryption key.

Upon receiving the normal registration request packet from the sensor node 130 in step S106, the portable receiver 120 transmits to the sensor node 130 a packet including installation information previously set by the user, group information, and a newly created network ID. Respond to registration requests. The type of this packet is a "registration request response packet". In the case of the registration request response packet, the network ID also uses 'network ID for registration'.

In the registration request response packet, the same information included in the registration request packet, such as 'packet type, registration network ID, sensor node type, sensor node ID', is recorded.

The fifth recorded 4-byte 'network ID' is a value generated by combining the ID of the portable receiver 120 and a random value at the time of preparing for registration of the sensor node 130, so as to prevent confusion with neighboring networks. This is the selected unique ID. The sixth, 1-byte 'group ID' is information used when it is necessary to distinguish a small group between devices using the same network ID, and can be set by the user during the registration process.

And the seventh 2-byte 'installation information' is information input by the user in the process of preparing for registration, and includes, for example, information such as a hospital room number and a bed number. It is possible to check the place where the sensor node 130 is installed through the installation information.

In the last eighth, a 1-byte-long 'checksum' for error checking is recorded as before.

The packet shown in FIG. 8 is a packet for the sensor node 130 to transmit sensor information to the portable receiver 120 after registration of the sensor node 130 is completed. This packet is transmitted from the sensor node 130 to the portable receiver 120 in step S120, and the packet type becomes "sensor information transmission packet".

The 'network ID' recorded after the first 1-byte 'packet type' is a unique network ID received from the portable receiver 120 in the registration process. The third and fourth 'sensor node type' and 'sensor node ID' are information of the sensor node itself, and 'sequence number' of 1 byte represents the number of times the sensor node 130 has transmitted sensor node information. 'Group ID' and 'installation information' are values set by the user in the registration process and received through the portable receiver 120 . At the end, a 'checksum' of 1 byte is also recorded.

This packet can be encrypted with the network ID received in the registration process, and the portable receiver 120 also decrypts it using the same encryption key.

By using such a sensor network configuration method, the problems of the existing network configuration method are solved.

That is, problems caused by data accumulation in the non-volatile memory can be solved, because the ID of the sensor node 130, installation information, group information, and the like are not stored in the non-volatile memory of the portable receiver 120. In addition, since information related to the sensor node 130 is not permanently stored in the portable receiver 120, information on a broken or unused sensor node does not need to be removed from the portable receiver 120. A failed sensor node can be discarded immediately without any additional deletion measures.

In the existing method, there is a problem in that the information of all sensor nodes that have been previously registered and used must be copied to the receiver to be newly added or all sensor nodes must be registered to the receiver to be newly added one by one. The method proposed in the present invention does not store sensor node information in the receiver, but generates a network ID at the time of configuring the network. Also, a packet normally encrypted using this network ID or a packet with a normal network ID is regarded as a packet transmitted from a normally registered sensor node. Therefore, the newly added receiver only needs to encrypt and copy the network ID used from the existing receiver. Afterwards, all packets transmitted from the sensor node can be decoded using the copied network ID.

Also, a problem arises when trying to add a sensor node in a situation where multiple receivers are being used. In the conventional method, when a sensor node to be added is registered using one receiver that is already in use, the newly registered sensor node cannot be recognized by other receivers that are already in use. Since the method used in the present invention identifies the sensor node in the network using the network ID, registering a new sensor node using any one receiver (however, when the same network ID is used) is used to detect the network Since the ID is stored and used in the sensor node, it can be normally recognized and used by all existing receivers.

In addition, when the location or usage of the sensor node is changed, the installation information of the sensor node is changed. In the present invention, since the installation information is stored in the sensor node, when the information of the sensor node is changed, it can be solved only by re-registering using the receiver using the changed value.

The advantage of the prior art method, that is, the method of storing the information of the sensor node 130 in the non-volatile memory device of the reception monitor 110 and the portable receiver 120, is that each portable receiver 120 And it is very convenient to configure a small group for each receiving monitor 110. If all sensor nodes 130 are registered in a specific portable receiver 120, the portable receiver 120 can receive all packets transmitted from all registered sensor nodes 130. In addition, the portable receiver 120 in which only some sensor nodes 130 are registered can receive only packets transmitted from some of the registered sensor nodes 130 and cannot receive packets from unregistered sensor nodes 130. can't

This is a very effective method for registering and using small groups of various categories such as nurses in charge, disease names, and patient grades in an environment where a plurality of sensor nodes 130 are mixed and used. In the present invention, a technique for classifying small groups within a network may be implemented in another method.

A group setting method used in the present invention is shown in FIG. 9 .

In the present invention, a small group can be set on the same network using a group ID. Groups can be directly set by a user when registering a plurality of sensor nodes 130 using the reception monitor 110 and the portable receiver 120, and can be designated by classifying a hospital room and a person in charge through group setting.

9 shows a case in which three portable receivers and three sensor nodes are separated using group settings. A case in which the group ID is 0 is a state in which signals of all groups can be received, and can be regarded as a case in which group IDs do not need to be distinguished. Therefore, devices (receiving monitors, portable receivers, sensor nodes) whose group ID is set to 0 can receive data from all devices included in the same network. Also, a device with a group ID of 0 can transmit data regardless of the group ID of a device receiving data.

In FIG. 9, since the group ID of sensor node 1 is set to 0, data can be received from all portable receivers (portable receiver 1, portable receiver 2, and portable receiver 3).

Since sensor node 2 has its group ID set to 1, it can receive only the portable receiver 2 whose group ID is set to 1 and the portable receiver 1 whose group ID is set to 0.

Since the group ID of sensor node 3 is set to 2, portable receiver 1 with group ID set to 0 and portable receiver 3 with group ID set to 2 can receive data.

This function allows a nurse to be assigned to each ward or a head nurse to be used to monitor the situation of all wards.

In the present invention, when a network is classified, a network ID is used instead of a method using the sensor node 130 number, and a group ID is used instead of a sensor node 130 number when a group is classified.

Although the preferred embodiments of the present invention have been described with reference to the accompanying drawings, the technical configuration of the present invention described above is another specific form without changing the technical spirit or essential features of the present invention by those skilled in the art to which the present invention belongs. It will be understood that it can be implemented as. Therefore, the embodiments described above should be understood as illustrative and not limiting in all respects, and the scope of the present invention is indicated by the claims to be described later rather than the detailed description, and the meaning and scope of the claims and All changes or modified forms derived from the equivalent concept should be construed as being included in the scope of the present invention.

100: sensor network 110: receiving monitor
120: portable receiver 130: sensor node

Claims (5)

A method of configuring a sensor network by registering one or more sensor nodes (130) with one or more reception monitors (110) or one or more portable receivers (120),
a first step of generating a network ID by the portable receiver 120;
a second step of inputting, into the portable receiver 120, sensor node installation information including information on a place where the sensor node 130 to be registered is to be installed;
a third step in which the sensor node 130 transmits a registration request packet to the portable receiver 120;
a fourth step of decrypting the registration request packet by the portable receiver 120 having received the registration request packet using an encryption key for registration request;
a fifth step of transmitting, by the portable receiver 120, the network ID and sensor node installation information to the sensor node 130 when the registration request packet is verified as a legitimate registration request;
The sensor node 130 stores the network ID and the sensor node installation information transmitted from the portable receiver 120 in the second non-volatile memory 134, and transmits a confirmation packet for confirming reception to the portable receiver ( 120) in the sixth step;
A seventh step of the sensor node 130 transmitting a sensor information transmission packet including the sensor node installation information to the portable receiver 120; How to configure a monitoring sensor network. According to claim 1,
In the second step, the portable receiver 120 stores the sensor node installation information in the first data memory 123 as a temporary memory. How to configure a sensor network. According to claim 1,
The network ID generated in the first step is
The portable receiver 120 is a unique ID distinguished from other networks configured around it, and is generated by adding a random value generated by a random function while using the unique number of the portable receiver 120, the sensor A method for constructing a patient monitoring sensor network that facilitates adding, deleting, and changing nodes. According to claim 1,
The sensor information transmission packet includes a 1-byte group ID,
Devices included in the sensor network are set to transmit and receive data between devices set to the same group ID, characterized in that, a patient monitoring sensor network configuration method that facilitates adding, deleting, and changing sensor nodes. According to claim 4,
When the group ID is 0, data can be transmitted to all devices and data can be received from all devices, characterized in that the patient monitoring sensor network that facilitates the addition, deletion and change of sensor nodes How to configure.

Images