WO2015080553A1

WO2015080553A1 - Method and system for enabling ip communication between an ip device and a non-ip internet of things device

Info

Publication number: WO2015080553A1
Application number: PCT/MY2014/000132
Authority: WO
Inventors: Zeldi Suryady KAMALURRADAT; Shariq Haseeb; Gopinath Rao Sinniah; Usman Sarwar; Reza Khoshdelniat
Original assignee: Mimos Berhad
Priority date: 2013-11-27
Filing date: 2014-05-29
Publication date: 2015-06-04
Also published as: MY182630A

Abstract

Described herein is a method that enables an IP device (200) that is capable of IP communication and at least one Internet of Things (loT) device (100) that is not capable of IP communication to communicate with each other in IP manner. Generally, the method works by providing the loT device (100) with virtual IP services, specifically to allocate and link the loT device (100) with a virtual IP address, making the loT device (100) to be virtually IP addressable and identifiable via the allocated virtual IP address. Also described herein is a system for executing the aforesaid method.

Description

METHOD AND SYSTEM FOR ENABLING IP COMMUNICATION BETWEEN AN IP DEVICE AND A NON-IP INTERNET OF THINGS DEVICE

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to IP communication between entities, and more particularly to an IP communication between an IP device that is capable of IP communication and at least one Internet of Things (loT) device that is not capable of IP communication.

BACKGROUND OF THE INVENTION

The Internet of Things (loT) is composed of heterogeneous objects that are operating on various existing technological protocols, and therefore their communication methods may vary from one to another. It is important for the heterogeneous objects to be able to communicate with each other or connect to a database, individual, etc., and therefore it has become a main question on how to achieve this sort of communication. In order to achieve this interoperability, the use of Internet protocol (IP) would be desirable as it is the de facto language of "Internet". Nevertheless, not all objects in loT operate using IP, such objects comprise radio-frequency identification (RFID), electronic product code (EPC) tag, etc. For these constrained devices, the communication using IP (e.g. IPv4/IPv6) is a big challenge. Yet, at the same time, the uses of these technologies have hugely become the integral parts of our daily lives. In order to increase the advantages and widen the usefulness of these technologies, the integration of IP communication into the same is essential. In view of the above, it therefore has become an aim of the present invention to solve the above-mentioned technical issues and disadvantages by introducing a method and system that enables an IP communication between an IP device that is capable of IP communication and at least one Internet of Things (loT) device that is not capable of IP communication by providing virtual IP services to the loT device.

SUMMARY OF THE INVENTION

The first core aspect of the present invention is directed to a method that enables an IP communication between an IP device that is capable of IP communication and an Internet of Things (loT) device that is not capable of IP communication. The method works by providing virtual IP services to the loT device, specifically to allocate and link a virtual IP address to the loT device, making the loT device virtually IP addressable and identifiable via the allocated virtual IP address.

The aforesaid method comprises a first step of registering the loT device to a gateway. In one embodiment of the present invention, the loT device is registered to the gateway by having its information stored in a first device record residing in the gateway, and replicated at a second device record residing in a virtual IP provider. A tunnel with an expiry period is created between the gateway and a virtual IP provider upon receiving a request message for communication with the loT device from the IP device to the virtual IP provider or a request message for communication with the IP device from the loT device to the gateway. In other words, the tunnel creation is done on-demand, triggered by the request message.

In an embodiment of the present invention relating to the tunnel creation, upon receiving the request message, communication managers check whether there is an existing tunnel that is connecting the gateway and the virtual IP provider via the device records. In the event that there is no existing tunnel, the communication managers instruct tunnel creators residing in the virtual IP provider and the gateway to create a tunnel between them, and the device records are updated with the change. In the event that there is an existing tunnel, the communication managers instruct the tunnel creators residing in the virtual IP provider and the gateway to prolong the expiry period of the existing tunnel, and the device records are updated with the change.

In a further embodiment of the present invention relating to the tunnel creation, upon receiving the request message sent by the IP device, a second communication manager residing in the virtual IP provider checks whether there is an existing tunnel via the second device record. In the circumstance where there is no existing tunnel, the second communication manager will instruct a second tunnel creator residing in the virtual IP provider and a first tunnel creator residing in the gateway to create the tunnel. Thereafter, the second device record residing in the virtual IP provider is updated with the change. In the circumstance where there is an existing tunnel, the second communication manager will instruct the second tunnel creator residing in the virtual IP provider and the first tunnel creator residing in the gateway to prolong the expiry period of that particular existing tunnel. Thereafter the second device record is updated with the change.

In another embodiment of the present invention relating to the tunnel creation, upon receiving a request message sent by the loT device, a first communication manager residing in the gateway checks whether there is an existing tunnel via the first device record. In the circumstance where there is no existing tunnel, the first communication manager will instruct the first tunnel creator residing in the gateway and the second tunnel creator residing in the virtual IP provider to create the tunnel. Thereafter, a first device record residing in the gateway is updated with the change. In the circumstance where there is an existing tunnel, the first communication manager will instruct the first tunnel creator residing in the gateway and the second tunnel creator residing in the virtual IP provider to prolong the expiry period of that particular existing tunnel. Thereafter the first device record is updated with the change.

Soon after the registration, the loT device is being allocated and linked with a virtual IP address, which is selected from an IP address pool, for a predetermined time upon receiving a request message for communication with the loT device from the IP device to the virtual IP provider or a request message for communication with the IP device from the loT device to the gateway.

In still another embodiment of the present invention relating to the virtual IP address allocation, before the loT device is being allocated and linked to the virtual IP address, the second communication manager residing in the virtual IP provider checks whether there is an existing virtual IP address that is linked to the loT device via the second device record. In the circumstance where there is no existing virtual IP address that is linked to the loT device, the second communication manager will allocate and link the loT device with the virtual IP address, which is selected from the IP address pool. Thereafter the second device record is updated with the change. In the circumstance where there is an existing virtual IP address that is linked to the loT device, the second communication manager will prolong the predetermined time of the existing virtual IP address that is linked to the loT device. Thereafter the second device record is updated with the change.

In still a further embodiment of the present invention relating to the virtual IP address allocation, before the loT device is being allocated and linked to the virtual IP address, the first communication manager residing in the gateway checks whether there is an existing virtual IP address that is linked to the loT device via the first device record. In the circumstance where there is no existing virtual IP address that is linked to the loT device, the first communication manager will request the second communication manager residing in the virtual IP provider to allocate and link the loT device with the virtual IP address, which is selected from the IP address pool. Thereafter the first device record is updated with the change. In the circumstance where there is an existing virtual IP address that is linked to the loT device, the first communication manager will prolong the predetermined time of the existing virtual IP address that is linked to the loT device. Thereafter the first device record is updated with the change.

After the tunnel creation and the virtual IP address allocation, at least one of the IP device and the loT device is being informed that the loT device has been successfully allocated and linked with the virtual IP address, and the tunnel has been successfully created and ready to be used for relaying packets between the IP device and the loT device. The IP device and the loT device are able now able to communicate with each other by sending a packet to each other, the said packet includes the virtual IP address that is now linked to and serves as the identity of the loT device, said virtual IP address enables the packet to be transmitted to the correct recipient. In the case where the IP device wishes to communicate with the loT device, the former first sends a packet including the virtual IP address that is linked to the loT device to the second communication manager residing in the virtual IP provider. Subsequently, the second communication manager encapsulates the packet and sends it to the first communication manager residing in the gateway through the created tunnel. Upon receiving the encapsulated packet, the first communication manager de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the loT device that is linked to the virtual IP address by using the loT device's native communication. In the case where the loT device wishes to communicate with the IP device, the former first sends a packet including the virtual IP address that is linked to the loT device to the first communication manager residing in the gateway by using its native communication. Subsequently, the first communication manager encapsulates the packet and sends it to the second communication manager residing in the virtual IP provider through the created tunnel. Upon receiving the encapsulated packet, the second communication manager de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the IP device, informing the IP device that the packet is originated from the loT device that is linked to the virtual IP address.

As mentioned above, the tunnel is created with an expiry period. Soon after the expiry period has expired, the tunnel is removed, and either the first device record or the second device record is updated with the change. As mentioned above, the virtual IP address is allocated and linked to the loT device for a predetermined time. Soon after the predetermined time has expired, the virtual IP address is removed and returned to the IP address pool, and either the first device record or the second device record is updated with the change.

Throughout the method as described above, it can be seen that many changes are made and recorded in either the first device record or the second device record. The method is therefore designed in a way that the first device record and the second device record are always in sync in order to update each other of any changes that may comprise changes made to the information of the loT device, the expiry period of the tunnel, and the virtual IP address that is allocated to the loT device and its predetermined time, etc. The second core aspect of the present invention is directed to a system that enables an IP communication between an IP device that is capable of IP communication and an Internet of Things (loT) device that is not capable of IP communication. The system works by providing virtual IP services to the loT device, specifically to allocate and link a virtual IP address to the loT device, making the loT device virtually IP addressable and identifiable via the allocated virtual IP address.

The aforesaid system comprises, in general, comprises a gateway that is connected to the loT device, forming a personal area network that is not capable of IP communication, and a virtual IP provider that is connected to the IP device, capable of IP communication.

