Mobile application for assisting a technician in carrying out an electronic work order

Information

  • Patent Grant
  • 11113642
  • Patent Number
    11,113,642
  • Date Filed
    Thursday, September 26, 2013
    11 years ago
  • Date Issued
    Tuesday, September 7, 2021
    3 years ago
Abstract
One embodiment is directed to a mobile application executing on a smartphone that is used to assist a technician in carrying out electronic work orders. In some embodiments, the mobile application uses a camera in the smartphone to take photos that are associated with one or more steps of the work order. In some embodiments, the mobile application is used to cause one or more LEDs associated with a step of the work order to be illuminated or otherwise visually actuated.
Description
BACKGROUND

Telecommunications networks typically include numerous logical communication links between various items of equipment. Often a single logical communication link is implemented using several pieces of physical communication media. For example, a logical communication link between a computer and an inter-networking device such as a hub or router can be implemented as follows. A first cable connects the computer to a jack mounted in a wall. A second cable connects the wall-mounted jack to a port of a patch panel, and a third cable connects the inter-networking device to another port of a patch panel. A “patch cord or cable” cross connects the two together. In other words, a single logical communication link is often implemented using several segments of physical communication media.


Various types of physical layer management (PLM) systems are used to facilitate the adding, changing, and removing of cross connections at a particular patch panel or a set of patch panels at a given location. Generally, such PLM systems include functionality to track what is connected to each port of a patch panel, trace connections that are made using a patch panel, and provide visual indications to a technician at a patch panel (for example, by illuminating an LED that is associated with the patch panel or a port thereof).


One exemplary type of PLM system makes use of an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other storage device that is integrated with or attached to a connector on a cable, fiber, or other segment of communication media. The storage device is used to store information about the connector or cable along with other information. The port (or other connector) into which the associated connector is inserted is configured to read the information stored in the EEPROM or other storage device when the connector is inserted that port.


Another type of PLM system makes of so-called “ninth wire” technology. Ninth wire technology makes use of special cables that include an extra conductor or signal path (also referred to here as the “ninth wire” conductor or signal path) that is used for determining which port each end of the cables is inserted into.


Another type of PLM system makes use of radio frequency identification (RFID) tags and readers. With this type of RFID PLM system, an RFID tag is attached to or integrated with a connector on a cable, fiber, or other segment of communication media. The RFID tag is used to store information about the connector or segment of communication media along with other information. The RFID tag can be read after the associated connector is inserted into a corresponding jack or other port using an RFID reader.


PLM systems typically include an application that enables electronic work orders to be constructed that specify one or more steps that are to be carried out by a technician at a particular location. For example, an electronic work order can indicate that a set of connections should be added, removed, and/or changed. For steps that involve adding, removing, and/or changing connections at a patch panel or other device that includes PLM technology, the proper performance of the steps can be verified using the PLM technology (for example, by using the PLM technology to confirm that the specified connection has been added, removed, and/or changed).


Electronic work orders can also includes steps that involve something other than adding, removing, and/or changing connections at a patch panel or other device that includes PLM technology. For example, an electronic work order can indicate that a technician should use a cable in a particular way (for example, routing the cable around specified cable guides). However, PLM systems are typically not able to automatically verify that the technician has properly carried out these types of steps.


Also, in the event that a technician finds it necessary to perform a step in a manner that deviates from what is specified in the electronic work order, the technician typically will manually enter information about the deviation into the PLM system. However, the PLM system is typically not able to acquire information that can be used to confirm or document such deviations, and either must rely on the data entered by the technician or have another individual travel to the work location in order to visually verify the information entered by the technician.


Furthermore, electronic work orders typically describe the steps to be performed using text.


Moreover, conventional electronic work order systems typically do not provide a convenient mechanism for a technician to illuminate (or otherwise visually actuate) light emitting diodes (LEDs) associated with a port or patch panel that is affected by a step in an electronic work order. Such conventional systems also typically do not provide a convenient mechanism for the technician to cause such LEDs to no longer be illuminated (or otherwise visually actuated).


SUMMARY

One embodiment is directed to a method of performing the steps of a work order. The method comprises generating an electronic work order. The electronic work order comprises a set of steps. The method further comprises communicating the electronic work order to a mobile application executing on a smartphone, using a camera included in the smartphone to take a picture related to the performance of at least one step associated with the electronic work order, associating the picture with the at least one step, and communicating the picture to an entity for use in documenting the at least one step.


Another embodiment is directed to a method of performing the steps of a work order. The method comprises generating an electronic work order. The electronic work order comprises a set of steps. The method further comprises communicating the electronic work order to a mobile application executing on a smartphone, receiving a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated, and sending a message from the mobile application executing on the smartphone to an external entity. The external entity is configured to visually actuate the visual indicator in response to receiving the message.


Another embodiment is directed to a program product for implementing a mobile application on a smartphone that is tangibly stored on a non-transitory storage medium. The program product comprises instructions operable to cause at least one programmable processor in the smartphone to receive an electronic work order comprising a set of steps, use a camera included in the smartphone to take a picture related to the performance of at least one step associated with the electronic work order, associate the picture with the at least one step, and communicate the picture to an entity for use in documenting the at least one step.


Another embodiment is directed to a program product for implementing a mobile application on a smartphone that is tangibly stored on a non-transitory storage medium. The program product comprises instructions operable to cause at least one programmable processor in the smartphone to receive an electronic work order comprising a set of steps, receive a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated, and send a message from the mobile application executing on the smartphone to an external entity. The external entity is configured to visually actuate the visual indicator in response to receiving the message.


Another embodiment is directed to a system comprising an aggregation point configured to receive and store information about connections made in a communication network. The system further comprises an electronic work order entity configured to generate an electronic work order. The electronic work order comprises a set of steps. The system further comprises a smartphone configured to receive the electronic work order using a mobile application executing on a smartphone. The smartphone comprises a camera. The mobile application is configured to: take a picture related to the performance of at least one step associated with the electronic work order, associate the picture with the at least one step, and communicate the picture to at least one of the aggregation point and the electronic work order entity for use in documenting the at least one step.


Another embodiment is directed to a system comprising an aggregation point configured to receive and store information about connections made in a communication network. The system further comprises an electronic work order entity configured to generate an electronic work order. The electronic work order comprises a set of steps. The system further comprises a smartphone configured to receive the electronic work order using a mobile application executing on a smartphone. The mobile application is configured to: receive a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated and send a message from the mobile application executing on the smartphone to an external entity. The external entity is configured to visually actuate the visual indicator in response to receiving the message.





DRAWINGS


FIG. 1 is a block diagram of one exemplary embodiment of a physical layer management (PLM) system that can be used with the mobile application technology described here.



FIG. 2 is a flow diagram showing one exemplary embodiment of a method of performing the steps of an electronic work using the mobile application shown in FIG. 1.



FIGS. 3A-3K are example screenshots of one exemplary embodiment of a mobile application and electronic work order application that can be used in the system of FIG. 1.





DETAILED DESCRIPTION


FIG. 1 is a block diagram of one exemplary embodiment of a physical layer management (PLM) system 100 that can be used with the mobile application technology described below. However, it is to be understood that the mobile application technology described below can be implemented using other PLM systems.


The particular PLM system 100 shown in FIG. 1 is described here as being implemented using EEPROM-based PLM technology (for example, the QUAREO™ PLM technology that is commercially available from TE Connectivity) with patch panels 102 that are configured to automatically obtain and track information about connections made at the ports 104 of the patch panels 102. However, it is to be understood that other embodiments can be implemented in other ways (for example, using RFID PLM technology or ninth-wire PLM technology). Patch panels, devices, and media that are configured to automatically obtain and/or track information about connections made using those devices and media are referred to here as “managed” devices and media.


Moreover, the mobile application technology described below can be implemented using devices and media that do not include functionality for automatically obtaining and tracking information about connections made using those devices and media. Such devices and media are also referred to here as “unmanaged” devices and media.


In this example, connections are made at the patch panels 102 using patch cables 106 that are terminated at each end with connectors 108 (for example, CAT-5 or CAT-6 patch cables that are terminated at each end with RJ-45 connectors). In this example, each connector 108 includes a storage device 110 (such as an Electrically Erasable Programmable Read-Only Memory (EEPROM)) in which information about the connector 108 and/or patch cable 106 is stored. Each connector 108 also includes a storage-device interface 112 via which information can be read from the associated storage device 110 when the connector 108 is inserted into a port 104 of a patch panel 102. In other embodiments, other types of devices, connectors, cabling, and media can be used (for example, fiber optic devices, cabling, and connectors).


