Priority

This application claims priority to co-owned and co-pending U.S. Patent Application Serial No. 14/168,633 filed on January 30, 2014 and entitled "METHODS AND APPARATUS FOR ENABLING AND DISABLING SCRAMBLING OF CONTROL SYMBOLS", which claims priority to co-owned and co-pending U.S. Provisional Patent Application Serial No. 61/759,311 filed on January 31, 2013 and entitled "METHODS AND APPARATUS FOR ENABLING AND DISABLING SCRAMBLING OF CONTROL SYMBOLS", each of the foregoing being incorporated herein by reference in its entirety.

Related Applications

This application is related to co-owned, co-pending U.S. Patent Application Serial No. 13/747,264, filed January 22, 2013 and entitled "METHODS AND APPARTUS FOR THE INTELLIGENT SCRAMBLING OF CONTROL SYMBOLS". 12/976,274 filed December 22, 2010 and entitled "METHODS AND APPARATUS FOR THE INTELLIGENT ASSOCIATION OF CONTROL SYMBOLS", and 13/747,383 filed January 22, 2013 and entitled "METHODS AND APPARATUS FOR ERROR RATE ESTIMATION", each of the foregoing being incorporated herein by reference in its entirety.

Background

1. Technological Field

The present disclosure relates generally to the field of data networking and telecommunications. More particularly, in one exemplary aspect, the present disclosure is directed to the intelligent configuration of scrambling operation to accommodate e.g., both scrambling and non-scrambling connections (such as to e.g., legacy type devices). 2. Description of Related Technology

HDMI (High-Definition Multimedia Interface) (see, inter alia, www.hdmi.org) is an exemplary dominant digital audio/video interface technology specified by the HDMI Founders. Current incarnations of the standard specify support for simple networking of digital audio/visual (A/V) interconnects, intended to be used primarily between an arbitrary assembly of multimedia "sources" (e.g., set-top boxes, DVD players, Blu-ray Disc players, video game consoles, computers or CPUs) and "sinks" (e.g., display monitors, home-theater system, etc.). This interconnection is generally unidirectional in nature; i.e., from source to sink, in current implementations.

As a brief aside, the current revision of HDMI (HDMI 1.4) utilizes TMDS

(Transition Minimized Differential Signaling) to transmit video, audio and auxiliary data over three main HDMI data lanes via one of three modes. FIG. 1 illustrates these TMDS modes in an exemplary 720x480p video frame. The three modes include: (1) a video data period in which the pixels of an active video line are transmitted; (2) a data island period in which audio and auxiliary data are transmitted; and (3) a control period which occurs between video and data island periods. HDMI utilizes TMDS in order to send 10-bit characters that are transmission minimized encoded.

During control periods, control symbols are transmitted repeatedly on the three HDMI main data lanes. HDMI defines four control symbols, representing the four values ObOO, ObOl, Ob 10 and Obi 1. The value transmitted on lane zero represents whether HSYNC, VSYNC, both or neither is/are being transmitted, and the values transmitted on lanes 1 and 2 are set to non-zero during preambles. Preambles are constructed from eight identical control symbols and are used to signify imminent transitions to data island periods or video data periods. Table 1 illustrates the preambles used for each data period type (i.e., TMDS mode).

Additionally, Table 2 illustrates the control signal-assignment on each of the three main TMDS channels.

The two control signals used for each of the TMDS channels are encoded into ten-bit codes as follows: case (Dl, DO):

0,0: q_out [9:0] = Obi 101010100;

0.1: q_out [9:0] = Ob0010101011;

1, 0: q_out [9:0] = Ob0101010100;

1,1: q_out[9:0] = Ob1010101011;

endcase;

As can be seen from above, these ten-bit codes used for the four control symbols have predominant clock pattern content (i.e., a significant amount of transmissions of 0101 bit-pattern sequences). Furthermore, the control symbols for control values Ob 10 and Ob11 are not DC balanced, which results in a significant baseline "wander" during the time that VSYNC is transmitted. Note also that VSYNC is often used in negative parity, which means that the VSYNC value transmitted is "0" when VSYNC is asserted, and "1" when VSYNC is not asserted (depending on the video frame specific resolution details).

HDMI uses the unique high-transition content of these control symbols to distinguish them from other types of symbols used in HDMI. The high-transition content can be detected by the receiver, and the control symbols may be used by the receiver to perform symbol alignment when first acquiring the incoming signal stream (so-called symbol alignment synchronization).

Unfortunately, existing HDMI implementations may produce undesirable electromagnetic interference (EMI) with nearby wireless services (for example: Wi- Fi, PAN (e.g., Bluetooth), and/or cellular services). The resultant radio frequency interference can negatively impact, for example, an end user's Wi-Fi bandwidth, and reduce cellular bandwidth (or drop cellphone calls) when the appropriate wireless services are used simultaneously with HDMI. Such a problem is exacerbated in devices in which HOMI is used in close proximity with other wireless services, such as in a laptop computer, a tablet, or a smart phone.

Various solutions for handling the electromagnetic emissions have been proposed. For example, in incipient HDMI proposals, the use of scrambling for control symbols is mandatory for certain transmission speeds (e.g., above 340 million Tcharacter/sec/channel, where a Tcharacter comprises 10 bits of information that represent a byte of data or a control symbol according to the TMDS encoding specification). It is currently anticipated that scrambling may be required for all transmission rates. Those of ordinary skill in the related arts will readily appreciate that where a scrambler is used to transmit a data stream, a descrambler must be used within the receiver to descramble the received data stream. Consequently, in order to support both future and legacy products, the Assignee hereof ideally desires methods and apparatus configured to intelligently enable and/or disable scrambling capabilities.

Improved apparatus and methods are needed to configure scrambling and non- scrambling compatibilities, such as when designing for a broad spectrum of possible usage scenarios. More specifically, such apparatus and methods would, inter alia, provide for mechanisms that intelligently negotiate/determine scrambling and/or non- scrambling operation when connected to a peer device.

Summary

The aforementioned needs are satisfied by providing, inter alia, improved apparatus and methods for intelligent selection and/or configuration of scrambling operation, such as for instance to accommodate both scrambling and non-scrambling connections (such as to e.g., legacy type devices).

In a first aspect, a method for intelligent configuration of a scrambling operation is disclosed. In one embodiment, the method includes: establishing a connection to a device; determining whether the device supports scrambling configuration; and when the device supports scrambling configuration, enabling a scrambler. In one variant, when the device does not support the scrambling configuration, the scrambler is disabled. In another embodiment, the method includes establishing a connection to a device; determining that the device supports a scrambling configuration; based at least on the determination that the device supports the scrambling configuration, enabling a scrambler.

In a second aspect, a computerized apparatus is disclosed. In one embodiment, the computerized apparatus includes a processor and logic configured to intelligently configure a scrambler. In another embodiment, the computerized apparatus includes a processor, an interface in data communication with the processor, and a non-transitory computer medium having at least one program stored thereon. The at least one computer program includes a plurality of instructions that are configured to, when executed, cause the computerized apparatus to: establish a connection to a device, determine if the device supports one or more scrambling functionalities, and configure the interface to transmit and/or receive data based at least in part on the determination.

In a third aspect, a computer readable apparatus is disclosed. In one embodiment, the apparatus includes a non-transitory storage medium having a plurality of instructions stored thereon, the plurality of instructions configured to, when executed, cause the sink device to: provide information indicative of one or more capabilities supported by the sink device, and select a scrambling profile of a plurality of scrambling profiles to use for data communication with a source device based at least on the information from the source device.

In a fourth aspect, a system is disclosed. In one embodiment, the system includes a first device and a second device in data communication with one another, such as via e.g., an HDMI-compliant interface. In another variant, at least one "source" and at least one '"sink" are in communication with one another via the interface, and negotiate scrambler operation between them.

In a fifth aspect, a method of operating computerized apparatus so as to at least mitigate electromagnetic emissions is disclosed.

In a sixth aspect, scrambling logic is disclosed. In one embodiment, the logic comprises software-based logic configures to run on a processing apparatus. In another embodiment, the logic is hardware-based.

Other features and advantages will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below. Brief Description of the Drawings

FIG. 1 is a graphical representation of an exemplary prior art HDMI 720x480p video frame.

FIG. 2 is a logical block diagram of an exemplary HDMI network.

FIG. 3 is a logical flow diagram illustrating one embodiment of the process steps for determining an appropriate mode of operation, in accordance with the principles described herein.

FIG. 4 is a functional block diagram illustrating one embodiment of a circuit adapted to implement the scrambling of control symbols, in accordance with the disclosure.

FIG. 5 is a functional block diagram illustrating one embodiment of a circuit adapted to implement the unscrambling of scrambled control symbols in accordance with the disclosure.

FIG. 6 is a functional block diagram illustrating an embodiment of a circuit adapted to implement the scrambling of control symbols in accordance with the disclosure.

FIG. 7 is a functional block diagram illustrating an embodiment of a circuit adapted to implement the unscrambling of scrambled control symbols in accordance with the disclosure.

FIG. 8 is a functional block diagram illustrating one embodiment of a network component apparatus adapted to implement the methods of the present disclosure.

All Figures © Copyright 2012-2014 Apple Inc. All rights reserved.

Detailed Description

Reference is now made to the drawings, wherein like numerals refer to like parts throughout.

Detailed Description of Exemplary Embodiments

Exemplary embodiments are now described in detail. While these embodiments are primarily discussed in the context of an HDMI audio/visual (A/V) component network, it will be recognized by those of ordinary skill that the present disclosure is not in any way limited to HDMI applications or protocols. In fact, the various embodiments set forth herein are useful in any network that can benefit from the reduction of electromagnetic interference, such as for example in instances where transmitted symbols include predominant clock pattern content in order to improve DC-balance on the transmission medium.

As used herein, the term "HDMI" refers without limitation to apparatus and technology compliant with HDMI specifications, such as "HDMI Specification" - Version 1.4b, dated October 11, 2011 which is incorporated herein by reference in its entirety, and including any prior or subsequent revisions thereof.

Furthermore, while the exemplary embodiments herein are disclosed in the context of a serial transmission of digital data represented as electrical levels, ones having ordinary skill in the related arts given the present disclosure will recognize that the various techniques may also extend to other systems and applications including, inter alia, multi-level wired systems (e.g., three-level encoded Ethernet), and modulated transmission schemes (e.g., a high frequency carrier that is modulated in the amplitude or frequency domain (AM or FM) by the signals being transmitted).

