CN112083914B - Method and system for realizing object model embedded operation system soft bus - Google Patents
Method and system for realizing object model embedded operation system soft bus Download PDFInfo
- Publication number
- CN112083914B CN112083914B CN202010895883.2A CN202010895883A CN112083914B CN 112083914 B CN112083914 B CN 112083914B CN 202010895883 A CN202010895883 A CN 202010895883A CN 112083914 B CN112083914 B CN 112083914B
- Authority
- CN
- China
- Prior art keywords
- bus
- cache
- communication
- recording
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
Abstract
The invention relates to a method and a system for realizing an object model embedded operation system soft bus, comprising the following steps: recording an object bus, wherein the recording comprises the steps of executing the processing of entering the bus, initializing, exiting a bus network and recording the entering data; buffering the input data by using the data and the linked list, wherein the buffering comprises adding buffering, deleting buffering, searching buffering and transferring buffering; the communication of the object bus comprises the basic communication, positioning, port communication and migration processing of a plurality of data objects in the incoming data. The beneficial effects of the invention are as follows: the plug and play of the software system is realized, any application program can be directly integrated into the system environment, the realization mode is simple, and the manpower and material resources are saved.
Description
Technical Field
The invention relates to the field of computers, in particular to a method and a system for realizing an object model embedded operating system soft bus.
Background
The intelligent equipment of network interconnection has been fully applied to the aspects of our lives, but with the crazy growth of the number of application software and hardware devices, many design problems in software development and application have not been or rarely appeared before and are gradually exposed. In order to enable the internetworking intelligent equipment to have negotiation, collaboration and self-organization capabilities, an object model-based operating system suitable for the internetworking intelligent equipment is rapidly developed. The object model operating system is a communication port (ports) which encapsulates software functions and communication ports together, defines an object model, and takes a conventional IPC as an object, wherein one object includes ports such as an input port (input ports) and an output port (output ports) in addition to attributes such as priority, scheduling mode (whether preemptive or not) and the like. The object is a basic unit of scheduling operation, can be independently addressed on the network and can communicate with other objects in a network transparent way through ports carried by the object.
The conventional embedded operating systems which are widely used at present, such as an ARIC653 operating system, an OSEK/VDX operating system, a VxWorks, pikeOS, QNX, uC/OS and the like, all use processes and files as abstract models, use classical IPC mechanisms such as message communication, mailboxes, semaphores, events and the like as communication mechanisms, and access the devices in a file mode. The process has no input/output semantics, can not express and package functions, and also does not support direct reference to functions, and needs to rely on an IPC mechanism to interact with other processes. However, IPC mechanisms act as process independent intermediate entities, both with uncertainty and with difficulty supporting transparent networked access. The above factors cause that the classical operating system abstraction model of process+ipc is difficult to adapt to the requirements of fine-grained functional encapsulation, transparent access between representation and network, communication and the like.
In addition, in the application of the internet of things, there is a problem that interaction is needed to be faced, interaction between different application software and interaction between hardware devices are taken as an example of smart home with gradual heating, and people often hope that a mobile phone can operate everything, and various smart home can be effectively interconnected. This is a significant challenge for conventional software designs, where interactions between complex software systems remain error-prone, and much effort and cost are focused on repeated development of the same design concepts and code components. However, the diversification of hardware architecture, complexity of the operating system and differentiation of the communication platform make it very difficult to design a scalable, interactive, efficient, componentized software system from scratch. In addition, in some situations, members of the entire system frequently access, exit the system and change access addresses due to some reason, such as signal fluctuations or some requirement, and it is difficult for software systems developed in conventional development modes to cope with such highly dynamic situations.
Disclosure of Invention
The invention aims at solving at least one of the technical problems existing in the prior art, and provides a method and a system for realizing an embedded operation system soft bus of an object model, and realizing plug and play of a software system.
The technical scheme of the invention comprises a method for realizing an embedded operating system soft bus of an object model, which is used for an object operating system and is characterized in that: recording an object bus, wherein the recording comprises the steps of executing the processing of entering the bus, initializing, exiting a bus network and recording the entering data; buffering the input data by using the data and the linked list, wherein the buffering comprises adding buffering, deleting buffering, searching buffering and transferring buffering; the communication of the object bus comprises the basic communication, positioning, port communication and migration processing of a plurality of data objects in the incoming data, wherein the port communication comprises the communication corresponding to a data port, an event port, a signal port and an output port.
The method for realizing the soft bus of the object model embedded operating system comprises the steps of recording an object record, a task record and a bus record, wherein the object record comprises the recording of an object, a task and a bus of entering data; wherein the bus record includes: when the object bus is about to enter the object bus network, the address information of other object buses in the network is acquired, and the address information is checked at set time intervals.
The method for implementing the object model embedded operating system soft bus according to the present invention, wherein the initializing includes: setting the object bus, including loading the protocol of the encapsulation layer/analysis layer of the communication module of the object bus, recording the IP address of the object bus, recording the existing object in the object bus into the object bus through the object recording function, and initializing the corresponding signal quantity.
The method for implementing the object model embedded operating system soft bus according to the present invention, wherein exiting the bus network comprises: and acquiring address information of an object bus in the object bus network, sending notification information including the address information to the object bus, and checking in a set interval.
The method for implementing the object model embedded operating system soft bus according to the present invention, wherein exiting the bus network comprises: closing the update of the own IP table, and sending an exit notification to the existing object buses, requesting them to delete the own address information.
The method for implementing the object model embedded operating system soft bus according to the present invention, wherein the buffering of the line bus comprises: adding a cache, and finding a cache address to be deleted according to the content to be deleted; the other is to find the buffer address which should be released according to the array sequence, delete the buffer after exchanging the two partial contents; deleting the cache, including adding the cache of the depended attribute while adding the existing data through the search linked list; searching a cache, namely searching whether the cache meeting the requirements exists in the cache according to the key information, and returning the cache information if the cache meets the requirements; and migrating the cache, wherein the state of the corresponding cache is marked as a cache state, waiting for migration, and the object of the cache state is in a state of refusing access or delaying access.
The method for implementing the object model embedded operating system soft bus according to the present invention, wherein the communication of the object bus includes: basic communication including transmission and reception of information; object positioning, including positioning by querying the object cache, querying the cache on the whole bus, and querying the object bus network; port communication, including setting specific protocol for application of encapsulation layer/analysis layer to complete communication; and the migration processing comprises the steps of sending a migration notification and a request before migration, activating a cache object, acquiring cache information and executing migration.
The technical scheme of the invention also comprises a system for realizing the object model embedded operation system soft bus, which is characterized in that: the object bus recording module is used for executing the processing of entering a bus, initializing, exiting a bus network and recording the entering data; the object bus buffer module is used for buffering the incoming data by using the data and the linked list, wherein the buffer comprises adding buffer, deleting buffer, searching buffer and transferring buffer; and the object bus communication module is used for carrying out basic communication, positioning, port communication and migration processing on a plurality of data objects in the incoming data, wherein the port communication comprises communication corresponding to a data port, an event port, a signal port and an output port.
The beneficial effects of the invention are as follows: the plug-and-play of the software system is realized, any application program can be directly integrated into the system environment as long as the bus interface standard is followed, the realization mode is simple, and the manpower and material resources are saved.
Drawings
The invention is further described below with reference to the drawings and examples;
FIG. 1 is a block diagram of a system according to an embodiment of the present invention;
fig. 2 is a functional schematic of a hierarchy in accordance with an embodiment of the present invention.
Fig. 3a,3b,3c,3d,3e,3f are flowcharts illustrating recording implementations according to embodiments of the present invention.
FIG. 4 is a flow chart of an object bus initialization implementation according to an embodiment of the invention.
FIG. 5 is a flow chart of an implementation of an ingress object bus network according to an embodiment of the invention.
FIG. 6 is a flow chart illustrating an exit object bus network implementation according to an embodiment of the invention.
FIGS. 7a,7b,7c are flowcharts of implementations of deleting a cache according to embodiments of the present invention.
FIGS. 8a,8b,8c are flowcharts illustrating an implementation of adding cache according to embodiments of the present invention.
FIG. 9 is a flow chart of an implementation of lookup caching according to an embodiment of the invention.
Fig. 10a and 10b are flowcharts of a migration cache implementation according to an embodiment of the present invention.
Fig. 11a,11b are flowcharts illustrating basic communication function implementations according to embodiments of the present invention.
FIG. 12 is a flow chart of an object localization implementation according to an embodiment of the present invention.
13a,13b,13c are diagrams illustrating port communication implementations according to embodiments of the invention.
FIG. 14 is a flow chart of an object migration implementation according to an embodiment of the present invention.
Detailed Description
Reference will now be made in detail to the present embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein the accompanying drawings are used to supplement the description of the written description so that one can intuitively and intuitively understand each technical feature and overall technical scheme of the present invention, but not to limit the scope of the present invention.
In the description of the present invention, a number means one or more, a number means two or more, and greater than, less than, exceeding, etc. are understood to not include the present number, and above, below, within, etc. are understood to include the present number.
In the description of the present invention, the continuous reference numerals of the method steps are used for facilitating examination and understanding, and by combining the overall technical scheme of the present invention and the logic relationships between the steps, the implementation sequence between the steps is adjusted without affecting the technical effect achieved by the technical scheme of the present invention.
In the description of the present invention, unless explicitly defined otherwise, terms such as arrangement and the like should be construed broadly, and those skilled in the art can reasonably determine the specific meaning of the terms in the present invention in combination with the specific contents of the technical scheme.
Referring to fig. 1, it includes: the recording module is used for executing the processing of entering a bus, initializing, exiting a bus network and recording on the entering data; the buffer memory module is used for buffering the entered data by using the data and the linked list, wherein the buffer memory comprises an addition buffer memory, a deletion buffer memory, a search buffer memory and a migration buffer memory; the communication module is used for carrying out basic communication, positioning, port communication and migration processing on a plurality of data objects in the incoming data, and the port communication comprises a data port, an event port, a signal port and communication corresponding to an output port.
FIG. 2 is a schematic diagram of a recovery heterogeneous executable trusted routing table according to an embodiment of the present invention. Referring to fig. 2 in conjunction with the technical solution of fig. 1, in this process, how to recover the own routing table after the heterogeneous execution bodies are on line again becomes a problem, and because the heterogeneous execution bodies are not trusted, the routing tables of other execution bodies cannot be directly copied to the local machine, and the invention proposes an idea: the new heterogeneous executable on line inversely analyzes the routing table from the arbitrated flow table. Because the flow table is already under mimetic arbitration, it is trusted.
Referring to fig. 3a,3b,3c,3d,3e are flowcharts of recording implementations.
Recording function
The recording function of the object bus mainly comprises three blocks of object recording, task recording and bus recording.
Object registration (refer to fig. 3 a):
void sbus_regist_object(struct object_regist*o)
object deletion (refer to fig. 3 b):
void sbus_delete_object(struct object_regist*o)
b: simplified representation of functions related to task recording:
find and add task (see fig. 3c, find first, add not send task request at the same time, return task location):
struct task_findIPbyName*searchTask(struct object_regist*o,char name[20])
task deletion (see fig. 3 d):
void deleteTask(struct task_findIPbyName*t)
simplified representation of functions related to bus records:
the bus record related operation is realized in the process of entering the bus network, and mainly comprises two processes: one is to acquire, when an object bus is to enter an object bus network, address information of other object buses in the network; the other is verification, after the address information of other object buses in the network is obtained, the address information is obtained again for verification after a period of time, so that potential problems (which are not notified) caused when a plurality of object buses access the object bus network at the same time can be avoided.
These two parts are now drawn separately, a simplified representation of their functions (the original procedure is not an independent method):
acquiring information of an object bus in a network (refer to fig. 3 e):
void getIPTable()
checking the acquired information of the object bus in the network (refer to fig. 3 f):
void getIPTable()
FIG. 4 is a flow chart of an object bus initialization implementation according to an embodiment of the invention.
The initialization of the object bus includes:
the initialization of the object bus is to set some information of the object bus, and specifically includes loading the protocol of the encapsulation layer/parsing layer of the communication module of the object bus, recording the IP address of the object bus, recording the existing object in the object bus into the object bus through the function of object recording, and initializing the corresponding signal quantity.
FIG. 5 is a flow chart of an implementation of an ingress object bus network according to an embodiment of the invention.
3) Entering the object bus network includes:
the entry into the object bus network is to inform the object bus in the object bus network that itself is to be added to the object bus network, since which object bus is to participate in all activities of the object bus network, including sending information, receiving information, etc. through the object bus network.
Because all the object buses are independent, and all address information of all the object buses is locally stored, the object buses need to do work when entering the network: acquiring address information of an object bus in an object bus network; an access notification is sent to these object buses informing them of their own address information. Considering that there may be multiple object bus accesses in the same time period, some potential problems may arise, and thus a verification step is added.
FIG. 6 is a flow chart illustrating an exit object bus network implementation according to an embodiment of the invention.
Exiting the object bus network includes:
exiting the object bus network is to notify the object bus in the object bus network, and to exit the object bus network itself. Since then the object bus is no longer involved in all activities of the object bus network, including not sending information through the object bus network, but also rejecting information, etc.
Similar to the task required for the object bus to enter the network, notification is performed before exiting, except that the update of its IPTable is closed first to avoid unnecessary trouble, and the overall flow is: closing the update of the IPTAble; an exit notification is sent to the existing object buses requesting them to delete their own address information. After a period of time, verification is performed, and exit notifications are sent to the newly added object buses that have not been notified previously, requesting them to delete their own address information.
FIGS. 7a,7b,7c are flowcharts of implementations of deleting a cache according to embodiments of the present invention.
Deleting the cache includes: the buffer memory adopts the structure of an array and a linked list, and in order to be convenient to use, the blank buffer memory space is uniformly placed at the end of the array, so that the acquisition during adding is faster.
Therefore, the cache is deleted in two main parts, one is to find the cache address to be deleted according to the content to be deleted; and the other is to find the buffer addresses which should be released according to the array sequence, and delete the buffer after exchanging the two parts of contents.
Simplified representation of the function in relation to delete cache (for simplicity of expression, no related operations of semaphore are described):
find the cache that should be released based on the content (see fig. 7 a):
struct object_cache*findNodeByContent(struct object_regist*o,struct object_cache c,struct object_cache*deps_head,struct object_cache*refs_head,int*type)
find the buffer that should be released from space (see fig. 7 b):
struct object_cache*findNodeByOrder(struct object_regist*o,struct object_cache*deps_head,struct object_cache*refs_head)
delete cache complete process (see fig. 7 c):
void deleteCache(struct object_regist*o,struct object_cache c)。
FIGS. 8a,8b,8c are flowcharts illustrating an implementation of adding cache according to embodiments of the present invention.
Adding a cache is the most basic function of the cache module, but is also the most core function, as it involves the implementation of the update policy of the cache. The performance, stability and availability of the cache are largely dependent on the algorithm that increases the cache. These contents are described in detail in the design of the cache module of the object bus in the previous section, and will not be described again. Next, an actual implementation of adding the cache function will be described.
Simple representation of the function in relation to the increase cache (for simplicity of expression, no related operation of the semaphore is described):
adding buffering of dependent properties (see fig. 8 a):
void addDependCache(struct object_regist*o,struct object_cache c)
adding the cache of dependent attributes (see fig. 8 b):
void addReferCache(struct object_regist*o,struct object_cache c)
increasing the buffer (see fig. 8 c):
void addCache(struct object_regist*o,struct object_cache c,cacheType type)
FIG. 9 is a flow chart of an implementation of lookup caching according to an embodiment of the invention. The searching cache is a part of the service function of the cache module, whether the cache meeting the requirements exists or not is searched in the cache according to the key information, and if yes, the cache information is returned.
Simple representation of the function in relation to look-up caching (for simplicity of expression, no related operation of semaphores is described):
struct object_cache searchCache(struct object_regist*o,char name[20])
fig. 10a and 10b are flowcharts of a migration cache implementation according to an embodiment of the present invention. The buffer memory migration is a service function provided by the buffer memory module for the object migration process, and aims to improve the availability of the buffer memory, mainly when the object is migrated, the corresponding buffer memory state is marked as a buffer memory state, and the state can reject and delay access and wait for updating. Next, an actual implementation of the cache migration related function will be described.
The functions related to cache migration can be simply implemented in the following form (for simplicity of expression, no related operations of the semaphore are described):
modify the migration state of the specified cache (see fig. 10 a):
void migrateCache(struct object_regist*o,struct object_id c)
modify the contents of the specified cache (see fig. 10 b):
void changeCache(struct object_regist*o,struct object_cache c)
fig. 11a,11b are flowcharts illustrating basic communication function implementations according to embodiments of the present invention.
Implementation of basic communication functions
Transmission of information (fig. 11 a) is included:
int sendDataLine(SOCKET sclient,struct dataLine dl,void*defaultTarget)
reception of information (see fig. 11 b):
void*service_run(void*null)
FIG. 12 is a flow chart of an object localization implementation according to an embodiment of the present invention. Object localization (object id is obtained by object name) is one of the functions of the core of the object bus, and is a precondition for many operations concerning an object operation. The specific flow is as shown in FIG. 12:
object localization is generally divided into three stages that progress in sequence: querying at the object's own cache, querying at a cache over the entire bus, querying over the object bus network. The time of inquiry is increased in sequence, and the inquiry can be stopped after the result is obtained in any step. It can also be seen from this flow that a good cache module will bring a great optimization to the positioning.
13a,13b,13c are diagrams illustrating port communication implementations according to embodiments of the invention. The communication of the ports is four, namely a data port, an event port, a signal port and an output port, and the working schematic diagram is shown in fig. 13a (port working schematic diagram):
the communication implementation of these ports is mainly to the application of the encapsulation layer/parsing layer in the communication module, ensuring the correct handling of these transmitted information by setting specific protocol contents. Because the flow similarities of the data port, event port, and signal port communications are high, only the data port and output port are shown as examples. As shown in fig. 13b (data port communication activity diagram) and fig. 13c (output port communication activity diagram), respectively.
From fig. 13b and 13c, it can be seen that the main flow and activities of data port communication and output port communication, it can be seen that the accurate representation and interpretation of protocols in the communication functions is the underlying guarantee of port communication activity.
FIG. 14 is a flow chart of an object migration implementation according to an embodiment of the present invention.
Object migration is a functional requirement of an object bus, and under some conditions, some object needs to be transferred. In this process, if the object bus does not take any measure, then the other objects related to the object will lose the target when they are accessed next time, the object needs to be relocated, and the previous caches of the object will be all discarded, so that the needed object address needs to be relocated after migration. All the behaviors can cause certain communication pressure on the object bus network, the object bus adopts the operation of migration communication, and the loss can be greatly reduced by coordinating the migration process to a certain extent, so that the negative influence caused by the object migration is reduced, and the utilization rate of the cache is improved.
The embodiments of the present invention have been described in detail with reference to the accompanying drawings, but the present invention is not limited to the above embodiments, and various changes can be made within the knowledge of one of ordinary skill in the art without departing from the spirit of the present invention.
Claims (5)
1. A method for realizing the soft bus of the embedded operating system of the object model is used for the object operating system and is characterized in that:
recording an object bus, wherein the recording comprises the steps of executing the processing of entering the bus, initializing, exiting a bus network and recording the entering data;
buffering the input data by using the data and the linked list, wherein the buffering comprises adding buffering, deleting buffering, searching buffering and transferring buffering;
the communication of the object bus comprises the basic communication, positioning, port communication and migration processing of a plurality of data objects in the incoming data, wherein the port communication comprises the communication corresponding to a data port, an event port, a signal port and an output port;
the records comprise an object record, a task record and a bus record, wherein the object record comprises the record of an object, a task and a bus of entering data, and the bus record comprises: when an object bus is about to enter an object bus network, acquiring address information of other object buses in the network, and checking the address information at set time intervals;
the cache of the object bus includes: adding a cache, and finding a cache address to be deleted according to the content to be deleted; the other is to find the buffer address which should be released according to the array sequence, delete the buffer after exchanging the two partial contents; deleting the cache, including adding the cache of the depended attribute while adding the existing data through the search linked list; searching a cache, namely searching whether the cache meeting the requirements exists in the cache according to the key information, and returning the cache information if the cache meets the requirements; migrating the cache, wherein the state of the corresponding cache is marked as a cache state, waiting for migration, and the object of the cache state is in a state of refusing access or delaying access;
the communication of the object bus includes:
basic communication including transmission and reception of information; object positioning, including positioning by querying the object cache, querying the cache on the whole bus, and querying the object bus network; port communication, including setting specific protocol for application of encapsulation layer/analysis layer to complete communication; and the migration processing comprises the steps of sending a migration notification and a request before migration, activating a cache object, acquiring cache information and executing migration.
2. The method of implementing an object model embedded operating system soft bus of claim 1, wherein the initializing comprises: setting the object bus, including loading the protocol of the encapsulation layer/analysis layer of the communication module of the object bus, recording the IP address of the object bus, recording the existing object in the object bus into the object bus through the object recording function, and initializing the corresponding signal quantity.
3. The method of implementing an object model embedded operating system soft bus of claim 1, wherein exiting the bus network comprises: and acquiring address information of an object bus in the object bus network, sending notification information including the address information to the object bus, and checking in a set interval.
4. The method of implementing an object model embedded operating system soft bus of claim 1, wherein exiting the bus network comprises: closing the update of the own IP table, and sending an exit notification to the existing object buses, requesting them to delete the own address information.
5. A system for implementing an object model embedded operating system soft bus, characterized by:
the object bus recording module is used for executing the processing of entering a bus, initializing and exiting a bus network and recording on the entering data, wherein the recording comprises an object recording, a task recording and a bus recording, the object recording comprises the recording of the object, the task and the bus of the entering data, and the bus recording comprises: when an object bus is about to enter an object bus network, acquiring address information of other object buses in the network, and checking the address information at set time intervals;
the object bus buffer memory module is used for buffering the incoming data by using the data and the linked list, wherein the buffer memory comprises an addition buffer memory, a deletion buffer memory, a search buffer memory and a migration buffer memory, and the buffer memory of the object bus comprises: adding a cache, and finding a cache address to be deleted according to the content to be deleted; the other is to find the buffer address which should be released according to the array sequence, delete the buffer after exchanging the two partial contents; deleting the cache, including adding the cache of the depended attribute while adding the existing data through the search linked list; searching a cache, namely searching whether the cache meeting the requirements exists in the cache according to the key information, and returning the cache information if the cache meets the requirements; migrating the cache, wherein the state of the corresponding cache is marked as a cache state, waiting for migration, and the object of the cache state is in a state of refusing access or delaying access;
the object bus communication module is used for carrying out basic communication, positioning, port communication and migration processing on a plurality of data objects in the incoming data, the port communication comprises communication corresponding to a data port, an event port, a signal port and an output port, and the communication of the object bus comprises: basic communication including transmission and reception of information; object positioning, including positioning by querying the object cache, querying the cache on the whole bus, and querying the object bus network; port communication, including setting specific protocol for application of encapsulation layer/analysis layer to complete communication; and the migration processing comprises the steps of sending a migration notification and a request before migration, activating a cache object, acquiring cache information and executing migration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010895883.2A CN112083914B (en) | 2020-08-31 | 2020-08-31 | Method and system for realizing object model embedded operation system soft bus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010895883.2A CN112083914B (en) | 2020-08-31 | 2020-08-31 | Method and system for realizing object model embedded operation system soft bus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112083914A CN112083914A (en) | 2020-12-15 |
| CN112083914B true CN112083914B (en) | 2023-09-12 |
Family
ID=73731227
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010895883.2A Active CN112083914B (en) | 2020-08-31 | 2020-08-31 | Method and system for realizing object model embedded operation system soft bus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112083914B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114296809B (en) * | 2021-12-24 | 2023-05-05 | 深圳航天科技创新研究院 | Object model construction method based on operating system and system call interface thereof |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226487A (en) * | 2008-01-30 | 2008-07-23 | 中国船舶重工集团公司第七〇九研究所 | Method for implementing inner core level thread library based on built-in Linux operating system |
| CN101605084A (en) * | 2009-06-29 | 2009-12-16 | 北京航空航天大学 | Virtual network message processing method and system based on virtual machine |
| CN101692229A (en) * | 2009-07-28 | 2010-04-07 | 武汉大学 | Self-adaptive multilevel cache system for three-dimensional spatial data based on data content |
| CN103294023A (en) * | 2012-03-02 | 2013-09-11 | 费希尔控制国际公司 | Methods and apparatus to reduce memory requirements for process control system software applications |
| CN103442049A (en) * | 2013-08-22 | 2013-12-11 | 浪潮电子信息产业股份有限公司 | Component-oriented mixed type cloud operating system structure and communication method thereof |
| CN107729623A (en) * | 2017-09-22 | 2018-02-23 | 深圳航天科技创新研究院 | More people concurrent modeling method, system and storage mediums |
| CN108369549A (en) * | 2016-01-19 | 2018-08-03 | 微软技术许可有限责任公司 | Use the versioned record management for restarting period |
| CN108810041A (en) * | 2017-04-27 | 2018-11-13 | 华为技术有限公司 | A kind of data write-in of distributed cache system and expansion method, device |
| CN110209383A (en) * | 2019-06-12 | 2019-09-06 | 广东省华系智能系统有限公司 | Ubiquitous object interaction interface method towards general manufacture and edge calculations |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10129363B2 (en) * | 2015-05-29 | 2018-11-13 | Sap Se | Plug-in cache |
-
2020
- 2020-08-31 CN CN202010895883.2A patent/CN112083914B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226487A (en) * | 2008-01-30 | 2008-07-23 | 中国船舶重工集团公司第七〇九研究所 | Method for implementing inner core level thread library based on built-in Linux operating system |
| CN101605084A (en) * | 2009-06-29 | 2009-12-16 | 北京航空航天大学 | Virtual network message processing method and system based on virtual machine |
| CN101692229A (en) * | 2009-07-28 | 2010-04-07 | 武汉大学 | Self-adaptive multilevel cache system for three-dimensional spatial data based on data content |
| CN103294023A (en) * | 2012-03-02 | 2013-09-11 | 费希尔控制国际公司 | Methods and apparatus to reduce memory requirements for process control system software applications |
| CN103442049A (en) * | 2013-08-22 | 2013-12-11 | 浪潮电子信息产业股份有限公司 | Component-oriented mixed type cloud operating system structure and communication method thereof |
| CN108369549A (en) * | 2016-01-19 | 2018-08-03 | 微软技术许可有限责任公司 | Use the versioned record management for restarting period |
| CN108810041A (en) * | 2017-04-27 | 2018-11-13 | 华为技术有限公司 | A kind of data write-in of distributed cache system and expansion method, device |
| CN107729623A (en) * | 2017-09-22 | 2018-02-23 | 深圳航天科技创新研究院 | More people concurrent modeling method, system and storage mediums |
| CN110209383A (en) * | 2019-06-12 | 2019-09-06 | 广东省华系智能系统有限公司 | Ubiquitous object interaction interface method towards general manufacture and edge calculations |
Non-Patent Citations (1)
| Title |
|---|
| 周瑞亮.基于对象模型操作系统的软件总线的设计与实现.《中国优秀硕士学位论文全文数据库 信息科技辑》.2021,(第1期),I138-420. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112083914A (en) | 2020-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10768919B2 (en) | Package installation on a host file system using a container | |
| US5511196A (en) | Method and system in a data processing system for the enhancement of relationships between reference objects in an object oriented environment and a data object outside an object oriented environment | |
| CN105740048A (en) | Image management method, device and system | |
| US8156507B2 (en) | User mode file system serialization and reliability | |
| CN110119304B (en) | Interrupt processing method and device and server | |
| CN111459632A (en) | Serial port agent for calling terminal application program and implementation method | |
| CN108536617A (en) | Buffer memory management method, medium, system and electronic equipment | |
| CN110321374A (en) | Standard file I/O operations system and method based on distributed network | |
| CN112083914B (en) | Method and system for realizing object model embedded operation system soft bus | |
| EP1249764A2 (en) | Processor system | |
| JPH09511858A (en) | Parallel execution of requests in OSI agent | |
| CN113051244B (en) | Data access method and device, and data acquisition method and device | |
| WO2023125836A1 (en) | Method for searching target database for high-dimensional vector, and related device | |
| CN110866065A (en) | Data exchange system, exchange method and storage medium | |
| CN107357853B (en) | Method and device for operating REDIS console and computer system | |
| WO2021238583A1 (en) | Method and apparatus for operating data object, and computing device and storage medium | |
| US11153388B2 (en) | Workflow engine framework for cross-domain extension | |
| CN115277707A (en) | Service processing method, device, electronic equipment and storage medium | |
| CN111949601B (en) | Data storage method and device and computer storage medium | |
| WO2024001280A1 (en) | Data flow perception method and related apparatus | |
| CN114546274B (en) | Big data processing dimension table calculation system and method based on cache | |
| CN116760913B (en) | Method and system for issuing k8s cluster protocol conversion platform configuration | |
| CN114866609B (en) | Data interconnection and intercommunication method and device based on unified information model | |
| CN116594848B (en) | Task monitoring method, device, equipment, terminal equipment and storage medium | |
| CN116821058B (en) | Metadata access method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |