Programmable form-factor pluggable controller

Abstract

The present subject matter relates to one or more devices, systems and / or methods. The disclosed Form-Factor Pluggable provides programmable connectivity for both applications and users to provision, monitor, and control non-ethernet serial and IoT targets remotely in real-time over existing optical ethernet infrastructure for low density use cases. The disclosed device is hot-pluggable, and all required DC power can be drawn from either the host ethernet network equipment receptacle or from the programmer, with no external power plug.

Description

PROGRAMMABLE FORM-FACTOR PLUGGABLE CONTROLLER

[0001] This invention relates to a programmable form-factor pluggable controller device that provides connectivity for both applications and users to provision, monitor, and control non-ethernet serial and IoT targets remotely in real-time over existing optical ethernet infrastructure.

[0002] Telecommunications and IoT networks worldwide are exponentially expanding over greater geographical distances while also rapidly increasing in both number of devices and device types. Governments, corporations, and individuals alike are all facing challenges related to this growing complexity.

[0003] The disclosed device mitigates this complexity by providing novel low density connectivity options for specialized applications and users to be able to provision, monitor, and control serial and IoT targets remotely in real-time over ethernet infrastructure. This increases productivity and efficiency for organizations and reduces their carbon footprint by reducing truck rolls.

[0004] Prior art US2014 / 0369214AI had reported a Small Form Factor SFP device that when inserted into a host ethernet network receptacle can collect the data from the serial console port of networking devices for later retrieval. The target network devices RS-232 serial console command line interface data would first be stored on a memory card in the pluggable device, that data would then be manually retrieved from the memory card via a remote terminal. Stored data logs would then be analyzed for the cause of network failures and field engineers would be dispatched to the site.

[0005] [PTL1]US2014／0369214AI

[0006] While the prior art, US2014 / 0369214AI, describes a small form-factor pluggable (SFP) device equipped with an RS-232 serial port it lacks key features. In comparison, the current invention presents a programmable form-factor pluggable control device that integrates multiple forms of serial communication along with IoT inputs and outputs. Incorporating multiple form factor and ethernet standards, real-time monitoring and control, API integration, Named Data Networking, and authentication and security mechanisms tailored to purpose.

[0007] To mitigate the sprawl and complexity of modern communication systems mentioned in the background, organizations often deploy equipment for ethernet to non-ethernet serial, and IoT communication for remote locations using optical ethernet infrastructure. Providing real-time secure control and monitoring in remote locations for switches, routers, servers, IoT devices, IoT sensors and more. Without this capability organizations are often forced to deploy truck rolls to remote locations or contract remote hands.

[0008] Existing industry solutions that allow for secure real time monitoring and control of non-ethernet serial and IoT communications are very bulky, require external power plugs, and in many cases require multiple devices. This makes high-density use cases such as large datacenters or large IoT clusters necessary to be practical. Remote low-density use cases are often not viable because these device’s oversized physical footprint, power management issues, and unmanageable cost.

[0009] This patent pertains to devices, systems, and their management. Below are the preliminary definitions and acronyms utilized in this disclosure. These definitions serve only to provide clear examples and illustrations for the reader's better comprehension. The definitions are not meant to limit the scope of the invention or alter the meaning of the acronyms or terminologies.

[0010] The Form-Factor Pluggable 100 of the present disclosure comprises of a housing, one variation of which is illustrated in FIG 1, others are described in Table 1, containing a printed circuit board (PCB) seen in FIG 10, 11, 12, and 13, containing a Management Interface 101, Monitoring Interface 102, Control Unit Interface 103, and a Network Interface 104 all illustrated in FIG 2.

[0011] The ethernet electrical receptacle of the existing optical ethernet Host Network Ethernet Device 106-b fits the housing and electrical pins fit the Form-Factor Pluggable 100 providing both ethernet connectivity and DC supply power.

[0012] The Network Interface 104 receives and transmits ethernet data and DC power from the Network Ethernet Device 106 electrical receptacle 106-b to the Control Unit Interface 103 where the ethernet communication is terminated. The Network Interface 104 will be configured accommodate on the 802.3 ethernet standard of the use case.