The aforementioned gateway further comprises another three essential elements, namely a first device record, a first communication manager, and a first tunnel creator. The first device record is used to store information that is related to the loT device and tunnel, for examples the physical address of the loT device, an expiry period of a tunnel, a virtual IP address that is allocated and linked to the loT device and its predetermined time, etc. The first communication manager is used to manage the creation of a tunnel with an expiry period between the gateway and the virtual IP provider, managing the allocation of a virtual IP address to the loT device for a predetermined time, and receiving, processing including encapsulating and de-capsulating, and sending packets between the loT device and the virtual IP provider. The first tunnel creator is used to create the tunnel as instructed by the first communication manager, and maintain the availability of the tunnel according to the expiry period.

The aforementioned virtual IP provider further comprises another four essential elements, namely a second device record, a second communication manager, a second tunnel creator, and an IP address pool. The second device record is used to store information that is related to the loT device and tunnel, for examples the physical address of the loT device, an expiry period of a tunnel, a virtual IP address that is allocated and linked to the loT device and its predetermined time, etc. The second communication manager is used to manage the creation of a tunnel with an expiry period between the gateway and the virtual IP provider, managing the allocation of a virtual IP address to the loT device for a predetermined time, and receiving, processing including encapsulating and de-capsulating, and sending packets between the IP device and the gateway. The second tunnel creator is used to create the tunnel as instructed by the second communication manager, and maintain the availability of the tunnel according to the expiry period. The IP address pool comprises a plurality of unused virtual IP addresses readily to be selected, allocated, and linked by the second communication manager to the loT device.

All the aforementioned elements within the system work together to enable IP communication between the IP device and the loT device. The IP device and the loT device are able now able to communicate with each other by sending a packet to each other, the said packet includes the virtual IP address that is now linked to and serves as the identity of the loT device, said virtual IP address enables the packet to be transmitted to the correct recipient. In the case where the IP device wishes to communicate with the loT device, the former first sends a packet including the virtual IP address that is linked to the loT device to the second communication manager residing in the virtual IP provider. Subsequently, the second communication manager encapsulates the packet and sends it to the first communication manager residing in the gateway through the created tunnel. Upon receiving the encapsulated packet, the first communication manager de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the loT device that is linked to the virtual IP address by using the loT device's native communication.

In the case where the loT device wishes to communicate with the IP device, the former first sends a packet including the virtual IP address that is linked to the loT device to the first communication manager residing in the gateway by using its native communication. Subsequently, the first communication manager encapsulates the packet and sends it to the second communication manager residing in the virtual IP provider through the created tunnel. Upon receiving the encapsulated packet, the second communication manager de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the IP device, informing the IP device that the packet is originated from the loT device that is linked to the virtual IP address.

The first device record and the second device record are always in sync in order to update each other of any changes made to either the first device record or the second device record. The said changes comprise changes made to the information of the loT device, the expiry period of the tunnel, and the virtual IP address that is allocated to the loT device and its predetermined time, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates the system architecture of the present invention.

DETAILED DESCRIPTION OF THE INVENTION The above mentioned and other features and objects of this invention will become more apparent and better understood by reference to the following detailed description. It should be understood that the detailed description made known below is not intended to be exhaustive or limit the invention to the precise disclosed form as the invention may assume various alternative forms. On the contrary, the detailed description covers all the relevant modifications and alterations made to the present invention, unless the claims expressly state otherwise. The present invention introduces herein two main aspects. They are a method and a system for enabling an IP communication between an IP device (200) that is capable of IP communication and at least one Internet of Things (loT) device (100) that is not capable of IP communication. The method and the system achieve this aim by providing virtual IP services to the loT device (100), specifically to allocate a virtual IP address to the loT device (100). This action consequently causes the loT device (100) to be virtually IP addressable and identifiable via the allocated virtual IP address. In other words, the loT device (100) is now capable of 'virtual' IP communication. The first aspect is now being discussed with the aid of Figure 1.

The method of the present invention comprises a few important steps. The first one is to register the loT device (100) to the gateway (300). In this instance for example, the registration process can be of storing information of the loT device ( 00) in the gateway (300). A storing element, namely a first device record (301) is presented in the gateway (300) for this purpose. Similar storing element, namely a second device record (401 ) is presented in a virtual IP provider (400), and the said information of the loT device (100) as stored in the first device record (301) is being replicated in the said second device record (401). The information of the loT device (100) can be of any information that can lead to the identification of that particular loT device (100), for example the physical address of the loT device. The second step is to create a tunnel (500) with an expiry period between the gateway (300) and the virtual IP provider (400). The creation of the tunnel (500) is actually based on a demand basis. In other words, the tunnel (500) is created only when the IP device (200) wishes to communicate with the loT device (100), or when the loT device (100) wishes to communicate with the IP device (100). In the former case, the IP device (200) states its wish to communicate with the loT device (100) by sending a request message to the virtual IP provider (400), whereas in the latter case, the loT device (100) states its wish to communicate with the IP device (200) by sending a request message to the gateway (300).

In an embodiment of the present invention relating to the tunnel (500) creation, upon receiving the request message, communication managers (302) (402) check whether there is an existing tunnel (500) via the device records (301) (401 ). In the event that there is no existing tunnel (500), the communication managers (302) (402) instruct tunnel creators (303) (403) residing in the virtual IP provider (400) and the gateway (300) to create a tunnel (500) between them, and the device records (301 ) (401) are updated with the change. In the event that there is an existing tunnel (500), the communication managers (302) (402) instruct the tunnel creators (303) (403) residing in the virtual IP provider (400) and the gateway (300) to prolong the expiry period of the existing tunnel (500), and the device records (301) (401) are updated with the change.

Two preferred embodiments of tunnel (500) creation will be discussed here. The first preferred embodiment relates to tunnel (500) creation caused by the desire of the IP device (200) to communicate with the loT device (100). Upon receiving the request message sent by the IP device, a step of checking whether there is an existing tunnel (500) is carried out. For this purpose, an element of second communication manager (402) residing in the virtual IP provider (400) is introduced to implement this particular task, and also other tasks which will be apparent later on. This checking task can be done by having the second communication manager (402) to directly detect the existence of an existing tunnel (500), or through the second device record (401). In the event that there is no existing tunnel (500), the second communication manager (402) instructs a second tunnel creator (403) residing in the virtual IP provider (400) and a first tunnel creator (303) residing in the gateway (300) to create a tunnel (500), bridging the communication gap between the gateway (300) and the virtual IP provider (400). Soon after the tunnel (500) creation, the second device record (401 ) will be updated with the change, specifically to store the information of the tunnel (500) including its expiry period. In the event that there is an existing tunnel (500), the second communication manager (402) instructs the second tunnel creator (403) and the first tunnel creator (303) to prolong, renew, or extend the expiry period of this particular existing tunnel (500). Soon after the extension, the second device record (401 ) will be updated with the change, specifically to store the information of the existing tunnel (500) including its prolonged, renewed, or extended expiry period. The second preferred embodiment relates to tunnel (500) creation caused by the desire of the loT device (100) to communicate with the IP device (200). Upon receiving the request message sent by loT device, a step of checking whether there is an existing tunnel (500) is carried out. For this purpose, an element of first communication manager (302) residing in the gateway (300) is introduced to implement this particular task, and also other tasks which will be apparent later on. This checking task can be done by having the first communication manager (302) to directly detect the existence of an existing tunnel (500), or through the first device record (301). In the event that there is no existing tunnel (500), the first communication manager (302) instructs a first tunnel creator (303) residing in the gateway (300) and a second tunnel creator (403) residing in the virtual IP provider (400) to create a tunnel (500), bridging the communication gap between the gateway (300) and the virtual IP provider (400). Soon after the tunnel (500) creation, the first device record (301) will be updated with the change, specifically to store the information of the tunnel (500) including its expiry period. In the event that there is an existing tunnel (500), the first communication manager (302) instructs the first tunnel creator (303) and the second tunnel creator (403) to prolong, renew, or extend the expiry period of this particular existing tunnel (500). Soon after the extension, the first device record (301) will be updated with the change, specifically to store the information of the existing tunnel (500) including its prolonged, renewed, or extended expiry period.

The third step is to allocate and link a virtual IP address to the loT device (100) for a predetermined time. This task is mainly carried out by the second communication manager (402) residing in the virtual IP provider (400), and the virtual IP address is selected from an IP address pool (404). The allocation of virtual IP address is actually based on a demand basis. In other words, the allocation is carried out only when the IP device (200) wishes to communicate with the loT device (100), or when the loT device (100) wishes to communicate with the IP device (200). In the former case, the IP device (200) states its wish to communicate with the loT device (100) by sending a request message to the virtual IP provider (400), whereas in the latter case, the loT device (100) states its wish to communicate with the IP device (200) by sending a request message to the gateway (300).

Two preferred embodiments of virtual IP address allocation will be discussed here. The first preferred embodiment relates to virtual IP address allocation caused by the desire of the IP device (200) to communicate with the loT device (100). Prior to allocating and linking the loT device (100) with the virtual IP address, a step of checking whether there is an existing virtual IP address that is linked to the loT device (100) is carried out. The element of second communication manager (402) residing in the virtual IP provider (400) as introduced above is also designed to implement this particular task, and it can be done by having the second communication manager (402) to directly detect the existence of an existing virtual IP address that is linked to the loT device (100), or through the second device record (401). In the event that there is no existing virtual IP address that has been allocated and linked to the loT device (100), the second communication manager (402) selects a virtual IP address from the IP address pool (404), and allocates and links the same to the loT device (100). Soon after the virtual IP address allocation, the second device record (401 ) will be updated with the change, specifically to store the information of the newly allocated virtual IP address that is linked to the loT device (100) and its predetermined time. In the event that there is an existing virtual IP address that has already been allocated and linked to the loT device (100), the second communication manager (402) prolongs, or extends the predetermined time of the existing virtual IP address that is linked to the loT device (100). Soon after the extension, the second device record (401) will be updated with the change, specifically to store the information of the existing virtual IP address that is allocated and linked to the loT device (100) and its prolonged or extended predetermined time.

