Smart City Device Debugging Based on Mobile Applications

Abstract

The invention is titled "Smart City Device Commissioning Based on Mobile Applications". An application running on a mobile device is used to configure multiple smart city devices. A method includes installing a specific smart city device and automatically identifying the geographical location of the specific smart city device by using the location service of the mobile device to identify the current geographical location of the mobile device. Configuration information for the specific smart city device is input using the user interface of the mobile device. The geographical location and configuration information of the specific smart city device are saved in the mobile device. The installation, input, identification, and storage steps are repeated for each smart city device among the multiple smart city devices. The saved geographical location and configuration information for each smart city device among the multiple smart city devices are uploaded from the mobile device to a remote server.

Description

Technical Field

[0001] The present disclosure generally relates to the commissioning of smart city devices. More specifically, the present disclosure relates to the use of a mobile application in the commissioning of smart city devices. Background Art

[0002] A smart city can include a large number of smart city devices such as cameras and other security and sensing devices. Once each of the smart city devices in the smart city is installed, it needs to be configured or commissioned. It should be understood that a smart city can include hundreds or even thousands of smart city devices. Configuring each of these smart city devices can be a long and time-consuming process in which errors can easily occur. When configuring a smart city device, it is important to know the actual installation location of each smart city device and other information about each device. Unfortunately, many smart city devices do not include location services. Even if a command and control (CC) system for the smart city has not been established and is not online, there will be a need for methods and systems for easily configuring each of the installed smart city devices using a mobile device, including the actual installation location. Summary of the Invention

[0003] The present disclosure relates to the use of a mobile application in the commissioning of smart city devices. In one example, a method provides for using an application program running on a mobile device to configure a plurality of smart city devices, the mobile device including a user interface and a memory. The illustrative method includes installing a particular smart city device among the plurality of smart city devices and automatically identifying the geographical location of the particular smart city device by using the location service of the mobile device to identify the current geographical location of the mobile device. Inputting configuration information for the particular smart city device using the user interface of the mobile device. Saving the geographical location and configuration information of the particular smart city device in the mobile device. Repeating the installation, input, identification, and storage steps for each of the plurality of smart city devices. Uploading the saved geographical location and configuration information for each of the plurality of smart city devices from the mobile device to a remote server, sometimes to a command and control (CC) system hosted by the remote server.

[0004] In another example, a method provides for using an application program running on a mobile device to configure a smart city device, the mobile device including a user interface and a memory. The method includes installing the smart city device and capturing configuration information for the smart city device using the user interface of the mobile device. Automatically identifying the GPS location of the smart city device by capturing the current GPS location of the mobile device. Saving the GPS location and configuration information to the memory of the mobile device. Uploading the saved GPS location and configuration information for the installed smart city device to a remote server.

[0005] In another example, a non-transitory computer-readable storage medium stores executable instructions thereon. When the executable instructions are executed by one or more processors of a mobile device, the mobile device is caused to capture configuration information for a smart city device input using the user interface of the mobile device, and to automatically identify the GPS location of the smart city device by capturing the current GPS location of the mobile device. The mobile device is caused to save the GPS location and the configuration information to the mobile device, and to upload the saved GPS location and configuration information for the installed smart city device to a remote server.

[0006] The foregoing Summary is provided to facilitate an understanding of some of the innovative features particular to this disclosure and is not intended to be a complete description. A full understanding of the disclosure may be obtained by taking the entire specification, claims, drawings, and abstract as a whole. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The present disclosure may be more fully understood in connection with the following description of various examples, considered in conjunction with the accompanying drawings, in which:

[0008] Figure 1 is a schematic block diagram of an exemplary smart city system;

[0009] Figure 2 is a flowchart showing an exemplary method of configuring multiple smart city devices;

[0010] Figure 3 is a flowchart showing an exemplary method of configuring multiple smart city devices;

[0011] Figure 4 is a flowchart showing an exemplary method of configuring multiple smart city devices;

[0012] Figure 5 is a flowchart showing an exemplary method of configuring multiple smart city devices;

[0013] Figure 6 is a flowchart showing an exemplary method of configuring multiple smart city devices; and

[0014] Figures 7 to 9 shows a screenshot from an exemplary application running on a mobile device.

[0015] While the present disclosure is subject to various modifications and alternative forms, specific details thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the present disclosure to the particular examples described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure. DETAILED DESCRIPTION

[0016] The following description should be read with reference to the accompanying drawings, in which like elements in different drawings are numbered in the same manner. The drawings are not necessarily to scale and depict examples that are not intended to limit the scope of the disclosure. Although examples of various elements are shown, those skilled in the art will recognize that many of the examples provided have suitable alternatives that can be utilized.

[0017] It is assumed herein that all numbers are modified by the term "about" unless the context clearly dictates otherwise. The recitation of numerical ranges by endpoints includes all numbers subsumed within that range (e.g., 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).

[0018] As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. As used in this specification and the appended claims, the term "or" is generally employed in its sense including "and / or" unless the context clearly dictates otherwise.

[0019] It should be noted that the recitation of "one embodiment," "some embodiments," "other embodiments," etc., in the specification is indicative that the described embodiments may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include that particular feature, structure, or characteristic. Moreover, these phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated that, whether or not explicitly described, that feature, structure, or characteristic may apply to other embodiments unless explicitly stated to the contrary.

[0020] Figure 1 is a schematic block diagram of an exemplary smart city system 10. The exemplary smart city system 10 includes a command and control (CC) server 12 operatively coupled to a plurality of smart city devices 14. The smart city devices 14 are labeled 14a, 14b, and 14c, respectively. Although only three smart city devices 14 are shown, it should be understood that this is merely illustrative, as the smart city system 10 can include any number of smart city devices 14 and may include a substantially greater number of smart city devices 14. Each of the smart city devices 14 can individually represent a camera or other security device such as a microphone or a shot locator, a streetlight sensor, a parking sensor, an automotive sensor, a vehicle tracking device, a trash can detector, etc. Some of the smart city devices 14 can include a separate controller that controls the operation of the smart city device 14. At least some of the smart city devices 14 can be controlled by the CC server 12 and / or can provide operational data to the CC server 12.

[0021] Although the CC server 12 is shown as cloud-based, it need not be. In some cases, the CC server 12 can actually be one or more computer servers or other computing devices operably coupled to multiple smart city devices 14. The CC server can be disposed within or otherwise coupled to a smart city command center (not shown), where individuals track multiple activities within the smart city. For example, individuals can track traffic, noise, crowd and / or mass behavior, air pollution, fires, security issues, and / or other conditions within the smart city. The smart city command center can include a video wall for displaying multiple videos from cameras disposed around the smart city, as well as other collected data and / or alerts. These are just examples.

[0022] When establishing a smart city, each of the smart city devices 14 needs to be installed and configured. Conceivably, configuring the smart city devices 14 can include using a mobile device 16 to determine the actual installation location of each of the smart city devices 14 at the time of its installation, and enabling the installer to manually input multiple configuration settings and parameters using the mobile device 16. Once the mobile device 16 has captured the appropriate configuration information including the installation location for each of the smart city devices 14, the mobile device 16 can upload the captured configuration information to a remote server 18. In some cases, the remote server 18 can ultimately provide the configuration information for each of the smart city devices 14 to the CC server 12. In some cases, a remote server 18 that communicates with but is separate from the CC server 12 can include a machine learning engine 30 and a cloud-based database 32. In some cases, the remote server 18 can actually be part of the CC server 12. The purposes of both the machine learning engine 30 and the cloud-based database 32 will be discussed subsequently.

[0023] For example, the mobile device 16 can be a tablet or a smartphone and can include multiple components that enable the mobile device 16 to be used to assist in configuring the smart city devices 14. For example, the mobile device 16 can include location services 20 that can be used to determine the current geographical location or position of the mobile device 16. By determining the location of the mobile device 16 itself at the time the installer is installing a particular smart device, the application running on the mobile device 16 can determine the installation location of the particular smart city device 14. The location services 20 can include, for example, one or more of a global positioning system (GPS), cellular triangulation between cell towers, Bluetooth beacons, and Wi-Fi beacons.

[0024] In the example shown, the mobile device 16 includes a memory 22. The memory 22 can be used to store configuration information. The memory 22 can be configured to store executable applications that, when executed by the processor 24, cause the mobile device 16 to perform appropriate steps to assist in configuring a plurality of smart city devices 14. The mobile device 16 also includes a user interface 26. The user interface 26 can include a display of the mobile device 16. The mobile device 16 can include a keyboard that is displayed on the display and is touch-sensitive. The mobile device 16 can be sensitive to a person sliding their finger around the displayed keyboard and can largely use this technology when sending text messages. The user interface 26 can include a voice interface that allows a person to input information by talking to the mobile device 16. The mobile device 16 can include a camera, which can be considered part of the user interface 26 because the camera can be used to provide information to the mobile device 16.

[0025] The mobile device 16 also includes a transceiver 28 that allows the mobile device 16 to communicate with other devices. The transceiver 28 can be configured to allow the mobile device 16 to communicate, for example, via a cellular network. In some cases, the transceiver 28 can also be configured to communicate via other wireless communication protocols such as, but not limited to, Bluetooth and / or Wi-Fi. The transceiver 28 can represent two or more different transceivers, each configured to communicate via a different wireless communication protocol.

[0026] An exemplary process for using the mobile device 16 to assist in configuring a plurality of smart city devices 14 includes an installer or other person whose task is to configure each of the plurality of smart city devices 14 to move or otherwise be in proximity to a particular smart city device 14. It should be understood that the plurality of smart city devices 14 can all be configured by a single installer using a single mobile device 16. In some cases, the plurality of smart city devices 14 can be divided into groups, where each group is assigned to a particular installer with their own mobile device 16. In either case, the installer uses the mobile device 16 to determine the current location of the mobile device 16, and thus an application running on the mobile device 16 can capture this current location and assign it as the actual installation site or location of a particular smart city device 14.

[0027] Then, the installer can use the user interface 26 of the mobile device 16 to input additional configuration details such as but not limited to the name of a specific smart city device 14, the IP address of the specific smart city device 14, the media access control (MAC) address of the specific smart city device 14, and any other desired details. The mobile device 16 can store the configuration details of the specific smart city device 14 in the memory 22 of the mobile device 16 until such time as the mobile device 16 is able to communicate with the remote server 18. This allows for the configuration of the smart city device 14 without the need for, for example, immediate access to the network of the remote server 18 and / or before the remote server 18 and / or the CC server 12 is able to accept information. In some cases, the mobile device 16 can communicate with the specific smart city device 14 being installed via, for example, Bluetooth and / or Wi-Fi. When so provided, at least some of the configuration information (e.g., IP address) collected by the mobile device can be sent to the specific smart city device 14 to configure the smart city device.

[0028] Figure 2 FIG. 4 is a flow chart illustrating an exemplary method 40 for configuring a plurality of smart city devices (such as smart city device 14) using an application running on a mobile device (such as mobile device 16). In some cases, at least some of the smart city devices can be security cameras or access control devices. As indicated at block 42, the exemplary method 40 includes installing a specific smart city device among the plurality of smart city devices. As indicated at block 44, the geographical location of the specific smart city device is automatically identified by using the location services of the mobile device to identify the current geographical location of the mobile device. The location services of the mobile device can use one or more of GPS, cellular triangulation, Bluetooth, and Wi-Fi to identify the current geographical location of the mobile device and thus identify the geographical location of the specific smart city device. In some cases, the geographical location is a GPS location.

[0029] As indicated at block 46, configuration information for the specific smart city device is input using the user interface of the mobile device (such as user interface 26). As indicated at block 48, the geographical location and configuration information of the specific smart city device are saved in the mobile device. The configuration information for the specific smart city device can include, for example, one or more of the following: device name, device type, MAC address, IP address, installer notes, image upload from the specific smart city device (e.g., via a wired, Bluetooth, or Wi-Fi connection to the specific smart city device), video upload from the specific smart city device, audio upload from the specific smart city device, device-specific test data, and one or more details about the installer of the specific smart city device (e.g., installer name, installer contact information, vendor name, etc.).

[0030] At decision block 50, it is determined whether all of the smart city devices have been configured. For example, this determination may be made by a user. If not, control returns to block 42 and the process continues with the installation of another smart city device. However, if at decision block 50 it is determined that all of the smart city devices have been configured, then control passes to block 52, where the saved geographical location and configuration information for each of the multiple smart city devices is uploaded from the mobile device to a remote server (such as remote server 18). In some cases, the installation step (block 42), the automatic identification step (block 44), the input step (block 46), and the save step (block 48) may be performed for each of the smart city devices before the remote server 18 is online or otherwise available to receive the uploaded information. In some cases, the saved geographical location and configuration information is uploaded to the remote server 18 before moving on to the next smart city device. In some cases, the upload step (block 52) occurs when the mobile device is connected to the remote server via a wide area network (WAN). These are merely examples.

[0031] Figure 3 FIG. 6 is a flowchart of an illustrative method 60 for configuring multiple smart city devices (such as smart city device 14) using an application running on a mobile device (such as mobile device 16). In some cases, at least some of the smart city devices may be security cameras or access control devices. As indicated by block 62, the illustrative method 60 includes installing a particular smart city device of the multiple smart city devices. As indicated by block 64, the geographical location of the particular smart city device is automatically identified by using the location services of the mobile device to identify the current geographical location of the mobile device. The location services of the mobile device may use one or more of GPS, cellular triangulation, Bluetooth, and Wi-Fi to identify the current geographical location of the mobile device and thus identify the geographical location of the particular smart city device. In some cases, the geographical location is a GPS location.

[0032] As indicated by block 66, configuration information for the particular smart city device is input using the user interface of the mobile device (such as user interface 26). As indicated by block 68, the geographical location and configuration information of the particular smart city device are saved in the mobile device. The configuration information for the particular smart city device may include, for example, one or more of the following: device name, device type, MAC address, IP address, installer notes, image upload from the particular smart city device, video upload from the particular smart city device, audio upload from the particular smart city device, device-specific test data, and one or more details about the installer of the particular smart city device.

[0033] At decision block 70, it is determined whether all the smart city devices have been configured. For example, this determination can be made by a user. If not, control returns to block 62 and the process continues with the installation of another smart city device. However, if at decision block 70 it is determined that all the smart city devices have been configured, then control passes to block 72 where the saved geographical location and configuration information for each of the multiple smart city devices is uploaded from the mobile device to a cloud-based database (such as cloud-based database 32) accessible by a remote server (such as remote server 18).

[0034] In some cases, the installation step (block 62), the automatic identification step (block 64), the input step (block 66), and the save step (block 68) can be performed for each of the smart city devices before the remote server 18 (and / or the cloud-based database 32) is online or otherwise available to receive the uploaded information. In some cases, the saved geographical location and configuration information is uploaded to the cloud-based database 32 before moving on to the next smart city device. In some cases, the upload step (block 72) occurs when the mobile device is connected to the remote server via a wide area network (WAN). The multiple smart city devices can be divided into multiple groups, where different users are assigned to each group, where each user uses a different mobile device to configure each of the smart city devices within their assigned group, and where different users upload the saved geographical location and configuration information for each of their respective smart city devices to the cloud-based database.

[0035] As indicated at block 74, method 60 continues by processing the geographical location and configuration information uploaded from the mobile device to the cloud-based database to identify missing geographical location and / or configuration information. As indicated at block 76, the missing geographical location and / or configuration information can be supplemented in the cloud-based database. In some cases, the missing geographical location and / or configuration information can be highlighted for an operator to supplement the missing geographical location and / or configuration information in the cloud-based database. In some cases, the missing geographical location and / or configuration information can be identified via a machine learning engine (such as machine learning engine 30). At least some of the missing geographical location and / or configuration information can be automatically supplemented via the machine learning engine.

[0036] Figure 4It is a flowchart showing an exemplary method 80 of configuring multiple smart city devices (such as smart city device 14) using an application running on a mobile device (such as mobile device 16). In some cases, at least some of the smart city devices can be security cameras or access control devices. As indicated by block 82, the exemplary method 80 includes installing a specific smart city device among the multiple smart city devices. As indicated by block 84, the geographical location of the specific smart city device is automatically identified by using the location service of the mobile device to identify the current geographical location of the mobile device. The location service of the mobile device can use one or more of GPS, cellular triangulation, Bluetooth, and Wi-Fi to identify the current geographical location of the mobile device, and thus identify the geographical location of the specific smart city device. In some cases, the geographical location is a GPS location.

[0037] As indicated by block 86, configuration information for the specific smart city device is input using the user interface of the mobile device (such as user interface 26). As indicated by block 88, the geographical location and configuration information of the specific smart city device are saved in the mobile device. The configuration information for the specific smart city device can include, for example, one or more of the following items: device name, device type, MAC address, IP address, installer notes, image upload from the specific smart city device, video upload from the specific smart city device, audio upload from the specific smart city device, device-specific test data, and one or more details about the installer of the specific smart city device.

[0038] At decision block 90, it is determined whether all smart city devices have been configured. For example, this determination can be made by the user. If not, control returns to block 82, and the process continues to install another smart city device. However, if at decision block 90 it is determined that all smart city devices have been configured, then control goes to block 92, where the saved geographical location and configuration information for each smart city device among the multiple smart city devices are uploaded from the mobile device to a cloud-based database (such as cloud-based database 32) accessible by a remote server (such as remote server 18).

[0039] In some cases, the installation step (block 82), the automatic recognition step (block 84), the input step (block 86), and the saving step (block 88) can be performed for each smart city device in the smart city devices before the remote server 18 (and / or the cloud-based database 32) is online or otherwise available to receive the uploaded information. In some cases, the saved geographical location and configuration information are uploaded to the cloud-based database 32 before moving on to the next smart city device. In some cases, the uploading step (block 92) occurs when the mobile device is connected to the remote server via a wide area network (WAN). Multiple smart city devices can be divided into multiple groups, where different users are assigned to each group, where each user uses a different mobile device to configure each smart city device within their assigned group, and different users upload the saved geographical location and configuration information for each smart city device within their respective smart city devices to the cloud-based database.

[0040] As indicated by block 94, the method 80 continues by processing the geographical location and configuration information uploaded to the cloud-based database such that the geographical location and configuration information (the geographical location and configuration information for each smart city device in the smart city devices can be in any of a plurality of formats (e.g., plain text file, CSV file, custom format, Json / xml, etc.)) is in a common format. The geographical location and configuration information now in the common format (e.g., Json / xml) can be accessed using a command and control (CC) system (such as the CC system 10), which is configured to assist an operator in monitoring and / or controlling at least some of the installed smart city devices.

[0041] Figure 5 is a flowchart showing an exemplary method 100 for configuring a smart city device (such as the smart city device 14) using an application running on a mobile device (such as the mobile device 16), where the mobile device includes a user interface (such as the user interface 26) and a memory (such as the memory 22). As indicated by block 102, the smart city device is installed. As indicated by block 104, configuration information for the smart city device is captured using the user interface of the mobile device. As indicated by block 106, the GPS location of the smart city device is automatically recognized by capturing the current GPS location of the mobile device. As indicated by block 108, the GPS location and the configuration information are saved to the memory of the mobile device. As indicated by block 110, the saved GPS location and configuration information for the installed smart city device are uploaded to a remote server (such as the remote server 18).

[0042] In some cases, automatically capturing the GPS location of a mobile device (block 106) can include displaying a map including a pointer on the user interface of the mobile device, the pointer indicating the current location of the mobile device and allowing the user to adjust the position of the pointer relative to the map when the displayed position of the pointer is inaccurate. Method 100 can include capturing the GPS location of the mobile device based on the displayed position of the pointer (which may have been corrected). For example, this is shown in Figure 7 as shown. In some cases, capturing configuration information for a smart city device using the user interface (block 104) can include displaying a screen that allows the user to enter parameter and parameter value pairs and then accepting the input name of the parameter and the parameter value of the parameter. For example, this is shown in Figure 8 as shown.

[0043] In some cases, and as indicated by block 112, method 100 can also include displaying a screen on the user interface that includes a "Local" button and a "Cloud" button. When the "Local" button is selected, the GPS location and configuration information for the smart city device can be saved to the memory of the mobile device. When the "Cloud" button is selected, the GPS location and configuration information for the smart city device can be uploaded to a cloud-based database (such as cloud-based database 32). In some cases, method 100 can also include displaying an "Add Another Device" button that, when selected, allows the user to configure another smart city device. Once the configuration of the smart city device is completed by selecting the "Local" button or the "Cloud" button, the user can select the "Add Another Device" button. For example, these features are shown in Figure 9 as shown.

[0044] Figure 6 is a flowchart showing an exemplary method 120 for installing and configuring one or more smart city devices. Exemplary method 120 begins at starting point 122. At block 124, a user such as but not limited to a field commissioning engineer logs into an application on their mobile device. As noted, any number "n" of field commissioning engineers can install and commission smart city devices simultaneously, as indicated by the field commissioning engineer number n logged in at block 124a. While the remainder of method 120 will be discussed simply with respect to a single field commissioning engineer, it should be recognized that multiple field commissioning engineers can perform each of the methods described as they move around the city installing and configuring smart city devices. As indicated by block 126, the field commissioning engineer installs and sets up the smart city device.

[0045] Next, as indicated by block 128, a field commissioning engineer manually inputs multiple different configuration information into the mobile device. The configuration information can include any information that the CC system 10 can communicate with a specific smart city device appropriately, learning how to identify information from a specific smart city device and how to (optionally) control the operation of a specific smart city device. Examples include but are not limited to the name of the smart city device, the type of the smart city device, the model number of the smart city device, the IP address of the smart city device, the MAC id of the smart city device, the upload of any appropriate image file, video file, and / or audio file, device type and vendor details. At block 130, the application running on the mobile device automatically captures the GPS coordinates of the smart city device.

[0046] At decision block 132, it is determined whether the mobile device is online. If the mobile device is not online, the control goes to block 134, where the configuration information input by the field commissioning engineer and the captured GPS coordinates of the specific smart city device are saved in the memory of the mobile device. However, if the mobile device is online, the control goes to block 136, and the configuration information input by the field commissioning engineer and the captured GPS coordinates of the specific smart city device are uploaded in their original format to a cloud-based database (such as the cloud-based database 32). It should be understood that, as indicated by block 136a, multiple different details (including vendor details (e.g., the vendor whose field commissioning engineer installed the specific smart city device)) can be included in the information uploaded to the cloud-based database. It should be understood that once the mobile device is online, any locally saved configuration information and captured GPS coordinates will be synchronized to the cloud-based database.

[0047] At decision block 140, it is determined whether the required data is available. This determination can be made by the remote server 18 and can include the machine learning engine 30 in some cases. If the required data is not available, the control goes to block 142, and any missing information can be manually input (or automatically input via the machine learning engine 30). Once the missing information has been input, or if it is determined at decision block 140 that all the required information exists, the control goes to block 144, where the rule engine converts the data of each vendor into an acceptable format for use by the CC system 10. Then, as indicated by block 146, the processed data is imported into the CC system 10. In some cases, the machine learning engine 30 can be used to determine what information is missing. For example, if a camera device does not have an IP address or lacks credential data, these fields can be highlighted by the system. In some cases, machine learning-based automatic device normalization can be enabled. For example, a vendor (e.g., one of the vendors whose field commissioning engineer installed the smart city device) can provide data in the x format, and the system can automatically convert the data to the y format.

[0048] Figures 7 to 9 Shows a screenshot from an exemplary application running on a mobile device. Figure 7 Shows screen 150, which can be regarded as a start screen. Screen 150 includes a map 152 that shows an area adjacent to where a particular smart city device is to be installed or has been installed and is waiting to be configured. Map 152 includes a pointer 154 indicating the current position of the mobile device relative to map 152. If the user believes the current position is not correctly indicated, they can adjust the position of pointer 154 relative to map 152 such that the application will capture the adjusted position. The GPS coordinates corresponding to the position of pointer 154 (whether adjusted or not) will be displayed in boxes 154a (latitude) and 154b (longitude).

[0049] The device name box 156 allows the user to enter a device name for a particular smart city device. The device name can be created by the user (e.g., a field commissioning engineer). In some cases, the device name may be automatically filled based on the current position and a map of the planned device locations stored in the mobile device. If appropriate, the MAC id box 158 can display an automatically generated value that can be overridden by the user. In some cases, the MAC id can be automatically filled by scanning a barcode on a particular smart device and / or downloading the MAC id from a particular smart device via Bluetooth, Wi-Fi, or other connections. The comment box 160 allows the user to enter any appropriate comments. The toolbar 162 allows the user to add attachments by capturing a picture (162a), a video (162b), or adding any attachment from the device (162c). If selected, the forward button 164 allows the user to move to the next screen.

[0050] Figure 8 Shows screen 170, which allows the user to add configuration information for a particular smart city device that is currently being configured. It should be understood that the configuration information can be added as parameter and parameter value pairs. For illustration, the first pair 172 includes a parameter name 172a (IP address) and a parameter value 172b (X.X.X.X). The second pair 174 includes a parameter name 174a (key) and a parameter value 174b (value). Additional pairs can be added by selecting the plus button 176. A pair can be removed by highlighting the pair and selecting the minus button 178. The back button 180 allows the user to return to a previous screen such as screen 150, while the forward button 182 allows the user to move to a subsequent screen.

[0051] Figure 9Shown is screen 190, which allows a user to locally save configuration information or upload configuration information on a mobile device. Screen 190 includes a "Local" button 192 and a "Cloud" button 194. By selecting the "Local" button 192, an application running on the mobile device will locally save the configuration information including the GPS location within the memory of the mobile device itself for subsequent upload to the cloud. By selecting the "Cloud" button 194, the application running on the mobile device is caused to upload the device data to the cloud. It is conceivable that if the mobile device is not online, the "Cloud" button 194 can be grayed out as unavailable.

[0052] Screen 190 includes a message 196 (Success), which notifies the user of successful local saving of data (if the "Local" button 192 is selected) or successful upload to the cloud (if the "Cloud" button 194 is selected). If there is a problem, the message 196 can alternatively display "Error" or any other appropriate message. In such a case, the user may be able to try again or try to change their selection. If they had initially selected the "Cloud" button 194, they can try to upload to the cloud again, or they can change their selection and alternatively select the "Local" button 192. This is just an example.

[0053] If selected, the back button 198 allows the user to return to a previous screen such as screen 150 or screen 170. The "Add Another Device" button 200 allows the user to proceed with a particular smart city device, continue their work, and move on to another smart city device. Then, the application running on the mobile device can return to the start screen (such as screen 150 as Figure 7 shown) for configuring the next smart city device. The next smart city device can be nearby, or the next smart city device can be in another part of the city.

[0054] Although several illustrative embodiments of the present disclosure have been so described, those skilled in the art will readily appreciate that other embodiments can be made and used within the scope of the appended claims herein. However, it should be understood that the present disclosure is illustrative in many respects. Changes can be made to the details (especially details related to the shape, size, arrangement of parts, and exclusion and order of steps) without exceeding the scope of the present disclosure. Of course, the scope of the present disclosure is defined in the language of the appended claims.

Claims

1. A method of configuring multiple smart city devices using an application running on a mobile device, the mobile device including a user interface and a memory, the method comprises: installing a specific smart city device among the multiple smart city devices; automatically identifying the geographical location of the specific smart city device by using the location service of the mobile device to identify the current geographical location of the mobile device, wherein the location service of the mobile device uses one or more of GPS, cellular triangulation, Bluetooth, and Wi-Fi to identify the current geographical location of the mobile device and thus identify the geographical location of the specific smart city device; manually inputting, by a user, configuration information for the specific smart city device using the user interface of the mobile device, the configuration information including one or more of a device name, a device type, an IP address, and an installer note for the specific smart city device; sending at least some of the configuration information to the specific smart city device to configure the specific smart city device; saving the geographical location and the configuration information of the specific smart city device in the mobile device; repeating the installation, input, identification, and storage steps for each smart city device among the multiple smart city devices; and uploading the saved geographical location and the configuration information for each smart city device among the multiple smart city devices from the mobile device to a remote server.

2. The method according to claim 1, wherein the saved geographical location and the configuration information are uploaded from the mobile device to a cloud-based database accessible by the remote server, and wherein the geographical location and the configuration information for each smart city device are stored in the cloud-based database in one of a plurality of formats, and wherein the remote server is configured to process the geographical location and the configuration information uploaded to the cloud-based database such that the geographical location and the configuration information for each smart city device are in a common format.

3. The method according to claim 2, further comprising accessing the geographical location and the configuration information in the common format using a command and control (CC) system, the CC system being configured to assist an operator in monitoring and / or controlling at least some of the installed smart city devices.

4. The method according to claim 1, further comprises: saving the geographical location and the configuration information to a cloud-based database accessible by the remote server; processing the geographical location and the configuration information in the cloud-based database to identify missing geographical location and / or configuration information; and supplementing the missing geographical location and / or configuration information in the cloud-based database.

5. The method according to claim 4, wherein the missing geographical location and / or configuration information is highlighted for an operator to supplement the missing geographical location and / or configuration information in the cloud-based database.

6. The method according to claim 4, wherein the missing geographical location and / or configuration information is identified and / or supplemented via a machine learning engine.

7. The method according to claim 1, wherein the saved geographical location and the configuration information are uploaded from the mobile device to a cloud-based database accessible by the remote server, and wherein the plurality of smart city devices are divided into a plurality of groups so that a plurality of users can simultaneously perform the installation and commissioning work of the smart city devices, wherein each of the plurality of users uses a different mobile device, and the method includes assigning different users among the plurality of users to each group of the plurality of smart city devices; each of the plurality of users using its corresponding mobile device to configure each smart city device within its assigned group; and each of the plurality of users uploading the saved geographical location and the configuration information of each smart city device in its respective smart city devices from its corresponding mobile device to the cloud-based database.

8. The method according to claim 1, wherein the configuration information for the specific smart city device includes one or more of the following items: MAC address, image upload from the specific smart city device, video upload from the specific smart city device, device-specific test data, and one or more details about the installer of the specific smart city device.

9. A non-transitory computer-readable storage medium having executable instructions stored thereon, the executable instructions, when executed by one or more processors of a mobile device, cause the mobile device to: capture configuration information for a smart city device manually input using a user interface of the mobile device, the configuration information including one or more of a device name, a device type, an IP address, and an installer note for a specific smart city device; automatically identify the GPS location of the smart city device by capturing the current GPS location of the mobile device; save the GPS location and the configuration information to the mobile device; and upload the saved GPS location and the configuration information for the installed smart city device to a remote server.

Images