CN108804238B - Soft bus communication method based on remote procedure call - Google Patents
Soft bus communication method based on remote procedure call Download PDFInfo
- Publication number
- CN108804238B CN108804238B CN201810273776.9A CN201810273776A CN108804238B CN 108804238 B CN108804238 B CN 108804238B CN 201810273776 A CN201810273776 A CN 201810273776A CN 108804238 B CN108804238 B CN 108804238B
- Authority
- CN
- China
- Prior art keywords
- actor
- node
- message
- rpc
- model
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a soft bus communication method based on remote procedure call, which comprises the following specific steps: step one, a soft bus overall architecture is called remotely; step two, establishing an Actor model mechanism; step three, establishing a rule linked list; step four, connecting simulation nodes; and step five, starting the life cycle of the Actor. In the method, the soft bus divides a centralized bus structure based on message distribution again and distributes the bus structure among different components to form a networked bus structure, so that the communication mechanism of multi-equipment, multi-bus type and multi-bus protocol is flexibly realized, the method has the characteristics of distributed communication, strong real-time performance, Actor-Actor peer-to-peer communication and the like, supports synchronous and asynchronous communication modes, and greatly improves the communication efficiency and performance of a distributed network.
Description
Technical Field
The invention relates to the field of communication, in particular to a soft bus communication method based on remote procedure call.
Background
With the rapid development of computer simulation technology, the distributed all-digital simulation technology is increasingly perfect and widely applied. The distributed all-digital simulation technology can be applied to the whole process from a software requirement scheme stage to an integrated verification stage, the problems of the requirements and deep level in design of a distributed embedded system are found, and the safety, reliability and consistency of the system are comprehensively investigated in multiple dimensions.
In a distributed all-digital simulation test system, a soft bus is one of the key modules. The method has the main functions of realizing data communication among all-digital simulation node modules and collaborative simulation among different nodes and ensuring the execution of the whole test process. The architecture of the soft bus and the message synchronization mechanism directly affect the performance of the whole simulation test system and the final test result. At present, the traditional distributed soft bus architecture mainly meets different application requirements by increasing functions and layer number, and certain limitations exist in the application of a distributed embedded system, such as: adding part of functions can restrict the overall performance and scale of the system, the system architecture is complex and large, and the system does not support waiting for a plurality of topoic messages at the same time.
Disclosure of Invention
The present invention is directed to a method for soft bus communication based on remote procedure call, so as to solve the problems in the background art.
In order to achieve the purpose, the invention provides the following technical scheme:
a soft bus communication method based on remote procedure call comprises the following specific steps:
step one, a soft bus overall architecture is called remotely;
step two, establishing an Actor model mechanism;
step three, establishing a rule linked list;
step four, connecting simulation nodes;
and step five, starting the life cycle of the Actor.
As a further scheme of the invention: the general architecture of the soft bus comprises a network transmission layer, an RPC layer, an Actor layer and a service layer.
As a further scheme of the invention: the network transmission layer is responsible for sending a data packet from the RPC layer to a remote node through a TCP channel, monitoring a bottom TCP link, and calling back an RPC layer processing function to perform demultiplexing and distribution processing after receiving data; the RPC layer is responsible for solving the problem of remote calling, and RPC is designed to uniformly solve the problems of calling mode, information serialization, process encapsulation, customer service agent and implementation of a service stub; the Actor layer is used as a service operation container, so that the abstraction of program implementation can be effectively improved; the service layer bears the business logic of the all-digital simulation test platform.
As a further scheme of the invention: the basic elements of the Actor model mechanism are actors (actors) and messages (messages), each Actor model is provided with a message queue (mailbox), the message queues are identified by addresses, the Actor model mechanism utilizes a resource lock, a scheduling signal lamp and a schedule queue linked list to well solve the problem of safe and efficient data transmission in multithreading, the Actor model task scheduling adopts a technical method of a thread pool to realize the cooperative work of all actors, the Actor model is an independent entity, and the state and the behavior of the other party are changed through message interaction, and the Actor model comprises 4 parts of functions: model initialization, message management, task scheduling and interface service, wherein an Actor model uses ID and name as identifiers, manages a message queue in a bidirectional list mode, pops up a message from the message queue for dispatch each time, executes corresponding action according to the RPC atomic operation type, supports synchronous and asynchronous message communication among the Actor models, executes specified operation after receiving an RPC request sent by the Actor model at the opposite end, each RPC request comprises a source node, a destination node, a message size and a data address, when the Actor model receives a plurality of messages, the messages are sequentially connected in series through a node pointer to form a message queue, thereby realizing centralized management of the messages, when the messages sent by the Actor models are received, the Actor entity is inserted into a head node of a schedeuenode linked list, after the operation is completed, a thread Actor ready signal lamp is sent to a scheduler through a scheduling signal lamp, in the Actor model, the message is the most basic unit of data transfer, and all contents in the message are stored using a structure (struct).
As a further scheme of the invention: the model initialization is responsible for binding the ID and the name of the Actor model and initializing the internal state of the Actor model; the message management is responsible for defining a message queue, a scheduling queue node and a temporary Actor node; the task scheduling is responsible for receiving and forwarding the message; the interface service is responsible for managing local or remote service objects, and service inquiry and call are realized in an internal procedure call or RPC routing mode.
As a further scheme of the invention: the connection of the simulation nodes is mainly connected with the full-digital simulation nodes through RPC soft buses, and the connection establishment process is as follows: the method comprises the steps that a node with a master node function establishes monitoring (TCP connection) at a port designated by a starting parameter, the node with a slave node function actively connects a designated port of a master node under the guidance of the starting parameter, the master node waits for a slave node to send a handshake message after receiving a connection request and completes the connection, the slave node actively sends the handshake message and waits for a handshake reply, the master node verifies the handshake message after receiving the handshake reply, a data callback is replaced by a routerForwardHandler and replies the handshake reply, the slave node verifies the handshake reply and replaces the data callback by the routerForwardHandler after receiving the handshake reply, at the moment, the communication relation of network peer is converted into the communication relation of Actor peer, and the communication relation is expressed as the connection of the Actor to the Actor.
As a further scheme of the invention: the life cycle of the Actor is closely related to the management of the simulation nodes, the simulation nodes are created, the Actor is started and instantiated, the response of node starting is issued to the main node, and the routing table of the node information is updated; and (4) simulating the abnormal node, stopping the Actor, issuing the offline notification of the node to the main node, and updating the routing table of the node information.
Compared with the prior art, the invention has the beneficial effects that: in the method, the soft bus divides a centralized bus structure based on message distribution again and distributes the bus structure among different components to form a networked bus structure, so that the communication mechanism of multi-equipment, multi-bus type and multi-bus protocol is flexibly realized, the method has the characteristics of distributed communication, strong real-time performance, Actor-Actor peer-to-peer communication and the like, supports synchronous and asynchronous communication modes, and greatly improves the communication efficiency and performance of a distributed network.
Drawings
FIG. 1 is a block diagram of a RPC soft bus architecture in a remote procedure call-based soft bus communication method.
FIG. 2 is a flowchart illustrating the initialization of the RPC layer in the remote procedure call based soft bus communication method.
Fig. 3 is a schematic process diagram of connecting simulation nodes in the soft bus communication method based on remote procedure call.
Fig. 4 is a message passing process diagram of an Actor model in the remote procedure call-based soft bus communication method.
Fig. 5 is a diagram of a message queue structure of an Actor model in a remote procedure call-based soft bus communication method.
FIG. 6 is a general flow chart of the soft bus of the RPC layer in the soft bus communication method based on the remote procedure call.
Fig. 7 is a state transition diagram of an Actor lifecycle in a remote procedure call based soft bus communication method.
Detailed Description
The technical solution of the present patent will be described in further detail with reference to the following embodiments.
Referring to fig. 1-7, a method for soft bus communication based on remote procedure call includes the following steps:
the method comprises the steps that firstly, a soft bus overall architecture is called remotely, the soft bus overall architecture comprises a network transmission layer, an RPC layer, an Actor layer and a service layer, the network transmission layer is responsible for sending a data packet from the RPC layer to a remote node through a TCP channel, meanwhile, a bottom TCP link is monitored, and after data are received, an RPC call-back layer processing function is used for carrying out demultiplexing distribution processing. The network transmission layer is realized by a high-performance cross-platform network library Libuv. The Libuv has the characteristics of asynchronism, non-blocking IO and message driving, and can effectively and quickly respond to network requests. In addition, libov also provides a platform-independent timer implementation, which can be used as a timer message source of the whole system; the RPC layer is responsible for solving the problem of remote invocation. The distributed architecture has the characteristic of calling diversity, so that RPC is designed to uniformly solve the problems of calling mode, information serialization, process encapsulation, customer service agent and service stub implementation and the like, in order to ensure the normal operation of the functions of all full-digital simulation nodes, all nodes of an RPC layer in the distributed full-digital simulation system must firstly complete system initialization, and the specific flow is as follows: after the system is started, a program loads an RPC subsystem and a plug-in management subsystem, each module respectively processes starting parameters of the RPC subsystem, the RPC subsystem mainly sets functions of node numbers and monitoring ports of the RPC subsystem, whether upper nodes are connected or not, the plug-in management subsystem sets a directory where plug-ins are located, which plug-ins need to be loaded and the like, the RPC subsystem is initialized, node names are set, network sub-threads are started, an Actor processing thread pool is started, and an Actor is generated according to the RPC starting parameters. If the node is the main node, monitoring is carried out; if the node is a child node, connecting to the main node, issuing the current node, initializing the plug-in subsystem: loading the plug-ins required by the command line, initializing, operating the plug-ins required by the command line, waiting for the exit event of the user, and finishing initialization; the Actor layer is used as a container for service operation, on one hand, the Actor layer is an intermediate link of message routing in the whole message layer architecture and has the function of RPC addressing. On the other hand, each Actor runs in an independent thread, has relatively independent program design and running environment, and can effectively improve the abstraction of program implementation; the service layer carries the business logic of the test platform. In the test platform, two service components are mainly included: deploying a service. The deployment service responds to the relevant commands of the deployment script and completes the functions of node creation, component instantiation, component parameter setting, component connection and the like. Device management services. Responding to an equipment registration command when the equipment management service response component instantiates, and responding to addressing operation and message receiving and sending operation among the equipment components when the test platform runs;
and secondly, establishing an Actor model mechanism, wherein basic elements of the Actor model are an Actor (Actor) and a message (message), the Actor model mechanism has the main function of processing the message, each Actor model has a message queue (mailbox), and the message queues are identified by addresses. And after the Actor model is created, forming a unique mailbox. Each Actor model is composed of a plurality of variables and methods, the variables form internal states after instantiation, and the methods form external interfaces. The Actor model is an independent entity, changes the state and the behavior of the other party through message interaction, and mainly comprises 4 parts of functions: model initialization, message management, task scheduling, interface services. When the Actor model receives a plurality of messages, the messages are sequentially connected in series through the node pointers to form a message queue, and the centralized management of the messages is realized. When receiving messages sent by a plurality of Actor models, the Actor entities are inserted into the head nodes of the scheduledQueueNode linked list, in order to prevent deadlock in the operation process, the locking and unlocking functions are added, and after the operation is completed, the dispatcher threads are informed of Actor readiness through a scheduling signal lamp. The problem of safe and efficient data transmission in multithreading is well solved by using the resource lock, the scheduling signal lamp and the schedule queue node linked list. The structure of Actor mainly defines the status, method, and the like of Actor. When an Actor is created, the ID and name of the Actor are bound first as the identifier of the Actor. Through locking and unlocking operations, the fact that at most one thread operates the Actor at the same time is guaranteed, and the situation that multiple threads access the Actor at the same time to cause deadlock is prevented. The status identification of the Actor task is encapsulated in the structure body, so that the Actor is prevented from being still scheduled when the message queue is empty, and the execution efficiency of the scheduling thread is improved. In addition, an Actor handler class is encapsulated and used for processing the atomic operation of the Actor, and the functions of the Actor such as starting, stopping, accessing and the like are realized. And the Actor model task scheduling adopts a technical method of a thread pool, so that the cooperative work of all actors is realized. And according to the core number and the simulation performance of the CPU of the host, the number of the threads is 4, and the management function of the thread pool is realized through a gSchedThread global array. The technology creates a series of idle threads in advance, and when the threads need to be used, idle threads are directly obtained from a thread pool, so that the process of creating the threads is omitted, and the efficiency of executing the program is improved. After the threads in the thread pool are used, the threads can be recovered for the next use; when the Actor model receives a plurality of messages, the messages are sequentially connected in series through the node pointers to form a message queue, and the centralized management of the messages is realized. When receiving messages sent by a plurality of Actor models, inserting the Actor entities into the head nodes of the scheduledQueueNode linked list, and sending ready notice of the Actor to the scheduler thread through the scheduling signal lamps after the operation is finished. In the Actor model, a message is the most basic unit of data transmission, and all contents in the message are stored using a structure (struct). The definition of the message is as follows:
and step three, establishing a rule linked list, wherein each all-digital simulation node and the RPC soft bus are connected through a TCP/IP network in the distributed all-digital simulation test platform. Each emulation node forms a mapping with the IP address and a hash value of a key, which is an m-bit binary string (key) of the port. When the simulation node needs to establish the theme, the simulation node registers to the RPC soft bus and sends (key, ip) to the RPC soft bus server, and the server maintains a rule linked list of the all-digital simulation node issuing theme for receiving and forwarding data in the communication link. If the all-digital simulation node N1 is created, issuing theme information T to the RPC server; when the all-digital simulation node N2 needs to subscribe the topic T, after a query request is sent to the RPC server, the simulation node N2 is changed into a Suspending state until the topic information is received, the simulation node is activated and changed into a Running state, meanwhile, the IP information of a topic T publishing node is received and stored to the node, and the publishing/subscribing process of the topic information is completed;
and step four, connecting the simulation nodes, connecting the all-digital simulation nodes through an RPC soft bus, establishing a 'physical' channel for transmitting an Actor message, and realizing the communication of Actor-Actor peer. Firstly, a main node is created, and is in a Listen state after the main node is completed, and the information of a specified port is monitored. And deploying the slave node, initiating a connect request to the master node, changing the master node into a Handshake state, and waiting for the other side to send a Handshake signal. After receiving the handshake signals, the master node is in a Verify state, verifies the handshake signals, replaces data, and sends a reply message to the opposite side to complete RPC connection between the nodes;
step five, starting an Actor lifecycle, wherein the Actor lifecycle is closely linked with the management of the simulation node, after the RouteActor receives a start command or the software needs to use a local Actor, a corresponding Actor instance is generated, a synchronous interface is called to issue service in the context of a local caller, after the Actor receives a start event, a start event call-back is completed in the Actor scheduling context, and after the Actor is started, service logic processing is completed in the Actor scheduling context; for example, the service ID, method parameter are acquired from the request parameter. Calling a callback function corresponding to the service; and when the operation code is a Call, packing the return result of the callback function into an RPC data format, replying to a caller, completing the stop operation of the Actor after receiving the stop command by the RouteActor, calling the stop event callback of the Actor, and completing the offline event notification of other actors.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.
Claims (6)
1. A soft bus communication method based on remote procedure call is characterized by comprising the following specific steps:
step one, a soft bus overall architecture is called remotely;
step two, establishing an Actor model mechanism;
step three, establishing a rule linked list;
step four, connecting simulation nodes;
step five, starting the life cycle of the Actor;
the Actor (Actor) and the message (message) are basic elements of the Actor model mechanism, each Actor model is provided with a message queue, the message queues are identified by addresses, the Actor model mechanism utilizes a resource lock, a scheduling signal lamp and a schedule queue linked list to well solve the problem of safe and efficient data transmission in multithreading, the Actor model task scheduling adopts a thread pool technical method to realize the cooperative work of all actors, the Actor model is an independent entity, the state and the behavior of the other party are changed through message interaction, and the Actor model comprises 4 parts of functions: model initialization, message management, task scheduling and interface service, wherein an Actor model uses ID and name as identifiers, manages a message queue in a bidirectional list mode, pops up a message from the message queue for dispatch each time, executes corresponding action according to the RPC atomic operation type, supports synchronous and asynchronous message communication among the Actor models, executes specified operation after receiving an RPC request sent by the Actor model at the opposite end, each RPC request comprises a source node, a destination node, a message size and a data address, when the Actor model receives a plurality of messages, the messages are sequentially connected in series through a node pointer to form a message queue, thereby realizing centralized management of the messages, when the messages sent by the Actor models are received, the Actor entity is inserted into a head node of a schedeuenode linked list, after the operation is completed, a thread Actor ready signal lamp is sent to a scheduler through a scheduling signal lamp, in the Actor model, the message is the most basic unit of data transfer, and all contents in the message are stored using a structure (struct).
2. The remote procedure call based soft bus communication method of claim 1, wherein the soft bus overall architecture comprises a network transport layer, an RPC layer, an Actor layer and a service layer.
3. The method of claim 2, wherein the network transport layer is responsible for sending packets from the RPC layer to the remote node via a TCP channel, monitoring underlying TCP links, and calling back RPC layer processing functions for demultiplexing and distribution processing after receiving data; the RPC layer is responsible for solving the problem of remote calling, and RPC is designed to uniformly solve the problems of calling mode, information serialization, process encapsulation, customer service agent and implementation of a service stub; the Actor layer is used as a service operation container, so that the abstraction of program implementation can be effectively improved; the service layer bears the business logic of the all-digital simulation test platform.
4. The remote procedure call based soft bus communication method according to claim 1, wherein the model initialization is responsible for binding an Actor model ID and name, initializing a state inside the Actor model; the message management is responsible for defining a message queue, a scheduling queue node and a temporary Actor node; the task scheduling is responsible for receiving and forwarding the message; the interface service is responsible for managing local or remote service objects, and service inquiry and call are realized in an internal procedure call or RPC routing mode.
5. The method according to claim 1, wherein the simulation nodes are connected to the full-digital simulation node mainly through RPC soft bus, and the connection establishment process is as follows: the method comprises the steps that monitoring is established on a port designated by starting parameters by a node with a master node function, TCP connection is adopted, the node with a slave node function is actively connected with a designated port of a master node under the guidance of the starting parameters, the master node waits for a slave node to send a handshake message after receiving a connection request and completes connection, the slave node actively sends the handshake message and waits for a handshake reply, the master node verifies the handshake message after receiving the handshake reply, a data callback is replaced by a routerForwardHandler and replies the handshake reply, the slave node verifies the handshake reply and replaces the data callback by the routerForwardHandler after receiving the handshake reply, at the moment, the peer-to-peer communication relationship of a network is converted into the peer-to-peer communication relationship of an Actor, and the communication relationship is expressed as the connection of the Actor to the Actor.
6. The soft bus communication method based on remote procedure call according to claim 1, wherein the life cycle of the Actor is closely linked with the management of the simulation node, the simulation node is created, the Actor is started and instantiated, a response of node start is issued to the master node, and a routing table of node information is updated; and (4) simulating the abnormal node, stopping the Actor, issuing the offline notification of the node to the main node, and updating the routing table of the node information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810273776.9A CN108804238B (en) | 2018-03-29 | 2018-03-29 | Soft bus communication method based on remote procedure call |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810273776.9A CN108804238B (en) | 2018-03-29 | 2018-03-29 | Soft bus communication method based on remote procedure call |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108804238A CN108804238A (en) | 2018-11-13 |
| CN108804238B true CN108804238B (en) | 2022-03-04 |
Family
ID=64094706
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810273776.9A Active CN108804238B (en) | 2018-03-29 | 2018-03-29 | Soft bus communication method based on remote procedure call |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108804238B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109587235A (en) * | 2018-11-30 | 2019-04-05 | 深圳市网心科技有限公司 | A kind of data access method based on network library, client, system and medium |
| CN110430073B (en) * | 2019-07-30 | 2022-06-21 | 中国工程物理研究院计算机应用研究所 | Heterogeneous system automatic operation and maintenance method based on abstract service atomic operation |
| CN110967621A (en) * | 2019-11-11 | 2020-04-07 | 北京中电华大电子设计有限责任公司 | SE chip test design method based on Actor model |
| CN113722002A (en) * | 2020-05-26 | 2021-11-30 | 网神信息技术（北京）股份有限公司 | Method and system for obtaining command line parameters, electronic device and storage medium |
| CN112422681B (en) * | 2020-11-18 | 2023-01-13 | 中盈优创资讯科技有限公司 | Cross-platform distributed communication calling method and device |
| CN112631577B (en) * | 2021-03-10 | 2021-05-28 | 北京瑞莱智慧科技有限公司 | Model scheduling method, model scheduler and model safety test platform |
| CN114816792B (en) * | 2022-04-20 | 2024-04-09 | 北京计算机技术及应用研究所 | Remote function calling method based on special channel |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103124981A (en) * | 2010-07-08 | 2013-05-29 | 情报通信产业振兴院 | Electronic document distribution system and electronic document distribution method |
| CN103473031A (en) * | 2013-01-18 | 2013-12-25 | 龙建 | Cooperative concurrent message bus, driving member assembly model and member disassembly method |
| CN104426800A (en) * | 2013-08-22 | 2015-03-18 | 塔塔顾问服务有限公司 | System and method for managing message queues in a peer-to-peer communication network |
| CN105335221A (en) * | 2015-10-09 | 2016-02-17 | 中国电子科技集团公司第二十九研究所 | Reconstructible distributed software bus |
| CN105488186A (en) * | 2015-12-01 | 2016-04-13 | 徐红伟 | Decentralized distributed credit investigation inquiry release method |
| CN105491123A (en) * | 2015-12-04 | 2016-04-13 | 北京航空航天大学 | Communication method and device among containers |
| WO2016134380A1 (en) * | 2015-02-20 | 2016-08-25 | Pristine Machine, LLC | Method to split data operational function among system layers |
| CN106850321A (en) * | 2017-04-05 | 2017-06-13 | 无锡华云数据技术服务有限公司 | A kind of simulated testing system of cluster server |
| CN106874130A (en) * | 2017-02-06 | 2017-06-20 | 西多多信息科技(北京)有限公司 | The processing method of distributed transaction in a kind of micro services framework |
| CN106888129A (en) * | 2017-04-20 | 2017-06-23 | 国家电网公司 | It is a kind of can elastic telescopic distributed service management system and its method |
| CN106953848A (en) * | 2017-02-28 | 2017-07-14 | 浙江工商大学 | A kind of software defined network implementation method based on ForCES |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10382587B2 (en) * | 2015-06-26 | 2019-08-13 | International Business Machines Corporation | De-duplicating remote procedure calls |
| CN106850829B (en) * | 2017-02-28 | 2019-11-22 | 苏州星熙数据科技有限公司 | A kind of micro services design method based on non-blocking communication |
-
2018
- 2018-03-29 CN CN201810273776.9A patent/CN108804238B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103124981A (en) * | 2010-07-08 | 2013-05-29 | 情报通信产业振兴院 | Electronic document distribution system and electronic document distribution method |
| CN103473031A (en) * | 2013-01-18 | 2013-12-25 | 龙建 | Cooperative concurrent message bus, driving member assembly model and member disassembly method |
| CN104426800A (en) * | 2013-08-22 | 2015-03-18 | 塔塔顾问服务有限公司 | System and method for managing message queues in a peer-to-peer communication network |
| WO2016134380A1 (en) * | 2015-02-20 | 2016-08-25 | Pristine Machine, LLC | Method to split data operational function among system layers |
| CN105335221A (en) * | 2015-10-09 | 2016-02-17 | 中国电子科技集团公司第二十九研究所 | Reconstructible distributed software bus |
| CN105488186A (en) * | 2015-12-01 | 2016-04-13 | 徐红伟 | Decentralized distributed credit investigation inquiry release method |
| CN105491123A (en) * | 2015-12-04 | 2016-04-13 | 北京航空航天大学 | Communication method and device among containers |
| CN106874130A (en) * | 2017-02-06 | 2017-06-20 | 西多多信息科技(北京)有限公司 | The processing method of distributed transaction in a kind of micro services framework |
| CN106953848A (en) * | 2017-02-28 | 2017-07-14 | 浙江工商大学 | A kind of software defined network implementation method based on ForCES |
| CN106850321A (en) * | 2017-04-05 | 2017-06-13 | 无锡华云数据技术服务有限公司 | A kind of simulated testing system of cluster server |
| CN106888129A (en) * | 2017-04-20 | 2017-06-23 | 国家电网公司 | It is a kind of can elastic telescopic distributed service management system and its method |
Non-Patent Citations (2)
| Title |
|---|
| "Agent-based manufacturing execution systems for short-series production scheduling";Rafal Cupek;《Computers in Industry》;20161031;第82卷;第245-258页 * |
| "基于分层模型的半实物仿真测试平台设计";高峰;《计算机工程》;20180115;第44卷(第1期);第106页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108804238A (en) | 2018-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108804238B (en) | Soft bus communication method based on remote procedure call | |
| CN110716748B (en) | Service processing method, device, computer readable medium and electronic equipment | |
| CN107590072B (en) | Application development and test method and device | |
| CN106850829B (en) | A kind of micro services design method based on non-blocking communication | |
| CN105472042A (en) | WEB terminal controlled message middleware system and data transmission method thereof | |
| CN104753817A (en) | Local analogy method and local analogy system for cloud computing message queue service | |
| CN111381983A (en) | Lightweight message middleware system and method of virtual test target range verification system | |
| US9164819B2 (en) | Composing message processing pipelines | |
| JP2005267118A (en) | Interprocessor communication system and program in parallel processing system using os for single processor | |
| CN113535362B (en) | Distributed scheduling system architecture and micro-service workflow scheduling method | |
| WO2021043124A1 (en) | Kbroker distributed operating system, storage medium, and electronic device | |
| WO2023246398A1 (en) | Cloud service implementation method and apparatus | |
| CN112230987A (en) | System and method for realizing distributed modular plug-in framework | |
| CN112698838A (en) | Multi-cloud container deployment system and container deployment method thereof | |
| CN115248692A (en) | Device and method for supporting cloud deployment of multiple deep learning framework models | |
| CN103677853A (en) | Method for achieving HIT-TENA middleware in DM642 type DSP | |
| CN106909368B (en) | Service-side service layer logic architecture for realizing rapid service development | |
| WO2023151503A1 (en) | Handle management or communication method, electronic device, storage medium and program product | |
| US10379918B2 (en) | System and method for MPI implementation in an embedded operating system | |
| JP5371613B2 (en) | Service linkage device | |
| CN102681881B (en) | Across machine dispatching method and system thereof | |
| CN109669793B (en) | Object calling method in middleware process | |
| Chen et al. | Research on client/server communication mechanism in autosar system | |
| CN115509146B (en) | Distributed communication resource integration method for flight maintenance simulator | |
| CN116016679A (en) | Cloud primary service communication 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 |