Skip to content
Free planNo credit card requiredStart writing

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 2,660 papers for “system call interface”

System call interface for Asbestos labels

Frey, Clifford A. (Clifford Arthur) · DSpace@MIT (Massachusetts Institute of Technology) · 2005

Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2005.

Cited by 0Open access

An Automatic Voice Call-Response System using Speech Interface

Tsuneyo Sano, Seiichi Wada · IEEJ Transactions on Electronics Information and Systems · 1994

In order to inspect the valid speech interface, we have developed an emergency voice call-response system whereby when a message is spoken into a telephone in the event of an accident or a disaster, the employees wanted are automatically reached and called on to respond to the call. A word recognition algorithm in this system is using a non-linear matching processing technique from the reason that need to carry out same time parallel processing of multiple-line, and recognition object word number is small-vocabulary (32 words). And we have developed a new method whereby computer recognizable standard patterns are generated by interval estimation processing limited small voice data. We were able to identify that validity of speech interface by field testing result.This paper describes about the description of this new method, and validity of speech interface for electric power enterprise.

Cited by 0Open access

attacks: Why the system call API is a bad untrusted rpc interface

Stephen Checkoway, Hovav Shacham · 2013

In recent years, researchers have proposed systems for running trusted code on an untrusted operating system. Protection mech-anisms deployed by such systems keep a malicious kernel from directly manipulating a trusted application’s state. Under such sys-tems, the application and kernel are, conceptually, peers, and the system call API defines an RPC interface between them. We introduce Iago attacks, attacks that a malicious kernel can mount in this model. We show how a carefully chosen sequence of integer return values to Linux system calls can lead a supposedly protected process to act against its interests, and even to undertake arbitrary computation at the malicious kernel’s behest. Iago attacks are evidence that protecting applications from malicious kernels is more difficult than previously realized. 1.

Cited by 0

Software Malicious Behavior Analysis Model based on System Call and Function Interface

Yongkai Fan, Jing Lei, Cong Peng et al. · 2019

Malware issue puzzles software users. Under the development of Internet, software technology has been involved in all parts of life such as Robot Control Software. There have been many methods to detect malicious Android applications. However, most of these are single behavior analysis models. In order to better detect the malicious behavior for more fields, we propose a malicious behavior analysis model based on system call and function interface with machine learning algorithm training. To clear the analysis model, we discuss the reasonable feature selection, data collection and analyze the implementation of static methods, dynamic methods and hybrid methods. In addition, we compare several important algorithm models to get the optimal model. Experimental result shows that our proposed optimal model has a higher accuracy than traditional way.

Cited by 1

A stubless heterogeneous remote procedure call system using multi-option presentation layer interface

Syan-Lin Wu · 1990

The 1980s have witnessed the emergence of a new architecture for computing based on networks of diversified computer systems. The integration of diverse systems into such an environment introduces functional compatibility issues that are not present in homogeneous networks. Effective treatments for functional compatibility, therefore, must go beyond the communication paradigms used in present distributed systems, such as the traditional Inter-Process Communication (IPC) and Remote Procedure Call (RPC). In this thesis, presented is a model called a Stubless Heterogeneous Remote Procedure Call System (SHRPCS) using multi-option presentation layer interface for developing a call processing environment in which heterogeneous distributed systems can share network-wide system resources through a remote procedure call mechanism using a stubless run-time facility (HRPC-RTL) and a multi-option presentation layer interface available for a single function call, or an aggregate call, or a Network Interface Language (NIL). Also, a new error recovery methodology for both regular RPC call and atomic call is presented to help recover from network failures, client crashes, or server crashes by means of reusing the execution outcome of orphans without killing them unnecessarily. This paper covers the rationale, design, implementation, and supporting environments of SHRPCS. Besides exploring various main issues, the algorithms to implement the major components of SHRPCS on HRPC-RTL, NetServer process, and Server process are also included. HRPC-RTL serves as one virtual stub for all client programming languages so as to reduce the complexity of generating a large number of potential stubs to 1. Because the architecture of SHRPCS is so modularly constructed that any new enhancement can be made incrementally on top of the existing system. Although the main focus of our work here is for heterogeneous RPC systems, the actually resulting framework can also apply to general RPC systems. The general RPC system, in fact, is a simple instance of SHRPCS.

Cited by 0

Iago Attacks: Why The System Call API Is a Bad Untrusted RPC Interface

