Methods and systems for allowing devices to send and receive data

Abstract

A method and system for configuring an electronic device by a management device is disclosed. When the management device is coupled to the electronic device and the electronic device is unable to communicate with a server, the method and system detect an identity of the electronic device and configure the electronic device with a configuration based on the identity. The configuration can also include authentication information, routing policy, energy policy, and any information for configuring the electronic device or for configuring the management device that configures the electronic device. The method and system also allow the electronic device to send and receive data to and from the server through the management device. The method and system can also diagnose the electronic device before configuring the electronic device.

Description

[0001] This application is a divisional application of patent application No. 2020800088533, filed on December 28, 2020, entitled "Method and System for Allowing a Device to Transmit and Receive Data". Technical Field

[0002] This disclosure generally relates to the field of computer networks. More specifically, this disclosure relates to a method and system in which a management device utilizes configuration to configure an electronic device and particularly provides connectivity to the electronic device in order to address problems of the electronic device. Background Technology

[0003] It is common for any electronic device (such as a computing device, networked device, mobile phone, or Internet of Things (IoT) device) to fail to function correctly. Electronic devices may have one or more problems, such as hardware issues, software issues, and firmware issues. In some cases, the problem may be external to the electronic device, such as a network issue. Furthermore, users may not be able to describe, identify, or resolve the problem.

[0004] Some manufacturers or companies attempt to resolve issues by requiring users to download software or allow remote troubleshooting. However, such downloads and remote troubleshooting can be difficult to perform when the electronic device cannot connect to the internet.

[0005] In another scenario, hardware problems such as temperature issues and sensor malfunctions may occur at the electronic device. This could prevent the device from starting. In this case, the user must manually check the hardware and / or software of the electronic device. However, the user may be unable or unwilling to perform the check. Summary of the Invention

[0006] According to one embodiment, a method and system are provided for configuring an electronic device via a management device. When the management device is coupled to the electronic device and the electronic device cannot communicate with a server, this method and system detects an identifier of the electronic device and configures the electronic device using a configuration based on the identifier. The configuration may further include authentication information, routing policies, energy policies, and any information about the management device used to configure the electronic device. According to one embodiment, the method and system also allow the electronic device to send data to and receive data from the server via the management device. According to one embodiment, the method and system may also diagnose the electronic device before configuring it.

[0007] The identification of the electronic device can be based on the International Mobile Equipment Identity (IMEI) and / or the International Mobile Subscriber Identity (IMSI). The method and system can communicate with a SIM card pool / SIM bank to retrieve one or more IMSIs of one or more SIM cards. One or more SIM cards are coupled to one or more SIM card slots in the SIM card pool. Attached Figure Description

[0008] To gain a more complete understanding of this disclosure and its advantages, the following description is now taken in conjunction with the accompanying drawings, in which the same reference numerals denote the same parts: Figure 1 Network environments according to various embodiments of this disclosure are shown; Figure 2A This is a block diagram illustrating the components of a management device according to one embodiment of the present disclosure; Figure 2B This is a block diagram illustrating the components of an electronic device according to one embodiment of the present disclosure; Figure 2C This is a block diagram illustrating components of another variation of an electronic device according to one embodiment of the present disclosure; Figure 3 This is a block diagram illustrating the software layout of a management device according to one embodiment of the present disclosure; Figure 4 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 5 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 6 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 7 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 8 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 9 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 10 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 11 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 12 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 13 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 14 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 15 This is a flowchart illustrating a process according to one embodiment of the present disclosure; Figure 16 Network environments according to various embodiments of this disclosure are shown; Figure 17 This is a flowchart illustrating a process according to one embodiment of the present disclosure; and Figure 18 This is a flowchart illustrating one of the embodiments of the present disclosure. Detailed Implementation

[0009] First, it should be understood that although exemplary embodiments are shown in the accompanying drawings and described below, the principles of this disclosure can be implemented using any number of techniques, whether currently known or unknown. This disclosure should in no way be limited to the exemplary embodiments and techniques shown in the accompanying drawings and described below. Furthermore, unless otherwise specifically indicated, the items depicted in the accompanying drawings are not necessarily drawn to scale.

[0010] Figure 1 Network topologies according to various embodiments of this disclosure are illustrated. Electronic device 116 can be any type of electronic device, such as... Figure 2B Electronic device 116A or Figure 2C Electronic device 116B. The electronic device may be a refrigerator, air conditioner, computing device, mobile phone, or Internet of Things (IoT) device. Electronic device 116 may have an interface that allows it to connect to a network such as the Internet 105 or a computing device such as management device 117.

[0011] When electronic device 116 has one or more problems, such as software problems, hardware problems and other problems, electronic device 116 may not be able to connect to the Internet 105.

[0012] In one variant, the electronic device (e.g., electronic device 116) may have the problem of not being able to connect to the Internet 105 itself. Electronic device 116 can be connected and configured using out-of-band management technology. Even if electronic device 116 is turned off, in sleep mode, hibernating, or the network is off, electronic device 116 can still be managed through a management interface. Management device 117 can connect to electronic device 116 using its management port, serial port, or console port. Management device 117 then establishes a connection with electronic device 116, such as connection 115. In this variant, management device 117 can connect to the Internet 105 itself and resolve the problems of electronic device 116.

[0013] In another variation, electronic device 116 can be managed using in-band. Electronic device 116 can be managed via a network such as the Internet 105 using common protocols such as Remote Login, Secure Shell (SSH), and Simple Network Management Protocol (SNMP). Management device 117 can be connected to electronic device 116 via connection 115 using its network port, parallel port, or Universal Serial Bus (USB) port. In this variation, electronic device 116 is configured when management device 117 is connected or coupled via connection 115. Therefore, electronic device 116 can establish a connection with the Internet 105 via management device 117 using connections 115 and 114.

[0014] Connection 115 can be a wireless or wired connection. Connection 115 can be established using a management port, serial port, console port, Ethernet, USB connection, Near Field Communication (NFC) technology, Bluetooth, Wi-Fi Direct, or other communication technologies. There are no restrictions on the type of interface or the type of connection used to connect to electronic device 116. Connection 114 can be a wireless or wired connection and can be established, such as Ethernet cable, DSL, T1, Wi-Fi, General Packet Radio Service (GPRS), Enhanced Data Rate Evolution of GSM (EDGE), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), or 5G.

[0015] In another variation, an electronic device (such as electronic device 116) can be directly connected to the Internet 105. However, electronic device 116 may have issues with proper operation. A management device (such as management device 117) can be connected to electronic device 116 via connection 115. Furthermore, management device 117 can be connected to the Internet 105 itself via connection 114.

[0016] In another variation, management device 117 is used for electronic device 116, which establishes a connection with Internet 105 through management device 117. Therefore, electronic device 116 can then connect to Internet 105 via a connection established using management device 117.

[0017] Management server 104 may be a security server, which may belong to and be maintained by a user or administrator of management server 104. Management server 104 may communicate with management device 117 to provide support and configuration for resolving problems found at electronic device 116.

[0018] Enterprise server 102 is a server that may belong to and be maintained by an enterprise. Enterprise server 102 provides support and configuration to electronic device 116 directly or through management device 117. Alternatively, management device 117 communicates with enterprise server 102 to request support and retrieve the configuration of electronic device 116 when needed.

[0019] Server 103 is a remote server. After being successfully configured with a configuration derived from enterprise server 102, electronic device 116 can communicate with server 103 via management device 117. In one variant, electronic device 116 communicates directly with server 103 without going through management device 117. In another variant, management device 117 communicates directly with server 103.

[0020] Management server 104 and server 103 are connected to the Internet 105 via connections 111 and 110, respectively. Enterprise server 102 is connected to the Internet 105 via intranet 106 using connections 109 and 112. Connections 109 to 112 may be of the same or different type as connection 114. Enterprise server 102 is connected to the Internet 105 via intranet 106.

[0021] In one variant, management device 117 retrieves configuration information for electronic device 116 from management server 104 or enterprise server 102. In this variant, electronic device 116 may not be able to communicate with management server 104 or enterprise server 102 to request support and configuration. In another variant, electronic device 116 retrieves configuration information from management server 104 or enterprise server 102 via management device 117. Alternatively, electronic device 116 communicates directly with management server 104 or enterprise server 102 to request support and configuration. This configuration is used to configure electronic device 116. Enterprise server 102 provides support and configuration based on the identification information of electronic device 116. Management server 104 provides support and configuration based on the identification information of management device 117. Alternatively, management server 104 provides support and configuration via management device 117, based on the identification of electronic device 116.

[0022] Subscriber Identity Module (SIM) pool 119 is an electronic device comprising multiple SIM card slots. Each SIM card slot can be coupled to one SIM card. Therefore, an International Mobile Equipment Identity (IMEI) is linked to each of the multiple SIM card slots. SIM cards may originate from different telecommunications companies. A management device 117 communicates with SIM card pool 119 to retrieve the International Mobile Subscriber Identity (IMSI) of the SIM cards coupled to the multiple SIM card slots. SIM card pool 119 is connected to the Internet 105 via at least one connection (such as connection 118). The IMSI includes a set of radio network identification values, such as Mobile Country Code (MCC), Mobile Network Code (MNC), and Mobile Subscriber Identification Number (MSIN). Alternatively, electronic device 116 may retrieve the IMSI via management device 117. Electronic device 116 uses the IMSI to establish one or more cellular connections. Management device 117 forwards authentication requests received from the corresponding telecommunications company service to SIM card pool 119 for use with the IMSI. The management device 117 then forwards the authentication response received from the SIM card pool 119 to the corresponding telecommunications company service of the SIM card's IMSI. Therefore, the management device 117 maintains the connection established for the electronic device 116 using the SIM card's IMSI. The SIM card pool 119 includes one or more Universal Integrated Circuit Cards (UICCs) for one or more SIM cards. Furthermore, a UMTS Subscriber Identity Module (USIM), a Mobile Subscriber Identity Module (RUIM), or a CDMA Subscriber Identity Module (CSIM) may be used with the UICC instead of the SIM card described in this disclosure. Additionally, the SIM card pool 119 may also include one or more Embedded Universal Integrated Circuit Cards (eUICCs) for one or more Embedded Universal Integrated Circuit Cards (eSIMs). The eSIM profile corresponding to the eSIM can be retrieved from the SIM card pool 119 by the electronic device 116 and the management device 117.

[0023] Figure 2A A block diagram of the components of management device 117 is shown. When electronic device 116 uses out-of-band management, it can use a management port, serial port, console port, network port, parallel port, Ethernet port, Power over Ethernet (PoE), or USB port as device interface 201 to connect to electronic device 116. Alternatively, device interface 201 can be implemented using NFC, Bluetooth, Wi-Fi, or other wireless communication technologies for connecting to electronic device 116. There are no limitations on the number and type of device interface 201. When electronic device 116 uses in-band management, remote login, SSH, or SNMP can be used to connect to electronic device 116 via device interface 201 through a network such as the Internet 105.

[0024] Management device 117 includes multiple network interfaces, such as network interfaces 210a and 210b. Each of network interfaces 210a and 210b can be an Ethernet interface, Frame Relay interface, fiber optic interface, cable interface, Digital Subscriber Line (DSL) interface, Token Ring interface, serial bus interface, USB interface, FireWire interface, or Peripheral Component Interconnect (PCI) interface. Management device 117 connects to the Internet 105 using one or more of network interfaces 210a and 210b. There is no limitation on the number and type of network interfaces 210a and 210b. Network interfaces 210a and 210b can be configured as local area network (LAN) network interfaces or wide area network (WAN) network interfaces. For example, network interface 210a can be a LAN network interface, while network interface 210b can be a WAN network interface. In another example, both network interfaces 210a and 210b are WAN network interfaces.

[0025] The management device 117 may also include a plurality of cellular modems 206a and 206b, a Wi-Fi module 202, and a Global Positioning System (GPS) module 203. The plurality of cellular modems 206a and 206b are used for cellular connectivity, such as GPRS, EDGE, UMTS, LTE, 4G, and 5G. The management device 117 is capable of connecting to the Internet 105 via one or more cellular modems 206a and 206b. Each cellular modem 206a and 206b includes one or more SIM card slots for coupling SIM cards. Therefore, the IMEI is linked to each of the one or more SIM card slots. It should be noted that those skilled in the art will understand that each of the plurality of cellular modems 206a and 206b may include one or more UICCs instead of one or more SIM cards. Furthermore, USIM, RUIM, or CSIM may be used with UICCs instead of the SIM cards described in this disclosure.

[0026] Multiple cellular modems 206a and 206b are capable of using one or more eUICCs for one or more eSIMs. Management device 117 can connect to an IEEE 802.11 access point using a Wi-Fi module, such as Wi-Fi module 202. Management device 117 can also use Wi-Fi module 202 to create a Wi-Fi network or hotspot. A GPS sensor, such as GPS module 203, is used to discover the location of management device 117. Electronic device 116 may be in a specific area and may require a specific configuration provided by the enterprise of electronic device 116 based on that specific area. Management device 117 can then retrieve the specific configuration of electronic device 116 by using one or more cellular modems 206a and 206b or Wi-Fi module 202.

[0027] The management device 117 also includes a processing unit 204, a main memory 205, an auxiliary memory 207, and a system bus 212. The management device 117 may also optionally include a help button 208, a liquid crystal display (LCD) 209, and a light-emitting diode (LED) 211. The help button 208, the LCD status 209, and the LED 211 can be used for operation and operation indication of the management device 117.

[0028] Processing unit 204 is directly connected to main memory 205. Processing unit 204 is also connected via system bus 212 to Wi-Fi module 202, GPS module 203, cellular modem 206, secondary storage 207, device interface 201, and network interfaces 210a and 210b. Processing unit 204 controls all operations and functions of management device 117. Help button 208 can be optionally used by a user or administrator. For example, when management device 117 is connected to or coupled to electronic device 116, a user or administrator can use help button 208 to begin diagnosing electronic device 116, allowing management device 117 to detect problems. Processing unit 204 can also indicate the functions and operations of management device 117 using LCD status 209 and LED 211.

[0029] The following restrictions do not apply: the management device 117 must have multiple cellular modems 206a and 206b, multiple network interfaces 210a and 210b, device interface 201, Wi-Fi module 202, GPS module 203, help button 208, LCD status 209, and LED 211.

[0030] For example, management device 117 may not have any of the following: network interfaces 210a and 210b, cellular modem 206b, device interface 201, Wi-Fi module 202, GPS module 203, help button 208, LCD status 209, and LED 211. In this example, management device 117 is able to connect to the Internet 105 via cellular modem 206a. Then, management device 117 can provide Internet 105 network connectivity to electronic device 116 via network interface 210a.

[0031] In another example, management device 117 may not have any of the network interfaces 210a and 210b, Wi-Fi module 202, GPS module 203, help button 208, LCD status 209, and LED 211. In this example, management device 117 can connect to the Internet 105 via one or two cellular modems 206a and 206b. Management device 117 can then provide network connectivity to electronic device 116 via device interface 201.

[0032] Figure 2B A block diagram of the components of electronic device 116A is shown. For illustrative purposes only, electronic device 116A may be a refrigerator, air conditioner, or IoT device. Electronic device 116A is capable of accessing a network. However, electronic device 116A may not allow other electronic devices to access the network. Electronic device 116A may have two types of interfaces, such as device interface 252 and network interface 253. Network interface 253 may be implemented using network ports, Ethernet ports, PoE ports, parallel ports, management ports, USB ports, WLAN interfaces, Bluetooth, NFC technology, infrared, or other communication technologies. Device interface 252 is used to connect directly (without a network) to another electronic device. Implementation of device interface 252 may include using serial ports, point-to-point Bluetooth, cross Ethernet, and junction boxes. Management device 117 can be connected to or coupled to electronic device 116A via device interface 252 or network interface 253. Management device 117 uses device interface 201 for connection to or coupling to electronic device 116A via connection 115. The processing unit 251 is used to execute programming instructions to operate the electronic device 116A. The electronic device 116A may also include a system bus, one or more storage media, sensors, and / or a SIM card slot for coupling a SIM card.

[0033] Figure 2C A block diagram of components of another variation of electronic device 116 is shown. Electronic device 116B is another hardware layout of electronic device 116 compared to electronic device 116A. For illustrative purposes only, electronic device 116 can be a hardware layout of electronic device 116B, and electronic device 116B can be a computing device, a mobile phone, or a networking device. Electronic device 116B is capable of accessing a network and providing the network to other electronic devices. When electronic device 116B is connected to a network via one or more WAN network interfaces, electronic device 116B allows other electronic devices to access the network via one or more LAN network interfaces. Electronic device 116B includes device interface 265, LAN network interface 267, and WAN interface 268. Device interface 265 performs... Figure 2BDevice interface 252. LAN network interface 267 and WAN network interface 268 can be implemented using network ports, Ethernet ports, PoE ports, parallel ports, serial ports, management ports, USB ports, WLAN interfaces, Bluetooth, NFC technology, infrared, or other communication technologies. In a specific example, WAN network interface 268 can be a cellular network interface, such as a 4G / 5G network interface. There are no limitations on the number and type of device interface 265, LAN network interface 267, and WAN interface 268. Electronic device 116B also includes a processing unit 261, main memory 263, and auxiliary memory 264. Processing unit 261, auxiliary memory 264, device interface 265, LAN network interface 267, and WAN interface 268 can be interconnected using a system bus. Processing unit 261 is directly connected to main memory 263. Processing unit 261 executes programming instructions stored in main memory 263 to operate electronic device 116B. Management device 117 is connected to electronic device 116B via device interface 201 through device interface 265 via connection 115.

[0034] Figure 3 This is a diagram illustrating various functions stored in main memory 205 and executed by processing unit 204 of management device 117. Management device 117 can perform various functions according to these functions. These functions can be in the form of software. The software may include an arrangement of program instructions 300 and is installed in management device 117.

[0035] The program instructions 300 may include functions such as an application installer 301, a Wi-Fi monitoring module 302, a screen sharing module 303, a pre-installed application 304, a cellular monitoring module 305, a status indication module 306, a storage module 307, a tier 2 / 3 / 4 monitoring module 308, a location monitoring module 309, a networking module 310, a load balancing module 311, a virtual private network (VPN) module 312, and a module 313 for communicating with a server.

[0036] Application installer 301 can be used to install configurations into electronic device 116. Wi-Fi monitoring module 302 can be used to monitor the Wi-Fi network or the connectivity of Wi-Fi module 202. Pre-installed application 304 can be used to operate management device 117 itself. Diagnostics of electronic device 116 can be performed by pre-installed application 304 to detect hardware and / or software problems.

[0037] Cellular monitoring module 305 can be used to monitor the cellular connections of cellular modems 206a and 206b to detect one or more telecommunications company services for one or more SIM cards. Cellular monitoring module 305 can then detect network coverage associated with one or more telecommunications company services to establish one or more cellular connections with one or more telecommunications company services using one or more SIM cards. Status indication module 306 can optionally be used for LCD status 209, LED 211, and help button 208. When management device 117 is operating, LCD status 209 and / or LED 211 can indicate the operating status. Help button 208 can be used to begin diagnostics of electronic device 116 after coupling or connecting management device 117. Storage module 307 can be used to manage, allocate, format, and / or partition main memory 205 and secondary memory 207 to operate management device 117. Layer 2 / 3 / 4 monitoring module 308 can be used to monitor different layers of the Open Systems Interconnection (OSI) network performed by management device 117. The location monitoring module 309 can be used by the GPS module 203 for positioning management device 117 or for positioning electronic device 116. The networking module 310 can be used to perform network functions of management device 117. The load balancing module 311 and VPN module 312 can be used with the networking module 310 to enhance the performance of the network functions of management device 117. Communication with the server module 313 can be used to communicate with servers (such as management server 104, server 103, or enterprise server 102).

[0038] Electronic device 116 can use VPN module 312 to establish a Virtual Private Network (VPN) connection with a server (e.g., server 103, management server 104, or enterprise server 102) via management device 117. VPN connections can be established using IPSec, OpenVPN, WireGuard, and / or other technologies. Figure 2B The components shown and Figure 2C The components shown are all suitable for electronic device 116 to establish a VPN connection. However, for ease of reading, if using... Figure 2B If the components shown are used to implement electronic device 116, then electronic device 116 cannot provide network connectivity to other devices. On the other hand, if electronic device 116 uses... Figure 2C If implemented using the components shown, electronic device 116 can provide network connectivity to other devices.

[0039] For example, when using IPsec, management device 117 can communicate with server 103 to retrieve VPN configuration information, including a pre-shared key and the IP address of server 103 used for the VPN connection. Furthermore, management device 117 can send a request to server 103 to retrieve the type of encryption algorithm (e.g., TripleDES (3DES), Data Encryption Standard (DES), Advanced Encryption Standard (AES)), authentication algorithm type (e.g., MD5, SHA1, SHA2), Diffie-Hellman (DH) group type (e.g., 768-bit, 1024-bit, 1536-bit), and lifetime (e.g., 60 seconds, 3600 seconds, 28800 seconds). For illustrative purposes, the pre-shared key is “ipsecvpn”, the IP address is “188.69.194.45”, the encryption algorithm type is “3DES”, the authentication algorithm type is “MD5”, the DH group is “768-bit”, and the lifetime is “3600 seconds”. When management device 117 retrieves the pre-shared key "ipsecvpn", IP address "188.69.194.45", encryption algorithm type "3DES", authentication algorithm type "MD5", DH block "768-bit block", and lifetime "3600 seconds", management device 117 can forward the VPN configuration information to electronic device 116 via connection 115. Electronic device 116 can then be configured according to the VPN configuration information received from management device 117 and establish a VPN connection with server 103.

[0040] In another variation, VPN configuration information used to configure the VPN connection can be stored in a local storage medium (such as secondary storage 207). In this variation, management device 117 can send information for configuring the VPN connection to electronic device 116 without retrieving VPN configuration information from server 103.

[0041] In another example, when using OpenVPN, management device 117 can communicate with server 103 to send a request for a client configuration file (e.g., client.ovpn). The client configuration file "client.ovpn" is used to configure electronic device 116 to establish a VPN connection with server 103. When management device 117 receives the client configuration file "client.ovpn", it can send it to electronic device 116 via connection 115. Furthermore, electronic device 116 can be configured with the client configuration file "client.ovpn" to establish a VPN connection with server 103. In one variant, management device 117 can retrieve the client certificate and username / password from server 103 and send them to electronic device 116 to establish a VPN connection. In another variant, the client configuration file "client.ovpn" or the client certificate and username / password can be stored in secondary storage 207. Management device 117 can then send the client configuration file "client.ovpn" or client certificate along with username / password to configure the VPN connection with electronic device 116 via connection 115.

[0042] In another example, when using WireGuard, a key generator can be used in both management device 117 and server 103 to generate a pair of encryption keys, namely, private and public. Management device 117 can send the private and public keys generated by management device 117 to server 103. Server 103 can send the private and public keys generated by server 103 to management device 117. It should be noted that the two keys must match for encryption and decryption. For example, if encryption is performed using the private key, decryption can be performed using only the public key. Management device 117 can then send the private and public keys received from server 103 to electronic device 116. Furthermore, management device 117 can determine the listening port number of server 103 and send the listening port number to electronic device 116. Electronic device 116 can then use the private and public keys received from server 103 and the listening port number to establish a VPN connection. In a variant, the private key, public key, and listening port number of server 103 can be stored in auxiliary storage 207. In this variant, management device 117 may not need to communicate with server 103 to configure the VPN connection. Management device 117 may send a client configuration file "client.ovpn" or a client certificate along with a username / password to configure the VPN connection with electronic device 116.

[0043] In another variation, an aggregated tunnel can be established between electronic device 116 and server 103 via management device 117. In this variation, management device 117 first establishes multiple connections with server 103 using multiple network interfaces, and then aggregates these connections to establish an aggregated tunnel. Electronic device 116 then communicates with server 103 through the aggregated tunnel.

[0044] Figures 4 to 15 Different processes according to embodiments of this disclosure are illustrated. For a better understanding of the embodiments, it should be considered in conjunction with… Figure 1 Let's take a look Figures 4 to 15 Due to software problems, hardware problems, or other issues, the electronic device may malfunction. A management device can correct the problem of the electronic device according to different conditions and methods. For illustrative purposes, the electronic device can be electronic device 116, and the management device can be management device 117. Electronic device 116 may have… Figure 2B The components shown or Figure 2C The components shown.

[0045] Figure 4 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 Let's take a look Figure 4 . Figure 4 The general case of this disclosure is shown.

[0046] In a network environment, an electronic device (e.g., electronic device 116) may be unable to connect to the network due to problems (e.g., hardware or software issues). Because of these problems, electronic device 116 may be unable to communicate with servers (e.g., server 103, management server 104, or enterprise server 102). However, management device 117 can still connect to or couple to electronic device 116 via a wireless or wired connection (such as connection 115). In this case, management device 117 can provide out-of-band connectivity to electronic device 116 because electronic device 116 cannot directly connect to server 103, management server 104, and enterprise server 102. Management device 117 is configured to connect to the Internet 105 itself using at least one of its own network interfaces. However, electronic device 116 will remain in a state where it still cannot connect to the Internet 105 through management device 117. Management device 117 is configured to detect the identification information of electronic device 116 via connection 115. Furthermore, management device 117 diagnoses electronic device 116 to resolve its problems. The management device 117 also uses configuration to configure the electronic device 116.

[0047] In another scenario, electronic device 116 may have the problem of connecting to the Internet 105 itself. However, when management device 117 is connected to or coupled to electronic device 116 via connection 115, electronic device 116 is then configured to connect to the Internet 105 via management device 117 using connections 115 and 114.

[0048] In another scenario, an electronic device (e.g., electronic device 116) is capable of connecting to the Internet 105 via a wireless or wired connection. However, electronic device 116 may still have problems, such as software issues. Electronic device 116 is capable of retrieving its own configuration; however, it cannot extract the configuration used for itself. It may be necessary to extract the configuration and provide it to electronic device 116 via management device 117. Management device 117 is connected to or coupled to electronic device 116 via connection 115. Management device 117 then configures electronic device 116. For illustrative purposes only, this document describes electronic device 116 and management device 117. Figure 4 .

[0049] In process 401, management device 117 connects to or couples to electronic device 116 via connection 115 using device interface 201. There are no restrictions on the interface type and connection type of management device 117. For example, if electronic device 116 is a refrigerator, management device 117 connects to the refrigerator using an interface supported by the refrigerator. The refrigerator may have a wireless local area network (WLAN) interface, such as IEEE 802.11. Management device 117 connects to or couples to the refrigerator via device interface 201 using a Wi-Fi connection. In another example, electronic device 116 may be a computer system. The computer system may have one or more of the following interfaces: a network interface, a parallel interface, a serial interface, or a USB interface. Management device 117 connects to the computer system through one or more of these interfaces.

[0050] In process 402, management device 117 detects identification information of electronic device 116. Identification information may include serial number, model, media access control (MAC) address, and / or the identifier of the user of electronic device 116.

[0051] In process 403, management device 117 diagnoses electronic device 116 to identify whether electronic device 116 has a hardware problem or a software problem.

[0052] In process 404, management device 117 configures electronic device 116. Based on the problem identified after the diagnosis in process 403, management device 117 can use this configuration to reconfigure electronic device 116 to fix the problem. Alternatively, if a hardware problem is identified after the diagnosis in process 403, management device 117 can apply a solution to electronic device 116 before configuring / reconfiguring it in process 404. The application of the solution can be based on... Figure 13 As described later. The application solution may also include restarting the electronic device 116, which will be described later according to... Figure 8 Description. Electronic device 116 may subsequently be able to begin sending and receiving Internet Protocol (IP) data packets, either independently or via management device 117. However, when management device 117 is disconnected from electronic device 116, electronic device 116 may be unable to send and receive IP data packets.

[0053] Figure 5 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 5 .exist Figure 5 In this process, the management device 117 identifies whether the electronic device 116 has a hardware problem, a software problem, or both. Based on the problem identified in the electronic device 116, the management device 117 provides support to the electronic device 116.

[0054] In process 502, the management device 117 identifies whether the electronic device 116 has a hardware problem.

[0055] If the management device 117 identifies a hardware problem in the electronic device 116, then at process 506, the management device 117 generates a hardware problem report. This report may include the type of hardware problem and / or the status of the hardware.

[0056] In process 507, management device 117 sends a report to the user or administrator of management device 117. The report can be in string format, binary format, XML format, or any other format. The report can be sent to the user or administrator via network, Bluetooth, infrared, Short Message Service (SMS), Multimedia Messaging Service (MMS), or email. Alternatively, the report can also be displayed to the user or administrator via a display module connected to management device 117. Process 507 can be optionally performed in this disclosure.

[0057] If electronic device 116 has no hardware problems, then electronic device 116 may have a software problem. Then, in process 503, management device 117 identifies the software problem.

[0058] In process 504, management device 117 receives configuration of electronic device 116 from a server, such as enterprise server 102 or management server 104. This configuration is used to configure electronic device 116 to fix software problems. The configuration can be received by management device 117 using IP data packets, or by using a cellular connection via one or more cellular modems 206a and 206b, via one or more SMS or MMS messages. The configuration is received after a request for configuration is sent to the server. In another variation, electronic device 116 can receive configuration directly from the server or via management device 117.

[0059] In one variant, electronic device 116 may have both software and hardware problems. Management device 117 then executes processes 506 and 503 accordingly. Management device 117 then repairs both the hardware and software problems of electronic device 116. Preferably, management device 117 executes processes 506 and 503 sequentially. More specifically, management device 117 repairs the hardware problem first, then the software problem. If the hardware problem is not repaired before the software problem is repaired, these repairs may not have any effect on electronic device 116. For example, electronic device 116 may have a faulty network interface as a hardware problem. Furthermore, the faulty network interface may be configured with an unusable configuration, which is a software problem. Management device 117 generates a report on the faulty network interface and sends the report to the user. The user can then be able to repair the faulty network interface based on the report. Additionally, management device 117 then configures the network interface to repair the software problem.

[0060] In another variation, management device 117 may be unable to fix the problem found at electronic device 116. Management device 117 then generates a report with the hardware and software status of electronic device 116. The report can then be sent to the user or administrator of management device 117.

[0061] Figure 6 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 6 . Figure 6 This illustrates when electronic device 116 might be unable to connect to the network due to a problem. However, management device 117 connects to the network itself and establishes a connection between electronic device 116 and the network.

[0062] In process 602, management device 117 is connected to Internet 105 via connection 114. In process 603, electronic device 116 establishes a connection to Internet 105 via management device 117 using connections 115 and 114.

[0063] In process 604, electronic device 116 receives configuration from server via management device 117 using IP data packets. To receive the configuration, electronic device 116 can send a request and its identification information to server via management device 117 using IP data packets, and the server can then send the configuration to electronic device 116 upon receiving the request.

[0064] In another variation, upon receiving a configuration, electronic device 116 authenticates whether the configuration is valid. The configuration may include authentication information for authentication. For example, electronic device 116 authenticates the configuration by extracting its contents using a password and authentication information. If the password allows extraction of the configuration's contents, the configuration is valid. Otherwise, the configuration is invalid. Furthermore, electronic device 116 authenticates the configuration using a server by verifying whether it was received from the server. If the configuration was received from the server, the configuration is valid.

[0065] Figure 7 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 7 .

[0066] Figure 7 The electronic device 116 may have problems and requires configuration using a configuration for fixing those problems. Configuration needs to be retrieved from an enterprise server (such as enterprise server 102). However, due to these problems, the electronic device 116 cannot receive configuration from enterprise server 102. The management device 117 receives the configuration for the electronic device 116 from enterprise server 102.

[0067] In process 702, management device 117 uses IP data packets to send identification information and configuration requests for electronic device 116 to enterprise server 102. Management device 117 sends the identification information and requests in IP data packets via Internet 105 and intranet 106 using connections 114, 112, and 109.

[0068] In process 703, management device 117 receives configuration from enterprise server 102 using IP data packets or via one or more SMS or MMS messages through a cellular connection via one or more cellular modems 206a and 206b.

[0069] Figure 8 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 8 .

[0070] Figure 8 This illustrates that there may be software or hardware problems in electronic device 116, and that electronic device 116 may need to be diagnosed to identify these problems. Electronic device 116 then needs to be partially or fully restarted based on the identified problems to resolve them. Management server 104 is able to instruct electronic device 116 to restart based on the identified problems via management device 117.

[0071] In process 802, the management device 117 generates a report on the problems of the electronic device 116. This report may include the hardware status, software status, and identification information of the electronic device 116.

[0072] In process 803, the management device 117 sends the report to the management server 104 via the Internet 105 using IP data packets.

[0073] In process 804, management device 117 receives instructions from management server 104 via IP data packets. These instructions are used to partially or completely restart electronic device 116. The instructions may include additional suggestions for troubleshooting for the user or administrator of management device 117 and / or electronic device 116.

[0074] In process 805, management device 117 partially or completely restarts electronic device 116 according to instructions received from management server 104. These instructions may include commands from a script file to restart electronic device 116. For example, commands from the script file may be used to restart one or more parts of electronic device 116. Alternatively, commands from the script file may be used to restart an entire part of electronic device 116. When the commands from the script file are executed by electronic device 116, management device 117 can then restart electronic device 116.

[0075] Management device 117 generates a report on the problem found at electronic device 116. Management device 117 then sends the identification information of electronic device 116 along with the report to management server 104 to receive instructions from management server 104. Instructions may include sending a configuration request to enterprise server 102. Management device 117 also sends a request to enterprise server 102 to configure electronic device 116. Figure 9 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 9 .

[0076] In process 902, the management device 117 generates a report on the problems of the electronic device 116. This report may include the hardware and software status of the electronic device 116.

[0077] In process 903, management device 117 sends identification information and reports of electronic device 116 to management server 104 via Internet 105 through connections 114 and 111.

[0078] Then, management server 104 can analyze the report received from management device 117 based on the instruction database stored in management server 104. The instruction database may include problems with electronic device 116 and their solutions. Management server 104 can then send instructions to management device 117. These instructions may include sending a configuration request to enterprise server 102. Additionally, instructions may be used to partially or completely restart electronic device 116 after configuration. In process 904, management device 117 receives instructions from management server 104.

[0079] In process 905, according to the instructions, via Internet 105 and intranet 106 through connections 114, 112 and 109, using IP data packets, management device 117 sends a configuration request to enterprise server 102.

[0080] In process 906, using IP data packets, via the Internet 105 and intranet 106, through connections 114, 112 and 109, management device 117 receives the configuration from enterprise server 102.

[0081] Electronic device 116 may have one or more problematic network interfaces. One or more network interfaces may be configured to be unusable, thus preventing electronic device 116 from connecting to a network such as the Internet 105. When management device 117 is connected or coupled to electronic device 116, electronic device 116 is configured by management device 117. Electronic device 116 then uses management device 117 to establish a connection with the Internet 105. Electronic device 116 is then able to send identification information to a server and receive configuration from the server via management device 117. The identification information may be the identification information of electronic device 116. Electronic device 116 then uses this configuration to configure / reconfigure one or more network interfaces. Figure 10 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 10 .

[0082] In process 1002, when management device 117 is connected or coupled to electronic device 116, electronic device 116 is configured by management device 117. In process 1003, electronic device 116 is connected to Internet 105 using management device 117 via connections 115 and 114.

[0083] In process 1004, a connection is established between electronic device 116 and Internet 105 using management device 117. In process 1005, electronic device 116 sends identification information and a configuration request to the server using the connection established by management device 117.

[0084] In process 1006, electronic device 116 receives configuration from server using management device 117. The server can send the configuration based on identification information after receiving the request.

[0085] The management device 117 may have already stored the configuration of the electronic device 116 in a local storage medium (e.g., auxiliary storage 207). The local storage medium can also be externally connected to or coupled to the management device 117 using a network port, USB port, NFC technology, Bluetooth, Wi-Fi, or other communication technologies. The management device 117 selects the configuration based on the identification information of the electronic device 116. Furthermore, the management device 117 uses this configuration to configure the electronic device 116 to troubleshoot problems. Figure 11 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 11 .

[0086] In process 1102, management device 117 selects a configuration for electronic device 116 based on identification information. Management device 117 may include multiple configurations for different electronic devices stored in auxiliary memory 207. Management device 117 then selects a configuration from the multiple configurations based on the identification information of electronic device 116.

[0087] If the configuration has already been retrieved and stored at the management device 117, a configuration can be selected from multiple configurations stored at a remote server such as the management server 104. Furthermore, after sending a request for the selected configuration, the management device 117 receives the configuration from the management server 104 using IP data packets. The management device 117 then uses this configuration to configure the electronic device 116 to fix the problem. Figure 12 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 12 .

[0088] In process 1202, management device 117 selects a configuration from multiple configurations stored at management server 104 based on the identification information of electronic device 116. Alternatively, management device 117 sends the identification information of electronic device 116 to management server 104 so that management server 104 can select a configuration based on the identification information of electronic device 116. Furthermore, management server 104 may have already stored multiple configurations for different electronic devices.

[0089] In process 1203, management device 117 uses IP data packets to send a configuration request to management server 104 via Internet 105 through connections 114 and 111.

[0090] In process 1204, after sending a request via Internet 105 using IP data packets through connections 111 and 114, management device 117 receives configuration from management server 104. The configuration can also be received via one or more SMS or MMS messages through a cellular connection via one or more cellular modems 206.

[0091] In one variant, upon receiving a configuration, management device 117 authenticates whether the configuration is valid. The configuration may include authentication information used for authentication. For example, management device 117 authenticates the configuration by extracting its contents using a password and authentication information. If the password allows extraction of the configuration's contents, the configuration is valid. Otherwise, the configuration is determined to be invalid. Management device 117 also authenticates the configuration using management server 104. If the configuration is received from management server 104, then the configuration is valid.

[0092] There may be a hardware problem in electronic device 116. Management device 117 diagnoses electronic device 116 to identify the hardware problem. It may be necessary to apply a solution to electronic device 116 to fix the hardware problem. Management device 117 applies the solution to electronic device 116. Figure 13 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 13 .

[0093] In process 1302, management device 117 selects a solution based on the problem. Various solutions are possible, such as partially or completely restarting electronic device 116, or regulating the temperature by controlling the speed of the cooling fan. The solution may be stored on a local storage medium, such as auxiliary storage 207, or on a remote server, such as management server 104.

[0094] In process 1303, management device 117 applies a solution to electronic device 116 via connection 115. For example, management device 117 can use a script file to command electronic device 116 to control the cooling fan speed to regulate the temperature and fix the problem. In another example, electronic device 116 may freeze and become unresponsive. Restarting electronic device 116 can resolve this issue. Management device 117 can command electronic device 116 to restart using a script file.

[0095] It may be necessary to retrieve configuration from a remote server, such as management server 104, to configure electronic device 116 and resolve issues. However, electronic device 116 may be unable to retrieve configuration from management server 104 due to problems. Instead, management device 117 retrieves the configuration of electronic device 116 via the Internet 105 based on the identification information of management device 117. Figure 14 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 14 .

[0096] In process 1402, management device 117 uses IP data packets to send identification information of management device 117 and a request for configuration of electronic device 116 to management server 104. The identification information may include serial number, model, MAC address, and / or the identifier of the user of management device 117.

[0097] In process 1403, management device 117 receives configuration from management server 104 using IP data packets, or via one or more SMS or MMS messages through a cellular connection using one or more cellular modems 206a and 206b. After receiving a request based on the identification information of management device 117, management server 104 sends the configuration of electronic device 116. Additionally, management device 117 authenticates the validity of the configuration. The configuration may include authentication information for authentication. For example, management device 117 authenticates the configuration by retrieving its contents using a password and authentication information. If the password allows retrieval of the configuration contents, the configuration is valid. Otherwise, the configuration is invalid. Management device 117 also authenticates the configuration using management server 104. If management device 117 determines that it has received configuration from management server 104, the configuration is determined to be valid.

[0098] It may be necessary to retrieve configuration from a remote server, such as management server 104, to configure electronic device 116 to resolve issues based on IMSI and / or IMEI. IMSI and / or IMEI can be used as identification information. Figure 15 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 1 and Figure 4 Let's take a look Figure 15 .

[0099] In process 1502, management device 117 sends the IMSI and / or IMEI to management server 104. The IMSI is the IMSI of the SIM card in the SIM card slot coupled to one of the cellular modems 206a and 206b in management device 117, and the IMEI is the IMEI of management device 117. The IMSI and / or IMEI may be sent along with a request for configuration of electronic device 116. Optionally, the IMSI may be the IMSI of the SIM card in the SIM card slot coupled to electronic device 116, and the IMEI may be the IMEI of electronic device 116.

[0100] In process 1503, management device 117 receives configuration from management server 104 via IP data packets or via one or more cellular modems 206a and 206b using one or more SMS or MMS messages. Upon receiving a request based on IMSI and / or IMEI, management server 104 sends the configuration of electronic device 116 to management device 117.

[0101] According to the processes depicted in various embodiments of this disclosure, after successful configuration, reconfiguration, and / or troubleshooting, electronic device 116 is able to communicate with SIM card pool 119, either directly or via management device 117. Electronic device 116 is then able to retrieve one or more IMSIs of one or more SIM cards from SIM card pool 119, either directly or via management device 117. Electronic device 116 can then use the MCC, MNC, and MSIN of one or more IMSIs to establish one or more cellular connections using one or more cellular modems. One or more cellular modems may be coupled to electronic device 116. In another case, management device 117 may communicate with SIM card pool 119 to utilize one or more SIM cards to establish one or more cellular connections using one or more cellular modems 206a and 206b.

[0102] A management device (e.g., management device 117) can maintain one or more cellular connections by forwarding authentication requests received from a telecommunications company service to a SIM card pool 119 and authentication responses received from a SIM card pool 119 to a telecommunications company service for one or more IMSIs of one or more SIM cards.

[0103] Figure 2B The components shown and Figure 2C Both of the components shown are applicable to the electronic device 116 in this disclosure. There is no limitation on the electronic device 116 to those having… Figure 2B The components shown are either limited to those having Figure 2C The components shown.

[0104] Figure 16 Network topologies according to various embodiments of this disclosure are shown. Figure 16 Is with Figure 1 Similar network topology. In Figure 16 In this configuration, electronic device 116 is not connected to the Internet 105 itself. Management device 117 may have multiple WAN network interfaces, such as network interfaces 210a and 210b and cellular modems 206a and 206b.

[0105] In one example, electronic device 116 provides network connectivity to other devices such as telephone 1602. Telephone 1602 is connected to electronic device 116 via connection 1604. Connection 1604 can be a wireless or wired connection. Connection 1604 can be established using a management port, serial port, console port, Ethernet, USB connection, Near Field Communication (NFC) technology, Bluetooth, Wi-Fi Direct, or other communication technologies. Laptop computer 1601, electronic device 116, and management device 117 are connected to wireless LAN 1603.

[0106] Figure 16 Other components and parts Figure 1 The components and parts are the same.

[0107] Routing policy

[0108] Figure 17 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 16 Let's take a look Figure 17 .

[0109] When management device 117 receives a configuration to configure electronic device 116, the configuration may include a routing policy. Management device 117 can then extract the routing policy from the configuration. The routing policy can provide instructions for sending or routing IP data packets received from electronic device 116.

[0110] Alternatively, electronic device 116 can receive the configuration itself via management device 117. Electronic device 116 can then be configured with a routing policy. In one example, the configuration includes configuration for at least one Service Set Identifier (SSID) and a routing policy for that at least one SSID. The routing policy can be based on the destination or source of IP data packets.

[0111] In process 1701, management device 117 receives configuration from electronic device 116. Configuration may be received from a server (such as management server 104 or enterprise server 102). Alternatively, configuration may be retrieved from local storage media (e.g., secondary storage 207). The configuration includes SSID configuration and SSID routing policies.

[0112] In process 1702, the processing unit of management device 117 configures management device 117 based on SSID configuration using one or more SSIDs. SSID configuration may include one or more strings to be used as SSIDs, a corresponding authentication password, a corresponding wireless network security type, and a corresponding encryption type. The wireless network security type may be Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), WPA2, or WPA3, while the encryption type may be Advanced Encryption Standard (AES) or Temporary Key Integrity Protocol (TKIP). For illustrative purposes, the SSID is "red," the authentication password is "0000000000," and the wireless network security type is WPA2. There is no limit to the number of SSIDs that can be created for each configuration.

[0113] For example, the configuration may also include another SSID "blue" and the corresponding authentication password, the corresponding wireless network security type, and the corresponding encryption type.

[0114] In process 1703, the processing unit of management device 117 configures management device 117 based on the routing policy of the SSID. The processing unit will send or route IP data packets received via the SSID based on the routing policy. There is no restriction on the type of routing policy stored in the configuration and executed by the processing unit of management device 117. For example, management device 117 has two WAN network interfaces, namely, network interface 210b and another WAN network interface ( Figure 2A (Not shown in the image). For example, a routing policy is used to limit all IP data packets received via SSID "red" that are to be sent using the first WAN network interface, and to limit all IP data packets received via SSID "blue" that are to be sent using the second WAN network interface. In another example, IP data packets received via SSID "red" will be sent via a VPN. A VPN can be established based on this configuration. In another example, flow control is implemented to limit the bandwidth of SSID "red" to a threshold, which can be specified in the configuration. In yet another example, IP data packets received and sent via SSID "red" will have a higher priority than IP data packets received and sent via SSID "blue". Higher-priority IP data packets will be processed and sent earlier than lower-priority IP data packets.

[0115] In process 1704, to allow electronic device 116 to access the network connected to management device 117, the user or administrator of electronic device 116 can enter the SSID "red", the wireless network security type WPA2, the encryption type AES, and the password "00000000000" into electronic device 116. Electronic device 116 will then be able to authenticate to management device 117 and access the network. In a variant, when management device 117 is coupled to electronic device 116 for out-of-band management, management device 117 can configure electronic device 116 using the SSID "red", the wireless network security type, the encryption type, and the password. Management device 117 can also configure electronic device 116 to diagnose and troubleshoot problems while performing out-of-band management.

[0116] In process 1705, when IP data packets are sent and received via one or more SSIDs, the processing unit of management device 117 executes routing policies on the IP data packets.

[0117] In one example, for illustrative purposes only, electronic device 116 provides network access to telephone 1602 via connection 1604. Electronic device 116 is also connected to a management device via connection 115, which is a wireless connection with SSID "Red". Therefore, telephone 1602 is able to access the Internet 105 via SSID "Red". IP data packets received and transmitted by telephone 1602 follow the routing policy of SSID "Red".

[0118] In another example, the user or administrator of laptop computer 1601 can enter the SSID "red", the wireless network security type "WPA2", the encryption type "AES", and the password "0000000000". Laptop computer 1601 will then be able to authenticate to management device 117 to use wireless LAN 1603. Laptop computer 1601 will then be able to access the Internet 105 via management device.

[0119] In one variant, multiple WAN network interfaces of management device 117 can form aggregated connections to a host (e.g., enterprise server 102) accessible via the Internet 105. The aggregated connections can be encrypted and may require authentication. The configuration for forming the aggregated connections is included in the configuration received in processing 1701. Routing policies may include sending IP data packets received via SSID "Red" to enterprise server 102 through the aggregated connections. This aggregated connection can be formed on multiple WANs connected to the WAN network interfaces of management device 117. This allows a user of laptop computer 1601 to connect to enterprise server 102 simply by connecting to SSID "Red".

[0120] Energy Strategy

[0121] Figure 18 This is a flowchart illustrating a process according to one of the embodiments of this disclosure. For a better understanding of the embodiments, it should be considered in conjunction with... Figure 16 Let's take a look Figure 18 Electronic device 116 may have Figure 2B or Figure 2C The components shown are for illustrative purposes only. Figure 2B The components mentioned are used for discussion. However, electronic device 116 is not limited to having Figure 2B The components shown.

[0122] When management device 117 receives or retrieves a configuration for electronic device 116 during processing 1801, the configuration may include an energy strategy. The configuration may be received from a server such as management server 104, or retrieved from a local storage medium such as auxiliary storage 207.

[0123] In process 1802, management device 117 extracts an energy strategy from the configuration. The energy strategy can be used to configure electronic device 116 to enable or disable device interface 252 of electronic device 116.

[0124] In process 1803, management device 117 configures electronic device 116 with an energy policy. The energy policy can be sent to electronic device 116 via connection 115 and network interface 253 or device interface 252.

[0125] In process 1804, electronic device 116 determines whether to enable device interface 252 based on a power strategy. The power strategy can be used to determine when electronic device 116 should turn device interface 252 on and off, for example, from 8 AM to 2 PM during the day. The power strategy can also be used to instruct electronic device 116 to keep device interface 252 in sleep mode or hibernation. For example, if device interface 252 is not used for 30 minutes, device interface 252 will be put into sleep mode. It should be noted that the power strategy is not limited to the attributes and parameters mentioned herein.

[0126] In process 1805, electronic device 116 enables device interface 252. In process 1806, electronic device 116 disables device interface 252.

[0127] In one variant, device interface 252 supplies power and / or provides data to another device by enabling or disabling device interface 252.

[0128] In one variant, an energy policy is used to configure when electronic device 116 should be turned on and off. In this variant, processes 1804 to 1806 are not executed. Instead, when processing unit 251 has received the energy policy from management device 117, electronic device 116 may schedule its own on and off times.

[0129] In one variant, electronic device 116 receives power from management device 117 and does not perform processes 1803 to 1806. Instead, management device 117 switches electronic device 116 on and off based on a power policy by supplying or de-supplying it. Electronic device 116 may use Power over Ethernet (PoE) technology to receive power from management device 117 via an Ethernet cable.

[0130] Modifications, additions, or omissions may be made to the systems, apparatuses, and methods described herein without departing from the scope of this disclosure. For example, components of the systems and apparatuses may be integrated or separate. Furthermore, the operation of the systems and apparatuses disclosed herein may be performed by more, fewer, or other components, and the described methods may include more, fewer, or other steps. Additionally, the steps may be performed in any suitable order.

Claims

1. A method performed at an electronic device, comprising: (a) When the management device is coupled to the electronic device: i. Establish a connection via the management device; ii. Determine the identification information based on the identification of the management device; iii. Send the identification information to the server via the connection; iv. Receive configuration from the server; v. Configure using the described configuration; as well as (b) After configuring using the above configuration, start sending and receiving data.

2. The method according to claim 1, further comprising: The management device establishes an aggregation tunnel between the electronic device and the server.

3. The method according to claim 1, wherein the identification information is based on a serial number, model, media access control (MAC) address and / or the identifier of the user of the management device.

4. The method of claim 1, wherein the server comprises a plurality of configurations, and the configurations are selected from the plurality of configurations based on the identification information.

5. The method of claim 1, wherein the connection is a cellular connection established using the cellular modem of the management device.

6. The method of claim 1, further comprising: Receive instructions from the server.

7. The method of claim 6, wherein the electronic device is restarted according to the instruction.

8. The method of claim 1, wherein the management device is coupled to the electronic device via a management port, serial port, or console port of the electronic device.

9. The method of claim 1, further comprising: After receiving the configuration from the server, the configuration is authenticated.

10. The method of claim 9, wherein if the configuration is valid, the electronic device is configured using the configuration.

11. An electronic device comprising: At least one network interface; At least one processing unit; At least one main storage medium; At least one auxiliary storage medium storing program instructions executed by the at least one processing unit for: (a) When the management device is coupled to the electronic device: i. Establish a connection via the management device; ii. Determine the identification information based on the identification of the management device; iii. Send the identification information to the server via the connection; iv. Receive configuration from the server; v. Configure using the described configuration; and (b) After configuring using the above configuration, start sending and receiving data.

12. The electronic device according to claim 11, further comprising: The management device establishes an aggregation tunnel between the electronic device and the server.

13. The electronic device of claim 11, wherein the identification information is based on a serial number, model, media access control (MAC) address and / or the identifier of the user of the management device.

14. The electronic device of claim 11, wherein the server comprises a plurality of configurations, and the configurations are selected from the plurality of configurations based on the identification information.

15. The electronic device of claim 11, wherein the connection is a cellular connection established using a cellular modem of the management device.

16. The electronic device of claim 11, wherein the at least one auxiliary storage medium further stores the program instructions executed by the at least one processing unit for: Receive instructions from the server.

17. The electronic device of claim 16, wherein the electronic device is restarted according to the instruction.

18. The electronic device of claim 11, wherein the management device is coupled to the electronic device via a management port, serial port, or console port of the electronic device.

19. The electronic device of claim 11, wherein the at least one auxiliary storage medium further stores the program instructions executed by the at least one processing unit for: After receiving the configuration from the server, the configuration is authenticated.

20. The electronic device of claim 19, wherein if the configuration is valid, the electronic device is configured using the configuration.

Images