KR20030056097A - Between Boards Message Handling System and Method - Google Patents

Abstract

PURPOSE: A system and a method for communicating a message between boards are provided to communicate the data through the message between the boards embedded into the system using a compact PCI(Peripheral Component Interconnect) bus as a hardware platform by transmitting the message to the corresponding board after attaching a message header, and transmitting the message to a task to process the message. CONSTITUTION: A PCI bus switch driver(20) detects an embedment state of the board, and operates the PCI bus switch interfacing each board with the compact PCI bus. An application layer generates the data communicating with other board, and carries out a function requested by the message received from other board. An interface(30) interfaces the PCI bus switch driver(20) with the application layer, and exchanges the data to communicate with other board by attaching the mail header. The application layer comprises a function request task(471-47m) and a function perform task(431-43n).

Description

Board-to-board message communication system and method

The present invention relates to a board-to-board message communication system and method, and more particularly, to a board-to-board message that allows data to be transmitted and received through messages between boards mounted in a system having a compact Peripheral Component Interconnect (PCI) bus as a hardware platform. A communication system and method are disclosed.

When exchanging data between a host board provided in the system and an I / O board that performs actual media data processing, or between I / O boards, the LC-bus is conventionally used as a hardware platform to separate messages from actual data. Communicate between boards.

Since the LC-bus has no separate interface layer, the hardware is directly accessed by the application layer portion that performs the actual data processing. That is, the LC-bus area defined on the memory map is directly accessed by the application layer to read the message.

Here, the application layer unit needs to periodically generate a task for checking whether a message has arrived and a task for processing the arrived message.

1 is a road, a message direction field, a board number field, a port number field, a message sequence number field, a function code field, a data field, and a checksum showing the configuration of a message applied to a conventional board-to-board message communication method. It is made with a field.

The total size of the message in the format described above is 32 bytes, and no actual data is included. The actual data is in different memory areas.

When a message arrives that does not involve actual data, the task that processes the message processes only that message and waits for the next message. When a message that carries actual data arrives, the task processes the message and the memory area where the actual data exists. Access by reading and process the relevant data as well.

On the other hand, if there is data to be sent to the other board, the data is recorded in a predetermined predetermined memory area.

As described above, when transmitting a message using a conventional LC-bus, there is a burden of accessing hardware directly from the application layer. As a result, you cannot port software programs to other similar boards.

In addition, since the message format is implemented in a structure that is not scalable or universal, there is an inconvenience of changing the message structure every time the system changes.

The present invention has been made to solve the above-described problems, and when data to be exchanged with other boards is generated, a message header is created and pasted and transmitted to the corresponding board, and when a message is received from another board, the header of the message is analyzed. Its purpose is to provide an inter-board message communication system and method for transmitting and receiving data through messages by transmitting the message to a task to be processed, by using a compact PCI bus as a hardware platform. have.

1 is a view showing the configuration of a message applied to a conventional board-to-board message communication method.

Figure 2 is a diagram showing the configuration of a board-to-board message communication system according to the present invention.

3 is a view showing the configuration of a message applied to the present invention.

4 is a flowchart for explaining a board-to-board message communication method according to the present invention.

*** Explanation of symbols for the main parts of the drawing ***

10.PCI bus switch, 20. PCI bus switch driver,

30. Interface section, 33. Receive tasks,

35, 39, 45-1, 45-2,... , 45-n. Message queue,

37.Send Task, 40. Application layer,

43-1, 43-2,... , 43-n. Perform tasks,

47-1, 47-2,... , 47-n. Feature request task

The board-to-board message communication system according to the present invention for achieving the above object, the PCI bus switch driver for detecting a mounting state of the board, and operating a PCI bus switch for interfacing each board and the compact PCI bus; An application layer unit for generating data to be communicated with another board and performing a function required by a message received from another board; Interface between the PCI bus switch driver and the application layer, and the interface to perform the task of sending and receiving a message header to the data to communicate with the other board.

The application layer unit may include: a function request task of generating data to be communicated with another board and transmitting data generated using an API provided by the interface unit to another board; And a function performing task for performing a corresponding function by analyzing a port number and a function code of a message transmitted from another board through the interface unit.

If there is a message received from another board, the interface unit analyzes a message header of the received message to determine which function execution task to send to, and receives the received task of delivering the received message to the determined function execution task. Wow; If there is a message received from the function request task, it is characterized by comprising a transmission task for determining which board to send the received message to, and sending it to the determined board with the message header attached.

The message header may include a magic number for checking whether the message is a valid message; A message length indicating the size of the entire message; A send / receive board name indicating the name of the sender / receiver board; A transmit / receive board ID indicating an ID of the transmit / receive board; A transmit / receive network ID indicating a PCI bus slot number on which each board is mounted; A transmit / receive sub ID indicating a message queue number of a function performing task in which the message is processed; A transmission / reception port ID indicating a number of a port to which the message belongs; A message type indicative of the continuity of the message; And a function code indicating the purpose of the message.

On the other hand, the board-to-board message communication method according to the present invention includes the steps of generating a message to communicate with the other board in the function request task, and sending the message generated using the API of the interface unit to the transmission task; A message transmission process of determining which board to send the message received from the function request task to the transmission task, preparing a message header, attaching the message to the received message, and transmitting the message to the determined board; Determining a function performing task to which a message received from another board is to be sent in a receiving task, and sending the received message to the determined function performing task; And performing a corresponding function by analyzing a port number and a function code of a message received from the receiving task in the function performing task.

The message transmission process may include: periodically polling a message queue to determine whether a message received from a function request task exists; If there is a received message as a result of the determination, determining a board to which the received message is to be sent, preparing a message header, and attaching the received message to the received message; Characterized in that the process of transmitting the message to the determined board.

The message receiving step may include: periodically polling a message queue to determine whether a message received from another board exists; If there is a message received as a result of the determination, analyzing a message header of the received message to determine a function performing task to which the received message is to be sent; And sending the received message to the determined function performing task.

Hereinafter, with reference to the accompanying drawings will be described in detail with respect to the board-to-board message communication system and method according to an embodiment of the present invention.

2 is a road showing a configuration of an inter-board message communication system according to the present invention, a PCI bus switch 10, a PCI bus switch driver 20, an interface unit 30, and an application layer unit 40 are provided. It is done by

In such a configuration, the PCI bus switch driver 20 operates a PCI bus switch 10 for interfacing each board with the compact PCI bus. In addition, the PCI bus switch driver 20 detects hermetic and mounting information of each board, which is performed by a board mount detection task (not shown) provided in the PCI bus switch driver 20.

As described above, since the PCI bus switch driver 20 is a library to be common to all boards, the PCI bus switch driver 20 provides an application programming interface (API) to the upper layer.

On the other hand, the interface unit 30 interfaces between the PCI bus switch driver 20 and the application layer unit 40, and since it is a library that will be common to all boards, it provides an API to the upper layer.

As described above, the interface unit 30 actually transmits and receives data that each board wants to communicate with other boards, and sends and receives message headers that are commonly attached to all messages to actual data to send to other boards. .

As described above, the interface unit 30 transmits and receives data to communicate with other boards, which periodically polls whether messages have been received from other boards, and if there is a received message, Whether the message came from the receiving task 33, which analyzes the header of the message and sends it to the analyzed task, and the functional request tasks 47-1, 47-2, ..., 47-n of the application layer unit 40; If there is a message received by polling periodically, it is determined by a transmission task 37 which sends a message header to the board after determining the board to which the message should be sent.

As described above, the reception task 33 creates a message queue 35 for boards other than the magnetic board, and determines whether a message is received from another board by setting a head and a tail field. Head and tail are the arguments used for general queuing mechanism, and the message input to the queue increases the head value by one and the message read from the queue decreases the tail value by one. There is no message to process, and if the tail value is greater than the head value, the message queue is full. As described above, by the queue mechanism, the reception task 33 determines whether a message comes from another board. If the message enters the message queue 35, the reception task 33 analyzes the header of the message to apply the message to the application layer unit 40. Determining which function task to send to, and sending the message to the determined function task.

Then, the transmission task 37 creates a message queue 39 for the function request tasks 47-1, 47-2, ..., 47-n existing in the application layer unit 40, and the head and tail fields. It is determined whether a message is received from the task existing in the application layer unit 40. If the function request tasks 47-1, 47-2, ..., 47-n of the application layer unit 40 have a message to send to another board, the API provided by the interface unit 30 provides the corresponding message. Is sent to the transmission task 37 of the interface unit 30 using.

As a result of periodically polling the message queue 39 in the transmission task 37, if a message enters the message queue 39, it is determined which board to send the board to, and then a message header is created and pasted. Send to the message queue of the receiving task of the partner board to send.

On the other hand, the application layer unit 40 is composed of different programs for each board, generates data that needs to communicate with other boards, and transmits a message using an API provided by the interface unit 30.

The application layer unit 40 has various kinds of function request tasks 47-1, 47-2,..., 47-n according to each application, and all the function requests present in the application layer unit 40 are present. The tasks 47-1, 47-2,..., 47-n may send a message to another board by using the API of the interface unit 30. In addition, in the application layer 40, there are also function performing tasks 43-1, 43-2,..., 43-n for finally processing a message from another board. 43-1, 43-2, ..., 43-n are provided with message queues 45-1, 45-2, ..., 45-n, and are received by the reception task 33 of the interface unit 30. The received messages are accumulated in the message queues 45-1, 45-2, ..., 45-n. Thus, the function performing tasks 43-1, 43-2, ..., 43-n periodically poll their message queues 45-1, 45-2, ..., 45-n to see if a message has entered. If a message is received, the port number and function code of the message are analyzed to perform the corresponding function.

3 is a diagram showing the configuration of a message applied to the present invention, a message applied to the present invention comprises a 32-byte message header (a) and 992 bytes of message data (b), the total size is 1024 bytes.

The message header (a) described above includes a magic numeric field (c), a message length field (d), a transmission board name field (e), a transmission board ID field (f), a transmission network ID field (g), and a transmission sub ID. Field (h), send port ID field (i), receive board name field (j), receive board ID field (k), receive network ID field (l), receive sub ID field (m), receive port ID field ( n), a message type field o, a message type field p, a serial number field q, a main function code field r, and a sub function code field s.

In such a configuration, the magic number field (c) is composed of a special number to check the validity of the message, and the magic number field (c) is filled in with OXF0F0F0F0 is a valid message.

The message length field (d) indicates the total size of the message and stores a value obtained by adding the data length to the message header. Here, the size of the message depends on the function code value of the message.

The transmit / receive board name field (e / j) is a field indicating the name of the transmit / receive board, and is defined as one byte value for each board in the interface unit 30.

The transmit / receive board ID field f / k is a field indicating the ID of the transmit / receive board.

The transmit / receive network ID field (g / l) is a field indicating a PCI bus slot number in which each board is mounted on the system, and is referred to when identifying each board in the interface unit 30. That is, when sending or receiving a message, it is used to determine which board to send the message to or from which board.

The transmit / receive sub ID field (h / m) is a field in which a message queue number of a function performing task in which a corresponding message is processed is stored. Any of the tasks in the application layer unit 40 in the interface unit 30 is stored. Referenced when determining whether to send a message to a task.

The transmit / receive port ID field (i / n) is a field in which the port number of the port to which the message belongs is stored. Here, the port means one call from the system-wide standpoint, and the capacity that can be processed for each board is determined. That is, if four I / O boards that process data are mounted in one system and each I / O board can handle 128 ports, each host board has one host board. Therefore, the capacity that the host board can handle It is 512 ports, and the processing capacity of the system is 512 ports.

The message type field o is a field indicating the continuity of the message. When the message having the same function code is continuously transmitted, the message type field o is set to 1 and sent.

The message type field p and the serial number field q are reserved areas.

The main function code field (r) indicates the purpose of each message and indicates that the host board requests an operation from the input / output board or the input / output board gives an acknowledgment (ACK) signal for the operation requested by the host board to the host board. Used to distinguish functions such as

The sub function code field s is used when it is necessary to distinguish the details of the main function code.

FIG. 4 is a flowchart for explaining a board-to-board message communication method according to the present invention, which will be described with reference to FIG. 2.

First, the message communication method between boards according to the present invention includes a message generating process (S100) of generating a message to be communicated with another board, determining which board to send the generated message to, and then attaching a message header to the corresponding board. The message receiving process (S200) for transmitting and the message receiving process (S300) for analyzing the message header of the message received from other boards in the receiving task 33 of the interface unit 30 and sending it to the corresponding function performing task, and receiving A function performing process of performing a corresponding function by analyzing a port number and a function code of the received message is performed.

Hereinafter, the above-described message generation process (S100) to function execution process (S400) will be described in detail.