[0013] The Control Unit Interface 103 transmits, receives, and terminates the ethernet communication protocols listed in Table 1 to Network Interface 104. Where the web, console, and API functions enable ethernet connectivity to the non-ethernet serial, and IoT communication.

[0014] The Control Unit Interface 103 transmits, receives, and terminates non-ethernet serial, and IoT communication from the Management Interface 101, and Monitoring Interface 102. Where the web, console, and API functions enable non-ethernet serial, and IoT to ethernet communication.

[0015] The Monitoring Interface 102 transmits and receives data between the non-ethernet serial, and IoT devices and / or sensor to the Control Unit Interface 103. Various use case specific transceivers, resistors, and capacitors are necessary between the Control Unit Interface 103 and target device or sensor depending on the specific non-ethernet serial or IoT communication specification.

[0016] Management Interface 101 has several functions. First to transmit and receive data between the non-ethernet serial, and IoT device or sensors to the Control Unit Interface 103 Second to transmit and receive data between the programmer debugger to the Control Unit Interface 103.

[0017] FIG 3 and 5 shows the Programmer Debugger 105 which may provide DC supply power to the Form-Factor Pluggable 100 if it is removed from the Host Network Ethernet Device 106 for programming, reprogramming, debugging, and if installed in the Host Network Ethernet Device 106 electrical receptacle 106-b it can program, reprogram, debug, while then receiving its DC supply power from the Host Network Ethernet Device 106 via the Form-Factor Pluggable 100 Management Interface 101.

[0018] The disclosed Form-Factor Pluggable device 100 invention leverages the power and flexibility of modern microcontrollers that are programmed for specific limited use cases reducing the size footprint, cost, and power requirements. Combining customized software solutions and holistic circuit design, the device achieves novel functionality and resource optimization adhering to the size and power constraints of the form factors listed in Table 1 for optical ethernet infrastructure.

[0019] The introduction of the Management Interface 101 for the Form-Factor Pluggable 100 combined with the Programmer Debugger 105 enables the ability to program, debug, and update the device. The introduction of programming updates enables Named Data Networking NDN, current security protocols, and API functionality which were previously unavailable in this form factor.

[0020] The disclosed Form-Factor pluggable 100 invention provides a novel compact economical connectivity option for specialized applications and users to be able to provision, monitor, and control non-ethernet serial and IoT targets remotely in real-time over existing optical ethernet infrastructure where resources are limited. This increases productivity for organizations by reducing their carbon footprint by limiting travel requirements for initial provisioning and troubleshooting. Service management teams, and automated applications using Interactive Access and Management Devices 600 may remotely combine these functions together through the API providing improved incident response time, SLA success, versatility, security, ease of operation, OPEX, CAPEX, and a reduced carbon footprint via reduced truck rolls.

[0021] Example of an SFF-8432 compatible RJ45 SFP Form-Factor Pluggable illustration for disclosed deviceExample of a Form-Factor Pluggable interface block diagram of the disclosed deviceExample application of Form-Factor Pluggable to a programmer debugger for disclosed deviceExample application of Form-Factor Pluggable to a network device serial console port for disclosed deviceExample application of Form-Factor Pluggable to a serial console port and programmer debugger for disclosed deviceExample application of Form-Factor Pluggable to a server or PC serial console port for disclosed deviceExample application of Form-Factor Pluggable to multi-port mux to various serial console ports for disclosed deviceExample application of Form-Factor Pluggable to IoT control device for disclosed deviceExample application of Form-Factor Pluggable connected directly to IoT inputs and outputs for disclosed deviceExample of Form-Factor Pluggable PCB block diagram of RJ45 serial for disclosed deviceExample of Form-Factor Pluggable PCB block diagram of RJ45 serial and USB for disclosed deviceExample of Form-Factor Pluggable PCB block diagram of USB-C, custom cable, or direct IoT in / out for disclosed deviceExample of Form-Factor Pluggable PCB block diagram of USB-C, custom cable, or direct IoT in / out with serial for disclosed device