The second preferred embodiment relates to virtual IP address allocation caused by the desire of the loT device (100) to communicate with the IP device (200). Prior to allocating and linking the loT device (100) with the virtual IP address, a step of checking whether there is an existing virtual IP address that is linked to the loT device (100) is carried out. The element of first communication manager (302) residing in the gateway (300) as introduced above is also designed to implement this particular task, and it can be done by having the first communication manager (302) to directly detect the existence of an existing virtual IP address that is linked to the loT device (100), or through the first device record (301). In the event that there is no existing virtual IP address that has been allocated and linked to the loT device (100), the first communication manager (302) requests the second communication manager (402) residing in the virtual IP provider (400) to select a virtual IP address from the IP address pool (404), and allocate and link the same to the loT device (100). Soon after the virtual IP address allocation, the first device record (301) will be updated with the change, specifically to store the information of the newly allocated virtual IP address that is linked to the loT device (100) and its predetermined time. In the event that there is an existing virtual IP address that has already been allocated and linked to the loT device (100), the first communication manager (302) prolongs, or extends the predetermined time of the existing virtual IP address that is linked to the loT device (100). Soon after the extension, the first device record (301) will be updated with the change, specifically to store the information of the existing virtual IP address that is allocated and linked to the loT device (100) and its prolonged or extended predetermined time.

Soon after the tunnel (500) has been successfully created and the virtual IP address has been successfully allocated and linked to the loT device (100), at least one of the IP device (200) and the loT device (100) is being informed of the same. At this point, the tunnel is ready to be utilized for transmission of packets between the IP device (200) and the loT device (100) via the gateway (300) and the virtual IP provider (400).

The IP device (200) and the loT device (100) are able now able to communicate with each other by sending a packet to each other, the said packet includes the virtual IP address that is now linked to and serves as the identity of the loT device (100), said virtual IP address enables the packet to be transmitted to the correct recipient.

Two preferred embodiments of packet transmission will be discussed here.

The first preferred embodiment relates to packet transmission from the IP device (200) to the loT device (100). First, the IP device (200) sends a packet including the virtual IP address that is allocated and linked to the loT device (100) to the second communication manager (402) residing in the virtual IP provider (400). In a sense, the virtual IP address provides an identity to the packet so that the packet is able to reach the final destination correctly, which is the loT device (100) that is now identifiable through the said virtual IP address. Next, the second communication manager (402) encapsulates the packet including the said virtual IP address, and send it to the first communication manager (302) residing in the gateway (300). This transmission from the second communication manager (402) to the first communication manager (302) is done through the created tunnel (500). Once the first communication manager (302) receives the encapsulated packet, it (302) then proceed to de-capsulate the encapsulated packet, retrieve the virtual IP address, and send the packet to the correct loT device (100) based on the virtual IP address that is allocated and linked to that particular loT device (100). The packet transmission from the first communication manager (302) to the loT device (100) is done by using the loT device's native communication, which may be radio-frequency identification (RFID), electronic product code (EPC) tag, or the like.

The second preferred embodiment relates to packet transmission from the loT device (100) to the IP device (200). First, the loT device (100) sends a packet including its virtual IP address to the first communication manager (302) residing in the gateway (300). In a sense, the virtual IP address provides an identity to the packet so that the IP device (200) will know the origin of the packet. The packet transmission from the loT device (100) to the first communication manager (302) is done by using the loT device's native communication, which may be radio-frequency identification (RFID), electronic product code (EPC) tag, or the like. Next, the first communication manager (302) encapsulates the packet including the said virtual IP address, and send it to the second communication manager (402) residing in the virtual IP provider (400). This transmission from the first communication manager (302) to the second communication manager (402) is done through the created tunnel (500). Once the second communication manager (402) receives the encapsulated packet, it (402) then proceed to de- capsulate the encapsulated packet, retrieve the virtual IP address, and send the packet to the IP device (200), informing the IP device (200) that the packet is originated from the loT device (100) that is linked to the retrieved virtual IP address. The expiry period of the tunnel (500) will now be discussed. As described throughout the whole document, the tunnel (500) is created with an expiry period. Upon the expiration of the expiry period, and if the expiry period is not prolonged, renewed, or extended, the tunnel (500) is then being removed, thus the link between the gateway (300) and the virtual IP provider (400) is abolished. Consequently, the first device record (301) or the second device record (401) will be updated with the change, specifically to remove any information that is related to the tunnel (500). The predetermined time of virtual IP address allocation will now be discussed. As described throughout the whole document, the loT device (100) is allocated and linked with a virtual IP address for a predetermined time. Upon the expiration of the predetermined time, and if the predetermined time is not prolonged, or extended, the virtual IP address is removed and unlinked from the loT device (100), and returned to the IP address pool (404). Consequently, the first device record (301) or the second device record (401) will be updated with the change, specifically to remove any information that is related to the virtual IP address.

