KR100250975B1 - Junction apparatus of b-isdn for multiprotocol stack supporting outer bus and its control method - Google Patents

Abstract

PURPOSE: A device for interfacing a B-ISDN(Broadband-Integrated Serviced Digital Network) for multi-protocol stack supporting an external bus and a control method using the same are provided to bypass motion picture data having much loads of a host processor to a board processing motion picture data through an external bus, so as to prevent an influence to the loads of the host computer. CONSTITUTION: An optical module(10) connected with a B-ISDN(Broadband-Integrated Serviced Digital Network) transceives optical signals. A Bt8222(20) manages a physical layer among protocols inside the B-ISDN. A Bt8230(30) manages an asynchronous adaptation layer. A bus controller(40) controls an address bus and a data bus, in order to perform a read/write operation in a register of the Bt8230(30). A local memory(50) maps a memory address of a Windows NT, or an address used by a local CPU of an internal network interface unit. A transmission FIFO(First In First Out)(60) connected with external media processing motion picture data transmits motion picture data to an external. And a receiving FIFO(70) receives motion picture data inputted from external media.

Description

Broadband Integrated Services Network (B-ISDN) matching device for multiprotocol stacks supporting external buses and control method thereof

The present invention relates to a broadband integrated network (B-ISDN) matching device and a control method for supporting a multi-protocol stack that supports an external bus, and to reduce the burden on the host processor and increase the communication efficiency, By bypassing the video data to the board that processes the video data through the external bus, the technology is configured to not affect the load of the host processor.

In recent years, enthusiasm for multimedia services in all industries, particularly in the telecommunications and consumer electronics sectors, has been tremendous.

This multimedia is mainly done through the Internet. Because of the limitation of the current Internet, it is difficult to assign it to all subscribers, and it is difficult for the general public to access because it has a disadvantage that it is not easy to connect with the public network.

Moreover, since multimedia services such as video require high capacity and high speed, they tend to service them through interworking with high speed networks, especially broadband integrated information networks (hereinafter referred to as B-ISDN). And through ATM Forums.

This B-ISDN network has the ability to cope with the following services.

ㆍ Interactive services: video telephony, video conferencing, data transmission and document communication

Message service: video mail, voice mail and E-mail, etc.

ㆍ Retrieval service: video text, database and multimedia DB

Distributive Services: Video on Demand, Electronic Newspapers and Electronic Publishing

There is a need for a network matching device that allows a PC running Windows NT, which is considered to be the most popular in the home, to access the B-ISDN network and provide multimedia services. .

The service that is considered to be widely used as a service provided by the B-ISDN network can be considered as an Internet service through interworking with an existing local area network (LAN) and a video service composed of video telephony, video conferencing, and VOD.

This can be divided into a TCP / IP stack for Internet service and a stack for B-ISDN dedicated application for video service.

Therefore, it is necessary to provide an efficient device driver that can raise these various protocol stacks, and in case of video service, the video data can be bypassed to the external bus to eliminate the overload of the host caused by using the host's own bus. There is an increasing need for a structure of a network matching device and a device driver capable of controlling it.

In view of the conventional requirements as described above, the present invention bypasses the video data that requires the most host processor load to the board that processes the video data through an external bus, thereby affecting the load of the host processor. It is an object of the present invention to provide a network matching device that does not reach.

In addition, the present invention is a device driver of the network matching device to have a structure that can be efficiently bound to the protocol stack such as "IPOA" and "LANE" that can provide Internet services as well as B-ISDN applications Therefore, it aims to be able to actively cope with various services to be provided in the future.

1 is a block diagram showing a schematic configuration of a broadband termination device (B-TE) using a network matching device to be implemented in the present invention.

FIG. 2 is a detailed block diagram of the B-ISDN network matching device of FIG. 1. FIG.

FIG. 3 shows segmentation processing and memory structure of Bt8230 in FIG.

4 is a flowchart of setting up a segmentation structure through a device driver.

FIG. 5 is a diagram illustrating a reassembly process and a memory structure of Bt8230 in FIG.

6 is a flowchart illustrating a reassembly structure setup through a device driver.

7 is a diagram showing the structure of a device driver according to the present invention.

8 is a diagram showing a relationship between a data structure and other data structures for an AIM DDI user according to the present invention.

9 is a diagram showing a relationship between a data structure for call / connection and other data structures according to the present invention.

10 is a diagram illustrating a relationship between a call / connection and a call / connection reception data structure according to the present invention.

11 is a diagram illustrating a case where two call / connection establishment requests arrive at a specific call / connection from a network according to the present invention.

12 is a diagram illustrating a case in which a call request according to the present invention is made irrespective of a time sequence in which two requests are made.

FIG. 13 is a diagram showing a data structure when a reference value is null or different from a user call identifier of a corresponding call / connection, when a call / connection establishment request according to the present invention is accepted.

FIG. 14 is a diagram showing a data structure in a case where a reference value is the same as a user call identifier of a corresponding call / connection, when a call / connection establishment request according to the present invention is accepted.

FIG. 15 is a diagram illustrating a connection list by status of an AIM DDI request according to the present invention. FIG.

16 is a diagram showing a relationship between an AIM DDI request and other data structures according to the present invention.

* Explanation of symbols for main parts of the drawings

100: network matching device 111: media encoder

112: media decoder 10: optical module

20: Bt8222 30: Bt8230

40: bus controller 50: local memory

60: send piepo 70: receive piepo

a: local transmission ring b: local segmentation status queue

c: local reassembly prequeue d: local reassembly prequeue

In order to achieve the above object, a structure of a network matching device implemented in the present invention includes: an optical module connected to a broadband integrated information network (B-ISDN) to exchange optical signals; A protocol processing unit in charge of a physical layer of protocols and asynchronous adaptation layer in a B-ISDN network; A bus controller which controls an address and a data bus to perform a read / write operation on a register in the protocol processor; A local memory connected to the protocol processing unit and capable of mapping to a memory address of Windows NT or an address that can be written by a local CPU in the network matching device; It is characterized in that it comprises a transmission / reception memory unit which is connected to the bus and the external media for processing the video data, to transfer the video data to the outside, to be processed in the external media.

In addition, the control method proposed in the present invention to achieve the above object is to transmit and receive information and data through the local memory using the bus controller of the network matching device in the general data transmission path; Moving picture data can be processed by an external media means via an external bus connected to a network matching device; When transmitting data to the network side during the processing, transmitting data of one frame to the transmitting memory means and transmitting a signal indicating that the frame has been transmitted to the protocol processing means; When receiving from the network, the data input through the protocol processing means is stored in the receiving memory means, and at the same time, a signal indicating that the data is stored in the receiving memory means is read from the external media means for processing. It features.

The above objects, features, and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a diagram showing a schematic configuration of a broadband termination device (hereinafter referred to as B-TE) using a network matching device to be implemented in the present invention. )Wow; A media encoder 111; Media decoder 112.

The B-TE terminal configured as described above provides a transmission capacity of 155.52 Mbps or 25.6 Mbps to the network side, and provides an interactive service, a message service, a search service, and a distribution service to a user, thereby providing a multimedia environment having a high speed transmission capability. Build it.

FIG. 2 is a detailed block diagram of the B-ISDN network matching device 100, which focuses on how to control traffic efficiently without affecting the host processor.

An optical module 10 connected to the B-ISDN network to transmit and receive optical signals; Bt8222 (20) in charge of the physical layer of the protocol in the B-ISDN network; A Bt8230 (30) in charge of the asynchronous adaptation layer; A bus controller 40 for controlling an address bus and a data bus to perform a read / write operation on a register in the Bt8230 (30); A local memory (50) connected to the protocol processing unit and capable of mapping to a memory address of Windows NT or an address that can be written by a local CPU in the network matching device; A transmission pipe (TxFIFO) 60 connected to a bus with an external media for processing video data and for delivering video data to the outside; And a receiving piezo (RxFIFO) 70 for receiving video data input from an external media.

In the network matching device configured as described above, a general data connection path uses an internal bus (PCI bus) to transfer or receive information and data through a local memory 50, and a data connection using an external bus such as a video. When the data is transmitted to the network, the data of one frame is transmitted to the transmission pipeo 60, and at the same time, the bus controller is executed by using "SEND _- FRM (it is reset after notifying the bus controller 40 that the frame is transmitted)." (40) informs the "LXMIT resist" in Bt8230 (30) that a frame has been delivered.