First, the function request task of the application layer unit 40 generates data, that is, a message that needs to communicate with another board, and transmits a message generated using the API of the interface unit 30 to the transmission task of the interface unit 30. The message is sent to the message queue 39 at 37 (S110, S120).

Meanwhile, the transmission task 37 of the interface unit 30 periodically polls the message queue 39 to perform the function request tasks 47-1, 47-2,..., 47-n of the application layer unit 40. It is determined whether the message received from the (S210).

If the message received from the function request tasks 47-1, 47-2, ..., 47-n of the application layer unit 40 exists as a result of the determination of step S210, the received message should be sent. The board is determined, and a message header is created and pasted to the message received in step S210 (S220 and S230).

Thereafter, the message is transmitted to the message queue of the reception task of the board determined in step S220 (S240).

Meanwhile, the reception task 33 of the interface unit 30 periodically polls the message queue 35 to determine whether there is a message received from another board (S310).

In the case where the message received from the other board exists as a result of the determination of step S310, the header of the received message is analyzed to determine which function performing task of the application layer unit 40 should be sent, The message is sent to the determined function performing task (S320, S330).

Meanwhile, each of the function performing tasks 43-1, 43-2,..., 43-n of the application layer unit 40 periodically has its own message queue 45-1, 45-2,. It is determined whether there is a received message by polling (S410).

If the received message exists as a result of the determination of step S410, the port number and the function code included in the message header of the received message are analyzed to perform a function required by the received message (S420).

The board-to-board message communication system and method of the present invention are not limited to the above-described embodiments, and may be variously modified and implemented within the scope of the technical idea of the present invention.

According to the board-to-board message communication system and method of the present invention as described above, when data is exchanged with another board in the application layer unit, the interface unit creates and attaches a message header and transmits it to the corresponding board. When a message is received from another board, it analyzes the header of the message and passes it to the task to process the message so that data between the boards mounted on the system using the compact PCI bus as a hardware platform can be exchanged through the message. do.

Claims (7)

A PCI bus switch driver for detecting a mounting state of a board and operating a PCI bus switch for interfacing each board with a compact PCI bus; An application layer unit for generating data to be communicated with another board and performing a function required by a message received from another board; And an interface unit for interfacing between the PCI bus switch driver and an application layer unit and attaching and receiving a message header to data to communicate with another board. The method of claim 1, wherein the application layer unit, A function request task of generating data to be communicated with another board and transmitting data generated using an API provided by the interface unit to another board; And a function performing task of analyzing a port number and a function code of a message received from another board through the interface unit to perform a corresponding function. The method of claim 1, wherein the interface unit, A reception task for analyzing a message header of the received message to determine to which function performing task to send the message, if there is a message received from another board, and delivering the received message to the determined function performing task; If there is a message received from the function request task, the board message communication system characterized in that it comprises a transmission task for determining which board to send the received message to, and send it to the determined board with the message header attached . The method of claim 1, wherein the message header, A magic number for checking whether the message is a valid message; A message length indicating the size of the entire message; A send / receive board name indicating the name of the sender / receiver board; A transmit / receive board ID indicating an ID of the transmit / receive board; A transmit / receive network ID indicating a PCI bus slot number on which each board is mounted; A transmit / receive sub ID indicating a message queue number of a function performing task in which the message is processed; A transmission / reception port ID indicating a number of a port to which the message belongs; A message type indicative of the continuity of the message; Board-to-board message communication system comprising a function code indicating the purpose of the message. Generating a message to be communicated with another board in a function request task and sending a message generated by using an API of an interface unit to a transmission task; A message transmission process of determining which board to send the message received from the function request task to the transmission task, preparing a message header, attaching the message to the received message, and transmitting the message to the determined board; Determining a function performing task to which a message received from another board is to be sent in a receiving task, and sending the received message to the determined function performing task; And performing a corresponding function by analyzing a port number and a function code of a message received from the receiving task in the function performing task. The method of claim 5, wherein the message transmission process, Periodically polling the message queue to determine whether there is a message received from the function request task; If there is a received message as a result of the determination, determining a board to which the received message is to be sent, preparing a message header, and attaching the received message to the received message; The board-to-board message communication method comprising the step of transmitting the message to the determined board. The method of claim 5, wherein the message receiving process comprises: Periodically polling the message queue to determine whether there is a message received from another board; If there is a message received as a result of the determination, analyzing a message header of the received message to determine a function performing task to which the received message is to be sent; And sending the received message to the determined function performing task.