KR102327947B1 - Method for Push-based Data Broadcast Control in Information-Centric Internet of Things - Google Patents

Abstract

The present invention relates to a method of controlling the broadcasting of Push-based data in an information-oriented Internet of Things (IoT) environment, which enables control of a broadcasting storm of Push-based data in an Internet of Things (IoT) environment of information-centric networking (ICN).
The push-based data broadcasting control method according to the present invention is a push-based data broadcasting control method in an ICN-based IoT environment. When an emergency situation is detected by a sensor node installed in a building, emergency situation information is transmitted from the sensor node. generating a data packet including a warning type according to an emergency situation at the receiving producer node, and broadcasting the generated data packet; The other producer node receiving the broadcast data packet checks whether the building in which it is located is the same as the producer node that transmitted the data packet. It characterized in that it includes; the step of transmitting to the Consumer node that manages the corresponding building.

Description

{Method for Push-based Data Broadcast Control in Information-Centric Internet of Things}

The present invention relates to a method for controlling broadcasting of Push-based data, and in particular, an information-oriented Internet of Things (IoT) that enables control of a broadcasting storm of Push-based data in an Internet of Things (IoT) environment of information-centric networking (ICN). It relates to a method of controlling the broadcasting of Push-based data in the environment.

ICN (Information Centric Networking) is a communication based on information identifiers rather than communication based on the address of the communication target host. It is a pull-based communication model that retrieves content only when a consumer requests it.

These ICNs support pull-based network traffic, but in case of emergency, important data may need to be delivered immediately to consumers on the network without a request. In the ICN-based Internet of Things (IoT)) environment, some push-based traffic is supported, but most conventional methods notify a signal message or interest packet such as a beacon message and save the interest packet for a long time to transmit push-based data in the ICN environment. We are taking a way to make it possible.

However, in these cases, since the conventional ICN models broadcast data within the entire transmittable range, a broadcast storm phenomenon such as network congestion and overhead due to data flooding occurs. This has a direct impact on the network's delay, throughput and other resources. As a result, emergency data does not reach the target consumer in an appropriate time, and the Internet of Things network does not operate smoothly in emergency situations. There was a problem that didn't happen.

Republic of Korea Patent Publication No. 10-2016-0076445 (published on June 30, 2016)

The present invention has been proposed to solve the broadcast storm problem occurring in the conventional ICN-based IoT environment, and an object of the present invention is to limit push-based data flooding delivered to the consumer through the Naming Scheme in the ICN-based IoT environment. It is to provide a push-based data broadcast control method.

The push-based data broadcasting control method according to the present invention for achieving the above object is a push-based data broadcasting control method in an ICN-based IoT environment. When an emergency is detected by a sensor node installed in a building, the sensor generating a data packet including a warning type according to an emergency situation at a producer node receiving emergency situation information from the node, and broadcasting the generated data packet; The other producer node receiving the broadcast data packet checks whether the building in which it is located is the same as the producer node that transmitted the data packet. and sending it to the Consumer node that manages the building.

Here, the producer node receiving the emergency information from the sensor node generates a data packet including a warning type, but the name of the data packet is " Campus name or location (Campus)/Name of building (BuildingName)/Number of floors of building (FloorNumber)/Number of rooms in building (RoomNumber)/ID of sensor node (SendorID)/Content (payload(Alert))" It is desirable to be broadcast.

In addition, the name of each device including the Producer installed in the building is "Campus name or location (Campus) / Name of the building (BuildingName) / It is desirable to name in the form of the number of floors of the building (FloorNumber)/the number of the room in the building (RoomNumber)/the number of the device (DeviceNumber).

The producer receiving the broadcast data packet checks the "campus name or location (Capmus)/name of the building (BuildingName) to which the building belongs" through the name of the data packet, and confirms that the "building is By comparing "Campus name or location (Capmus)/Name of building (BuildingName)" to which they belong, the corresponding data packet is re-broadcasted if they are the same, and the corresponding data packet is discarded if they are not the same.

In addition, the data packet includes a Content Name field for registering a content name, a MetaInfo field for registering optional additional information related to content, a Content field for registering content content, and a Signature field for data authentication, wherein the MetaInfo field It is desirable to display the warning type (AlterType) according to the emergency situation.

On the other hand, the ush-based data broadcasting control method according to the present invention is a push-based data broadcasting control method in an ICN-based VANET environment. generating and broadcasting a data packet including RSU (Road Side Unit) information of the road on which the user is located; The other vehicle node receiving the broadcast data packet compares the RSU information according to the location of the vehicle node that transmitted the data packet with the RSU information according to its own location. and allowing the data packet to be delivered to the corresponding RSU.

The vehicle node in which the emergency situation occurs generates a data packet including RSU information, but the name of the data packet is "ID (VehicleID)/vehicle that can distinguish a vehicle" through a namespace design according to the hierarchical naming structure of ICN. RSU ID (RSUID)/vehicle direction/vehicle speed (Speed)/content (payload (accident))" that changes according to GPS is named in the format and is preferably broadcast.

In addition, the vehicle node receiving the broadcast data packet checks the "RSU ID (RSUID)" according to the GPS location of the vehicle broadcasting the data packet through the name of the data packet, and " RSU ID (RSUID)" is compared, and if they are identical, the corresponding data packet is re-broadcast, and if it is not the same, the corresponding data packet is discarded.

Due to the nature of broadcasting in a wireless network environment, if data packets are not controlled through an efficient mechanism, network bandwidth consumption may be high, and many resources may be utilized in the network. In particular, in the case of a push-based scenario, important data may not reach the target consumer in a timely manner. To solve this problem, the present invention proposes a naming scheme in which data packets are named in a specific area to control the data packets, instead of transmitting the data packets to all devices in the network. The naming scheme proposed in the present invention not only saves network resources but also has the effect of allowing important data to reach an appropriate consumer at an appropriate time.

1 is an example in which data flooding occurs in a conventional smart building;

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The present invention provides a push-based data broadcasting control method that limits push-based data flooding without using any signal message to activate push-based traffic in an ICN-based Internet of Things (ICN-IoT) environment. . In the present invention, as such a push-based data broadcasting control method, an efficient content namespace design, a device namespace design, and a naming scheme in which a part of the data packet format is modified are proposed.

In the Naming Scheme according to the present invention, the content namespace design and the device namespace design control data packet flooding to reduce network congestion. In addition, in order to display an alert type in preparation for various emergency situations, the existing data packet format of ICN was partially modified and strengthened.

The Naming Scheme proposed in the present invention efficiently controls the number of unnecessary data packets in the network through the design of the content namespace and the device namespace. Hereinafter, the Naming Scheme as above will be described assuming two situations, a smart building situation and a vehicle network situation.

[ Smart Building Scenario ]

First, the Naming Scheme according to the present invention will be described by applying it to a smart building situation. In the case of the smart building situation, problems occurring in the conventional smart building situation will be described first, and then the smart building situation according to the present invention will be described.

1 shows an example in which data flooding occurs in a conventional smart building.

The smart building situation shown in FIG. 1 shows a use case scenario of a smart campus, and the smart building consists of three buildings A, B, and C. Each building consists of three floors (Floor1, Floor2, Floor3), and each floor has several rooms. Also, in this use-case scenario, it is assumed that there are various types of sensor devices such as temperature, camera, fire, and smoke sensors in each room on every floor. All sensor nodes in each room are connected to one producer node, which collects data from all sensor nodes in each room and then delivers the collected data to consumers.

Each layer consists of a producer node and a wi-fi access point (AP). Each building has a Consumer node that controls and monitors the building involved. That is, when an abnormal situation such as a fire or an intruder occurs in a building, the Consumer node notifies the basic procedure of an emergency by lowering the delay.

Suppose an emergency occurs on the 3rd floor of building A. In this case, the producer node does not wait for the consumer's request and broadcasts data within the transmittable range. When data is broadcast, all devices within the transmission range also broadcast the data. 1 shows a process in which a producer on the third floor of building A broadcasts an emergency warning message. This emergency alert was received by all devices within transmission range, including Building B. When the device in Building B receives the data, it is rebroadcast within the transmission range, and eventually the data floods all the buildings in the campus.

Although the data is first given to the Consumer in Building A, the data arrives at every building on the campus. This data flooding process causes congestion and overhead in the network, which directly affects the network latency, throughput and other resources. As a result, emergency data may not reach the target consumer within an appropriate time.

Therefore, the data flooding phenomenon causes a serious problem in the IoT network, which prioritizes the delivery of appropriate information within an appropriate time. In the past, there was no case of dealing with such a problem through ICN namespace design, so in the present invention, the data flooding phenomenon was solved through direct ICN namespace design. Therefore, the present invention proposes to control data flooding as well as design a namespace for contents and devices.

