JP2017512392A - Dynamic mobile sensor network platform for ID-based communication - Google Patents

Abstract

The present invention relates to a dynamic mobile sensor network capable of communicating with various types of sensors having different protocols. The platform includes each mobile sensor and each mobile sensor gateway, where network protocols and application programs can be installed separately, changed, and updated. Users can install new applications on the built sensor network and use them in different network environments for new types of services.

Description

  The present invention relates to a method for mobile sensor network setup, and the present invention belongs to the technical field of information communication technology (ICT).

  In the market, various types of sensors are currently used to sense sensor data by wireless communication (eg, ZigBee) and transmit it to a sink server (receiving server). Each sensor network is becoming a major component of various new network architectures and applications. However, these sensor networks are application specific and they are designed and deployed to provide certain types of services. Their settings are almost static and cannot be easily adapted to different network environments or various new applications. These network protocols and applications are preinstalled in packages that each user cannot separate, replace or change.

  The present invention relates to a dynamic mobile sensor network platform. The platform includes a mobile sensor and a mobile sensor gateway that can easily install new application programs to acquire new sensor data and provide new services to consumers. The present invention describes how a sensor network platform supports disparate network protocols at the network layer, performs identifier (ID) based communication to supply sensor data from each mobile sensor to each sink, and a sensor administrator Specifies whether each control and monitoring command issued by is sent to the mobile sensor. Patent Document 1 discloses ID-based communication achieved by an ID / locator separation protocol stack. Patent Document 2 discloses that mobile sensors and mobile sensor gateways support mobility (movement) and multihoming to reliably provide sensor data regardless of their location. Patent Document 3 discloses network access authentication and each data transfer security function. It specifies the implementation of mobile sensors and mobile sensor gateways.

Patent Document 1 discloses a protocol stack of an ID / locator separation network architecture, a method of forming node names or host names and IDs, ID / locator separation-based communication initialization processing, and ID / locator separation that supports a support hierarchical network structure. Is disclosed. This is in accordance with the paper of HIMALIS (Heterogeneity Inclusion and Mobility Adaptation through Locator ID Separation) in Non-Patent Document 1.
Patent Document 2 discloses a mobility management method for an ID / locator separation network architecture as an extension to Patent Document 1. This follows the publication of Non-Patent Document 2.
Patent Document 3 discloses a security providing method for the ID / locator separation network architecture disclosed in Patent Document 1.

Japanese Patent No. 5327832 JP 2011-117391 A International Publication No. WO / 2013/111192 (Application No .: PCT / JP2012 / 000505)