We now will further discuss on the first device record (301) and the second device record (401). From the above, it can be seen that many changes are made and recorded in either the first device record (301 ) or the second device record (401). It is therefore very important to make sure that the records in both the device records (301) (401) are the same. Hence, the method is designed in such a way that a sync process will take place whenever there is a change made to either one of the device records (301) (401), ensuring that the device records (301) (401) are always updating each other with respect of changes and the records in both the device records (301 ) (401) are always the same. The changes mentioned herein may include changes made to the information of the loT device (100), the expiry period of the tunnel (500), and the virtual IP address that is allocated to the loT device (100) and its predetermined time, etc.

The second aspect is now being discussed with the aid of Figure 1.

In general, the system of the present invention comprises a gateway (300) that is connected to an loT device (100), forming a personal area network that is not capable of IP communication, and a virtual IP provider (400) that is connected to an IP device (200), capable of IP communication.

Further, the above-mentioned gateway (300) comprises other elements which are identified as a first device record (301), a first communication manager (302), and a first tunnel creator (303). Similarly, the above-mentioned virtual IP provider (400) comprises other elements which are identified as a second device record

(401) , a second communication manager (402), a second tunnel creator (403), and an IP address pool (404). The first device record (301) and the second device record (401) are used to store and record any information that is related to the loT device (100) and the tunnel (500), for examples the physical address of the loT device (100), an expiry period of a tunnel (500), a virtual IP address that is allocated and linked to the loT device (100) and its predetermined time, etc. Many changes are made and recorded in either the first device record (301) or the second device record

(401) . It is therefore very important to make sure that the records in both the device records (301) (401) are the same. Hence, the device records (301) (401) are designed in such a way that a sync process will take place whenever there is a change made to either one of them (301) (401). This ensures that the device records (301) (401) are always updating each other with respect of changes and the records in both the device records (301) (401) are always the same. The changes mentioned herein may include changes made to the information of the loT device (100), the expiry period of the tunnel (500), and the virtual IP address that is allocated to the loT device (100) and its predetermined time, etc.

The first communication manager (302) and the second communication manager

(402) are used to manage the creation of a tunnel with an expiry period between the gateway (300) and the virtual IP provider (400). The detailed method of tunnel creation and how the communication managers (302) (402) manage the process is as described in the first aspect of the present invention.

Further, the first communication manager (302) and the second communication manager (402) are also used to manage the allocation of a virtual IP address to the loT device (100) for a predetermined time. The detailed method of virtual IP address allocation and how the communication managers (302) (402) manage the process is as described in the first aspect of the present invention. Furthermore, the first communication manager (302) and the second communication manager (402) are also used to receive, process including encapsulate and de-capsulate, and send packets between the loT device (100) and the IP device (200). Specifically, the first communication manager (302) manages packet transmission to and from the loT device (100) and the gateway (300), whereas the second communication manager (402) manages packet transmission to and from the IP device (200) and the virtual IP provider (400).

Two preferred embodiments of packet transmission between the loT device (100) and the IP device (200) will be discussed here.

The second preferred embodiment relates to packet transmission from the loT device (100) to the IP device (200). First, the loT device (100) sends a packet including its virtual IP address to the first communication manager (302) residing in the gateway (300). In a sense, the virtual IP address provides an identity to the packet so that the IP device (200) will know the origin of the packet. The packet transmission from the loT device (100) to the first communication manager (302) is done by using the loT device's native communication, which may be radio-frequency identification (RFID), electronic product code (EPC) tag, or the like. Next, the first communication manager (302) encapsulates the packet including the said virtual IP address, and send it to the second communication manager (402) residing in the virtual IP provider (400). This transmission from the first communication manager (302) to the second communication manager (402) is done through the created tunnel (500). Once the second communication manager (402) receives the encapsulated packet, it (402) then proceed to de- capsulate the encapsulated packet, retrieve the virtual IP address, and send the packet to the IP device (200), informing the IP device (200) that the packet is originated from the loT device (100) that is linked to the retrieved virtual IP address.

The first tunnel creator (303) and the second tunnel creator (403) are used to create the tunnel (500) as instructed by the first communication manager (302) and the second communication manager (402). Moreover, the tunnel creators (303) (403) also play the role of maintaining the availability of the tunnel (500) for packet transmission by the first communication manager (302) and the second communication manager (402) according to the expiry period. The IP address pool (404) comprises a plurality of unused virtual IP addresses readily to be selected, allocated, and linked by the second communication manager (402) to the loT device (100).

Claims

A method for enabling an IP communication between an IP device (200) that is capable of IP communication and at least one Internet of Things (loT) device (100) that is not capable of IP communication by providing virtual IP services to the loT device (100), characterized in that, the method comprises the steps of:

a) registering the loT device (100) to a gateway (300) by having information of the loT device (100) stored in a first device record (301) residing in the gateway (300) and replicated in a second device record (401) residing in a virtual IP provider (400);

b) creating a tunnel (500) with an expiry period between the gateway (300) and the virtual IP provider (400), and selecting a virtual IP address from an IP address pool (404) and allocating the virtual IP address to the loT device (100) for a predetermined time upon receiving a request message for communication with the loT device (100) from the IP device (200) to the virtual IP provider (400) or a request message for communication with the IP device (200) from the loT device (100) to the gateway (300); and

c) informing at least one of the IP device (200) and the loT device (100) that the loT device (100) has been allocated and linked with the virtual IP address and the tunnel (500) has been created;

wherein the IP device (200) and the loT device (100) are now able to communicate with each other by sending a packet to each other, the said packet includes the virtual IP address that is now linked to and serves as the identity of the loT device (100), said virtual IP address enables the packet to be transmitted to the correct recipient.

2) A method in accordance with claim 1 , wherein the IP device (200) and the loT device (100) communicates with each other by sending a packet to each other, the said packet includes the virtual IP address that is now linked to and serves as the identity of the loT device (100), said virtual IP address enables the packet to be transmitted to the correct recipient, a) in the event that the IP device (200) initiates the communication with the loT device (100), the method further comprises the steps of sending the packet including the virtual IP address that is linked to the loT device (100) to a second communication manager (402) residing in the virtual IP provider (400), which in turn encapsulates the packet, and sends the encapsulated packet to a first communication manager (302) residing in the gateway (300) via the tunnel (500), where upon the arrival of the encapsulated packet at the gateway (300), the first communication manager (302) de- capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the loT device (100) that is linked to the virtual IP address by using the loT device's native communication;

b) in the event that the loT device (100) initiates the communication with the IP device (200), the method further comprises the steps of sending the packet including the virtual IP address that is linked to the loT device (100) to the first communication manager (302) residing in the gateway (300) by using its native communication, which in turn encapsulates the packet, and sends the encapsulated packet to the second communication manager (402) residing in the virtual IP provider (400) via the tunnel (500), where upon arrival of the encapsulated packet at the virtual IP provider (400), the second communication manager (402) de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the IP device (200), informing the IP device (200) that the packet is originated from the loT device (100) that is linked to the virtual IP address.

A method in accordance with claim 1 , wherein the first device record (301) and the second device record (401) are always in sync to update each other of any changes made to either the first device record (301) or the second device record (401), the changes comprise changes made to the information of the loT device (100), the expiry period of the tunnel (500), and the virtual IP address that is allocated to the loT device (100) and its predetermined time.

A method in accordance with claim 1 , wherein the step of creating a tunnel (500) with an expiry period between the gateway (300) and the virtual IP provider (400) further comprises the step of checking whether there is an existing tunnel (500) by the communication managers (302)

(402) via the device records (301) (401);

wherein in the event that there is no existing tunnel (500), the communication managers (302) (402) instruct tunnel creators (303) (403) residing in the virtual IP provider (400) and the gateway (300) to create a tunnel (500) between them, and the device records (301) (401) are updated with the change;

wherein in the event that there is an existing tunnel (500), the communication managers (302) (402) instruct the tunnel creators (303)

(403) residing in the virtual IP provider (400) and the gateway (300) to prolong the expiry period of the existing tunnel (500), and the device records (301) (401) are updated with the change.

A method in accordance with claim 1 , wherein the step of allocating a virtual IP address to the loT device (100) for a predetermined time further comprises the step of checking whether there is an existing virtual IP address that is linked to the loT device (100) by the second communication manager (402) residing in the virtual IP provider (400) via the second device record (401);

wherein in the event that there is no existing virtual IP address that is linked to the loT device (100), the second communication manager (402) allocates the loT device (100) with a virtual IP address, and the second device record (401) is updated with the change;

wherein in the event that there is an existing virtual IP address that is linked to the loT device (100), the second communication manager (402) prolongs the predetermined time of the existing virtual IP address that is linked to the loT device (100), and the second device record (401) is updated with the change.