To this end, the present invention proposes a naming scheme composed of a namespace design and device namespace design for controlling push-based data in an IoT environment, and an improved data packet format in which a part of an existing data packet is modified.

2 shows an enhanced data packet format according to an embodiment of the present invention, and the present invention proposes an improved data packet format in which the existing data packet format is modified.

As shown in Fig. 2, the ICN data packet includes a Content Name field for registering a content name, a MetaInfo field for registering optional additional information related to content, a Content field for registering content content, and a Signature field for data authentication. However, in the present invention, "AlertType" is added to indicate the alert type in the MetaInfo field of the data packet.

This is because in a smart campus situation there can be several types of alarms, such as smoke alarms, heat alarms, fire alarms, and intruder alarms. For example, an attempt or unauthorized entry into a building or room is detected, and such an alarm can be linked to a security surveillance camera, a lighting system, and a remote monitoring system of a security company. Also, as an example, when the temperature of a room rises above a certain threshold, a warning alarm should be sent to the building manager or person concerned.

As described above, in the present invention, an "AlertType" item is added to the MetaInfo field of the data packet to indicate the alarm type so that the Cunsumer can check it.

On the other hand, the data packet generated in that room is named with the name of the room where the risk occurred. That is, the data packet in the Naming Scheme proposed in the present invention is limited to a specific building of the smart campus, and the design method of the content namespace follows the hierarchical naming structure of ICN. A typical content namespace design is represented by the various components of a hierarchy, for example "/Campus/BuildingName/FloorNumber/RoomNumber/SensorId/payload".

where "Campus" is the name or location of the campus the building belongs to, "BuildingName" is the name of the building, "FloorNumber" is the number of floors, "RoomNumber" is the specific room number within the building, "sensorId" is the ID of the sensor, and "payload" contains the actual content.

In more detail, let us consider the smart campus scenario of Hongik University. For example, the namespace of Hongik University Building A is "Hong/BuildingA/Floor3/Room301/Id001/Alert". In this namespace, it means that an alarm was issued in Room 301, 3rd floor, Building A, Hongik University. This warning message, which actually means data, needs to be delivered to the relevant Consumer node in Building A (the manager responsible for building management) to take action. The Consumer receives a data packet that contains a name and other optional fields. The "MetaInfo" field of the data packet is utilized to indicate the alert type. Therefore, the consumer can easily get information about the type of alert received.

On the other hand, since the existing ICN is basically a pull-based model, some modifications are required to enable push-based data transmission in the ICN-based IoT environment. First, assuming that all devices in the building are approved in advance, all data packets are broadcast in push-based ICN communication. For example, when building A broadcasts a data packet, all devices within the transmittable range of building A (including buildings B and C) also receive the data packet. Therefore, all nearby buildings within range are broadcasting data packets which incur additional overhead on the network, so data packets may not reach the right consumer in a reasonable time. In order to control such a data packet broadcast storm, a namespace design for a device (device namespace design) is also required.

The hierarchical namespace design for these smart campus devices is as follows. For example, the name of the device on the 3rd floor of Building A is "/Hongik/BuildingA/Floor3/Room301/Device005". According to the device namespace in the example above, "Device 005" belongs to Room 301 on the 3rd floor of Hongik University Building A. Thus, when a data packet is broadcast from building A, it will be received by all devices within transmission range of building A.

When each device receives a data packet, each device checks the namespace of the received data packet and compares it with its own namespace. If the first and second namespace components of a data packet such as "/Hongik/BuildingA/" match up to the second component of the device's namespace (/Hongik/BuildingA), the data packet is processed and delivered to other nodes. . Through this process, the data packet is delivered through all intermediate nodes of building A from the 3rd to the 2nd floor, and when it finally reaches the Consumer node, appropriate actions can be taken accordingly. 3 shows a process in which a data packet is delivered to a consumer in such a smart building.

On the other hand, if the first and second components of the namespace of a data packet do not match up to the second component of the device's namespace (/Hongik/BuildingA), the data packet is not transmitted any more. For example, if a device located in building B receives a data packet, because its second component (/Hongink/BuildingB) does not match. The data packet is no longer delivered and is ignored.

In this way, the data flooding phenomenon is reduced through the content namespace design of the Naming Scheme according to the present invention, the device namespace design, and the improved data packet format so that the data packet including the alarm information can reach the consumer at an appropriate time. do.

