Remote computing device recovery

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may establish a connection with a server through a wireless network. The UE may receive, from the server and via the connection through the wireless network, at least one of a firmware image file or a software image file. The UE may transmit at least one of the firmware image file or the software image file to a computing device. Numerous other aspects are described.

Description

[Technical Field]

[0001] Various aspects of this disclosure generally relate to wireless communications, and also to techniques and apparatus for remote computing device recovery. [Previous Technology]

[0002] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies (MIMs) capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such MIMs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP). Other examples of wireless communication technologies that can be implemented in wireless communication systems include Wi-Fi, Wi-Fi Direct, Bluetooth, Near Field Communication (NFC), Zigbee, WiMAX, Wireless Local Area Network (WAN) and / or Wireless Personal Area Network (WPAN), and other examples.

[0003] A wireless network may include one or more base stations (e.g., cellular base stations, Wi-Fi routers) that support wireless communication with user equipment (UE) (or multiple UEs), computing devices (or multiple computing devices), and / or other types of wireless communication devices. Wireless communication devices may communicate with base stations via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the wireless communication device, while "uplink" (or "UL") refers to the communication link from the wireless communication device to the base station.

[0004] The aforementioned wireless communication technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, and / or global levels. New Radio (NR), which may be referred to as 5G, is a collection of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on the downlink (CP-OFDM), and using CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful. [Summary of the Invention]

[0005] Some aspects described herein relate to methods of wireless communication performed by a user equipment (UE). The method may include establishing a connection with a server via a wireless network. The method may include receiving at least one of a firmware image file or a software image file from the server and via the connection through the wireless network. The method may include transmitting at least one of the firmware image file or the software image file to a computing device.

[0006] Some aspects described herein relate to methods of wireless communication performed by a computing device. The method may include receiving at least one of a firmware image file or a software image file from at least one of a UE or a server. The method may include using at least one of the firmware image file or the software image file to perform a recovery operation for the computing device.

[0007] Some aspects described herein relate to a UE for wireless communication. The user equipment may include memory and one or more processors coupled to the memory. One or more processors may be configured to establish a connection with a server via a wireless network. One or more processors may be configured to receive at least one of a firmware image file or a software image file from a server and via a connection through a wireless network. One or more processors may be configured to transmit at least one of the firmware image file or the software image file to a computing device.

[0008] Some aspects described herein relate to computing devices for wireless communication. The computing device may include memory and one or more processors coupled to the memory. The one or more processors may be configured to receive at least one of a firmware image file or a software image file from at least one of a UE or a server. The one or more processors may be configured to perform recovery operations for the computing device using at least one of the firmware image file or the software image file.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to establish a connection with a server via a wireless network. When executed by one or more processors of the UE, the set of instructions enables the UE to receive at least one of a firmware image file or a software image file from a server and via the connection through the wireless network. When executed by one or more processors of the UE, the set of instructions enables the UE to send at least one of a firmware image file or a software image file to a computing device.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a computing device. When executed by one or more processors of the computing device, the set of instructions enables the computing device to receive at least one of a firmware image file or a software image file from at least one of a UE or a server. When executed by one or more processors of the computing device, the set of instructions enables the computing device to perform a recovery operation for the computing device using at least one of the firmware image file or the software image file.

[0011] Some aspects described herein relate to apparatus for wireless communication. The apparatus may include components for establishing a connection with a server via a wireless network. The apparatus may include components for receiving at least one of a firmware image file or a software image file from a server and via the connection through the wireless network. The apparatus may include components for transmitting at least one of the firmware image file or the software image file to a computing device.

[0012] Some aspects described herein relate to apparatus for wireless communication. The apparatus may include components for receiving at least one of a firmware image file or a software image file from at least one of a UE or a server. The apparatus may include components for performing a recovery operation for the apparatus using at least one of the firmware image file or the software image file.

[0013] The aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and processing systems as described herein with reference to the accompanying drawings and description.

[0014] The features and technical advantages of the examples according to this disclosure have been summarized quite extensively above in order to provide a better understanding of the following detailed description. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as a basis for modifications or designs to other structures used to achieve the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein in terms of their organization and operation, as well as their associated advantages, will be better understood through the following description, taken in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a limitation of the claims.

[0015] Although aspects are described in this disclosure by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or package arrangements. For example, some aspects can be implemented via integrated wafer embodiments or other non-module-based devices (e.g., end-user equipment, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices and / or devices supporting artificial intelligence). Aspects can be implemented in wafer-level components, modular components, non-wafer-level components, device-level components and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of different sizes, shapes, and configurations.

Implementation Method

[0024] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as being limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of any other aspect of this disclosure or in combination with any additional aspects of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using additional structures, functionalities, or structures and functionalities that supplement or complement the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claimed item.

[0025] Several aspects of a telecommunications system will now be given with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0026] Although the terms commonly associated with 5G or New Radio (NR) Radio Access Technology (RAT) are used herein to describe the aspects, the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0027] Figure 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. Wireless network 100 may be or may include elements of one or more types of wireless networks, such as cellular networks, computer networks, and / or other types of wireless networks. For example, wireless network 100 may include components and / or devices of 5G (e.g., NR) networks and / or 4G (e.g., LTE) networks, among other examples. As another example, wireless network 100 may include components and / or devices of computer networks, such as local area networks (LANs), wired LANs (WLANs), wide area networks (WANs), and / or virtual private networks (VPNs), among other examples. Wireless network 100 may include one or more base stations 110. In some cases, the wireless network 100 includes one or more cellular base stations (shown as BS 110a, BS 110b, BS 110c, and BS 110d), one or more computer network base stations (shown as BS 110e), and / or one or more other types of base stations. Base station 110 may communicate with user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), with network controller 130 (or multiple network controllers 130), with computing devices 140 (or multiple computing devices 140, shown as computing devices 140a, 140b, and 140c), and / or other network entities. Cellular base station 110 (sometimes referred to as BS) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or Transmit / Receive Points (TRPs). Each cellular base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​base station 110 and / or the base station subsystem serving that coverage area, depending on the context in which the term is used. Computer network base station 110 may include routers, bridges, hubs, switches, firewalls, and / or other types of computer network equipment communicating with UE 120 and / or computing device 140, as well as one or more network controllers 130 included in the computer network.

[0028] Base station 110 can provide communication coverage for macro cells, pico cells, femtocells, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UE 120 and / or computing devices 140 with service subscriptions. A pico cell can cover a relatively small geographic area and can allow unrestricted access for UE 120 and / or computing devices 140 with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access for UE 120 and / or computing devices 140 associated with that femtocell (e.g., UE 120 and / or computing devices 140 in a Closed Subscriber Group (CSG)). Base station 110 for macro cells can be referred to as a macro base station. Base station 110 for pico cells can be referred to as a pico base station. Base station 110 for femtocells can be referred to as a femtocell or a home base station. In the example shown in Figure 1, BS 110a can be a macro base station of macro cell 102a, BS 110b can be a pico base station of pico cell 102b, and BS 110c can be a femto base station of femto cell 102c. The base station can support one or more (e.g., three) cells.

[0029] In some examples, the cell may not have to be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, base stations 110 may interconnect with each other and / or interconnect to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0030] Wireless network 100 may include one or more relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., base station 110 or UE 120) and send data transmissions to a downstream station (e.g., UE 120 or base station 110). A relay station may be a UE 120 capable of relaying transmissions of other UE 120s. In the example shown in Figure 1, BS 110d (e.g., a relay base station) may communicate with BS 110a (e.g., a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. The base station 110 relaying the communication may be referred to as a relay station, relay base station, repeater, etc.

[0031] The wireless network 100 can be a heterogeneous network, including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 can have different transmit power levels, different coverage areas, and / or different effects on interference in the wireless network 100. For example, macro base stations can have high transmit power levels (e.g., 5 watts to 40 watts), while pico base stations, femto base stations, and relay base stations can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0032] Network controller 130 may be coupled to or communicate with a set of base stations 110, and may provide coordination and control for these base stations 110. Network controller 130 may communicate with base stations 110 via a backhaul communication link. Base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links. In some aspects, one or more network controllers 130 may be included in the core network of a cellular network and may communicate with one or more cellular base stations 110. In some aspects, one or more network controllers 130 may be included in a computer network (e.g., a computer data network) and may communicate with one or more computer network base stations 110.

[0033] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, a smart accessory (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via wireless media.

[0034] Some UEs 120 may be considered machine-type communications (MTC) or evolved or enhanced machine-type communications (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which can communicate with base stations, another device (e.g., remote devices), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses the components of UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0035] Typically, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, air interface, etc. A frequency can be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0036] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0037] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating frequency bands. In 5G NR, the two initial operating frequency bands are identified as the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), similar naming issues sometimes occur when referring to FR2, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0038] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have identified the operating bands for these IF bands as the frequency range name FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to IF band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4-a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0039] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" as used herein can broadly indicate a frequency that can be less than 6 GHz, it can be within FR1, or it can include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the term "millimeter wave" as used herein can broadly indicate a frequency that can include intermediate frequency band frequencies, and can be within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or it can be within the EHF band. It is contemplated that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0040] As further illustrated in FIG1, one or more computing devices (e.g., computing device 140a, computing device 140b, computing device 140c) may communicate with one or more other devices. For example, computing device 140a may communicate with UE 120, base station 110, and / or server 150, among other examples. Although computing device 140a is shown outside the coverage area of ​​base station 110, computing device 140a may alternatively be located within the coverage area of ​​base station 110 and communicate with UE 120. In some aspects, computing device 140b may communicate with server 150 via base station 110 (e.g., cellular base station 110) and one or more network controllers 130 (e.g., one or more network controllers 130 included in the cellular core network). In some aspects, UE 120 may communicate with server 150 via base station 110 and one or more network controllers 130. In some respects, computing device 140C can communicate with server 150 via base station 110 (e.g., computer network base station 110 such as base station 110e) and one or more network controllers 130 (e.g., included in one or more network controllers 130 in a computer network).

[0041] The computing device described herein may include a personal computer, a laptop computer, a tablet computer, or another type of electronic user equipment that includes a boot chain. The boot chain includes firmware that the computing device can use to boot the computing device into an operating configuration that allows the operating system (OS) of the computing device to be loaded. Examples of boot chains include Basic Input / Output System (BIOS), Extensible Firmware Interface (EFI), and / or Unified EFI (UEFI), among others.

[0042] Server 150 may include enterprise servers, on-premises servers (e.g., servers located on-site or in a data center managed by the entity), and / or cloud-based servers (e.g., servers located off-site and providing access to the server via a cloud computing interface), and other examples. Cloud computing refers to the network-based on-demand availability of computer system resources, such as data storage and computing power. Cloud computing providers typically offer services under different service models, including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). Server 150 may host or store information technology (IT) materials, information, and / or electronic archives associated with the entity. Entities may include enterprises, educational institutions, and / or government entities, and other examples.

[0043] In some aspects, UE 120 may include a communication manager 160. As described in more detail elsewhere herein, the communication manager 160 may establish a connection with server 150 via wireless network 100 (e.g., via base station 110 and / or network controller 130, and other examples); receive at least one of firmware image files or software image files from server 150 and via the connection via wireless network 100; and send at least one of firmware image files or software image files to computing devices (e.g., computing device 140a, computing device 140b). Additionally or alternatively, the communication manager 160 may perform one or more other operations described herein.

[0044] In some aspects, computing device 140 may include communication manager 170. As described in more detail elsewhere herein, communication manager 170 may receive at least one of firmware image files or software image files from at least one of UE 120 or server 150; and use at least one of the firmware image files or software image files to perform recovery operations of computing device 140. Alternatively or additionally, communication manager 170 may perform one or more other operations described herein.

[0045] As stated above, Figure 1 is provided only as an example. Other examples may differ from those described in conjunction with Figure 1.

[0046] Figure 2 is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0047] At base station 110, transmitting processor 220 can receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmitting processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 can process (e.g., encode and modulate) the data for UE 120, at least in part, based on the MCS(multiple) selected for UE 120, and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., Semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding data machines 232 (e.g., T data machines) (shown as data machines 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of data machine 232. Each data machine 232 can use its respective modulator component to process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each data unit 232 may also use its own modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a downlink signal. Data units 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas), wherein the set of corresponding antennas is shown as antennas 234a to 234t.

[0048] At UE 120, a set of antennas 252 (shown as antennas 252a to 252R) can receive downlink signals from base station 110 and / or other base stations 110, and can provide a set of received signals (e.g., R received signals) to a set of data terminals 254 (e.g., R data terminals) shown as data terminals 254a to 254R. For example, each received signal can be provided to a demodulator component (shown as DEMOD) of data terminal 254. Each data terminal 254 can use its respective demodulator component to modulate (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each data terminal 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from data terminal 254, can perform MIMO detection on the received symbols (if applicable), and can provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) detected symbols, provide decoded data for UE 120 to data slot 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some examples, one or more components of UE 120 may be included in housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include one or more devices, such as those in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more collections of antenna elements and / or one or more antenna arrays, and other examples, or may be included therein. Antenna panels, antenna groups, collections of antenna elements and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), collections of coplanar antenna elements, collections of non-coplanar antenna elements and / or one or more antenna elements coupled to one or more transmitting and / or receiving assemblies (such as one or more assemblies of FIG. 2).

[0051] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-encoded (if applicable) by the TX MIMO processor 266, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmitting processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., refer to Figures 5-10).

[0052] At base station 110, uplink signals from UE 120 and / or other UEs can be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data slot 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule downlink and / or uplink communication for one or more UEs 120. In some examples, modem 232 of base station 110 may include modulator and demodulator. In some examples, base station 110 includes transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., refer to Figures 5-10).

[0053] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with remote computing device recovery, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform or direct the operation of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include non-transitory computer-readable media storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct operations such as process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes as described herein. In some examples, execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, among others.

[0054] In some aspects, UE 120 includes components for establishing a connection with server 150 via wireless network 100; components for receiving at least one of firmware image files or software image files from server 150 and via the connection via wireless network 100; and / or components for transmitting at least one of firmware image files or software image files to computing device 140. Components for UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 160, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0055] Although the boxes in Figure 2 are illustrated as different components, the functions described above with respect to the boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be performed by or under the control of the controller / processor 280.

[0056] As stated above, Figure 2 is provided only as an example. Other examples may differ from those described in conjunction with Figure 2.

[0057] FIG3 is a diagram of an example computing device 140 according to the present disclosure. As shown in FIG3, the computing device 140 may include a bus 310, a processor 320, a memory 330, an input component 340, an output component 350, a communication component 360, and a chipset 370.

[0058] Bus 310 includes one or more components enabling wired and / or wireless communication between components of computing device 140. Bus 310 can couple two or more components of FIG. 3 together, such as via operative coupling, communicative coupling, electronic coupling, and / or electrical coupling. Processor 320 includes a central processing unit, graphics processing unit, microprocessor, controller, microcontroller, digital signal processor, field-programmable gate array, application-specific integrated circuit, and / or another type of processing component. Processor 320 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 320 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

[0059] Memory 330 includes volatile and / or non-volatile memory. For example, memory 330 may include random access memory (RAM), read-only memory (ROM), a hard disk drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). Memory 330 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and / or removable memory (e.g., removable via a Universal Serial Bus connection). Memory 330 may be a non-transitory computer-readable medium. Memory 330 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of computing device 140. In some implementations, memory 330 includes one or more memory units such as those coupled to one or more processors (e.g., processor 320) via bus 310. The memory 330 may include multiple memory devices and / or various types of memory devices, such as RAM devices, ROM devices, storage devices (e.g., hard disk drives or solid-state drives (SSDs)), flash memory devices, and / or another type of memory device.

[0060] Input component 340 enables computing device 140 to receive input, such as user input and / or sensed input. For example, input component 340 may include a touch screen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, accelerometer, gyroscope, and / or actuator. Output component 350 enables computing device 140 to provide output, such as via a display, speaker, and / or light-emitting diode. Communication component 360 enables computing device 140 to communicate with other devices via wired and / or wireless connections. For example, communication component 360 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna. In some aspects, computing device 140 includes multiple communication components 360, such as the multiple components of UE 120 described above in conjunction with FIG. 2.