Exemplary HDMI System -

Referring now to FIG. 2, one exemplary HDMI network is illustrated. As shown, the HDMI network comprises one or more source devices 202, and one or more sink devices 204. It is appreciated that while the illustrated network describes the foregoing topology (i.e., one or more sources, and one or more sinks), the various aspects of the disclosure are in no way so limited.

As previously described with FIG. 1, HDMI transmissions include: (1) a video data period in which the pixels of an active video line are transmitted; (2) a data island period in which audio and auxiliary data are transmitted; and (3) a control period which occurs between video and data island periods.

As shown, exemplary source 202A supports both scrambled and non- scrambled transmissions, whereas source 202B only supports non-scrambled transmissions. Similarly, sink 204A supports both scrambled and non-scrambled reception, whereas sink 204B only supports non-scrambled reception. During scrambled operation, source 202A and sink 204A enable respective complementary linear feedback shift registers (LFSR) which are XORed with the data stream. During unscrambled operation, source 202A and sink 204A disable the LFSR. Under certain circumstances (such as above a transmit bit rate threshold), the source 202A and sink 204A may optionally enable scrambling to improve performance and reduce EMI emissions. Incipient draft HDMI standards have required that: (i) a source shall only use scrambling when it determines that the sink supports scrambling, and (ii) a sink that supports scrambling must be able to determine whether the incoming signal is being scrambled or not. More directly, when source 202A is connected to sink 204B, its LFSR must be disabled. Similarly, when source 202B is connected to sink 204A, the sink 204A must disable its receiving LFSR.

The Assignee hereof often prioritizes "user experience" over other considerations; thus to these ends, methods and apparatus are needed which intelligently configure scrambling operation to accommodate e.g., both scrambling and non-scrambling connections (such as to e.g., legacy type devices). Ideally, there should be no perceptible (to a human observer) delay as a result of the discovery process, so as to optimize the aforementioned user experience. Furthermore, there should be ideally little or no user-visible artifacts (e.g., blank or flashing screen) when enabling/disabling scrambling.

Additionally, various use cases may have more or less commercial importance for the Assignee hereof. For example, while dynamic enabling/disabling of scrambling may be supported within the larger HDMI population, various embodiments described herein may be configured if desired to limit enabling/disabling of scrambling to certain situations e.g., when there is a change of display resolution, etc. Methods -

FIG. 3 illustrates one exemplary embodiment of a method 300 for determining an appropriate mode of operation according to the disclosure.

At step 302 of the method 300, a source device and a sink device establish a connection. In one embodiment the connection is a control and data connection, and can be established under any number of different scenarios, such as for instance being manually configured/initiated by a user, automatically (e.g., by software) and/or semi- automatically (e.g., upon making of a physical connection between the two devices). In one exemplary embodiment, the connection is an HDMI connection which includes: (1) video data, (2) other data (e.g., audio, text, etc.), (3) control, (4) null data (blanking intervals, guard data, etc.). Various other protocols and technologies may similarly benefit from the principles described herein; other common examples of bus technologies include for example (and without limitation): DisplayPort™, Thunderbolt™, USB, Firewire™, etc.

The connection may be wired or wireless, and may incorporate one or more logical virtual connections.

While the foregoing topology is described in terms of a unidirectional connection between a source device (transmitter) and a sink device (receiver), it is appreciated that other topologies may be used, including e.g., unicast, multicast, broadcast, bidirectional, unidirectional, etc. Additionally, the following discussions are described within the context of a direct connection; however it is further appreciated that in some instances, various principles described herein may have application to both circuit-switched and/or packet-switched networks and/or other technologies that incorporate one or more intermediary entities (e.g., network or relay nodes between the source and the sink).

At step 304 of the method 300, the source device and/or sink device determine if scrambling can be enabled/disabled. In one embodiment, determination can be made explicitly via a messaging transaction. To ensure backward compatibility, the messaging transaction may further take the form of a two-part query that requests the device version/revision, and for versions/revisions which are appropriately enabled, a subsequent query for capabilities may be made. In other common embodiments, the messaging transaction may take the form of a non-fatal query (i.e., where legacy devices are configured to ignore unexpected/unknown transactions).

In yet other embodiments, the source and/or sink read a register and/or configuration file to determine the peer entity's capabilities. For example, devices which are can be configured to enable/disable scrambling may have a dedicated addressable memory space for storing various capabilities flags. In some cases, this dedicated addressable memory space is a hard-coded read only memory (ROM); alternately, the memory space is implemented within registers or device memory.

In still other embodiments, the source and sink receive capabilities information according to an out-of-band process. Common examples of out-of-band processes include e.g., manual input (e.g., a user enables scrambling in both the source and sink), an external registry device (e.g., a networked management entity, etc.), via higher layers of software (such as for instance the application software which controls both the source and the sink, etc.)

In alternate implementations, the devices may implicitly determine scrambling capabilities based on ongoing communications. For example, certain technologies may provide known symbols at regular intervals or associated with prescribed events. Based on the expected symbol, the sink may implicitly determine if the source is scrambling the symbols, or alternately if the symbols are being transmitted in their "unscrambled" form.

In another such example, it is appreciated that scrambling imparts certain desirable qualities to the data stream e.g., reduced emissions, desirable running disparities, limited clock content, etc. An appropriately enabled sink can detect the presence or absence of one or more of these qualities to determine if the source is scrambling the data stream.

Other forms of implicit determination may be based on certain "agreed" use cases, etc. For example, the source and sink may have implicit agreements to enable/disable scrambling under certain use cases. Common examples include, without limitation: exceeding or falling below certain prescribed data rates, the presence of neighboring devices, the presence of neighboring interferers, type of application, etc.

If scrambling can be enabled/disabled, the source device and the sink device negotiate one or more scrambling parameters (step 306) for a connection, otherwise, the source and sink device operate in a default mode (step 308) for the connection.

Examples of scrambling parameters may include e.g., type of scrambler (for example, when multiple different scrambling LFSRs, algorithms, etc. are supported), exceptions (e.g., data or control symbols which are not to be scrambled, etc.), duration of scrambling, etc. For example, a source and sink may have multiple different scrambling capabilities to support a wide range of devices. During operation, the source and the sink must agree (either explicitly or implicitly) on the type of scrambler used, etc. In some use scenarios, the source and sink may need to explicitly negotiate or agree on certain circumstances where scrambling may or may not be enabled. For instance, in some cases the source and sink may need to dynamically determine when to scramble data, control, and null data. In other examples, the scrambling may only be implemented over a subset of the periods (e.g., data-only, etc.).

Still other options may include scrambler operation after e.g., low power modes, display resolution changes, mode changes, etc. For example, in some cases, the scrambler should be reset after each resolution change. In other examples, the scrambler is not reset during low power modes.

As step 310 of the method 300, data is transacted over the connection. Example Operation

Referring now to one illustrative example, various principles as described herein are applied to one exemplary HDMI network.

The exemplary sink device indicates that it supports optional scrambling operation with e.g., a flag that is set in the sink's extended display identification data (EDID).

As a brief aside, the EDID is a data structure that describes the sink device's capabilities to a source device (e.g. graphics card or set-top box). The composition of the EDID data structure is defined by the Video Electronics Standards Association (VESA). For example, the EDID may include information such as e.g., manufacturer name and serial number, product type, phosphor or filter type, timings supported by the display, display size, luminance data, and pixel mapping data.

Traditionally, the EDID is transmitted from the sink device to the source device during connection initiation. In other configurations, the EDID may be read from the sink device. Typical implementations store the EDID in a non-volatile memory (e.g., programmable read-only memory (PROM), electrically erasable (EEPROM), FLASH, etc.) which can often be read even if the sink device does not have power.

The EDID data structure is commonly used with a companion display data channel (DDC) access protocol. The DDC protocol is used when the source and sink negotiate one or more display parameters, etc. In one exemplary embodiment, the DDC protocol is performed over an I2C (Inter-Integrated Circuit) bus.

In either implementation, the flag may be addressable at a particular register (or memory space) address. During initialization (or operation) the source device can read the flag, or alternately the sink device can advertise the capability. The additional time required to read the flag (over the duration to read e.g., existing EDID memory space) is negligible, and has no perceptible impact. In some optimized variants, the register space may be organized so that all appropriate capabilities can be read by the source device in a single read transaction. During normal operation, if a source device supports scrambling, then it reads the sink capabilities from the appropriate address space. If the sink device supports scrambling, then the source device determines if scrambling should be enabled.

In some embodiments, the source may automatically enable scrambling where the sink is similarly enabled. In other embodiments, the source device may consider other factors in its determination of whether to enable scrambling, including without limitation: effects on power consumption, computational complexity, data requirements, neighboring device requirements, etc. For example, different types of scrambling mechanisms have different degrees of EMI emission, processing, control overhead, power consumption, etc. So-called "self-synchronizing" scramblers may reduce control overhead, but may require more computational complexity (and corresponding power) than other types of scramblers in the source and/or sink. In other examples, for slow enough and/or intermittent transactions, scrambling may not be required at all (e.g., EMI emissions are relatively low) and may be disabled to save on power consumption.

Certain embodiments may further enable and/or disable other features in view of the scrambling/descrambling state. For example, scrambling may assist in certain types of clock recovery (e.g., because EMI emissions which "bleed" into clock recovery circuits are reduced, etc.). Therefore, when scrambling is enabled the receiver can recover the clock from much lower power signaling, and the source may transmit the clock at reduced signal amplitudes. Other common features which may be enabled/disabled include e.g., error recovery, forward error correction, reduced power consumption modes (e.g., sleep, idle, etc.). In alternate embodiments, these features may be separately enabled and/or disabled.

Moreover, while the foregoing example is described in terms of initial configuration (e.g., when the source and sink are first connected), it is appreciated that other events may trigger re-evaluation, or may delay such evaluation. For example, re- evaluation may occur when there is a change in operating mode (e.g., display size), a change in power consumption, a change in neighboring device operation, a change in software application, etc. In still other cases, a user or other external entity may choose to enable/disable scrambling operation. For example, the presence neighboring device activity (e.g., a phone call) may trigger the source to re-evaluate and possibly transition to scrambling operation (as well as transition from scrambling operation when the call is completed).

In some embodiments, when the source determines that scrambling is necessary, the source writes to a status flag in the HDMI DDC register space (or I2C space). When the sink reads the DDC register space, the sink can determine if scrambling is enabled. The register write/read mechanism may be suitable for implementations where the source enables/disables scrambling at known times (e.g., before commencing video transmission or on a mode-set). However, if the source enables/disables scrambling at arbitrary times, the sideband channel and the main link signaling may fall out of synchronization (resulting in undesirable visual artifacts, or complete link failure).

In one exemplary embodiment, the scrambler may be enabled and disabled according to a periodic (or otherwise well defined) scheme. For example, in one such implementation, the original so-called TMDS "unscrambled" control characters are transmitted to assist in character synchronization (i.e., to identify where the 10-bit character boundaries occur in the bit stream). However, due to the adverse EMI emissions associated with the unscrambled control characters, the proposed HDMI requirements limit such transmissions to a few unscrambled control characters (in sequence), so as to minimize the EMI/RFI impact. In one such instance, the transmitter transmits a small number of these at periodic intervals (e.g. once every video frame). The receiver determines that scrambling is not being used if it receives a sequence that exceeds the expected number. In other examples, since "scrambled" control symbols are distinct and are never transmitted when scrambling is not being used, detecting one (or a few) scrambled control symbols allows the receiver to determine that scrambling is enabled.

In other embodiments, the sink device may be configured to actively detect scrambling based on e.g., known control symbols. For instance, TMDS control symbols have specific bit patterns (see e.g., Description of Related Technology, discussed supra) when scrambling is not used, which can be clearly distinguished from other bus traffic. These control characters are also never produced when the scrambler is enabled (i.e., no input to the scrambling logic will result in the identical waveform). Consequently, a sink device can detect that the source is (or is not) scrambling its transmissions by detecting the absence (or presence) of the legacy control characters. Certain "robust" variations may additionally require the detection of a sequence of such control characters (e.g., four control symbols); in some very rare circumstances, even when scrambling is not being used, a number of bit errors may create a false detection.

In the context of these limitations, a sink device can detect scrambling/non- scrambling operation by searching for a string of non-scrambled control characters which do not comply with the defined requirements. For example, if the sink detects more than the prescribed number of non-scrambled control characters with no intervening scrambled control characters, then the sink can infer that scrambling is disabled. For robust designs, the count may be further padded with a margin of error (e.g., the detection of a few extra unscrambled control characters (over the expected number) with no intervening scrambled control characters).

Explicit Scrambler Synchronization - Various implementations may further implement some scheme for synchronizing the LFSR in the source with the complementary LFSR in the sink. In some embodiments, synchronization is performed by forcing the LFSRs to reset to an initial value. In one such implementation, the source resets its own LFSR, and transmits an explicit scrambler reset (SR) sequence to the sink; responsively, the sink resets its LFSR.

It is further appreciated that for certain embodiments, the initialization of the scrambling/descrambling LFSR can be performed regardless of whether scrambling is actually used. In one embodiment, the source and sink can synchronize their respective LFSRs, and shift through LFSR states as successive characters are received, while acquiring character lock. If scrambling is being used, then the LFSRs are already synchronized and can be immediately used. Otherwise, if scrambling is not being used, then the LFSRs can be disregarded. Even if the scrambling is not enabled, the LFSRs may be kept active so that scrambling can be quickly enabled in the future. Conversely, if scrambling is not enabled the LFSRs may be halted to, inter alia, reduce power consumption.

During the character lock process, the sink may not be able to count all ten characters, as the sink may not have character synchronization until near the end of the sequence. Since the sink cannot rely on an accurate count to determine when to enable scrambling, in one exemplary implementation the sink resets the LFSR when it detects a character other than a non-scrambled control character. More directly, the sink device will assume that any received characters (received after the non-scrambled control characters) are scrambled. It is further appreciated that the next scrambled character may still be a control character. For example, when the source enables scrambling during a control character sequence, the next character will be a scrambled control character. Under these situations, the exemplary sink can take the required action e.g., reset the LFSR and immediately descramble the subsequent received scrambled control characters.

In alternate synchronization schemes, the LFSR in the source and sink device may have "self-synchronization" properties. Self-synchronizing LFSRs have a property where the receiving LFSR can match its state to the transmitting LFSR by forcing its inputs to the received data for a designated period. Self-synchronizing LFSRs do not require an explicit reset sequence. Self-synchronization schemes have limited utility in the context of extant HDMI scrambling proposals (although future implementations may incorporate self-scrambling capabilities), and thus the discussion of self-synchronizing LFSRs is provided in a subsequent section hereinafter. Self-Synchronizing Scramblers -

While explicit scrambler synchronization can be used when scrambling occurs at known times e.g., (before start of video transmission, on a mode-set, etc.), however, explicit scrambler synchronization may not be appropriate for usage scenarios where scrambling is enabled/disabled at arbitrary times. Consequently, an alternative mechanism to support arbitrary scrambler synchronization is a self synchronizing scrambler. Self-synchronizing scramblers use the values being transmitted to synchronize the receiver's LFSR. This technique is used in related standards such as the IEEE 1394b-2002 specification, which is incorporated by reference herein in its entirety.

A self-synchronizing scrambler pair exhibits the property where the transmitting LFSR can transmit a particular sequence of symbols; where the particular sequence when received by the receiving LFSR, will result in the transmit and receive LFSRs being synchronized. In one exemplary HDMI self-synchronizing LFSR, a known value is included in the pre-scrambled control character value. This known value is used to generate a 5-bit pre-scrambled value that selects from an alphabet of 32 scrambled control characters.

The sink initializes its LFSR to an initial state and uses the known value to "descramble" the incoming data. This does not require an explicit scrambling reset symbol, nor does the receiver need to explicitly detect whether scrambling is being used or not. Only sixteen (16) of the resulting scrambled control characters will synchronize the receiver's LFSR. Typically, there are many more than sixteen (16) symbols transmitted during each horizontal blanking interval, and so synchronization occurs almost immediately (without perceptible artifacts to the user).

To disable scrambling, the source picks a point in time when it is about to transmit at least 16 control characters, and resets its LFSR to all zeros. The subsequently transmitted control characters use this LFSR value (the LFSR stays zero) and then continues as usual. The transmitted data is scrambled with the reset LFSR (in effect not scrambled), and is "descrambled" in the receiver with a receiving LFSR of zero (in effect not descrambled).

Apparatus -

Referring now to FIG. 4, an exemplary embodiment of a circuit 400 adapted for the transmission of scrambled control symbols is illustrated. The circuit illustrated in FIG. 4 is shown implemented in hardware, although it is appreciated that the logic illustrated in FIG. 4 could readily be implemented in software, or combinations of hardware and software, as well.

The exemplary circuit 400 includes an LFSR 402 which is selected for this embodiment because the operation of the LFSR is advantageously deterministic, while also providing a sequence of bits that appears random. Accordingly, and as discussed previously herein, synchronization between transmitter and receiver can be maintained if the cycles between the LFSR at the transmitter and the LFSR at the receiver remains synchronized, and both LFSR's are loaded with the same seed value. In an exemplary embodiment, the LFSR is a 16-bit LFSR, although it is appreciated that other LFSR configurations could readily be substituted, such as for example, those described previously herein. When using an exemplary 16-bit LFSR, a subset of bits (e.g. the four (4) least significant bits) is used for control symbol encoding. Of this subset of bits, an additional subset (e.g. the two (2) least significant bits of the subset) is fed into an XOR logic gate 404 along with control signals Dl and DO. The output of the XOR logic gate is then combined with the remaining bits from the additional subset (e.g. the two (2) most significant bits of the subset) to produce a 4-bit random value. This random value is then fed into a data structure (e.g., a lookup table 406). The lookup table then chooses a scrambled control symbol value and forwards this scrambled control symbol value to transmitter 408. The scrambled control symbols are in the exemplary embodiment preselected so that they contain desirable numeric properties such that their transmission over a transmission medium minimizes undesirable electromagnetic radiation and resultant EMI. The number of preselected scrambled control symbols can be chosen from any sufficiently large set of scrambled control symbols such that their transmission characteristics are desirable when placed in proximity to other transmission mediums, whether wired or wireless.

Referring now to FIG. 5, an exemplary embodiment of a circuit 500 adapted to implement the reception of scrambled control symbols is illustrated. The circuit illustrated in FIG. 5 is shown implemented in hardware, although it is again appreciated that the logic illustrated could readily be implemented in software as well, or combinations thereof. The circuit 500 includes a receiver 502 that receives the incoming scrambled control symbols from the transmitter. These incoming scrambled control symbols are then fed into a lookup table 504. The lookup table 504 is essentially a reverse of the lookup table 406 shown in FIG. 4; the lookup table in FIG. 5 takes the scrambled control symbol and outputs an apparent random value (e.g., the 4-bit value that served as the input to the lookup table in FIG. 4).

The circuit also includes an LFSR 508 which is synchronized with the LFSR 402 illustrated in FIG. 4 so that its output is identical. Similar to that shown in FIG. 4, in an exemplary embodiment, the LFSR is a 16-bit LFSR, in which a subset of bits (e.g. the four (4) least significant bits) is used for control symbol decoding. This subset of bits is then fed into an XOR logic gate 506, and is XOR'd with the bit value determined by the lookup table 504. The output of this XOR operation is a 4-bit value with the least significant two bits being indicative of the original control signals Dl and DO.

Referring now to FIG. 6, an exemplary embodiment of a circuit 600 adapted for the transmission of scrambled control symbols is illustrated. The circuit illustrated in FIG. 4 is shown implemented in hardware, although it is appreciated that the logic illustrated in FIG. 6 could readily be implemented in software, or combinations of hardware and software, as well. The circuit 600 includes an LFSR 602 which is advantageously used because the operation of the LFSR is deterministic, while also providing a sequence of bits that appears random. In an exemplary implementation, the LFSR is a 16-bit LFSR that is "self-synchronizing" as described previously herein. When using an exemplary 16-bit LFSR, a subset of bits (e.g. the four (4) least significant bits) is used for control symbol encoding.

Of this subset of bits, an additional subset (e.g. the two (2) least significant bits of the subset) is fed into an XOR logic gate 604 along with control signals D1 and D0. The output of the XOR logic gate is then combined with the XOR'd output of the two most significant bits of this subset and the lane number to produce a 4-bit random value. This random value is then fed into a lookup table 606. The lookup table then chooses a scrambled control symbol value and forwards this scrambled control symbol value to transmitter 608.

Referring now to FIG. 7, an exemplary embodiment of a circuit 700 adapted to implement the reception of scrambled control symbols, such as those transmitted in the transmitter of FIG. 6 is illustrated. The circuit illustrated in FIG. 7 is shown implemented in hardware, although it is again appreciated that the logic illustrated could readily be implemented in software as well, or combinations thereof. The circuit 700 includes a receiver 702 that receives the incoming scrambled control symbols from the transmitter. These incoming scrambled control symbols are then fed into a lookup table 704. The lookup table 704 is essentially a reverse of the lookup table 606 shown in FIG. 6; the lookup table in FIG. 7 takes the scrambled control symbol and outputs an apparent random value (e.g., the 4-bit value that served as the input to the lookup table in FIG. 6).

The least significant two bits of this 4-bit value are then fed into an XOR logic gate 706, along with the value of scramble key 710 in order to output the control values "Dl" and -'D0". In order to generate the value of scramble key 710, the most significant two bits of this 4-bit value are fed into a shift register 708. As discussed previously herein, due to the nature of the LFSR chosen in the transmitter, i.e. the generating function for the LFSR does not contain the terms X3, X2 or XI, the shift register can be used in order to generate the appropriate scramble key value for the next scrambled control symbol received at the receiver 702. In this manner, by using a self- synchronizing LFSR in the transmitter, the receiver can be implemented without having to contain its own respective LFSR, thereby greatly simplifying the receiver logic.

Referring now to FIG. 8, an exemplary user device (apparatus) 800 having control symbol encoding/decoding capability is illustrated. As used herein, the term "user device' ^* includes but is not limited to cellular telephones, smartphones (such as for example an iPhone™ manufactured by the Assignee hereof), tablets (such as for example an iPad™), phablets, personal computers (PCs), such as for example an iMac™, Mac Pro™, Mac Mini™, MacBook™, MacBook Pro™, MacBook Air™, and minicomputers, whether desktop, laptop, or otherwise, as well as mobile devices such as handheld computers, PDAs, video cameras, set-top boxes, personal media devices (PMDs) (such as for example an iPod™), display devices (e.g., those compliant with the aforementioned HDMI standard(s)), or any combinations or variants of the foregoing. While a specific device configuration and layout is shown and discussed, it is recognized that many other configurations may be readily implemented by one of ordinary skill given the present disclosure, the apparatus 800 of FIG. 8 being merely illustrative of the broader principles of the disclosure. For example, it is appreciated that the device illustrated in FIG. 8 could readily be implemented as either a source or alternatively as a sink, or in fact could be configured to operate as both. Appropriate modifications to the layout shown would be readily apparent to one of ordinary skill given the present disclosure.

The illustrated apparatus 800 of FIG. 8 includes an upstream plurality of ports and corresponding receiving elements (e.g., receiver or transceiver network interfaces) 802, a downstream plurality of ports and corresponding transmitting elements (transmitting interfaces or transceivers) 804. As used herein, the terms "network interface" or "interface" typically refer to any signal, data, or software interface with a component, network or process including for example and without limitation those of the HDMI, FireWire (e.g., FW400, FW800, etc.), USB (e.g., USB2, USB 2.0, USB 3.0, wireless USB), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), Thunderbolt, or wireless varieties.

The upstream plurality of ports and associated receiving elements 802 may comprise one or more upstream auxiliary channels, one or more upstream media ports, and receiver apparatus (e.g., multiplexing switches, reception logic, clock recovery circuitry, etc.). In one exemplary embodiment, the auxiliary channel is bi-directional and carries management and device control data, and the upstream media ports minimally comprise receivers for unidirectional data lanes, and use of an embedded clock. The receiver apparatus monitors and selectively enables and disables the auxiliary and media ports. In certain embodiments, the receiver apparatus may be adapted to utilize a packet- based unidirectional network protocol, such as the exemplary HDMI protocol previously described herein.

Similarly, the downstream plurality of ports and associated receiving elements 804 comprise one or more downstream auxiliary channels, one or more downstream media ports, and transmitter apparatus (e.g. demultiplexing switches, transmission logic, clock embedding circuitry, etc.). In one exemplary embodiment, the auxiliary channel is bi-directional and carries management and device control data, and the downstream media ports minimally comprise transmitters for unidirectional data lanes, and inclusion of an embedded clock. The transmitter apparatus monitors and selectively enables and disables the auxiliary and media ports. As with the receiver, the transmitter apparatus may be adapted to utilize a packet-based unidirectional network protocol (e.g., HDMI).

In an exemplary implementation, the downstream-facing ports may include a serializer adapted to receive an input word and output a bit stream. For example, in one configuration, the serializer may receive a 10-bit input word and output ten (10) serial bits. In addition, the serializer may also provide an optional corresponding clock.

Conversely, in another configuration, the upstream-facing ports may also include a de-serializer adapted to receive a serial bit stream and output a word. Furthermore, such de-serializing apparatus may additionally require clock recovery circuitry and boundary detection, as is well understood in the digital computing arts. For example, in one embodiment, the de-serializer may receive 10 (ten) serial bits, and convert it into one 10-bit word. When the de-serializer detects a misalignment of timing by one or more bits, the de-serializer accordingly skips or pads its rate accordingly. Furthermore, during initialization, the de-serializer may recognize an initiation sequence.

Also included are one or more storage devices (e.g., a memory subsystem) 810 used to store for example data for transmission or that has been received.

It will be appreciated that not all elements are required in a single device for operation within a "network", for instance a device only capable of "source" operation would not require upstream ports, or certain audio or video elements. Conversely, a "sink" device may not require downstream ports. Moreover, the "receiver" 802 and "transmitter" 804 elements may comprise transceivers capable of both transmission and reception if desired.

Note that as used herein, such network may be comprised of as few as two devices in communication with one another via an interface, or even two components in communication with one another within the same host apparatus.

The processing subsystem 806 may comprise one or more of central processing units (CPU) or digital processors, such as a microprocessor, digital signal processor, field-programmable gate array, RISC core, or plurality of processing components mounted on one or more substrates.

The processing subsystem is coupled to memory subsystem 810, which may include for example SRAM, FLASH and SDRAM components. As used herein, the term "memory" includes any type of integrated circuit or other storage device adapted for storing digital data including, without limitation, ROM. PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS, RLDRAM, SRAM, "flash" memory (e.g., NAND/NOR), and PSRAM.

The processing subsystem may also comprise additional co-processors, such as a dedicated graphics accelerator, network processor (NP), or audio/video processor. As shown processing subsystem 806 includes discrete components, however it is understood that in some embodiments they may be consolidated or fashioned in a SoC (system-on- chip) or other ASIC (application specific integrated circuit) configuration.

The processing subsystem 806 is adapted to receive one or more media streams from an upstream apparatus 802 for processing for media displays such as a video display 812, or audio speakers 814. Processing subsystem 806 may preferentially comprise graphics processors, applications processors, and or audio processors. In "'thin clients", the processing subsystem 806 may be significantly reduced in complexity and limited to simple logic, or in extreme cases altogether non-existent.

The control code scrambling circuitry 816 is, in an exemplary embodiment, tightly coupled (i.e., directly accessible) for execution on the processing subsystem. This circuitry could be embodied in hardware, software or a combination of both. As used herein, the term "circuitry" refers to any type of device having any level of integration (including without limitation ULSI, VLSI, and LSI) and irrespective of process or base materials (including, without limitation Si, SiGe, CMOS and GaAs). ICs may include, for example, memory devices, digital processors, SoC devices, FPGAs, ASICs, ADCs, DACs, transceivers, memory controllers, and other devices, as well as any combinations thereof It is however recognized that the control code scrambling circuitry could alternatively be decoupled and executed independent of the processing element in alternate embodiments.

In an exemplary embodiment, the control code encoding circuitry 816 of the apparatus of FIG. 8 is implemented at least in part as a computer program; e.g., module of executable application software embodied within a tangible medium such as a physical block of memory (for example, the memory subsystem 808 of FIG. 8). As used herein, the term "computer program" or "software" is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example and without limitation, C/C++, Fortran, COBOL, PASCAL, assembly language, and the like, as well as object-oriented environments such as Java™ (including J2ME, Java Beans, etc.).

In one exemplary embodiment, the computer-readable medium includes instructions which are configured to, when executed by a processor, establish a connection to a peer device. In one embodiment the connection is a control and data connection, and can be established under any number of different scenarios, such as for instance being manually configured/initiated by a user, automatically (e.g., by software) and/or semi-automatically (e.g., upon making of a physical connection between the two devices). In one exemplary embodiment, the connection is an HDMI connection which includes: (1) video data, (2) other data (e.g., audio, text, etc.), (3) control, (4) null data (blanking intervals, guard data, etc.). Various embodiments of the apparatus 800 may establish e.g., unidirectional connections, bidirectional, broadcast, multicast, etc.

Once connected, the processor can determine if scrambling can be enabled/disabled. Determinations can be made implicitly (e.g., according to pre-agreed usage cases) or explicitly (e.g., via a messaging transaction). Other common examples include e.g., reading a register and/or configuration file to determine the peer entity's capabilities. For example, devices which are can be configured to enable/disable scrambling may have a dedicated addressable memory space for storing various capabilities flags.

In still other embodiments, the capabilities information can be received according to an out-of-band process. Common examples of out-of-band processes include e.g., manual input (e.g., a user enables scrambling in both the source and sink), an external registry device (e.g., a networked management entity, etc.), via higher layers of software (such as for instance the application software which controls both the source and the sink, etc.)

In yet other valiants, processor may implicitly determine scrambling capabilities based on ongoing communications. For example, certain technologies may provide known symbols at regular intervals or associated with prescribed events.

If scrambling can be enabled/disabled, the device may be further configured to negotiate one or more scrambling parameters for a connection, otherwise, the processor will default to legacy operation. Thereafter, the device is configured to transact data over the connection (either with or without scrambling enabled).

It will be readily appreciated by those of ordinary skill that different combinations and/or variations of the foregoing can be made depending on the desired application and performance attributes.

It will be recognized that while certain embodiments of the disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the disclosure and claims herein.

While the above detailed description has shown, described, and pointed out novel features of the disclosure as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art. The foregoing description is of the best mode presently contemplated. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles, and the scope of the present disclosure should be determined with reference to the claims.