Source: http://www.google.com/patents/US6977939?dq=system+for+measuring+web+traffic&ei=Lg8FT__TIIr-sQKzxaGRCg
Timestamp: 2016-05-04 02:26:02
Document Index: 40591352

Matched Legal Cases: ['art 1', 'art 2', 'art 3', 'art 4', 'art 5', 'art 6']

Patent US6977939 - Method and apparatus for emulating ethernet functionality over a serial bus - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsThe invention allows applications to transparently use a bus, such as the IEEE-1394 serial bus, as if it were an Ethernet (IEEE 802.3). In a conventional Ethernet, each node is assigned a unique 6-byte MAC address in order to receive frames addressed to it over the LAN. According to the invention, IEEE-1394...http://www.google.com/patents/US6977939?utm_source=gb-gplus-sharePatent US6977939 - Method and apparatus for emulating ethernet functionality over a serial busAdvanced Patent SearchPublication numberUS6977939 B2Publication typeGrantApplication numberUS 09/769,438Publication dateDec 20, 2005Filing dateJan 26, 2001Priority dateJan 26, 2001Fee statusPaidAlso published asUS7317734, US20020136225, US20050157732Publication number09769438, 769438, US 6977939 B2, US 6977939B2, US-B2-6977939, US6977939 B2, US6977939B2InventorsJoseph M. Joy, Arvind Murching, Lawrence R. CleetonOriginal AssigneeMicrosoft CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (30), Non-Patent Citations (29), Referenced by (49), Classifications (7), Legal Events (5) External Links: USPTO, USPTO Assignment, EspacenetMethod and apparatus for emulating ethernet functionality over a serial bus
US 6977939 B2Abstract
The invention allows applications to transparently use a bus, such as the IEEE-1394 serial bus, as if it were an Ethernet (IEEE 802.3). In a conventional Ethernet, each node is assigned a unique 6-byte MAC address in order to receive frames addressed to it over the LAN. According to the invention, IEEE-1394 bus node identifiers are mapped to Ethernet MAC addresses using for example a digital signature algorithm. Ethernet frames are then “wrapped” into 1394 bus packets and addressed to the destination node using the hashed address. The receiver unwraps the 1394 packet and restores the Ethernet frame to its original form. An optimum packet size for transmission of Ethernet packets over the 1394 bus is selected with reference to speed topology maps in the 1394 bus nodes, and this optimum size is transmitted to bus nodes. This packet size is reported to TCP to specify the packet size, and all packets larger than that size are fragmented and reassembled at the receiving node. The protocol works transparently across networks that are linked via bridges.
1. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocol, wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; (3) transmitting the second packet over the network to a destination node in the network; and (4) in response to determining that no mapping exists for a particular Ethernet address, transmitting the second packet over a bridge channel that is monitored by a network bridge. 2. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocol, wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; (3) transmitting the second packet over the network to a destination node in the network; and (4) prior to step (1), generating an Ethernet address derived from node addressing information using a digital signature algorithm. 3. The method of claim 2, wherein the generating step comprises the step of performing an exclusive OR operation between a portion of a digital signature generated by the digital signature algorithm and a stored constant.
4. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocol, wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; (3) transmitting the second packet over the network to a destination node in the network; (4) prior to step (1), generating an Ethernet address derived from node addressing information; and (5) determining whether the generated Ethernet address conflicts with other Ethernet addresses in the network. 5. The method of claim 4, wherein the determining step comprises the step of transmitting the generated Ethernet address and the node addressing information to other nodes in the network and evaluating responses from the other nodes.
6. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocol, wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses and further includes binding an Ethernet-compliant application programming interface (API) that emulates Ethernet functionality using an IEEE 1394 serial bus; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; and (3) transmitting the second packet over the network to a destination node in the network. 7. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocol, wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses, the step of converting further including converting the first request to transmit the packet into an IEEE-1394 serial bus request; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; and (3) transmitting the second packet over the network to a destination node in the network including transmitting the second packet over an asynchronous data channel on the serial bus. 8. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocol, wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses, the step of converting further including converting the first request to transmit the packet into an IEEE-1394 serial bus request; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; and (3) transmitting the second packet over the network to a destination node in the network including transmitting the second packet over an isochronous data channel on the serial bus. 9. A method of emulating an Ethernet protocol in a network that uses a non-Ethernet protocol, comprising the steps of:
(1) converting a first request to transmit a packet using an Ethernet protocol into a second request to transmit the packet using the non-Ethernet protocols wherein the conversion is based on a stored mapping between Ethernet and non-Ethernet addresses; (2) encapsulating the packet into a second packet compatible with the non-Ethernet protocol; (3) transmitting the second packet over the network to a destination node in the network; and (4) determining an optimum packet size for use in transmitting packets over the network, wherein the step of determining the optimum packet size is performed by consulting speed topology maps for heterogeneous nodes on the network. 10. The method of claim 9, wherein the optimum packet size is selected based on a maximum packet size that can be accommodated by any two Ethernet-emulated nodes on the network.
11. A system that supports Ethernet emulation, comprising:
a non-Ethernet network communication medium including an IEEE-1394 compliant serial bus; and a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols; a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol (ARP) that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols wherein the interface driver converts requests to transmit Ethernet packets into requests to transmit 1394 bus-specific packets, and wherein the interface driver, in response to determining that a destination Ethernet address is unknown, transmits a packet over a bridge channel that is monitored by a network bridge. 12. A system that supports Ethernet emulation, comprising:
a non-Ethernet network communication medium; and a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols; a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol (ARP) that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols, and wherein the interface driver receives node-specific information from other network nodes and, in response thereto, associates the node-specific information with Ethernet MAC addresses. 13. A system that supports Ethernet emulation, comprising:
a non-Ethernet network communication medium including an IEEE-1394 compliant serial bus; and a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols; a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol (ARP) that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols wherein the interface driver converts requests to transmit Ethernet packets into requests to transmit 1394 bus-specific packets, and wherein the interface driver generates an internal table that maps an Ethernet address to node addressing information obtained from another node in the network and stores the mapping information for use in transmitting data packets over the communication medium. 14. The system according to claim 13, wherein the interface driver generates an Ethernet address using a digital signature algorithm applied to the node addressing information.
15. The system according to claim 13, wherein the interface driver performs a conflict resolution procedure to determine whether the generated Ethernet address conflicts with other Ethernet addresses in the system.
16. A system that supports Ethernet emulation, comprising:
a non-Ethernet network communication medium including an IEEE-1394 compliant serial bus; and a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols; a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol (ARP) that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols wherein the interface driver converts requests to transmit Ethernet packets into requests to transmit 1394 bus-specific packets, and wherein the interface driver transmits emulated Ethernet packets using an asynchronous channel on the 1394 bus. 17. A system that supports Ethernet emulation, comprising:
a non-Ethernet network communication medium including an IEEE-1394 compliant serial bus; and a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols; a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol (ARP) that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols wherein the interface driver converts requests to transmit Ethernet packets into requests to transmit 1394 bus-specific packets, and wherein the interface driver transmits emulated Ethernet packets using an isochronous channel on the 1394 bus. 18. A system that supports Ethernet emulation, comprising:
a non-Ethernet network communication medium; a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols; a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol (ARP) that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols; and a network bridge node coupled to the network communication medium, wherein in response to a unicast Ethernet packet received on the bridge channel, the network bridge node retransmits the packet to other networks to which the network bridge node is connected. 19. A system that supports Ethernet emulations comprising:
a non-Ethernet network communication medium; and a plurality of network nodes coupled to the non-Ethernet network communication medium, each network node comprising in combination: a network card and associated drivers that transmit and receive packets over the network communication medium using network-specific protocols: a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol; an Address Resolution Protocol IARPI that translates IP addresses into Ethernet Media Access Control (MAC) addresses; and an interface driver that presents an Ethernet-compliant interface to the TCP/IP protocol and ARP, wherein the interface driver converts Ethernet-specific requests from the TCP/IP protocol and ARP into requests that conform to the network-specific protocols, and wherein the interface driver determines an optimum packet size for transmitting emulated Ethernet packets on the network communication medium, wherein the interface driver determines the optimum packet size by consulting speed topology maps from a plurality of network nodes.
The well-known Ethernet protocol (IEEE 802.3) provides a method of transmitting data packets over a local area network. Ethernet packets are transmitted on a cable without pre-arranged scheduling, such that collisions may occur on the cable. The protocol includes mechanisms for detecting collisions and retransmitting packets that fail to reach their destination due to a collision. Bridges between networks allow packets to be further transmitted between nodes residing on different networks (see FIG. 4). Each data packet, referred to as a “frame” in Ethernet parlance, conforms to a well-known standard including 6-byte (48-bit) source and destination addresses embedded in a 14-octet frame header.
It is conventional to transmit Internet Protocol (IP) packets, which rely on a different format and addressing scheme, over an Ethernet. As is conventional, IP data packets are “encapsulated” in an Ethernet frame, transmitted over an Ethernet LAN, and “unwrapped” at the receiving node to restore the original IP packet.
FIG. 2 shows a conventional system in which IP packets are transmitted between two nodes 200 and 250 over an Ethernet LAN. Application programs on each node (201 and 251) communicate with each other using TCP/IP protocols 202 and 252, respectively. As part of this process, an Address Resolution Protocol (ARP) 203 and 253 is used in each Ethernet node to translate 32-bit IP addresses into 48-bit MAC addresses and vice versa.
ARP works by broadcasting a packet containing the IP address with which the transmitting node is interested in communicating to all nodes attached to an Ethernet. Most nodes ignore the broadcast, but the ARP in the destination node responds upon recognizing that the IP address in the packet matches its own. The destination node responds with a message indicating its MAC address, which the transmitting node then uses to transmit the packet. Each node typically maintains a cache of ARP responses on the assumption that address mappings rarely change. As shown in FIG. 4, ARP also works across bridged networks, since ARP broadcasts are received by bridges that then pass them on to nodes on the bridged networks. Consequently, ARP responses may arrive from networks other than the LAN on which the transmitting node resides.
Recently, a serial bus standard known as the IEEE 1394 bus has been developed. Implementations of this bus are based on the internationally adopted ISO/IEC 13213 (ANSI/IEE 1212) CSR Architecture Specification and the IEEE 1394-1995 Serial Bus Specification, which are publicly available documents. A typical system conforming to the IEEE 1394 standard includes a plurality of nodes that are interconnected via point-to-point links, such as cables, that each connect a single node of the serial bus to another node of the serial bus. The nodes are addressable entities that can be independently reset and identified. The 1394 bus provides both asynchronous and isochronous (time-guaranteed delivery) capabilities. The IEEE 1394 bus standard requires that each node have a 64-bit unique node identifier, which permanently identifies the node throughout its life, independent from other nodes or events on the serial bus.
According to another aspect of the invention, an optimum packet size for transmission of Ethernet packets over the 1394 bus is selected and broadcast to all bus nodes. The protocol works transparently across networks linked via bridges, by utilizing abridge channel for traffic destined for nodes external to the local 1394 bus.
FIG. 2 shows a conventional Ethernet local area network (LAN) in which a conventional Address Resolution Protocol (ARP) is used to map IP addresses to Ethernet MAC addresses.
FIG. 11 shows how four different local area networks can be integrated into one virtual LAN using bridges, wherein one or more of the networks is an emulated Ethernet implemented on an IEEE 1394 serial bus.
An IEEE 1394 interface 142 may also be provided. The IEEE 1394 interface 142 couples an IEEE 1394-compliant serial bus 145 to the system bus 130 or similar communication bus. The IEEE 1394-compliant serial bus 145, as known in the art, allows multiple devices 148 to communicate with the computer 100 and each other using high-speed serial channels. The IEEE 1394 serial bus standard is based largely upon the internationally adopted ISO/JEC 13213 (ANSI/IEEE 1212) CSR Architecture Specification and the IEEE 1394-1995 Serial Bus Specification. Additional buses such as the PCI bus can be provided in computer 100 and interfaced to the IEEE 1394 and other buses.
The other input to the XOR operation is a randomly-generated 48-bit constant 1006, which could form part of an Ethernet-over-1394 protocol specification. The purpose of the XOR operation is to reduce the likelihood that the generated MAC address would conflict with some other scheme for generating MAC addresses from the 64-bit node identifier. A proposed constant is: 0xDE 0xE4 0xED 0xB8, which was generated by coin-tossing. Finally, the 48-bit pattern is converted into a valid Ethernet MAC address by setting the “locally administered” bit and clearing the “multicast bit.” The resultant MAC address 1007 represents a 46 bit hash of the original 64-bit node identifier.
Various MAC address generation schemes outlined above leave a small but finite possibility that two identical MAC addresses could be created. Accordingly, in certain embodiments a conflict resolution step is also performed, as illustrated by step 603 in FIG. 6. The conflict resolution procedures, however, are optional given the small chance of a conflict (e.g., much smaller than the probability of a hardware failure). One protocol, described below, detects collisions among all E/1394 nodes in all E/1394 segments in abridged LAN (for example,between LANs 1101 and 1103 in FIG. 11). E/1394 nodes that use IEEE-assigned MAC addresses should not participate in collision detection and resolution, with the exception that bridge nodes must forward the collision-detection traffic as described further below. This protocol also has the property that nodes newly entering a network do not knock out nodes already in the network.
(a) Broadcast the packet on all other connected LAN segments; (b) Process (for collision detection) any MAC13TO13HW13MAPPING13PKTs received from other connected LAN segments before sending them out on the local E/1394 segment; and (c) Broadcast MAC13TO13HW13MAPPING13PKTs received on each connected E/1394 segment to other Ethernet LAN segments. E/1394 nodes should transmit the packet under the following situations, with the specified values for the flnit field:
(a) On initialization, 3 times, one second apart, with flnit set to 1. (b) In response to a conflicting MAC13TO13HW13MAPPING13PKT received from some other node, the flnit field is set to 1 for the first 10 seconds after initialization, and 0 afterwards. To resolve collisions, a node wins a collision under the following conditions: (1) During the first 10 seconds of initialization, if the conflicting received packet has a numerically smaller Eu64Id field AND its flnit value is 1. (2) After the first 10 seconds of initialization, if the conflicting received packet has a numerically smaller Eu64Id field OR its flnit value set to 1. The node loses collision resolution otherwise. Nodes losing collision resolution should disable their network interface and not attempt to rejoin with the same MAC address. Optionally, they may save the fact that they have lost the collision resolution in persistent memory, and attempt to re-join with a different MAC address.
FIG. 11 shows how four different local area networks can be integrated into one virtual LAN using bridges, wherein one or more of the networks is an emulated Ethernet implemented on an IEEE 1394 serial bus. As shown in FIG. 1, a first network 1101 comprises an E/1394 network; that is, a 1394 serial bus including nodes having Ethernet emulation capabilities. Node 1108 on this network includes for example an emulated MAC address of 123 and IP address of 10.0.0.1. Network 1101 is coupled to network 1102 via bridge 1105. Network 1102 may comprise, for example, a CAT 5 Ethernet LAN including a node 1109 having a real MAC address of 456 and IP address of 10.0.0.2.
5. Since Node 1110 owns address 10.0.0.3, it responds by sending an ARP reply addressed to MAC address 123 (the MAC address that originated the ARP request). The E/1394 driver on node 1110 recognizes that MAC 123 is not on the local LAN 1103 (because it uses link-layer ARP to build a table of MAC-addresses and 1394 information for all E/1394 nodes on the local 1394 Bus), so it sends the unicast IP ARP reply on the bridge channel.
7. Bridge 1105 receives this packet, and since it recognizes MAC 123, sends the packet directly to node 1108, using the IEEE 1394 information corresponding to this MAC address—it looks up this information it its MAC to 1394 table.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5774695 *Mar 22, 1996Jun 30, 1998Ericsson Inc.Protocol interface gateway and method of connecting an emulator to a networkUS5845152Mar 19, 1997Dec 1, 1998Apple Computer, Inc.Method for transmission of isochronous data with two cycle look aheadUS5911059Dec 18, 1996Jun 8, 1999Applied Microsystems, Inc.Method and apparatus for testing softwareUS5938735Oct 21, 1997Aug 17, 1999Ricoh Company, Ltd.System for establishing optimized ISDN communication by identifying common communication attributes of destination and source terminals prior to establishing communication link therebetweenUS5953511Apr 8, 1997Sep 14, 1999National Instruments CorporationPCI bus to IEEE 1394 bus translatorUS5978902Dec 17, 1997Nov 2, 1999Advanced Micro Devices, Inc.Debug interface including operating system access of a serial/parallel debug portUS5991520 *Feb 2, 1996Nov 23, 1999Sony CorporationApplication programming interface for managing and automating data transfer operations between applications over a bus structureUS6088364Jul 14, 1997Jul 11, 2000Yamaha CorporationInterface apparatus connecting between multimedia network and music networkUS6094530Apr 29, 1998Jul 25, 2000Intel CorporationRemotely monitoring execution of a programUS6134662Jun 26, 1998Oct 17, 2000Vlsi Technology, Inc.Physical layer security manager for memory-mapped serial communications interfaceUS6219697 *May 2, 1997Apr 17, 20013Com CorporationMethod and apparatus for operating the internet protocol over a high-speed serial busUS6266729 *Mar 18, 1999Jul 24, 2001Microsoft CorporationComputer for encapsulating legacy data transport protocol for IEEE 1394 serial busUS6272581 *Apr 27, 2000Aug 7, 2001Microsoft CorporationSystem and method for encapsulating legacy data transport protocols for IEEE 1394 serial busUS6279123Sep 15, 1998Aug 21, 2001Lucent Technologies, Inc.System for viewing and monitoring embedded processor operationUS6347337Aug 20, 1999Feb 12, 2002Intel CorporationCredit based flow control scheme over virtual interface architecture for system area networksUS6353595Nov 8, 1999Mar 5, 2002Siemens AktiengesellschaftMethod and configuration for the network-wide analysis of connections in telecommunications networksUS6374399Apr 21, 1999Apr 16, 2002Advanced Micro Devices, Inc.Apparatus and method for providing list and read list capability for a host computer systemUS6378000Apr 29, 1999Apr 23, 2002Mitsubish Electric Research Laboratories, IncAddress mapping in home entertainment networkUS6430635 *Sep 27, 1999Aug 6, 2002Lg Electronics IncProtocol interfacing methodUS6434117 *Mar 5, 1999Aug 13, 2002Nec CorporationIEEE-1394 serial bus network capable of multicast communicationUS6496509 *Aug 3, 1998Dec 17, 2002Advanced Micro Devices, Inc.System for transmitting data packets between computers via an IEEE-1394 network mediumUS6496862 *Apr 29, 1999Dec 17, 2002Mitsubishi Electric Research Laboratories, Inc.Remote monitoring and control of devices connected to an IEEE 1394 bus via a gateway deviceUS6522654 *May 15, 1998Feb 18, 2003Harris-Exigent, Inc.Method for hosting the internet protocol suite on the IEEE-1394 high speed serial busUS6538758May 11, 1999Mar 25, 2003Canon Kabushiki KaishaImage output apparatus and method thereof, and image output systemUS6600756Jun 14, 1999Jul 29, 2003Hewlett-Packard Development Company, Lp.Method of improving the performance of a bus which is asynchronous-traffic intensiveUS6701371 *Aug 30, 1999Mar 2, 2004Samsung Electronics Co., Ltd.Data transfer method for matching upper protocal layer to high speed serial busUS6725311 *Sep 14, 2000Apr 20, 2004Microsoft CorporationMethod and apparatus for providing a connection-oriented network over a serial busUS20020133632Mar 5, 2002Sep 19, 2002Salloum Salazar Antonio EliasSystem of apparatuses that communicate via a bus structureUS20020141418 *Mar 19, 1999Oct 3, 2002Avner Ben-DorTunneling between a bus and a networkUS20030078063Jan 26, 2001Apr 24, 2003Yvon LegallaisMethod for isochronous resource management in a network based on hiperlan 2 techonology* Cited by examinerNon-Patent CitationsReference1"P1394.1 Draft Standard for High Performance Serial Bus Bridges", The Institute of Electrical and Electronics Engineers, Inc., Feb. 7, 1999, pp. 9-34.2Arun Ayyagari et al., "IEEE 802.11 Quality of Service", white paper, Mar., 2000, 10 pages.3Cisco Systems Inc., "Quality of Service (QoS) Networking", http://www.cisco.com/univercd/cc/td/doc/clsintwk/ito_doc/gos.htm, Jun. 1999.4Congruent Software, Inc., P. Johansson, "RFC 2734: Ipv4 over IEEE 1394", Dec. 1999.5D. Plummer, "RFC 826: An Ethernet Address Resolution Protocol", http://cie.motor.ru/RFC/Orig/rfc826.txt, Nov. 1982, pp. 1-8.6D. Steinberg, et al., "An Empirical Analysis of the IEEE-1394 Serial bus Protocol", IEEE Jan. 2000, pp. 58-64.7G. Hoffman et al., IEEE 1394: A Ubiquitous Bus, COMPCON '95, Mar. 5, 1995, pp. 1-9, www.skipstone.com/comcon.html.8IEEE std 1394-1995, IEEE Standard for a High Performance Serial Bus, 1996, pp. 1-45.9IETF, T. Saito, et al., "'IP over iso1394' and 'AV over iso1394' controlled by an extension of MCAP" http://search.ietf.org/internet-drafts/draft-ieft-ip1394-ip-over-iso1394-00.txt, pp. 1-11, Sep. 1999.10International Electrotechnical Commission, "Consumer audio/video equipment- Digital interface- Part 1: General", IEC First edition, Feb. 1998, Reference No. 61883-1, pp. 7-78.11International Electrotechnical Commission, "Consumer audio/video equipment- Digital Interface- Part 2: SD-DVCR data transmission", IEC First edition, Feb. 1998, Reference No. 61883-2, pp. 5-15.12International Electrotechnical Commission, "Consumer audio/video equipment- Digital interface- Part 3: HD-DVCR data transmission", IEC First edition, Feb. 1998, Reference No. 61883-3, pp. 5-13.13International Electrotechnical Commission, "Consumer audio/video equipment- Digital interface- Part 4: MPEG2-TS data transmission", IEC First edition, Feb. 1998, Reference No. 61883-4, pp. 5-23.14International Electrotechnical Commission, "Consumer audio/video equipment- Digital interface- Part 5: SDL-DVCR data transmission", IEC First edition, Feb. 1998, Reference No. 61883-5, pp. 5-17.15International Electrotechnical Commission, "Consumer Audio/Video Equipment- Digital Interface- Part 6: Audio and music data transmission protocol", IEC Reference No. 61883-6/WD2, Nov. 1999, pp. 1-23.16J. Postel, et al., "RFC 1042: A Standard for the Transmission of IP Datagrams over IEE 802 Networks", http://IEC,motor.ru/RFC/Orig/rfc1042.txt, Feb. 1988, pp. 1-14.17Microsoft Corporation, "A Short Overview of QoS Mechanisms and Their Interoperation", 1999, pp. 1-7.18Microsoft Corporation, "NdisClCloseCall", http://www.microsoft.com/hwdev/ddk/DDKdocs/Win2K103ndisx_7rsi.htm, Apr. 1999.19Microsoft Corporation, "NdisSendPackets", http://www.Microsoft.com/ddk/DDKdocs/Win2k/103ndisx_88s2.htm, Apr. 1999.20Microsoft Corporation, "Quality of Service Technical White Paper", 1999.21Microsoft Corporation, "SBP-2 Support and Windows 2000", http://agent.microsoft.com/hwdev/print/sbp2_w2000.htm, Mar. 25, 1999.22Microsoft Corporation, "Windows 2000 Driver Development Kit Documentation", http://www.microsoft.com/ddk/ddkdocs/win2K/vdd_24px.htm, et al., Apr. 1999.23Microsoft Corporation, "Windows 2000 Driver Development Kit Documentation", http://www.microsoft.com/hwdev/ddk/DDKdocs/Win2k/102gen_9eg7.htm, et al., Apr. 1999.24Microsoft Corporation, "Windows 2000 Driver Development Kit Documentation", www.microsoft.com/hwdev/ddk/DDKdocs/Win2k/102gen_9ffr.htm, et al., Apr. 1999.25Microsoft Corporation, "Windows 2000 Driver Development Kit Documentation", www.microsoft.com/hwdev/ddk/DDKdocs/Win2k/202mini_60yv.ntm, Apr. 1999.26MindShare, Inc., D. Anderson, "Fire Wire System Architecture IEEE 1394a Second Edition PC System Architecture Series", Dec. 1998, pp. 13-34.27Unibrain S.A., "The IEEE-1394 Development Toolkit for Windows NT 4.0/98/98SE", http://www.unibrain.com/products/ieee-1394/fireapi.htm, Apr. 14, 2000.28Unibrain S.A., "Unibrain FireAPI(TM) Documentation 1394 Class Driver, Kernal Mode Interface", Jul. 1999, pp. 1-193.29Unibrain S.A., "Unibrain FireAPI(TM) Documentation, 1394 Class Driver, User Mode Interface", Apr. 4, 2000, pp. 1-281.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7130925 *Jul 2, 2002Oct 31, 2006Sony CorporationInformation processing apparatus and method for receiving/transmitting data between an IEEE802-based format and an IEEE1394-based formatUS7174390 *Jan 4, 2002Feb 6, 2007Egenera, Inc.Address resolution protocol system and method in a virtual networkUS7208681Apr 26, 2005Apr 24, 2007Sony CorporationElectronic device and information reproduction systemUS7352726 *Aug 19, 2002Apr 1, 2008Sony CorporationCommunication device, communication method and program for packet communications between two networks that conform to different standardsUS7463647Jan 22, 2003Dec 9, 2008Sony CorporationMethod of and apparatus for providing reserved bandwidth to ethernet devices over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified hubUS7502840 *Nov 27, 2002Mar 10, 2009Cisco Technology, Inc.System and method for assigning media addresses to multiple internal nodesUS7529256 *Jul 8, 2005May 5, 2009Cisco Technology, Inc.Communication device client update system and methodUS7542474 *Feb 22, 2002Jun 2, 2009Sony CorporationMethod of and apparatus for providing isochronous services over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified hubUS7623501 *Nov 24, 2009Intel CorporationMethods and apparatus for resolving address mapping associated with a wireless mesh networkUS7724747 *Sep 30, 2008May 25, 2010International Business Machines CorporationMethods and apparatus for creating addressesUS7801150 *Sep 21, 2010Juniper Networks, Inc.Multiple media access control (MAC) addressesUS7848327Dec 7, 2010International Business Machines CorporationMethods and apparatus for creating addressesUS7908387 *Jun 17, 2003Mar 15, 2011Electronics And Telecommunications Research InstituteLookup service system in JINI-based home network supporting IEEE1394 and TCP/IPUS8051191Apr 28, 2008Nov 1, 2011Microsoft CorporationEthernet extensibilityUS8065435 *May 29, 2007Nov 22, 2011China Mobile Communications CorporationMethod for assigning address to the intelligent information household appliance and the sub-equipment in the household networkUS8094678Jan 10, 2012Sony CorporationMethod of and apparatus for providing reserved bandwidth to ethernet devices over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified HUBUS8379654Feb 19, 2013Sony CorporationMethod of and apparatus for providing isochronous services over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified hubUS8401024 *Nov 18, 2008Mar 19, 2013Telefonaktiebolaget Lm Ericsson (Publ)Ethernet address management systemUS8457122 *Aug 1, 2007Jun 4, 2013Broadcom CorporationMultiport switch for cascaded ethernet AV device networkingUS8493959Aug 12, 2010Jul 23, 2013Juniper Networks, Inc.Multiple media access control (MAC) addressesUS8606986 *Jun 4, 2012Dec 10, 2013Apple Inc.Methods and apparatus for bridged data transmission and protocol translation in a high-speed serialized data systemUS9008079Dec 5, 2012Apr 14, 2015Iii Holdings 2, LlcSystem and method for high-performance, low-power data center interconnect fabricUS9054990May 18, 2012Jun 9, 2015Iii Holdings 2, LlcSystem and method for data center security enhancements leveraging server SOCs or server fabricsUS9069929Jun 19, 2012Jun 30, 2015Iii Holdings 2, LlcArbitrating usage of serial port in node card of scalable and modular serversUS9075655 *Sep 21, 2012Jul 7, 2015Iii Holdings 2, LlcSystem and method for high-performance, low-power data center interconnect fabric with broadcast or multicast addressingUS9077654May 18, 2012Jul 7, 2015Iii Holdings 2, LlcSystem and method for data center security enhancements leveraging managed server SOCsUS9092594Jun 19, 2012Jul 28, 2015Iii Holdings 2, LlcNode card management in a modular and large scalable server systemUS9262225Dec 27, 2012Feb 16, 2016Iii Holdings 2, LlcRemote memory access functionality in a cluster of data processing nodesUS9311269Dec 3, 2012Apr 12, 2016Iii Holdings 2, LlcNetwork proxy for high-performance, low-power data center interconnect fabricUS20020152346 *Feb 22, 2002Oct 17, 2002Stone Glen DavidMethod of and apparatus for providing isochronous services over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified hubUS20020156612 *Jan 4, 2002Oct 24, 2002Peter SchulterAddress resolution protocol system and method in a virtual networkUS20030007505 *Jul 2, 2002Jan 9, 2003Takuro NodaInformation processor and method, recording medium and programUS20030039260 *Aug 19, 2002Feb 27, 2003Kenji FujisawaCommunication device, communication method and programUS20030133476 *Jan 22, 2003Jul 17, 2003Sony CorporationMethod of and apparatus for providing reserved bandwidth to ethernet devices over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified hubUS20040103183 *Jun 17, 2003May 27, 2004Tai-Yeon KuLookup service system in JINI-based home network supporting IEEE1394 and TCP/IPUS20050215099 *Apr 26, 2005Sep 29, 2005Sony CorporationElectronic device and information reproduction systemUS20060268766 *May 26, 2005Nov 30, 2006Anand RangarajanMethods and apparatus for resolving address mapping associated with a wireless mesh networkUS20070008981 *Jul 8, 2005Jan 11, 2007Pathan Arnavkumar MCommunication device client update system and methodUS20070226377 *Feb 9, 2006Sep 27, 2007Dell Products L.P.Detecting parameters of a system UART and matching those parameters in a serial-over-LAN (SOL) UARTUS20080144620 *Feb 26, 2008Jun 19, 2008Vinit JainMethods and apparatus for creating addressesUS20090022153 *Sep 30, 2008Jan 22, 2009Vinit JainMethods and apparatus for creating addressesUS20090034518 *Aug 1, 2007Feb 5, 2009Broadcom CorporationMultiport switch for cascaded ethernet av device networkingUS20090182858 *May 29, 2007Jul 16, 2009China Mobile Communications CorporationMethod for assigning address to the intelligent information household appliance and the sub-equipment in the household networkUS20090190598 *Nov 18, 2008Jul 30, 2009Peter Skov ChristensenEthernet address management systemUS20100054243 *Mar 4, 2010Glen David StoneMethod of and apparatus for providing reserved bandwidth to ethernet devices over switched ethernet including a home network wall plate having a combined IEEE 1394 and ethernet modified HUBUS20100064080 *Mar 11, 2010International Business Machines CorporationManaging pci-express max payload size for legacy operating systemsUS20100306571 *Dec 2, 2010Juniper Networks, Inc.Multiple media access control (mac) addressesUS20120236872 *Sep 20, 2012Colin Whitby-StrevensMethods and apparatus for bridged data transmission and protocol translation in a high-speed serialized data systemUS20130022040 *Jan 24, 2013Calxeda, Inc.System and method for high-performance, low-power data center interconnect fabric with broadcast or multicast addressing* Cited by examinerClassifications U.S. Classification370/401, 370/467International ClassificationH04L12/46Cooperative ClassificationH04L12/4633, H04L12/462European ClassificationH04L12/46B7, H04L12/46ELegal EventsDateCodeEventDescriptionJan 26, 2001ASAssignmentOwner name: MICROSOFT CORPORATION, WASHINGTONFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOY, JOSEPH M.;MURCHING, ARVIND;CLEETON, LAWRENCE R.;REEL/FRAME:011524/0656Effective date: 20010111May 20, 2009FPAYFee paymentYear of fee payment: 4Aug 11, 2009CCCertificate of correctionMar 18, 2013FPAYFee paymentYear of fee payment: 8Dec 9, 2014ASAssignmentOwner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTONFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001Effective date: 20141014RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services