[0061] The computing device 140 can perform one or more operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 330) can store a set of instructions (e.g., one or more instructions or code) for execution by the processor 320. The processor 320 can execute the set of instructions to perform one or more operations or procedures described herein. In some implementations, execution of the set of instructions by one or more processors 320 causes one or more processors 320 and / or the computing device 140 to perform one or more operations or procedures described herein. In some implementations, hard-wired circuitry is used instead of or in combination with instructions to perform one or more operations or procedures described herein. Additionally or alternatively, the processor 320 can be configured to perform one or more operations or procedures described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0062] The chipset 370 may include hardware components (e.g., electronic components, integrated circuitry) configured to manage and / or facilitate the flow of data, information, and / or instructions between one or more other hardware components of the computing device 140 via bus 310 (e.g., a front-side bus (FSB) and / or another type of bus). For example, the chipset 370 may manage and / or facilitate the flow of data, information, and / or instructions between the communication manager 170, processor 320, memory 330, peripheral devices such as input components 340 and output components 350, and / or communication components 360, and other examples. The chipset 370 may be configured to perform memory controller functions, graphics controller functions, Fast Peripheral Component Interconnect (PCIe) controller functions, and / or other functions.

[0063] The chipset 370 may be located on the motherboard of the computing device 140 and / or on another circuit board of the computing device 140. In some aspects, the chipset 370 includes multiple electronic components, such as a northbridge and / or a southbridge, and other examples. Alternatively, the chipset 370 may be included in a single electronic component. Additionally and / or alternatively, all or part of the functionality and / or hardware of the chipset 370 may be integrated into another component of the processor 320, memory 330, and / or components of the computing device 140.

[0064] The processor 320, memory 330, and / or chipset 370 may perform one or more operations to boot the computing device 140 and / or load the OS of the computing device 140. Booting (or bootstrapping) refers to a sequence of operations that initialize the hardware of the computing device 140, test the hardware of the computing device 140 (referred to as power-on self-test (POST)), and / or load portions of the OS into memory 330 so that the OS can be loaded and executed by the processor 320.

[0065] As shown in FIG3, the boot chain 380 may be stored in the memory 330 of the computing device 140, such as ROM, flash memory, immutable storage, and / or another type of memory component. The boot chain 380 may include firmware such as BIOS or UEFI, and other examples. The processor 320 may execute the boot chain 380 (e.g., directly from the memory 330) to execute a boot sequence to boot the computing device 140. For example, the processor 320 may use the boot chain 380 to perform POST to initialize the chipset 370, communication components 360, and / or peripheral devices of the computing device 140 (e.g., input components 340 and / or output components 350), and other examples. If the POST is successful, the processor 320 may continue to load one or more partition tables, allowing the processor 320 to use the boot chain 380 to execute a bootloader to load the OS 390 of the computing device 140.

[0066] In some aspects, the computing device 140 includes components for receiving at least one of a firmware image file or a software image file from at least one of a UE 120 or a server 150; and / or components for performing a recovery operation of the computing device 140 using at least one of the firmware image file or the software image file. In some aspects, the components for the computing device 140 to perform the operations described herein may include, for example, one or more of a communication manager 170, a processor 320, a memory 330, an input component 340, an output component 350, a communication component 360, and / or a chipset 370, as well as other examples.

[0067] The number and arrangement of components shown in FIG3 are provided as examples. Computing device 140 may include additional, fewer, different, or differently arranged components compared to those shown in FIG3. Alternatively, a set of components of computing device 140 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of computing device 140.

[0068] FIG4 is a diagram of an exemplary server 150 according to the present disclosure. As shown in FIG4, the server 150 may include a bus 410, a processor 420, a memory 430, an input component 440, an output component 450, and a communication component 460.

[0069] Bus 410 includes one or more components enabling wired and / or wireless communication between components of server 150. Bus 410 can couple two or more components of FIG. 4 together, such as via operative coupling, communicative coupling, electronic coupling, and / or electrical coupling. Processor 420 includes a central processing unit, graphics processing unit, microprocessor, controller, microcontroller, digital signal processor, field-programmable gate array, application-specific integrated circuit, and / or another type of processing component. Processor 420 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 420 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

[0070] Memory 430 includes volatile and / or non-volatile memory. For example, memory 430 may include RAM, ROM, a hard disk drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). Memory 430 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and / or removable memory (e.g., removable via a Universal Serial Bus connection). Memory 430 may be a non-transitory computer-readable medium. Memory 430 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of server 150. In some implementations, memory 430 includes one or more memories such as those coupled to one or more processors (e.g., processor 420) via bus 410.

[0071] Input component 440 enables server 150 to receive input, such as user input and / or sensed input. For example, input component 440 may include a touchscreen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, accelerometer, gyroscope, and / or actuator. Output component 450 enables server 150 to provide output, such as via a display, speaker, and / or light-emitting diode. Communication component 460 enables server 150 to communicate with other devices via wired and / or wireless connections. For example, communication component 460 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna.

[0072] Server 150 may perform one or more operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 430) may store a set of instructions (e.g., one or more instructions or code) for execution by processor 420. Processor 420 may execute the set of instructions to perform one or more operations or procedures described herein. In some implementations, execution of the set of instructions by one or more processors 420 causes one or more processors 420 and / or server 150 to perform one or more operations or procedures described herein. In some implementations, hard-wired circuitry is used instead of or in combination with instructions to perform one or more operations or procedures described herein. Additionally or alternatively, processor 420 may be configured to perform one or more operations or procedures described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0073] As described above, server 150 may be associated with an entity and may store various electronic files associated with the entity (e.g., in memory 430). Examples include firmware image file 470 and / or software image file 480, among others. Firmware image file 470 may include boot chain image files, BIOS image files, and / or UEFI image files that can be used to reimage and / or repair the boot chain of the computing device 140 associated with the entity, among others. Software image file 480 may include OS image files and / or another type of electronic file (or electronic file) that can be used to reimage and / or repair the OS of the computing device 140 associated with the entity.

[0074] The number and arrangement of components shown in Figure 4 are provided as examples. Server 150 may include additional, fewer, different, or differently arranged components compared to those shown in Figure 4. Alternatively, a set of components of server 150 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of server 150.

[0075] In some cases, a computing device may become inoperable. For example, one or more electronic files of the computing device may be corrupted or deleted, which may cause the computing device to be unable to load its OS and / or unable to boot. As used herein, a “completely inoperable” computing device refers to a computing device with an inoperable boot chain. An inoperable boot chain may include a corrupted or deleted boot chain image file, preventing the computing device’s processor from executing the boot chain to boot the computing device. As used herein, a “partially inoperable” computing device refers to a computing device that can load and execute a valid boot chain but cannot load its OS. The OS may be corrupted and / or one or more electronic files of the OS may be deleted, causing the computing device to be unable to load and execute the OS.

[0076] Typically, when a computing device associated with an entity becomes inoperable, it is taken to the entity's IT service desk for repair. This can be a time-consuming process, as the user must bring the computing device to the IT service desk, potentially resulting in a loss of productivity for both the user and the computing device. Furthermore, in some cases, such as when the user is operating the computing device remotely (e.g., working from home, remote work, studying away from campus), bringing the computing device to the IT service desk may be impractical due to travel distance, travel restrictions, and / or delivery time.

[0077] An alternative method could be to provide a firmware image file (e.g., a boot chain image file, BIOS image file, UEFI image file) and / or a software image file (e.g., an OS image file) to an optical disc, a Universal Serial Bus (USB) drive, a Secure Digital (SD) card, or another type of portable storage device, and mail the portable storage device to the user, allowing the user to use the firmware image file and / or software image file to perform a recovery of the computing device. However, this is also time-consuming and results in a loss of productivity for the computing device (e.g., in some cases, because the delivery of the portable storage device may take days or weeks).

[0078] Some aspects described herein enable the remote recovery of non-operational computing devices (e.g., non-operational computing device 140) without requiring the non-operational computing device to be taken to an entity's IT service desk and / or without requiring the mailing of a portable storage device containing firmware and / or software image files. As described herein, the non-operational computing device can communicate with a server associated with an entity (e.g., server 150) to obtain the firmware and / or software image files via a wireless network (e.g., wireless network 100). For example, a UE (e.g., UE 120) can establish a connection with the server via the wireless network and can authenticate with the server using an authentication certificate associated with the non-operational computing device. The UE can then receive the firmware and / or software image files from the server via the wireless network, and the UE can provide the firmware and / or software image files to the non-operational computing device using a wired or wireless connection. Alternatively, the non-operational computing device may include wireless communication capabilities that can be used by the boot chain and / or chipset (e.g., chipset 370) of the non-operational computing device to communicate with a server to receive firmware image files and / or software image files from the server via a wireless network (e.g., without assistance from the UE).

[0079] In this way, non-operational computing devices (e.g., fully non-operational computing devices, partially non-operational computing devices) can be remotely restored without having to bring them to a physical IT service desk. This reduces downtime of non-operational computing devices (e.g., from days or weeks to minutes), which increases the productivity of non-operational computing devices.

[0080] Figure 5 is a diagram illustrating an example 500 associated with recovery of a remote computing device according to the present disclosure. As shown in Figure 5, example 500 may include communication between multiple communication devices. The communication devices may include computing device 140, UE 120, base station 110, network controller 130, and server 150.

[0081] Computing device 140 may be associated with an entity such as a business, educational institution, or government entity, among other examples. In some aspects, computing device 140 is an operational computing device. In some aspects, computing device 140 is a non-operational computing device, such as a completely non-operational computing device or a partially non-operational computing device. In some aspects, computing device 140 is included in a wireless network, such as wireless network 100. In some aspects, computing device 140 is not included or registered in a wireless network, or computing device 140 is outside the coverage area of ​​the wireless network.

[0082] Server 150 may include an on-site server located at the entity's location (e.g., a data center managed by the entity, an office site of the entity) or a cloud-based server hosted off-site in a cloud computing environment. Server 150 may store image files of the entity's computing devices. Image files may include firmware image files 470, software image files 480, and / or another type of file that can be used to image, reimage, or repair the boot chain or OS of the computing devices associated with the entity. Server 150 may be communicatively coupled to the entity's network (e.g., a private network, a secure network) and may be accessed by computing device 140 via a secure channel after authentication with server 150. Secure channels may include VPN tunnels, Hypertext Transfer Protocol Secure (HTTPS) connections, and / or cloud-based login portals, among other examples.

[0083] Authentication refers to verifying the identity of computing device 140 and / or verifying the access rights of computing device 140. For example, authentication credentials (e.g., security tokens, security profiles, entity profiles, security keys, domain certificates, certificates) may be provided to (and stored by) computing device 140. A certificate may indicate one or more identifiers associated with computing device 140, which can be used to verify the identity of computing device 140. Furthermore, a certificate may indicate one or more access permissions for computing device 140, such as permissions to access an entity's network and / or permissions to access image files stored by server 150.

[0084] The UE 120, base station 110, and network controller 130 may be included in a wireless network. The UE 120 and base station 110 may communicate on a radio access link that includes uplink and downlink. The base station 110 and network controller 130 may communicate on a backhaul link, which may include a wireless link or a wired link.

[0085] The UE 120 and the computing device 140 can communicate over a wireless connection (e.g., Bluetooth connection, Wi-Fi direct connection, or cellular connection, and other examples) and / or a wired connection (e.g., USB connection, Ethernet connection). The UE 120 and the server 150 can communicate over a wireless network via a base station 110 and / or one or more network controllers 130.

[0086] As described above, computing device 140 may include non-operational computing devices. In order to restore computing device 140 (e.g., without using a portable storage device or by taking computing device 140 to a physical IT service desk), UE 120 may obtain firmware image files and / or software image files from server 150, and may provide firmware image files and / or software image files to computing device 140 so that computing device 140 can use the firmware image files and / or software image files to perform a recovery operation.

[0087] At 505, UE 120 can establish a connection with server 150 via a wireless network. For example, UE 120 can establish a wireless connection with base station 110, which may include a cellular base station (e.g., where the wireless connection includes a cellular connection such as an LTE connection, a 5G NR connection, or another type of cellular connection), a Wi-Fi router (e.g., where the wireless connection includes a Wi-Fi connection), and / or another type of wireless communication device communicating with wireless and / or wired computer networks. In some aspects, UE 120 may initiate a Random Access Channel (RACH) procedure with base station 110, or perform another type of connection establishment procedure according to one or more communication protocols (e.g., Bluetooth protocol, Wi-Fi protocol). UE 120 can establish a secure channel with server 150 via a wireless connection and via network controller 130. Network controller 130 may include 5G NR network function devices, gateways, LAN gateways, switches, and / or another type of computer network controller. Secure channels may include VPN tunnels between UE 120 and server 150 via wireless networks (e.g., via base station 110 and / or via one or more network controllers 130), HTTPS connections between UE 120 and server 150, and / or other types of secure channels.

[0088] UE 120 may be provided with an entity profile (e.g., an IT profile, an enterprise profile) associated with the entity and computing device 140. The entity profile may be stored by UE 120 and may include the authentication certificate of computing device 140. The entity profile enables UE 120 to authenticate computing device 140 to server 150 and to establish a secure channel with server 150 using the authentication certificate of computing device 140, which may not be feasible when computing device 140 is not operational. In some aspects, UE 120 is provided with an entity profile before UE 120 is deployed to the service. In some aspects, a separate entity profile is issued by the entity to UE 120, which enables UE 120 to establish a secure channel with server 150 to obtain the entity profile of computing device 140.

[0089] At 510, UE 120 can receive firmware image files (e.g., firmware image file 470, such as a boot chain image file, BIOS image file, or UEFI image file, and other examples) and / or software image files (e.g., software image file 480, such as an OS image file) from server 150 via a wireless network connection. Specifically, UE 120 can receive firmware image files and / or software image files using a secure channel over the connection to server 150. In some aspects, UE 120 and computing device 140 (e.g., via UE 120, base station 110, and one or more network controllers 130) establish a secure channel (e.g., VPN tunnel, HTTPS connection) between computing device 140 and server 150. In this way, firmware image files and / or software image files are sent from server 150 to computing device 140 along a fully secure channel, which increases the security of the computer network when remotely restoring computing device 140.

[0090] At 515, UE 120 may send (and computing device 140 may receive) firmware image files and / or software image files. In some aspects, UE 120 sends (and computing device 140 receives) firmware image files and / or software image files to computing device 140 via a wired connection (e.g., USB connection, Ethernet connection). In some aspects, UE 120 sends (and computing device 140 receives) firmware image files and / or software image files to computing device 140 via a wireless connection (e.g., Bluetooth connection, Wi-Fi connection, cellular connection).

[0091] In some aspects, computing device 140 may use its boot chain 380 to receive firmware image files and / or software image files. For example, even if computing device 140 may be completely inoperable, processor 320 and / or chipset 370 of computing device 140 may use boot chain 380 to access communication components 360 of computing device 140. The immutable storage in memory 330 may be provided with a networking protocol stack that can be used by processor 320 and / or chipset 370 (e.g., via boot chain 380) without fully booting computing device 140. This enables computing device 140 to receive recovery files (e.g., firmware image files and / or software image files) even if computing device 140 cannot load and execute a valid boot chain 380.

[0092] At 520, the computing device 140 performs a recovery operation using a firmware image file and / or a software image file. This enables the recovery of the computing device 140 without having to bring the computing device 140 to a physical IT service desk and / or without waiting for a portable storage device to be delivered.

[0093] In some aspects, when the computing device 140 is a partially non-operating computing device, the UE 120 receives a software image file 480 from the server 150 and sends the software image file 480 to the computing device 140, which performs a recovery operation to repair or re-image the OS 390 of the computing device 140. In some aspects, when the computing device 140 is a completely non-operating computing device, the UE 120 receives a firmware image file 470 from the server 150 and sends the firmware image file 470 to the computing device 140, which performs a recovery operation to repair or re-image the boot chain 380 of the computing device 140. In some aspects, when the computing device 140 is a completely non-operating computing device, the UE 120 receives both the firmware image file 470 and the software image file 480 from the server 150. Here, the UE 120 sends both the firmware image file 470 and the software image file 480 to the computing device 140. The computing device 140 can perform a first recovery operation to repair or re-image the boot chain 380 using the firmware image file 470, and the computing device 140 can perform a second recovery operation (e.g., after performing the first recovery operation) to repair or re-image the OS 390 using the software image file 480.

[0094] As stated above, Figure 5 is provided only as an example. Other examples may differ from those described in conjunction with Figure 5.

[0095] FIG6 is a diagram illustrating Example 600 associated with recovery of a remote computing device according to the present disclosure. Example 600 includes an alternative implementation of Example 500, wherein computing device 140 communicates with server 150 via a wireless network (e.g., via base station 110 and / or one or more network controllers 130) without the assistance from UE 120 as in Example 500.

[0096] At 605, computing device 140 can establish a connection with server 150 via a wireless network. For example, the communication component 360 of computing device 140 may include cellular communication capabilities, and computing device 140 may establish a wireless connection with base station 110 (e.g., computing device 140 may initiate a RACH procedure with base station 110). As another example, computing device 140 may communicate with computer network base station 110 (e.g., base station 110e), which may include a Wi-Fi router (e.g., where the wireless connection includes a Wi-Fi connection) and / or another type of wireless communication device communicating with wireless and / or wired computer networks. Computing device 140 may establish a secure channel with server 150 via a wireless connection and via network controller 130. Secure channels may include a VPN tunnel between computing device 140 and server 150 over a wireless network (e.g., through base station 110 and / or through one or more network controllers 130), an HTTPS connection between computing device 140 and server 150, and / or another type of secure channel.

[0097] Alternatively, computing device 140 may establish another type of wireless connection to connect to server 150 via a wireless network. For example, computing device 140 may establish a Wi-Fi connection with a cellular modem, and the cellular modem may establish a cellular connection with base station 110.

[0098] The computing device 140 may be provided with an entity profile (e.g., an IT profile, an enterprise profile) associated with the entity and the computing device 140. The entity profile may be stored by the computing device 140 and may include the authentication certificate of the computing device 140. The entity profile enables the computing device 140 to authenticate itself to the server 150 and to establish a secure channel with the server 150 using the authentication certificate of the computing device 140.

[0099] At 610, computing device 140 can receive firmware image files (e.g., firmware image file 470, such as a boot chain image file, BIOS image file, or UEFI image file, and other examples) and / or software image files (e.g., software image file 480, such as an OS image file) from server 150 via a wireless network connection. Specifically, computing device 140 can receive firmware image files and / or software image files using a secure channel connected to server 150.

[0100] In some aspects, computing device 140 may use its boot chain 380 to receive firmware image files and / or software image files. For example, even if computing device 140 may be completely inoperable, processor 320 and / or chipset 370 of computing device 140 may use boot chain 380 to access communication components 360 of computing device 140. The immutable storage in memory 330 may be provided with a networking protocol stack that can be used by processor 320 and / or chipset 370 (e.g., via boot chain 380) without fully booting computing device 140. This enables computing device 140 to receive recovery files (e.g., firmware image files and / or software image files) even if computing device 140 cannot load and execute a valid boot chain 380.

[0101] In 615, computing device 140 performs a recovery operation using a firmware image file and / or a software image file. This enables the recovery of computing device 140 without having to bring computing device 140 to a physical IT service desk and / or without waiting for portable storage devices to be delivered.

[0102] In some aspects, when the computing device 140 is a partially non-operating computing device, the computing device 140 receives a software image file 480 from the server 150 and performs a recovery operation to repair or re-image the OS 390 of the computing device 140. In some aspects, when the computing device 140 is a completely non-operating computing device, the computing device 140 receives a firmware image file 470 from the server 150 and performs a recovery operation to repair or re-image the boot chain 380 of the computing device 140. In some aspects, when the computing device 140 is a completely non-operating computing device, the computing device 140 receives both the firmware image file 470 and the software image file 480 from the server 150. Here, the computing device 140 may perform a first recovery operation to repair or re-image the boot chain 380 using the firmware image file 470, and the computing device 140 may perform a second recovery operation (e.g., after performing the first recovery operation) to repair or re-image the OS 390 using the software image file 480.

[0103] As described above, Figure 6 is provided only as an example. Other examples may differ from those described in conjunction with Figure 6.

[0104] FIG7 is a diagram illustrating an exemplary process 700 performed by a UE, for example, according to the present disclosure. The exemplary process 700 is an example in which the UE (e.g., UE 120) performs an operation associated with remote computing device recovery.

[0105] As shown in FIG7, in some aspects, process 700 may include establishing a connection with the server via a wireless network (block 710). For example, the UE (e.g., using the communication manager 160, communication manager 908 and / or connection establishment component 910 depicted in FIG9) may establish a connection with the server via a wireless network, as described above.

[0106] As further shown in FIG7, in some aspects, process 700 may include receiving at least one of a firmware image file or a software image file from a server and via a wireless network connection (block 720). For example, the UE (e.g., using the communication manager 160, communication manager 908 and / or receiving component 902 depicted in FIG9) may receive at least one of a firmware image file or a software image file from a server and via a wireless network connection, as described above.

[0107] As further shown in FIG7, in some aspects, process 700 may include sending at least one of a firmware image file or a software image file to a computing device (block 730). For example, a UE (e.g., using the communication manager 160 and / or the sending component 904 depicted in FIG9) may send at least one of a firmware image file or a software image file to a computing device as described above.

[0108] Process 700 may include other aspects, such as any single aspect or any combination of aspects of one or more other processes described below and / or described elsewhere herein.

[0109] In a first aspect, the computing device includes a fully non-operating computing device having a non-operating boot chain, wherein receiving at least one of a firmware image file or a software image file includes receiving a firmware image file, wherein the firmware image file includes a boot chain image file, and wherein sending at least one of the firmware image file or the software image file to the computing device includes sending a boot chain image file to the computing device.

[0110] In a second aspect, either alone or in combination with the first aspect, process 700 includes receiving a software image file from a server and via a connection through a wireless network; and sending the software image file to a computing device after sending the software image file to the computing device.

[0111] In a third aspect, alone or in combination with one or more of the first to second aspects, the computing device includes a partially non-operating computing device capable of loading a valid boot chain of the computing device rather than an OS of the computing device, wherein receiving at least one of the firmware image file or the software image file includes receiving the software image file, wherein the software image file includes an image file of the OS, and wherein sending at least one of the firmware image file or the software image file to the computing device includes sending the software image file to the computing device.

[0112] In the fourth aspect, sending a software image file to a computing device, either alone or in combination with one or more of the first to third aspects, includes communicating with the boot chain of the computing device to send the software image file to the computing device.

[0113] In the fifth aspect, sending a software image file to a computing device, either alone or in combination with one or more of the first to fourth aspects, includes sending the software image file to the computing device via a wireless connection.

[0114] In the sixth aspect, sending a software image file to a computing device, either alone or in combination with one or more of the first to fifth aspects, includes sending the software image file to the computing device via a wired connection.

[0115] In the seventh aspect, establishing a connection with the server, either alone or in combination with one or more of the first to sixth aspects, includes obtaining a verification certificate associated with the computing device; and using the verification certificate to verify the computing device with the server.

[0116] In the eighth aspect, the authentication certificate is included, either alone or in combination with one or more of the first to seventh aspects, in an entity profile associated with the computing device stored on the UE.

[0117] In the ninth aspect, the server includes a cloud-based server, either alone or in combination with one or more of the first to eighth aspects, and wherein establishing a connection with the server includes authenticating the UE to the server using an authentication certificate associated with the UE.

[0118] In the tenth aspect, the server includes an in-location server, either alone or in combination with one or more of the first to ninth aspects, and wherein establishing a connection with the server includes establishing a secure channel between the UE and the in-location server.

[0119] In the eleventh aspect, receiving at least one of the firmware image files or software image files, alone or in combination with one or more of the first to tenth aspects, includes receiving at least one of the firmware image files or software image files through a secure channel.

[0120] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 700 includes establishing a secure channel between a computing device and a server in the location via a UE, and wherein sending at least one of a firmware image file or a software image file to the computing device includes sending at least one of the firmware image file or the software image file to the computing device via the secure channel.

[0121] Although FIG7 illustrates example blocks of process 700, in some respects process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in FIG7. Alternatively or concurrently, two or more blocks of process 700 may be executed in parallel.

[0122] FIG8 is a diagram illustrating an exemplary process 800 performed, for example, by a computing device according to the present disclosure. Exemplary process 800 is an example in which a computing device (e.g., computing device 140) performs an operation associated with remote computing device recovery.

[0123] As shown in FIG8, in some aspects, process 800 may include receiving at least one of a firmware image file or a software image file from at least one of the UE or the server (box 810). For example, a computing device (e.g., using the communication manager 170, communication manager 1008 and / or receiving component 1002 depicted in FIG10) may receive at least one of the firmware image file or the software image file from at least one of the UE or the server, as described above.

[0124] As further shown in FIG8, in some aspects, process 800 may include performing a recovery operation of the computing device using at least one of a firmware image file or a software image file (block 820). For example, the computing device (e.g., using the communication manager 170, communication manager 1008 and / or recovery component 1010 depicted in FIG10) may use at least one of a firmware image file or a software image file to perform a recovery operation of the computing device, as described above.

[0125] Process 800 may include other aspects, such as any single aspect or any combination of aspects of one or more other processes described below and / or described elsewhere herein.

[0126] In a first aspect, the computing device includes a completely non-operational computing device having a non-operational boot chain, wherein receiving at least one of a firmware image file or a software image file includes receiving a firmware image file, wherein the firmware image file includes a boot chain image file, and wherein performing a recovery operation includes repairing the boot chain using the boot chain image file.

[0127] In a second aspect, processing 800 alone or in combination with the first aspect includes receiving a software image file from at least one of the UE or the server; and using the software image file to perform another recovery operation of the computing device, wherein the other recovery operation includes at least one of: using the software image file to repair the OS of the computing device, or using the software image file to re-image the OS of the computing device.

[0128] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 800 includes repairing the OS of the computing device after performing a recovery operation.

[0129] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the computing device includes a portion of non-operating computing device capable of loading a valid boot chain of the computing device rather than the OS of the computing device, wherein receiving at least one of a firmware image file or a software image file includes receiving a software image file from a UE, wherein the software image file includes an image file of the OS, and wherein performing a recovery operation includes at least one of: using the software image file to repair the OS of the computing device, or using the software image file to re-image at least one of the OS of the computing device.

[0130] In the fifth aspect, receiving at least one of the firmware image files or software image files, alone or in combination with one or more of the first to fourth aspects, includes receiving at least one of the firmware image files or software image files from a server via a UE.

[0131] In the sixth aspect, receiving at least one of the firmware image files or software image files, alone or in combination with one or more of the first to fifth aspects, includes establishing a connection with a server via a wireless network and receiving at least one of the firmware image files or software image files from the server via the wireless network connection.

[0132] In the seventh aspect, the server includes a cloud-based server, either alone or in combination with one or more of the first to sixth aspects, and wherein establishing a connection with the server includes obtaining an authentication certificate associated with the computing device; and using the authentication certificate to authenticate the computing device to the cloud-based server.

[0133] In the eighth aspect, the server includes an on-site server, either alone or in combination with one or more of the first to seventh aspects, and wherein establishing a connection with the server includes establishing a secure channel between the computing device and the on-site server.

[0134] In the ninth aspect, receiving at least one of the firmware image files or software image files, alone or in combination with one or more of the first to eighth aspects, includes receiving at least one of the firmware image files or software image files through a secure channel.

[0135] In the tenth aspect, receiving at least one of the firmware image files or software image files, alone or in combination with one or more of the first to ninth aspects, includes receiving at least one of the firmware image files or software image files from at least one of the UE or the server using at least one of the wired communication interfaces or wireless communication interfaces of the computing device.

[0136] In the eleventh aspect, receiving at least one of the firmware image files or software image files, alone or in combination with one or more of the first to tenth aspects, includes using a boot chain of a computing device to communicate with a wireless communication interface that receives at least one of the firmware image files or software image files.

[0137] Although FIG8 illustrates example blocks of process 800, in some respects process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in FIG8. Alternatively or concurrently, two or more blocks of process 800 may be executed in parallel.

[0138] FIG9 is a diagram of an exemplary device 900 for wireless communication. Device 900 may be a UE (e.g., UE 120), or a UE may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, base station, server, or other communication device). As further shown, device 900 may include a communication manager 908, which may include or be included in a communication manager 160. Communication manager 908 may include a connection establishment component 910, and other examples.

[0139] In some aspects, device 900 may be configured to perform one or more operations described herein in conjunction with Figures 5 and / or 6. Alternatively, device 900 may be configured to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, device 900 and / or one or more components shown in Figure 9 may include one or more components of the UE described above in conjunction with Figure 2. Alternatively, one or more components shown in Figure 9 may be implemented within one or more components described above in conjunction with Figure 2. Alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0140] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog / digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the UE described above in conjunction with FIG. 2.

[0141] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 906. In some aspects, transmitting component 904 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital / analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples), and can transmit the processed signals to device 906. In some aspects, transmitting component 904 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof, as described above in conjunction with FIG. 2. In some aspects, transmitting component 904 may be co-located with receiving component 902 in a transceiver.

[0142] The connection establishment component 910 can establish a connection with a server (e.g., device 906) via a wireless network. The receiving component 902 can receive at least one of a firmware image file or a software image file from the server (e.g., device 906) via the wireless network connection. The sending component 904 can send at least one of the firmware image file or the software image file to a computing device (e.g., another device 906).

[0143] The receiving component 902 can receive software image files from a server (e.g., device 906) and via a connection through a wireless network.

[0144] The sending component 904 may send the software image file to the computing device (e.g., another device 906) after sending the firmware image file to the computing device (e.g., another device 906).

[0145] The connection establishment component 910 can establish a secure channel, such as a VPN tunnel, between a computing device (e.g., another device 906) and a site server (e.g., device 906) via the device 900.

[0146] The number and arrangement of components shown in Figure 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 9. Furthermore, the two or more components shown in Figure 9 may be implemented within a single component, or the single component shown in Figure 9 may be implemented as multiple distributed components. Alternatively or alternatively, the set of components (one or more components) shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0147] FIG10 is a diagram of an exemplary device 1000 for wireless communication. Device 1000 may be a computing device (e.g., computing device 140), or a computing device may include device 1000. In some aspects, device 1000 includes a receiving component 1002 and a transmitting component 1004, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 can use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, base station, server, or other communication device). As further shown, device 1000 may include a communication manager 1008, which may include or be included in a communication manager 170. Communication manager 1008 may include a recovery component 1010, and other examples.

[0148] In some aspects, device 1000 may be configured to perform one or more operations described herein in conjunction with Figures 6 and / or 7. Alternatively, device 1000 may be configured to perform one or more processes described herein, such as process 800 of Figure 8. In some aspects, device 1000 and / or one or more components shown in Figure 10 may include one or more components of the computing device described above in conjunction with Figure 3. Alternatively, one or more components shown in Figure 10 may be implemented within one or more components described above in conjunction with Figure 3. Alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0149] The receiving component 1002 may receive communications from the device 1006, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog / digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include a bus and / or communication interface as described in conjunction with FIG. 3.

[0150] Transmitting component 1004 can transmit communications to device 1006, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of device 1000 can generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1006. In some aspects, transmitting component 1004 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital / analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples), and can transmit the processed signals to device 1006. In some aspects, transmitting component 1004 may include a bus and / or communication interface as described in conjunction with FIG3. In some aspects, transmitting component 1004 may be co-located with receiving component 1002 in a transceiver.