V.P.Kafle and M. Inoue, "HIMALIS: Heterogeneity inclusion and mobility adaptation through locator ID separation in new generation network," IEICE Transactions on Communications, vol. E93-B, no. 3, March 2010. V.P.Kafle, R. Li, H. Tazaki, and H. Harai, "Network mobility management in HIMALIS architecture of future networks," Proc. Mobiworld 2012 Workshop (collocated with IEEE Globecom 2012), December 2012. VP Kafle, R. Li, D. Inoue, and H. Harai, "Design and implementation of security for HIMALIS architecture of future networks," IEICE Transaction on Information and Systems, vol.E96-D no.2, pp. 226- 237, February 2012. G. Montenegro, N. Kushalnagar, J. Hui, and D. Culler, "Transmission of IPv6 packets over IEEE 802.15.4 networks," IETF RFC 4944, September 2007.http: //tools.ietf.org/html/rfc4944

  Most modern sensor networks are specialized for specific applications because they have been designed and deployed to provide only specified services. Those settings are almost static and it is not easy to make changes to provide new services. These network protocols and application programs are preinstalled in a package format that cannot be separated, replaced or changed by each user. They also lack support for mobility across the Internet and cannot reliably track moving objects such as animals, people and vehicles.

  Accordingly, one of the objects of the present invention is to provide a dynamic mobile sensor network platform capable of communicating with various types of sensors having different protocols.

  It is another object of the present invention to provide a dynamic mobile network platform that can achieve mobility support for the entire Internet and can track mobiles.

  The above-mentioned problems are solved by the invention described in the claims. The present invention is described with respect to a dynamic mobile sensor network platform. The platform includes multiple mobile sensors and multiple mobile sensor gateways, where networking protocols and application programs can be installed, modified, and updated separately. A user can install multiple new applications on the built sensor network, which allows the application to be used in different network environments for new types of services.

  The sensor network platform supports heterogeneous protocols at the network layer, provides sensor data from mobile sensors to each sink, and is ID-based to send control and monitoring commands to mobile sensors issued by sensor administrators Use communication. In order to reliably provide sensor data regardless of sensor location, mobile sensors and each mobile sensor gateway inherently support mobility and multi-homing, and have network access authentication and data transfer security features. Each user or their user computer can freely install a new application program on the already deployed mobile sensor network. They can configure the sensor network to operate in a lightweight mode or a full-function mode according to application requirements or available network environments.

  A first aspect of the present invention relates to a mobile sensor network setup method. The method includes connecting the mobile sensor 11 and the mobile sensor gateway 13 in the mobile sensor network 12. These mobile sensor networks 12 have different network protocols. That is, the networks may have different or various network protocols.

  The method of the present invention may include the step of connecting the mobile sensor network 12 to the access network 15 having a different network protocol after the step of connecting the mobile sensor 11 and the mobile sensor gateway 13. That is, these access networks 15 may have different or various network protocols.

  The mobile sensor 11 includes a sensing unit and a communication unit. The sensing unit includes a plurality of sensors for detecting each physical event and generating sensor data. Since the mobile sensor can sense the environment, the sensing unit can obtain information on the environment. Examples of physical events are temperature, pressure, humidity, light, movement, vibration, presence of an object or action, etc.

  The communication unit includes a calculation component, a storage, and a communication component. The calculation component performs various operations. The storage accumulates various information and the results of operations performed by the computing components. The communication component sends or receives information or data.

  This communication unit has various sensor applications for collecting sensor data from the sensing unit. This communication unit has each network function for realizing a sensor data transmission function using ID-based communication via at least one of the mobile sensor gateways 13 connected in one of the mobile sensor networks 12 to which the mobile sensor gateway 13 belongs. Have a device. That is, the mobile sensor gateway 13 recognizes the ID of the communication unit and enables communication using this ID.

  Since the mobile sensor network has the features as described above, and the method includes the steps described above, the communication unit supports heterogeneous network protocols, and using one of them, at least the mobile sensor gateway 13 Communication with one can be performed. Further, the mobile sensor gateway 13 can use a heterogeneous network protocol for communicating with the mobile sensor 11 in one of the mobile sensor networks 12 and a heterogeneous network protocol for communicating with the access network 15.

  A preferred embodiment of the first aspect includes a mobile sensor network 12 having a heterogeneous network protocol, and for transmitting sensor data from the mobile sensor 11 to the sink server 19 via the access network 15, and sensor control. In order to transmit the monitoring command to the mobile sensor 11 and the mobile sensor gateway 13, the method further includes a step of performing ID-based communication.

The preferred embodiment of the other first aspect further comprises managing the movement of one of the mobile sensors 11 as it moves independently from one of the mobile sensor networks 12 to the other. It is a method. The term mobility management means that the mobile sensor 11 or mobile sensor gateway 13 moves to a new mobile sensor network 12 or a new access network 15 and updates their location stored in the sink server 19 and name registry server 22. Then, when the sensor data is continuously transmitted to the sink server 19 and each control command is received from the client computer 21, the process for causing the mobile sensor 11 or the mobile sensor gateway 13 to acquire a new locator is performed. Means execution.
As the mobile sensor moves from the first mobile sensor network to the second sensor network, the sink server receives information from mobile sensors from different mobile sensor gateways, which causes the sink server to Can be recognized as moving to the other sensor network.

  The embodiment includes a step of managing the movement of the mobile sensor gateway 13 when one of the mobile sensor gateways 13 moves from one of the access networks 15 to the other. The embodiment includes a step of managing one movement of each mobile sensor network as a whole when the mobile sensor gateway 13 and the mobile sensor 11 move from one of the access networks 15 to the other. The details are described in FIG. 7 and in the relevant part of this description (see chapter “Mobile Management Function”).

  Another preferred embodiment of the first aspect establishes security in each network connection with the mobile sensor 11 and the mobile sensor gateway 13 and establishes security through an ID-based communication session to transfer sensor data from the mobile sensor 11. Transmission to the sink server 19 and transmission of each sensor control and monitoring command from the client computer 21 to the mobile sensor 11 and the mobile gateway 13, and security of mobility management of the mobile sensor 11, the mobile sensor gateway 13, and the mobile sensor network 12 It relates to a method comprising the step of establishing.

  Another preferred embodiment of the first aspect is a sensor application comprising mobile sensor 11, mobile sensor network 12 and mobile sensor gateway 13 applications in self-health management in various hospitals and in automatic patient registration and monitoring. About.

  The present invention can provide various services with high reliability to each sensor data related service provider by using sensor data collected from each mobile sensor network using a heterogeneous network protocol. That is, mobile sensors, mobile sensor gateways or sink servers have the freedom to select their appropriate network layer protocol from the protocols available in their network. For example, a mobile sensor can be connected to a WiFi network or to a low-required IEEE 802.15.4 network depending on the power of the mobile sensor or the availability of each network type in that environment. Similarly, the mobile sensor gateway can be connected to an IP version 4 (IPv4) or IP version 6 (IPv6) network. The present invention also secures mobile sensors and mobile sensor gateways to new mobile sensor networks and new access networks, respectively, by identifying the sensors themselves as they move to new networks and initiate connections with them. Connect to. Each mobile sensor and each mobile sensor gateway can continue each communication with each sink server to transmit sensor data even when they are performing a mobility management process. This feature allows mobile sensors carried by various mobile objects such as animals, humans, and vehicles to continuously sense physical events in their various situations, and without interrupting sensor data to the sink server Send it.

  Thus, the present invention can provide a dynamic mobile sensor network platform that can communicate with various types of sensors having different protocols.

  The present invention can achieve support for travel across the Internet and can provide a dynamic mobile network platform that can track mobiles.

