Vending machine for transceivers

Abstract

Embodiments generally relate to a housing, comprising storage for one or more vendable items, wherein the housing is configured to selectively vend one or more vendable items; a controller, within the housing, comprising a processor in connection with a memory; a user interface in communication with the controller, configured to allow a user to selectively vend the one or more vendable items; a programming module, within the housing in connection with the processor, wherein the programming module is configured to communicatively connect to the one or more vendable items when dispensed; and wherein the controller is configured to upload program code to the one or more vendable items through the programming module.

Description

[0001] VENDING MACHINE FOR TRANSCEIVERS

[0002] Technical field

[0003] The field of the disclosure generally relates to vending machine for transceivers.

[0004] Background

[0005] In data centre environments, a lack of easy access to non-programmed transceivers can be challenging, and can result in loss of productivity - particularly if current data centre supplies are low, or if suppliers for the aforementioned transceivers are closed or out of supply. Furthermore, datacentre work requires lots of travel for transceiver suppliers. Accordingly, due to the travel demands of supplying multiple datacentres, it can be common for customers to lose, misplace, or forget inventory; including both transceivers and the tools to program them to work with a vendor’s hardware. Typical issues in the supply of transceivers to data centres can impact productivity, especially if inventory needs to be ordered internationally. Accordingly, it is desired to ameliorate or address one or more issues associated with supply and programming of transceivers in data centres, or at least provide a useful alternative thereto.

[0006] Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

[0007] Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present disclosure as it existed before the priority date of each of the appended claims.

[0008] Summary

[0009] Some embodiments relate to a system comprising: a housing, comprising storage for one or more vendable items, wherein the housing is configured to selectively vend one or more vendable items; a controller, within the housing, comprising a processor in connection with a memory; a user interface in communication with the controller, configured to allow a user to selectively vend the one or more vendable items; a programming module, within the housing in connection with the processor, wherein the programming module is configured to communicatively connect to the one or more vendable items when dispensed; and wherein the controller is configured to upload program code to the one or more vendable items through the programming module. The system may further comprise a dispensing elevator within the housing, configured to convey the one or more vendable items between a storage location and a dispenser. The user interface may further comprise a card reader, and is configured to allow card payment from a user. The one or more vendable items may comprise one or more transceivers. The one or more transceivers may comprise optical transceivers.

[0010] Some embodiments relate to a method comprising: determining one or more items to be selected for vending from a vending machine; responsive to determining one or more items for vending, determining whether the one or more items are in stock within the vending machine; determining a payment associated with vending the one or more items; responsive to determining whether the one or more items are in stock and the payment associated with the one or more items, vending the one or more items form the vending machine; determining a coding type for the one or more items; and uploading program code, related to the coding type, to the one or more items by connection with the vending machine.

[0011] The one or more items may be transceivers. The transceivers may be optical transceivers.

[0012] Brief description of drawings

[0013] Fig.1 is a diagram of a vending machine for transceivers, according to some embodiments;

[0014] Fig.2 is a flow chart of a method of operating a vending machine for transceivers, according to some embodiments;

[0015] Fig.3A is an example user interface screen, displaying an initial option screen, according to some embodiments;

[0016] Fig.3B is further example user interface screen, displaying a module detection button, according to some embodiments;

[0017] Fig.3C is a further example user interface screen, displaying an initial programming screen, according to some embodiments;

[0018] Fig.3D is a further example user interface screen, displaying a transceiver programming selection menu, according to some embodiments; and

[0019] Fig.3E is a further example user interface screen, displaying a return screen, according to some embodiments.

[0020] Detailed description Embodiments of the disclosure relate to vending machines for transceivers. In particular, a vending machine configured to dispense non-programmed transceivers is provided, allowing a user to select a desired transceiver, pay for it at the machine, and have it dispensed ready for use. In data centre environments, easy access to new transceivers is beneficial. However, existing solutions require delivery of transceivers or retrieval of transceivers from storage, and for a user to separately configure the new transceiver, thereby disrupting productivity and workflow of data centre workers. Moreover, the requirement for separate programming boxes can lead to loss or misuse of the boxes. The disclosed embodiments aim to address this by providing a vending machine with an integrated programming port, configured to upload program code to transceivers (such as optical transceivers), and prepare them ready for use with a simple and easy to use process. In some embodiments, the stored transceivers may include SFP / SFP+, QSFP+, QSFP28, QSFP-DD, CFP, CFP2, OSFP, or other similar transceivers. Accordingly, the vending machine may contain code suitable to program these transceivers through the programming port.

[0021] Fig.1 depicts an embodiment of a vending machine for transceivers 100. The vending machine 100 comprises a housing 105, configured to store one or more vendable items (such as transceivers 115) in a storage area 110.

