Patents
Literature
Hiro is an intelligent assistant for R&D personnel, combined with Patent DNA, to facilitate innovative research.
Hiro

48 results about "Java Native Interface" patented technology

The Java Native Interface (JNI) is a foreign function interface programming framework that enables Java code running in a Java virtual machine (JVM) to call and be called by native applications (programs specific to a hardware and operating system platform) and libraries written in other languages such as C, C++ and assembly.

Extended keyboard support in a run time environment for keys not recognizable on standard or non-standard keyboards

A keyboard is programmatically adapted to enable an application in a run time environment to distinguish operator keys (ALT/CTRL), not otherwise recognizable on a standard keyboard and special keys not otherwise recognizable on a non-standard keyboard by the application, when actuated. In one embodiment, a native Dynamic Link Library (DLL) is created in memory to capture the keystroke stream and maintain state information about the keyboard. A Java Native Interface (JNI) is created in the DLL and provided to a Java application. At initialization time, the Java application loads the native DLL with extended program instructions relating to key recognition in its static constructor. The Java application receives notification when an ALT or CTRL key is actuated. At that time the Java application calls the native DLL to receive the extended program instruction to determine whether the right or left ALT or CTRL key was actuated. The DLL programmatically determines whether the right or left ALT or CTRL key was struck. The DLL provides the Java application a flag that allows the application to determine if a "right" or a "left" (ALT/CTRL) key was actuated. On a non-standard keyboard, the Java application calls the native DLL to receive the necessary information on the key that was actuated. Again, the DLL programmatically provides a flag and extended keystroke data that allows the Java application to determine if a special key was actuated.
Owner:IBM CORP

Method and system for metering execution of interpreted programs

A method and a corresponding system (200) for metering execution of interpreted programs (220) are proposed. Typically, an interpreter, such as the Java Virtual Machine (215), lacks built-in capabilities for communicating with the hardware and software platform of the computer directly; for this purpose, the virtual machine invokes external native functions through the Java Native Interface (225). The solution of the invention is based on the idea of stubbing the dynamic libraries (235) that implement those native functions. Therefore, when the virtual machine needs a native function (for example, to load a new class), a stub library (250) is loaded in place of the required dynamic library. As soon as the virtual machine calls the desired command, the stub library takes control and identifies the interpreted program that is run by the virtual machine; preferably, this operation is performed by querying a catalogue that associates the new class with the corresponding interpreted program. The stub library then loads the dynamic library and forwards the required command. In a different embodiment, the class loader is replaced with a stub module. In this case, the stub class loader detects the loading of the class including a main method of the interpreted program; the main method is then updated by inserting a call to a licensing agent, in order to identify the interpreted program when the main method is actually executed.
Owner:IBM CORP

Method of integrating X window intrinsics based toolkits and widgets with java

A method of integrating an Xt Intrinsics based toolkit with a JAVA application. The application includes a process thread that implements an X event loop and an application thread that suspends execution of the event loop to allow a call to be made through the JAVA Native Interface to a toolkit or a widget to cause something to be displayed. The application thread includes a write socket to communicate a token to a read socket of the event loop, and performs a blocking read suspending the thread. The event loop returns an acknowledgment token via a write socket to a read socket of the thread that unblocks its blocking read and the event loop invokes its own blocking read suspending its execution. The file descriptor function, XtAppAddInput, preferably, is used to read the token and to set the blocking read. After a toolkit call is made, a token is sent from a second write socket of the thread to a second read socket of the event loop that unblocks its blocking read resuming the event loop. JAVA multithreading support services, such as JAVA's wait and notifyAll methods, are employed in multithreaded applications to ensure that only one thread at a time can make a call. Use of a separate Intrinsics application context to service the event loop is employed, windows are managed in separate hierarchies associated with each application context, and a special JAVA Canvas manages native windows transparent to the programmer.
Owner:GENERAL ELECTRIC CO

Software development kit (SDK) module for Android real time streaming protocol (RTSP) player

The invention belongs to the field of the software development kit (SDK) design of an Android real time streaming protocol (RTSP) player application scheme, and in particular relates to an SDK module for an Android RTSP player. The SDK module comprises an Android system layer, a database interface layer, an audio/video output layer and a player network layer from bottom to top, wherein the database interface layer comprises a lib layer and a java native interface (JNI) layer from bottom to top; the lib layer comprises an Opencore module and an RTSPFfmpeg module; the player network layer is provided with an RTSP server and an RTSP client which are mutually connected; the RTSPFfmpeg module comprises an Ffmpeg decoding module and a Live555 transmission module and is provided with a JNI and an application programming interface (API); the RTSP client comprises an Opencorertsp client which is based on the Opencore module, and a Live555 client; and the player network layer is provided with an active selector and calls the API of the module in the lib layer through the active selector. The SDK module supports two optional modules, namely the Opencore module and the Ffmpeg module, and supports various audio/video formats.
Owner:SOUTH CHINA UNIV OF TECH

Method of integrating X Window Intrinsics based toolkits and widgets with JAVA

InactiveUS20050060724A1Without risk of data corruptionInterprogram communicationExecution for user interfacesIntrinsicsFile descriptor
A method of integrating an Xt Intrinsics based toolkit with a JAVA application. The application includes a process thread that implements an X event loop and an application thread that suspends execution of the event loop to allow a call to be made through the JAVA Native Interface to a toolkit or a widget to cause something to be displayed. The application thread includes a write socket to communicate a token to a read socket of the event loop, and performs a blocking read suspending the thread. The event loop returns an acknowledgment token via a write socket to a read socket of the thread that unblocks its blocking read and the event loop invokes its own blocking read suspending its execution. The file descriptor function, XtAppAddInput, preferably, is used to read the token and to set the blocking read. After a toolkit call is made, a token is sent from a second write socket of the thread to a second read socket of the event loop that unblocks its blocking read resuming the event loop. JAVA multithreading support services, such as JAVA's wait and notifyAll methods, are employed in multithreaded applications to ensure that only one thread at a time can make a call. Use of a separate Intrinsics application context to service the event loop is employed, windows are managed in separate hierarchies associated with each application context, and a special JAVA Canvas manages native windows transparent to the programmer.
Owner:GENERAL ELECTRIC CO

Android terminal and method for realizing TR069 network management agent

ActiveCN104184618AEffective analysis efficiencyOvercoming Fragmentation DisadvantagesData switching networksInformation repositorySystem configuration
The invention discloses an Android terminal and a method for realizing a TR069 network management agent. The method comprises the steps of continuously using an a TR069 protocol processing unit of a c-code local module on an original Linux platform to carry out interaction with a network-side network management platform, continuously using a local information management unit applicable to an Android environment on the original Linux platform to carry out maintenance on a local information base, and using an agent service module and an AIDL (Android interface definition language) service end module which correspond to an Android version prepared by using JAVA to carry out interaction with a user-side Android application program; the agent service module and the AIDL service end module mutually call the TR069 protocol processing unit through a JNI (Java native interface), thereby realizing report and registration of system configuration, updating of the system configuration and calling of related functions of Android application programs. The method disclosed by the invention makes full use of a JNI mechanism of an Android system, realizes mutual call of Java and local C-codes, and realizes the TR069 network management agent; a defect of fragmentation of the Android system is overcome; and a scheme of an existing Linux platform C can be directly transplanted.
Owner:FENGHUO COMM SCI & TECH CO LTD
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Try Eureka
PatSnap group products