On the other hand, when receiving data of one frame from the network, the Bt8230 (30) stores the received frame in the receiving PIPO 70, and "FIFO _- NOT" notifying that the data is stored in the PIFI on the external bus. _- EMPTY "by sending a control signal, and gets the external media processing board reads the frame.

As described above, by bypassing the video data that requires the most host processor load to the board that can process the video data through the external bus, it does not affect the load of the host process, thereby providing high quality video and high efficiency to the user. To provide host performance.

In addition, by configuring the Bt8230 (30) to control traffic at the ATM layer, it is configured to transmit the video data and other data in accordance with the traffic contracted to the B-ISDN network.

In addition, the Bt8230 (30) configures the local memory 50 in the network matching device 100 as shown in FIG. 3 so that the video data connection can be segmented like the other data connections. Next, the memory structure in FIG. 3 is set according to the process of FIG.

In the memory structure of FIG. 3, it should be noted that the local transmission ring (a) and the local segmentation state queue (segmentation memory structure) used by the Bt8230 (30) for receiving a video data stream from an external bus. Set the status of Local Segmentation Status Queu) e (b) to be always overwritten. In particular, pointers to all segmentation buffers of the Local Tranmit Ring (a) Always point to each of the pipettes 60 and 70 above.

After a moving picture data frame is written in PIPO, the control signal input from the external bus is designated by glue logic to determine how many moving picture data is written to the "SEG _- LXMIT" register in Bt8230 (30). Put it.

The above process will be described in detail. ① Initialize the structure of the host, the local memory, and the common memory, and set up a virtual channel connection (hereinafter referred to as VCC) table.

(2) The transmission ring is set (in the figure, entry 3 is designated).

Inform Bt8230 (30) that the data entry is three.

(4) If the next numeric request value is greater than zero (PND> 0), the data is stored as a buffer descriptor.

⑤ Provides the data stored in the public memory according to the scheduler of Bt8230 (30).

(6) The common part convergence sublayer (CPCS-SDU) is made by Bt8230 (30) into a cell without a head error checksum (HEC) and transferred to Bt8222 (20).

⑦ Bt8222 (20) provides HEC when outputting the data received above.

8. Finally, the segmentation result is stored in the status queue of the common memory.

4 is a flow chart illustrating a process of establishing and releasing a call / connection in a local memory so that the Bt8230 can segment a video data connection like other data connections. Determining whether the external bus is used, recording the size and the pointer in the entry of the host transmission ring, and setting the necessary values in the segmentation VCC table (segvcc table) (S1); If it is determined that the external bus is used, obtaining a size of a media data frame and a pointer of a transmission pipeo (S2); (S3) recording the size and the pointer in the entry of the local transmission ring if the value is found; After the recording, it is determined whether the recording is completed in all the entries of the local transmission ring. If the recording is not completed, the process is repeated until the recording is completed. Then, the process of setting the necessary values in the 'segvcc table' is performed (S4). It is executed, including.

FIG. 5 illustrates the configuration of the local memory in the network matching device so that the Bt8230 can reassemble the video data connection together with other data connections, and is set according to the procedure of FIG. .

At this time, the memory structure of FIG. 5 is to be noted that the local reassembly free queue for reassembly that the Bt8230 (30) will use to transfer the video data stream from the Bt8230 (30) to an external bus (c). And the Local Reassembly Status Queue (d) memory structure to always be in the overwritten state, especially all reassembly buffers of the local reassembly prequeue (c). The assembly buffer pointer is always set to point to each of the above fifos.

In detail, when a cell is input to the Bt8230 (30) through the ①Bt8222 (20), ② executes a hash function (Bash function) between the Bt8230 (30) and the shared memory.

(3) Find the VCC table entry by hash bucket.

(4) Find the free buffer and set the owner bit.

(5) The direct memory access (DMA) in the Bt8230 (30) stores 48 bytes to the host and local memory.

(6) Write the buffer status and owner bit.

7) If an error has occurred, report this error interrupt to the host.

Due to the hardware structure and software processing as described above, general data connections are delivered to the host, and only the data connection related to video can be separated and transferred to other media buses by external buses.

