The preemptive scheduling based structure is used in JBOSN RTOS and provide additional policy, the round-robin scheduling. Also The Strong policy of time management makes to implement the may powerful features in the embedded systems required a tight time constraint.

Using a single address space, the kernel, middleware, and application of the single physical address space makes to be able to use the rapid implementation of real-time task switching. And all component is loaded in the form of one image on the target system, but by its own relocation techniques with each other, and a separate, it is possible to protect itself from the other modules.

The record does not provide the user in arms, is the lack of features for the module itself felt capabilities can be inserted in the product. Of course, there is nothing functionally constraints.

When you write a driver or operating system, middleware, multi-tasking capabilities of the various issues raised by (the synchronization, the sharing, and tasking conflicts ...) can be written without considering at all, to guarantee the stability of the system is possible.

Interrupt latency of the system, especially a constant delay in the real-time operating system is a very important issue. JBOSN RTOS provides always a constant interrupt delay and prevents efficiently the interrupt priority reserse. Most of the operating system interrupt for the delay in the implementation of multi-tasking features considerable sacrifices in order to avoid conflicts and tasks, and interrupt delay consideration when creating the driver should be written and will not affect the system. The creation of this relatively difficult for the driver in the operating system, the general developers are difficult to access. JBOSN RTOS resolves this issue at all these issues, so, developers can create without worrying about the driver at all for the delay does not affect interrupts.