Stephen Checkoway, Hovav Shacham · 2012

In recent years, researchers have proposed systems for running\ntrusted code on an untrusted operating system. Protection mechanisms deployed\nby such systems keep a malicious kernel from directly manipulating a trusted\napplication’s state. Under such systems, the application and kernel are,\nconceptually, peers, and the system call API defines an RPC interface between\nthem. We introduce Iago attacks, attacks that a malicious kernel can mount in\nthis model. We show how a carefully chosen sequence of integer return values to\nLinux system calls can lead a supposedly protected process to act against its\ninterests, and even to undertake arbitrary computation at the malicious\nkernel’s behest. Iago attacks are evidence that protecting applications from\nmalicious kernels is more difficult than previously realized.Pre-2018 CSE ID: CS2012-0984

Cited by 7

A flexible system call interface for interprocessor communication in a distributed memory multicomputer

Maria D. Maggio, David W. Krumme · ACM SIGOPS Operating Systems Review · 1991

The Multifaceted Communication System for the distributed memory NCUBE is an interprocessor communication system that supports many features useful for application programs: asynchronous, partially and fully synchronous calls in blocking and non-blocking modes, buffered and unbuffered transmissions, gather and scatter operations, broadcasting, a general pipe mechanism, and file operations. A major achievement of this design is the use of a single, consistent user interface. This paper describes the main features of that interface and the semantics of the operations it embodies.

Cited by 4Open access

Safe dynamic linking in an extensible operating system

Emin Gun, Sirer Marc, E. Fiucynski et al. · 1996

The protection of operating system code from user code in most systems is based on the separation provided by anarchitecturally enforced user/kernel boundary. The boundary isolates an application from the kernel and from other applications. Only through the system call interface can applications interact with kernel services or one another. The system call interface has worked well in the past because the number of services

Cited by 0

Agricultural Human-Machine Dialogue System Development Based on Semantic and Location Similarity of Short Text Model

Qingfeng Wei, Chenxue Zhong, Jun Yu et al. · 2018

To the problem that the reply accuracy is low and its can't answer common chat topics at the same time in agricultural man-machine dialogue, a similarity model is proposed by a comprehensive consideration of semantic words and position words, a system development process is design that agricultural problems call the interface of agricultural knowledge database, non professional issues call the interface of universal chat database. Through the test of the agricultural consulting service robot system development, the accuracy rate of the advisory reply reached 86.1%. The satisfaction rate of the system reached 80.5%.

Cited by 2

The use of callback method in a threaded client of a distributed .NET application

I. Kostal · 2011

If we develop by .NET Remoting a .NET distributed application with a threaded client that has a user interface (UI) for a control of a distributed mechatronics system we have to often solve a problem of the responsiveness of its user interface. In a Windows Forms UI application all the code usually runs on a single thread known as the primary UI thread that is important because it is in charge of maintaining the responsiveness of the user interface. But how does our application respond when an asynchronous method call has finished executing and how do we update the user interface when an asynchronous call is finished? In this case we can take advantage of a handy feature of delegates that let us set up a callback method that is automatically executed by the common language runtime (CLR) when an asynchronous method call is completed. This paper shortly describes setting up a callback method by a delegate type named AsyncCallback that is defined by the Framework Class Library in the System namespace. In a conclusion the paper demonstrates the use of a callback method in the threaded client of sample distributed .NET application that was built in the Microsoft Visual Basic 2008 language and in the Microsoft Visual Studio 2008 development environment. By a callback method this client keeps the responsiveness of its user interface during executing an asynchronous call and updates the user interface when an asynchronous call is finished.

Cited by 0

GSM Pocket Guide

Muhammad Ashraf · Bulletin of Miscellaneous Information (Royal Gardens Kew)

This article includes the followin Tops: GSM system architecture The Base station controller (BSC) the mobile switching center (MSC): The Home location register (HLR); The visitor location register (VLR The authentication center (AuC): The mobile station (MS) The equipment identity register (EIR): The base station subsystem (BSS Operation and Maintenance Center (OMC) The base transceiver station (BTS) Interfaces and protocols GSM1900 GSM1800 GSM900 Logical channels on the air interface The air interface Um GSM Channels on Air Interface Traffic channels on the air interface Burst formats The Abis interface Protocols on the A interface The A interface MSC protocols MSC-based interfaces Alarm monitoring Test and measurement problems in GSM Call Forwarding (CF) Call Hold (CH) Calling Line ID uthentication and much more

Cited by 0

The q-Interface to UNIX

Robert D. Russell · HAL (Le Centre pour la Communication Scientifique Directe) · 1998

This report describes an application program interface to UNIX called the q-interface. It is designed to provide the programmer with convenient access to a reliable, message-oriented asynchronous network transport service, and to asynchronous event handling in general. It utilizes a «call-back» paradigm to notify the programmer of the occurrence of asynchronous events, and guarantees that all call-backs are atomic. It hides both the notification mechanism of the underlying operating system and the underlying networking system, which in the first implementation is TCP/IP.

Cited by 0Open access

Microsoft Research Video 104151: Splitting Interfaces: Making Trust Between Applications and Operating Systems Configurable

Microsoft Research · Bulletin of Miscellaneous Information (Royal Gardens Kew) · 2006

In current commodity systems, applications have no way of limiting their trust in the underlying operating system (OS), leaving them at the complete mercy of an attacker who gains control over the OS. In this talk, I will describe the design and implementation of Proxos, a system that allows applications to configure their trust in the OS by partitioning the system call interface into trusted and untrusted components. System call routing rules that indicate which system calls are to be handled by the untrusted commodity OS, and which are to be handled by a trusted private OS, are specified by the application developer. We find that rather than defining a new system call interface, routing system calls of an existing interface allows applications currently targeted towards commodity operating systems to isolate their most sensitive components from the commodity OS with only minor source code modifications. We have built a prototype of our system on top of the Xen Virtual Machine Monitor with Linux as the commodity OS. In practice, we find that the system call routing rules are short and simple – on the order of 10's of lines of code. In addition, applications in Proxos incur only modest performance overhead, with most of the cost resulting from inter-VM context switches. This work will appear in OSDI 2006. ©2006 Microsoft Corporation. All rights reserved.

Cited by 0

Design of traffic information system display for a typical mobile communication: article / Fatin Fatimah Mohammad Afendy

Mohammad Afendy, Fatin Fatimah · UiTM Institutional Repositories (Universiti Teknologi MARA) · 2013

This paper is about the design of a traffic information system for a typical mobile communication such as dropped calls. The database used for this project is Microsoft Access 2010 (Access). The database used to store the username and password for login. In this project, Microsoft Excel 2010 (Excel) used to insert a chart and can be displayed from Visual Basic 6.0 (VB) by clicking the command button exists. The chart was inserted for Max. Dropped Call vs Cell ID, Max. Dropped Call vs Cell ID for each hour in one day and Max. Dropped Call vs Time. Besides, pie chart also can be displayed to find which cell are most frequently occur a dropped call. VB used as a user interface in this project to allowed users to view the chart. Other than that, from the chart also can identify at which time dropped call are most often occurs. The interface that used are drawn in a form such as 'Label', 'Command Button', Text Box', and 'Picture Box'. VB used as the user interface because of its user-friendly interface and data access features.

Cited by 0

System and Method for Providing a Climate Data Analytic Services Application Programming Interface

Tamkin, Glenn S., Duffy, Daniel Q., Schnase, John L. · NASA STI Repository (National Aeronautics and Space Administration)

A system, method and computer-readable storage devices for providing a climate data analytic services application programming interface. The system includes a programming library that enables client device software to invoke the capabilities of a climate data analytics system through requests to various services supported by the climate data analytics system, and also includes a client-side communications interface that enables the programming library's methods to interact with a climate data analytics system's server interface to obtain access to the capabilities of the system. In one implementation, the programming library is implemented in the Python programming language. The programming library can include basic utilities that call a single, server-side method implemented by one of the various services supported by the climate data analytics system, and extended utilities that call a series of basic utilities and/or other extended utilities that have been placed under programmatic control in order to create client-side convenience methods and workflows.

Cited by 0Open access

SAPL

Tilman P. Otto · 2002

The SAP company (Walldorf / Germany) provides a software interface for its R2 and R3 products called "Remote Function Call" (RFC). This interface is available on multiple operating systems and allows external systems written in C or C++ to directly call function modules of a R2/R3 system. In addition, it is even possible to provide external server function modules within an external system, which can be accessed from within the SAP system. This paper presents the newly developed RFC based APL extension "SAPL" that allows writing client and server applications for SAP systems entirely in APL. SAPL is the bridge between the powerful multi-dimensional data processing capabilities of APL and SAP based business applications.

Cited by 0