FIG. 6 is a flowchart illustrating a process of establishing and releasing a call / connection in a local memory so that the Bt8230 can reassemble a video data connection like other data connections. When a call / connection is established, an external bus is used. Determining whether or not to perform the step of setting values necessary for the reassembly VCC table (rsmvcc table) when the external bus is not used (T1); Then setting up values necessary for a hash table and a hash bucket (T2); If the external bus is used, obtaining the size of the media data frame, and then obtaining a pointer of the received PIPO (T3); Writing the size and the pointer to an entry of a Local FreeQue when all the values are obtained (T4); Subsequently, it is determined whether or not the recording is completed in all entries of the local preque, and if the recording is not completed, iterate until recording is completed, and then set the necessary values in the reassembly VCC table. And a step T5 of performing the step T2 of setting values necessary for the hash table and the hash bucket.

FIG. 7 is a diagram illustrating the structure of an AIM device driver that drives the network matching device configured as described above. The AIM device driver has a work thread having a work queue as shown in FIG. Thread) and provides AIM service in a multiprotocol stack environment.

The transaction thread accumulates requests from the AIM application to the transaction queue first, and the task thread sequentially processes the requests accumulated in the task queue and then targets the processed results. Will be delivered.

In particular, requests from the AIM board are accumulated once in the work queue via the interrupt processing routine. The subsequent processing is the same as that of the AIM application.

Each request has a buffer for the request, which has a header that indicates what kind of request the request is.

The following describes how the AIM device driver manages data structures for these calls and requests.

First, the AIM device driver interface (DDI) user (aimdd _- user _- t) is a data structure that identifies the application program or high-level device driver that wants to access the AIM device driver. The following describes the relationship between data structures and other data structures.

In case of application program, AIM device driver is opened through the creation file function (CreateFile (): Win 32 function) and in the case of upper level device driver through "IoGetDeviceObjectPointer ()" kernel device driver support function. One "AIM DDI User" data structure is created for each.

All requests for AIM device drivers are then managed for each user, preventing one user from accessing resources (calls / connections, data, etc.) of other users at random.

The following is the definition of data structure.

In the above description, "au _- status" indicates the user's status. The initial value is TRUE, and when the "CloseHandle ()" function or the "ObDereferenceObject ()" function is called, it has a false value (FALSE).

Subsequent new requests to this user are ignored.

Also, the "au _- count" is the number of pointers that refer to this data structure.

Also, the "au _- xact _- list" and "au _- call _- list" are connection lists for requests ("xact _- t") and call / connection ("aimdd _- call _- t") to the user, respectively.

Also, the "au _- user _- list _- entry" is a place-holder for connecting each user.

Finally, the "au _- file _- object" is a file descriptor for distinguishing each user.

Second, as a description of call / connection, the data structure of the call / connection shown in FIG. 9 and other data structures will be described with reference to the drawings.

Call / connection data structure is a data structure to hold information about call / connection set by user.

Here is the call / connection data structure:

User calls / connections are currently point-to-point call / connections, point-tp-multipoint call / connections, and PVC call / connections. It is divided into (PVC call / connection), each of which is divided into information elements (information element (point-to-point vs. point-to-multipoint)) or AIM DDI exchanged by the AIM device driver during call / connection setup. Primitives (PVC call / connection) automatically identify the AIM device driver.

This division is contained in the "ac _- mode".

Each call / connection has a user call identifier (ID) ("ac _- ref") and a network call identifier ("ac _- net _- ref").

The user call identifier is a call / connection descriptor obtained by the user through "AIM _- DDI _- ASSOCIATE _- ENDPOINT _- REQ", and the network call identifier is the call reference value of the Q.2931 (or Q.2971) call / connection. call reference value).

These two identifiers have the same value when the user requests a call / connection establishment, or a different value when a call / connection establishment request is made from the network (or in the "AIM _- DDI _- ACCEPT _- INCOMING _- CALL _- REQ" primitive). When the "accepting call reference value" is set to the same value as the user call identifier of a particular call / connection, it has the same value ("accepting call reference value" in the "AIM _- DDI _- ACCEPT _- INCOMING _- CALL _- REQ" primitive). null).

The status of a call / connection also has a user call status ("ac _- user _- status") and a network call status ("ac _- status").

