Abstract:
Provided are a method and apparatus for transmitting an isochronous stream in an Internet protocol (IP) over Institute of Electrical and Electronics Engineers (IEEE) 1394. The method includes: requesting isochronous stream transmission over a predetermined serial bus; and receiving an isochronous stream through the predetermined serial bus using a service of a predetermined network protocol based on a response to the request, and the method allowing the IP over IEEE 1394 to support isochronous stream transmission.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     This application claims the priority of Korean Patent Application No. 10-2004-0082567, filed on Oct. 15, 2004, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference.  
         [0002]     1. Field of the Invention  
         [0003]     The present invention relates to a method and apparatus for transmitting an isochronous stream, and more particularly, to a method and apparatus for transmitting an isochronous stream according to an Internet protocol (IP) over an Institute of Electrical and Electronics Engineers (IEEE) 1394.  
         [0004]     2. Description of the Related Art  
         [0005]     The IEEE 1394 protocol is widely used for multimedia devices such as video camcorders which require high-speed transmission of mass storage data because IEEE 1394 supports faster transmission speeds than other conventional standards. In particular, since IEEE 1394 supports real-time isochronous stream transmission, IEEE 1394 is commonly used for home digital devices and is emerging as a substitute for a backbone of a home network due to its expandability and capacity for high-speed transmission.  
         [0006]     As electric home appliances have become digitalized, compatibility between information technology (IT) devices and electric home appliances has been actively studied and data transmission using an IP is considered to be a more efficient communication method in a hybrid network of a home. Accordingly, the Internet Engineering Task Force (IETF) proposed IP over IEEE 1394 in RFC 2734. IP over IEEE 1394 defines the IEEE 1394 standard using IP services such as a Quality of Service (QOS) guarantee.  
         [0007]      FIG. 1  is a configuration diagram of a conventional IP over IEEE 1394 protocol stack.  
         [0008]     Referring to  FIG. 1 , the conventional IP over IEEE 1394 protocol stack includes an application layer  11 , a TCP/IP layer  12 , and an IEEE 1394 layer  13 .  
         [0009]     The application layer  11  contains an IP over IEEE 1394 application  111 .  
         [0010]     The TCP/IP layer  12  includes an IP over IEEE 1394 device driver  121 , and the IP over IEEE 1394 device driver  121  contains an asynchronous block write-module  1211  and an asynchronous stream module  1212 .  
         [0011]     The IEEE 1394 layer  13  includes a physical layer  131 , a link layer  132 , a transaction layer  133 , and a bus management layer  134 .  
         [0012]     Although the conventional IEEE 1394 standard supports both asynchronous stream transmission and isochronous stream transmission, as shown in  FIG. 1 , the conventional IP over IEEE 1394 supports only asynchronous block write or asynchronous stream packet transmission. That is, since the conventional IEEE 1394 standard defines only isochronous stream packet transmission which is not based on an IP but is instead based on a time division and given that the conventional IP over IEEE 1394 defines only the asynchronous block write or asynchronous stream packet transmission, packets such as moving picture experts group (MPEG) 2 packets which require a QOS guarantee and real-time transmission cannot be transmitted in real-time with the QOS being guaranteed.  
       SUMMARY OF THE INVENTION  
       [0013]     The present invention provides a method and apparatus allowing IP over IEEE 1394 to support isochronous stream transmission.  
         [0014]     The present invention also provides a computer readable recording medium having embodied thereon a computer program for executing the method.  
         [0015]     According to an aspect of the present invention, there is provided a method of receiving an isochronous stream, the method comprising: requesting isochronous stream transmission over a predetermined serial bus; and receiving an isochronous stream through the predetermined serial bus using a service of a predetermined network protocol based on a response to the request.  
         [0016]     According to another aspect of the present invention, there is provided an apparatus for receiving an isochronous stream, the apparatus comprising: a requesting portion which requests isochronous stream transmission over a predetermined serial bus; and a receiving portion which receives an isochronous stream over the predetermined serial bus using a service of a predetermined network protocol based on a response to the request by the requesting portion.  
         [0017]     According to still another aspect of the present invention, there is provided a computer readable recording medium having embodied thereon a computer program for executing the method of receiving an isochronous stream.  
         [0018]     According to yet another aspect of the present invention, there is provided a method of transmitting an isochronous stream, the method comprising: obtaining an isochronous resource to generate an obtained result of the isochronous source for transmitting the isochronous stream when a request for isochronous stream transmission is received over a predetermined serial bus; and transmitting the isochronous stream over the predetermined serial bus using a service of a predetermined network protocol based on the obtained result.  
         [0019]     According to a further aspect of the present invention, there is provided an apparatus for transmitting an isochronous stream, the apparatus comprising: an isochronous resource obtaining portion which obtains an isochronous resource and generates an obtained result of the isochronous resource for transmitting the isochronous stream when a request for isochronous stream transmission is received over a predetermined serial bus; and a transmitting portion which transmits the isochronous stream over the predetermined serial bus using a service of a predetermined network protocol based on the obtained result.  
         [0020]     According to another aspect of the present invention, there is provided a computer readable recording medium having embodied thereon a computer program for executing the method of transmitting an isochronous stream.  
         [0021]     According to another aspect of the present invention, there is provided a method of transmitting and receiving an isochronous stream, the method comprising: requesting isochronous stream transmission over a predetermined serial bus; obtaining an isochronous resource to generate an obtained result of the isochronous resource for transmitting the isochronous stream when the request is received; transmitting the isochronous stream over the predetermined serial bus using a service of a predetermined network protocol based on the obtained result; and receiving the transmitted isochronous stream.  
         [0022]     According to another aspect of the present invention, there is provided a computer readable recording medium having embodied thereon a computer program for executing the method of transmitting and receiving an isochronous stream. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0023]     The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:  
         [0024]      FIG. 1  is a configuration diagram of a conventional IP over IEEE 1394 protocol stack;  
         [0025]      FIG. 2  is a block diagram of an isochronous stream transmission/receipt system according to an exemplary embodiment of the present invention; and  
         [0026]      FIG. 3  illustrates a cycle configuration according to the IEEE 1394 standard;  
         [0027]      FIG. 4  illustrates a format of an isochronous stream packet according to an exemplary embodiment of the present invention;  
         [0028]      FIG. 5  illustrates in detail the format of the isochronous stream packet illustrated in  FIG. 4 ;  
         [0029]      FIG. 6  is a diagram for explaining packet management of the isochronous stream packet module illustrated in  FIG. 2 ;  
         [0030]      FIGS. 7 and 8  are flowcharts illustrating a method of transmitting and receiving an isochronous stream according to an exemplary embodiment of the present invention;  
         [0031]      FIG. 9  is a flowchart illustrating in detail operation  87  illustrated  FIG. 8 ; and  
         [0032]      FIG. 10  is a flowchart illustrating in detail operation  76  illustrated in  FIG. 8 .  
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0033]      FIG. 2  is a block diagram of an isochronous stream transmission/receipt system according to an exemplary embodiment of the present invention.  
         [0034]     Referring to  FIG. 2 , an isochronous stream receiving device mounted on a first node  2  according to the present invention includes an application layer  21 , a TCP/IP layer  22 , and an IEEE 1394 layer  23 .  
         [0035]     When the present embodiment is implemented in practice, it will be understood by those of ordinary skill in the art that besides the layers illustrated in  FIG. 2 , other layers can be further included in the protocol stack or some layers can be substituted with other layers. For instance, a session layer can be further included, or the TCP layer can be substituted with a User Datagram Protocol (UDP) layer. In addition, when the present embodiment is implemented in practice, it will be also understood by those of ordinary skill in the art that besides the elements illustrated in  FIG. 2 , other elements can be further included. For example, the TCP/IP layers  22  and  32  can further include elements defined by RFC 2734 corresponding to the IPv4 over IEEE 1394 standard, and the IEEE 1394 layers  23  and  33  can further include elements defined by the IEEE 1394 standard.  
         [0036]     The application layer  21  includes an isochronous stream transmission requesting portion  211 , an isochronous stream receipt preparing portion  212 , and an isochronous stream receiving portion  213 .  
         [0037]     The isochronous stream transmission requesting portion  211  requests a second node  3  to transmit an isochronous stream over the IEEE 1394 bus, using asynchronous block write by calling an asynchronous block write function in the application layer  21 .  
         [0038]     The IEEE 1394 standard supports various transfer modes such as the asynchronous block write, an asynchronous stream, an isochronous stream, etc. In particular, commands such as IP datagram, address resolution protocol (ARP) request/response, multicast channel allocation protocol (MCAP) advertisement/solicitation, and the like, are transmitted using an asynchronous block write mode. Therefore, the isochronous stream transmission requesting portion  211  requests the second node  3  to transmit the isochronous stream using the asynchronous block write.  
         [0039]     The isochronous stream receipt preparing portion  212  receives a response to the isochronous stream transmission request from the second node  3 , and prepares to receive the isochronous stream with reference to a channel and bandwidth included in the received response. More specifically, the isochronous stream receipt preparing portion  212  prepares to receive the isochronous stream by calling an input output control (IOCTL) in the application layer. The IOCTL, which is one of a Linux command, is a function which manipulates parameters of lower layers. That is, the isochronous stream receipt preparing portion  212  sets values of registers of the IEEE 1394 layer that are related to preparation for isochronous stream receipt and prepares to receive the isochronous stream by calling the IOCTL. Further, when the preparation for asynchronous stream receipt has been completed, the isochronous stream receipt preparing portion  212  informs the second node  3  that the isochronous stream receipt preparing portion  212  has prepared to receive the isochronous stream over the IEEE 1394 bus  4  using the asynchronous block write by calling an asynchronous block write function in the application layer.  
         [0040]     The isochronous stream receiving portion  213  receives the isochronous stream, using a service of the IP, over the IEEE 1394 bus  4  from the second node  3  which is informed by the isochronous stream receipt preparing portion  212 . More specifically, the isochronous stream receiving portion  213  can receive the isochronous stream over the IEEE 1394 bus  4  while the QOS is guaranteed using a service such as packet routing through an optimized path provided by the IP. A typical example of an isochronous stream is a moving picture content stream which needs to be transmitted in real time.  
         [0041]     The TCP/IP layer  22  includes an isochronous stream extracting portion  221  and an IP over IEEE 1394 device driver  222 .  
         [0042]     The isochronous stream extracting portion  221  extracts an isochronous stream from isochronous stream packets output from an isochronous stream packet module  2213 . More specifically, the isochronous stream extracting portion  221  removes headers from the isochronous stream packets, and generates the isochronous stream by collecting data stored in payloads of the isochronous stream packets.  
         [0043]     The IP over IEEE 1394 device driver  222  includes an asynchronous block write module  2211 , an asynchronous stream packet module  2212 , and the isochronous stream packet module  2213 .  
         [0044]     The asynchronous block write module  2211  supports the asynchronous block write which is based on an IP, the asynchronous stream packet module  2212  supports asynchronous stream packet transmission/receipt which is based on an IP, and the isochronous stream packet module  2213  supports isochronous stream packet transmission/receipt which is based on an IP.  
         [0045]     The IEEE 1394 layer  23  includes a physical layer  231 , a link layer  232 , a transaction layer  233  and a bus management layer  234  which corresponds to the IEEE 1394 device driver.  
         [0046]     The physical layer  231  physically and electrically connects the IEEE 1394 layer and the IEEE 1394 bus.  
         [0047]     The link layer  232  has two queues for transmission and a single queue for receipt in order to transmit and receive packets in two transmission modes, that is, an asynchronous transmission mode and an isochronous transmission mode. The two queues for transmission are divided into a queue for asynchronous transmission and a queue for isochronous transmission and used in writing, and the queue for receipt is used in reading. Additionally, the link layer  232  controls a cycle for smooth transmission and receipt.  
         [0048]      FIG. 3  illustrates a cycle configuration according to the IEEE 1394 standard.  
         [0049]     Referring to  FIG. 3 , a cycle master of the bus management layer  234  transmits a cycle start packet every 125 μsec. Nodes receiving the cycle start packet over the IEEE 1394 bus  4  synchronize the cycle on the basis of the cycle start packet. After the cycle start packet is transmitted, packets are transmitted in the isochronous transmission mode for a predetermined period of time, and packets are transmitted through channel arbitration in the asynchronous transmission mode for a remained period of time.  
         [0050]      FIG. 4  illustrates a format of an isochronous stream packet according to an exemplary embodiment of the present invention.  
         [0051]     Referring  FIG. 4 , the isochronous stream packet includes an isochronous header  51 , a CIP header  52 , a TCP/IP header  53 , and a data field  54 . As shown in  FIG. 3 , the isochronous stream packet is transmitted after the cycle start packet, which is transmitted every 125 μsec.  
         [0052]     The data field  54  is composed of four packets, each of 24 bytes. When a total of eight 24-byte packets, which are stored in data fields of two isochronous stream packets, are collected, an MPEG 2 packet composed of a time stamp (TS) and a transport stream packet (TSP) can be obtained. MPEG 2 is a typical moving picture compression standard.  
         [0053]      FIG. 5  illustrates in detail the format of the isochronous stream packet illustrated in  FIG. 4 .  
         [0054]     Referring to  FIG. 5 , an isochronous header  51  of the isochronous stream packet includes a data length field  511 , a tag field  512 , a channel field  513 , a tCode (transaction code) field  514 , an sy (synchronization) field  515 , and a Header_CRC (cyclic redundancy check)  516 . Further, a Data_CRC field  517  is added after the Data field  54 .  
         [0055]     Referring to  FIG. 2  again, the link layer  232  includes an isochronous stream packet detecting portion  2321 .  
         [0056]     The isochronous stream packet detecting portion  2321  detects the isochronous stream packets in packets input from the physical layer  231  referring to values of the tag field  512  of the isochronous header  51 .  
         [0057]     A value of 00 in the tag field  512  illustrated in  FIG. 5  indicates that a packet is in an isochronous transmission mode or an asynchronous transmission mode according to the conventional IEEE 1394a, and a value of 01 in the tag field  512  indicates an IEC 61883 CIP header. Also, a value of 10 in the tag field  512  indicates the IP over IEEE 1394 according to the present embodiment, and a value of 11 in tag field  512  indicates a general asynchronous stream packet (GASP) according to the conventional IEEE 1394a standard. The isochronous stream packets are input to the isochronous stream packet module  2213  of the IP over IEEE 1394 device driver  222  using the reserved value of 10 in a tag field  512  of the isochronous header  51 .  
         [0058]     The transaction layer  233  controls the link layer  232  such that reading and writing are performed on a node having a particular address. More specifically, the transaction layer  233  issues a read transaction such that a read can be performed on a node having a particular address. The transaction layer  233  also issues a write transaction such that a write can be performed on the node. Additionally, the transaction layer  233  issues a lock transaction such that updates can be performed until a specific condition is satisfied.  
         [0059]     The bus management layer  234  manages the IEEE 1394 bus by controlling the transaction layer  233 , the link layer  232  and the physical layer  231 . In particular, the bus management layer  234  includes an isochronous resource manager (IRM) which manages a limited channel resource, a bandwidth resource and the like, and the cycle master which controls bus timing.  
         [0060]     Referring to  FIG. 2  again, the protocol stack of the isochronous stream transmission device mounted on the second node  3  according to the present embodiment is composed of an application layer  31 , a TCP/IP layer  32 , and an IEEE 1394 layer  33 .  
         [0061]     The application layer  31  includes an isochronous resource obtaining portion  311 , an isochronous stream transmission responding portion  312 , and an isochronous stream transmitting portion  313 .  
         [0062]     When the application layer  31  receives a request for transmission of the isochronous stream over the IEEE 1394 bus  4  using the asynchronous block write, the isochronous resource obtaining portion  311  obtains an isochronous resource for transmission of the isochronous stream. More specifically, the isochronous resource obtaining portion  311  informs the IP over IEEE 1394 device driver  322  in the IP layer  32  of the content type and the maximum packet size of the isochronous stream by calling the IOCTL in the application layer  31 . The content type and the maximum packet size of the isochronous stream is used to decide a channel and bandwidth of the isochronous stream that the second node  3  intends to transmit. Afterwards, the isochronous resource obtaining portion  311  is informed of the channel and the bandwidth, which correspond to the isochronous source, as a response to the content type and maximum packet size sent to the IP over IEEE 1394 device driver  322 , that is, the return value for the IOCTL call. In the present invention, the maximum packet size is used as a data rate.  
         [0063]     The isochronous stream transmission responding portion  312  transmits a response including information about the channel and the bandwidth, which are results of obtaining the isochronous resource in the isochronous resource obtaining portion  311 , to the first node  2  over the IEEE 1394 bus  4  using an asynchronous block write by calling the asynchronous block write function in the application layer  31 .  
         [0064]     When the isochronous stream transmitting portion  313  is informed by the first node  2 , which received the response transmitted from the isochronous stream transmission responding portion  312 , that preparation for isochronous stream receipt is completed, the isochronous stream transmitting portion  313  uses the service of IP based on the obtained result in the isochronous resource obtaining portion  311  and transmits the isochronous stream over the IEEE 1394 bus  4  by calling the isochronous stream transmission function in the application layer  31 . More specifically, by using a service such as packet routing through an optimized path that the IP provides, the isochronous stream transmitting portion  313  can transmit the isochronous stream over the IEEE 1394 bus  4  with guaranteed QOS.  
         [0065]     The TCP/IP layer  32  contains an isochronous stream packet generating portion  321  and an IP over IEEE 1394 device driver  322 .  
         [0066]     The isochronous stream packet generating portion  321  generates the isochronous stream packets from the isochronous stream in the TCP/IP layer  32  according to an isochronous stream transmission function call of the isochronous stream transmitting portion  313  from the application layer  31 . In particular, the isochronous stream packet generating portion  321  records a predetermined value in a type of service (TOS) field of an IPv4 header if the isochronous stream packet is an IPv4 packet, or a predetermined value in a traffic class field of an IPv6 header if the isochronous stream packet is an IPv6 packet so that the isochronous stream packets and the general packets can be managed by different queues in the IP over IEEE 1394 device driver  322 . The specific values recorded in the TOS field of the IPv4 header or the traffic class field of the IPv6 header will now be described with reference to  FIG. 6 .  
         [0067]      FIG. 6  is a diagram for explaining packet management of the isochronous stream packet module illustrated in  FIG. 2 .  
         [0068]     Referring to  FIG. 6 , each of the TOS field of the IPv4 header or the traffic class field of the IPv6 header includes a differentiated service code point (DSCP) field  531  and a currently unused (CU) field  532 .  
         [0069]     The isochronous stream packet generating portion  321  records a value of 00 in the CU field  532  when the packet output from the application layer  31  is a general packet, and records a value of 01 when the packet output from the application layer  31  is an isochronous stream packet.  
         [0070]     The IP over IEEE 1394 device driver  322  includes an asynchronous block write module  3211 , an asynchronous stream packet module  3212 , and an isochronous stream packet module  3213 .  
         [0071]     The asynchronous block write module  3211  corresponds to the above-mentioned asynchronous block write module  2211 , the asynchronous stream packet module  3212  corresponds to the above-mentioned asynchronous stream packet module  2212 , and the isochronous stream packet module  3213  corresponds to the above-mentioned isochronous stream packet module  2213 .  
         [0072]     The IP over IEEE 1394 device driver  322  is informed of the content type and the maximum packet size of the isochronous stream through the IOCTL call from the application layer  31 , and informs an isochronous resource manager in the transaction layer  333  of the content type and the maximum packet size of the isochronous stream. Thereafter, when the IP over IEEE 1394 device driver  322  is assigned the channel and bandwidth by the isochronous resource manager, the IP over IEEE 1394 device driver  322  informs the application layer  31  of the assigned channel and bandwidth. On the other hand, when the IP over IEEE 1394 device driver  322  is not assigned the channel and bandwidth by the isochronous resource manager, the IP over IEEE 1394 device driver  322  informs the application layer  31  that the isochronous stream cannot be transmitted.  
         [0073]     Further, the IP over IEEE 1394 device driver  322  registers the assigned channel and bandwidth to an output plug control register (oPCR) and an output master plug register (oMPR) of the second node  3  and to an input plug control register (iPCR) of the first node  2  and an input master plug register (iMPR) through an asynchronous lock transaction, and generates an isochronous channel for transmitting the isochronous stream packets. oPCR, oMPR, iPCR, and iMPR are registers defined by the IEEE 1394 standard for generating an isochronous channel.  
         [0074]     In addition, the IP over IEEE 1394 device driver  322  manages the isochronous stream packet and the general stream packet with different queues with reference to the value of the TOS field of the IPv4 header when the isochronous stream packet generated by the isochronous stream packet generating portion  321  is an IPv4 packet, or with reference to the value of the traffic class field of the IPv6 header when the isochronous stream packet is an IPv6 packet. Also, the IP over IEEE 1394 device driver  322  transmits the isochronous stream packet based on management which will be described in detail with reference to  FIG. 6 .  
         [0075]     Referring to  FIG. 6 , the isochronous stream packet module  3213  of the IP over IEEE 1394 device driver  322  includes a packet divider  61 , a general packet queue  62 , and an isochronous stream packet queue  63 .  
         [0076]     The IP over IEEE 1394 device driver  322  stores the general packet in the general packet queue  62  when the value of the CU field  532  in the TOS field of the IPv4 header or in the traffic class field of the IPv6 header is 00, and stores the isochronous stream packet in the isochronous stream packet queue  63  when the value of the CU field  532  is 01. The packets stored in the general packet queue  62  and the isochronous stream packet queue  63  are stored in an IEEE 1394 transmission queue  64  of the IEEE 1394 device driver  322  according to a scheduling algorithm which is the most suitable for the network environment where the first node  2  and the second node  3  are placed. That is, as shown in  FIG. 3 , every 125 μsec after a cycle start packet is received, an isochronous stream packet is transmitted through the isochronous channel, and then, the asynchronous stream packets and the asynchronous block write packets are transmitted through the channel arbitration.  
         [0077]     The IEEE 1394 layer  33  includes a physical layer  331 , a link layer  332 , a transaction layer  333 , and a bus management layer  334 . The transaction layer  333 , the link layer  332 , the physical layer  331 , and the bus management layer  334  correspond to an IEEE 1394 device driver.  
         [0078]     The physical layer  331  corresponds to the above-mentioned physical layer  231 , the link layer  332  corresponds to the above-mentioned link layer  232 , the transaction layer  333  corresponds to the above-mentioned transaction layer  233 , and the bus management layer  334  corresponds to the above-mentioned bus management layer  234 .  
         [0079]     However, the link layer  332  includes an isochronous stream packet displaying portion  3321  instead of the isochronous stream packet detecting portion  2321  of the link layer  232 .  
         [0080]     As shown in  FIGS. 4 and 5 , the isochronous stream packet displaying portion  3321  records the value of 10, which indicates the isochronous stream packet, in the tag field  512  of the isochronous header  51  in order to distinguish the isochronous stream packet from the general packet.  
         [0081]      FIGS. 7 and 8  are flowcharts illustrating a method of transmitting and receiving an isochronous stream according to an exemplary embodiment of the present invention.  
         [0082]     Referring to  FIGS. 7 and 8 , the method of transmitting and receiving the isochronous stream includes the following operations. The operations of the method of transmitting and receiving an isochronous stream is processed in the first node  2  (Node A) and the second node  3  (Node B) illustrated in  FIG. 2 . Accordingly, the above description related to the isochronous stream receiving device mounted on the first node  2  and the isochronous stream transmission device mounted on the second node  3  will be applied to the method of transmitting and receiving an isochronous stream even though the description is omitted below.  
         [0083]     In operation  71 , the isochronous stream transmission requesting portion  211  of the first node  2  sends a request to the second node  3  to transmit an isochronous stream using an asynchronous block write over the IEEE 1394 bus  4  by calling the asynchronous block write function in the application layer  21 .  
         [0084]     In operation  81 , the isochronous resource obtaining portion  311  of the second node  3  receives the request for the isochronous stream transmission using the asynchronous block write over the IEEE 1394 bus  4 .  
         [0085]     In operation  82 , the isochronous resource obtaining portion  311  of the second node  3  obtains the isochronous resource for transmitting the isochronous stream in response to the request received in operation  81 . More specifically, the second node  3  informs the IP over the IEEE 1394 device driver  322  in the IP layer  32  of the content type and the maximum packet size of the isochronous stream by calling the IOCTL in the application layer  31 .  
         [0086]     In operation  83 , the IP over IEEE 1394 device driver  322  of the second node  3  is informed of the content type and the maximum packet size of the isochronous stream through the IOCTL call from the application layer  31 . The IP over 1394 IEEE device driver  322  informs the isochronous resource manager in the transaction layer  333  of the content type and the maximum packet size of the isochronous stream, and is assigned the channel and bandwidth by the isochronous resource manager.  
         [0087]     In operation  84 , when the IP over IEEE 1394 device driver  322  of the second node  3  is assigned the channel and bandwidth in operation  83 , the IP over IEEE 1394 device driver  322  registers the assigned channel and bandwidth with the oPCR and oMPR of the second node  3  and with the iPCR of the first node  2  and the iMPR through the asynchronous lock transaction to generate the isochronous channel for transmitting the isochronous stream packets, and informs the application layer  31  of the assigned channel and bandwidth.  
         [0088]     In operation  85 , when the IP over IEEE 1394 device driver  322  of the second node  3  is not assigned the channel and bandwidth, the IP over IEEE 1394 device driver  322  informs the application layer  31  that the isochronous stream cannot be transmitted.  
         [0089]     In operation  86 , when the isochronous stream transmission responding portion  312  of the second node  3  is informed of the channel and bandwidth informed by the IP over IEEE 1394 device driver  322  in operation  84 , the isochronous stream transmission responding portion  312  transmits the response including information about the channel and bandwidth to the first node  2  using the asynchronous block write over the IEEE 1394 bus  4  by calling the asynchronous block write function in the application layer  31 . On the other hand, when the isochronous stream transmission responding portion  312  is informed by the IP over IEEE 1394 device driver  322  that the isochronous stream cannot be transmitted, the isochronous stream transmission responding portion  312  transmits to the first node  2  a response which indicates that the isochronous stream transmission is not possible using the asynchronous block write over the IEEE 1394 bus  4  by calling the asynchronous block write function from the application layer  31 .  
         [0090]     In operation  72 , the isochronous stream receipt preparing portion  212  of the first node  2  receives from the second node  3  the response to the request for the isochronous stream transmission.  
         [0091]     In operation  73 , when the response received in operation  72  includes the channel and bandwidth for transmitting the isochronous stream, the isochronous stream receipt preparing portion  212  determines that isochronous stream transmission is possible, or determines that isochronous stream transmission is not possible when the response indicates that the isochronous stream transmission is not possible.  
         [0092]     In operation  74 , when it is determined that the isochronous stream transmission is possible in operation  73 , the isochronous stream receipt preparing portion  212  of the first node  2  prepares to receive the isochronous stream with reference to the channel and bandwidth included in the response by calling the IOCTL in the application layer  21 .  
         [0093]     In operation  75 , when it is determined that the isochronous stream transmission is not possible in operation  73 , the isochronous stream receipt preparing portion  212  of the first node  2  terminates an isochronous stream transmission request process.  
         [0094]     In operation  76 , when the isochronous stream receipt preparing portion  212  of the first node  2  completes the preparation for the isochronous stream receipt, the isochronous stream receipt preparing portion  212  informs the second node  3  that the isochronous stream receipt has been prepared using the asynchronous block write over the IEEE 1394 bus  4  by calling the asynchronous block write function in the application layer  21 .  
         [0095]     In operation  87 , when the isochronous stream transmitting portion  313  of the second node  3  is informed of the fact that the isochronous stream receipt has been prepared in operation  76 , the isochronous stream transmitting portion  313  transmits the isochronous stream to the first node  2  using the service of IP based on the obtaining result of the isochronous resource obtaining portion  311  over the IEEE 1394 bus  4  by calling the isochronous stream transmission function in the application layer  31 .  
         [0096]     In operation  77 , the isochronous stream receiving portion  213  receives the isochronous stream from the second node  3 , which has received the information from the isochronous stream receipt preparing portion  212 , by using the service of the IP over the IEEE 1394 bus  4 .  
         [0097]     The operations  71  through  77  are included in the method of receiving the isochronous stream, and the operations  81  through  87  are included in the method of transmitting the isochronous stream.  
         [0098]      FIG. 9  is a flowchart illustrating in detail operation  87  illustrated  FIG. 8 .  
         [0099]     Referring to  FIG. 9 , operation  87  includes the following operations.  
         [0100]     In operation  871 , the isochronous stream transmitting portion  313  of the second node  3  outputs the isochronous stream from the application layer  31  to the TCP/IP layer  32 .  
         [0101]     In operation  872 , the isochronous stream packet generating portion  321  of the second node  3  generates the isochronous stream packets from the isochronous stream output in operation  871 . In particular, the isochronous stream packet generating portion  321  of the second node  3  records a predetermined value in the TOS field of the IPv4 header when the isochronous stream packet is an IPv4 packet or records a predetermined value in the traffic class field of the IPv6 header when the isochronous stream packet is an IPv6 packet so that the isochronous stream packet and the general packet are managed with different queues by the IP over the IEEE 1394 device driver  322 .  
         [0102]     In operation  873 , the IP over IEEE 1394 device driver  322  of the second node  3  manages the isochronous stream packet and the general packet with different queues with reference to the value of the TOS field of the IPv4 header when the isochronous stream packet generated in operation  872  is an IPv4 packet or with reference to the value of the traffic class field of the IPv6 packet when the isochronous stream packet is an IPv6 packet. Also, the IP over IEEE 1394 device driver  322  transmits the isochronous stream packet based on the management. More specifically, the IP over IEEE 1394 device driver  322  of the second node  3  stores the general packet in the general packet queue  62  when the value of the CU field  532  of the TOS field in the IPv4 header or the traffic class field in the IPv6 header is 00, and stores the isochronous stream packet in the isochronous stream packet queue  63  when the value of the CU field  532  is 01.  
         [0103]     In operation  874 , the IEEE 1394 layer  33  of the second node  3  stores the packets which are stored in the general packet queue  62  and the isochronous stream packet queue  63  in operation  873  in an IEEE 1394 transmission queue  64  according to a scheduling algorithm which is the most suitable for the network environment where the first node  2  and the second node  3  are placed.  
         [0104]     In operation  875 , the IEEE 1394 layer  33  of the second node  3  transmits the isochronous stream packets in the order that they are stored in the IEEE 1394 transmission queue  64  in operation  874 . At this moment, the isochronous stream packet displaying portion  3321  of the IEEE 1394 layer  33  records a value of 10 which indicates an isochronous stream packet in the tag field  512  of the isochronous header  51  so that the isochronous stream packet can be distinguished from the general packets.  
         [0105]      FIG. 10  is a flowchart illustrating in detail operation  76  illustrated in  FIG. 8 .  
         [0106]     Referring to  FIG. 10 , operation  76  includes the following operations.  
         [0107]     In operation  761 , the isochronous stream packet detecting portion  2321  of the first node  2  detects the isochronous stream packets from the packets input from the physical layer  231  with reference to the value of the tag field  512  of the isochronous header  51 , and outputs the detected isochronous stream packets to the isochronous stream packet module  2213  of the IP over IEEE 1394 device driver  222 .  
         [0108]     In operation  762 , the isochronous stream extracting portion  221  of the first node  2  extracts the isochronous stream from the isochronous stream packets output from the isochronous stream packet module  2213  which received the isochronous stream packets in operation  761 . More specifically, the isochronous stream extracting portion  221  of the first node  2  removes headers from the isochronous stream packets and collects data recorded in payloads of the isochronous stream packets to generate the isochronous stream, and outputs the generated isochronous stream to the isochronous stream receiving portion  213  of the application layer  21 .  
         [0109]     In operation  763 , the isochronous stream receiving portion  213  of the first node  2  receives the isochronous stream which was output in operation  762 .  
         [0110]     The embodiments of the present invention can be written as computer programs and can be implemented in general-use digital computers that execute the programs using a computer readable recording medium. Examples of the computer readable recording medium include magnetic storage media (e.g., ROM, floppy disks, hard disks, etc.), optical recording media (e.g., CD-ROMs, or DVDs), and storage media such as carrier waves (e.g., transmission through the Internet).  
         [0111]     According to the present invention, by allowing an IP over IEEE 1394 to support isochronous stream transmission, an isochronous stream can be efficiently and securely transmitted using an IP service. That is, isochronous stream packets can be transmitted with a QOS that is guaranteed through an optimized path. As a result, the quality of the real-time transmission of multimedia contents, for example, voice over IP (VoIP), image communications and a streaming service between IT devices and electric home appliances can be enhanced.  
         [0112]     In particular, the present invention is more useful for IP over IEEE 1394-based isochronous stream transmission when time division type isochronous Ethernet according to an the IEEE 802.9 committee standard is supported. Further, according to the present invention, both isochronous stream transmission and asynchronous stream transmission can be supported in a single application, and isochronous stream packets can be more rapidly transmitted by managing the isochronous stream packets with different queues.  
         [0113]     While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims.