U.S. patent application number 11/833854 was filed with the patent office on 2008-11-20 for single device for handling client side and server side operations for a/v bridging and a/v bridging extensions.
Invention is credited to Wael William Diab.
Application Number | 20080285572 11/833854 |
Document ID | / |
Family ID | 40026962 |
Filed Date | 2008-11-20 |
United States Patent
Application |
20080285572 |
Kind Code |
A1 |
Diab; Wael William |
November 20, 2008 |
SINGLE DEVICE FOR HANDLING CLIENT SIDE AND SERVER SIDE OPERATIONS
FOR A/V BRIDGING AND A/V BRIDGING EXTENSIONS
Abstract
Aspects of a single device for handling server side operations
for A/V bridging and A/V bridging extensions may include a single
IC device that is configured to enable encapsulation of generated
digital video data within an encapsulating PDU. The single IC
device may enable determination of a traffic class designation
associated with the encapsulating PDU. The single IC device may
enable transmission of the encapsulating PDU via a network based on
the traffic class designation. Aspects of a single device for
handling client side operations may include a single IC device that
is configured to enable extraction of received digital video that
is encapsulated within an encapsulating PDU. The encapsulating PDU
may be received via a network at a destination device. The single
IC device may enable transmission of the received digital video
data to a multimedia monitor coupled to the destination device via
an interface connector.
Inventors: |
Diab; Wael William; (San
Francisco, CA) |
Correspondence
Address: |
MCANDREWS HELD & MALLOY, LTD
500 WEST MADISON STREET, SUITE 3400
CHICAGO
IL
60661
US
|
Family ID: |
40026962 |
Appl. No.: |
11/833854 |
Filed: |
August 3, 2007 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
60917870 |
May 14, 2007 |
|
|
|
Current U.S.
Class: |
370/401 |
Current CPC
Class: |
H04N 19/176 20141101;
H04N 21/6373 20130101; H04N 5/85 20130101; H04L 12/2805 20130101;
G09G 5/006 20130101; H04N 21/43615 20130101; H04L 2012/2849
20130101; Y02D 30/32 20180101; H04N 21/64322 20130101; H04N 19/61
20141101; H04N 19/172 20141101; H04N 9/8042 20130101; G09G 2370/10
20130101; Y02D 30/00 20180101; H04N 7/106 20130101; H04N 21/43632
20130101; H04L 12/2816 20130101 |
Class at
Publication: |
370/401 |
International
Class: |
H04L 12/28 20060101
H04L012/28 |
Claims
1. A method for communicating data, the method comprising:
configuring a single integrated circuit (IC) device for one or both
of client side operation and server side operation, wherein: said
client side operation enables extraction of received digital video
data encapsulated within an encapsulating protocol data unit (PDU);
and transmission of said extracted received digital video data to a
multimedia monitor via an interface connector; and said server
operations enables encapsulation of generated digital video data
within an encapsulating PDU; and transmission of said encapsulated
PDU based on a traffic class designation associated with said
encapsulating PDU.
2. The method according to claim 1, comprising receiving said
encapsulating protocol data unit (PDU) via a network at a
destination device comprising said single IC device.
3. The method according to claim 2, wherein said multimedia monitor
is coupled to said destination device via said interface
connector.
4. The method according to claim 3, wherein said multimedia monitor
enables rendering of said received digital video data thereon.
5. The method according to claim 1, comprising determining said
traffic class designation associated with said encapsulating
PDU.
6. The method according to claim 1, comprising transmitting said
encapsulating PDU via a network based on said traffic class
designation.
7. The method according to claim 1, wherein said received
encapsulating PDU comprises an Ethernet frame and/or an Internet
Protocol (IP) packet.
8. The method according to claim 1, wherein said transmitted
encapsulating PDU comprises an Ethernet frame and/or an Internet
Protocol (IP) packet.
9. The method according to claim 1, comprising extracting said
received digital video data from said encapsulating PDU based on a
data type.
10. The method according to claim 9, wherein said data type is
determined based on at least one data type identifier.
11. The method according to claim 10, wherein said at least one
data type identifier comprises an EtherType and an
EtherTypeSubType.
12. The method according to claim 1, comprising indicating whether
said transmitted encapsulating PDU encapsulates said generated
digital video data based on at least one data type identifier.
13. The method according to claim 12, wherein said at least one
data type identifier comprises an EtherType and an
EtherTypeSubType.
14. The method according to claim 1, wherein said single IC device
is configured for at least said client operations and/or said
server operations by one or more of: a control signal, an internal
fuse, firmware and/or a determined logic level coupled to a contact
on said single IC device.
15. The method according to claim 14, comprising dynamically
configuring said single IC device based on said control signal.
16. A system for communicating data, the system comprising: a
single integrated circuit (IC) device that enables configuration
for one or both of client side operation and server side operation,
wherein: said client side operation enables extraction of received
digital video data encapsulated within an encapsulating protocol
data unit (PDU); and transmission of said extracted received
digital video data to a multimedia monitor via an interface
connector; and said server operations enables encapsulation of
generated digital video data within an encapsulating PDU; and
transmission of said encapsulated PDU based on a traffic class
designation associated with said encapsulating PDU.
17. The system according to claim 16, wherein said single IC device
enables reception of said encapsulating protocol data unit (PDU)
via a network at a destination device comprising said single IC
device.
18. The system according to claim 17, wherein said multimedia
monitor is coupled to said destination device via said interface
connector.
19. The system according to claim 18, wherein said multimedia
monitor enables rendering of said received digital video data
thereon.
20. The system according to claim 16, wherein said single IC device
enables determination of said traffic class designation associated
with said encapsulating PDU.
21. The system according to claim 16, wherein said single IC device
enables transmission of said encapsulating PDU via a network based
on said traffic class designation.
22. The system according to claim 16, wherein said received
encapsulating PDU comprises an Ethernet frame and/or an Internet
Protocol (IP) packet.
23. The system according to claim 16, wherein said transmitted
encapsulating PDU comprises an Ethernet frame and/or an Internet
Protocol (IP) packet.
24. The system according to claim 16, wherein said single IC device
enables extraction of said received digital video data from said
encapsulating PDU based on a data type.
25. The system according to claim 24, wherein said data type is
determined based on at least one data type identifier.
26. The system according to claim 25, wherein said at least one
data type identifier comprises an EtherType and an
EtherTypeSubType.
27. The system according to claim 16, wherein said single IC device
enables indication of whether said transmitted encapsulating PDU
encapsulates said generated digital video data based on at least
one data type identifier.
28. The system according to claim 27, wherein said at least one
data type identifier comprises an EtherType and an
EtherTypeSubType.
29. The system according to claim 16, wherein said single IC device
is configured for at least said client operations and/or said
server operations by one or more of: a control signal, an internal
fuse, firmware and/or a determined logic level coupled to a contact
on said single IC device.
30. The system according to claim 29, wherein said single IC device
enables dynamic configuration based on said control signal.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY
REFERENCE
[0001] This application makes reference to, claims priority to, and
claims the benefit of U.S. Provisional Application Ser. No.
60/917,870, filed on May 14, 2007, which is hereby incorporated
herein by reference in its entirety.
FIELD OF THE INVENTION
[0002] Certain embodiments of the invention relate to communication
networks. More specifically, certain embodiments of the invention
relate to a method and system comprising a single device for
handling client side and server side operations for A/V bridging
and A/V bridging extensions.
BACKGROUND OF THE INVENTION
[0003] The generation and rendering of high end graphics often
involves the movement of large quantities of data. Frequently the
data is stored in a server, from which it may be accessed by users
at computer workstations (or, more generally, at computing devices)
via a network. Once the data is received at the computing device,
the graphics may be displayed on an attached video monitor. In many
cases the video monitor is physically separate and has been
conventionally attached to the computing device via an analog
interface, such as a video graphics array (VGA) interface, or a
digital interface such as a digital visual interface (DVI). In a
typical configuration, an interface in the computing device is
connected to a compatible interface in the video monitor via an
interstitial connector, such as a cable.
[0004] In an alternative configuration, the computing device may
incorporate a video monitor. An example of this configuration is a
laptop computer in which the video monitor is a component in the
physical computing device unit. Whether the video monitor is
physically incorporated within the computing device or is a
physically separate device, the video monitor may or may not have
touch screen capability.
[0005] Display Port is a digital interface standard, which enables
a computing device to send graphics and video data to a video
monitor, or multimedia display device, via a Display Port
interface. In this regard, the Display Port interface standard may
describe a point-to-point interface, which is capable of
transmitting data from a device connected at one end of a
connecting cable to a device connected at the other end of the
connecting cable. The graphics and/or video data communicated
across the Display Port interface may be sent in mini-packets as
described in applicable standards. The mini-packets may contain
information comprising instructions on how to render the graphics
and/or video data on the video display screen, for example. The
mini-packets may be sent via a plurality of data paths referred to
as "lanes". In an exemplary Display Port interface, there may be
four (4) such lanes.
[0006] In addition to supporting unidirectional data traffic from
the computing device to the computer monitor (or other attached
video display device), the Display Port standard may also enable
the bidirectional transfer of data. For example, the Display Port
standard may allow for the exchange of encryption keys to enable
the transfer of encrypted digital data across the Display Port
interface. This capability may enable protection of digital content
transferred across the Display Port interface.
[0007] Further limitations and disadvantages of conventional and
traditional approaches will become apparent to one of skill in the
art, through comparison of such systems with some aspects of the
present invention as set forth in the remainder of the present
application with reference to the drawings.
BRIEF SUMMARY OF THE INVENTION
[0008] A system and/or method is provided which comprises a single
device for handling client side and server side operations for A/V
bridging and A/V bridging extensions, substantially as shown in
and/or described in connection with at least one of the figures, as
set forth more completely in the claims.
[0009] These and other advantages, aspects and novel features of
the present invention, as well as details of an illustrated
embodiment thereof, will be more fully understood from the
following description and drawings.
BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS
[0010] FIG. 1 is a diagram illustrating an exemplary system for
transfer of Display Port data across a network, in accordance with
an embodiment of the invention.
[0011] FIG. 2 is a diagram illustrating exemplary bridging of
Display Port traffic over Ethernet, in accordance with an
embodiment of the invention.
[0012] FIG. 3 is a diagram illustrating an exemplary system enabled
to transmit and/or receive Display Port and/or Ethernet data
streams, in accordance with an embodiment of the invention.
[0013] FIG. 4A is a block diagram of an exemplary single IC device
configured for use in a server system, in accordance with an
embodiment of the invention.
[0014] FIG. 4B is a block diagram of an exemplary single IC device
configured for use in a server system, in accordance with an
embodiment of the invention.
[0015] FIG. 5A is a block diagram of an exemplary single IC device
configured for use in a client system, in accordance with an
embodiment of the invention.
[0016] FIG. 5B is a block diagram of an exemplary single IC device
configured for use in a client system, in accordance with an
embodiment of the invention.
[0017] FIG. 6 is a flowchart illustrating exemplary steps for a
single IC device configured for use in a server system, in
accordance with an embodiment of the invention.
[0018] FIG. 7 is a flowchart illustrating exemplary steps for a
single IC device configured for use in a client system, in
accordance with an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0019] Certain embodiments of the invention may be found in a
method and system comprising a single device for handling client
side and server side operations for A/V bridging and A/V bridging
extensions. In one exemplary aspect of the invention, a single
integrated circuit (IC) device may be configured to enable the
transmission of Display Port mini-packets across a network. This
exemplary aspect of the invention may be practiced in a server
device, such as a video server. In another exemplary aspect of the
invention, the single IC device may be configured to enable
reception of Display Port mini-packets that were transported across
a network. This exemplary aspect of the invention may be practiced
in a client device, such as a computing device.
[0020] FIG. 1 is a diagram illustrating an exemplary system for
transfer of Display Port data across a network, in accordance with
an embodiment of the invention. Referring to FIG. 1, there is shown
a computing cluster 102, a network 112, a computing device 122 and
a multimedia monitor 124. The computing cluster 102 may comprise a
video server 104, a file server 106, a database server 108 and a
network management server 110.
[0021] The computing cluster 102 may comprise a plurality of
servers, each of which may perform one or more specific tasks, or
execute one or more specific applications. Each server may store
data which may be accessible to users at computing devices 122,
which are attached to the network 112. The servers within the
computer cluster 102 may communicate with each other, and/or with
the network 112 via Ethernet interfaces. The video server 104 may
store computer graphics data in addition to storing video, audio
and/or multimedia programs. The multimedia monitor 124 may enable
the rendering and display of visual images comprising video and/or
graphics, for example.
[0022] The video server 104 may comprise hardware and/or software,
which enables processing of graphics, video, audio and/or
multimedia data. The computer graphics, video, audio and/or
multimedia stored at the video server 104 may be accessible via the
network 112. In this application, video, which may also refer to
digital video (including high definition video), may comprise
uncompressed video, compressed video, encrypted uncompressed video
and/or encrypted compressed video, for example. Audio may comprise
uncompressed audio, compressed audio, encrypted uncompressed audio
and/or encrypted compressed audio. The file server 106 may store
one or more files. The file server 106 may be utilized, for
example, to store files from various users. The database server 108
may store one or more database programs, applications and/or files.
The network management server 110 may store information pertaining
to the configuration and/or availability of various network
communications devices and/or interfaces. The network management
server 110 may utilize a protocol such as the simple network
management protocol (SNMP). The computing device 122 and multimedia
monitor 124 may communicate via Display Port interfaces. The
computing device 122 may communicate with the network 112 via an
Ethernet interface.
[0023] In an exemplary mode of operation, the video server 104 may
encapsulate the video data in one or more Display Port
mini-packets. The video data may be uncompressed. In turn, the
video server 104 may encapsulate the one or more Display Port
mini-packets in one or more Ethernet frames. Alternatively, the
video server 104 may directly encapsulate the digital video data in
one or more Ethernet frames. The format of the Ethernet frames may
be specified in applicable standards documents, such as IEEE 802
standards. The Ethernet frames may contain an address (for example,
in a destination address field within the Ethernet frames), which
indicates that the Ethernet frames are to be transported across the
network 112, and delivered to the computing device 122. The
Ethernet frames may comprise a designation (for example, in an
EtherType field of the Ethernet frames), which indicates that the
Ethernet frames are being utilized to encapsulate Display Port
mini-packets. The Ethernet frames may also comprise a traffic class
identifier, which may enable the network 112 to provide services in
accordance with AV Bridging specifications. These services may
comprise prioritized transport of the Ethernet frames across the
network 112 to enable the time duration for transport across the
network 112 to meet latency targets associated with the specified
traffic class.
[0024] The video server 104 may transport the Ethernet frames via
an Ethernet interface connector 132 to the network 112. The
Ethernet frames may subsequently be transported from the network
112 to the computing device 122 via an Ethernet interface connector
134. An exemplary Ethernet interface connector may be a category 5
cable.
[0025] Upon receipt of the Ethernet frames, the computing device
122 may determine (for example, based on an identifier in the
EtherType field of the received Ethernet frames) that the received
Ethernet frames contain Display Port mini-packets. The computing
device 122 may de-encapsulate the Display Port mini-packets. The
computing device 122 may subsequently send the de-encapsulated
Display Port mini-packets to the multimedia monitor 124 via the
Display Port interface connector 136. The Display Port interface
connector 136 may enable physical connection between the computing
device and the multimedia monitor 124 via a point-to-point
connection. The digital video contained within the Display Port
mini-packets may then be rendered for display at the multimedia
monitor 124.
[0026] In various embodiments of the invention, point-to-point
oriented traffic, which contains no destination identification
information (such as a destination address, for example) may be
encapsulated in Ethernet packets at a centralized server (such as a
video server 104), and transported across a network 112 (such as a
LAN, for example). The point-to-point oriented traffic may comprise
Display Port mini-packets, or digital video (including high
definition video) data generated by an application program, for
example. The encapsulated traffic may be de-encapsulated at a
network destination device (such as the computing device 122) and
delivered to a destination multimedia device (such as the
multimedia monitor 124). Thus, in various embodiments of the
invention, from the perspective of the application(s), which enable
the generation of the point-to-point oriented traffic, the
centralized server (such as the video server 104) may transport the
point-to-point oriented traffic across a network 112 to the
destination multimedia device 124 as though the destination
multimedia device 124 were directly attached to the centralized
server via an interface, which is suitable for transport of the
point-to-point oriented traffic. In an exemplary embodiment of the
invention, the interface may be a Display Port interface, when the
Ethernet frames encapsulate Display Port mini-packets. In another
exemplary embodiment of the invention, the interface may be a DVI,
when the Ethernet frames encapsulate digital video data suitable
for transport via a DVI.
[0027] In various embodiments of the invention, the tasks performed
by the computing device 122 may comprise reception of Ethernet
frames via the Ethernet interface connector 134, determination that
the Ethernet frames may contain encapsulated Display Port
mini-packets, de-encapsulation of the Display Port mini-packets,
and transfer of the de-capsulated Display Port mini-packets to the
multimedia monitor 124 via the Display Port interface connector
136. In this regard, the video server 104 may generate instructions
for rendering the video data on the multimedia monitor 124 within
the Display Port mini-packets instead of requiring that this task
be performed within the computing device 122. Thus, various
embodiments of the invention may enable the computing device 122 to
be a "thin client" device, which may not require high performance
hardware and/or software capabilities to enable the generation of
Display Port mini-packets for high performance video and/or
graphics applications. This in turn may enable the rendering of
high performance video and/or graphics on multimedia monitors 124
which are attached to low cost computing devices 122. Prior to the
reception of the Ethernet frames, the computing device 122 may send
a request to the video server 104. The video server 104 may respond
to the request by sending the video data to the computing device
122 via the network 112.
[0028] FIG. 2 is a diagram illustrating exemplary bridging of
Display Port traffic over Ethernet, in accordance with an
embodiment of the invention. Referring to FIG. 2, there is shown
the video server 104 (FIG. 1), the network 112, the computing
device 122 and the multimedia monitor 124. The video server 104 may
comprise digital video 202 and a plurality of protocol layers. The
protocol layers may comprise a Display Port mini-packet layer 204,
an Ethernet payload layer 212, a Display Port light physical
(PHY-Lite) layer 206, an Ethernet medium access control (MAC) layer
214 and an Ethernet physical (PHY) layer 216. The network 112 may
comprise one or more switching devices which comprise at least one
Ethernet PHY layer 222 and 226 and at least one Ethernet MAC layer
224. The computing device 122 may comprise a plurality of protocol
layers including an Ethernet payload layer 235, a Display Port
Mini-Packet layer 236, an Ethernet MAC layer 234, an Ethernet PHY
layer 232 and a Display Port PHY layer 244. The multimedia monitor
124 may comprise protocol layers related to the digital video 202
and to a plurality of protocol layers including a Display Port PHY
layer 252 and a Display Port mini-packet layer 254. The Display
Port PHY layer 244 may comprise suitable logic, circuitry and/or
code that may enable generation of electrical and/or optical
signals for transport via the Display Port interface connector 136.
The Display Port PHY-Lite layer 206 may comprise logic, circuitry
and/or code, which may enable generation of electrical and/or
optical signals suitable for transport within the video server 104.
However, the generated signals may not be suitable for transport of
signals via an external interface.
[0029] In various embodiments of the invention, the digital video
202 may be generated by an application, which may be executing
within the video server 104. The digital video 202 may then be
encapsulated in Display Port mini-packets in the Display Port
mini-packet layer 204. The Display Port mini-packets may also
contain instructions to enable rendering of the digital video 202
on the multimedia monitor 124. A Graphics Processing Unit (GPU) may
generate the Display Port mini-packets. The Display Port PHY-Lite
layer 206 may enable reception of the Display Port mini-packets and
generation of the line coded bits at a LAN subsystem within the
video server 104. The line coded bits may be decoded and
reassembled to form Ethernet payload(s). The Ethernet payload layer
212 may subsequently send the Ethernet payload(s) to the Ethernet
MAC layer 214. The Ethernet MAC layer 214 may encapsulate the
received Ethernet payload(s) in one or more Ethernet frames. The
Ethernet frames may comprise information, which indicates that the
Ethernet frames contain one or more encapsulated Display Port
mini-packets and/or traffic class identification, for example. The
Ethernet MAC layer 214 may send the Ethernet frames to the Ethernet
PHY layer 216, which may enable transport of the Ethernet frames to
the network 112 via the Ethernet interface connector 132. The
traffic class identification may enable the utilization of AV
Bridging services for the transport of the Ethernet frames within
the network 112.
[0030] Within the network 112, the Ethernet PHY layer 222 within a
switching device (such as an Ethernet switch) may receive the
Ethernet frames via the Ethernet interface connector 132. One or
more of the switching devices within the network 112 may support AV
Bridging services. The Ethernet MAC layer 224 may enable the
switching device to determine (based on the destination address
field within the Ethernet frames, for example) that the computing
device 122 is the destination device for receipt of the Ethernet
frames. The Ethernet MAC layer 224 may send the Ethernet frames to
the Ethernet PHY layer 226, which may enable transport of the
Ethernet frames to the computing device 122 via the Ethernet
interface connector 134.
[0031] Within the computing device 122, the Ethernet PHY layer 232
may receive the Ethernet frames via the Ethernet interface
connector 134, which may be subsequently sent to the Ethernet MAC
and MAC services layer 234. The Ethernet MAC and MAC services layer
234 may determine that the received Ethernet frames contain
encapsulated Display Port mini-packets. The Ethernet MAC and MAC
services layer 234 may de-encapsulate the Ethernet payloads from
the received Ethernet frames. The Ethernet payload layer 235 may
receive the Ethernet payload and generate one or more Display Port
mini-packets. The Display Port mini-packets may then be sent to the
Display Port mini-packet layer 236. The Display Port mini-packet
layer 236 may determine that the received Display Port mini-packets
are to be sent to the multimedia monitor 124. The Display Port
mini-packet layer may send the Display Port mini-packets to the
Display Port PHY layer 244, which may subsequently transmit the
Display Port mini-packets to the multimedia monitor 124 via the
Display Port interface connector 136.
[0032] Within the multimedia monitor 124, the Display Port PHY
layer 252 may receive the Display Port mini-packets via the Display
Port interface connector 136. The Display Port PHY layer 252 may
send the received Display Port mini-packets to the Display Port
mini-packet layer 254. The Display Port mini-packet layer 254 may
extract the digital video 202 from the received Display Port
mini-packets. The Display Port mini-packet layer 254 may also
extract instructions contained within the Display Port
mini-packets, which enable rendering of the digital video 202 at
the multimedia monitor 124. The multimedia monitor 124 may then
utilize the extracted instructions to display the digital video
202.
[0033] As shown in FIG. 2, in various embodiments of the invention,
the video server 104 and the multimedia monitor 124 may process
digital video, while the computing device 122 may not or may be
limited in performance. Thus, in various embodiments of the
invention, the computing device 122 may be a low cost appliance,
which may not be required to comprise costly hardware and/or
software to enable processing and/or rendering of high performance
multimedia, video and/or graphics.
[0034] Various embodiments of the invention may not be limited to
the transfer of Display Port mini-packets across a LAN. For
example, in various embodiments of the invention, the Display Port
mini-packets may be encapsulated within any of a variety of
protocol data units (PDU) associated with higher layer protocols,
for example a network layer protocol. An exemplary network layer
protocol may be defined as set forth in a relevant protocol
reference model (PRM), for example as specified by a standards
organization such as the International Organization for
Standardization (ISO).
[0035] In an exemplary embodiment of the invention, which utilizes
a network layer protocol, Display Port mini-packets may be
encapsulated within IP (Internet Protocol) packets. The IP packets
may subsequently be encapsulated within Ethernet frames.
Encapsulation of the Display Port mini-packets within IP packets
may enable the transport of the encapsulated Display Port
mini-packets across a network, such as the Internet. The transport
of encapsulated Display Port mini-packets within IP packets may
also utilize protocols such as the Reservation Protocol (RSVP) as
defined by the Internet Engineering Task Force (IEFT), for example.
The services provided by RSVP may be coordinated with AV Bridging
services to support isochronous and/or real-time transmission of IP
packets, which contain encapsulated Display Port mini-packets. In
this regard, quality of service (QoS) aspects of RSVP (or similar
higher layer protocol) may be mapped to the physical layer via AV
Bridging to enable the transport of the encapsulated Display Port
mini-packets across a network based on suitable bandwidth and
latency targets.
[0036] Within the context of the ISO PRM, Ethernet functions
related to medium access control (MAC) may be associated with the
data link layer (DLL), while Ethernet functions related to line
coding of data and generation of signals for transmission of bits
via a physical medium may be associated with the physical layer
(PHY). IP related functions may be associated with the network
layer. At least a portion of a PDU for a given protocol layer may
be encapsulated as a service data unit (SDU) within the PDU for the
next lower protocol layer.
[0037] FIG. 3 is a diagram illustrating an exemplary system enabled
to transmit and/or receive Display Port and/or Ethernet data
streams, in accordance with an embodiment of the invention.
Referring to FIG. 3 the system 300 may comprise a CPU 302, a memory
controller hub (MCH) 304, a graphics processing unit (GPU) 306, a
memory block 308, an input/output controller hub (ICH) 310, a low
speed peripheral block 312, a LAN subsystem 314, a DP connector
316, an Ethernet connector 318a, an Ethernet connector 318b and
memory 320.
[0038] The CPU 302 may comprise suitable logic, circuitry, and/or
code that may enable processing data and/or controlling operations
of the system 300. In this regard, the CPU 302 may be enabled to
provide control signals to the various other blocks comprising the
system 300. The CPU 302 may also enable execution of applications
programs and/or code. The applications programs and/or code may
enable generation of digital video and/or graphics. The CPU 302 may
also enable the retrieval of stored digital video and/or graphics.
The CPU 302 may be accessed via the MCH 304.
[0039] The MCH 304 may comprise suitable logic, circuitry, and/or
code that may enable the storage and/or retrieval of data at high
data transfer rates. For example, the MCH 304 may enable retrieval
and/or storage of digital video and/or graphics data for high
performance applications, such as high definition video, high
resolution 3-D graphics, &c. In various embodiments of the
invention, the MCH 304 may be referred to as a northbridge
(NB).
[0040] The GPU 306 may comprise suitable logic, circuitry, and/or
code for generating, rendering, and/or manipulating graphics data.
The GPU 306 may output digital video and/or graphics. The GPU 306
may also output encrypted digital video and/or graphics for
applications that utilize digital content protection, for example.
The GPU 306 may encapsulate the digital video and/or graphics in
Display Port mini-packets. The Display Port mini-packets generated
by the GPU 306 may also comprise instructions, which enable
rendering of the digital video and/or graphics for display on a
multimedia monitor 124 (FIG. 1). The GPU 306 may also output
protocol data units associated with other high definition (HD)
protocols. The GPU 306 may comprise Display Port PHY layer
functionality, which enables the GPU 306 to send and/or receive
Display Port mini-packets via the Display Port connector 316.
[0041] The memory 308 may comprise suitable logic, circuitry,
and/or code that may enable the storage and/or retrieval of data.
For example, the memory 308 may enable the storage and/or retrieval
of video and/or graphics data. The memory 308 may also enable the
storage and/or retrieval of encryption keys, which may be utilized
for encryption and/or decryption of data. The memory 308 may
additionally store data, for example, configuration data and/or
state variables utilized in controlling/configuring the various
blocks of the system 300. The memory 308 may also enable the
storage of code, which enables the execution of multimedia
applications, for example. The memory 308 may utilize various
technologies, such as dynamic random access memory (DRAM), which
enable data to be stored and/or retrieved at sufficiently high data
rates to enable high performance multimedia applications, for
example.
[0042] The ICH 310 may comprise suitable logic, circuitry, and/or
code that may enable the storage and/or retrieval of data from
peripheral devices such as hard disk drives. The ICH 310 may also
enable the retrieval of input signals and/or interrupt signals from
peripheral devices, such as keyboard device and mouse devices,
and/or other peripheral devices including various peripheral
component interconnect (PCI) devices, for example. In various
embodiments of the invention, the ICH 310 may be referred to as a
southbridge (SB).
[0043] The LAN subsystem 314 may comprise suitable logic,
circuitry, and/or code to enable the transmission and/or reception
of Ethernet frames. The LAN subsystem 314 may comprise PHY layer
functions and MAC layer functions. The LAN subsystem 314 may enable
transmission and/or reception of Ethernet frames at various
transfer rates, such as 10 Mbps, 100 Mbps, 1,000 Mbps (or 1 Gbps)
and/or 10 Gbps, or other rates (for example, higher rates). The LAN
subsystem 314 may also enable transmission and/or reception of
Ethernet frames via wireless LANs (WLAN).
[0044] The PHY layer functions may enable transmission of Ethernet
frames via a communication medium. The PHY layer functions may also
enable reception of Ethernet frames via the communication medium.
The PHY layer functions may generate signals for transmission that
are suitable for the physical medium being utilized for
transmitting the signals. For example, for an optical communication
medium, the PHY layer may generate optical signals, such as light
pulses, or for a wired communication medium, the PHY layer may
generate electromagnetic signals.
[0045] The MAC layer functions may enable orderly communication
between systems that are communicatively coupled via a shared
communication medium. The MAC layer may comprise one or more
coordination functions (CF) that enable a system to determine when
it may attempt to access the shared communication medium. For
example, in a wired communication medium, for example Ethernet, a
CF may utilize a carrier sense multiple access with collision
detection (CSMA/CD) algorithm. The MAC layer functions may
implement mechanisms for scanning the communication medium to
determine when it is available for transmission of signals. The MAC
layer functions may comprise back off timer mechanisms, which may
be utilized by a system to determine how often to attempt to access
a communication medium, which is currently determined to be
unavailable.
[0046] The MAC layer functions may also enable AV Bridging
capabilities. In this regard, the MAC layer functions may determine
a traffic class which is associated with transmitted Ethernet
frames. Based on the determined traffic class, the MAC layer
functions may perform traffic shaping by determining a time instant
at which an Ethernet frame may be sent to the network via the
Ethernet interface. That time instant may be determined based on a
time instant at which one or more preceding Ethernet frames were
also transmitted via the Ethernet interface. The time instant may
also be determined based on stored "credits", which may indicate a
quantity of octets of Ethernet frame data that may be transmitted
at "line rate" before transmission of subsequent Ethernet frames is
suspended pending the accumulation of additional credits.
[0047] The MAC layer functions, which support AV Bridging, may also
enable the end-to-end transport of Ethernet frames based on
specified latency targets by initiating admission control
procedures. The latency targets, which may specify a maximum time
duration for the transport of Ethernet frame across the network,
may be determined based on a specified traffic class. A destination
Ethernet device may initiate admission control procedures by
initiating a registration request across the network to the source
Ethernet device. A successful registration may enable the network
to reserve resources for the transport of Ethernet frames between
the source Ethernet device and the destination Ethernet device, in
accordance with the specified latency targets.
[0048] The Ethernet MAC layer functions may also enable an exchange
of timing synchronization information between communicating
Ethernet devices. Individual Ethernet MAC layer functions
associated with each of a plurality of Ethernet devices within a
LAN may exchange timing synchronization with the Ethernet MAC layer
function associated with a specified Ethernet device associated
with the LAN, wherein the specified Ethernet device may provide
system timing for the plurality of Ethernet devices associated with
the LAN. The traffic shaping and/or timing synchronization
capabilities may enable AV Bridging services to support isochronous
and/or real time services, such as streaming media services.
[0049] In various embodiments of the invention, the MAC layer
functions within the LAN subsystem 314 may enable the reception of
Display Port mini-packets and encapsulation of the received Display
Port mini-packets within Ethernet frames. The Ethernet frames may
utilize AV Bridging services when being transmitted via the network
112. The MAC layer functions within the LAN subsystem 314 may also
enable the reception of Ethernet frames and the de-encapsulation of
Display Port mini-packets from Ethernet frames, which are
determined to contain encapsulated Display Port mini-packets.
[0050] In various embodiments of the invention, the MAC layer
functions within the LAN subsystem 314 may enable the encapsulation
of digital video 202 within Display Port mini-packets and
encapsulation of Display Port mini-packets within Ethernet frames.
The Ethernet frames may utilize AV Bridging services when being
transmitted via the network 112. In an exemplary embodiment of the
invention, the LAN subsystem 314 may be configured to enable this
mode of operation in a single IC device by coupling a contact point
in the IC package, within which is contained the LAN subsystem 314,
to a determined logic level. For example, when the contact point is
coupled to a logic level HI, the LAN subsystem 314 may be
configured to enable the encapsulation of digital video 202 within
Display Port mini-packets, encapsulation of the Display Port
mini-packets within Ethernet frames, and transmission of the
Ethernet frames via the network 112. A LAN subsystem 314 utilized
within a video server 104 may be configured for this mode of
operation, for example.
[0051] In another exemplary embodiment of the invention, the LAN
subsystem 314 may be configured to enable this mode of operation in
a single IC device based on code, such as firmware and/or data
stored within the memory 320. In another exemplary embodiment of
the invention, the LAN subsystem 314 may be configured to enable
this mode of operation in a single IC device based on a control
signal, Config_Cntl, received from the CPU 302. For example, when
the control signal presents a logic level, Config_Cntl=HI, the LAN
subsystem 314 may be configured to enable the encapsulation of
digital video within Display Port mini-packets, encapsulation of
the Display Port mini-packets within Ethernet frames, and
transmission of the Ethernet frames via the network 112.
[0052] In another exemplary embodiment of the invention, the LAN
subsystem 314 may be configured to enable this mode of operation in
a single IC device based on an internal fuse. The fuse may be
configured during manufacture of the single IC device. For example,
when the fuse is configured in an open state, the fuse may disable
an electrical continuity path within the single IC. When the fuse
in configured in the open state, for example, the LAN subsystem 314
may be configured to enable the encapsulation of digital video
within Display Port mini-packets, encapsulation of the Display Port
mini-packets within Ethernet frames, and transmission of the
Ethernet frames via the network 112.
[0053] The MAC layer functions within the LAN subsystem 314 may
also enable the reception of Ethernet frames and the
de-encapsulation of Display Port mini-packets from Ethernet frames,
which are determined to contain encapsulated Display Port
mini-packets. In an exemplary embodiment of the invention, the LAN
subsystem 314 may be configured to enable this mode of operation in
a single IC device by coupling a contact point in the IC package,
within which is contained the LAN subsystem 314, to a determined
logic level. For example, when the contact point is coupled to a
logic level LO, the LAN subsystem 314 may be configured to enable
the reception of Ethernet frames, de-encapsulation of the Display
Port mini-packets contained within the received Ethernet frames,
and transmission of the Display Port mini-packets to a multimedia
monitor 124. A LAN subsystem 314 utilized within a computing device
122 may be configured for this mode of operation, for example.
[0054] In another exemplary embodiment of the invention, the LAN
subsystem 314 may be configured to enable this mode of operation in
a single IC device based on code, such as firmware and/or data
stored within the memory 320. In yet another exemplary embodiment
of the invention, the LAN subsystem 314 may be configured to enable
this mode of operation in a single IC device based on a control
signal, Config_Cntl, received from the CPU 302. For example, when
the control signal presents a logic level, Config_Cntl=LO, the LAN
subsystem 314 may be configured to enable the reception of Ethernet
frames, de-encapsulation of the Display Port mini-packets contained
within the received Ethernet frames, and transmission of the
Display Port mini-packets to a multimedia monitor 124.
[0055] In another exemplary embodiment of the invention, the LAN
subsystem 314 may be configured to enable this mode of operation in
a single IC device based on an internal fuse. The fuse may be
configured during manufacture of the single IC device. For example,
when the fuse is configured in a short state, the fuse may enable
electrical continuity path within the single IC. When the fuse in
configured in the short state, for example, the LAN subsystem 314
may be configured to enable the reception of Ethernet frames,
de-encapsulation of the Display Port mini-packets contained within
the received Ethernet frames, and transmission of the Display Port
mini-packets to a multimedia monitor 124.
[0056] In various embodiments of the invention, the LAN subsystem
314 may comprise a single IC die, a plurality of IC die, a single
IC or a plurality of ICs, which operate as a single device with a
unified interface.
[0057] The Display Port connector 316 may enable physical
connection of a Display Port interface connector 136 to the system
300. The physical connection may comprise at least conductors for
each of the 4 lanes in the Display Port interface and for an
auxiliary (AUX) channel. The 4 lanes may enable the transmission or
reception of Display Port mini-packets, while the AUX channel may
enable transmission and reception of control signals, input from
peripheral devices, such as keyboards and/or mouse device, and for
the exchange of encryption keys.
[0058] The Ethernet connector 318a may enable physical connection
of an Ethernet interface connector 132 to the system 300. The
Ethernet connector 318a may enable physical connection via an 8P8C
connector and/or via in RJ45 connector, for example. The Ethernet
connector 318b may be substantially similar to the Ethernet
connector 318a.
[0059] Various embodiments of the invention may enable rendering of
digital video 202 and/or graphics on a multimedia monitor 124,
which has a direct physical connection to the system 300 via a
Display Port interface connector 136 without requiring that the
system 300 comprise digital video and/or graphics processing
capabilities. In an exemplary embodiment of the invention, the
system 300 may comprise a computing device 122. In operation, the
system 300 may receive Ethernet frames via the Ethernet connector
318a. The LAN subsystem 314 within the computing device 122 may be
configured to receive the Ethernet frames and determine that the
received Ethernet frames contain encapsulated Display Port
mini-packets. The LAN subsystem 314 may de-encapsulate the Display
Port mini-packets. The LAN subsystem may utilize Display Port PHY
layer 244 functionality to transmit the de-encapsulated Display
Port mini-packets to a multimedia monitor 124 (FIG. 1) via the
Display Port connector 316. The multimedia monitor 124 may render
digital video 202 contained within the Display Port mini-packets
for visual display.
[0060] The system 300 may utilize the AUX channel to transmit data
signals. In an exemplary embodiment of the invention, a computing
device 122 may send station identification information to the video
server 104 via the AUX channel. The ability to send station
identification information, for example, may enable the computing
device 122 to be utilized in universal plug and play (UPnP)
networks. The CPU 302 may generate the station identification
information, which may be sent to the GPU 306 via the MCH 304. The
GPU 306 may send the station identification information via the AUX
channel.
[0061] Various embodiments of the invention may also enable the
transmission of conventional Ethernet frames. The ICH 310 may
receive signals generated in response to input from a keyboard
device and/or from a mouse device, for example. The ICH 310 may
receive the input from the keyboard device and/or mouse device via
one or more PCI interfaces. The ICH 310 may convert the signals
into input data. The ICH 310 may send the input data to the LAN
subsystem 314. The LAN subsystem 314 may encapsulate the input data
in one or more Ethernet frames. The Ethernet frames may contain a
designation within the EtherType field, which indicates that the
Ethernet frame may not comprise one or more encapsulated Display
Port mini-packets. In this regard, the EtherType designation for
Ethernet frames, which comprise one or more encapsulated Display
Port mini-packets, may be distinguished from the EtherType
designation for Ethernet frames, which do not comprise one or more
Display Port mini-packets. The Ethernet frames may be transmitted
via the Ethernet connector 318a.
[0062] Various embodiments of the invention may utilize a plurality
of Ethernet connectors for the reception and/or transmission of
Ethernet frames from one or more networks. In an exemplary
embodiment of the invention, Ethernet frames, which encapsulate
Display Port mini-packets, or which encapsulate digital video data,
may be transmitted/received via the Ethernet connector 318a, while
conventional Ethernet frames may be transmitted/received via the
Ethernet connector 318b. In various embodiments of the invention,
the Ethernet connector 318a may enable transmission and/or
reception of Ethernet frames to/from a first network while the
Ethernet connector 318b may enable transmission and/or reception of
Ethernet frames to/from a second network.
[0063] In various embodiments of the invention, Ethernet frames,
which encapsulate Display Port mini-packets, or which encapsulate
digital video data, may be transmitted/received via either Ethernet
connector 318a and/or 318b. Conventional Ethernet frames may be
transmitted/received via either Ethernet connector 318a and/or
318b. In various embodiments of the invention, the LAN subsystem
may enable the transmission and/or reception of Ethernet frames via
a single Ethernet connector 318a or 318b, or via a plurality of
Ethernet connectors comprising at least Ethernet connectors 318a
and 318b.
[0064] In another exemplary embodiment of the invention, the system
may comprise a video server 104. In operation, the CPU 302 may
enable generation of digital video 202. The CPU 302 may also enable
the retrieval of digital video 202 from memory 308. The MCH 304 may
enable the high speed transfer of digital video 202 from the CPU
302 and/or from the memory 308 to the GPU 306. The GPU 306 may
process the digital video to, for example, incorporate graphics.
The GPU 306 may also generate instructions, which enable the
rendering of the processed digital video on a multimedia monitor
124. The GPU 306 may generate one or more Display Port
mini-packets, each of which may comprise at least a portion of the
generated rendering instructions and/or processed digital
video.
[0065] The GPU 306 may output the Display Port mini-packets to the
LAN subsystem 314. The LAN subsystem 314 may be configured to
encapsulate the Display Port mini-packets in Ethernet frames. The
LAN subsystem 314 may utilize Ethernet MAC layer 214 functionality
to enable the utilization of AV Bridging capabilities for the
transport of the Ethernet frames via the network 112. The LAN
subsystem 314 may utilize Ethernet PHY layer 216 functionality to
enable the transmission of the Ethernet frames via the Ethernet
connector 318a.
[0066] FIG. 4A is a block diagram of an exemplary single IC device
configured for use in a server system, in accordance with an
embodiment of the invention. FIG. 4A shows an exemplary embodiment
of the LAN subsystem 314, which is configured for use in a server
system. Referring to FIG. 4A, there is shown a single IC device
400, a GPU 306 (from FIG. 3), an ICH (from FIG. 3), a Display Port
connector 316, Ethernet connectors 318a and 318b and 10 GBASE-T PHY
layer blocks 436a and 436b. The single IC device 400 may comprise a
MAC client 422a, MAC client 422b, time stamp shims 424a and 424b,
10G Ethernet MAC block 426, Display Port to Ethernet block 432, PCI
to Ethernet block 434 and a Display Port PHY-Lite layer 206 (from
FIG. 2).
[0067] The GPU 306 may encapsulate data in one or more Display Port
mini-packets. The Display Port mini-packets may comprise an
identifier, which indicates whether the Display Port mini-packets
contain video data or other types of data. The GPU 306 may transmit
Display Port mini-packets, which contain video data, via the Video
Main Lanes [3:0]. The GPU 306 may transmit AUX channel data, via
the AUX Channel.
[0068] The single IC device 400 may comprise suitable logic,
circuitry and/or code that may be configured to enable
encapsulation of digital video within Display Port mini-packets,
encapsulation of the Display Port mini-packets within one or more
Ethernet frames and transmission of the Ethernet frames via the
Ethernet connector 318. The Display Port PHY-Lite layer 206 may
receive Display Port mini-packets via at least the Video Main Lanes
[3:0] and may receive AUX channel data via at least the AUX
Channel. The Display Port PHY-Lite layer 206 may generate binary
bits.
[0069] In various embodiments of the invention, the Display Port
PHY-Lite layer 206 may comprise a transmitter (TX) block, a
receiver (RX) block, a transceiver (TX/RX) block and a selector
switch. The TX block receives input signals from the Video Main
Lanes [3:0] interface. The TX/RX block receives input signals from
the AUX Channel interface and outputs the received signals to the
interface 440. The TX/RX block also receives input signals from the
interface 440 and outputs the received signals to the AUX Channel
interface.
[0070] The Display Port PHY-Lite layer 206 may receive an input
configuration control signal, Config_Cntl, which configures the
Display Port PHY-Lite layer 206 for use in a server system. When
the Display Port PHY-Lite layer 206 is configured for use in a
server system, the selector switch couples the output of the TX
block to the interface 440. In this aspect of the invention, the TX
block may receive input signals from the Video Main Lanes [3:0]
interface and outputs the received signals to the interface 440 via
the selector switch. When the Display Port PHY-Lite layer 206 is
configured for use in a server system, the RX block may be
inactive. When the TX/RX block receives and/or transmits AUX
channel data, the selector switch may be configured such that the
TX block and RX block are inactive. When the TX/RX block receives
and/or transmits AUX channel data, the selector switch may be
configured such that the TX block and RX block are inactive.
[0071] The Display Port to Ethernet block 432 may enable reception
of bits from a Display Port PHY-Lite layer 206. The Display Port to
Ethernet block 432 may enable assembly of the bits to form one or
more Ethernet payloads. An Ethernet payload may comprise one or
more bits from one or more Display Port mini-packets, MP. In an
exemplary embodiment of the invention, the Ethernet payload may
comprise a plurality of concatenated Display Port mini-packets. In
another exemplary embodiment of the invention, the Ethernet payload
may comprise a concatenation of payloads from a plurality of
Display Port mini-packets with a single Display Port mini-packet
header appended to the concatenated payloads.
[0072] The MAC client 422a may receive Ethernet payloads from the
Display Port to Ethernet block 432 and encapsulate the Ethernet
payloads in one or more Ethernet frames, EF.sub.1. The Ethernet
frames, EF.sub.1, may comprise EtherType=DP (where DP may represent
a numerical value), which indicates that the Ethernet frames
EF.sub.1 contain encapsulated Display Port mini-packets. In
addition, the Ethernet frames, EF.sub.1, may also comprise a field
EtherTypeSubType=VID (where VID may represent a numerical value),
which indicates that the Display Port mini-packets may contain
video data. The Ethernet frames, EF.sub.1, may comprise a field
EtherTypeSubType=AUX (where AUX may represent a numerical value),
which indicates that the Ethernet payloads contain AUX channel
data. The subtype may also indicate one or a plurality of
multimedia monitors, attached to a computing device, which is to
receive the Display Port mini-packets.
[0073] The ICH 310 may enable reception of input signals from
peripheral devices and the generation of bits from the received
input signals. The generated bits may be transmitted via a PCI
interface.
[0074] The PCI to Ethernet block 434 may enable reception of bits
from a PCI interface. The bits may be generated based on input
received from a peripheral device. The PCI to Ethernet block 434
may enable assembly of the bits to construct one or more Ethernet
payloads EP.
[0075] The MAC client 422b may receive Ethernet payloads, EP, and
encapsulate the Ethernet payloads in one or more Ethernet frames,
EF.sub.2. The Ethernet frames EF.sub.2 may comprise
EtherType.noteq.DP, which indicates that the Ethernet frames
EF.sub.2 may not contain Display Port mini-packets.
[0076] The time stamp shims 424a and 424b may receive Ethernet
frames EF.sub.1 and EF.sub.2 from the corresponding MAC clients
422a and 422b. The time stamp shims 424a and 424b may append time
synchronization information, such as a time stamp, to the Ethernet
frames EF.sub.1 and EF.sub.2 based on an EtherType designation, for
example. The time stamp shims 424a and 424b may append a time stamp
when the EtherType field indicates that the Ethernet frame is to
utilize AV Bridging capabilities for transport across a network
112, for example.
[0077] The 10G Ethernet MAC block 426 may enable the transmission
of the Ethernet frames EF.sub.1 and EF.sub.2 via the network 112.
The 10G Ethernet MAC block 426 may enable generation of header
information within the Ethernet frames, which enable the
utilization of AV Bridging services within the network 112 for
transport of the Ethernet frames. The 10G Ethernet MAC block 426
may also enable traffic shaping of transmitted Ethernet frames by
determining time instants at which the Ethernet frames EF.sub.1 and
EF.sub.2 may be transmitted to the network 112. The 10G Ethernet
MAC block 426 may also enable generation of header information
within the Ethernet frames, which utilize conventional Ethernet
services within the network 112. The conventional Ethernet services
may not utilize traffic shaping and/or AV Bridging services, for
example. In various embodiments of the invention, Ethernet frames,
which utilize conventional Ethernet services, may be transported
via a network, which is separate from the network 112. The 10G
Ethernet MAC block 426 may enable determination of a network, which
is to be utilized for the transport of Ethernet frames EF.sub.1
and/or EF.sub.2.
[0078] The 10GBASE-T PHY layer 436a may enable the reception of
bits from Ethernet frames. The 10 GBASE-T PHY layer 436a may line
encode the received bits to enable transmission via an Ethernet
connector 318a. The 10 GBASE-T PHY layer 436b may be substantially
similar to the 10 GBASE-T PHY layer 436a. The 10 GBASE-T PHY layer
436b may line encode the received bits to enable transmission via
an Ethernet connector 318b. 10G is an exemplary Ethernet bit rate;
various embodiments of the invention may also be practiced at other
bit rates suitable for carrying HD traffic.
[0079] The 10GBASE-T PHY layer 436a may also receive line coded
bits via the Ethernet connector 318a. The 10GBASE-T PHY layer 436b
may also receive line coded bits via the Ethernet connector 318b.
The 10GBASE-T PHY layer 436a or 436b may decode the received line
coded bits, which may be sent to the 10G Ethernet MAC block 426.
The 10G Ethernet MAC block 426 may assemble the received decoded
bits to construct one or more Ethernet frames EFR. The 10G Ethernet
MAC block 426 may determine whether the constructed Ethernet frames
EFR contain one or more Display Port mini-packets, MPR, or Ethernet
payloads, EPR, which may not contain Display Port mini-packets. The
10G Ethernet MAC block 426 may make the determination based on a
designation within EtherType field within the received Ethernet
frames EFR. The 10G Ethernet MAC block 426 may send the Ethernet
frames EFR to the time stamp shim 424a or 424b.
[0080] The time stamp shim 424a may send Ethernet frames, EFR,
which contain encapsulated Display Port mini-packets, to the MAC
client 422a. Additionally, the MAC client 422a may determine
whether the Ethernet frames contain Display Port mini-packets or
AUX Channel data based on an EtherTypeSubType field within the
Ethernet frames. At a video server 104, received Ethernet frames
may contain AUX channel data. The MAC client 422a may
de-encapsulate the AUX channel data from the Ethernet frames EFR.
The MAC client 422a may send the AUX channel data to the Display
Port to Ethernet block 432. The Display Port to Ethernet block 432
may convert the AUX channel data to bits, which may be sent to the
Display Port PHY-Lite layer 206. The Display Port PHY-Lite layer
206 may send the AUX channel data to the GPU 306 via the AUX
Channel. The GPU 306 may transfer the AUX channel data to the MCH
304. The MCH 304 may in turn transfer the AUX channel data to the
CPU 302, which may process the data. The AUX channel data may be
sent to the multimedia monitor 124 via the AUX Channel.
[0081] The time stamp shim 424b may send Ethernet frames, EFR,
which do not contain encapsulated Display Port mini-packets to the
MAC client 422b. The MAC client 422b may de-encapsulate the
Ethernet payloads, EPR, from the received Ethernet frames EFR. The
MAC client 422b may send the Ethernet payloads EPR to the PCI to
Ethernet block 434. The PCI to Ethernet block 434 may convert the
Ethernet payloads EPR to signals, which may be sent to the ICH 310.
The ICH 310 may convert the signals to bits, which may be sent to
the CPU 302 via the MCH 304. The CPU 302 may process the data.
[0082] FIG. 4B is a block diagram of an exemplary single IC device
configured for use in a server system, in accordance with an
embodiment of the invention. FIG. 4B shows an exemplary embodiment
of the LAN subsystem 314, which is configured for use in a server
system. FIG. 4B differs from FIG. 4A in that the exemplary single
IC device shown in FIG. 4B incorporates the 10GBASE-T PHY layer
blocks 436a and 436b from FIG. 4A. Referring to FIG. 4B, there is
shown a single IC device 450, a GPU 306 (from FIG. 3), an ICH (from
FIG. 3), a Display Port connector 316 and Ethernet connectors 318a
and 318b. The single IC device 450 may comprise a MAC client 422a,
MAC client 422b, time stamp shims 424a and 424b, 10G Ethernet MAC
block 426, Display Port to Ethernet block 432, PCI to Ethernet
block 434, a Display Port PHY-Lite layer 206 (from FIG. 2) and
10GBASE-T PHY layer blocks 436a and 436b.
[0083] FIG. 5A is a block diagram of an exemplary single IC device
configured for use in a client system, in accordance with an
embodiment of the invention. FIG. 5A shows an exemplary embodiment
of the LAN subsystem 314, which is configured for use in a client
system. Referring to FIG. 5A, there is shown a single IC device
500, a GPU 306 (from FIG. 3), an ICH (from FIG. 3), a Display Port
connector 316, Ethernet connectors 318a and 318b and 10GBASE-T PHY
layer blocks 436a and 436b. The single IC device 500 may comprise a
MAC client 422a, MAC client 422b, time stamp shims 424a and 424b,
10G Ethernet MAC block 426, Display Port to Ethernet block 432, PCI
to Ethernet block 434 and a Display Port PHY layer 244 (from FIG.
2).
[0084] The single IC device 500 may comprise suitable logic,
circuitry and/or code that may be configured to enable reception of
Ethernet frames via the Ethernet connector 318, which encapsulate
Display Port mini-packets, de-encapsulation of the Display Port
mini-packets and transmission of the Display Port mini-packets,
which contain digital video 202, via the Display Port connector
316.
[0085] The 10GBASE-T PHY layer 436a may receive line coded bits via
the Ethernet connector 318a. The 10 GBASE-T PHY layer 436b may
receive line coded bits via the Ethernet connector 318b. The
10GBASE-T PHY layer 436a or 436b may decode the received line coded
bits, which may be sent to the 10G Ethernet MAC block 426. The 10G
Ethernet MAC block 426 may assemble the received decoded bits to
construct one or more Ethernet frames EFR. The 10G Ethernet MAC
block 426 may determine whether the constructed Ethernet frames EFR
contain one or more Display Port mini-packets, MPR, or Ethernet
payloads, EPR, which may not contain Display Port mini-packets. The
10G Ethernet MAC block 426 may make the determination based on a
designation within EtherType field within the received Ethernet
frames EFR. The 10G Ethernet MAC block 426 may send the Ethernet
frames EFR to the time stamp shim 424a or 424b.
[0086] The time stamp shim 424a may send Ethernet frames, EFR,
which contain encapsulated Display Port mini-packets, to the MAC
client 422a. Additionally, the MAC client 422a may determine
whether the Ethernet frames contain video data or AUX Channel data
based on an EtherTypeSubType field within the Ethernet frames. At a
computing device 122, received Display Port mini-packets MPR may
contain video data. The computing device 122 may also receive AUX
Channel data. The MAC client 422a may de-encapsulate the Display
Port mini-packets MPR (or AUX channel data) from the Ethernet
frames EFR. The MAC client 422a may send the Display Port
mini-packets MPR (or AUX channel data) to the Display Port to
Ethernet block 432. The Display Port to Ethernet block 432 may
convert the Display Port mini-packets MPR to bits, which may be
sent to the Display Port PHY layer 244. The Display Port to
Ethernet block 432 may also send AUX channel data to the Display
Port PHY layer 244. The Display Port PHY layer 244 may assemble the
bits to reconstruct the Display Port mini-packets MPR.
[0087] In the case where the Display Port mini-packets contain
video data, the Display Port mini-packets may be sent to the
Display Port connector 316 via the Video Main Lanes [3:0]. The
Display Port mini-packets may be sent to the multimedia monitor 124
for display. In instances where the Ethernet frames may comprise
AUX channel data, the AUX channel data may be sent to the GPU 306
via the AUX Channel. The GPU 306 may transfer the data to the MCH
304. The MCH 304 may in turn transfer the data retrieved from the
received Display Port mini-packets to the CPU 302, which may
process the data.
[0088] In various embodiments of the invention, the Display Port
PHY layer 244 may comprise a transmitter (TX) block, a receiver
(RX) block, a transceiver (TX/RX) block and a selector switch. The
TX/RX block receives input signals from the AUX Channel interface
and outputs the received signals to the interface 440. The TX/RX
block also receives input signals from the interface 440 and
outputs the received signals to the AUX Channel interface.
[0089] The Display Port PHY layer 244 may receive an input
configuration control signal, Config_Cntl, which configures the
Display Port PHY layer 244 for use in a client system. When the
Display Port PHY layer 244 is configured for use in a client
system, the selector switch couples the input of the RX block to
the interface 440. In this aspect of the invention, the RX block
may receive input signals from the interface 440 via the selector
switch and outputs the received signals to the Video Main Lanes
[3:0] interface. When the Display Port PHY layer 244 is configured
for use in a client system, the TX block may be inactive. When the
TX/RX block receives and/or transmits AUX channel data, the
selector switch may be configured such that the TX block and RX
block are inactive.
[0090] The time stamp shim 424b may send Ethernet frames, EFR,
which do not contain encapsulated Display Port mini-packets to the
MAC client 422b. The MAC client 422b may de-encapsulate the
Ethernet payloads, EPR, from the received Ethernet frames EFR. The
MAC client 422b may send the Ethernet payloads EPR to the PCI to
Ethernet block 434. The PCI to Ethernet block 434 may convert the
Ethernet payloads EPR to signals, which may be sent to the ICH 310.
The ICH 310 may convert the signals to bits, which may be sent to
the CPU 302 via the MCH 304. The CPU 302 may process the data.
[0091] In an exemplary embodiment of the invention, the LAN
subsystem 314 may comprise the Display Port to Ethernet block 432,
the Display Port PHY layer 244, the MAC clients 422a and 422b, the
time stamp shims 424a and 424b, the 10G Ethernet MAC block 426 and
the PCI to Ethernet block 434. In another exemplary embodiment of
the invention, the LAN subsystem 314 may comprise the Display Port
to Ethernet block 432, the Display Port PHY layer 244, the MAC
clients 422a and 422b, the time stamp shims 424a and 424b, the 10G
Ethernet MAC block 426, the PCI to Ethernet block 434 and the
10GBASE-T PHY layer blocks 436a and 436b.
[0092] In various embodiments of the invention, the video server
104 may selectively transmit digital video 202 to one or more of a
plurality of video monitors 124, each of which may be connected, by
point-to-point connection, to a corresponding computing device
122.
[0093] The video server 104 may generate Display Port mini-packets,
which may be selectively displayed on one or more of a plurality of
multimedia monitors. In this regard, the physical Video Main Lanes
[3:0] and AUX Channel group shown in FIG. 4, may represent a
plurality of logical Video Main Lanes [3:0] and AUX Channel groups,
wherein each logical group may correspond to one of the plurality
of multimedia monitors 124. Each logical group may be distinguished
based on the Ethernet MAC address associated with the computing
device 122 to which the multimedia monitor 124 may be connected by
point-to-point connection, for example.
[0094] The GPU 306 within the video server 104 may generate Display
Port mini-packets comprising digital video 202 for rendering at the
selected multimedia monitor 124, which is attached to the
destination computing device 122. The GPU 306 may select a logical
Video Main Lanes [3:0] and AUX Channel group, which corresponds to
the selected multimedia monitor 124 based on the Ethernet MAC
address associated with the computing device 122, to which the
multimedia monitor 124 may be connected. The GPU 306 may generate
one or more Display Port mini-packets, which may be sent to the
Display Port-Lite layer 206 via the Video Main Lanes [3:0]. The
Display Port mini-packet may comprise a destination identifier,
which identifies a logical Video Main Lanes [3:0] and AUX Channel
group, which in turn identifies the destination computing device
122. The Display Port mini-packets may be sent from the Display
Port-Lite layer 206 to the Display Port to Ethernet block 432. The
Display Port to Ethernet block 432 may in turn send the Display
Port mini-packets to the MAC client 422a.
[0095] The MAC client 422a may encapsulate the Display Port
mini-packets in Ethernet frames and send the Ethernet frames to the
10G Ethernet MAC block 426. The MAC client 422a may designate a
value in the Destination Address field within the Ethernet frame,
which corresponds to the MAC address for the destination computing
device 122, based on the destination identifier information
associated with the received Display Port mini-packets. The
Ethernet frames may be sent to the time stamp shim 424a, which may
insert a time stamp within the Ethernet frame. The time stamped
Ethernet frame may then be sent to the 10G Ethernet MAC block
426.
[0096] The 10G Ethernet MAC block 426 may generate a value for
insertion in the EtherTypeSubType field within the Ethernet frames
based on whether the Ethernet frames encapsulate Display Port
mini-packets or AUX channel data. The 10G Ethernet MAC block may
also insert fields within the Ethernet header which enable the
utilization of AV Bridging capabilities for the transport of the
Ethernet frame within the network 112, for example a traffic class
designation. The Ethernet frames may be sent to the 10GBASE-T PHY
block 436a or 436b, which may subsequently transmit bits via the
corresponding Ethernet connector 318a or 318b. The Ethernet frames
may be transmitted via the network 112 or another network. The
destination address for the Ethernet frames may indicate that the
destination is the computing device 122, which is connected via a
point-to-point connection to the selected multimedia monitor
124.
[0097] Similarly, each of the multimedia monitors 124 may transmit
AUX channel data to the video server 104, for example encryption
keys. The AUX channel data may be transmitted via a corresponding
AUX channel and received by the Display Port PHY layer 244. The AUX
channel data may be generated by the CPU 302 and communicated to
the GPU 306 via the MCH 304. The GPU 306 may send the AUX channel
data via the AUX channel. The AUX channel data may be sent to the
Display Port to Ethernet block 432. The Display Port to Ethernet
block 432 may in turn send the AUX channel data to the MAC client
422a. The MAC client 422a may encapsulate the AUX channel data in
Ethernet frames and send the Ethernet frames to the 10G Ethernet
MAC block 426.
[0098] The 10G Ethernet MAC block 426 may send the Ethernet frames
to the 10GBASE-T PHY block 436a or 436b, which may subsequently
transmit bits via the corresponding Ethernet connector 318a or
318b. The Ethernet frames may be transmitted via the network 112 or
another network. The Destination Address within the Ethernet frames
may indicate that the destination is the video server 104. The
Source Address within the Ethernet frames may indicate the
computing device 122 from which the Ethernet frames were sent. The
video server 104 may receive the Ethernet frames, which contain
Display Port mini-packets. The video server 104 may identify the
multimedia monitor 124 associated with the Display Port
mini-packets based on the Source Address field contained within the
received Ethernet frames.
[0099] FIG. 5B is a block diagram of an exemplary single IC device
configured for use in a client system, in accordance with an
embodiment of the invention. FIG. 5B shows an exemplary embodiment
of the LAN subsystem 314, which is configured for use in a client
system. FIG. 5B differs from FIG. 5A in that the exemplary single
IC device shown in FIG. 5B incorporates the 10 GBASE-T PHY layer
blocks 436a and 436b from FIG. 5A. Referring to FIG. 5B, there is
shown a single IC device 550, a GPU 306 (from FIG. 3), an ICH (from
FIG. 3), a Display Port connector 316 and Ethernet connectors 318a
and 318b. The single IC device 550 may comprise a MAC client 422a,
MAC client 422b, time stamp shims 424a and 424b, 10G Ethernet MAC
block 426, Display Port to Ethernet block 432, PCI to Ethernet
block 434, a Display Port PHY-Lite layer 206 (from FIG. 2) and 10
GBASE-T PHY layer blocks 436a and 436b.
[0100] Various embodiments of the invention as shown in FIGS. 4A,
4B, 5A and 5B may not be limited to 10G Ethernet networks, but may
also be practiced in 10BASE-T networks, 100BASE-TX networks, 2.5G
networks, 5G networks, 40G networks, 100G networks and/or 1000G
networks, for example. Various embodiments of the invention may be
practiced in networks, which utilize copper-based interfaces as
well as optical-based interfaces.
[0101] FIG. 6 is a flowchart illustrating exemplary steps for a
single IC device configured for use in a server system, in
accordance with an embodiment of the invention. The flowchart of
FIG. 6 is exemplary as various embodiments of the invention may
also be practiced with other digital video protocols, including HD
video. Referring to FIG. 6, the single IC device 450 may be
configured, based on a control signal, an external pin and/or an
internal fuse (as described above), for use in a server system. In
step 602, the GPU 306 within the video server 104 may encapsulate
digital video in Display Port mini-packets. In step 604, an
EtherTypeSubType field value may be set to a value indicating that
the Display Port mini-packets encapsulate digital video. In step
606, the Display Port mini-packets may be encapsulated in Ethernet
frames by the MAC client 422a within the LAN subsystem 314. The
Ethernet frames may comprise the EtherTypeSubType field designation
determined in step 604. In step 608, the 10G Ethernet MAC block 426
may determine an AV Bridging traffic class. In step 610, the LAN
subsystem 314 may transmit the Ethernet frames via the network 112
to the computing device 122.
[0102] FIG. 7 is a flowchart illustrating exemplary steps for a
single IC device configured for use in a client system, in
accordance with an embodiment of the invention. The flowchart of
FIG. 7 is exemplary as various embodiments of the invention may
also be practiced with other digital video protocols, including HD
video. Referring to FIG. 7, the single IC device 550 may be
configured, based on a control signal, an external pin and/or an
internal fuse (as described above), for use in a client system. In
step 702, the computing device 122 may receive Ethernet frames from
the video server 104 via the network 112. Step 704 may determine
whether the received Ethernet frames contain Display Port
mini-packets or AUX Channel data. When the received Ethernet frames
do not contain Display Port mini-packets or AUX Channel data, in
step 706, the received Ethernet frames may be processed utilizing
conventional Ethernet processing. In this regard, the Ethernet
frames may be sent to the MAC client 422b within the LAN subsystem
314.
[0103] When the received Ethernet frames contain Display Port
mini-packets or AUX Channel data, in step 708, the MAC client 422a
may de-encapsulate the Display Port mini-packets or AUX Channel
data from the Ethernet frames. Step 710 may determine whether the
Ethernet frames contain Display Port mini-packets, which
encapsulate digital video. When the Ethernet frames contain Display
Port mini-packets, which contain digital video, in step 712, the
Display Port mini-packets may be sent to the multimedia monitor
124. The multimedia monitor 124 may render the digital video on the
monitor. When the Ethernet frames do not contain Display Port
mini-packets, which encapsulate digital video, in step 714, the AUX
Channel data may be sent via an AUX channel to the GPU 306 and/or
multimedia monitor 124. The data sent to the GPU 306 may
subsequently be sent to the CPU 302.
[0104] Exemplary aspects of a single device for handling server
side operations for A/V bridging and A/V bridging extensions may
comprise a single IC device 450 configured to enable encapsulation
of generated digital video data 202 within an encapsulating PDU.
The encapsulating PDU may be an Ethernet frame or an IP packet. The
generated digital video data 202 may itself be encapsulated within
one or more Display Port mini-packets, in which case, the Display
Port mini-packet(s) with encapsulated generated digital video data
202 may be encapsulated within the encapsulating PDU(s). The single
IC device 450 may enable determination of a traffic class
designation associated with the encapsulating PDU. The single IC
device 450 may enable transmission of the encapsulating PDU via a
network 112 based on the traffic class designation. The single IC
device 450 may enable indication of whether the transmitted
encapsulating PDU encapsulated the generated digital video 202
based on at least one data type identifier. The data type
identifiers may comprise an EtherType and an EtherTypeSubType.
[0105] Exemplary aspects of a single device for handling client
side operations may include a single IC device 550 configured to
enable extraction of received digital video data that is
encapsulated within an encapsulating PDU. The encapsulating PDU may
be an Ethernet frame or an IP packet. The encapsulating PDU may be
received via a network 112 at a destination device, such as a
computing device 122. The single IC 550 device may enable
transmission of the received digital video data to a multimedia
monitor 124 coupled to the destination device via an interface
connector, such as a Display Port interface connector 136. The
single IC device 550 may enable extraction of the received digital
video from the encapsulating PDU based on a data type. The data
type may be determined based on at least one data type identifier.
The data type identifier may comprise an EtherType and an
EtherTypeSubType. In various embodiments of the invention, the
received digital video data 202 may be encapsulated within one or
more Display Port mini-packets, in which case, the Display Port
mini-packet(s) with encapsulated received digital video data may be
encapsulated within the encapsulating PDU(s). Thus, the data type
identifiers may enable determination of when the encapsulating
PDU(s) comprise one or more Display Port mini-packets and/or when
the received digital video data is encapsulated within the Display
Port mini-packet(s).
[0106] The single IC device may be configured for server side
operations and/or client side operations based on a control signal,
an internal fuse, firmware and/or a determined logic level coupled
to a contact point to the single IC device. The control signal may
enable dynamic configuration of the single IC device.
[0107] Another embodiment of the invention may provide a
machine-readable storage, having stored thereon, a computer program
having at least one code section executable by a machine, thereby
causing the machine to perform the steps as described herein for a
single device for handling client side and server side operations
for A/V bridging and A/V bridging extensions.
[0108] Accordingly, the present invention may be realized in
hardware, software, or a combination of hardware and software. The
present invention may be realized in a centralized fashion in at
least one computer system, or in a distributed fashion where
different elements are spread across several interconnected
computer systems. Any kind of computer system or other apparatus
adapted for carrying out the methods described herein is suited. A
typical combination of hardware and software may be a
general-purpose computer system with a computer program that, when
being loaded and executed, controls the computer system such that
it carries out the methods described herein.
[0109] The present invention may also be embedded in a computer
program product, which comprises all the features enabling the
implementation of the methods described herein, and which when
loaded in a computer system is able to carry out these methods.
Computer program in the present context means any expression, in
any language, code or notation, of a set of instructions intended
to cause a system having an information processing capability to
perform a particular function either directly or after either or
both of the following: a) conversion to another language, code or
notation; b) reproduction in a different material form.
[0110] While the present invention has been described with
reference to certain embodiments, it will be understood by those
skilled in the art that various changes may be made and equivalents
may be substituted without departing from the scope of the present
invention. In addition, many modifications may be made to adapt a
particular situation or material to the teachings of the present
invention without departing from its scope. Therefore, it is
intended that the present invention not be limited to the
particular embodiment disclosed, but that the present invention
will include all embodiments falling within the scope of the
appended claims.
* * * * *