[0022] The storage area 110 may be provided in connection with a dispensing means 150. Dispensing means 150 may be an elevator or conveyor, configured to move a product 115 to a vending bay 155 without risking damage to the vendable items 115. Vending bay 155 may comprise a compartment within the housing 105 that is selectively openable subject to a completed transaction, allowing a user to reach into the bay 155 to retrieve a vended transceiver 115. It will be appreciated that dispensing means other than elevators or conveyors may be provided. For example, in some embodiments, a rotating ring dispenser system may be used. The arrangement and connection of vending means 150 and bending bay 155 may be configured to allow smooth and gentle conveyance of transceivers 115, to avoid undue damage to them when being vended. Dispensing means 150 and vending bay 155 may be in communication with control 120, allowing for control over their operation according to program code stored within memory 130.

[0023] Vending bay 155 may further comprise an access hatch 156, configured to prevent a user reaching into the bay 155 until it is opened. The access hatch 156 may comprise an airlock style hatch. Access hatch may 156 be a pivotable hatch, affixed to the housing 105 at one end by a motor configured to activate to open the hatch upon confirmation of a successful purchase. In some embodiments, vending bay 155 may comprise a product sensor 157 configured to determine whether a vended item has arrived in the bay 155. The product sensor 157 may comprise a load cell. Product sensor 157 may comprise a barcode scanner, such as a QR code reader for example. Product sensor may be configured to determine product data such as weight, height, dimensions, or a bar code of a vended item in the bay 155, and to provide the product data to the controller 120 to be stored in the memory 130. Product data may be used to determine whether an item has successfully been vended and / or collected.

[0024] Housing 105 may comprise a rigid body suitable to house the components of vending machine system 100. Housing 105 may further comprise apertures configured to mount and / or provide access to user interface 140, programming module 145, and payment interface 146. In some embodiments, any or all of the user interface 140, programming module 145, and payment interface 146 may be integrally formed into the housing. In such embodiments, the direct integration of the user interface 140, programming module 145, and payment interface 146 may improve resilience of these components to wear and tear associated with use of the vending machine. This may be particularly beneficial in the case of the programming module 145 which typically sees a high degree of interaction with users, as they insert and remove transceivers purchased from the vending machine 100 for subsequent programming. In some embodiments, the programming module 145 may be removable from within the housing 105 In such embodiments, the housing 105 may have access hatches, ports, or other opening means that allow ease of access to the programming module 145. In still other embodiments, the programming module 145 may comprise a separate programming interface housing 147 - which is configured to removably affix the programming module 145 to the housing 105. Accordingly, the programming interface housing 147 may be easily removed housing 105 for replacement of the programming module 145. In such embodiments, the ease of removal of the programming module 145 can allow for improved servicing of the vending machine 100 due to the frequent use of the programming module 145, or to allow for maintenance or upgrade of the programming module 145.

[0025] Controller 120 may comprise a processor 125 in communication with memory 130, and be configured to allow for operation of the vending machine 100. Memory 130 may further comprise a code library 135, containing stored data related to transceiver code for upload to dispensed transceivers through programming module 145. Programming module 145 may comprise a transceiver adapter or other device programming module, housed within the housing 105, and having a communication port (such as a USB port for example) to facilitate communication with a dispensed transceiver. The port of the programming module 145 may be accessible from the exterior of the housing 100. programming module 145 may further comprise a tuning box, depending on the requirements of the housed transceivers.

[0026] In existing solutions, operating system specific software is used to program transceivers. This is typically a Microsoft™ Windows based application for use with Windows compatible devices such as personal computers, capable of connecting to a transceiver by a host adapter (such as an Aardvark I2C / SPI Host Adapter for example). This reliance on operating system specific software and hardware limits the functionality of programming transceivers. Accordingly, some embodiments of the present disclosure may utilise custom developed programming software stored in code library 135, configured to allow users to program transceivers from touchscreen devices (such as tablets or smartphones for example) when used as a user interface 140. Touch-screen devices utilised in the present disclosure may be compatible with host adapter hardware, configured to allow direct connection to a vended transceiver. Requirements and considerations of touch-screen based transceiver programming applications are outlined below:

[0027] Core functionality requirements

[0028] • Detect when a fibre optic transceiver is inserted into the programming hardware;

[0029] • Read and identify the transceiver type and specifications

[0030] • Present user with appropriate vendor and transceiver type options based on detection

[0031] • Allow user selection from dropdown menus for vendor and transceiver type

[0032] • Handle locked EEPROM scenarios with appropriate unlock codes

[0033] • Program the transceiver with the selected EEPROM image

[0034] • Verify successful programming

[0035] • Display programming status and results

[0036] Technical requirements

[0037] • - Target Device: tablets / devices with touchscreen capability

[0038] • - Programming Hardware: I2C / SPI Host Adapter via USB connection

[0039] • - USB Connection: Application must interface with the programming hardware via USB using Android's USB Host API