[Vehicle Network Status]

Hereinafter, an example in which the Naming Scheme according to the present invention is applied to a vehicle network situation will be described.

Recently, to change the host-oriented model of VANET (Vehicular ad hoc network) from IP networking to name-based communication, ICN (Information Centric Network) was introduced to VANET. In ICN-based VANET, consumers follow a pull-based mechanism, where consumers send interest packets for content retrieval.

Meanwhile, recently, push-based ICN proposals have also been proposed in VANET. However, all these proposals incur an overhead in the network because they use additional messages such as beacons to send important data that should be delivered immediately. In other words, they tend to rely on beacon messages to help deliver data packets, which are accompanied by congestion when broadcasting. Although the size of the Beacon message is small, it still causes congestion in the network due to the broadcasting mechanism. Therefore, since the Beacon transmits control information, the Broadcasting Beacon in the VANET may cause problems such as a broadcasting storm and high bandwidth usage, and consequently the network becomes overloaded. Accordingly, the existing schema of ICN-based VANET controls the interest broadcast storm through hop limit and other additional control information that brings overhead to the network.

In contrast, in the present invention, an additional control message such as a beacon message is not used, and the location information is based on a global positioning system (GPS) location, and a vehicle obtains location information through GPS for data packet transmission. Vehicles only send data packets to predetermined consumers in this area, which can help reduce the number of data packets on the network.

In the present invention, a variable naming scheme is proposed for an ICN-based VANET that optimizes network utilization by efficiently reducing data packet flooding. In order to explain the Naming Scheme in the vehicle network situation, we will consider the emergency situation.

4 is a diagram illustrating a network situation for a vehicle in which a naming scheme is performed according to an embodiment of the present invention. 4 illustrates a situation in which a vehicle (node) broadcasts a data packet to all nearby vehicles when an accident occurs. In this case, all nearby vehicles deliver data packets to the corresponding Consumer, a Roadside Unit (RSU). will do It is assumed that each vehicle is equipped with GPS and knows the location information used by the car navigation system. The location of the vehicle can be obtained locally through GPS, and the location of each node is transmitted as a data packet immediately after the prefix name. The other fields remain the same as in the ICN data packet. Therefore, whenever the vehicle transmits a data packet, it first checks the current location from the local GPS, and then transmits such information with it.

The characteristic of the Naming Scheme proposed in the present invention can be called various Names. Since VANET is a fully mobile environment, using a "static/constant" naming scheme for a dynamic network may not work. In addition, in the proposed Naming Scheme, communication is vehicle-to-vehicle (V2V) communication, and vehicles are intermediate nodes that serve as relay nodes to transmit data to consumers. This intermediate node is the same as the case of the smart building situation described above, but in this case, all nodes are characterized by mobility.

In the present invention, ICN-based VANET namespace design follows the hierarchical naming structure of ICN composed of other properties separated by "/". A typical namespace design consisting of the various components of a hierarchy can be expressed as "/VehicleID/RSUID/Direction/Speed/payload".

Here, VehicleID is an ID that can distinguish a vehicle, RSU ID is a GSU ID that changes according to the vehicle GPS, Direction is the direction of the vehicle, Speed is the speed of the vehicle, and actual data is transmitted to the payload.

In the case of FIG. 4 , it is assumed that an accident has occurred near RSU2. This means that the vehicle in the accident is within the range of RSU2. Therefore, in this case, the producer (producer) immediately broadcasts the data in the transmission range without waiting for the consumer's request. Because VANNET is an ad-hoc environment, data will be broadcast in the transmission range, and every vehicle will broadcast data packets further.

In Fig. 4, when an accident vehicle (Producer) in the transmission range of RSU2 broadcasts an emergency alert, this emergency alert is received by all vehicles within the transmission range. On the other hand, since these vehicles are constantly moving, they will move to different RSU ranges and additionally broadcast data in the transmission range.

In this way every vehicle starts sending data packets that will be flooded in the network. Such data flooding causes congestion and overhead in the network, which is a very important problem because it can seriously affect network resources. As a result, urgent data may not reach the right consumer at the right time. This data flooding is one of the serious problems in VANETs where the delivery of important data is a priority.

Since there has not been a case in which this problem has been dealt with through ICN namespace design in the prior art, the present invention proposes to solve the data flooding phenomenon through a namespace design method for controlling ICN-based VANET push-based data. When the vehicle is moving, the name of the vehicle should also be changed variably according to the mobility. Therefore, the namespace of the present invention is variable, and the data name has a variable characteristic based on the GPS location of the vehicle.