FIG. 1 shows the components of a dynamic mobile sensor network according to the present invention. FIG. 2 shows a signaling sequence for securely establishing a mobile sensor gateway connection with a HIMALIS access network. FIG. 3 illustrates a signaling sequence for securely establishing a mobile sensor connection with a mobile sensor network in a situation where the mobile sensor gateway is operating as a proxy for the mobile sensor. FIG. 4 illustrates the proxy of FIG. FIG. 5 shows a signaling sequence for securely establishing a mobile sensor connection with a mobile sensor network in the situation where the mobile sensor gateway is operating as a mobile sensor repeater. FIG. 6 shows a signaling sequence for securely establishing a mobile sensor connection with a mobile sensor network in a situation where the mobile sensor gateway is operating as a HIMALIS gateway. FIG. 7 illustrates a signaling sequence for managing mobile sensor movement when the mobile sensor moves from one mobile sensor network to another mobile sensor network alone. FIG. 8 shows a signaling sequence for managing movement of a mobile sensor gateway when moving from one access network to another access network by executing a make-before-break handover. . FIG. 9 shows a signaling sequence for managing the movement of the mobile sensor gateway when the mobile sensor moves from one access network to another access network by executing a break-before-make handover. FIG. 10 shows an additional signaling sequence for managing the movement of the entire mobile sensor network when the mobile sensor gateway and the mobile sensor move together from one access network to another access network. FIG. 11 shows a signaling sequence for securely establishing an ID-based communication session between the mobile sensor and the sink server when the mobile sensor is connected to the HIMALIS access network. FIG. 12 shows a signaling sequence for securely establishing an ID-based communication session between the mobile sensor and the sink server when the mobile sensor gateway is connected to the Internet access network. FIG. 13 illustrates ID-based communication across network segments of heterogeneous protocols. FIG. 14 illustrates the software modules of the mobile sensor and mobile sensor gateway.

Dynamic Mobile Sensor Network Components FIG. 1 shows an example of each component of a dynamic mobile sensor network platform. The mobile sensor network 12 includes mobile sensors (MSs) 11 and mobile sensor network gateways (MSGs) 13. The mobile sensor gateway 12 is connected to one or more access networks 15 via MSGs 13. The MSG 13 is connected to the access network 15 via a wireless access point (WAP) 17. The access network 15 can use, for example, IPv4 or IPv6 as a network layer protocol. Also, the two access networks can use different network layer protocols, for example, one using IPv4 and the other using IPv6. The access network 15 can be connected to the Internet via a HIMALIS gateway (HGs) 20 or other gateways. The figure shows a sink server 19 (hereinafter referred to as “sink”) located in the Internet that collects sensor data from each MS 11. The sink 19 can provide advanced sensor application services by distributing sensor data to other storage servers such as a big data server. This mobile sensor network is monitored and controlled by the computer of the sensor administrator 21 by generating each control command. These components are outlined in the following paragraphs.

Mobile sensor (MS):
The MS 11 has at least two units: a sensing unit and a communication unit. The sensing unit senses the environment, generates sensor data, and provides the data to the communication unit. The communication unit is a device that receives sensor data from the sensing unit and transmits it to the sink 19. The communication unit has each communication function and each application for collecting sensor data and transmitting it to the sink 19 through the network. This communication protocol stack is based on an extension to the ID / locator separation network architecture [Patent Document 1], the mobility management method [Patent Document 2], and the security method [Patent Document 3]. The link layer access technology can be WiFi (ie IEEE 802.11) or IEEE 802.15.4, but also for low power consumption. These documents are incorporated herein for reference. Together with IEEE802.15.4, the 6LoWPAN protocol [Non-Patent Document 4] can be used at the network layer. The MS has the ability to securely identify itself and connect to the mobile sensor network, starting each ID-based communication with each sink, and mobility management.

