, pp.97-108 http://dx.doi.org/10.14257/ijseia.2014.8.6.08 Designing and Embodiment of Software that Creates Middle Ware for Resource Management in Embedded System Suk Hwan Moon and Cheol sick Lee Department of Computer Information, Cheju halla University, Jeju Special Self-Governing Province, Republic of Korea Department of Computer Information, Cheju halla University, Jeju Special Self-Governing Province, Republic of Korea msh@chu.ac.kr, sigma@chu.ac.kr Abstract With high performance of hardware and development of diverse devices such as sensors, the embedded system is required to satisfy instant and diversified demands. Embedded middle ware should perform a mediating role of continuous management for productivity of complex embedded system, recombination of device, and provision of convenience in management by analyzing functions of existing system and more effectively handling new functions. To do so in this paper, composition and handling procedure of remote embedded system are schematized and a middle ware framework and dynamic module reuse method appropriate for small embedded system are designed, proposing a method for embodiment of software for reuse of resources and remote management. Keywords: Embedded Middleware, Embedded System Management, Embedded System reusability, Resource Management 1. Introduction Embedded system is currently applied to most fields including home, automobile, office, building, and plant. Especially, while there is no functional difference in embedded system developed for special purposes, the system is developed for each purpose without consideration on the use of reusable devices, due to convenience in maintenance. Currently, many companies developing embedded systems are making improvement on overlapping or similar functions through conversion from hardware process to software technology. Embedded software must be able to perform complex functions in diverse fields with basic functions such as real-time processing, high reliability, optimization technology, application of specific system, and network and multimedia handling functions [7]. Embedded OS technology is developing quickly with the focus on light weight, low power, fast booting, and high reliability. With recent appearance of diverse devices based on sensor technology, embedded software requires a flexible and expandable platform structure. [1, 2] For this reason, design of embedded systems has become extremely complex with very low productivity. Studies on recycling of existing system resources are actively conducted nowadays, but there are limits to the adapter method which simply adds devices and modifies software on the existing system [3]. Accordingly in this paper, a middle ware framework for remote analysis and management of basic embedded system structure is presented to easily examine the interface between embedded hardware and software, and to reassign or reuse resources. This framework provides an additional processing module in addition to the reusable processing module in ISSN:1738-9984 IJSEIA Copyright c 2014 SERSC
which the functional module, added by the middle ware framework according to input and output methods or information of each module, is connected to input, processing and output modules configured as a unit of reusable functional module. In addition, an embedded system and algorithm in which the additional processing module is included in the basic module provided by the above middle ware are suggested. In addition, a method for embodiment of development tool to analyze functional module information of existing embedded system and create intuitive resource structure is designed and experimented with a work tool, which can use UI to easily reconfigure the interface for other uses upon addition of function or change of device in embedded system. 2. Configuration of Middle Ware and Designing of Framework for Management of Embedded System 2.1. System Structure for Management of Embedded System Figure 1. Composition of Remotely Managed Embedded System One or more embedded systems can be attached to an area depending on the system characteristics and size of service area. In case of multiple systems, systems installed may have identical functions or completely different functions. As shown in Figure 1, the structure in this paper was designed (1) so that embedded middle ware is mounted in a terminal in the embedded system service area, and functions that do not require OS or middle ware transfer data through communication with the middle ware terminal and receiving commands from the terminal. This is similar to the concept of sink node in USN, and it is a method that reduces overall system cost by removing unnecessary system functions and optimizing the system. In the service area, embedded system mounted with middle ware receives commands from the management server through continuous communication based on wired or wireless network, processes data transferred from subordinate device, and transmits the processed data to the server (2). Data provided in each embedded system service area (sensor data, image data, status information, etc.) are saved in the database (3). Data saved in the database can be used on the website through web server to monitor the area and perform commands according to schedule (4). The system administrator is mounted with software that assigns / reassigns profile and functional module of embedded system installed in each area. It can examine remote middle ware resources and update functional modules. 98 Copyright c 2014 SERSC
Figure 2. Middle Ware Processing Block Diagram Embedded middle ware is largely divided into input, processing and output parts. Input part transfers sensor, image and electric signals from sensors and devices on the system to middle ware. Processing part performs data processing works such as operation of actuator, checking of threshold, data filtering, and scheduling with timer and dynamically allocates modules at the system core to process events. Figure 2 is a figure showing composition of middle ware processing that includes automatic update and management modules for remote management. 2.2. System Middle Ware Design for Management of Embedded System Embedded middle ware in general is developed for special purposes by minimizing hardware and software resources. However, this does not mean that optimized hardware or software can only perform originally intended functions. In other words, many embedded systems can mount additional devices and change functions with increased performance of hardware, increased communication speed and improved functions of embedded OS. Compressive software made for special purposes can be split into modules for reuse in necessary parts. This paper designs a system for easy change of functions by converting general embedded system resources to modules and software functions to components, suggesting an intuitive user tool with functional modules separated for ultimate development and management. In this paper, a middle ware framework is proposed to increase reusability of embedded system resources, replace processing logic and allow convenient configuration of embedded system. A middle ware creation tool is developed for development and management of the framework. Copyright c 2014SERSC 99
2.1.1. Method of Increasing Usability: As performance of processor is limited, diversity provided by existing middle ware scripts can result in processing cost of having to parse the script every time. Modules are mounted by functional unit to configure an embedded system. 2.1.2. Method of Replacing Processing Logic: While existing middle wares handle diverse external interfaces using adapter module, they allow processing logic to be expanded by unit of module. For instance, if there is an embedded system that transfers and saves images from USB camera through a module which saves image information on the hard disk, the system can be made so that it only saves the image when human face is recognized by additionally developing a module that recognizes face, transmitting image output from the module to input of face recognition module, analyzing the image received to check whether there is a face, and creating an output event to save the image on the hard disk when a face exists. If a module recognizes license plate numbers, the embedded system can recognize license plate number instead of human face by removing face recognition module and adding license plate number recognition module. 2.1.3. Convenient Configuration of Embedded System: For management of embedded system, embedded system is configured on a laptop or PC using Wi-Fi or Bluetooth. As for the configuration method, embedded system information and module information are received to assign the wanted modules using GUI and to appropriately connect modules. 2.1.4. Middle Ware Framework: A framework is offered to provide background information of embedded system and middle ware for a third developer to develop new modules and mount them on the embedded system. 2.3. System Middle Ware Framework for Management of Embedded System General module reuse is operated according to generalization rule by generalizing the interface of unit module, and flexibility is extremely reduced because of limitation in the logic caused by generalization. Therefore in this paper, only the minimal part needed for system operation is generalized. For the remaining part, middle ware framework was designed using reflection technique to dynamically analyze the module, verify connection of each module, and set dynamic connection. Two aspects need to be considered when designing an embedded middle ware. One is to consider the environment in which the system is installed, and the other is to assume that type and number of sensors can differ. That is, environment can differ depending on the place in which the embedded system is installed, and the middle ware must accommodate for changes in type and number of sensors. It must be designed so that added sensor device data can be handled as identical to existing sensor environment. This can be embodied based on plug-in architecture by creating functional module of component. This means that when a new device is added to an existing embedded system, the middle ware component is renewed according to function of the added device and the middle ware dynamically links the corresponding component. 100 Copyright c 2014 SERSC
Figure 3. Embedded Middle Ware Framework Figure 3 is a middle ware framework for reuse of dynamic module. It has various hardware devices, driver to manage such devices, and middle ware located on top of embedded system OS. Middle ware includes reusable modules and a framework. Reusable modules are classified into input modules that receive input from various external devices, processing modules to process logics, and output modules to send data out to external devices. The middle ware framework consists of a manager that manages diverse information, provider that offers background information on the embedded system, and middle ware core used to manage all components. Figure 4. Middle Ware Framework for Reuse of Dynamic Module Embedded middle ware framework can use communication devices (Bluetooth, USB, Wi- Fi, CDMA, etc.,) of the embedded system to remotely reconfigure one or more embedded system middle wares on a remote terminal (mobile, laptop, computer, etc.,). Since module unit control and embedded system status can be checked here, it offers the grounds for easier management of complex system. Copyright c 2014SERSC 101
Figure 4 is a middle ware framework used for data processing, communication with remote server and management to dynamically reused modules and handle services by virtualizing a system with general functions. Embedded middle ware provides the grounds for configuration of modules and convenient management of modules. It provides a framework for processing of base functions (queue management, thread management, scheduling, device management, etc.) and information (memory, storage device information, etc.) when a third developer wishes to develop a unit module and mount it on the embedded system. Contents manager manages all contents instances. Event manager manages contents instance events by registering or removing them from managers. Resource manager manages resource information of the middle ware. Connection manager provides basic functions for connection such as serial port connection, Bluetooth connection and socket connection. File manager offers management on files in the middle ware. Queue manager provides queue management that require buffer. Thread manager provides thread management for processes that require thread, and time manager manages Time Manager instances which generate an event when regular event or scheduling event is necessary. Sound manager provides sound source output function using sound card on the embedded system. Location manager provides locational information of the embedded system when GPS is mounted on the embedded system. Log monitor monitors log output information of content instances, and log data are processed by the provider. State monitor monitors the change in status of content instances. Error monitor monitors errors that occur in content instances. All modules, controllers, managers, monitors, providers and modules needed for operation of the middle ware are managed and operated on the middle ware as a unit called content. The purpose of clustering them as a content is to offer independence to developers of unit modules and provide a minimal guideline for operation of the middle ware system. 2.4. Embedded Middle Ware Creation Software Expansion of the embedded system can be made easier through unit module configuration, and time and cost needed for development can be reduced and unit modules can be developed easily by reusing unit modules. This allows for reduced time and cost for unit module development as background function and information are provided to the embedded system through the middle ware framework. In addition, this is useful for development of embedded system management tool, which allows easy configuration and convenient management of the embedded middle ware. The method of configuring unit module is easily understood based on GUI. Figure 5 is a UI for management of embedded system. System configuration can be understood at a glance when the corresponding system devices are connected remotely or locally. The embedded system with new functions can be created through reuse of existing modules based on reassignment of input, processing and output module or modification of existing modules. In other words, the system can include a functional module with a manager element which manages one or more of contents management, thread management, event management, time management, file management, queue management, resource management and sound management, or a monitor element that monitors one or more among log data, status change and error occurring in the above middle ware. 102 Copyright c 2014 SERSC
Figure 5. Embedded System Management for Remote Control Software UI In Figure 5, shows the list of reusable modules on the embedded system and shows the list of framework modules that can be used on the middle ware. is an actual work window. When a module needed for operation is selected on, the module instance is registered on the work window of. When a module instance is selected, module information is displayed on the window of. Module information includes basic information of module, method information and event information. Information about method and event of module uses reflection technique of.net framework or Java. Figure 6. Connection of Interface between Modules When module 1 is selected for connection, the event list is displayed underneath. When the event to be connected is selected and moved to the wanted module using drag-and-drop, methods that correspond to the parameter type of the event are displayed. The two modules are connected by selecting the method. Copyright c 2014SERSC 103
Figure 7. Interface between Dynamic Methods shows the window for log of events and errors occurring on the middle ware. displays basic information of module, method and event information, and connection among modules. is a module control window to selectively start or stop modules, and allows the user to select methods and events on module information to check the current role of the module. Figure 8. Process Logic to Analyze, Dynamically Load, and Register unit Module On Middle Ware (Left), Procedure for Connection between Modules (Right) Figure 8 shows the processing logic for creation of a dynamic module, which includes the procedure for analyzing the embedded system resources, dynamically loading them, and registering them on middle ware, as well as reuse or reassignment of each module by middle ware and management software. 3. Method of Reusing Dynamic Modules in Embedded Middle Ware To reuse embedded system resources and add embedded hardware device or function, the middle ware needs to first analyze current device information. For this, the middle ware loads dynamic module based on plug-in and registers the module with the module manager to share or reassign the module on embedded software. 104 Copyright c 2014 SERSC
Figure 9. UI for Reassignment and Management of Embedded Middle Ware Resources Figure 9 shows a UI that analyzes existing embedded system resources to display interface among resources on the screen. This software was developed / experimented using.net CF on Windows CE. To mount new functional module on the embedded system for easier configuration of an improved embedded system, first, information of multiple modules composed of reusable functional module unit is obtained from the embedded system through the middle ware framework. These multiple modules are classifies into one or more of input, processing and output modules and displayed on the work window of the user device. User equipment include but does not need to be limited to mobile, laptop and PC attached with a communication device for management of the embedded system. Functional modules can be displayed on user equipment using GUI method. When a signal is entered on user equipment to select one of reusable multiple modules and additional modules, input method and output event information of the selected module are displayed. As such, with consideration on input method and output event information of each module, the user connects two or more modules among the above reusable multiple modules and additional modules through the middle ware framework and appropriately assigns modules to configure an improved embedded system. Figure 10. Addition and Setting of New Module (Processing Function) (Left), Configuration of Embedded System with New Functions and Reused Resources (Right) Copyright c 2014SERSC 105
As shown in Figure 9, this paper analyzed modules of the current system using reflection technique, added processing modules specifying processing data of the added devices, configured a logic to create and handle new processing events through reuse of existing modules, performed an experiment for change to a system with new functions(figure 10.). Since such development tool includes basic modules for embedded system resources (timer, on/off control, etc.), available modules are gradually increased with development of more applications. This results in gradual reduction in time and cost needed for further application. 4. Conclusion System recycling and expansion based on the reuse of embedded system resources proposed in this paper were applied to a system with embedded operating system and profile storage memory. Accordingly, configuration of operating system base and framework design were proposed. As a result, increase in embedded systems subject to analysis allows diverse modules to be recorded and managed, and recorded module information can be continuously reused in the future. Also, the analyzed embedded system configuration can be visualized by management software to conveniently reassign or add resources according to dynamic processing procedure. Moreover, middle ware was designed based on service-oriented architecture for attachment on end terminal and remote management. The compositions of remote embedded system and middle ware processing presented in this paper were designed for easy management of devices with diverse functions in specific fields and other embedded system in different fields. Embedded system resource reuse and management software based on reflection technique reduces the generalization process of modules compared to the component method, resulting in slight increase of programming complexity. However in the end, the system can have quick response and time and cost of system design and manufacture can be saved by configuring a system appropriate for diverse fields using high performance embedded hardware and by allowing efficient management with development tool that takes distributed environment into account. Future plan is to study a technique for reducing the complexity of programming, which appeared as a disadvantage of the system proposed in this study, by adding a middle ware function for conversion of common protocol for various devices based on further segmentation of embedded system resources. Module arrangement will be optimized with application of learning ability through process of inference. References [1] J. P. Loyall, Emerging trends in adaptive middleware and its application to distributed real-time embedded systems, Lecture Notes in Computer Science, vol. 2855, (2003), pp. 20-34. [2] J. Peng, J. D. Liu and T. Yang, Research and implementation of the real-time middleware in open system, Lecture Notes in Computer Science, vol. 3032, (2004), pp. 803-808. [3] C.-B. Park, Y.-D. You and H. Choi, The Design of Dynamic Reconfiguration of Software Platform for Embedded Systems, Korea Computer Congress 2005, vol. 32, no. 1(A), (2005). [4] C. Jin Kim, S. Hee Lee and E. Sook Cho, A Reusability Enhancement Technique of Embedded System using Plug-In Method, Journal of the Korea Society for Simulation, vol. 18, no. 4, (2009), pp. 81-94. [5] M. sun Kom, S. Won Lee, C.-H. Lee, H. Choi and K. seok Cho, Design and Performance Analysis of the Interface Middleware for Embedded Systems, Journal of Computing Science and Engineering, vol. 14, no. 1, (2008), pp. 52-62. [6] J. Axel, Modeling Embedded System and SOCs, Mogan Kaufmann, (2004). [7] C. Jin Kim and E. Sook Cho, A Design of Dynamic Meta-model for Reusable Framework of Embedded Sytem, Journal of the Korea Information Processing Society, vol. 15-D, no. 6, no. 4, (2008), pp. 815-824. [8] H. Teja Sukmana, J.-B. Lee, K.-W. Rim, Y.-S. Hwang, Y.-J. Kim and S.-S Ahn, Embedded System Integrated Prototyping Mechanism Based on Reusable Component, Journal of the Korea Information Processing Society, vol. 16-A No.3, no. 4, (2009), pp. 199-208. 106 Copyright c 2014 SERSC
[9] S. Hwan Moon and C. Sick Lee, Dynamic Management Software Design in Embedded System using Middle Ware, Advanced Science and Technology Letters, vol. 46-47, (2014), pp. 186-191. [10] H.-C. Son Design and implementation of the method for generation of custom-made embedded middleware, master s dissertation, University of Jeju, (2010). Authors Suk-Hwan Moon, received his Master's degree in Department of Information Engineering from Cheju University at 1997 and earned the ABD in the Department of Computer Engineering from Joongang University at 2005. He is currently an Associate Professor at Department of Computer Information, Cheju halla University. His research interests include embedded system, computer vision, multimedia contents processing, sensor networking. Cheol-Sick Lee, He obtained master s degree in the Department of Computer Engineering at Jeju National University in 2009 and completed doctoral course in 2013. He is currently an adjunct professor of Computer Information at Jeju Halla University and CEO of Gaonuri Co., Ltd. Research fields include embedded system, intelligent system, IT convergence and database. Copyright c 2014SERSC 107
108 Copyright c 2014 SERSC