[0040] User interface requirements

[0041] • Intuitive touchscreen interface optimized for tablet use

[0042] • Clear workflow: detect — > select vendor — > select type — > program

[0043] • Visual indicators for connection status, detection process, and programming status

[0044] • Error handling with user-friendly messages

[0045] • Simple navigation and minimal learning curve In some embodiments, code library 135 contains program code which, when executed, allows for extension of the application to connect to a cloud-based backend that can dynamically generate EEPROM code based on the detected transceiver, while maintaining offline functionality for static EEPROM files. In such embodiments, the requirements of the program code stored in code library 135 are outlined below.

[0046] Cloud Backend

[0047] • Secure API backend

[0048] • Capability to dynamically generate EEPROM images based on transceiver type and serial number

[0049] • Must fully replicate the generation logic discovered from reverse engineering the Smart Optics application

[0050] • Support all vendor-specific algorithms for EEPROM generation

[0051] • Storage and management of EEPROM unlock codes for locked transceivers

[0052] • System to generate or retrieve unlock codes as needed for specific transceiver types

[0053] • User authentication and authorization

[0054] • Secure storage of EEPROM templates and generation algorithms

[0055] • Logging and auditing of programming operations

[0056] Extended Application Functionality

[0057] • Cloud synchronization for latest EEPROM images and templates

[0058] • Offline functionality for static EEPROM files

[0059] • Dynamic EEPROM generation for transceivers requiring serial number-specific programming

[0060] • User account management

[0061] • Usage analytics and reporting

[0062] Security Requirements

[0063] • Secure communication between app and cloud backend (TLS / SSL)

[0064] • Secure storage of credentials and sensitive data

[0065] • Protection of proprietary EEPROM data and generation algorithms

[0066] • Role-based access control

[0067] Hardware Integration

[0068] • Application must be capable of being integrated with external hardware via USB

[0069] • Define communication interface between the application and any connected hardware systems

[0070] • Support for automated operations in an industrial context It will be understood that programs used in the facilitation of a touch screen embodiment of the user interface 140 may be compatible with typical touch screen devices such as Android™ compatible tablets or Apple™ products and their operating systems (such as the iOS operating system for example).

[0071] User interface 140 may comprise a keyboard, touchscreen, numpad, or any combination thereof, configured to allow operation of the vending machine 100. The user interface 140 may allow for selection of a transceiver type from within the storage area 110, and may prompt a user to select a payment method and / or present payment information, and other prompts to guide a user through the process of purchasing, vending, and programming a transceiver 115. Accordingly, interface 140 may comprise a POS (point of sale) system. User interface 140 may allow for a user to select a type of transceiver for programming, or a desired programming type. The controller 120 receives the request from the user interface 140, and transmits code from the code library 135 to a transceiver 115 connected to the programming module, responsive to a user request.

[0072] Payment interface 146 may comprise a card reader, NFC communication interface, and / or cash collection means, configured to receive a payment from a user to allow for purchase of a transceiver 115. Payment interface 146 may be in connection with the controller 120.

[0073] The vending machine 100 may be connected to the internet, or a network 160, allowing data to be sent and received to the vending machine to allow for operational software updates, and / or the collection of sales data. In some embodiments, the control 120 may issue alerts over network 160. The alerts may relate to stock supplies, unauthorised entry attempts, faults, or other relevant data.

[0074] Fig.2 depicts a flow chart of a process 200 of the operation of the vending machine 100 according to some embodiments. At stage 205, the process 200 begins, with initialisation of the vending machine 100. At this stage, user interface 140 may display screen 300, prompting a user to make a selection between purchasing optics with button 302 or programming optics with button 304.

[0075] At stage 210, a user interacts with user interface 140 to select a transceiver 115 from the vending machine 100. This may comprise interacting with a touchscreen or numpad. At stage 215, upon receiving the input form user interface 140, the processor 125 queries the memory 130, to determine with the desired transceiver is in stock. Memory 130 may be configured to store stock levels, transceiver types, and other information related to the sale of the transceivers 115. If the selected transceiver is in stock, then the user interface 140 notifies the user to continue by providing payment. If the transceiver is not in stock, then a notification is delivered to the user via the user interface 140, and the process 200 is ended. Processor 125 may be a stock processor that comes with known vending machines. Processor 125 may further comprise a proto-board.

[0076] At stage 220, the user presents a payment through the payment interface 146. In one example, this may be performed with present a credit card, in an embodiment where the payment interface 146 comprises a card reader. The payment interface 146 transmits the payment data to the processor 125. Processor 125 determines, based on transceiver cost data stored in memory 130, whether the payment has been successfully received at 230. If payment does not process successfully at stage 230, then the transaction process ends. If the payment does process successfully at stage 230, the processor 125 sends instructions to the dispensing means 150 to vend the desired transceiver 115 and to dispense it via the vending bay 155 at stage 235. At stage 235, stock levels are updated within memory 130.

[0077] At stage 240, a customer collects the vended transceiver from the vending bay 155, and at stage 245 inserts the transceiver into a port of the programming module 145, and may be presented with the option to start detecting a transceiver by using the start detecting module button 307 of screen 305 on user interface 140. After this, programming module 145 may send data to the processor indicating that the transceiver 115 is successfully connected, and if the transceiver is successfully detected, the user may continue the process 200; this may be prompted by screen 310, with options to continue to program optics at button 312, or to cancel and return to the start of the process 200 by button 314. Screen 310 may display a conditional indicator of whether the transceiver was connected successfully 311 At stage 250, a user selects a coding type to be applied to the transceiver 115 via the user interface 140. At this stage, the user may be presented with screen 315 by user interface 140, allowing them to select the brand of vended transceiver through menu 320, and the model number through menu 317. A confirmation display may be provided at 319 to indicate the specific coding instructions for the selected model of transceiver. The user may be presented with the ability to code the transceiver by button 322, or to return to detecting the presence of the transceiver with button 324. The instructions related to this coding type are sent from the user interface 140 to the controller 120, which retrieves the program code associated with the selected coding type from code library 135. The program code is then sent back through the processor and into the programming module 145, to the connected transceiver 115. The programming module 145 may have a separate display, built into the housing 105 to display status information or other alerts to a user. At stage 255, the controller 120 queries the connected transceiver 115 to determining with the code upload was successful. If the code upload was successful, the user may be presented with screen 325 with an indication of the success of the upload at 327. The user may be presented with a button 329 to end the process 200. If the code upload was not successful, then the user is notified via user interface 140, and prompted to retry selecting the desired coding type at stage 250. If the coding is successful, then the process 200 moves to stage 255 where the user is notified of the successful programming of the transceiver via user interface 140. At stage 260, the user is then prompted to remove the transceiver from the programming module 145. After this, the process ends at stage 265. In some embodiments, a user may only be allowed to program a transceiver after purchase. In other embodiments, a user can freely program any transceiver, regardless of whether a purchase has been conducted, thereby allowing users to try again in events where they select the wrong programming type.

[0078] Accordingly, a simple to use vending machine is provided for non-programmed transceivers, which also allows for convenient uploading of program code for the vended transceivers.

Claims

Claims1. A system comprising: a housing, comprising storage for one or more vendable items, wherein the housing is configured to selectively vend one or more vendable items; a controller, within the housing, comprising a processor in connection with a memory; a user interface in communication with the controller, configured to allow a user to selectively vend the one or more vendable items; a programming module, integrated within the housing and in connection with the processor, wherein the programming module is configured to communicatively connect to the one or more vendable items when dispensed; and wherein the controller is configured to upload program code to the one or more vendable items through the programming module.

2. The system of claim 1 , further comprising a dispensing elevator within the housing, configured to convey the one or more vendable items between a storage location and a dispenser.

3. The system of claim 1 or claim 2, wherein the user interface further comprises a card reader, and is configured to allow card payment from a user.

4. The system of any one of the preceding claims, wherein the one or more vendable items comprises one or more transceivers.

5. The system of claim 5, wherein the one or more transceivers comprise optical transceivers.

6. The system of any one of the preceding claims, further comprising a programming interface housing, configured to releasable attach the programming module with the housing.

7. The system of any one of the preceding claims, wherein the system further comprises a vending bay within the housing, configured to store a vended item for collection by a user.

8. The system of claim 7, wherein the vending bay further comprises a access hatch, covering configured to selectively allow a user access to the vending bay upon successful determination of the purchase of the vended item.

9. The system of claim 7 or claim 8, wherein the vending bay further comprises a load cell in connection with the processor, configured to determine weight data of a vended item within the vending bay.

10. The system of any one of claims 7 to 9, wherein the vending bay further comprises a bar code scanner in connection with the processor, configured to determine an identification code data of a vended item within the vending bay.

11. The system of claim 9 or claim 10, wherein the processor is configured to receive weight data and / or identification code data of a vended item within the vending bay, and to determine whether an item was vended successfully based on the weight data and / or identification code data.

12. A method comprising: determining one or more items to be selected for vending from a vending machine; responsive to determining one or more items for vending, determining whether the one or more items are in stock within the vending machine; determining a payment associated with vending the one or more items; responsive to determining whether the one or more items are in stock and the payment associated with the one or more items, vending the one or more items form the vending machine; determining a coding type for the one or more items; and uploading program code, related to the coding type, to the one or more items by connection with the vending machine.

13. The method of claim 6, wherein the one or more items are transceivers.

14. The method of claim 7, wherein the transceivers are optical transceivers.

Images