Mobile sensor gateway (MSG)
This MSG 13 has all the functions of the communication unit of the MS 11 for performing ID-based communication. It has functions for network layer protocol conversion, multihoming management, routing and packet forwarding. It has at least two wireless interfaces. That is, one is for connection with the mobile sensor network 12 and the other is for connection with the access network 15. The mobile sensor network link may be a power saving radio, ie IEEE 802.15.4, and the access network link may be WiFi. Additionally, it may have additional wireless and wired interfaces for connecting with cellular networks and wired access networks. This mobile sensor network interface uses the 6LoWPAN protocol in the network layer, whereas the access network interface is IPv4 or IPv6.

HIMALIS gateway (HG):
HG 20 is similar to MSG in that it also has the functionality for network layer protocol conversion, mobility and multi-homing management for ID-based communication. At least two interfaces: a wireless interface (eg, WiFi) for setting up a downstream link with the access network and another wired interface (eg, Ethernet (for example) for setting up each upstream link to the Internet or transit network. Registered trademark)). Additionally, it can have each additional upstream link to create a multihomed access network. It supports both IPv4 and IPv6, and translates from IPv4 to IPv6, and reverses if necessary. It participates in MS and MSG network access control through an authentication mechanism. Note that some access networks do not have HG, ie they are just Internet access networks, and each MSG is directly connected to the Internet.

sink:
The sink 19 has an ID / locator separation base protocol, performs ID-based communication with each MS and each MSG, and collects and stores sensor data. It may have either IPv4 or IPv6 protocol or both protocols at the network layer. It collects and stores sensor data obtained from each MS and places them on each client, or other storage server such as a big data server, creating various applications such as the Internet of Things (IoT) service. It also owns each sensor application for distribution. However, in this embodiment, the big data server is not an essential part of technological innovation.

Sensor administrator:
The computer or client computer of the sensor manager 21 issues each command, and monitors, sets, or controls each MS and each MSG via ID-based communication. In FIG. 1, the sensor administrator is located in the Internet, but it may be located anywhere on each access network 15. FIG. 1 shows a name registry server 22 (also referred to as a “name registry”) for storing, updating, and retrieving the ID and locator mapping of each MS and each MSG. These servers may exist in the Internet access network or in the HIMALIS access network to assist each MS in resolving hostname IDs and locators of other nodes (eg, sinks). .

Network functions These networks can be classified into two planes: the control plane and the data plane. The following paragraphs describe various control and data plane functions.

Control plane functions:
Each control plane function is used for network access control, mobility management, registration, search, and update of ID / locator mapping in each name register. Each data plane function establishes an ID-based communication session and transfers sensor data from the MS to the sink via the network of the heterogeneous network layer protocol.
Each network access control function identifies and attaches a procedure for the mobile sensor network to the access network. Therefore, MSG and MS identify themselves and are securely connected to the access network and sensor network respectively.

To establish a mobile sensor gateway connection with an access network:
As shown in FIG. 1, the MSG can be connected to an access network including or not including the HG. The signaling sequence performed by the MSG to connect to the access network changes in these two cases.

  In an access network including the HG referred to in this embodiment as a HIMALIS access network, the MSG executes the signaling sequence shown in FIG. 2 and is securely connected to the access network. As shown in the diagram, after completing the layer 2 (L2) link setup by using a link layer protocol (eg IEEE802.11), the dynamic changed for HIMALIS deployed with HG In the locator assignment message sent from the Host Configuration Protocol (DHCP) server (represented as “MSG hostname / ID / LLoc” in the figure), the HG hostname, ID and local locator used in the LLoc ( LLoc), that is, MSG receives the IP address. This MSG will be used to calculate a message authentication code (MAC) to protect subsequent messages, a host registration request message containing its hostname, ID, and an algorithm that calculates the integrity of the data. Set. This host registration request message also includes a MSG signature ("|| MSG's sig" in the figure indicates that a MSG signature has been added to the message). MSG sends a host registration message to HG. Upon obtaining this message, HG proves the MSG match by securely retrieving the MSG ID and PK from the name registry / authentication server. If the MSG signature is verified, the HG stores the MSG parameters in the host table. HG then (in the figure, represented by {Access ID, Access Key} MSG PK) Access ID encrypted both by MSG's public key, Host Registration Response message with access key, and Global Locator (GLoc), set the locator for the upstream link of HG. This message is signed by HG (represented by “|| HG ’s sig” in the figure) and sent to MSG. When this message is received by MSG, the procedure for establishing that connection to the access network is successfully completed. The MSG then sends a location update message containing the global locator to the name registry. This message is protected by including security information that is computed by using a pre-shared security key between the MGS and the name registry.

  Here, when the HG does not exist in the access network that is the Internet access network, the MSG is connected to the access network using a conventional host setting protocol such as DHCP provided by the access network. To help MSG identify the HIMALIS access network and the Internet access network, additional information such as HG IDs and locators, local name registry servers, and authentication agents has been modified for HIMALIS. Included in the DHCP Offer message.

  We have made it possible to connect MSG to either the HIMALIS access network or the Internet access network for flexibility in sensor network deployment. This HIMALIS access network gives the authority to provide MSG with additional functions of network access security, seamless mobility and communication on heterogeneous access networks. If this network is not deployed, it will simplify the mobile sensor network deployment in that it does not require a special node, i.e. HG, in the access network, but an additional authorization mechanism not specified here will be used. You will need it.

  Depending on the type of access network, MSG can operate as one of the following three modes for MS network access: alternate node, relay node, and HG. In the first and second modes, the MSG will be connected to the HIMALIS access network. And in the third mode, it will be connected to the Internet access network.

The procedure for establishing a mobile sensor connection with a mobile sensor network is:
The sequence of signaling messages exchanged by the MS to connect to the mobile sensor network depends on the operating mode of the MSG indicated by the second half of the network offer or locator assignment message notified in the sensor network.

  Mobile sensor connection procedure with the mobile sensor network when MSG acts as an alternative node: The role of the MS in the procedure to make a connection with the mobile sensor network only requires that it initiates the connection procedure, It is further mitigated in that MSG negotiates with HG to handle the remaining steps of authentication and local registration required to complete the connection procedure. FIG. 3 shows the sequence of each signaling message exchanged to establish the MS connection with the mobile sensor network. After completing the Layer 2 (L2) link setup by using the IEEE 802.15.4 protocol, the MSG is the local locator (LLoc), ie the IP address used in the sensor network and the access network (in the figure the MS hostname / Send MSG hostname, ID and LLoc (expressed as ID / LLoc) to MS. This MS sets up and sends to the MSG a host registration message that includes an algorithm that calculates its hostname, ID and data integrity used to calculate a message authentication code to protect subsequent messages. This message contains the MS signature ("|| MS's sig" in the figure means that the MS signature is added to the message). Upon obtaining this message, MSG verifies the MS match by retrieving the MS's ID and PK from the name registry and authentication server. If this MS's signature is verified, each of the above parameters of this MS are stored in the host table, and then a host registration request is sent to the HG that includes the MS's ID and reference locator. The reference locator is a locator of the upstream link of the MSG, that is, a locator obtained by the MSG from the access network. The HG stores the MS ID and reference locator in the host table, and sends a response back to the MSG. This MSG then sets up a host registration response message containing the access ID and access key that are both encrypted by the MS's public key (represented by "{access ID, access key} MS's PK" in the figure). This message is signed by the MSG (represented by “|| MSG's sig” in the figure) and sent to the MS. When this message is received by the MS, the network connection procedure is successfully completed. The MS then sends a location update message containing the new reference locator to the name registry. This message is protected by using a pre-shared security key between the MS and the name registry. Thus, this name registry stores the latest MS ID and locator mapping so that any other host that spontaneously initiates an ID-based communication session with the MS can retrieve the MS's latest ID / locator mapping. .

  FIG. 4 shows an alternative sequence of signaling messages exchanged by securely establishing a connection of the MS with the mobile sensor network by demonstrating that the MS and MSG match each other. After the MS has this type of reliable association with the MSG, the MS entrusts the MSG to perform signaling operations in the access network for the MS. This MSG can change each parameter in each signaling message being exchanged between the MS and the access network (ie, HG), and this HG treats the MS's ID as the other ID of the MSG.

  Procedure for mobile sensor connection with mobile sensor network when MSG operates as a relay node: Procedure for connection of MS with mobile sensor network shown in FIG. 5 is network access of host in [Patent Document 3] Is an extended version of the procedure specified as In this mode, the HG located in the access network passes the authentication procedure to the MS. This MSG simply converts 6LoWPAN to IPv6 and IPv6 to IPv4, if necessary, in each signaling packet.

  Procedure for mobile sensor connection with mobile sensor network when MSG operates as HG: The procedure for MS connection with mobile sensor network shown in FIG. 6 is the network in the host in [Patent Document 3] MSG, an extended version of the procedure specified as access, controls network access and MS identity and locator mapping in the host table used in MS mobility management and possible communication across each heterogeneous protocol. Have HG follow the certification procedure to maintain.

  As specified above, MS and MSG will thus be able to operate flexibly in different modes, ie lightweight signaling mode and full signaling mode, and available network environments, device capabilities (eg low Network capacity protocols and wireless technologies can be selected that meet each application requirement (eg, higher reliability, continuous connectivity).

Mobility management function:
In the dynamic mobile sensor network described above, where the mobility of the MS, MSG or the entire sensor network is originally supported, that mobility is the main feature. This MS can safely change its link from one sensor network (ie, from one MSG) to another without disrupting their ID-based communication session, and from the access network to another You can change that link. For mobility support, MS and MSG use an extension of the HIMALIS mobility function [Patent Document 2].

  As shown in FIG. 7, when an MS moves from one sensor network (ie from an old MSG) to another (ie to a new MSG), it authenticates itself, as explained above, and A connection with the new mobile sensor network is first established by acquiring a new locator. It then updates the locator stored in the sink and in the name registry by sending a location update request message containing the new locator. The sink updates the MS locator in its ID table and sends it back to the MS. Similarly, the name registrar updates the MS locator in the record and sends a response message back to the MS. The MS will resume ID-based communication with the sink via the new MSG. The MS then unregisters each parameter of the MS obtained from the old mobile sensor network by sending a host deregistration message to the old MSG via the new HG and the new MS. The old HG and old MSG remove the MS record from their respective host tables and return a host deregistration message to the MS. However, the deregistration process is not essential for a successful handover. On the one hand, it is implemented for a sophisticated handover mechanism that properly deletes the state information associated with the MS from the old mobile sensor network as well as the old access network.

This MSG can move with all MSs alone or together underneath (this is also known as sensor network mobility). In both cases, MSG is almost the same handover procedure: a new local locator (configured using the network prefix of the access network) and a global (configured using the network prefix of the HG upstream interface). Establish a connection with a new access network to obtain a locator and update its name registry with the new global locator. This MSG is either a make-before-break type handover or a break-before-make type handover, depending on whether it can remain connected to the old HG when performing handover signaling via the new HG. Perform a handover.
Figure 8 shows the old and new HG and handover signaling in order to redirect or relay downstream packets to the new HG and forward the new HG to the MSG (and ultimately forward to the MS). Shows a make-before-break type handover (also known as a seamless handover) that allows MSG to communicate with the old and new HG. FIG. 9 shows a break-before-make type handover when the MSG is disconnected from the old access network before connecting to the new access network. In this case, the MSG transmits a handover instruction message to the old HG in order to request the old HG to relay each packet using the new HG. The remaining steps are similar to those in FIGS. If the MSG is moving alone, any MS that detects the presence of MSG in the new sensor network will initiate a network connection procedure as previously described to connect to the mobile sensor network. Is also possible.

  FIG. 10 shows an additional signaling sequence for sensor network mobility. Once the MSG completes the handover, it sends a message containing the IDs of all MSs directly below it to the new HG, and the new HG adds these IDs to its host table and sends them to the MSG. Send back. This MSG then notifies each MS located immediately below the information on the change of the global locator by sending a handover notification message. By receiving this message, the MS that moves with the MSG recognizes that its global locator has changed, performs a locator update using the sink, and continues ID-based communication.

ID / locator mapping registration, search and update functions:
If the MSG or MS is securely connected to the access network or sensor network via the initial registration process specified in [Patent Document 3], it will have its host name, ID, and public key registered in the name registry To get. This name registry also provides a shared secret key. Whenever the MSG or MS changes its global locator due to its mobility, it sends a locator update message containing the global locator to the name register. This message contains security information or code calculated by using a shared secret key. The name registry authenticates the security code and updates its record accordingly. Similarly, any other code that voluntarily establishes an ID-based communication session using the MS (eg, a sink or an administrator) can send name resolution to a name registry as specified in [Patent Document 3]. You can securely retrieve MS ID, locator and public key by sending solution query.

ID-based communication to send sensor data over heterogeneous network protocol Data plane is provided by the control plane to establish ID-based communication between MS and sink to transfer sensor data via MSG For example, information such as ID / locator mapping and each security key is used. To establish an ID-based communication session as shown in FIGS. 11 and 12, the MS or sink exchanges their ID and each locator, verifies each other match, and executes the signaling sequence to share the session key Start the communication initialization procedure by negotiating (sesskey). Thereafter, both the MS and the sink store each other's ID, each locator, and each security key in their ID tables as shown in FIG. Similarly, sink IDs and locators can be used to perform network layer header (ie, each locator) translations in each sensor data packet that travels from MS to sink via each network in each heterogeneous protocol. Stored in each ID table of HG. For ID-based communication as specified in [Patent Document 1], the application and transport layer, for example, socket application program interface (API) match confirmation and checksum calculation to protect the integrity of each data segment, etc. In this function, an ID whose value and each format does not depend on each lower layer network protocol is used. In other words, each ID is a locator whose format or length depends on the protocol version (eg, an IPv4 address is 32 bits long, whereas an IPv6 address is 128 bits long), ie Different from each IP address. Thus, in ID-based communication, the same application can be used in different mobile sensors that can use different protocols (either IPv4 or IPv6) at the network layer. Thus, the present invention is preferred for heterogeneous protocol Internet communication at the network layer. It is also possible to use either IPv4 or IPv6 protocol at the network layer to route and forward each packet using an IP address, ie a locator. However, these IP addresses are not used in the application layer and transport layer. Only each ID is used in each application and transport layer. The matching layer inserted between the transport layer and the network layer uses the ID table to map each ID to each locator and vice versa. The MS and MSG tables are updated as the MS or MSG changes its locator due to its mobility. These conditions prevent the ID-based communication from being disconnected due to an event when the MS, MSG, or sink moves from one network to another. Thus, ID-based communication maintains session continuity even when each underlying network protocol changes or each location of each endpoint changes during the session. Also, each ID present in the packet header does not change so that the packet traverses each network domain of each heterogeneous protocol, but each locator present in the packet header changes as such. Each ID present in the packet header is used as a reference value for converting each locator in the packet header when the packet passes through each network domain of each different protocol.

Software Modules in Mobile Sensor and Mobile Sensor Gateway FIG. 14 shows MS and MSG software modules. The sensor application and 6LoWPAN daemon are in user space, and the HIMALIS stack, TUN (virtual network kernel device) and each serial connection module are in the kernel. The sensor application in the MS collects sensor data by activating the sensor unit via a USB connection. It creates each sensor data packet and sends them to the HIMALIS stack via each UDP socket. In this HIMALIS stack, the packet sequentially passes through an IPv6 including UDP, ID, and UDP header, an ID header including a sink and its own ID, and an IPv6 header including MSG and its own locator. This HIMALIS stack sends packets in user space to the TUN device that supplies HIMALIS to the 6LoWPAN daemon. The 6LoWPAN daemon converts a 40 octet IPv6 header into 6 octets (if not fragmented) or 8 octets (if fragmented) 6LoWPAN. This packet may be fragmented if its size does not fit within 102 octets that can be operated as an IEEE 802.15.4 MAC service data unit (MSDU). The 6LoWPAN daemon writes packets in a serial port attached to a wireless interface connected to the mobile sensor network. This data is then transmitted over the mobile sensor network. On the MSG side, the processing occurs in the opposite direction. That is, the wireless interface connected to the mobile sensor network receives the packet from the sensor network and sends it to the 6LoWPAN daemon via the serial port. The 6LoWPAN daemon reconstructs the fragmented packet, creates a full IPv6 header, and writes the packet to the TUN device. This packet then passes through the HIMALIS stack, which either provides the packet to the sensor application in the MSG or forwards the packet to the access network via a wireless interface connected to the access network. it can. In the former case, the sensor application can add more information to the sensor data, for example location information obtained from GPS, and then send the packet to the access network. In the latter case, the MSG acts as a mere router for forwarding sensor data packets received from the sensor network to the access network. Note that the HIMALIS stack inherently supports network layer protocol conversion from IPv4 to IPv6 and vice versa. Therefore, the access network can be an IPv4 or IPv6 network. This ID-based communication is used to control and monitor the MS from a remote location. As shown in FIG. 1, a sensor administrator can issue a sensor control command and a sensor monitoring command, and the sensor control command and the sensor monitoring command are securely transmitted to the MS by ID-based communication. These control commands can turn the MS on and off, or change its data sampling rate. Similarly, each monitoring command can read the status of the sensor, for example, whether it is powered on or off, its latest data, time and position.

  Depending on the availability of the service network in the environment and the capacity of the sensor device, not only the link layer such as IEEE802.11 (WiFi) or IEEE802.15.4 but also the network layer such as IPv4 and IPv6 However, the present invention can be applied to applications based on sensor networks and sensor data. Mobile sensors and mobile sensor gateways in different sensor networks use different network protocols, but they can communicate with the same sink server to send sensor data. Even when they move from one network to another, they can continue their communication with the sink server. Each mobile sensor and each mobile sensor gateway is attached to multiple mobile objects such as animals, humans and vehicles, continuously sensing physical events in their environment, and sending sensor data to the sink can do.

  The mobile sensor network platform can provide each sensor application service based on sensor data of various environments such as temperature, light, pressure, and humidity. A new sensor can be added to the sensor unit at any time by adding an application program corresponding to the communication unit. The MS can create sensor data at a preset sampling rate and send them to the sink. MSG can add location information to sensor data. An MS can send sensor data to one or more sinks via an MSG. Similarly, a sink can obtain sensor data from many MSs. The relationship between MS, MSG and sink can be controlled by the sensor administrator. Accordingly, the sensor administrator distributes each MSID (for example, host name) and each security key necessary to establish an ID-based communication session for collecting sensor data from the MS to each sink. Each ID-based communication session persists even when moving from one access network to another MS, MSG or sensor network. To increase reliability and smooth handover, the MSG can be equipped with two or more upstream links that are simultaneously connected to different access networks.

  Two applications: self-health management in hospital and automatic patient registration and monitoring

Self-health management:
Since the aforementioned platform easily supports the addition of new sensor modules to each mobile sensor node, new sensors are added, in addition to ambient light, temperature, pressure and humidity, eg blood pressure, insulin level, heart or lung Body parameters such as the state of can be read. Carry MS with MSG regardless of patient's own position and movement status, and sensor data can be continuously transmitted to sink where self-health management application uses this data to assess patient health . In one alternative deployment approach, the patient holds only the MS and uses MSG that is carried by others or installed in each home and each public place that people often visit. In this case, the MS and the MSG authenticate each other using the HIMALIS access control mechanism [Patent Document 3] before causing the MS to transmit sensor data to the sink. In this way, body parameters are automatically monitored without requiring the patient to go through procedures such as measuring or transmitting information. If the patient wants to know his health, the patient can establish an ID-based communication session with the sink at any time using the client device and download information about the patient himself. If the patient carries both MS and MSG, MSG can be used as a client device to get online health services.

Automatic patient registration and monitoring in hospitals:
Other applications of mobile sensor networks can be in their automatic monitoring and registration when patients visit a hospital. The patient carries each MS and installs each MSG at the hospital, entrance, and waiting room. When a patient enters the hospital, the MS accesses the sensor network via MSG and sends the patient's body parameters to a sink server located in the hospital. The health check application running in the sink server numerically grasps the patient's condition in advance based on past and current sensor data, and nurses and doctors indicate the patient's current health condition to the hospital. Deliver results to each client device owned by nurses and doctors so that they can be known as they come. Even when the patient is moving around the hospital, the patient's location and body parameters are continuously monitored. Thus, the implementation of this service effectively reduces delays in patient registration and testing by automatically providing patient information to each nurse and doctor as soon as the patient enters the hospital or room. Will be useful in terms.

  The present invention is applicable in the ICT industry.

Claims (5)

Connecting a plurality of mobile sensors (11) and a plurality of mobile sensor gateways (13) in a plurality of mobile sensor networks (12) having different network protocols;
Connecting the mobile sensor network (12) to each access network (15) having a heterogeneous network protocol;
Each of the mobile sensors (11) includes a sensing unit and a communication unit,
The sensing unit contains a plurality of sensors that detect physical events and generate sensor data;
The communication unit comprises computation, storage and communication components;
The communication unit further comprises a sensor application that collects sensor data from the sensing unit and is connected to at least one mobile sensor gateway connected in one of the mobile sensor networks (12) to which the mobile sensor gateway (13) belongs. By using ID-based communication via (13), it has a network function to transmit the sensor data,
The communication unit can support the heterogeneous network protocol and can use one of the heterogeneous network protocols communicating with at least one of the mobile sensor gateways (13), and the mobile sensor gateway (13 ) Can use different network protocols when communicating with the mobile sensor (11) in one of the mobile sensor networks (12), and also when communicating with the access network (15). You can use mobile sensor network setup method. Sensor data is transmitted from the mobile sensor (11) to the sink server (19) via the mobile sensor network (12) and the access network (15) having a heterogeneous network protocol, and sensor control and monitoring commands are transmitted The method of claim 1, further comprising performing ID-based communication for transmission to a mobile sensor (11) and the mobile sensor gateway (13). Managing the movement of the mobile sensor when one of the mobile sensors (11) moves independently from one of the mobile sensor networks (12) to another mobile sensor network;
Managing the movement of the mobile sensor gateway when one of the mobile sensor gateways (13) moves independently from one of the previous access networks (15) to another access network;
Managing the movement of one of the mobile sensor networks as a whole when the mobile sensor gateway (13) and the mobile sensor (11) move together from one of the access networks (15) to another access network The method according to claim 1, further comprising: Further comprising establishing security in a network connection of the mobile sensor (11) and the mobile sensor gateway (13),
Establishing security by the ID-based communication session, transmitting sensor data from the mobile sensor (11) to the sink server (19), and from the client computer (21) to the mobile sensor (11) and the mobile sensor gateway The sensor control and monitoring command is transmitted to (13), and security in mobility management of the mobile sensor (11), the mobile sensor gateway (13), and the mobile sensor network (12) is established. Method. The method of claim 3, wherein the sensor application includes applications of the mobile sensor (11), mobile sensor network (12), mobile sensor gateway (13) in hospital self-health care and automatic patient registration and monitoring. .

Images