A method in accordance with claim 1 , wherein the step of providing a virtual IP address to the loT device (100) for a predetermined time further comprises the step of checking whether there is an existing virtual IP address that is linked to the loT device (100) by the first communication manager (302) residing in the gateway (300) via the first device record (301);

wherein in the event that there is no existing virtual IP address that is linked to the loT device (100), the first communication manager (302) request the second communication manager (402) residing in the virtual IP provider (400) to allocate the loT device (100) with a virtual IP address, and the first device record (301) is updated with the change;

wherein in the event that there is an existing virtual IP address that is linked to the loT device (100), the first communication manager (302) prolongs the predetermined time of the existing virtual IP address that is linked to the loT device (100), and the first device record (301) is updated with the change.

A method in accordance with claim 1 further comprises the steps of:

a) removing the tunnel (500) when the expiry period is expired;

b) removing the virtual IP address that is allocated and linked to the loT device (100) when the predetermined time is expired; and c) updating either the first device record (301 ) or the second device record (401) with the changes.

A system for enabling an IP communication between an IP device (200) that is capable of IP communication and at least one Internet of Things (loT) device (100) that is not capable of IP communication by providing virtual IP services to the loT device (100), the system comprises:

a) a gateway (300) that is connected to the loT device (100), forming a personal area network that is not capable of IP communication; b) a virtual IP provider (400) that is connected to the IP device (200), capable of IP communication;

characterized in that:

the gateway (300) comprises:

i) a first device record (301 ) for storing information of the loT device

(100), an expiry period of a tunnel (500), and a virtual IP address that is allocated and linked to the loT device (100) and its predetermined time;

ii) a first communication manager (302) for managing the creation of a tunnel (500) with an expiry period between the gateway (300) and the virtual IP provider (400), managing the allocation of a virtual IP address to the loT device (100) for a predetermined time, and receiving, processing including encapsulating and de- capsulating, and sending packets between the loT device (100) and the virtual IP provider (400),

iii) a first tunnel creator (303) for creating the tunnel (500) as instructed by the first communication manager (302) and maintaining the tunnel (500) according to its expiry period;

the virtual IP provider (400) comprises:

a) a second device record (401) for storing information of the loT device (100), an expiry period of a tunnel (500), and a virtual IP address that is allocated and linked to the loT device (100) and its predetermined time;

b) a second communication manager (402) for managing the creation of a tunnel (500) with an expiry period between the gateway (300) and the virtual IP provider (400), managing the allocation of a virtual IP address to the loT device (100) for a predetermined time, and receiving, processing including encapsulating and de-capsulating, and sending packets between the IP device (200) and the gateway (300); c) a second tunnel creator (403) for creating the tunnel (500) as instructed by the second communication manager (402) and maintaining the tunnel (500) according to its expiry period; and

d) an IP address pool (404) comprising a plurality of unused virtual IP addresses readily to be allocated to the loT device (100);

wherein the IP device (200) and the loT device (100) communicates with each other by sending a packet to each other, the said packet includes the virtual IP address that is now linked to and serves as the identity of the loT device (100), said virtual IP address enables the packet to be transmitted to the correct recipient.

A system in accordance with claim 8, wherein in the event that the IP device (200) initiates the communication with the loT device (100), the IP device (200) sends the packet including the virtual IP address that is linked to the loT device (100) to a second communication manager (402) residing in the virtual IP provider (400), which in turn encapsulates the packet, and sends the encapsulated packet to a first communication manager (302) residing in the gateway (300) via the tunnel (500), where upon the arrival of the encapsulated packet at the gateway (300), the first communication manager (302) de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the loT device (100) that is linked to the virtual IP address by using the loT device's native communication; and

wherein in the event that the loT device (100) initiates the communication with the IP device (200), the loT device (100) sends the packet including the virtual IP address that is linked to the loT device (100) to the first communication manager (302) residing in the gateway (300) by using its native communication, which in turn encapsulates the packet, and sends the encapsulated packet to the second communication manager (402) residing in the virtual IP provider (400) via the tunnel (500), where upon arrival of the encapsulated packet at the virtual IP provider (400), the second communication manager (402) de-capsulates the encapsulated packet, retrieves the virtual IP address, and sends the packet to the IP device (200), informing the IP device (200) that the packet is originated from the loT device (100) that is linked to the virtual IP address.

10) A system in accordance with claim 8, wherein the first device record (301) and the second device record (401) are always in sync to update each other of any changes made to either the first device record (301) or the second device record (401), the changes comprise changes made to the information of the loT device (100), the expiry period of the tunnel (500), and the virtual IP address that is allocated to the loT device (100) and its predetermined time.