Examples of storage device technology suitable for use in the example shown in FIG. 1 are described in the following United States patent applications, all of which are hereby incorporated herein by reference: U.S. Provisional Patent Application Ser. No. 61/252,964, filed on Oct. 19, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY”; U.S. Provisional Patent Application Ser. No. 61/253,208, filed on Oct. 20, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY”; U.S. patent application Ser. No. 12/907,724, filed on Oct. 19, 2010, titled “MANAGED ELECTRICAL CONNECTIVITY SYSTEMS”; U.S. Provisional Patent Application Ser. No. 61/303,948, filed on Feb. 12, 2010, titled “PANEL INCLUDING BLADE FEATURE FOR MANAGED CONNECTIVITY”; U.S. Provisional Patent Application Ser. No. 61/413,844, filed on Nov. 15, 2010, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”; U.S. Provisional Patent Application Ser. No. 61/439,693, filed on Feb. 4, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”; U.S. patent application Ser. No. 13/025,730, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”; U.S. patent application Ser. No. 13/025,737, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”; U.S. patent application Ser. No. 13/025,743, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”; U.S. patent application Ser. No. 13/025,750, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”; U.S. Provisional Patent Application Ser. No. 61/303,961; filed on Feb. 12, 2010, titled “Fiber Plug And Adapter For Managed Connectivity”; U.S. Provisional Patent Application Ser. No. 61/413,828, filed on Nov. 15, 2010, titled “Fiber Plugs And Adapters For Managed Connectivity”; U.S. Provisional Patent Application Ser. No. 61/437,504, filed on Jan. 28, 2011, titled “Fiber Plugs And Adapters For Managed Connectivity”; U.S. patent application Ser. No. 13/025,784, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”; U.S. patent application Ser. No. 13/025,788, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”; U.S. patent application Ser. No. 13/025,797, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”; U.S. patent application Ser. No. 13/025,841, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”; U.S. Provisional Patent Application Ser. No. 61/413,856, filed on Nov. 15, 2010, titled “CABLE MANAGEMENT IN RACK SYSTEMS”; U.S. Provisional Patent Application Ser. No. 61/466,696, filed on Mar. 23, 2011, titled “CABLE MANAGEMENT IN RACK SYSTEMS”; U.S. Provisional Patent Application Ser. No. 61/252,395, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN ELECTRICAL SYSTEMS”; U.S. patent application Ser. No. 12/905,689, filed on Oct. 15, 2010, titled “MANAGED CONNECTIVITY IN ELECTRICAL SYSTEMS”; U.S. Provisional Patent Application Ser. No. 61/252,386, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS”; U.S. patent application Ser. No. 12/905,658, filed on Oct. 15, 2010, titled “MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS”.


As noted above, in the exemplary embodiment shown in FIG. 1, the system 100 comprises one or more managed patch panels 102. Each managed patch panel 102 comprises a plurality of ports 104. Each port 104 is associated with a respective jack on the front face of the managed patch panel 102 into which a connector 108 of a patch cable 106 can be inserted. Each port 104 is also associated with a respective rear termination point (not shown) at which a horizontal run of cable can be terminated. Each port 104 is configured to communicatively couple the jack associated with that port 104 (and any patch cable 106 inserted therein) to the respective termination point (and any horizontal run of cable terminated thereat). In this way, a patch cable 106 inserted into the front jack of the port 104 can be connected to the corresponding horizontal run of cabling terminated at the corresponding rear termination point.


As noted above, each of the managed patch panels 102 in the examples described here includes physical layer management (PLM) functionality 114 that is configured to automatically obtain information about connections that are made using the ports 104 of that panel 102. In the example shown in FIG. 1, each of the managed patch panels 102 includes storage-device interfaces 116. Each of the ports 104 of the managed patch panels 102 is configured to include (or otherwise be associated with) a respective storage-device interface 116. The storage-device interface 116 of each port 104 is configured to mate, and inter-operate, with a corresponding storage-device interface 112 used in a connector 108 attached to an end of a patch cable 106 that is attached to a port 104 of the managed patch panel 102. Software 118 executing on a programmable processor (such as a controller) 120 associated with each patch panel 108 is able to read and write data from and to the storage device 110 associated with any connector 108 that is connected to a given port 104 using that port's storage-device interface 112. The software 118 and programmable processor 120 can be implemented in the manner described in the aforementioned US provisional patent applications and US non-provisional patent applications.


More specifically, when a connector 108 attached to an end of a patch cable 106 is inserted into the front jack of one of the ports 104 of a managed patch panel 102, the software 118 associated with that port 104 uses the storage-device interface 116 for that port 104 to detect that the connector 108 has been inserted and to read the information stored in the storage device 110 integrated into that connector 108. The software 118 then communicates at least a portion of that information to an aggregation point 124 (described below).


In this example, the PLM functionality 114 in each patch panel 102 includes one or more light emitting diodes (LEDs) (or other visual indicators) 122 that are associated with each port 104 of the managed patch panel 102. Each LED 122 is coupled to the programmable processor 120 in the patch panel 102 so that the software 118 executing on that programmable processor 120 can actuate the LEDs 122 (for example, by turning the LEDs 112 on or off or flashing or changing the color of the LEDs 112).


In the example shown in FIG. 1, the system 100 further comprises an aggregation point 124 and an electronic work order application 126. The aggregation point 124, electronic work order application 126, and managed patch panels 102 communicate with one another over a network 128. The computers on which the aggregation point 124 and electronic work order application 126 are implemented include an appropriate network interface to communicatively couple those computers to the network 128. In the example shown in FIG. 1, the programmable processors 120 in the managed patch panels 102 are communicatively coupled to the network 128 by including a respective “management” or “non-service” port 129 that is separate from the “service” ports 104. However, the programmable processors 120 in the managed patch panels 102 can be communicatively coupled to the network 128 using one or more of the “service” ports 104.


In one embodiment, the network 128 comprises an INTERNET PROTOCOL network. The network 128 can be implemented using one or more of a local area network (LAN), a wide area network (WAN), the INTERNET, a virtual local area network (VLAN), and a virtual private network (VPN), an enterprise network, and a telecommunication service provider network. Moreover, the managed patch panels 102 can be a part of the equipment used to implement the network 128.


The electronic work order application 126 is typically implemented in software that runs on a computer that is coupled to the network 128. In one embodiment, the electronic work order application 126 is implemented as software that runs on a server (or other computer).


The aggregation point 124 is typically implemented as software that runs on a computer that is coupled to the network 128. The electronic work order application 126 and the aggregation point 124 can run on the same computer and/or can be implemented as a part of the same software.


The aggregation point 124 is configured to receive physical layer information pertaining to various devices and media used to implement the physical layer in the network 128 (not just the patch cables 106). The physical layer information (PLI) includes information about various devices in the network 128 (for example, information about the patch panels 102) (also referred to here as “device information”) as well as information about any segments of physical communication media attached to the ports of those devices (also referred to here as “media information”). The device information includes, for example, an identifier for each device, a type identifier that identifies the device's type, and port information that includes information about the device's ports. The media information includes information that is read from storage devices that are attached to various segments of physical communication media.


Examples of media information that can be stored in such storage devices include, without limitation, an identifier that uniquely identifies that particular segment of physical communication media (similar to an ETHERNET Media Access Control (MAC) address but associated with the physical communication media and/or connector attached to the physical communication media), a part number, a plug or other connector type, a cable or fiber type and length, a serial number, a cable polarity, a date of manufacture, a manufacturing lot number, information about one or more visual attributes of physical communication media or a connector attached to the physical communication media (such as information about the color or shape of the physical communication media or connector or an image of the physical communication media or connector), and other information used by an Enterprise Resource Planning (ERP) system or inventory control system. In other embodiments, alternate or additional data is stored in such storage devices. For example, testing, media quality, or performance information can be stored in such storage devices. The testing, media quality, or performance information, for example, can be the results of testing that is performed when a particular segment of media is manufactured or installed.


The media information can also include information about physical communication media that does not have any storage devices attached to it. This latter type of media information can be manually supplied to the aggregation point 124.


The aggregation point 124 includes a database or other data store (not shown) for storing the physical layer information provided to it. The aggregation point 124 also includes functionality that provides an interface for external devices or entities to access the physical layer information maintained by the aggregation point 124. This access can include retrieving information from the aggregation point 124 as well as supplying information to the aggregation point 124. In this example, the aggregation point 124 is implemented as “middleware” that is able to provide such external devices and entities with transparent and convenient access to the PLI maintained by the aggregation point 124. Because the aggregation point 124 aggregates PLI from the relevant devices in the network 128 and provides external devices and entities with access to such PLI, the external devices and entities do not need to individually interact with all of the devices in the network 128 that provide PLI, nor do such devices need to have the capacity to respond to requests from such external devices and entities.


The aggregation point 124, in this example, implements an application programming interface (API) by which application-layer functionality can gain access to the physical layer information maintained by the aggregation point 124 using a software development kit (SDK) that describes and documents the API.


More information about physical layer information and the aggregation point 124 can be found in U.S. Provisional Patent Application Ser. No. 61/152,624, filed on Feb. 13, 2009, titled “MANAGED CONNECTIVITY SYSTEMS AND METHODS” and U.S. patent application Ser. No. 12/705,497, filed on Feb. 12, 2010, titled “AGGREGATION OF PHYSICAL LAYER INFORMATION RELATED TO A NETWORK”, both of which are hereby incorporated herein by reference.


In this example, the electronic work application 126 is used to construct electronic work orders. As noted above, each electronic work specifies one or more steps that are to be carried out by a technician at a particular location. For example, an electronic work order can indicate that one or more connections implemented using the ports 104 of the patch panels 102 should be added, removed, and/or changed. For steps that involve adding, removing, and/or changing connections made at the ports 104 of the patch panels 102, the information that is read from the associated storage devices 110 by the PLM functionality 114 in the patch panels 102 and communicated to the aggregation point 124 can be used by the electronic work order application 126 to verify that the specified connection has been added, removed, and/or changed correctly.


As noted above, electronic work orders can also includes steps that involve something other than adding, removing, and/or changing connections made using the ports 104 of a managed patch panel 102. For example, an electronic work order can indicate that a technician should route a cable in a particular way (for example, routing the cable around specified cable guides).


Also, the LEDs 122 associated with the ports 104 of the managed patch panels 102 can be actuated in order to guide a technician in carrying out the steps of electronic work orders.


In this example, each electronic work order is communicated to a smartphone 132 (or similar device) that is carried by a technician that has been assigned to carry out that electronic work order. In this example, the smartphone 132 is configured to execute a mobile application 134. The mobile application is configured to communicate with the electronic work order application 126 and the aggregation point 124 and to receive the electronic work orders. This mobile application 134 is also referred to here as the “electronic work order mobile application” 134 or the “PLM mobile application” 134. The mobile application 134 comprises program instructions that are stored (or otherwise embodied) on or in an appropriate non-transitory storage medium or media from which at least a portion of the program instructions are read by at least one programmable processor included in the smartphone 132 for execution thereby.


The electronic work order can be communicated wirelessly to the smartphone 132 over the Internet (for example, via a cellular or wireless local area network to which the smartphone 132 is wirelessly connected). The electronic work order can also be communicated to the smartphone 132 in other ways (for example, using a wired connection with the smartphone 132).


In this example, the smartphone 132 includes a camera 136.


A technician can use the mobile application 134 executing on the smartphone 132 to access an electronic work order and to view information about the steps of each electronic work order on the smartphone's display.


The technician can use the mobile application 134 to carry out the steps specified in the electronic work orders assigned to the technician and to mark them as “done”. The technician can use the mobile application 134 to perform general, connect, and disconnect work order steps. As noted above, the mobile application 134 can be used to carry out steps that involve patch (or other cables) and patch panels (or other devices) that include PLM functionality (such cables and devices are also referred to here as “managed” cables and devices and such steps are also referred to here as “managed steps”).


The mobile application 134 can also be used to carry out steps that involve patch cables (or other cables) and patch panels (or other devices) that do not include PLM functionality (such cables and devices are also referred to here as “unmanaged” cables and devices and such steps are also referred to here as “unmanaged steps”). In the example shown in FIG. 1, the unmanaged devices include a switch 140 and an unmanaged patch panel 142, both of which do not include any PLM functionality.


Also, the mobile application 134 is configured to capture and display photos from the camera 136 in the smartphone 132 in order to document a work order step and to communicate the photos back to the electronic work order application 126 and/or aggregation point 124 for use in documenting and verifying that the technician has properly carried out that step. The mobile application 134 is also configured to enable a technician to enter comments about work order steps that have been carried out. These last two features of the mobile application 134 can also be used in the event that a technician finds it necessary to perform a step in a manner that deviates from what is specified in the electronic work order. These features can be used to document the rationale and the nature of the deviation. For example, where a step of a work order indicates that a particular length of cable should be used but one is not available, the technician can use a cable having a different length and enter a comment explaining why this was done and take a picture of the cable that was used.


These two features can also be used to provide information about general and unmanaged steps that are performed. For example, where a step specifies that a cable be routed in a particular way, after the technician has routed the cable in the manner specified in the step, the technician can use the mobile application 134 to take a picture of the properly routed cable using the smartphone's camera 136. The mobile application 134 is configured to associate the picture with that step of the electronic work order. The technician can also enter a comment about how the cable was routed. The mobile application 134 communicates the captured photo and comment back to the electronic work order application 126 and/or aggregation point 124, where the captured photo and comment can be used to document and verify that step.


The mobile application 134 is also configured to display events and alarms for the technician. The mobile application 134 can be configured to obtain the alarms and events from the electronic work order application 126 and/or the aggregation point 124.



FIG. 2 is a flow diagram showing one exemplary embodiment of a method 200 of performing the steps of an electronic work using the mobile application 134 described above in connection with FIG. 1. The example shown in FIG. 2 is described here as being implemented using the system 100 shown in FIG. 1, though it is to be understood that other embodiments can be implemented in other ways. Moreover, the blocks of the flow diagram shown in FIG. 2 have been arranged for ease of explanation; however, it is to be understood that this arrangement is merely exemplary, and it should be recognized that the processing associated with method 200 (and the blocks shown in FIG. 2) can occur in any order (for example, using standard event-driven programming techniques).


Method 200 comprises generating an electronic work order (block 202). As noted above, each electronic work order comprises a set of steps of the type described above in connection with FIG. 1. In this example, the electronic work order application 126 is used to create the electronic work order. In this example, method 200 further comprises communicating the electronic work order to a mobile application 134 executing on a smartphone 132 (block 204). In this example, the electronic work order can be wirelessly communicated from the electronic work order application 126, for example, using a cellular or wireless local area network communication link, or can be communicated from the electronic work order application 126 using a wired connection to the Internet or a local area network or a wired direct connection to the electronic work order application 126.


Method 200 further comprise displaying information about one or more of the steps associated with the electronic work order using the mobile application 134 executing on the smartphone 132 (block 206) and displaying information about events and alarms using the mobile application 134 executing on the smartphone 132 (block 208). In this example, either of these actions can be requested by the technician using the user interface implemented by the mobile application 134. The information that is displayed using the mobile application 134 can include textual and visual information (pictures). Also, in this example, the event and alarm information can be communicated to the mobile application 134 from the aggregation point 124 and/or the electronic work order application 126. In this way, the mobile application 134 provides the technician with a convenient way to see such information while on-site and performing the steps of an electronic work order.


Method 200 further comprises using a camera 136 included in the smartphone 132 to take a picture related to the performance of at least one step included in the electronic work order (block 210) and associating the picture with the at least one step (block 212). In this example, the mobile application 134 is configured to do this.


Method 200 further comprises communicating the picture to an entity for use in documenting the at least one step (block 214). In this example, the mobile application 134 is configured to communicate the picture to at least one of the aggregation point 124 and the electronic work order application 126 for use in documenting the step the picture is associated with.


Such a picture can be taken in order to provide confirmation that a particular step in the electronic work order has been performed in the manner specified in the electronic work order. This is especially usual for electronic work orders that include steps that involve something other than adding, removing, and/or changing connections at a managed patch panel or other managed device. For example, a step in an electronic work order can indicate that a technician should use a cable in a particular way (for example, routing the cable around specified cable guides). After performing such a step, and then using the mobile application 134 to take a picture of the cable, associate the picture with that step, and then communicate that picture to the aggregation point 124 or the electronic work order application 126. Then, a manager can view the picture in order to confirm that the cable was routed as directed in the electronic work order.


Such a picture can also be taken in the event that a technician finds it necessary to perform a step in an electronic work order in a manner that deviates from what is specified in the electronic work order. For example, where a step in an electronic work order specifies that a particular length of cable is to be used to make a particular connection but a cable of that length is not available, the technician can take a picture of the cable that is actually used (in addition to using the mobile application 134 to enter a text comment that explains the rationale for the deviation). The mobile application 134 can be used to associate the picture with that step and then communicate that picture to the aggregation point 124 or the electronic work order application 126. The picture can be used for documentation purposes and, if the connection is made using an unmanaged patch panel or other unmanaged device, to confirm that a cable of the length described in the technician's comment was indeed used to make the connection.