For example, in FIG. 4 , it is assumed that an accident has occurred in the transmission range of RSU2, vehicle ID is 5, the vehicle is moving in the east direction, and the location of the vehicle is within the range of RSU2. The accident vehicle generates data packets and broadcasts them within the transmission range. At this time, the vehicle's namespace is expressed as "/VehicleID5/RSU2/East/X,Y/50Kmph/accident".

When a data packet is broadcast by a vehicle with ID 5, it is received by all vehicles within the transmission range of vehicle 5. When receiving a data packet, each vehicle first checks the namespace of the received data packet and compares it with its own namespace. In this case, the vehicle namespace may be configured as "/VehicleID/RSUID". In this namespace, it can be seen that the accident vehicle ID is 5, and this vehicle is moving in the same direction (east) as the range of RSU2.

If the second component of the data namespace (RSU2) matches the second component of the vehicle namespace (RSU2), the data packet is processed and broadcast through all intermediate nodes of RSU2. If the data packet namespace and vehicle namespace do not match, the data packet is discarded and no longer forwarded.

In addition, when receiving a data packet broadcast from a vehicle in an accident within the range of RSU2, and when the vehicle enters RSU3 outside the transmission range of RSU2, this vehicle and other vehicles also broadcast a data packet that causes a data broadcast storm and send In this case, when receiving a data packet, other vehicles in the RSU3 range will first compare their namespace with the received data packet namespace, the second element, such as the namespace (/VehicleID5/RSU2/) You can see that it was built by RSU2, not RSU3. Therefore, all vehicles in RSU3 will discard the data packet and no longer process or transmit the data packet. By controlling data packet flooding in the above manner, unnecessary re-broadcasting of data packets is not performed.

As described above, in the present invention, the data flooding phenomenon can be solved by preventing unnecessary data packet broadcasting through a naming scheme that provides a content namespace design, a device namespace design, and an improved data packet format.

The present invention is not limited to the above-described embodiments, and various modifications and variations can be made by those of ordinary skill in the art to which the present invention pertains within the scope of equivalents of the technical spirit of the present invention and the claims to be described below. Of course, this can be done.

Claims (8)

A method for controlling broadcasting of push-based data in an ICN-based IoT environment, comprising:
(a) When an emergency is detected by a sensor node installed in a building, a producer node that receives emergency information from the sensor node generates a data packet including a warning type according to the emergency situation, and broadcasts the generated data packet casting;
(b) The other producer node receiving the broadcast data packet checks whether the building where it is located is the same as the producer node that transmitted the data packet, and if it is the same building, rebroadcasts the data packet, including; allowing the data packet to be delivered to a Consumer node that manages the building;
The data packet includes a Content Name field for registering a content name, a MetaInfo field for registering optional additional information related to content, a Content field for registering content content, and a Signature field for data authentication. A method for controlling broadcasting of Push-based data, characterized in that an alert type (AlterType) according to the situation is displayed.
The method of claim 1,
The producer node receiving the emergency information from the sensor node generates a data packet including a warning type,
The name of the data packet is "Campus name or location to which the building belongs (Campus) / Name of the building (BuildingName) / Number of floors of the building (FloorNumber) / Room in the building" through the content namespace design following the hierarchical naming structure of ICN. Number (RoomNumber)/ID of sensor node (SendorID)/Content (payload(Alert))" The broadcasting control method of Push-based data, characterized in that it is named and broadcast.
3. The method of claim 2,
The name of each device including the producer installed in the building is
Through the device namespace design following the hierarchical naming structure of ICN, "Campus name or location to which the building belongs (Campus) / Name of the building (BuildingName) / Number of floors of the building (FloorNumber) / Number of rooms in the building (RoomNumber) / A method for controlling broadcasting of Push-based data, characterized in that it is named in the form of a device number (DeviceNumber).
4. The method of claim 3,
The producer receiving the broadcast data packet
Through the name of the data packet, check the “Campus name or location (Capmus)/Name of the building (BuildingName)” where the data packet is created, and check the “Campus name or location (Capmus)/building By comparing "Name (BuildingName)",
If the data packet is the same, the corresponding data packet is re-broadcast, and if the data packet is not the same, the corresponding data packet is discarded.
delete delete delete delete

Images