Designing Middleware for Internet of Things by Ajit Singh

Author:Ajit Singh [Singh, Ajit]
Language: eng
Format: mobi, epub
Publisher: UNKNOWN
Published: 2020-11-15T16:00:00+00:00

Figure 4.3 Interactions with external entities to provide a Video monitoring application

4.4 Non-functional requirements

The VMS non-functional requirements that we have identified in our interviews have also been addressed in the literature. We identified the following non-functional requirements for the VMS:

.

1. Ease of configuration for admin-user [10] [2]

VMS should be able to connect to different types of cameras, which each can support specific communication protocols and standards. However, to facilitate the configuration of different types of camera, VMS should support a single GUI interface for admin-users to work with different cameras.

2. Facilitate monitoring[2]

VMS should facilitate monitoring by providing both configuration and location transparency for guard. For example, the guard can refer to a location that has to be monitored by using its video service name. For instance, to monitor Hall A, which is covered by camera 1 and camera 2, guard only needs to send the name of the location (Hall A ). VMS is in charge of finding the address and the configuration of the required cameras, which either has been set by an admin-user or already, has a default value in the system.

3. Supporting new types of cameras [13]

VMS has to be able to support different types of camera in different domains. Thus, VMS has to be extendable with minimum changes, and it also needs to allow new cameras to be added to the system.

4. Scalability [10], [13], [2], [35]

The security management platform has to be capable of supporting different numbers of camera. The company VMS as a main part of the security platform is in charge of supporting a large number (more than 1000) of cameras. To support a large scale system, VMS has to be able to integrate with the third-party camera service provider to distribute part of the necessary process.

5. Security and privacy The major security problem of IoT is related to authentication and data integration [34]. To do the authentication, we need data exchange between authentication servers and devices. This makes a problem when an application use passive RFID tags in an IoT-based system, because a passive RFID does not have the capability of handling many communications with an authentication server. This problem has not been solved yet [36].

4.5 Conclusion

In this chapter, we identified both functional and non-functional requirements that should be considered in the design and implementation of a VMS. In order to identify these requirements, we conducted interviews with the technical staff of a commercial company (Nedap). We interviewed the technical staff of the research and development department in order to have a general understanding about both the current and next generation of VMS. We also had interviews with the software architects and developers of the current VMS to collect more information of the system.

Furthermore, we reviewed the literature on middleware for IoT-based systems to identify those requirements that a VMS should be able to support.

In our project, we are going to answer to two of these non-functional requirements: (1) providing ease of configuration for admin-user; (2) providing ease of monitoring for a guard who is as an end-user in VMS.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.