• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.6
• /
• pp.637-647
• /
• 2010

Recent embedded systems are being more complicated due to their hierarchical software architecture including operating systems. The performance of such complicated software architecture could not be well analyzed through separate analysis of each software layer; the combined effect and the interactions among the whole software layers should be considered. In this paper, we show the design and implementation of a performance analysis framework that enables hierarchical analysis of performance of Linux-based embedded systems considering interactions among the software layers. By using the proposed framework, we can obtain useful run-time information about a hierarchical software structure which usually consists of user-defined function layer, library function layer, system call layer, and kernel events layer. Experimental results reveal that the proposed framework could accurately identify the performance bottlenecks with the corresponding software layers during executions of target applications through the accompanying sub-steps of the analysis: the actual execution paths, the execution time of each observed event in each software layer, and the control flows across the software layers.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.11a
• /
• pp.265-267
• /
• 2005

본 논문에서는 무선 랜과의 인터워킹 등 새로운 특징을 갖는 주요 기능들을 추가하기 위한 기반 시스템인 3G Evolution 시스템 개발에 필요한 액세스 시스템 내의 서브 시스템인 RRCS(Radio Resource Control Subsystem)를 구현 및 검증하기 위하여 단말-기지국간 무선 액세스 프로토콜을 형식 기술 언어인 SDL(Specification and Description Language)을 이용해 구현하였다. 여기서 효율적 시스템 설계를 위해 복잡한 각 메시지 처리 함수는 C 언어를 이용해 라이브러리화하고 이를 SDL 시스템 내에서 호출하도록 지원하는 방법을 사용했다.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.29 no.1
• /
• pp.45-55
• /
• 2019

DEX file and share objects (also known as the SO file) are important components that define the behaviors of an Android application. DEX file is implemented in Java code, whereas SO file under ELF file format is implemented in native code(C/C++). The two layers - Java and native can communicate with each other at runtime. Malicious applications have become more and more prevalent in mobile world, they are equipped with different evasion techniques to avoid being detected by anti-malware product. To avoid static analysis, some applications may perform malicious behavior in native code that is difficult to analyze. Existing researches fail to extract the call relationship which includes both Java code and native code, or can not analyze multi-DEX application. In this study, we design and implement a system that effectively extracts the call relationship between Java code and native code by analyzing DEX file and SO file of Android application.

• The Transactions of the Korea Information Processing Society
• /
• v.2 no.4
• /
• pp.487-498
• /
• 1995

For the purpose of the sharing and reusability of software systems in an integrated CASE environment, it is necessary to develope the repository-based integrated software environment. In this paper, we designed and implemented the repository interface between CASE tools and IRDS service interface. We have already implemented the IRDS service interface system according to ANSI IRDS standard in order to develop a repository of an integrated CASE environment. We implemented the repository interface using the CLI(Call Level Interface) method that is composed callable run-time libraries.

• Journal of Korea Multimedia Society
• /
• v.13 no.10
• /
• pp.1514-1524
• /
• 2010

The standard Java class library does not support the platform-dependent features needed by the application. Therefore, the Java application including the platform -dependent features must supplement the required features by invoking native functions using JNI. The native language programmer has to explicitly specify how to connect to various Java objects and later to disconnect from them. In this paper, I suggest a way to avoid these annoying works. The native method in the pure java class can not contain a native code block. By providing a native code block for the native method, it is possible for programmer to write a native code without being aware of JNI. To achieve this, I introduced the native class that is a java class on the native environment, and made it possible to interchange data by placing an arbitrator between the java class and the native class.