[0151] The receiving component 1002 may receive at least one of a firmware image file or a software image file from the device 1006 (e.g., at least one of a UE or a server). The recovery component 1010 may use at least one of the firmware image file or the software image file to perform a recovery operation of the device 1000.

[0152] The receiving component 1002 can receive a software image file from the device 1006 (e.g., at least one of the UE or the server).

[0153] The recovery component 1010 may use a software image file to perform another recovery operation on the device 1000. The recovery operation may include at least one of the following: using a software image file to repair the OS of the device 1000, or using a software image file to re-image the OS of the device 1000.

[0154] The recovery component 1010 can repair the OS of the device 1000 after performing a recovery operation.

[0155] The number and arrangement of components shown in Figure 10 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 10. Furthermore, the two or more components shown in Figure 10 may be implemented within a single component, or the single component shown in Figure 10 may be implemented as multiple distributed components. Alternatively or alternatively, the set of components (one or more components) shown in Figure 10 may perform one or more functions described as being performed by another set of components shown in Figure 10.

[0156] The following provides an overview of some aspects of this disclosure:

[0157] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: establishing a connection with a server via a wireless network; receiving at least one of a firmware image file or a software image file from the server and via the connection via the wireless network; and sending at least one of the firmware image file or the software image file to a computing device.

[0158] Aspect 2: According to the method of aspect 1, wherein the computing device includes a fully non-operating computing device having a non-operating boot chain, wherein receiving at least one of a firmware image file or a software image file includes: receiving a firmware image file, wherein the firmware image file includes a boot chain image file, and wherein sending at least one of the firmware image file or the software image file to the computing device includes: sending the boot chain image file to the computing device.

[0159] Aspect 3: According to the method of aspect 2, the method further includes: receiving a software image file from a server and via a connection through a wireless network; and sending the software image file to a computing device after sending the software image file to the computing device.

[0160] Aspect 4: A method according to one or more aspects 1-3, wherein the computing device includes a portion of non-operating computing device capable of loading a valid boot chain of the computing device rather than an operating system (OS) of the computing device; wherein receiving at least one of a firmware image file or the software image file includes: receiving a software image file, wherein the software image file includes an image file of an OS; and wherein sending the firmware image file or at least one of the software image files to the computing device includes: sending the software image file to the computing device.

[0161] Aspect 5: According to the method of aspect 4, sending the software image file to the computing device includes: communicating with the boot chain of the computing device to send the software image file to the computing device.

[0162] Aspect 6: According to the method of aspect 4 or 5, sending the software image file to the computing device includes: sending the software image file to the computing device via a wireless connection.

[0163] Aspect 7: The method according to one or more aspects 4-7, wherein sending a software image file to a computing device includes: sending the software image file to the computing device via a wired connection.

[0164] Aspect 8: The method according to one or more aspects 1-8, wherein establishing a connection with the server includes: obtaining an authentication certificate associated with the computing device; and authenticating the computing device to the server using the authentication certificate.

[0165] Aspect 9: According to the method of aspect 8, wherein the authentication certificate is included in an entity profile associated with the computing device stored on the UE.

[0166] Aspect 10: A method according to one or more aspects 1-9, wherein the server includes a cloud-based server, and wherein establishing a connection with the server includes: authenticating the UE to the server using an authentication certificate associated with the UE.

[0167] Aspect 11: A method of one or more of Aspect 10, wherein the server includes an on-site server, and wherein establishing a connection with the server includes establishing a secure channel between the UE and the on-site server.

[0168] Aspect 12: According to the method of aspect 11, receiving at least one of the firmware image file or software image file includes receiving at least one of the firmware image file or software image file through a secure channel.

[0169] Aspect 13: The method according to aspect 11 or 12 further includes: establishing a secure channel between a computing device and a server in the location via a UE, wherein sending at least one of a firmware image file or a software image file to the computing device includes: sending at least one of the firmware image file or the software image file to the computing device via the secure channel. Specifically, sending at least one of the firmware image file or the software image file to the computing device includes: sending at least one of the firmware image file or the software image file to the computing device via the secure channel.

[0170] Aspect 14: A method of wireless communication performed by a computing device, the method comprising: receiving at least one of a firmware image file or a software image file from at least one of a user equipment (UE) or a server; and using at least one of the firmware image file or the software image file to perform a recovery operation for the computing device.

[0171] Aspect 15: According to the method of aspect 14, wherein the computing device includes a fully non-operating computing device having a non-operating boot chain, wherein receiving at least one of a firmware image file or a software image file includes: receiving a firmware image file, wherein the firmware image file includes a boot chain image file, and wherein performing a recovery operation includes: repairing the boot chain using the boot chain image file.

[0172] Aspect 16: The method according to aspect 15 further includes: receiving a software image file from at least one of the UE or the server; and using the software image file to perform another recovery operation of the computing device, wherein the other recovery operation includes at least one of: using the software image file to repair the operating system (OS) of the computing device, or using the software image file to re-image the OS of the computing device.

[0173] Aspect 17: According to the method of aspect 16, the method further includes: repairing the operating system (OS) of the computing device after performing the recovery operation.

[0174] Aspect 18: A method according to one or more aspects of aspects 14-17, wherein the computing device includes a partially non-operating computing device capable of loading a valid boot chain of the computing device rather than the operating system (OS) of the computing device, wherein receiving at least one of a firmware image file or a software image file includes: receiving a software image file, wherein the software image file includes an image file of the OS; and wherein performing a recovery operation includes at least one of: using the software image file to repair the operating system (OS) of the computing device, or using the software image file to re-image the OS of the computing device.

[0175] Aspect 19: The method according to one or more aspects 14-18, wherein receiving at least one of the firmware image file or software image file includes: receiving at least one of the firmware image file or software image file from a server via a UE.

[0176] Aspect 20: The method according to one or more aspects of aspects 14-19, wherein receiving at least one of the firmware image file or software image file includes: establishing a connection with a server via a wireless network; and receiving at least one of the firmware image file or software image file from the server via the connection via the wireless network.

[0177] Aspect 21: According to the method of aspect 20, wherein the server includes a cloud-based server; and wherein establishing a connection with the server includes: obtaining an authentication certificate associated with the computing device; and authenticating the computing device to the cloud-based server using the authentication certificate.

[0178] Aspect 22: According to the method of aspect 20 or 21, wherein the server includes an on-site server; and wherein establishing a connection with the server includes: establishing a secure channel between the computing device and the on-site server.

[0179] Aspect 23: According to the method of aspect 22, receiving at least one of the firmware image file or the software image file includes: receiving at least one of the firmware image file or the software image file through a secure channel.

[0180] Aspect 24: The method according to one or more aspects 14-23, wherein receiving at least one of the firmware image file or software image file includes: receiving at least one of the firmware image file or software image file from at least one of the UE or the server using at least one of the wired communication interface or the wireless communication interface of the computing device.

[0181] Aspect 25: The method according to one or more aspects 14-24, wherein receiving at least one of the firmware image file or software image file includes: using a boot chain of a computing device to communicate with a wireless communication interface that receives at least one of the firmware image file or software image file.

[0182] Aspect 26: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods of aspects 1-13.

[0183] Aspect 27: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors being configured to perform a method according to one or more aspects of aspects 1-13.

[0184] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one component for performing a method according to one or more aspects 1-13.

[0185] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods of one or more aspects of aspects 1-13.

[0186] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 1-13.

[0187] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more methods of aspects 14-25.

[0188] Aspect 32: A device for wireless communication, the device including a memory and one or more processors coupled to the memory, the one or more processors being configured to perform a method according to one or more aspects of aspects 14-25.

[0189] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing a method according to one or more aspects 14-25.

[0190] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods of one or more aspects of aspects 14-25.

[0191] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions which, when executed by one or more processors of a device, cause the device to perform the methods of one or more aspects of aspects 14-25.

[0192] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made based on the foregoing disclosure, or may be derived from practice in the aspects described.