[0022] The following passage includes specific details provided as examples to help readers understand the disclosed method(s), system(s), and device(s) thoroughly. Skilled professionals may realize that the disclosed information can still be implemented without these details. Some commonly known procedures, components, hardware, and circuitry are mentioned briefly to avoid making the disclosure unnecessarily complicated. The examples used in this description refer to Form-Factor Pluggable devices 100, methods, and systems. However, it is important to note that the disclosed method(s), system(s), and device(s) can be used in any context where its connectivity services are necessary or desired.

[0023] The disclosed Form-Factor Pluggable device 100, is not limited to, but leverages open standards from the following bodies. Institute of International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), Internet Engineering Task Force(IETF), Electrical and Electronics Engineers (IEEE), National Institute of Standards and Technology (NIST), Federal Information Processing Standards (FIPS), Storage Networking Industry Association (SNIA), Telecommunications Industry Association(TIA), USB Implementers Forum (USB-IF), Small Form Factor (SFF), and various other Multi Source Agreement (MSA) Committees. This ensures high levels of interoperability, and supply chain efficiency.

[0024] The disclosed Form-Factor Pluggable device 100 may be compatible with the Host Network Ethernet Device 106 electrical receptacle 106-b ports which are standardized by, but not limited to, the following organizations, the Institute of Electrical and Electronics Engineers (IEEE), Storage Networking Industry Association (SNIA), Small Form Factor (SFF), and various other Multi Source Agreement (MSA) Committees that define the mechanical, electrical, register, and software specifications. See Table 1.

[0025] The disclosed Form-Factor Pluggable device 100 may be physically compatible with, but not limited to, the following Host Network Ethernet Device 106 electrical receptacle 106-b standards SFP / + / 10 / 28 / 56 / 112, XFP, QSFP / + / 10 / 28 / 56 / DD, CFP / 2 / 4 / 8, OSFP-SR / LR / FR / DR / ZR / ER and other affiliated standards listed in TABLE 1 along with any other future similar ethernet networking industry form-factor pluggable related standard.

[0026] The disclosed Form-Factor Pluggable device 100 PCB shown in FIG 10, 11, 12, and 13 foundational components may include one or more of the following DC Power Regulator, MCU or MPU, MAC, MUX, ETH PHY, USB PHY, EPROM, and serial transceiver along with supporting components. The block diagrams found in FIG 10, 11, 12, and 13 are to promote the readers comprehension and are not meant to limit the scope of the invention by any means or alter the meaning of acronyms or terminologies by any means.

[0027] The disclosed Form-Factor Pluggable device 100 standards bodies used to define serial communication include, but are not limited to, the Electronics Industry Alliance (EIA) which was later adopted by the Telecommunications Industry Association (TIA), and the USB Implementers Forum (USB-IF). The TIA-232 / 422 / 485 standards were initially identified by the prefix "RS" (Recommended Standard), but the prefix was later changed to "EIA" and "TIA" to reflect the organizations responsible for maintaining the standards.

[0028] The disclosed Form-Factor Pluggable device 100 Management Interface 101 and Monitoring Interface 102 serial communications may include, but are not limited to, TIA-232 / 422 / 485, UART, USART, SPI, CAN, JTAG, SWD, Modbus, BACnet, I2C, I3C and USB 1.0 / 1.1 / 2.0 / 3.0 / 3.1 / 3.2 / 4 standards. These protocols may operate utilizing both open source and proprietary methods and will evolve with future revisions.

[0029] The disclosed Form-Factor Pluggable device 100 Monitoring Interface 102 GPIO General-Purpose Input Output functions may include, but are not limited to, general-purpose digital input, general-purpose digital output, interrupt input, analog input, PWM (Pulse Width Modulation) output, and port multiplexing.

[0030] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 is programmed to optimize the clock speed, memory usage, and peripheral power resources. The memory is used to store the limited software and data for the desired for each specific use case. The peripheral is used to connect the microcontroller to the specific external use case inputs or outputs. This information is then aggregated to top optimize the overall circuit design to fit the size and power constraints of the form factor combinations listed in Table 1.

