Task xx Scope Connector Pin Strand Purpose To

  • Slides: 26
Download presentation
Task xx Scope – Connector Pin Strand • • • Purpose – To re-look

Task xx Scope – Connector Pin Strand • • • Purpose – To re-look at this to see if it can be simplified Specifically –Includes – Excludes – none External Dependencies – none Assumptions – none Risks – none Revision #. # © 2017 Open Networking Foundation 1

Team Members • Leader - Members – ? ? ? Revision #. # ©

Team Members • Leader - Members – ? ? ? Revision #. # © 2017 Open Networking Foundation 2

 • IPR Declaration – Is there any IPR associated with this presentation NO

• IPR Declaration – Is there any IPR associated with this presentation NO • NOTICE: This contribution has been prepared to assist the ONF. This document is offered to the ONF as a basis for discussion and is not a binding proposal on Cisco or any other company. The requirements are subject to change in form and numerical value after more study. Cisco specifically reserves the right to add to, amend, or withdraw statements contained herein. • THE INFORMATION HEREIN IS PROVIDED “AS IS, ” WITHOUT ANY WARRANTIES OR REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION, WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Revision #. # © 2017 Open Networking Foundation

Physical vs Logical • On the physical side we have Connectors with ‘pins’ •

Physical vs Logical • On the physical side we have Connectors with ‘pins’ • Everything else is logical Revision #. # © 2017 Open Networking Foundation 4

Cablesets are a simple way to represent simple cables • We will define a

Cablesets are a simple way to represent simple cables • We will define a Simple. Cableset as a special case that 1. Has two identical ends 2. Each end uses all of the connector In a similar manner, a jumper wire would warrant a special solution Revision #. # © 2017 Open Networking Foundation 5

Copper pair / Fibre Strand etc. termination • • Option 1 A cable end

Copper pair / Fibre Strand etc. termination • • Option 1 A cable end may have a Connector or strand ends A piece of Equipment may have connectors A connector may connect to other connectors or terminate strand ends – we will call the first type a Plug. Socket. Connector and the second type a Termination. Connector A Plug. Socket. Connector has ‘pins’, a Termination. Connector has termination. Pins Cable strand. Ends are the equivalent of connector pins For copper pairs we may decide to fudge things a little and refer to a pair of pins as a pin and a pair of strand ends as a strand end If the connections are entirely 1 -1 then use the high level connections, else use the pinby-pin connections Revision #. # © 2017 Open Networking Foundation 6

Options Shown Pictorially Revision #. # © 2017 Open Networking Foundation 7

Options Shown Pictorially Revision #. # © 2017 Open Networking Foundation 7

Copper pair / Fibre Strand etc. termination with Ranges Option 2 • This allows

Copper pair / Fibre Strand etc. termination with Ranges Option 2 • This allows us to connect contiguous ranges which can reduce the number of instances required compared to pinby-pin interconnection • If the connections are entire 1 -1 then use the high level connections, else if there are useful contiguous range connections use the range option, else use the pin-by-pin connections • Note that Cable. End. Has. Connectors can only be used if the cable strand to connector pin mapping is not to be recorded (e. g. for pre-made standard cables) Revision #. # © 2017 Open Networking Foundation 8

Now use the item – range union datatype to simplify Option 3 • This

Now use the item – range union datatype to simplify Option 3 • This allows us to simplify the model by abstracting contiguous ranges and pin-by-pin interconnections • If the connections are entire 1 -1 then use the high level connections, else use the pin/range option • Note that if the terminations need to also be managed they should be converted from associations to classes (as was done in the TMF Outside Plant model). Revision #. # © 2017 Open Networking Foundation <<Union>> 9

Comparing the options with a contrived example Conn-A: 7 -9 to Conn-B: 1 -3

Comparing the options with a contrived example Conn-A: 7 -9 to Conn-B: 1 -3 plus Conn. A: 12 to Conn-B: 4 Option 1 Option 2 Option 3 Revision #. # © 2017 Open Networking Foundation 10 Option 3 has the class model simplicity of Option 1 with a similar instance efficiency to Option 2. Which model is the best depends on the situation. Option 1 degrades quickly for every case that’s not 1 -1 connectors. Option 2 is better than Option 3 if there are large numbers of individual pin connections.

How it compares to the TMF outside plant one Define a range owned by

How it compares to the TMF outside plant one Define a range owned by each end and then associate them m. TOP Outside Plant Submission Telstra-Cisco 1 -2. doc , written around 2007. Should be refactored as shown below. Define a termination that owns the ranges involved at each end. Then decorate the ranges onto the connectors. Revision #. # © 2017 Open Networking Foundation 11

Adopting a TMF outside plant style would invert the dependencies This model does allow

Adopting a TMF outside plant style would invert the dependencies This model does allow some nonsense options but also provides a lot more flexibility (such as one -many terminations). It also normalizes the self joins. The names here may be a bit wonky – are they ends or parts ? Revision #. # © 2017 Open Networking Foundation 12

Termination Example Revision #. # © 2017 Open Networking Foundation 13

Termination Example Revision #. # © 2017 Open Networking Foundation 13

Another option from the Storage work • With the definition of Termination, it is

Another option from the Storage work • With the definition of Termination, it is possible now to define an ‘internal termination range’ • Then just like with the Storage model, we don’t have to map the ranges on each side of the Termination, but can map them both to the internal Termination numbering • This is important for Storage where the mappings could be very complex and variable • For connector / pin / strand it is unclear if actual usage complexity would benefit from this approach or not (the number of range intersections vs the number of external ranges) Here we have 2 + 7 = 9 external ranges and 7 intersections. 7/(9/2) = 1. 6 – which seems like a useful metric Input Numbering 0 -7 Revision #. # © 2017 Open Networking Foundation 0 -7 Output Numbering 0 -19 Output Numbering 8 -15 16 -23 Output Internal Numbering 16 -23 … Input Internal Numbering … Input Numbering 14 0 -19 0 19 8 0 0 -7 16 8 -15 30 32 40 24 16 -23 8 -15 16 -23 49 … …

Adding (Logical) Signal These are ‘physical signals’ PHY such as can be seen with

Adding (Logical) Signal These are ‘physical signals’ PHY such as can be seen with an oscilloscope or similar measuring device Revision #. # © 2017 Open Networking Foundation 15 Note that the LTP is likely to be inside of a chip, not at a physical point on a connector – so there is a slight positioning mismatch between the LTP and the Signal. Ref. Point

Signal Example – RJ 14 The pink boxes are there to promote discussion on

Signal Example – RJ 14 The pink boxes are there to promote discussion on ‘what is a signal ? ’ – just define it and be consistent Red boxes are signal groups ? https: //en. wikipedia. org/wiki/Registered_jack#RJ 45 Revision #. # © 2017 Open Networking Foundation 16

Signal Spec • Obviously the previous example is madness. For standard signals – we

Signal Spec • Obviously the previous example is madness. For standard signals – we want only 1 additional instance per physical LTP ! • So let’s only do the detail work in the Spec layer for standard signals and connector allocations Revision #. # © 2017 Open Networking Foundation 17 Similar to LP, where Lp. Port is only in the Spec layer

https: //en. wikipedia. org/wiki/Modular_connector#8 P 8 C Signal Example – 100 TX Each box

https: //en. wikipedia. org/wiki/Modular_connector#8 P 8 C Signal Example – 100 TX Each box is a signal pin allocation Connector Definition TD = Transmit Data RD = Receive Data DA-DD = Bidirectional Data, signals A-D Signal Definition Revision #. # © 2017 Open Networking Foundation 18

This shows : • Many signals on a pin • Many signal groups on

This shows : • Many signals on a pin • Many signal groups on a connector • Many allocations on a connector Signal Example – RJ 14 Again Voice Trip + Voice Battery + could be combined if required Note the second POTs is additive without changing the first, so one model can do RJ 11, RJ 14 and RJ 25 Revision #. # © 2017 Open Networking Foundation 19

Signal Example Similar to the voice example we could show the power/DC signals separate

Signal Example Similar to the voice example we could show the power/DC signals separate or combined with the data signals For 1 G, we could define a Rx. Tx stream and use it 4 times (A-D) – do we have 1 or 4 PHY LTP ? The Signal definitions should be done together with the LTP PHY definitions https: //en. wikipedia. org/wiki/Power_over_Ethernet Revision #. # © 2017 Open Networking Foundation 20

Two Signal Models • The first model is for unique signal / connector /

Two Signal Models • The first model is for unique signal / connector / cable end combinations • The second is optimized for standard signal / connector arrangements • Now look at making the first model consistent with the second Revision #. # © 2017 Open Networking Foundation 21

Combined Logical Signal (Spec + Instance) Revision #. # © 2017 Open Networking Foundation

Combined Logical Signal (Spec + Instance) Revision #. # © 2017 Open Networking Foundation 22

Optical Fiber Connectors 100 M https: //en. wikipedia. org/wiki/Fast_Ethernet#100 BASE-FX Signal • This more

Optical Fiber Connectors 100 M https: //en. wikipedia. org/wiki/Fast_Ethernet#100 BASE-FX Signal • This more complex than the Ethernet twisted pair case where we only had 1 type of connector https: //commons. wikimedia. org/wiki/File: LC-optical-fiber-connector-hdr-0 a. jpg https: //en. wikipedia. org/wiki/Optical_fiber_connector Revision #. # © 2017 Open Networking Foundation 23

https: //en. wikipedia. org/wiki/100_Gigabit_Ethernet Optical Fiber Connectors 100 G Signal Lanes * Media =

https: //en. wikipedia. org/wiki/100_Gigabit_Ethernet Optical Fiber Connectors 100 G Signal Lanes * Media = Nr fibre strands Revision #. # © 2017 Open Networking Foundation 24

https: //en. wikipedia. org/wiki/100_Gigabit_Ethernet Optical Fiber Connectors 100 G Connector https: //en. wikipedia. org/wiki/Optical_fiber_connector

https: //en. wikipedia. org/wiki/100_Gigabit_Ethernet Optical Fiber Connectors 100 G Connector https: //en. wikipedia. org/wiki/Optical_fiber_connector http: //www. fiber-optical-networking. com/2865. html Signal MPO-24 “ 24 -fiber MPO connector for a high-speed fiber optic link” Each ‘pin’ is Tx or Rx (MPO-12 is 1 row only) https: //commons. wikimedia. org/wiki/File: MPO_Stecker_HR. jpg Revision #. # © 2017 Open Networking Foundation 25 Lanes * Media = 20 fibre strands

So which option to use for Optical signals ? • There is a lot

So which option to use for Optical signals ? • There is a lot of variation and less standardization • There may be a lot less quantities for a given SP or Enterprise, so scalability may be less of a concern • If the SP or Enterprise has large optical equipment variation and small numbers of each then the operational model may make sense • If the SP or Enterprise has few optical equipment variants and large numbers of each then the specification model may make sense. • Data center optical seems to be more standardized and the specification model is likely to be more appropriate there Revision #. # © 2017 Open Networking Foundation 26