[0193] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referring to software, firmware, middleware, microcode, hardware description languages, or others, software should be interpreted broadly as representing instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, and other examples. As used herein, a "processor" is implemented using hardware and / or a combination of hardware and software. It is clear that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in any way. Therefore, the operation and behavior of the systems and / or methods described herein do not refer to any specific software code, as those skilled in the art will generally understand that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0194] As used herein, “satisfying the threshold” may refer to values ​​greater than the threshold, greater than or equal to the threshold, less than or equal to the threshold, or not equal to the threshold, depending on the context.

[0195] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of different aspects. Many of these features may be combined in ways not specifically described in the claims and / or not disclosed in the specification. The disclosure of an aspect includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase “at least one of…” in the list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., any other ordering of a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c).

[0196] No element, action, or instruction as used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where the intention is for only one item, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has / have / having” are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise. Furthermore, as used herein, the term "or" is intended to be inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise explicitly stated (e.g., if used in combination with "either of the two" or "only one of..."). [Simplified Explanation of the Diagram]

[0016] To gain a more detailed understanding of the foregoing features of this disclosure, reference can be made to various aspects for a more specific description of the above-briefly summarized content, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as the description may allow for other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an exemplary computing device according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example server according to the present disclosure.

[0021] Figures 5 and 6 are illustrations of examples of recovery associated with a remote computing device according to the present disclosure.

[0022] Figures 7 and 8 are diagrams illustrating an exemplary process associated with the recovery of a remote computing device according to the present disclosure.

[0023] Figures 9 and 10 are diagrams of exemplary devices for wireless communication according to the present disclosure.

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: Establish a connection with the server via wireless network; Receive at least one of a firmware image file or a software image file from the server and via the connection through the wireless network; and send at least one of the firmware image file or the software image file to a computing device.

2. The method according to request item 1, wherein, The computing device includes a fully non-operational computing device having a non-operational boot chain; wherein receiving at least one of the firmware image file or the software image file includes: receiving the firmware image file, wherein the firmware image file includes a boot chain image file; and wherein sending at least one of the firmware image file or the software image file to the computing device includes: sending the boot chain image file to the computing device.

3. The method according to claim 2 further includes: The software image file is received from the server and via the connection through the wireless network; And after sending the firmware image file to the computing device, the software image file is sent to the computing device.

4. The method according to request item 1, wherein, The computing device includes a portion of non-operating computing device capable of loading a valid boot chain for the computing device instead of the operating system (OS) of the computing device; wherein receiving at least one of the firmware image file or the software image file includes: receiving the software image file, wherein the software image file includes an image file of the OS; and wherein sending at least one of the firmware image file or the software image file to the computing device includes: sending the software image file to the computing device.

5. The method according to request item 4, wherein, Sending the software image file to the computing device includes: communicating with the boot chain of the computing device to send the software image file to the computing device.

6. The method according to claim 4, wherein, Sending the software image file to the computing device includes: sending the software image file to the computing device via a wireless connection.

7. The method according to request item 4, wherein, Sending the software image file to the computing device includes: sending the software image file to the computing device via a wired connection.

8. A method of wireless communication performed by a computing device, comprising: Receive at least one of a firmware image file or a software image file from at least one of a user equipment (UE) or a server; And to perform a recovery operation for the computing device using at least one of the firmware image file or the software image file.

9. The method according to claim 8, wherein, The computing device includes a fully non-operating computing device having a non-operating boot chain; wherein receiving at least one of the firmware image file or the software image file includes: receiving the firmware image file, wherein the firmware image file includes a boot chain image file; and wherein performing the recovery operation includes: using the boot chain image file to repair the boot chain.

10. The method according to claim 9, further comprising: Receive the software image file from at least one of the UE or the server; And to perform another recovery operation on the computing device using the software image file, wherein the other recovery operation includes at least one of the following: using the software image file to repair the operating system (OS) of the computing device, or using the software image file to re-image the OS of the computing device.

11. The method according to claim 10, further comprising: After performing the recovery operation, the operating system (OS) of the computing device is repaired.

12. The method according to claim 8, wherein, The computing device includes a portion of non-operating computing device capable of loading a valid boot chain for the computing device instead of the operating system (OS) of the computing device; wherein receiving at least one of the firmware image file or the software image file includes: receiving the software image file from the UE, wherein the software image file includes an image file of the OS; and wherein performing the recovery operation includes at least one of: using the software image file to repair the operating system (OS) of the computing device, or using the software image file to re-image the OS of the computing device.

13. The method according to claim 8, wherein, Receiving at least one of the firmware image file or the software image file includes: receiving at least one of the firmware image file or the software image file from the server via the UE.

14. A user equipment (UE) for wireless communication, comprising: Memory; One or more processors coupled to the memory are configured to: establish a connection with a server via a wireless network; Receive at least one of a firmware image file or a software image file from the server and via the connection through the wireless network; and send at least one of the firmware image file or the software image file to a computing device.

15. The UE according to request item 14, wherein, In order to establish the connection with the server, the one or more processors are configured to: obtain an authentication certificate associated with the computing device; and use the authentication certificate to authenticate the computing device with the server.

16. The UE according to request item 15, wherein, The authentication certificate is included in an entity profile associated with the computing device stored on the UE.

17. The UE according to request item 14, wherein, The server includes a cloud-based server; and wherein, in order to establish the connection with the server, the one or more processors are configured to: authenticate the UE to the server using an authentication certificate associated with the UE.

18. The UE according to request item 14, wherein, The server includes an in-location server; and wherein, in order to establish the connection with the server, the one or more processors are configured to: establish a secure channel between the UE and the in-location server.

19. The UE according to request item 18, wherein, In order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: receive at least one of the firmware image file or the software image file through the secure channel.

20. The UE according to request item 18, wherein, The one or more processors are further configured to: establish the secure channel between the computing device and the server in the location via the UE; In addition, in order to send at least one of the firmware image file or the software image file to the computing device, the one or more processors are configured to send at least one of the firmware image file or the software image file to the computing device through the secure channel.

21. A computing device for wireless communication, comprising: Memory; One or more processors coupled to the memory are configured to: receive at least one of a firmware image file or a software image file from at least one of a user equipment (UE) or a server; and use at least one of the firmware image file or the software image file to perform a recovery operation for the computing device.

22. The computing device according to claim 21, wherein, The computing device includes a fully non-operating computing device having a non-operating boot chain; wherein, in order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: receive the firmware image file, wherein the firmware image file includes a boot chain image file; and wherein, in order to perform the recovery operation, the one or more processors are configured to: repair the boot chain using the boot chain image file.

23. The computing device according to claim 21, wherein, The computing device includes a portion of non-operating computing device capable of loading a valid boot chain for the computing device rather than the operating system (OS) of the computing device; wherein, in order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: receive the software image file, wherein the software image file includes an image file of the OS; and wherein, in order to perform the recovery operation, the one or more processors are configured to: use the software image file to repair the operating system (OS) of the computing device, or use the software image file to re-image the OS of the computing device.

24. The computing device according to claim 21, wherein, In order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: receive at least one of the firmware image file or the software image file from the server via the UE.

25. The computing device according to claim 21, wherein, In order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: establish a connection with a server via a wireless network; and receive at least one of the firmware image file or the software image file from the server via the connection via the wireless network.

26. The computing device according to claim 25, wherein, The server includes a cloud-based server; and wherein, in order to establish the connection with the server, the one or more processors are configured to: obtain an authentication certificate associated with the computing device; and use the authentication certificate to authenticate the computing device with the cloud-based server.

27. The computing device according to claim 25, wherein, The server includes an in-location server; and wherein, in order to establish the connection with the server, the one or more processors are configured to: establish a secure channel between the computing device and the in-location server.

28. The computing device according to claim 27, wherein, In order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: receive at least one of the firmware image file or the software image file through the secure channel.

29. The computing device according to claim 21, wherein, In order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: receive the firmware image file or the software image file from at least one of the UE or the server using at least one of the wired communication interface or the wireless communication interface of the computing device.

30. The computing device according to claim 21, wherein, In order to receive at least one of the firmware image file or the software image file, the one or more processors are configured to: communicate with a wireless communication interface for receiving the firmware image file or the software image file using the boot chain of the computing device.

Images