[0031] The disclosed Form-Factor Pluggable device 100 is accessed, remotely controlled, and monitored by Interactive Access and Management Devices 600 which may consist of, but are not limited to, the following equipment and systems. Servers, desktop and laptop computers, IoT devices, and cloud clusters for service management as well as artificial intelligence and machine learning. This access can be manual for the user via reverse telnet or SSH, and through automation, via API for example. The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 may utilize, but is not limited to, Named Defined Networking (NDN), also referred to as content-based networking, data-oriented networking, or information-centric networking for ethernet communication that is compatible with the standards listened in table 1.

[0032] This table1 is a Form-Factor standard reference and is not meant to limit the scope of the invention by any means or alter the meaning of acronyms or terminologies by any means.

[0033] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 may utilize, but is not limited by, the following programming languages: Assembly Language, C, Rust, Ada, C++, MicroPython, Python, Mojo, Fortran, D, Chapel, Nim, Swift, Go, MATLAB, Julia, Lua, Kotlin, Haskell, Scheme, Elixir, and Crystal. The programming languages mentioned above allow the microcontroller to target specific use cases, optimizing processor utilization, minimizing memory requirements, and managing power consumption efficiently. These languages may operate utilizing both open source and proprietary methods and will evolve with future revisions.

[0034] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 may utilize, but is not limited by, the following operating systems FreeRTOS, Zephyr, RIOT, TinyOS, Contiki, ChibiOS, NuttX, Mbed OS, Embedded Xinu, micro-C / OS-II, TinyOS 2, eCos, Fuchsia, RTEMS, ChibiOS / RT, LiteOS, HelenOS, PicoOS, micro-Clinux, and L4Microkernel. The operating systems mentioned above allow the microcontroller to target specific use cases, optimizing processor utilization, minimizing memory requirements, and managing power consumption efficiently. These operating systems may operate utilizing both open source and proprietary methods and will evolve with future revisions.

[0035] The disclosed Form-Factor Pluggable device 100 communications and security features may be standardized by, but not limited to, the Internet Engineering Task Force (IETF), International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), National Institute of Standards and Technology (NIST), and Federal Information Processing Standards (FIPS).

[0036] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 may provide, but is not limited by, the following security protocols and encryption support with TLS, HTTPS, AES, HMAC, RSA, SHA, SNMP (Simple Network Management Protocol), and SSH. These protocols may operate utilizing both open source and proprietary methods and will evolve with future revisions.

[0037] The disclosed Form-Factor Pluggable device 100 will draw its required power from either the Host Network Ethernet Device 106 electrical receptacle 106-b via the Network Interface 104, or via the Management Interface 101 from the Programmer Debugger 105. No external power plug is required. The disclosed Form-Factor Pluggable device 100 Programmer Debugger 105 will be capable of initial programming, re-programming, and debugging the Control Unit Interface 103 through the Management Interface 101.

[0038] The disclosed Form-Factor Pluggable device 100 may provide supply power to IoT Devices 500 via Management Interface 101.

[0039] The disclosed Form-Factor Pluggable device 100 is hot-pluggable which means that it can be inserted or removed from a compatible network device, such as a switch or router, while the device is still powered on and operational. This allows for easy and flexible installation, maintenance, and upgrades without the need for downtime or disrupting the network. The hot pluggable feature is possible due to the design of the interface, which includes features such as automatic detection and configuration of the module by the Host Network Ethernet Device 106 when the Form-Factor Pluggable device 100 is connected to the electrical receptacle 106-b.

[0040] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 operational modes may include, but are not limited to, SSH, Reverse SSH, Telnet, Reverse Telnet, TCP, Secure TCP Server, Secure TCP Client, UDP, and Disabled mode. Along with any future updated standards or any similar proprietary functions.

[0041] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 may be compatible with, but is not limited to, Local Server, TACACS+, and FreeRADIUS authentication methods. These authentication methods operate utilizing both open source and proprietary methods and will evolve with future revisions.

[0042] The disclosed Form-Factor Pluggable device 100 Control Unit Interface 103 may support a wide range of virtual interfaces including but not limited to web, console Telnet / SSH, and API.

[0043] The disclosed Form-Factor Pluggable device 100 Management Interface 101 and Monitoring Interface 102 entry-exit physical exterior connector may include, but is not limited to, the following standards for physical connectors RJ45, USB A / B / Mini / Micro / C, RJ45 to DB-9 adapters, along with terminators, and resistors to meet various serial electrical standards. The RJ45 connector version, for many common use cases, a standard TIA-568B patch cable may connect a network device Form-Factor port to a serial device console port allowing for simple installation. Using open standards for physical connectors provides interoperability and efficiency. FIG 1 shows only an external casing with an example RJ45 serial connector, however disclosed Form-Factor Pluggable device 100 may also utilize the form factors listed above, and any other relevant future serial electrical connector standards.

[0044] The disclosed Form-Factor Pluggable 100 devices Network Interface 104 may support and 802.3 IEEE standardized electrical system-side ethernet network interfaces such as those listed in TABLE 1.

[0045] The following practical use case scenario descriptions are to promote the readers comprehension and are not meant to limit the scope of the invention by any means or alter the meaning of acronyms or terminologies by any means.

[0046] Scenario 1 is illustrated in FIG 3 using the PCB configurations listed in FIG 10, 11, 12, and 13 when the Form-Factor Pluggable 100 is connected to the Programmer Debugger 105 via the Management Interface 101 to program, reprogram, and debug the Control Unit Interface 103. This enables security features and APIs to stay current and viable through updates. If the Form-Factor Pluggable 100 is removed from the Host Network Ethernet Device 106 the Programmer Debugger 105 provides DC supply voltage for programming functions.

[0047] Scenario 2 is illustrated in FIG 4, 5, 6, & 7 using the PCB configurations listed in FIG 10, 11, and 13 when deploying new equipment such as servers and ethernet networking devices to remote datacenters or on customer premises that require initial provisioning. The Form-Factor Pluggable 100 is hot-pluggable which allows for easy and flexible installation without the need for downtime or disrupting a network. A Host Network Ethernet Device 106 with a Form-Factor Pluggable 100 device installed in 106-b can be deployed with minimal configuration along with any additional Network Ethernet Devices 200, Servers 300, or industrial devices. This allows technicians and remote hands with specialized training to perform the installation easily. Specialized network engineers and server administrators, for example, can connect remotely from Interactive Access and Management Devices 600 eliminating the need for remote location travel. This will free up the time of key personnel and reduce carbon footprint via reduced truck rolls.

[0048] Scenario 3 is illustrated in FIG 4, 5, 6, & 7 using the PCB configurations listed in FIG 10, 11, and 13 when remotely monitoring and controlling a server or ethernet networking device in real-time via the serial console port. Remote connection is established by the application or user from Interactive Access and Management Devices 600 through the Form-Factor Pluggable 100 via reverse telnet, or reverse SSH to the serial console port of a Network Ethernet Device 106-a, 200-a, Server 300a, or industrial device. In many similar scenarios the physical connection from the Management Interface 101 and the Monitoring Interface 102 to the serial console port of a connected device would be a common TIA-568B strait through cat5e patch cable, other physical connector and conductor variations are also possible. This connection allows the Control Unit Interface 103 to communicate with the serial console command line interface of the targeted device. Service management applications and users may remotely connect to the Form-Factor Pluggable 100 Control Unit Interface 103 allowing FreeRadius, TACACS+, or local server authentication while also performing automated and manual functions via API. Service management teams, and automated applications using Interactive Access and Management Devices 600 may remotely combine these functions together providing improved incident response time, SLA success, versatility, security, ease of operation, OPEX, CAPEX, and a reduced carbon footprint via reduced truck rolls.

[0049] Scenario 4 is illustrated in FIG 5 using the PCB configurations listed in FIG 10, 11, and 13 when a serial device and a programmer debugger both operate simultaneously. The Management Interface 101 and the Monitoring Interface 102 share a physical entry-exit point from the Form-Factor Pluggable 100 which may use an RJ45, USB-C, or a custom cable. The Form-Factor Pluggable 100 is installed in the Host Network Ethernet Device 106 and is connected to the Programmer Debugger 105 via the Management Interface 101 to program, reprogram, and debug while the Monitoring Interface 102 is simultaneously connected to with a Host Network Ethernet Device 200, Server 300, or industrial device through its serial console port providing the same functionality as in Scenario 3. This configuration provides dual functionality and real time debugging capability.

[0050] Scenario 5 is illustrated in FIG 7 using the PCB configurations listed in FIG 11 and 13 when remotely monitoring and controlling multiple servers and / or ethernet networking devices in real-time via serial console ports. All aspects of the system operation and the functional benefits are the same as in Scenario 3 except for the number of additional available serial ports. The Form-Factor Pluggable 100 connects using both serial and USB protocols to the Serial MUX 400, which receives its DC Power supply from the Management Interface 101. The Control Unit Interface 103 uses USB protocol via the Management Interface 101 to control the Serial MUX 400 connecting the Monitoring Interface 102 serial output to target devices serial consoles. Allowing for one Form-Factor Pluggable 100 to provide remote monitoring and control for multiple Network Ethernet Devices 106-a, 200-a, Servers 300a, or industrial devices via the serial console.

[0051] Scenario 6 is illustrated in FIG 8 using the PCB configurations listed in FIG 11, 12, and 13 when remotely monitoring and controlling IoT devices in datacenters, customer premises, and industrial locations. The IoT Device 500 remotely connects the application or user of Interactive Access and Management Devices 600 through the Form-Factor Pluggable 100. The Control Unit Interface 103 uses USB protocol via the Management Interface 101 to communicate with, and supply DC power to, the IoT Device 500. USB communications are limited to approximately 5 meters via copper cabling, and 300 meters via fiber, however most IoT inputs and outputs have a range of approximately 500-1000 meters from the input or output terminal. Thermistors, air quality sensors, humidity sensors, contacts, 0-10V, 4-20ma inputs and outputs and more can be supported. Service Management applications and users may remotely connect to the Form-Factor Pluggable 100 Control Unit Interface 103 making FreeRadius, TACACS+, or local server authentication possible while also performing automated and manual functions via API. Service management teams, and automated applications using Interactive Access and Management Devices 600 may remotely combine these functions together providing improved incident response time, SLA success, versatility, security, ease of operation, OPEX, CAPEX, and a reduced carbon footprint via reduced truck rolls.

[0052] Scenario 7 is illustrated in FIG 8 using the PCB configurations listed in FIG 10, 11, and 13 when remotely monitoring and controlling IoT devices in datacenters, on customer premises, and in industrial settings. The Modbus IoT Device 500 remotely connects the application or user of Interactive Access and Management Devices 600 through the Form-Factor Pluggable 100. The Control Unit Interface 103 utilizes the Modbus protocol via the Monitoring Interface 102 to communicate with the Modbus IoT Device 500. This example is not limited to the Modbus protocol, it is used as a reference due to its popularity, other protocols such as BACnet, and CAN are interchangeable for this scenario. IoT management applications and users may remotely connect to the Form-Factor Pluggable 100 Control Unit Interface 103 making FreeRadius, TACACS+, or local server authentication possible while also performing automated and manual functions via API. IoT system administrators using Interactive Access and Management Devices 600 may remotely combine these functions together with automation based on aggregated data providing improved incident response time, versatility, security, ease of operation, OPEX, and CAPEX.

[0053] Scenario 8 is illustrated in FIG 9 using the PCB configurations listed in FIG 12 and 13 when remotely monitoring and controlling IoT sensors, contacts, inputs, and output in datacenters and on customer premises. All aspects of the system operation and the functional benefits are the same as in Scenario 6 except that the IoT inputs and outputs are connected directly to the Form-Factor Pluggable 100. Thermistors, air quality sensors, humidity sensors, contacts, 4-20ma inputs and outputs and more may be supported. If the temperature is too high, or a rack door opens, or the power fails it could send a notification to a user or application. This configuration is less costly but has fewer inputs and outputs than possible in Scenario 6.

[0054] While certain features of the described implementations are illustrated as described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the scope of the embodiments.

