throbber
DTE power over MDIDTE power over MDIDTE Discovery Process Proposal
`
`Robert Muir
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 1
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`DTE power over MDIAgenda•
`
`General MDI link description.
`Level One discovery process proposal
`Discovery process alternatives - review
`Conclusions
`Q and A
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 2
`Juniper v ChriMar
`IPR2016-01397
`
`•
`•
`•
`•
`Agenda
`

`

`Certain assumption have been made about various
`components of the link based upon both customer and
`vendor feedback.
`
`DTE power over MDIMDI Link Description•
`–Link using CAT3 or CAT5 cable will have loop impedance of up to30 Ohms.–Power requirement at the DTE will be 8-9 Watts thus requiring us toprovide 11-12 Watts from the switch or other supplying device.–Voltage should be a maximum of 45V d.c. (40V +/- 10% typical)–Current will be injected via the center taps using a Phantom Powermethod on the TX and RX pairs.–Magnetics will increase in height to accommodate the increase incurrent carrying capability.–The Bob Smith Termination will be changed to remove the d.c. pathbetween Magnetics center taps.–Discovery process will be resident in the PHY device.•
`
`Note that there is no change required to the PHY or the
`MAC in the Client DTE
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 3
`Juniper v ChriMar
`IPR2016-01397
`
`MDI Link Description
`

`

`DTE power over MDIBob Smith TerminationsMDI Link DescriptionLegacy terminationMDI powered termination
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 4
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Certain assumption have been made about various
`components of the link based upon both customer and
`vendor feedback.
`
`DTE power over MDIMDI Link Description•
`–Link using CAT3 or CAT5 cable will have loop impedance of up to30 Ohms.–Power requirement at the DTE will be 8-9 Watts thus requiring us toprovide 11-12 Watts from the switch or other supplying device.–Voltage should be a maximum of 45V d.c. (40V +/- 10% typical)–Current will be injected via the center taps using a Phantom Powermethod on the TX and RX pairs.–Magnetics will increase in height to accommodate the increase incurrent carrying capability.–The Bob Smith Termination will be changed to remove the d.c. pathbetween Magnetics center taps.–Discovery process will be resident in the PHY device.•
`
`Note that there is no change required to the PHY or the
`MAC in the Client DTE
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 5
`Juniper v ChriMar
`IPR2016-01397
`
`MDI Link Description
`

`

`DTE power over MDILevel One PHY Discovery ProcessLevel One PHY proposal
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 6
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`The schematic on previous page shows the circuit
`for this implementation.
`
`DTE power over MDILevel One PHY Discovery process•
`–As can be seen from the previous page this proposal uses aloop back between the TX and RX pairs.–There is a Low Pass Filter with a 25kHz pole placed in the loopback path in the DTE.–This filter will completely kill all data and link pulses.–There is no requirement for a relay as the filter will be a highimpedance to data under normal operating conditions.–Low frequency pulses are sent across the link which will passthrough the filter during the discovery process.–The amplitude of these recovered pulses allows us determinethe DTE type and make a decision on applying power or not.Level One PHY proposal
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 7
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Discovery Determination
`
`DTE power over MDI•
`–When a pulse is sent out the amplitude of the returned signalwill vary as follows;–In the case of a loop back cable (Type 1) or patch panel testplug. There is no attenuation of the transmitted pulse so aHIGH level pulse is returned.–In the case of a DTE requiring power the LPF will attenuate thepulse giving a MID level pulse on the return path.–In the case of a DTE not requiring power there would be nopulse returned as there is no loop back.–In the case of a DTE requiring power being connected to alegacy switch the normal data and link pulses would beattenuated by the LPF. No Link or data would be seen.•Preliminary lab testing shows that we would be able todetermine, with some margin, the type of DTE deviceon the link over the entire length of the link.Level One PHY proposal
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 8
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Improving the Robustness of the Discovery
`Process
`
`DTE power over MDI•
`–Each pulse would be Xusecs wide–The pulse would be sent a number of times, say 10.–Each of these pulses would be spaced Ymsec apart.–Each of these 10 pulses would have to give the same resultconsecutively at the receiver in order to produce a valid result.–Further each pulse would have to be received within specificwindow during the transmission time. This would allow us to besure that the result is a consequence of our test stimulus.–This bounding of the occurrence of the pulse will allow us toeliminate NLPs, FLPs, 10/100 data or idle from being mistakenas a DTE requiring power.Level One PHY proposalMid level PulseHigh Level Pulse XusecYmsecReceive Valid Window
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 9
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`MAC Control Interface Requirements
`
`•The MAC would control the discovery process via the MDIO/MDCinterface. A total of 3 register bits would be required to control thisfunction.–
`
`Enable Discovery Process
`
`Start/Restart Discovery Process
`
` - This register bit would enable ordisable the discovery process.–
` - This register bit wouldbegin the actual process. This bit should be auto-cleared whenthe process is complete.–
`
`DTE Discovered
`
`DTE power over MDI•
` - This register bit is set when a DTE requiringpower has been discovered. This bit should be auto-clearedwhen the Start/Restart Discovery Process bit is set.•This combination of bits will allow the MAC complete control overhow many times it wishes to run the discovery process. Oncesatisfied that the result is consistent the MAC can apply power tothe DTE.Level One PHY proposal
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 10
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Discovery Process relative to Link Determination
`
`DTE power over MDI•
`•The Discovery process is a separate process carriedout prior to Auto Negotiate or Parallel Detect.Level One PHY proposalAuto Negotiate Process complete ?DTE DiscoveryLink UP ?MAC Applies PowerBeginYESNOYESNODTE_Discovery_disabled + NLP_Received + 100M_PresentDTE_Discovery_enabled * DTE_DiscoveredUCT (Wait_Timer)
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 11
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`DTE power over MDIIEEE York proposalIEEE York proposal
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 12
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`DTE power over MDITrickle Current proposalTrickle Current proposal
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 13
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`The LOC PHY based discovery process has the
`following advantages over the previous proposals;
`
`DTE power over MDIConclusions•
`–Solves the corner cases that were an issue with the originalPHY based proposal.–Minimal changes to switch or DTE to allow PHY discoveryprocess.–Fastest time to market implementation. All technology wellunderstood.–Lowest cost implementation.•Eliminates the requirement for a relay in the DTE. $0.30•No requirement for isolated comparators or current sensingelements in the power supply. $0.65 ($0.95 if opto-isolated)–Least number of components reduces return loss and layoutissuesConclusions
`
`November, 1999
`
`IEEE Kauai
`
`Juniper Ex 1037-p. 14
`Juniper v ChriMar
`IPR2016-01397
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket