CN107171918B - Message transceiving method in GJB289A bus module supporting priority - Google Patents
Message transceiving method in GJB289A bus module supporting priority Download PDFInfo
- Publication number
- CN107171918B CN107171918B CN201710282861.7A CN201710282861A CN107171918B CN 107171918 B CN107171918 B CN 107171918B CN 201710282861 A CN201710282861 A CN 201710282861A CN 107171918 B CN107171918 B CN 107171918B
- Authority
- CN
- China
- Prior art keywords
- message
- messages
- cache
- receiving
- urgent
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40143—Bus networks involving priority mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/6215—Individual queue per QOS, rate or priority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
- H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40267—Bus for use in transportation systems
- H04L2012/4028—Bus for use in transportation systems the transportation system being an aircraft
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Communication Control (AREA)
Abstract
The invention provides a message transceiving method in a GJB289A bus module supporting priority, when a bus interface module serves as a BC, the bus interface module independently creates a cache for a high-priority message to ensure that the high-priority message is sent preferentially. The receiving adopts a second-level cache form, and the first-level cache adopts a receiving large queue form, so that the time sequence of message receiving is ensured. The second-level cache adopts a pointer mode, so that the classification of the messages according to different priorities is ensured, and the message cache does not occupy excessive memory space; meanwhile, different receiving modes are adopted for messages with different priorities, an interrupt receiving mode is adopted for emergency messages with high priorities, and an inquiry mechanism is adopted for receiving periodic messages with common priorities. When the user needs to extract the message according to the received message sequence, the user can select to extract the message from the first-level cache. When the user needs to extract the message according to the message priority, the user can choose to extract the message from the second-level cache.
Description
Technical Field
The present invention relates to bus technology, and more particularly, to a message transmission and reception technology in a bus module.
Background
The bus network GJB289A (MIL-STD-1553B) in the field of avionics has been widely applied in the field of avionics for many years, but in an onboard avionics network and an avionics comprehensive laboratory, the existing GJB289A bus module has no priority for message transceiving, and the message transceiving effect is influenced.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method capable of supporting message prioritization in a GJB289A bus module for receiving and sending.
The technical scheme adopted by the invention for solving the technical problems is that the message receiving and sending method in the GJB289A bus module supporting the priority comprises the following steps:
1) a sending step: the bus interface module MBI correspondingly puts the message to be sent into three types of sending caches for storage, wherein the three types of sending caches are as follows: an emergency message cache, an asynchronous message cache and a common message cache;
the emergency message cache stores emergency messages, the priority is highest, and when the emergency message cache is not empty, the bus interface module preferentially sends message contents in the emergency message cache to the GJB289A bus;
the asynchronous message cache stores asynchronous messages, the priority is higher than that of the common messages and lower than that of the emergency messages, and the bus interface module sends the asynchronous messages to a GJB289A bus according to the fixed asynchronous period of the asynchronous messages;
the common message cache stores common messages, the common messages are bus messages with common priority, a double-data cache form is adopted, idle caches are preferentially selected to store messages, and when no message needs to be sent in the emergency message cache and the asynchronous message cache, the bus interface module sends data in the double caches to a GJB289A bus in a ping-pong switching mode;
2) a receiving step: the receiving management of the bus interface module adopts a two-level cache form; the first-level cache stores messages according to a receiving time sequence, the second-level cache only stores message pointers and is divided into an urgent message pointer queue and a non-urgent message pointer queue group according to the priority of the messages; the non-urgent message pointer queue group comprises more than 2 non-urgent message pointer queues, and the non-urgent message pointer queues are distinguished according to different MsgIDs; storing the pointers of the urgent messages in an urgent message pointer queue according to a receiving time sequence, and storing the pointers of the non-urgent messages in a corresponding non-urgent message pointer queue according to the MsgID; the emergency message adopts an interrupt receiving mode, and the non-emergency message adopts an inquiry receiving mode; the non-urgent messages include asynchronous messages and normal messages.
The invention provides a message transceiving method in a GJB289A bus module, when the bus interface module serves as a BC, the bus interface module independently creates a cache for a high-priority message to ensure that the high-priority message is sent preferentially. The receiving adopts a second-level cache form, and the first-level cache adopts a receiving large queue form, so that the time sequence of message receiving is ensured. The second-level cache adopts a pointer mode, so that the classification of the messages according to different priorities is ensured, and the message cache does not occupy excessive memory space; meanwhile, different receiving modes are adopted for messages with different priorities, an interrupt receiving mode is adopted for emergency messages with high priorities, and an inquiry mechanism is adopted for receiving periodic messages with common priorities. When the user needs to extract the message according to the received message sequence, the user can select to extract the message from the first-level cache. When the user needs to extract the message according to the message priority, the user can choose to extract the message from the second-level cache. Therefore, differentiated message extraction is carried out according to different requirements of users, the receiving time sequence of the messages can be ensured, and the requirement that the users extract the messages with high priority preferentially can be met.
The invention has the beneficial effect of ensuring that the high-priority message is sent and received preferentially.
Drawings
FIG. 1 is a diagram of a transmit message queue;
FIG. 2 is a diagram of a receive message queue;
FIG. 3 is a schematic diagram of a process for transmitting data by MBI as BC;
FIG. 4 is a diagram illustrating the reception and transmission of MBI as RT;
FIG. 5 is a diagram illustrating the reception of MBI as BM;
FIG. 6 is a control flow diagram of MBI as BC;
FIG. 7 is a control flow diagram of MBI as RT;
fig. 8 is a control flow chart of MBI as BM.
Detailed Description
For convenience of description, the english abbreviation appears in the text:
MsgID: a message identifier;
ICD: an interface control file;
MBI: a bus interface module;
RT: a remote terminal;
BC: a bus controller;
BM: a bus monitor.
A GJB289A bus module supporting priority is composed of a message sending part and a message receiving part.
1 differentiating transmission buffer management according to message priority
As shown in fig. 1, when MBI is used as BC, MBI applies for three types of cache, an urgent message cache, an asynchronous message cache, and a general message cache, respectively, according to different message transmission priorities.
The emergency message cache stores emergency messages, when the application software sends the emergency messages, the messages are stored in the emergency message cache, the priority of the emergency messages is highest, and when the emergency message cache is not empty, the message contents in the emergency message cache are sent preferentially; the asynchronous message cache stores asynchronous messages, and each asynchronous message sends the asynchronous message according to a fixed asynchronous period of the message; the common message cache stores common messages, the common messages are bus messages with common priority, and a double-data cache mode is adopted.
The three message caches are arranged in an FPGA firmware program of the MBI, the FPGA firmware program polls the empty and full states of the three caches according to a high-speed clock period, the priority of the emergency message is highest, when the emergency message cache is not empty, the message in the emergency message queue is sent to a transceiver module at the first moment, and the transceiver module sends the message to a GJB289A bus. Asynchronous message priority second, when there is both an asynchronous message and a normal message, the asynchronous message is preferentially transmitted. The common message cache adopts double-cache management, when an application sends a common message, a firmware program preferentially selects an idle cache to store the message, and when neither the emergency message cache nor the asynchronous message cache has the message to be sent, the common message double-cache adopts a ping-pong switching mode to send data to a GJB289A bus through a transceiver.
2, according to the requirement of receiving message, receiving the second-level buffer for managing the receiving queue.
As shown in fig. 2, the receive queue manages messages using a level two cache, and the user may choose to retrieve messages from either the level one or the level two cache. When the user needs to extract the message according to the received message sequence, the message can be selected to be extracted from the first-level cache. When a user desires to extract messages according to message priority, the user may choose to extract messages from the second level cache. The first-level cache completely ensures that the message is stored according to the message receiving time sequence, and the message is directly extracted from the first-level cache, so that the receiving time sequence of the message can be ensured. For example, when acting as a BM, the user is concerned with the timing of receiving messages, so when acting as a BM mode, messages can be directly extracted from the first level cache.
The second-level cache is divided into an urgent message queue and a non-urgent message queue group according to different priorities of the messages. Only the address information of the real data is stored in the two queues. Not occupying too much memory.
The emergency message queue does not need to be divided into queues according to the MsgID, all emergency messages are stored in the emergency message queue according to the receiving time sequence, and non-emergency messages are managed according to different MsgID divided queues. The non-urgent messages include asynchronous messages and bus messages of general priority.
The receiving of the urgent message adopts an interruption mode, so that the application software can receive the urgent message at the first time after receiving the urgent message, and for the non-urgent message, the application software actively inquires and performs corresponding receiving operation.
The storage and extraction modes of the received cached messages are as follows:
the storage space of each message in the first-level cache is of a fixed length, the space of each message cache can be regarded as a unit, and each unit is provided with a mark quantity to indicate that the unit is in an empty state or a full state. When MBI receives bus message, it searches the first level 'unit' buffer circularly, when it finds the first 'unit' buffer in 'empty' state, it stores the message into the 'unit' buffer, then the 'unit' buffer is set to 'full' state, then establishes the second level buffer queue according to the priority of the message, if the message is urgent, it stores the pointer of the message into the urgent message pointer queue of the second level buffer, at the same time, it sets an interrupt signal, the upper layer application starts to extract the urgent message after receiving the interrupt signal. If the message is a non-urgent message, storing its pointer in a corresponding non-urgent message MsgID pointer queue according to the MsgID of the message. The storage is repeated in a circulating way.
After receiving the emergency message extraction interrupt signal, the application software directly finds the emergency message pointer from the emergency message pointer queue of the second-level cache, finds the actual storage position of the emergency message in the first-level cache through the pointer, extracts the message from the unit cache of the message in the first-level cache, and then sets the state of the unit cache to be in an empty state. The extraction of the urgent message is repeated in this manner.
The application software periodically queries the MsgID pointer queue of the non-urgent message in the second-level cache, when a certain MsgID pointer queue is found to be non-empty, a corresponding message extraction interface is called, a pointer of the message is found from the MsgID pointer queue, the actual storage position of the message in the first-level cache is found through the pointer, the message is extracted from the 'unit' cache of the message in the first-level cache, and then the 'unit' cache state is set to be an 'empty' state. The extraction of the non-urgent message is repeated in this manner.
Because the received messages are sorted again according to the priority level during the second-level cache, in order to reduce the memory consumption, the second-level cache queue adopts a pointer queue form, and the actual storage space of the messages is still in the first-level cache. Therefore, the messages in the first-level cache become discrete caches, so that the first-level cache adopts a unit management mode to update the empty and full states in real time and recycle the unit cache.
According to the GJB289A protocol, 11 bits of the command word are left to describe a message in addition to the "data word count" 5 bits, and there are at most 2^11(2048) messages, so there are at most 2048 message IDs. 2048 message queue sets are established for the regular messages.
The method can adopt an interrupt mode for receiving the urgent message, software starts to extract the message after receiving an interrupt signal, and for the non-urgent message, the application software actively inquires and carries out corresponding receiving operation for the non-urgent message. .
The normal work of the MBI sending message as BC needs five configuration tables for matching use, which are respectively as follows: a message name to MsgID mapping table; a MsgID to command word (CMD) mapping table; a sub-address to vector word mapping table; interface control parameter definition table; and a bus table.
Message name to MsgID mapping table: and the corresponding relation between the message name of the ICD and the MsgID is described. The total number N of the messages is contained; the number n of the emergency messages; message name description and MsgID description of n urgent messages; message name descriptions and MsgID descriptions for N-N messages.
MsgID and CMD mapping table: for describing the correspondence of the MsgID and the message command word. The total number N of the messages is contained; the number n of the emergency messages; the MsgID description and CMD description of n urgent messages; MsgID description and CMD description of N-N non-urgent messages.
Sub-address to vector word mapping table: the method is used for describing the vector digit number corresponding to each sub-address corresponding to each terminal. The number of the terminals N is included; the vector words of the N terminals are described using patterns.
Interface control parameter definition table: for storing configuration information for bus messages. Including the RT device number; a message transmission interval; a status word response time interval; a status word response timeout threshold; dt (device timer) clock base value; a clock load value of WDT1(Watchdog Timer); remote load value of WDT 2; terminal parameter definition (including valid terminal number, terminal attribute); the message name and the version number of the MsgID mapping table; MsgID and the version number of the command word mapping table; the sub-address and vector word mapping table version number; the sub-address and vector word mapping table version number; interface control parameter definition table version number;
a bus meter: the method is used for describing an emergency message table, a periodic message table and an asynchronous message table. Including the number of emergency messages; emergency message content; the number of periodic messages; a small period value; the number of small cycles; periodic message content; number of asynchronous messages, content of asynchronous messages;
1) data transmission of the BC is as shown in FIG. 3, when the MBI serving as the BC is powered on, the FPGA firmware program reads a configuration file from the FLASH MEM module and uploads a message name and an MsgID mapping table to application software; storing the emergency message table, the asynchronous message table and the non-emergency message table into a message cache module according to the mapping relation between the MsgID and the command word mapping table; reading the content of the mapping table of the correspondence between the subaddress and the vector word and storing the content into a message refreshing module;
when the application software has message refreshing, the corresponding MsgID of the message name is found through the message name and MsgID matching module according to the corresponding relation of the message name and the MsgID mapping table, and the software issues a message to the MsgID and command word matching module according to the MsgID.
And after receiving the MsgID, the MsgID and command word matching module identifies the priority of the message and sends the message to the message caching module. And the message caching module finds the command word corresponding to the MsgID according to the corresponding relation between the MsgID and the command word mapping table, directly sends the message to the transceiver module if the message is an emergency message or an asynchronous message, and sends the message to the message refreshing module to judge the refreshing state of the message if the message is a non-emergency message.
The message refreshing module firstly judges the message type after receiving the message, if the message is from BC to RT, the message refreshing mark is detected, if the message refreshing mark is set to one, the message is sent to the transceiver module, if the message is from RT to BC, the vector word mark is checked, and if the corresponding vector word position is set to 1, the message is sent to the transceiver module.
The transceiver module receives the message and then sends the message to the GJB289A bus.
The BC reception procedure is the same as RT.
2) The reception of MBI as RT and its transmission process are shown in fig. 4. When the power-on initialization is carried out, a driver extracts the MsgID and command word corresponding relation mapping table file from the FLASHMEM module and stores the MsgID and command word corresponding relation mapping table file into a corresponding data structure, the vector word updating module reads the content of the sub-address and vector word corresponding relation mapping table, and meanwhile, the clock management module reads the interface parameter definition file to carry out operations such as initializing the clock.
When receiving, the transceiver module stores all messages into a local receiving queue according to the bus message receiving time sequence, and simultaneously sets a drive interrupt to start receiving data. And the driver stores all the messages into a first-level cache of the receiving queue according to a receiving time sequence, classifies the messages according to the MsgID and the content of the command word corresponding relation mapping table taken during initialization, and stores the urgent messages and the non-urgent messages into a second-level cache of the receiving queue by using different queues.
And the messages in the second-level cache of the receiving queue are delivered to an application layer for data extraction through an MsgID and message name matching module.
When the RT is used as a sending end, application software finds the corresponding relation between the MsgIDs corresponding to the message names according to the 'message name and MsgID mapping table'. And sending the message to the MsgID and command word matching module through the MsgID and message name matching module, and sending the data word content of the message to the data word storage module according to the MsgID and command word mapping table and the constraint on the RT address and the subaddress in the command word. At the moment, the vector word updating module updates the vector words according to the data updating information of the data word storage module and by combining the sub-addresses read during power-on initialization and the corresponding relation file contents of the vector words.
3) As the MBI of the BM, it only needs to receive messages, and as shown in fig. 5, the upload message is a message of the first-level cache arranged according to the received message timing sequence. BM messages are written and stored while being uploaded and applied to display and process messages, so that data playback is facilitated.
The following description of the messaging flow of MBI as BC, RT, BM respectively:
1) MBI as BC:
as shown in fig. 6, the sending message buffer controller module is connected to the PC interface, and receives a message that is refreshed by an application and writes the message into the message buffer, and the sending message buffer controller is connected to the message sending scheduling controller module, which controls scheduling of message sending. The bus table controller module and the asynchronous table controller module are connected with a message sending scheduling controller, the scheduler module reads messages of a message sending cache under the cooperation of the bus table controller and the asynchronous table controller and sends the messages to a message receiving/sending controller, the message receiving/sending controller sends the messages to a coder-decoder module when sending the messages to generate message coded data to be sent to a bus, after the coder-decoder receives the messages from the bus, the messages are sent to a message receiving cache controller by the message sending/receiving controller, the message receiving cache controller searches for a MsgID and CMD mapping table and stores the messages to a message receiving large queue. When the application reads the message, the receiving message cache controller reads the message from the receiving message large queue and sends the message to the PC end interface.
2) MBI as RT:
as shown in fig. 7, the PC application refreshes the data word to the data word cache management module through the interface, and the data word cache management module temporarily stores the refreshed message into the data word cache. When the data word is read by the message receiving and transmitting processing controller module connected with the data word buffer management module, the data word buffer management module reads out the message in the data word buffer and transmits the message to the message receiving and transmitting processor, and the message receiving and transmitting processor transmits the message to be transmitted to the coder-decoder to generate the coded data and transmits the coded data to the bus. When the codec receives the message on the bus and sends the message to the message transceiver controller, the corresponding message is sent to the RT receiving cache controller according to the receiving processing rule, and the receiving cache controller sequentially puts the message into the message receiving cache. When the application needs to read the message, the message data is extracted from the message receiving cache through the PC and the equipment interface. The received message is sent to a hardware watchdog of the WDT controller module control device after the message content is extracted in the messaging controller, and an interrupt signal is provided for the application.
3) MBI as BM:
as shown in fig. 8, the BM bus monitor module is mainly a terminal for monitoring bus information, and the codec decodes the message from the bus and sends the message to the BM message receiving and processing controller, the controller sends the message and the message attribute to the message receiving and buffering controller according to the message type, and the message receiving and buffering controller temporarily stores the message in the message receiving and buffering controller. The application receives the extraction message through the PC, and the message receiving cache controller reads the message receiving cache and sends the data to the interface between the equipment and the PC to realize the extraction of the message.
Claims (1)
1. The message transceiving method in the GJB289A bus module supporting the priority is characterized by comprising the following steps of:
1) a sending step: the bus interface module MBI correspondingly puts the message to be sent into three types of sending caches for storage, wherein the three types of sending caches are as follows: an emergency message cache, an asynchronous message cache and a common message cache;
the emergency message cache stores emergency messages, the priority is highest, and when the emergency message cache is not empty, the bus interface module preferentially sends message contents in the emergency message cache to the GJB289A bus;
the asynchronous message cache stores asynchronous messages, the priority is higher than that of the common messages and lower than that of the emergency messages, and the bus interface module sends the asynchronous messages to a GJB289A bus according to the fixed asynchronous period of the asynchronous messages;
the common message cache stores common messages, the common messages are bus messages with common priority, a double-data cache form is adopted, idle caches are preferentially selected to store messages, and when no message needs to be sent in the emergency message cache and the asynchronous message cache, the bus interface module sends data in the double caches to a GJB289A bus in a ping-pong switching mode;
2) a receiving step: the receiving management of the bus interface module adopts a two-level cache form; the first-level cache stores messages according to a receiving time sequence, the second-level cache only stores message pointers and is divided into an urgent message pointer queue and a non-urgent message pointer queue group according to the priority of the messages; the non-urgent message pointer queue group comprises more than 2 non-urgent message pointer queues, and the non-urgent message pointer queues are distinguished according to different message identifications MsgID; storing the pointers of the urgent messages in an urgent message pointer queue according to a receiving time sequence, and storing the pointers of the non-urgent messages in a corresponding non-urgent message pointer queue according to the MsgID; the emergency message adopts an interrupt receiving mode, and the non-emergency message adopts an inquiry receiving mode; the non-urgent messages include asynchronous messages and normal messages.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710282861.7A CN107171918B (en) | 2017-04-26 | 2017-04-26 | Message transceiving method in GJB289A bus module supporting priority |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710282861.7A CN107171918B (en) | 2017-04-26 | 2017-04-26 | Message transceiving method in GJB289A bus module supporting priority |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107171918A CN107171918A (en) | 2017-09-15 |
| CN107171918B true CN107171918B (en) | 2020-06-16 |
Family
ID=59812390
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710282861.7A Active CN107171918B (en) | 2017-04-26 | 2017-04-26 | Message transceiving method in GJB289A bus module supporting priority |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107171918B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109962858B (en) * | 2017-12-25 | 2023-03-31 | 宇通客车股份有限公司 | CAN bus data transmission method and control system |
| CN110149259B (en) * | 2019-05-09 | 2021-09-14 | 中国航空工业集团公司西安航空计算技术研究所 | GJB289A bus scheduling method and device based on hybrid triggering |
| CN111510396B (en) * | 2020-06-30 | 2020-10-27 | 腾讯科技（深圳）有限公司 | Message sending method and related device |
| CN115396257A (en) * | 2022-10-31 | 2022-11-25 | 永联智慧能源科技(常熟)有限公司 | System and method for reducing battery data uploading busy degree of battery replacement station |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001268082A (en) * | 2000-03-22 | 2001-09-28 | Nec Corp | Priority controller for same destination address and its method |
| CN1804816A (en) * | 2004-12-29 | 2006-07-19 | 英特尔公司 | Method for programmer-controlled cache line eviction policy |
| CN102713852A (en) * | 2012-02-01 | 2012-10-03 | 华为技术有限公司 | Multicore processor system |
| CN107211588B (en) * | 2010-01-25 | 2014-01-01 | 西北工业大学 | The aircraft utilities system health control method of carrier wave is spread based on power line |
| CN103888293A (en) * | 2014-02-25 | 2014-06-25 | 电子科技大学 | Data channel scheduling method of multichannel FC network data simulation system |
| CN104199790A (en) * | 2014-08-21 | 2014-12-10 | 北京奇艺世纪科技有限公司 | Data processing method and device |
| CN105068864A (en) * | 2015-07-24 | 2015-11-18 | 北京京东尚科信息技术有限公司 | Method and system for processing asynchronous message queue |
-
2017
- 2017-04-26 CN CN201710282861.7A patent/CN107171918B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001268082A (en) * | 2000-03-22 | 2001-09-28 | Nec Corp | Priority controller for same destination address and its method |
| CN1804816A (en) * | 2004-12-29 | 2006-07-19 | 英特尔公司 | Method for programmer-controlled cache line eviction policy |
| CN107211588B (en) * | 2010-01-25 | 2014-01-01 | 西北工业大学 | The aircraft utilities system health control method of carrier wave is spread based on power line |
| CN102713852A (en) * | 2012-02-01 | 2012-10-03 | 华为技术有限公司 | Multicore processor system |
| CN103888293A (en) * | 2014-02-25 | 2014-06-25 | 电子科技大学 | Data channel scheduling method of multichannel FC network data simulation system |
| CN104199790A (en) * | 2014-08-21 | 2014-12-10 | 北京奇艺世纪科技有限公司 | Data processing method and device |
| CN105068864A (en) * | 2015-07-24 | 2015-11-18 | 北京京东尚科信息技术有限公司 | Method and system for processing asynchronous message queue |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107171918A (en) | 2017-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107171918B (en) | Message transceiving method in GJB289A bus module supporting priority | |
| TWI400617B (en) | Schedule and data caching for wireless transmission | |
| WO2015078219A1 (en) | Information caching method and apparatus, and communication device | |
| US11483244B2 (en) | Packet buffer spill-over in network devices | |
| US20090034549A1 (en) | Managing Free Packet Descriptors in Packet-Based Communications | |
| CN111221759B (en) | Data processing system and method based on DMA | |
| CN107786623B (en) | Message asynchronous processing method and device | |
| EP2030096A2 (en) | Data communication flow control device and methods thereof | |
| US20190196989A1 (en) | Method, Apparatus, and System for Accessing Memory Device | |
| EP2219114A1 (en) | Method and apparatus for allocating storage addresses | |
| CN101707564B (en) | Processing method and processing device for transmitting and receiving network data in zero-copy buffer queue | |
| WO2022062524A1 (en) | Memory management method and apparatus, device and storage medium | |
| KR100861692B1 (en) | Unified contents update system for mobile widget application and method thereof | |
| CN107025184B (en) | Data management method and device | |
| CN111897665A (en) | Data queue processing method and device | |
| JP4022442B2 (en) | Control method of fieldbus interface board | |
| US20200034186A1 (en) | Methods and apparatus for verifying completion of groups of data transactions between processors | |
| US10198362B2 (en) | Reducing bandwidth consumption when performing free memory list cache maintenance in compressed memory schemes of processor-based systems | |
| CN101087256B (en) | Message transmission method and system | |
| CN111201516A (en) | Message passing in data processing system | |
| US10733118B2 (en) | Computer system, communication device, and storage control method with DMA transfer of data | |
| CN103442091B (en) | Data transmission method and device | |
| WO2021087990A1 (en) | Tag updating method and device, electronic apparatus, and storage medium | |
| CN118101608A (en) | Gigabit single optical port server adapter with low data overflow | |
| CN112347030A (en) | Data processing method and system based on FPGA |
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 |