[0055] Acronym Definitions used in this application specification are as follows AES: Advanced Encryption Standard API: Application Programming Interface BACnet: Building Automation and Control Network CAN: Controller Area Network CAPEX: Capital expenditure CFP: C Form-Factor Pluggable EIA: Electronic Industries Alliance EEPROM: Electrically Erasable Read-Only Memory FIPS: Federal Information Processing Standards HMAC: Hash-based Message Authentication Code HTTPS: Hypertext Transfer Protocol Secure I2C: Inter-Integrated Circuit IEC: International Electrotechnical Commission IEEE: Institute of Electrical and Electronics Engineers IETF: Internet Engineering Task Force IoT: The Internet of Things ISO: International Organization for Standardization JTAG: Joint Test Action Group LAN: Local Area Network MAC: Media Access Control Mbps: Megabits per second MCU: Microcontroller Unit MII: Media Independent Interface MPU: Micro Processing Unit MSA: Multisource agreement NDN: Named Data Networking NIST: National Institute of Standards and Technology OPEX: Operational expenditure OSFP: Octal Small Form-factor Pluggable PCB: Printed Circuit Board PHY: Physical interface QSFP: Quad Small Form-Factor Pluggable RADIUS: Remote Authentication Dial-In User Service RGMII: Reduced Gigabit Media Independent Interface RSA: Rivest-Shamir-Adleman SFF: Small Form Factor SFP: Small Form factor Pluggable SGMII: Serial Gigabit Media Independent Interface SHA: Secure Hash Algorithm SLA: Service Level Agreement SNIA: Storage Networking Industry Association SNMP: Simple Network Management Protocol SPI: Serial Peripheral Interface SSH: Secure Shell is a protocol SWD: Serial Wire Debug TACACS+: Terminal Access Controller Access-Control System Plus TCP: Transmission Control Protocol TIA: Telecommunications Industry Association TLS: Transport Layer Security UDP: User Datagram Protocol USB: Universal Serial Bus WAN: Wide Area Network XFP: Form factor Pluggable XGMII: 10 Gigabit Media Independent Interface

Claims

1. A form-factor pluggable device that provides real-time and programmable ethernet connectivity allowing for the remote control and monitoring of non-ethernet serial and IoT devices, as well as IoT sensors by both users and applications. Wherein; The disclosed form-factor pluggable device includes a control unit interface, a network interface, monitoring interface, and management interface. The ethernet interface connects the control unit interface to the host ethernet network equipment's Form-Factor Pluggable receptacle. The monitoring interface connects the control unit interface to connected serial and IoT devices or sensors. The management interface allows for the connection of a programmer to provide initial programming, debugging, and system updates for the control unit interface, also to connect USB devices, and may either provide DC power to, or receive DC power from its connected devices. The programable control unit interface provides the processing capabilities to allow connectivity between the ethernet interface, monitoring interface, and the management interface.

2. The form-factor pluggable control unit interface, as in claim 1, may provide the following security protocols and encryption support with TLS, HTTPS, AES, HMAC, RSA, SHA, SNMP, and SSH. Along with any future updated similar standards or any future updated similar proprietary functions.

3. The form-factor pluggable device may support, but is not limited to local server, TACACS+, and FreeRADIUS authentication methods.

4. The form-factor pluggable control unit interface, as in claim 1, may support, but is not limited to one or more of the following virtual interfaces including web, console via Telnet / SSH, and API.

5. The form-factor pluggable control unit interfaces, as in claim 1, may support, but is not limited to, remote monitoring and control capabilities for both manual users and automated applications or systems.

6. The form-factor pluggable device as in claim 1 may draw power from either the network interface via the host network ethernet device receptacle, or the management interface via the programmer debugger, no external power source is required during normal operation or programming.

7. The form-factor pluggable management interface, as in claim 1, may provide DC power for a connected device such as an IoT Device, or Serial MUX.

8. The form-factor pluggable control unit interface, as in claim 1, non-ethernet serial communication operational modes may include, but are not limited to SSH, Reverse SSH, Telnet, Reverse Telnet, TCP, TCP Server, TCP Client, and UDP.

9. The form-factor pluggable, as in claim 1, may support Named Data Networking (NDN), also referred to as content-based networking, data-oriented networking, or information-centric networking for ethernet communication.

Images