User call status mainly represents the state change of the call / connection according to the AIM DDI primitive (see TM "AIM DDI Flowchart"), and the network call status is the call / connection of the call / connection within the Q.2931 (or Q.2971) control plane. Indicates the state.

And "ac _- count" represents the number of pointers to call / connection data structures.

"Ac _- user" also refers to the "AIM DDI User" data structure that the call / connection belongs to.

In addition, "ac _- vcc _- index" has a "null" value for AAL No. 1 / connection and "VCC _- INDEX" in AIM board for AAL No. 5 / connection.

Also, "ac _- all _- call _- list _- entry" and "ac _- user _- call _- list _- entry" are placeholders for call / connection linked lists belonging to the same user as the list of all call / connections respectively. (place-holder).

Also, "ac _- xact _- list" is a linked list for AIM DDI requests pending on call / connection.

"Ac _- party _- list" is also a connection list for parties of point-to-multipoint call / connections.

Other data structures are the data structures required to wait for a call / connection from the network (see next section), or those required for simple management.

Third, the data structure related to call / connection setup request reception is described. When the "AIM _- DDI _- ARRIVAL _- OF _- INCOMING _- CALL _- IND" primitive is executed, the relationship between call / connection and call / connection reception data structure is described. A description with reference to FIG. 10 is shown.

When a request for call / connection establishment is received from the network, the call / request must be delivered to a specific AIM application or higher level device through the "AIM _- DDI _- ARRIVAL _- OF _- INCOMING _- CALL _- IND" primitive. .

For this purpose, there is a request-receive data structure "aimdd _- listen _- t", which is placed on the "ac _- listen" of the call / connection when the "AIM _- DDI _- PREPARE _- INCOMING _- CALL _- REQ" primitive is requested. Is recorded.

The following is the "aimdd _- listen _- t" data structure.

"Al _- call" indicates a pointer to the call / connection.

Also, "al _- lli _- found" and "al _- hli _- found" are internal variables that are additionally used in the processing of call / connection transmission requests.

Also, al _- listen _- list _- entry "is a place-holder for a list that concatenates all the" aimdd _- listen _- t "data structures.

"al _- sap" refers to the server access point (hereinafter referred to as SAP) for AIM DDI, which is the broadband upper layer information (B-HLI) and the broadband lower layer information (B-LLI). Is made up of a combination.

In addition, "as _- hli _- content" and "as _- lli _- content" refer to them, respectively, and "as _- hli _- filter" and "as _- lli _- filter" indicate only which of these information areas are of interest. Indicates.