Method 200 further comprises receiving a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated (block 216) and, in response to that, sending a message from the mobile application 134 executing on the smartphone 132 to an external entity, where the external entity is configured to visually actuate the visual indicator in response to receiving the message (block 218). In this example, the visual indicator comprises one or more light emitting diodes 122 that are associated with a port 104 or patch panel 102 that is affected by the current step of the work order. The LEDs 122 can be visually actuated, for example, by illuminating the LED 122, flashing the LED 122, and/or changing the color of the LED 122.


In this example, the mobile application 134 executing on the smartphone 132 is configured to display on the screen of the smartphone 132 a suitable user interface element that a technician can interact with in order to indicate that the technician would like the one or more LEDs 122 associated with the port 104 (or patch panel 102) involved with the current step of the work order to be illuminated (or otherwise visually actuated). In this example, when the mobile application 134 receives such user input from the technician, the mobile application 134 sends a message to the aggregation point 124 (the external entity in this example) indicating that the aggregation point 124 should illuminate or otherwise visually actuate the relevant LEDs 122. The aggregation point 124 does this in response to receiving such a message.


Method 200 further comprises receiving a user input indicating that the visual indicator associated with the current step should stop being visually actuated (block 220) and, in response to that, sending a stop message from the mobile application 134 executing on the smartphone to the external entity, where the external entity is configured to stop visually actuating the visual indicator in response to receiving the stop message (block 222). In this example, the mobile application 134 executing on the smartphone 132 is configured to display on the screen of the smartphone 132 a suitable user interface element that a technician can interact with in order to indicate that the technician would like the one or more LEDs 122 that are associated with the port 104 (or patch panel 102) involved with the current step of the work order to stop being illuminated (or otherwise visually actuated). In this example, when the mobile application 134 receives such user input from the technician, the mobile application 134 sends a message to the aggregation point 124 (the external entity in this example) indicating that the aggregation point 124 should stop illuminating or otherwise visually actuating the relevant LEDs 122. The aggregation point 124 does this in response to receiving such a message.


In this way, the technician is provided with a convenient way to cause the LEDs 122 (or other visual indicators) that are associated with the current step of the electronic work order to be visually actuated (and thereafter stopped) while the technician is on-site and performing that step.



FIGS. 3A-3K are example screenshots of one exemplary embodiment of a mobile application 134 and electronic work order application 126 that can be used with the system 100 of FIG. 1.



FIG. 3A is a screenshot of a “Work Orders” screen displayed by the mobile application 134 on the smartphone 132. This Work Orders screen displays a technician's active work orders. The percentage of each work order that is completed is displayed using a bar control (where the orange part of the bar control indicates how much of the work order has been completed). Also, in this example, the active work order (for example, one for which one or more LEDs 122 are illuminated or otherwise actuated) is indicated by a LED icon.



FIG. 3B is a screenshot of a “Work Order List” screen of the electronic work order application 126 that lists some of the work orders shown in the example of FIG. 3A.



FIGS. 3C-3D are screenshots of “Steps” screens displayed by the mobile application 134 on the smartphone 132.


A Step screen is displayed when the technician taps on a particular work order displayed in the Work Orders (shown in FIG. 3A). For example, FIG. 3C shows the Step screen that is displayed if the technician taps on the work order labeled “Comms patching Friday 13”, and FIG. 3D shows the Step screen that is displayed if the technician taps on the work order labeled “Catalogue Comms room”. For each step, the start and end dates for that step are displayed. To start working on that step, the technician can tap the Start button is displayed in that Step screen. If the step is a managed step and the mobile application 134 is connected to the aggregation point 124, tapping the Start button causes the aggregation point 124 to visually actuate any associated LEDs 122 (for exampled, by flashing the LEDs 122). This provides a visual signal to aid the technician in carrying out the step. To stop working on that step, the technician can tap the Stop button that is displayed in that Step screen. This causes the aggregation point 124 to stop visually actuating any associated LEDs 122. The mobile application 134 provides a convenient mechanism for the technician to cause the LEDs 122 to be visually actuated in order to provide the technician visual assistance in carrying out that step.


For steps that involve a connection or disconnection of a connection, “to” and “from” ports are displayed on the screen. Also, the different types of steps (for example, Connect, Disconnect, General) can be color-coded (for example, Connect steps can be displayed using the color green, Disconnect steps can be displayed using the color red, and General steps can be displayed using the color grey). In this example, the technician can indicate that a general step has been completed by tapping a circle to “check off” that step as being completed. Managed steps can be marked as being completed as follows. When the indicated connector 108 is inserted into or removed from a port 104 of a managed patch panel 102, the software 118 associated with that port 104 will detect that event and read the information from the associated storage device 110 (in the case of an insertion) and report the event back to the aggregation point 124. The aggregation point 124, in response to such an event, will verify that the correct port 104 has been affected and, if it has, will communicate with the mobile application 134 to indicate that the step has been correctly completed. This requires the mobile application 134 to be in communication with the aggregation point 124. In this example, the screen can be refreshed by tapping on the Refresh button.


As noted above, a technician can enter comments about, and take photos related to, a particular step if required. FIG. 3E is a screenshot of one example of a Step screen that shows how Comments and Photos can be associated with a step. The technician can enter a Comment by tapping on the “Add a Comment” control, which causes a field to be displayed that the technician can enter the comment into. The technician can view photos that have been associated with the step by tapping on the Photo control, which, as shown in FIG. 3F, lists any Photos that have been associated with that step. The technician can tap the Camera icon in order to take a new photo or to select an existing photo from the photo library on the smartphone 132. The mobile application then associated the new or selected photo with that step. These photos require uploading to the aggregation point 124 and/or electronic work order application 126. Those photos that have not yet been uploaded are identified, in this example, with a Cloud icon, which the technician can tap in order to cause the selected photo to be uploaded. After the photo has been uploaded, the Cloud icon is no longer displayed. In the example shown in FIGS. 3E and 3F, these Comment and Photo features are used with the “general” steps of an electronic work order (though they can be used with other types of steps as well in other examples).


The mobile application 134 is also configured to display information about any errors that occur in connection with performing a step. One example of an error that is reported in a step screen is shown in FIG. 3G. Additional details about the error can be viewed by tapping on the “Incorrect Cable fitted” button.


The mobile application 134 is also configured to display details about the cables involved in a step. One example of a cable detail screen is shown in FIG. 3H. As shown in FIG. 3H, Comments and Photos can be associated with the cable.


As noted above, the mobile application 134 is also configured to display information about events and alarms. FIG. 3I is a screenshot of one example of an Event screen displayed by the mobile application 134. In this example, those events that are associated with open alarms are indicated by a red alarm clock signal.



FIG. 3J shows a screenshot of one example of an Event Viewer screen that is displayed by the electronic work order application 124.



FIG. 3K is a screenshot of one example of a Settings screen that a technician can use to log into the aggregation point 124. As shown in FIG. 3K, the technician can enter a username and password and view and change an IP address for the aggregation point 124 (also referred to as the ICM Server) using this screen. In this example, updates are applied by tapping the Update ICM Settings button. The technician can also use this screen to view an End User License Agreement for the mobile application 134.


Example Embodiments

Example 1 includes a method of performing the steps of a work order, the method comprising: generating an electronic work order, the electronic work order comprising a set of steps; communicating the electronic work order to a mobile application executing on a smartphone; using a camera included in the smartphone to take a picture related to the performance of at least one step associated with the electronic work order; associating the picture with the at least one step; and communicating the picture to an entity for use in documenting the at least one step.


Example 2 includes the method of Example 1 and further includes displaying information about one or more of the steps associated with the electronic work order using the mobile application executing on the smartphone.


Example 3 includes any of the methods of Examples 1-2 and further includes displaying information about events and alarms using the mobile application executing on the smartphone.


Example 4 includes a method of performing the steps of a work order, the method comprising: generating an electronic work order, the electronic work order comprising a set of steps; communicating the electronic work order to a mobile application executing on a smartphone; receiving a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated; and sending a message from the mobile application executing on the smartphone to an external entity, wherein the external entity is configured to visually actuate the visual indicator in response to receiving the message.


Example 5 includes the method of Example 4, wherein the visual indicator comprises at least one light emitting diode.


Example 6 includes the method of Example 5, wherein visually actuating the light emitting diode comprises at least one of illuminate the light emitting diode, flashing the light emitting diode, and changing the color of the light emitting diode.


Example 7 includes any of the methods of Examples 4-6 and further includes: receiving a user input indicating that the visual indicator associated with the at least one step included in the electronic work order should stop being visually actuated; and sending a stop message from the mobile application executing on the smartphone to the external entity, wherein the external entity is configured to stop visually actuating the visual indicator in response to receiving the stop message.


Example 8 includes a program product for implementing a mobile application on a smartphone, tangibly stored on a non-transitory storage medium, comprising instructions operable to cause at least one programmable processor in the smartphone to: receive an electronic work order comprising a set of steps; use a camera included in the smartphone to take a picture related to the performance of at least one step associated with the electronic work order; associate the picture with the at least one step; and communicate the picture to an entity for use in documenting the at least one step.


Example 9 includes the program product of Example 8 and further comprises instructions operable to cause the at least one programmable processor in the smartphone to display information about one or more of the steps associated with the electronic work order using the mobile application executing on the smartphone.


Example 10 includes the program product of any of the Examples 8-9 and further comprises instructions operable to cause the at least one programmable processor in the smartphone to display information about events and alarms using the mobile application executing on the smartphone.


Example 11 includes a program product for implementing a mobile application on a smartphone, tangibly stored on a non-transitory storage medium, comprising instructions operable to cause at least one programmable processor in the smartphone to: receive an electronic work order comprising a set of steps; receive a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated; and send a message from the mobile application executing on the smartphone to an external entity, wherein the external entity is configured to visually actuate the visual indicator in response to receiving the message.


Example 12 includes the program product of Example 11, wherein the visual indicator comprises at least one light emitting diode.


Example 13 includes the program product of Example 12, wherein visually actuating the light emitting diode comprises at least one of illuminate the light emitting diode, flashing the light emitting diode, and changing the color of the light emitting diode.


Example 14 includes any of the program products of Examples 11-13 and further comprises instructions operable to cause the at least one programmable processor in the smartphone to receive a user input indicating that the visual indicator associated with the at least one step included in the electronic work order should stop being visually actuated; and send a stop message from the mobile application executing on the smartphone to the external entity, wherein the external entity is configured to stop visually actuating the visual indicator in response to receiving the stop message.


Example 15 includes a system that includes an aggregation point configured to receive and store information about connections made in a communication network; an electronic work order entity configured to generate an electronic work order, the electronic work order comprising a set of steps; a smartphone configured to receive the electronic work order using a mobile application executing on a smartphone; wherein the smartphone comprises a camera, wherein the mobile application is configured to: take a picture related to the performance of at least one step associated with the electronic work order, associate the picture with the at least one step; and communicating the picture to at least one of the aggregation point and the electronic work order entity for use in documenting the at least one step.


Example 16 includes the system of Example 15, wherein the mobile application is configured to display information about one or more of the steps associated with the electronic work order.


Example 17 includes the system of Example 15, wherein the mobile application is configured to display information about events and alarms.


Example 18 includes a system that includes: an aggregation point configured to receive and store information about connections made in a communication network; an electronic work order entity configured to generate an electronic work order, the electronic work order comprising a set of steps; a smartphone configured to receive the electronic work order using a mobile application executing on a smartphone; wherein the mobile application is configured to: receive a user input indicating that a visual indicator associated with at least one step included in the electronic work order should be visually actuated; and send a message from the mobile application executing on the smartphone to an external entity, wherein the external entity is configured to visually actuate the visual indicator in response to receiving the message.


Example 19 includes the system of Example 18, wherein the visual indicator comprises at least one light emitting diode.


Example 20 includes the system of Example 19, wherein visually actuating the light emitting diode comprises at least one of illuminate the light emitting diode, flashing the light emitting diode, and changing the color of the light emitting diode.


Example 21 includes any of the systems of Examples 18-19, wherein the mobile application is configured to: receive a user input indicating that the visual indicator associated with the at least one step included in the electronic work order should stop being visually actuated; and send a stop message from the mobile application executing on the smartphone to the external entity, wherein the external entity is configured to stop visually actuating the visual indicator in response to receiving the stop message.


A number of embodiments have been described. Nevertheless, it will be understood that various modifications to the described embodiments may be made without departing from the spirit and scope of the claimed invention. Also, combinations of the individual features of the above-described embodiments are considered within the scope of the inventions disclosed here.

Claims
  • 1. A method, comprising: generating an electronic work order, the electronic work order comprising a set of steps that are to be carried out by a single technician at a particular location, wherein at least one step of the set of steps includes adding, moving, or changing a connection made at a first port of a device;communicating the electronic work order to a mobile application executing on a smartphone;displaying information about the at least one step of the set of steps included in the electronic work order with the mobile application executing on the smartphone;receiving a first user input, at the mobile application executing on the smartphone, during performance of the at least one step of the set of steps included in the electronic work order, the first user input requesting that an electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order be visually actuated, wherein the electronic visual indicator is located on the device, distinct from the smartphone, having one or more ports to attach cables to the device, wherein the electronic visual indicator is associated with the first port of the one or more ports where a connection is changed as part of the at least one step of the set of steps included in the electronic work order;in response to the received first user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order be visually actuated, sending a request from the mobile application executing on the smartphone to an external entity, wherein the external entity visually actuates the electronic visual indicator in response to receiving the request from the mobile application executing on the smartphone;receiving a second user input, at the mobile application executing on the smartphone, during performance of the at least one step of the set of steps included in the electronic work order, the second user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order stop being visually actuated; andin response to the received second user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order stop being visually actuated, sending a stop request from the mobile application executing on the smartphone to the external entity, wherein the external entity is configured to stop visually actuating the electronic visual indicator in response to receiving the stop request from the mobile application executing on the smartphone; andwherein the method further comprises at least one of: receiving an additional user input, at the mobile application executing on the smartphone, indicating that a second step of the set of steps included in the electronic work order has been completed; andreceiving a communication from the external entity, at the mobile application executing on the smartphone, verifying that the at least one step of the set of steps included in the electronic work order that includes adding, moving, or changing the connection made at the first port of the device has been correctly completed.
  • 2. The method of claim 1, wherein the electronic visual indicator comprises at least one light emitting diode.
  • 3. The method of claim 2, wherein visually actuating the light emitting diode comprises at least one of illuminating the light emitting diode, flashing the light emitting diode, and changing the color of the light emitting diode.
  • 4. The method of claim 1, further comprising receiving, at the mobile application executing on the smartphone, a third user input indicating that the at least one step of the set of steps included in the electronic work order, which includes adding, moving, or changing the connection made at the first port of the device, has been completed.
  • 5. The method of claim 4, comprising: receiving an additional user input, at the mobile application executing on the smartphone, indicating that a second step of the set of steps included in the electronic work order has been completed; andreceiving a communication from the external entity, at the mobile application executing on the smartphone, verifying that the at least one step of the set of steps included in the electronic work order, which includes adding, moving, or changing the connection made at the first port of the device, has been correctly completed;the method further comprising receiving a second communication from the external entity, at the mobile application executing on the smartphone, verifying that second step of the set of steps included in the electronic work order has been correctly completed.
  • 6. A program product for implementing a mobile application on a smartphone, tangibly stored on a non-transitory storage medium, comprising instructions operable to cause at least one programmable processor in the smartphone to: receive an electronic work order comprising a set of steps that are to be carried out by a single technician at a particular location, wherein at least one step of the set of steps includes adding, moving, or changing a connection made at a first port of a device;display information about the at least one step of the set of steps included in the electronic work order;receive a first user input during performance of the at least one step of the set of steps included in the electronic work order, the first user input requesting that an electronic visual indicator associated with visually assisting the technician in carrying out at least one step of the set of steps included in the electronic work order be visually actuated, wherein the electronic visual indicator is located on a device, distinct from the smartphone, having one or more ports to attach cables to the device, wherein the electronic visual indicator is associated with the first port of the one or more ports where a connection is changed as part of the at least one step of the set of steps included in the electronic work order;in response to the received first user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out at least one step of the set of steps included in the electronic work order be visually actuated, send a request from the mobile application executing on the smartphone to an external entity, wherein the external entity visually actuates the electronic visual indicator in response to receiving the request from the mobile application executing on the smartphone;receive a second user input during performance of the at least one step of the set of steps included in the electronic work order, the second user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order stop being visually actuated; andin response to the received second user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order stop being visually actuated, send a stop request from the mobile application executing on the smartphone to the external entity, wherein the external entity is configured to stop visually actuating the electronic visual indicator in response to receiving the stop request from the mobile application executing on the smartphone; andwherein the program product further comprises instructions operable to cause the at least one programmable processor in the smartphone to: receive an additional user input, at the mobile application executing on the smartphone, indicating that a second step of the set of steps included in the electronic work order has been completed; and/orreceive a communication from the external entity, at the mobile application executing on the smartphone, verifying that the at least one step of the set of steps included in the electronic work order that includes adding, moving, or changing the connection made at the first port of the device has been correctly completed.
  • 7. The program product of claim 6, wherein the electronic visual indicator comprises at least one light emitting diode.
  • 8. The program product of claim 7, wherein visually actuating the light emitting diode comprises at least one of illuminating the light emitting diode, flashing the light emitting diode, and changing the color of the light emitting diode.
  • 9. The program product of claim 6, further comprising instructions operable to cause the at least one programmable processor in the smartphone to receive a third user input indicating that the at least one step of the set of steps included in the electronic work order, which includes adding, moving, or changing the connection made at the first port of the device, has been completed.
  • 10. The program product of claim 9, comprising instructions operable to cause the at least one programmable processor in the smartphone to: receive an additional user input, at the mobile application executing on the smartphone, indicating that a second step of the set of steps included in the electronic work order has been completed; andreceive a communication from the external entity, at the mobile application executing on the smartphone, verifying that the at least one step of the set of steps included in the electronic work order, which includes adding, moving, or changing the connection made at the first port of the device, has been correctly completed;the program product further comprising instructions operable to cause the at least one programmable processor in the smartphone to receive a second communication from the aggregation point, at the mobile application executing on the smartphone, verifying that second step of the set of steps included in the electronic work order has been correctly completed.
  • 11. A system comprising: an aggregation point configured to receive and store information about connections made in a communication network;an electronic work order entity configured to generate an electronic work order, the electronic work order comprising a set of steps that are to be carried out by a single technician at a particular location, wherein at least one step of the set of steps includes adding, moving, or changing a connection made at a first port of a device; anda smartphone configured to receive the electronic work order using a mobile application executing on a smartphone;wherein the mobile application executing on the smartphone is configured to:display information about the at least one step of the set of steps included in the electronic work order with the mobile application executing on the smartphone;receive a first user input during performance of the at least one step of the set of steps included in the electronic work order, the first user input requesting that an electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order be visually actuated, wherein the electronic visual indicator is located on the device, distinct from the smartphone, having one or more ports to attach cables to the device, wherein the electronic visual indicator is associated with the first port of the one or more ports where a connection is changed as part of the at least one step of the set of steps included in the electronic work order;in response to the received first user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order be visually actuated, send a request from the mobile application executing on the smartphone to the aggregation point, wherein the aggregation point visually actuates the electronic visual indicator in response to receiving the request from the mobile application executing on the smartphone;receive a second user input during performance of the at least one step of the set of steps included in the electronic work order, the second user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order stop being visually actuated; andin response to the received second user input requesting that the electronic visual indicator associated with visually assisting the technician in carrying out the at least one step of the set of steps included in the electronic work order stop being visually actuated, send a stop request from the mobile application executing on the smartphone to the aggregation point, wherein the aggregation point is configured to stop visually actuating the electronic visual indicator in response to receiving the stop request from the mobile application executing on the smartphone; andwherein the mobile application executing on the smartphone is further configured to: receive an additional user input, at the mobile application executing on the smartphone, indicating that a second step of the set of steps included in the electronic work order has been completed; and/orreceive a communication from the aggregation point, at the mobile application executing on the smartphone, verifying that the at least one step of the set of steps included in the electronic work order that includes adding, moving, or changing the connection made at the first port of the device has been correctly completed.
  • 12. The system of claim 11, wherein the electronic visual indicator comprises at least one light emitting diode.
  • 13. The system of claim 12, wherein visually actuating the light emitting diode comprises at least one of illuminating the light emitting diode, flashing the light emitting diode, and changing the color of the light emitting diode.
  • 14. The system of claim 11, wherein the mobile application executing on the smartphone is further configured to receive a third user input indicating that the at least one step of the set of steps included in the electronic work order, which includes adding, moving, or changing the connection made at the first port of the device, has been completed.
  • 15. The system of claim 14, wherein the mobile application executing on the smartphone is configured to: receive an additional user input, at the mobile application executing on the smartphone, indicating that a second step of the set of steps included in the electronic work order has been completed; andreceive a communication from the aggregation point, at the mobile application executing on the smartphone, verifying that the at least one step of the set of steps included in the electronic work order, which includes adding, moving, or changing the connection made at the first port of the device, has been correctly completed;wherein the mobile application executing on the smartphone is further configured to receive a second communication from the aggregation point, at the mobile application executing on the smartphone, verifying that second step of the set of steps included in the electronic work order has been correctly completed.
CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/706,460, filed on Sep. 27, 2012, which is hereby incorporated herein by reference.

US Referenced Citations (210)
Number Name Date Kind
4446454 Pyle May 1984 A
5052940 Bengal Oct 1991 A
5161988 Krupka Nov 1992 A
5195902 Bengal Mar 1993 A
5299944 Larabell et al. Apr 1994 A
5394503 Dietz, Jr. et al. Feb 1995 A
5418334 Williams May 1995 A
5420512 Spillane et al. May 1995 A
5448675 Leone et al. Sep 1995 A
5461693 Pimpinella Oct 1995 A
5463706 Dumont et al. Oct 1995 A
5473715 Schofield et al. Dec 1995 A
5483467 Krupka Jan 1996 A
5487666 DiGiovanni Jan 1996 A
5541586 Wise Jul 1996 A
5550755 Martin et al. Aug 1996 A
5606664 Brown et al. Feb 1997 A
5649001 Thomas et al. Jul 1997 A
5764043 Czosnowski et al. Jun 1998 A
5821510 Cohen et al. Oct 1998 A
5832071 Voelker Nov 1998 A
5854824 Bengal et al. Dec 1998 A
5876240 Derstine et al. Mar 1999 A
5909464 Cohen et al. Jun 1999 A
5910776 Black Jun 1999 A
6002331 Laor Dec 1999 A
6222908 Bartolutti et al. Apr 2001 B1
6223219 Uniacke et al. Apr 2001 B1
6234830 Ensz et al. May 2001 B1
6238235 Shavit et al. May 2001 B1
6240090 Enhager May 2001 B1
6285293 German et al. Sep 2001 B1
6300877 Schannach et al. Oct 2001 B1
6307880 Evans et al. Oct 2001 B1
6330307 Bloch et al. Dec 2001 B1
6350148 Bartolutti et al. Feb 2002 B1
6359859 Brolin et al. Mar 2002 B1
6368155 Bassler et al. Apr 2002 B1
6378111 Brenner et al. Apr 2002 B1
6424710 Bartolutti et al. Jul 2002 B1
6442032 Linares et al. Aug 2002 B1
6499861 German et al. Dec 2002 B1
6516345 Kracht Feb 2003 B1
6522737 Bartolutti et al. Feb 2003 B1
6564258 Uniacke May 2003 B1
6574221 Petersen Jun 2003 B1
6574586 David et al. Jun 2003 B1
6577243 Dannenmann et al. Jun 2003 B1
6636152 Schannach et al. Oct 2003 B2
6684179 David Jan 2004 B1
6725177 David et al. Apr 2004 B2
6778505 Bullman et al. Aug 2004 B1
6784802 Stanescu Aug 2004 B1
6808116 Eslambolchi et al. Oct 2004 B1
6847856 Bohannon Jan 2005 B1
6881096 Brown et al. Apr 2005 B2
D510068 Haggay et al. Sep 2005 S
6961675 David Nov 2005 B2
6968994 Ashwood Smith Nov 2005 B1
6976867 Navarro et al. Dec 2005 B2
6993417 Osann, Jr. Jan 2006 B2
7038135 Chan et al. May 2006 B1
7039028 Chen et al. May 2006 B2
7042562 Kiani et al. May 2006 B2
7046899 Colombo et al. May 2006 B2
7057105 Gottardo et al. Jun 2006 B2
7075910 Chen et al. Jul 2006 B2
7077710 Haggay et al. Jul 2006 B2
7081808 Colombo et al. Jul 2006 B2
7123810 Parrish Oct 2006 B2
7126918 Roberts Oct 2006 B2
7136936 Chan et al. Nov 2006 B2
7142536 Gossett et al. Nov 2006 B1
7153142 Shifris et al. Dec 2006 B2
7159026 Lau et al. Jan 2007 B2
7160143 David et al. Jan 2007 B2
7193422 Velleca et al. Mar 2007 B2
7197214 Elkins, II et al. Mar 2007 B2
7226217 Benton et al. Jun 2007 B1
7229020 Goodison et al. Jun 2007 B2
7234944 Nordin et al. Jun 2007 B2
7246746 McNamara et al. Jul 2007 B2
7254652 Anderson et al. Aug 2007 B2
7266087 Wahl Sep 2007 B2
7289334 Behrens et al. Oct 2007 B2
7289436 Schaller et al. Oct 2007 B2
7297018 Caveney et al. Nov 2007 B2
7312715 Shalts et al. Dec 2007 B2
D559186 Kelmer Jan 2008 S
7315224 Gurovich et al. Jan 2008 B2
7317735 Ojard Jan 2008 B1
7328033 Rappaport et al. Feb 2008 B2
D564966 Shifris Mar 2008 S
7352289 Harris Apr 2008 B1
7377819 Cooper et al. May 2008 B1
7382765 Kennedy et al. Jun 2008 B2
7401985 Aronson et al. Jul 2008 B2
7406231 Beck et al. Jul 2008 B1
D575743 Shifris et al. Aug 2008 S
7411405 Nordin Aug 2008 B2
7433363 Rosen et al. Oct 2008 B2
7445389 Aronson Nov 2008 B2
7453864 Kennedy et al. Nov 2008 B2
7468669 Beck et al. Dec 2008 B1
7479032 Hoath Jan 2009 B2
7483419 Bullman et al. Jan 2009 B2
7499616 Aronson et al. Mar 2009 B2
7517243 Caveney et al. Apr 2009 B2
7540667 Murano Jun 2009 B2
7547150 Downie et al. Jun 2009 B2
7551456 Behrens et al. Jun 2009 B2
7564795 Stephenson et al. Jul 2009 B2
7586942 Golasky et al. Sep 2009 B2
7605707 German et al. Oct 2009 B2
7616589 Nagata et al. Nov 2009 B2
7617245 De Souza et al. Nov 2009 B2
7667574 Downie et al. Feb 2010 B2
7698156 Martucci et al. Apr 2010 B2
7760094 Kozischek et al. Jul 2010 B1
7772975 Downie et al. Aug 2010 B2
7782202 Downie et al. Aug 2010 B2
7839266 Hoglund et al. Nov 2010 B2
7855697 Chamarti et al. Dec 2010 B2
7856166 Biribuze et al. Dec 2010 B2
7870242 Nguyen Jan 2011 B2
7965186 Downie et al. Jun 2011 B2
8000991 Montagut Aug 2011 B2
8037173 Tuckey et al. Oct 2011 B2
8050939 Graves et al. Nov 2011 B2
8075348 Mei et al. Dec 2011 B2
8092249 German et al. Jan 2012 B2
8099311 La Vecchia et al. Jan 2012 B2
8116434 German et al. Feb 2012 B2
8138925 Downie et al. Mar 2012 B2
8172468 Jones et al. May 2012 B2
8181229 Macauley May 2012 B2
8203450 German et al. Jun 2012 B2
8248208 Renfro, Jr. Aug 2012 B2
8264355 Kozischek et al. Sep 2012 B2
8264366 Chamarti et al. Sep 2012 B2
8643476 Pinn Feb 2014 B2
8768738 Jacobs Jul 2014 B2
20010001270 Williams Vigliaturo May 2001 A1
20010024360 Hirata et al. Sep 2001 A1
20020138604 Kopelvitz et al. Sep 2002 A1
20030046339 Ip Mar 2003 A1
20030061393 Steegmans et al. Mar 2003 A1
20030194912 Ferentz Oct 2003 A1
20030197619 Lawrence et al. Oct 2003 A1
20030219033 Silvester Nov 2003 A1
20040024717 Sneeringer Feb 2004 A1
20040073597 Caveney et al. Apr 2004 A1
20050071514 Anderson et al. Mar 2005 A1
20050164548 Spears et al. Jul 2005 A1
20050186819 Velleca et al. Aug 2005 A1
20050190768 Cutler Sep 2005 A1
20050245127 Nordin et al. Nov 2005 A1
20060047800 Caveney et al. Mar 2006 A1
20060059293 Wurzburg et al. Mar 2006 A1
20060160395 Macauley et al. Jul 2006 A1
20060160396 Macauley et al. Jul 2006 A1
20060179144 Nagase Aug 2006 A1
20060185887 Neujahr Aug 2006 A1
20060203715 Hunter et al. Sep 2006 A1
20060227759 Bohm et al. Oct 2006 A1
20060235741 Deaton et al. Oct 2006 A1
20060253561 Holmeide et al. Nov 2006 A1
20060268507 Takahashi Nov 2006 A1
20060268747 Van Haalen et al. Nov 2006 A1
20060282527 Chiou et al. Dec 2006 A1
20070025306 Cox et al. Feb 2007 A1
20070058338 Lee Mar 2007 A1
20070117444 Caveney et al. May 2007 A1
20070153823 Wojtowicz Jul 2007 A1
20070162954 Pela Jul 2007 A1
20070230452 Hough et al. Oct 2007 A1
20070274234 Kubota Nov 2007 A1
20080049627 Nordin Feb 2008 A1
20080159738 Lavranchuk Jul 2008 A1
20080181136 Watanabe et al. Jul 2008 A1
20080181138 Dalberg Jul 2008 A1
20080219268 Dennison Sep 2008 A1
20080265915 Clark et al. Oct 2008 A1
20090081888 Nordin et al. Mar 2009 A1
20090100298 Lange et al. Apr 2009 A1
20090195349 Frader-Thompson et al. Aug 2009 A1
20090322487 Lange et al. Dec 2009 A1
20100020722 Farkas et al. Jan 2010 A1
20100054157 Farkas et al. Mar 2010 A1
20100120264 Caveney May 2010 A1
20100205032 Nielsen Aug 2010 A1
20100210135 German et al. Aug 2010 A1
20100211664 Raza et al. Aug 2010 A1
20100211665 Raza et al. Aug 2010 A1
20100211697 Raza Aug 2010 A1
20100215049 Raza Aug 2010 A1
20100238003 Chan et al. Sep 2010 A1
20100267274 McNally et al. Oct 2010 A1
20100271961 Caveney Oct 2010 A1
20100271963 Caveney Oct 2010 A1
20110244698 Jacks et al. Oct 2011 A1
20110255611 Caveney et al. Oct 2011 A1
20120007717 Jong Jan 2012 A1
20120084108 Bohannon et al. Apr 2012 A1
20120309211 Jacks et al. Dec 2012 A1
20130128758 Polland May 2013 A1
20130205579 Mather et al. Aug 2013 A1
20130207782 Mather et al. Aug 2013 A1
20130306723 Mather et al. Nov 2013 A1
20140111346 Pinn Apr 2014 A1
Foreign Referenced Citations (10)
Number Date Country
1322356 Nov 2001 CN
1622555 Jun 2005 CN
1809985 Jul 2006 CN
1811743 Aug 2006 CN
101199161 Jun 2008 CN
1569494 Aug 2005 EP
2001297044 Oct 2001 JP
102008017170 Feb 2008 KR
2004105317 Dec 2004 WO
2011057383 May 2011 WO
Non-Patent Literature Citations (57)
Entry
“ID Tag Requirements for Infrastructure and Network Elements Management”, Dec. 2011, pp. 1-32, Publisher: International Telecommunication Union.
Meredith, “Managers Missing Point of Intelligent Patching ”, “http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1099991,00.html”, Jun. 21, 2005, pp. 12, Publisher: SearchDataCenter.com.
Milligan, “Intelligent Patching Systems Carving Out a ‘Large’ Niche”, “http://www.cablinginstall.com/index/display/article-display/207641/articles/cabling-installation-maintenance/volume-12/issue-7/contents/technology/int”, Jul. 1, 2004, pp. 16, vol. 12, No. 7, Publisher: Cabling Installation & Maintenance.
Mirjalily et al. , “Best Multiple Spanning Tree in Metro Ethernet Networks”, “Computer and Electrical Engineering, 2009. ICEE'09. Second International Conference on”, Dec. 28-30, 2009, pp. 117-121, vol. 2, Publisher: IEEE, Published in: Dubai.
Feltgen, “PCT Patent Application PCT/EP2009/009036: Method and Arrangement for Identifying at Least One Object”, Dec. 16, 2009, pp. 125, Published in: WO.
“UPnP Device Architecture 1.1”, Oct. 15, 2008, pp. 1-272, Publisher: UPnP Forum.
European Patent Office, “International Search Report and Written Opinion”, “from PCT Counterpart of U.S. Appl. No. 14/037,871”, dated Dec. 19, 2013, pp. 1-10, Published in: EP.
Chinese Patent Office, “First Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,497”, dated Nov. 2, 2012, pp. 1-34, Published in: CN.
Chinese Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,497”, dated Apr. 24, 2013, pp. 1-10, Published in: CN.
European Patent Office, “Extended European Search Report”, “from Foreign Counterpart of U.S. Appl. No. 12/705,497”, dated Sep. 27, 2012, pp. 1-6, Published in: EP.
Mexican Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,497”, dated Oct. 11, 2013, pp. 1-8, Published in: MX.
U.S. Patent and Trademark Office, “Final Office Action”, “U.S. Appl. No. 12/705,497”, dated Oct. 16, 2012, pp. 1-29.
U.S. Patent and Trademark Office, “Office Action”, “U.S. Appl. No. 12/705,497”, dated Apr. 17, 2012, pp. 1-31.
The International Bureau of WIPO, “International Preliminary Report on Patentability”, “from PCT Application No. PCT/US2010/024181”, dated Aug. 25, 2011, pp. 1-7, Published in: CH.
Korean Intellectual Property Office, “International Search Report”, “from PCT Application No. PCT/US2010/024181”, dated Sep. 28, 2010, pp. 1-10, Published in: KR.
Chinese Patent Office, “First Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,501”, dated Sep. 5, 2012, pp. 1-24, Published in: CN.
Chinese Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,501”, dated Mar. 13, 2013, pp. 1-38, Published in: CN.
State Intellectual Property Office, P.R. China, “Third Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,501”, dated Jul. 31, 2013, pp. 1-7, Published in: CN.
European Patent Office, “Extended European Search Report”, “from Foreign Counterpart of U.S. Appl. No. 12/705,501”, dated Sep. 19, 2012, pp. 1-9, Published in: EP.
European Patent Office, “Extended European Search Report”, “from Foreign Counterpart of U.S. Appl. No. 12/705,501”, dated May 22, 2012, pp. 1-7, Published in: EP.
Mexican Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,501”, dated Oct. 11, 2013, pp. 1-11, Published in: MX.
U.S. Patent and Trademark Office, “Office Action”, “U.S. Appl. No. 12/705,501”, dated Apr. 5, 2013, pp. 1-39.
U.S. Patent and Trademark Office, “Office Action”, “from U.S. Appl. No. 12/705,501”, dated Sep. 24, 2013, pp. 1-18.
U.S. Patent and Trademark Office, “Restriction Requirement”, “U.S. Appl. No. 12/705,501”, dated Dec. 14, 2012, pp. 1-6.
The International Bureau of WIPO, “International Preliminary Report on Patentability”, “from PCT Application No. PCT/US2010/024184”, dated Aug. 25, 2011, pp. 1-7, Published in: CH.
Korean Intellectual Property Office, “International Search Report”, “from PCT Application No. PCT/US2010/024184”, dated Sep. 27, 2010, pp. 1-10, Published in: KR.
European Patent Office, “Extended European Search Report”, “from Foreign Counterpart of U.S. Appl. No. 12/705,506”, dated Oct. 11, 2012, pp. 1-9, Published in: EP.
Mexican Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,506”, dated Oct. 11, 2013, pp. 1-7, Published in: MX.
U.S. Patent and Trademark Office, “Final Office Action”, “U.S. Appl. No. 12/705,506”, dated Dec. 14, 2012, pp. 1-29.
U.S. Patent and Trademark Office, “Office Action”, “U.S. Appl. No. 12/705,506”, dated Jun. 28, 2012, pp. 1-32.
The International Bureau of WIPO, “International Preliminary Report on Patentability”, “from PCTCounterpart of U.S. Appl. No. 12/705,506”, dated Aug. 25, 2011, pp. 1-6, Published in: CH.
International Searching Authority, “International Search Report”, “from Foreign Counterpart of U.S. Appl. No. 12/705,506”, dated Sep. 30, 2010, pp. 1-9, Published in: WO.
Chinese Patent Office, “First Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,514”, dated Sep. 4, 2012, pp. 1-14, Published in: CN.
Chinese Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,514”, dated Mar. 5, 2013, pp. 1-24, Published in: CN.
State Intellectual Property Office, P.R. China, “Third Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,514”, dated Jun. 24, 2013, pp. 1-18, Published in: CN.
European Patent Office, “Extended European Search Report”, “from Foreign Counterpart of U.S. Appl. No. 12/705,514”, dated Oct. 11, 2012, pp. 1-6, Published in: EP.
Mexican Patent Office, “Office Action”, “from Foreign Counterpart of U.S. Appl. No. 12/705,514”, pp. 1-5, Published in: MX.
U.S. Patent and Trademark Office, “Advisory Action”, “U.S. Appl. No. 12/705,514”, dated Nov. 14, 2012, pp. 1-4.
U.S. Patent and Trademark Office, “Final Office Action”, “U.S. Appl. No. 12/705,514”, dated Aug. 23, 2012, pp. 1-20.
U.S. Patent and Trademark Office, “Office Action”, “U.S. Appl. No. 12/705,514”, dated Mar. 15, 2012, pp. 1-25.
U.S. Patent and Trademark Office, “Office Action”, “from U.S. Appl. No. 12/705,514”, dated Sep. 25, 2013, pp. 1-45, Published in: US.
U.S. Patent and Trademark Office, “Pre-Appeal Brief Decision”, “U.S. Appl. No. 12/705,514”, dated Dec. 18, 2012, pp. 1-2.
The International Bureau of WIPO, “International Preliminary Report on Patentability”, “from PCT Counterpart of U.S. Appl. No. 12/705,514”, dated Aug. 25, 2011, pp. 1-6, Published in: CH.
Korean Intellectual Property Office, “International Search Report”, “from PCT Application No. PCT/US2010/024188”, dated Sep. 28, 2010, pp. 1-9, Published in: KR.
U.S. Patent and Trademark Office, “Advisory Action”, “from U.S. Appl. No. 13/248,413”, dated Sep. 30, 2013, pp. 1-3.
U.S. Patent and Trademark Office, “Final Office Action”, “from U.S. Appl. No. 13/248,413”, dated Jul. 18, 2013, pp. 1-15.
U.S. Patent and Trademark Office, “Office Action”, “from U.S. Appl. No. 13/248,413”, dated Dec. 24, 2012, pp. 1-12, Published in: US.
International Searching Authority, “International Search Report”, “from Foreign Counterpart of U.S. Application No.”, dated Feb. 20, 2013, pp. 1-11.
European Patent Office, “International Search Report”, “from PCT Application Serial No. PCT/EP2013/000441”, dated Aug. 21, 2013, pp. 1-15, Published in: WO.
Figueira et al., “10GE WAN PHY: Physical Medium Attachment (PMA)”, “IEEE 802.3 Meeting, Albuquerque”, Mar. 2000, pp. 1-42.
Dimitrov et al. , “Embedded Internet Based System”, 2008, pp. 103-107.
“Embedded Ethernet System Design Guide”, Aug. 2008, Publisher: Silicon Laboratories.
“The Ethersmart Wildcard”, “http://www.mosaic-industries.com/Products/WildCards/ETHx/”, 2008, Publisher: Mosaic Industries, Inc.
Farkas et al. , “Automatic Discovery of Physical Topology in Ethernet Networks”, “Advance Information Networking and Applications, 2008. AINA 2008. 22nd International Conference on”, Mar. 25-28, 2008, pp. 848-854, Publisher: IEEE, Published in: Okinawa.
Feuzeu et al. , “A New Scheme for Interconnecting LANS With Label Switching Bridges”, “Local Computer Networks, 2005. 30th Anniversary. The IEEE Conference on”, Nov. 17, 2005, pp. 303-311, Publisher: IEEE, Published in: Sydney.
“IntelliMAC”, May 2003, pp. 1-6, Publisher: Nordx/CDT.
Kang et al. , “Design and Implementation of Network Management System for Power Line Communication Network ”, “IEEE International Symposium on Power Line Communications and its Applications (ISPLC 2007)”, Mar. 28, 2007, pp. 23-28, Publisher: IEEE.
Related Publications (1)
Number Date Country
20140089028 A1 Mar 2014 US
Provisional Applications (1)
Number Date Country
61706460 Sep 2012 US