If this specific information areas should have a specific value, the information area on the _{"filter as - - (h /} 1) li""as - - (h / 1) li conten" and setting the information area to a specific value, the Set all to "1".

And if the content of the particular information domain correlation which may have any value is set to _{"as - filter - (h /} 1) li" all "0", the information area on.

Meanwhile, referring to FIG. 11, two call / connection establishment requests from a network arrive at a specific call / connection when "ac _- listen _- queue _- num" of a specific call / connection is 2 as follows. .

"Ac _- listen _- queue _- num" in the call / connection data structure indicates the number of requests that can be processed when multiple call / connection establishment requests arrive.

If this value is 1 then all subsequent configuration requests are rejected immediately.

"ac _- listen _- pending _- num" indicates the number of configuration requests currently waiting for processing, and cannot exceed "ac _- listen _- queue _- num".

When a call / connection setup request arrives, the AIM device driver first examines the "all call / connection reception data structures" and compares the SAP of the setup request with the SAP of the call / connection reception data structures, if there is a matching data structure. Will create a new call / connection to store the request and connect to "ac _- listening _- list".

If there is more than one matching data structure, the close call / connection is selected from "all call / connection incoming data structures". If no matching data structure exists, the call / connection establishment request is immediately rejected.

If an application or higher level device driver requests "AIM _- DDI _- WAIT _- ON _- INCOMING _- CALL _- REQ", the first request is transferred to "ac _- accept _- call" of the call / connection.

This is done regardless of the time order in which the two requests were made, as shown in FIG.

Next, FIG. 13 shows that when a call / connection establishment request is accepted through "AIM _- DDI _- ACCEPT _- INCOMING _- CALL _- REQ", the "accepting call reference value" is null or the user call identifier of the call / connection. And data structures in different cases.

Next, FIG. 14 shows data when a call / connection establishment request is accepted through "AIM _- DDI _- ACCEPT _- INCOMING _- CALL _- REQ" and the "accepting call reference value" is the same as the user call identifier of the call / connection. The structure is shown.

Compared to the case of FIG. 13, the call / connection A and the call / connection reception data structure A are all lost, and the call / connection A " is rejected and destroyed.

Fourth, the PARTY data structure (aimdd _- party _- t) is implemented so that only one exists as a place-holder for point-to-point call / connection. In the case of point-to-multipoint, one is created at the first call / connection setup and one after each new party is added.

The following shows the party data structure.

In the above, "ap _- ref" represents a party reference number.

Also, "ap _- status" indicates the status of the party.

In addition, "ap _- xact _- list" indicates AIM DDI requests that are pending for the party.

Also, "ap _- call _- list _- entry" is a place-holder for the party list of the call / connection to which the party belongs.

Fifth, a description of the AIM DDI request will be described with reference to the connection list according to the state of the AIM DDI request shown in FIG.

The AIM DDI Request (xact _- t) data structure is used for input / output (I / O) requests from applications or higher-level device drivers, and for primitive requests from the Q.2931 (or Q.2971) control plane. And primitives are requested from the AAL 5 data plane.

The following is the AIM DDI request data structure.

In the above description, "xact _- user" indicates where the AIM DDI request is made. If the request is made from the control plane or the data plane, it has a null value.

In this case, "xact _- user _- list _- entry" indicates a place-holder for the AIM DDI request list of the corresponding AIM DDI user.

"xact _- irp" points to an IRP when an AIM DDI request is made from an application or higher level device driver, and "xact _- extension" points to a pointer to "EXTENSION" of the AIM device to which the AIM DDI request belongs.

AIM DDI requests belong to each status list according to the status of the request, where "xact _- status" represents the status of the request and "xact _- list _- entry" is a place-holder for the status list.

In addition, when an AIM DDI request must wait for a specific event and return a result, it must be pending, which is connected to a list of calls / connections or to a list of parties.

In this case, the bit mask for the event "xact _- wait" waits, "xact _- call _- list _- entry" places a place-holder for the list of calls / connections, and "xact _- party _- list _- entry". Indicates a place-holder for a list of parties.

If an AIM DDI request is linked to a list of calls / connections, then "xact _- call" indicates that call / connection.

An AIM DDI request points to the buffer for the request as "xact _- req _- ptr" and the buffer size as "xact _- req _- size".

Also, the buffer for the result is indicated by "xact _- ret _- ptr", the start offset of valid data is indicated by "xact _- ret _- offset", and the size of valid data is indicated by "xact _- ret _- size".

It also contains the results of the IRP process in "xact _- ret _- status".

When the AIM DDI request is a data send / receive request, "xact _- aal _- req _- list" and "xact _- read _- data" respectively indicate a list of the data send request and a pointer to the received data.

Figure 16 shows the relationship between AIM DDI requests and other data structures. In the figure, the status of all AIM DDI requests linked to a list of calls / connections or to a list of parties is handled by the processing thread. It is a state.

For reference, each arrow shown in FIGS. 8 through 16 has the following meaning.

: 리스트로 연결되어 있으며, 레퍼런스 카운트(reference count)를 하나 증가시킨다.

It is linked to a list and increments the reference count by one.

: 리스트로 연결되어 있으며, 레퍼런스 카운트와는 무관하다.

It is linked to a list and is not related to the reference count.

: 포인터로 연결되어 있으며, 레퍼런스 카운트를 하나 증가시킨다.

Connected by pointer, increments the reference count by one.

: 포인터로 연결되어 있으며, 레퍼런스 카운트와 무관하다.

: Connected by pointer, independent of reference count.

As described in detail above, the present invention has a bypass structure to an external bus for another media processing board, thereby eliminating the overload of the system, and thus, the host process can more actively respond to user demands, and ITU-T It has a message filter for routing control based on the high layer information and the low layer information defined in Q.2931, so that routing to multiprotocol stacks and their applications is easier and more efficient. There is an advantage to providing.

In addition, there is an advantage in having a data structure that can be processed immediately and efficiently in accordance with various requests from the network and users, it is accompanied with the advantage to provide a system that is very well adapted to the various multimedia services to be provided in the future.

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, those skilled in the art will be able to various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims You will have to look.

Claims (9)

An optical module connected to a broadband integrated information network (B-ISDN) to exchange optical signals; A protocol processing unit in charge of a physical layer of protocols and asynchronous adaptation layer in a B-ISDN network; A bus controller which controls an address and a data bus to perform a read / write operation on a register in the protocol processor; A local memory connected to the protocol processor and capable of mapping to a memory address of Windows NT or an address that can be written by a local CPU in the network matching device; Multi-protocol supporting an external bus, comprising a memory unit for transmitting / receiving connected to a bus with an external media processing video data and transferring the video data to the outside for processing on the external media. Broadband Integrated Services Network (B-ISDN) matching device for stacks. The memory system of claim 1, wherein the local memory includes: a memory structure for enabling segmentation of a video data connection like other data connections when receiving a video data stream; A B-ISDN matching device for a multi-protocol stack supporting an external bus, comprising a memory structure for reassembling a video data connection like other data connections. The multiprotocol stack for supporting an external bus according to claim 2, wherein the state of the local transmission ring and the local segmentation state queue belonging to the local memory in the memory structure for segmentation is always set to be overwriteable. Broadband Integrated Services Network (B-ISDN) matching device. The B-ISDN matching for multi-protocol stacks according to claim 3, wherein the pointers of all segmentation buffers of the local transmission ring always point to the memory for the transmitter / receiver. Device. The multi-bus supporting multiple bus according to claim 2, wherein the states of the local reassembly prequeue and the local reassembly state queue belonging to the local memory in the memory structure for reassembly are always set to be overwriteable. Broadband Integrated Services Network (B-ISDN) matching device for protocol stacks. The broadband integrated communication network (B-ISDN) for a multi-protocol stack supporting an external bus according to claim 5, wherein the pointer of the reassembly buffer of the local reassembly prequeue always points to the memory for the transmitter / receiver. Matching device. CLAIMS 1. A control method of a network matching device for transmitting / receiving general data and moving picture data, the general data transmission path using a bus controller in a network matching device to transmit / receive information and data through a local memory; Moving picture data can be processed by an external media means via an external bus connected to a network matching device; When transmitting data to the network side during the processing, transmitting data of one frame to the transmitting memory means and transmitting a signal indicating that the frame has been transmitted to the protocol processing means; When receiving from the network, the data input through the protocol processing means is stored in the receiving memory means, and at the same time, a signal indicating that the data is stored in the receiving memory means is read from the external media means for processing. A method for controlling a Broadband Integrated Services Network (B-ISDN) matching device for a multiprotocol stack supporting an external bus. The method of claim 7, wherein the call / connection setup and release process for enabling data transmission to the network side includes determining whether to use an external bus when the call / connection is established, and transmitting the host when the external bus is not used. Recording a size and a pointer in an entry of a ring, and setting values necessary for a segmentation virtual channel connection table; If the external bus is used, obtaining the size of the media data frame and a pointer of the transmission memory means; If the value is found, writing a size and a pointer to an entry of a local transmission ring; And determining whether or not the recording is completed in all entries of the local transmission ring after the recording, and if the recording is not completed, repeating the recording until the recording is completed, and then setting necessary values in the segmentation virtual channel connection table. B-ISDN matching device control method for a multi-protocol stack supporting an external bus, characterized in that for executing. The method of claim 7, wherein the call / connection setup and release process for enabling data reception from the network side determines whether to use an external bus when the call / connection is established, and not to use the external bus. Setting values required for the reassembly virtual channel connection table; Then setting values necessary for the hash table and the hash bucket; If the external bus is used, obtaining the size of a media data frame, and then obtaining a pointer of a receiving memory means; Writing the size and pointer to an entry of a local prequeue when all of the values are obtained; Then, it is determined whether or not the recording is completed in all entries of the local preque, and if the recording is not completed, iterate until recording is completed, and then set the necessary values in the reassembly virtual channel connection table. When the completion is completed, comprising the steps of setting the necessary values for the hash table and the hash bucket Broadband Integrated Services Network (B-ISDN) matching device control method for supporting a multi-protocol stack, characterized in that the execution.

Images