Patent Description:
The field of the present disclosure relates to integrated roofing accessories, including integrated shingles and other suitable roofing accessories.

With the coming <NUM> network buildout by major carriers, typically, traditional wireless/cellular/over-air deployments will not work at scale. Due to the frequencies required to deliver on network speeds and reduce latency, signal propagation suffers.

Consequently, many carriers around the world are deploying coverage using fifth generation cellular networking (<NUM>) protocols over current <NUM>/LTE networks (herein referred to as "<NUM>(lite)"), such as, e.g., using frequencies below <NUM> ("sub-<NUM>" or "sub-<NUM>"). However, such solutions are not capable of the speeds and latencies of millimeter wave (mmWave) networks using <NUM> protocols (referred to herein as "<NUM>").

On average, <NUM> signals propagate about <NUM> meters in good conditions, but are easily blocked by trees, walls and/or inclement weather. The result is that the mmWave signals of <NUM> have a greatly reduced effective distance. As the frequencies are raised, the distance that an effective <NUM> signal can be sent is reduced and the probability of signal blocking/absorption also increases.

As a result, there is a need for denser <NUM> cell site installations than <NUM>, LTE and <NUM>(lite) deployments. Additionally, the supporting infrastructure (backhaul) to connect the <NUM> cell sites or antennas to the carriers, ultimately to the internet, typically employs fiber optic cabling. Supporting a fiber connection every few hundred meters, as needed for effective <NUM> coverage, is difficult, if not impossible. The time and costs to do so are the current impediment to <NUM> rollout.

Systems, methods and apparatuses of embodiments of the present description enable widespread and cost effective <NUM> signal coverage using dense cell sites by embedding <NUM>-capable infrastructure in roofing accessories that are installable in commercial and/or residential roofing structures.

At least one embodiment of the disclosure is herein described, by way of example only, with reference to the accompanying drawings. With specific reference now to the drawings in detail, the embodiments shown are by way of example and for purposes of illustrative discussion of embodiments of the disclosure. In this regard, the description taken with the drawings makes apparent to those skilled in the art how embodiments of the disclosure may be practiced.

Among those benefits and improvements that have been disclosed, other objects and advantages of this disclosure will become apparent from the following description taken in conjunction with the accompanying figures. Detailed embodiments of the present disclosure are disclosed herein; however, the disclosed embodiments are merely illustrative of the disclosure that may be embodied in various forms. In addition, each of the examples given regarding the various embodiments of the disclosure which are intended to be illustrative, and not restrictive.

Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The phrases "in one embodiment," "in an embodiment," and "in some embodiments" as used herein do not necessarily refer to the same embodiment(s), though it may. Furthermore, the phrases "in another embodiment" and "in some other embodiments" as used herein do not necessarily refer to a different embodiment, although it may. All embodiments of the disclosure are intended to be combinable without departing from the scope of the disclosure.

As used herein, the term "based on" is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of "a," "an," and "the" include plural references.

Some embodiments of the present disclosure relate to methods and systems that include the least one integrated roofing accessory. As defined herein an "integrated roofing accessory" is a roofing accessory with at least one <NUM>-infrastructure-supporting ("SG-enabled") electronic component. In some embodiments, the at least one <NUM>-infrastructure-supporting electronic component is embedded within at least one roofing accessory component. In another embodiments, the at least one <NUM>-infrastructure-supporting electronic component is directly or indirectly attached to at least one roofing accessory component.

Some embodiments of the present disclosure relate to at least one integrated roofing accessory. Some embodiments of the present disclosure include a plurality of integrated roofing accessories. Some embodiments of the present disclosure include at least three integrated roofing accessories. Some embodiments of the present disclosure include at least five integrated roofing accessories. Some embodiments of the present disclosure include at least ten integrated roofing accessories. Some embodiments of the present disclosure include at least fifty integrated roofing accessories. Some embodiments of the present disclosure include at least one hundred integrated roofing accessories. Some embodiments of the present disclosure include at least one-thousand integrated roofing accessories.

In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories.

In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM>,<NUM> integrated roofing accessories.

In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories. In some embodiments, there are <NUM> to <NUM> integrated roofing accessories.

Non- limiting examples of the at least one roofing accessory component of the at least one integrated roofing accessory include: roofing caps, laminate roofing accessories, roofing sheets, ridge caps, ridge vents, roofing frames, roofing shingles and the like, or any combination thereof. Additional non-limiting examples of the at least one portion of the roofing accessory are found in <CIT> and <CIT>.

Non-limiting examples of the at least one electronic component of the at least one integrated roofing accessory include: at least one antenna, at least one solar array, at least one battery, at least one computing device, at least one controller, at least one processor, the like, or any combination thereof. The at least one electronic component may also include one or more processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. In some embodiments, the one or more processors may be implemented as a Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors; x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be dual-core processor(s), dual-core mobile processor(s), and so forth. Additional examples of suitable electronic components can be found in <CIT>.

As used herein, the term "dynamically" means that events and/or actions can be triggered and/or occur without any human intervention. In some embodiments, events and/or actions in accordance with the present description can be in real-time and/or based on a predetermined periodicity of at least one of: nanosecond, several nanoseconds, millisecond, several milliseconds, second, several seconds, minute, several minutes, hourly, several hours, daily, several days, weekly, monthly, etc..

As used herein, the term "real-time" is directed to an event/action that can occur instantaneously or almost instantaneously in time when another event/action has occurred. For example, the "real-time processing," "real-time computation," and "real-time execution" all pertain to the performance of a computation during the actual time that the related physical process (e.g., a user interacting with an application on a mobile device) occurs, in order that results of the computation can be used in guiding the physical process.

<FIG> depicts a non-limiting exemplary embodiment of a <NUM> cell in having an integrated roofing accessory described herein. In the non-limiting exemplary embodiment, integrated roofing accessory <NUM> may be in a form of frame that may include at least one cover <NUM>, and at least one electronics compartment <NUM>, jointly referenced herein as the frame components. In some embodiments, the frame components may also include a front edge portion <NUM>, a right edge portion <NUM>, a left edge portion <NUM> and a back-edge portion (not shown). Together, the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion may form a frame to carry or enclose the cover <NUM> and electronics compartment <NUM>. In some embodiments, the combination of the frame, the cover <NUM> and the electronics compartment <NUM> may form an integrated roofing accessory <NUM> that may be installed on a roof (a single <NUM> cell site) as a unit with or without additional integrated roofing accessories.

In some embodiments, the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion may be separately attachable to each other, to the cover <NUM>, or both. However, in some embodiments, the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion are all fixed to each other, such as by being integrally formed together, fastened together with a suitable fastener (e.g., bolt, screw, rivet, pin, etc.), connected via an adhesive, or by some other method. The frame of the integrated roofing accessory <NUM> may then carry the cover <NUM> and/or electronics compartment <NUM>. In some embodiments, the frame components may be made of any material. In some embodiments, the frame components include at least one of molded or extruded plastic, aluminum, a polymer composite material, the like, or any combination thereof.

In some embodiments, each of the cover <NUM>, electronics compartment <NUM> and any other frame components may be integrally formed, e.g., by, for example, without limitation, molding or cutting the electronics compartment <NUM> into a material, such as, e.g., roofing material (e.g., a polymer or other suitable roofing material). Thus, the electronics of the electronics compartment <NUM> as well as the attachment mechanisms of the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion may be embedded into the material.

In some embodiments, the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion, or a combination thereof may be fixed to the cover <NUM> or removably attached. Moreover, as shown in <FIG>, one or more roofing accessories <NUM> can be joined via one or more frame components (for example, without limitation, by one or more attachment mechanisms on the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion, or a combination thereof). For example, integrated roofing accessories <NUM> may be removable joined among themselves and/or removably joined to other roofing accessories and components, such as shingles, waterproofing membranes, underlayment, tiles, photovoltaic panels, among other suitable roofing accessories and components to cover a roof via, for example, without limitation, suitable mating mechanisms on one or more frame components (e.g., the cover <NUM>) Various additional examples of the frame components that may be utilized to build and/or join the integrated roofing accessories <NUM> among themselves or to other roofing accessories, and their arrangements are disclosed in <CIT>; <CIT>; and <CIT>.

In some embodiments, at least one electronic component <NUM> is housed in the electronics compartment <NUM>, which may be mounted to or recessed in the top surface of roof and mounted to or embedded into an underside of the cover <NUM>. In some embodiments, cover <NUM> may be covered with a protective material chosen from at least one of, a polymer, an epoxy, the like, or combinations thereof. In some embodiments, the frame components may also include at least one additional electronics compartment (not shown), which may include at least one second electronic component and wiring to electrically connect the integrated roofing accessory <NUM> to additional roofing accessories and infrastructure (e.g., power source, photovoltaic panels, additional integrated roofing accessories <NUM>, etc.). For example, one or more the frame components may be formed with a data bus or data bussed to enable electronic communication with mating busses of adjacent and/or attached additional roofing accessories. As such, electronic components <NUM> may interconnect with electronic components in other roofing accessories to create a system of interconnect roofing accessories.

In some embodiments, the cover <NUM> and electronics compartment <NUM> form a modified photovoltaic module of the integrated roofing accessory <NUM>. For example, the modified photovoltaic module may have a photovoltaic panel employed as the cover <NUM>. In some embodiments, the modified photovoltaic module includes a frame constructed from the frame components, and the electronic components <NUM> included within the electronics compartment <NUM>. In some embodiments, electronics compartment <NUM> may be integrated into the photovoltaic panel, when such is utilized as the cover <NUM>, or in one or more of the front edge portion <NUM>, the right edge portion <NUM>, the left edge portion <NUM> or back edge portion of the frame components. In some embodiments, the electronics compartment <NUM> may be an additional compartment enclosed within the integrated roofing accessory <NUM> (e.g., enclosed by one or more framing components (e.g., the cover <NUM>)).

In some embodiments, the modified photovoltaic module may include a photovoltaic panel (as the cover <NUM>), that may be modified to collocate <NUM>-enabled antennae with the photovoltaic panel, e.g., without limitation, by placing one or more antenna elements between photovoltaic cells of the photovoltaic panel, placing one or more antenna elements over or under photovoltaic cells of the photovoltaic panel, integrating antenna elements into the photovoltaic cells of the photovoltaic panel, or by another suitable technique. Accordingly, a <NUM> radio of the electronic components <NUM> may emit a signal via the photovoltaic panels using the collocated antennae.

In some embodiments, the integrated roofing accessory <NUM> may emit <NUM> signals using one or more antennae integrated into the cover <NUM>. For example, a dielectric antenna may be embedded in a polymer sized to cover one or more frame components such as, without limitation, the electronics compartment <NUM>. In some embodiments, the dielectric antenna may be a patch antenna, or other suitable antenna for embedding in the cover <NUM> such that the cover <NUM> may form an antenna module covering the electronic components <NUM> of the integrated roofing accessory <NUM>. As a result, the cover <NUM> may serve as both a roofing accessory to weatherproof a roof of a house, as well as an antenna for a <NUM> network, as described below.

As shown in <FIG>, the integrated roofing accessories <NUM> may be mounted onto a roof <NUM> using any suitable attachment mechanism such as fasteners (e.g., nails, screws, pins) and/or adhesives, or by attachment mechanisms mating to the attachment mechanisms of the frame components (left and right edge portions <NUM>/<NUM>, front edge portion <NUM>, and back edge portion (not shown)), such as the attachment mechanisms disclosed in <CIT>, <CIT>, and <CIT>. In some embodiments, the integrated roofing accessories <NUM> can be coated with asphalt before, during, or after installation. In some embodiments, the integrated roofing accessories <NUM> may be mounted on, under, or within one or more roofing materials. As used herein, the term "roofing material" includes, but is not limited to, shingles, waterproofing membranes, underlayment, tiles and photovoltaic panels.

In some embodiments, the integrated roofing accessories <NUM> on the roof <NUM> may electrically communicate with each other wirelessly or via a wired connection routed through the side portions <NUM>/<NUM> (e.g., via a bus, as described above). Accordingly, in some embodiments, one integrated roofing accessory <NUM> on the roof <NUM> can be connected to a power source, such as, e.g., via wiring <NUM> to a connection in a ridge vent <NUM> or to some other power source connection. However, in some embodiments, each roofing accessory <NUM> may be separately connected to the wiring <NUM> to the ridge vent <NUM>.

In some embodiments, the at least one integrated roofing accessory may include electronics components <NUM> including a communication module that is configured to allow <NUM> signals to be transmitted. In some embodiments, the at least one integrated roofing accessory may include electronics components <NUM> including a communication module that is configured to allow <NUM> signals to be received. In some embodiments, the at least one integrated roofing accessory may include electronics components <NUM> including a communication module that is configured to allow <NUM> signals to be transmitted and received.

In some embodiments, the at least one integrated roofing accessory includes at least one embedded antenna. As used herein, the term "antenna" or "antennae" can refer to a device that is part of a transmitting or receiving system to transmit or receive wireless signals. In some embodiments, the at least one embedded antenna is configured to perform at least one of the following operations: receiving electromagnetic waves (e.g., <NUM> signals), transmitting electromagnetic waves (e.g., <NUM> signals), or any combination thereof.

In some embodiments, the at least one integrated roofing accessory is configured to support at least one signal propagation strategy. The at least one signal propagation strategy includes, but is not limited to, at least one of: many inputs-many outputs (MIMO), beam forming mesh, the like, or any combination thereof.

In some embodiments, the at least one embedded antenna is at least one dielectric antenna. In some embodiments, the at least one dielectric antenna takes the form of at least one dielectric antenna array. In some embodiments, the at least one dielectric antenna array includes a plurality of dielectric antennas configured to wirelessly receive a controllable beam in response to electromagnetic waves. In some embodiments, the at least one dielectric antenna array includes a plurality of dielectric antennas configured to wirelessly transmit a controllable beam in response to the electromagnetic waves. In some embodiments, the at least one dielectric antenna array includes a plurality of dielectric antennas configured to wirelessly transmit and receive a controllable beam in response to the electromagnetic waves.

In some embodiments, the dielectric antenna is embedded within the cover <NUM> or is covered by the cover <NUM> within the at least one recessed electronics compartment <NUM>. Accordingly, the cover <NUM> may be constructed from a material that has a minimal effect on the <NUM> signals emitted by the dielectric antenna, such as a material that is transparent to mmWave signals, thus causing sufficiently low attenuation to the mmWave signals for a stable data transmission or reception. For example, the cover <NUM> may include a polymer, including engineered polymers, such as the D30™ Gear4™ and <NUM> Signal Plus material having microvoids for reducing mmWave attenuation, as disclosed by "<NPL>). In some embodiments, the dielectric antenna is mounted on an exterior surface of the at least one frame <NUM>, e.g., on an exterior of the cover <NUM> relative to the at least one recessed electronics compartment <NUM>.

In some embodiments, the at least one integrated roofing accessory may include at least one of an embedded photovoltaic array (e.g., an array of photovoltaic panels), an embedded battery, or any combination thereof. In some embodiments, at least one of the embedded photovoltaic array, the embedded battery, or any combination thereof can dynamically supply power to roofing accessories and solutions.

In some embodiments, the embedded battery is configured to be charged by either the embedded photovoltaic array or an external power source. In some embodiments, the embedded battery is configured to deliver direct current (DC) power to devices or systems on or around a roof. In some embodiments, the embedded battery is configured to deliver alternating current (AC) power to devices or systems on or around a roof.

In some embodiments, the at least one integrated roofing accessory includes at least one of: at least one computing device, at least one storage component, or at least one memory component. In some embodiments, the at least one integrated roofing accessory is configured to dynamically carry out prescribed functions. In some embodiments, the at least one integrated roofing accessory is configured to be controlled remotely by a network operator or administrator (e.g., a <NUM> network), such as in a software defined network <NUM> as described below with reference to <FIG>. In some embodiments, the at least one integrated roofing accessory is configured to be controlled remotely by a wired connection. In some embodiments, the at least one integrated roofing accessory includes a base configuration. In some embodiments, the at least one integrated roofing accessory can be expanded from the base configuration.

Non-limiting examples of the at least one computing device include at least one personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and the like. Additional non-limiting examples of the at least one computing device include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. In some embodiments, the one or more processors may be implemented as a Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors; x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be dual-core processor(s), dual-core mobile processor(s), and so forth.

Non-limiting examples of the at least one storage component or the least one memory component include: read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), or any combination thereof.

In some embodiments, a plurality of integrated roofing accessories described herein can be installed on a plurality of roofs, so as to create an integrated roofing accessory network (<NUM> network). In some embodiments, a plurality of integrated roofing accessories described herein can be installed on a single roof so as to create the integrated roofing accessory network.

In some embodiments, a method of using an integrated roofing accessory network described herein includes: providing a plurality of integrated roofing accessories as described herein; transmitting at least one electromagnetic signal (e.g., a <NUM> signal) from a first integrated roofing accessory; and receiving the at least one electromagnetic signal by a second integrated roofing accessory. In some embodiments, the second integrated roofing accessory further transmits the at least one electromagnetic signal to a third integrated roofing accessory, and so on. In some embodiments, the first integrated roofing accessory is located on a first building, the second integrated roofing accessory is located on a second building, the third integrated roofing accessory is located on a third building, and so on.

<FIG> depicts a networking model incorporating a <NUM>-enabled integrated roofing accessory <NUM> according to aspects of embodiments of the present description.

In some embodiments, the integrated roofing accessory network may be configured to utilize Open Systems Interconnection (OSI) model, utilizing a flamework of standards for communication between different systems manufactured by different vendors, to communicate between integrating roofing accessories and other devices and/or systems (e.g., wireless carrier network, home network, etc.). The OSI model creates an open systems networking environment where any vendor's computer system, connected to any network, freely shares data with any other computer system on that network, or on a linked network.

Typically, the OSI model organizes the communication process into seven different layers of interrelated protocols in a layered sequence. Layers <NUM> through <NUM> define network access protocols and layers <NUM> through <NUM> deal with end-to-end communication protocols between a message source and a message destination. Each layer includes at least one function that is within an upper and a lower logical boundary. The services of each layer are combined with the services of lower layers to create new services that are made available to the higher layers. The layers include:.

In some embodiments, the set-up of the exemplary integrated roofing accessory network in accordance with present disclosure may include software modules or combination software and hardware modules forming software-defined radio (SDR) <NUM> that include software that executes and assembles OSI layers <NUM>-<NUM> and transmission hardware (e.g., antennae <NUM> and transceivers <NUM>) that execute OSI layers <NUM>-<NUM>, or combinations of software and hardware.

In some embodiments, the integrated roofing accessories <NUM> may include hardware-based radio modules for interfacing with a <NUM> network. The radio modules may include circuitry for each of, e.g., amplifying, filtering, mixing, attenuating, etc.. However, in some embodiments, the integrated roofing accessories employ SDR <NUM> modules. An SDR <NUM> module can be formed from hardware including a general-purpose processing device with software-based virtual signal processing components for amplifying, filtering, mixing, attenuating, etc. to produce the SDR <NUM> through virtual means.

In some embodiments, a basic SDR <NUM> module may include a processing device (e.g., central processing unit (CPU) or graphical processing unit (GPU)) equipped with an analog-to-digital converter, preceded by some form of RF front end. In some embodiments, the RF front end includes antennae <NUM> (e.g., one or more dielectric antennae or other suitable antenna types) and a transceiver <NUM>. Significant amounts of signal processing are handed over to the general-purpose processor, rather than being done in special-purpose hardware (electronic circuits). Such a design produces a radio which can receive and transmit widely different radio protocols based solely on the software used.

In some embodiments, layer <NUM> of a software defined network <NUM> according to the OSI model layers can include the physical components of the integrated roofing accessories <NUM> and respective SDR <NUM> modules. In some embodiments, such physical components may include, e.g., one or more antennae <NUM>. Each integrated roofing accessory <NUM> on each building may include physical antennae <NUM>-<NUM> to form a network of integrated roofing accessories <NUM> installed as roofing accessories throughout an area.

As described above, to improve signal density and signal number, as well as maximize the number of concurrent connections, the antennae <NUM> may include antenna elements positioned on a roof of a structure, such as house or building. In some embodiments, the antenna elements may be configured for <NUM> signaling. In some embodiments, the antennae <NUM> may include further elements for <NUM> signaling, or the <NUM> elements may be compatible with the frequencies for <NUM>.

In particular, in some embodiments, the integrated roofing accessories <NUM> may employ layer <NUM>, or physical, components including antennae <NUM> to provide an uplink and downlink signal transmission method for random access, channel measurement, and terminal feedback in a cellular network using fifth generation (<NUM>) frequency bands including unlicensed, licensed shared and extremely high frequency (EHF) bands, as well as any other <NUM> functionalities over <NUM> and mmWave frequency bands.

In some embodiments, the <NUM> communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., <NUM> bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog or digital beam forming, or other signal propagation enhancements, and combinations thereof. Accordingly, the integrated roofing accessories <NUM> may include antennae <NUM> that incorporate such MIMO, FD-MIMO, array, beamforming and other technologies for improved mmWave signal propagation.

In some embodiments, such integrated roofing accessories <NUM> employ a physicalantennae <NUM> to facilitate development of advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like. In a <NUM> system, such as one formed by a network of the integrated roofing accessories <NUM> (and, optionally, additional <NUM>-enabled devices and systems), Orthogonal Frequency Division Multiplexing (OFDM), hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) may be employed individually or in combination as advanced coding modulation (ACM). In some embodiments, filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology may be incorporated instead or in addition.

Typically, in <NUM> communication, use of new frequency bands may be employed to obtain wider bandwidths for data rates of at least <NUM> Gbps. The mmWave frequency band in particular is a candidate for wide bandwidth transmissions. The mmWave frequency band is the <NUM> to <NUM> band of the electromagnetic spectrum (<NUM> to <NUM> wavelength). Accordingly, the antennae <NUM> may be configured for to emit and receive signals in the mmWave frequency band. Spectrum in traditional cellular bands, below <NUM> (e.g., "<NUM>(lite)"), is finite. As cellular data traffic continues to grow, new frequency bands may need to be considered for use. Unlike traditional cellular bands, mmWave bands may allow large blocks of contiguous spectrum to be allocated, allowing for bandwidths on the order of GHz or more. Moreover, the mmWave frequency bands may allow multi-element antenna arrays to be used.

Accordingly, in some embodiments, the antennae <NUM> may include multi-element antenna arrays, which may comprise very small elements, with sizes on the scale of integrated-circuit (IC) chip elements. Use of these multi-element antenna arrays may provide large antenna gain and sufficient power output through over-the-air power combining. This combination of large bandwidths and device architectures may allow mmWave antennae <NUM> to provide peak rates on the order of <NUM> Gbps and to provide ample capacity to meet the future demands.

However, in mmWave communication, power loss is large owing to attenuation of radio waves, limiting the transmission distance. Thus, in some embodiments, beamforming may be employed to overcome the limitation of short transmission distance. With beamforming, transmission power can be concentrated in a specific direction according to the configuration of a transmitting antennae <NUM>. When receiving, the antennae <NUM> may also enhance performance in a specific direction with beamforming. Beamforming (or spatial filtering) is a signal processing technique used in sensor arrays for directional signal transmission or reception. This is achieved by combining elements in an antenna array in such a way that signals at particular angles experience constructive interference while others experience destructive interference. Beamforming can be used at both the transmitting and receiving ends in order to achieve spatial selectivity.

In some embodiments, the antenna elements of the antennae <NUM> may be controllable for MIMO signaling. In radio, multiple-input and multiple-output, or MIMO, is a method for multiplying the capacity of a radio link using multiple transmission and receiving antennas to exploit multipath propagation. The MIMO is a space-time signal processing where a natural dimensional of transmitting data is complemented with a spatial dimension inherent in the use of multiple spatially distributed antennas. MIMO is able to turn multipath propagations into a benefit because signals on the transmit antennas at one end and the receiver antennas at the other end are integrated such that a quality of bit error rate (BER) or a data rate of the communication for each wireless user or a transmitting distance is improved, thereby increasing a communication network's quality of service.

A MIMO channel contains many individual radio links, hence it has Nt×Nr SISO (Single-Input Single-Output) channels (also called sub-channels), where Nt refers to a number of transmit channels, and Nr refers to a number of receive channels. For example, a <NUM>×<NUM> MIMO arrangement contains <NUM> links and hence <NUM> SISO channels. The SISO channels can be combined in various ways to transmit one or more data streams to the receiver. Thus, the antenna elements may be separate, individually controllable antennae <NUM>, or sub-elements of a single antennae <NUM>, or a combination thereof, that together may communicate data. In some embodiments, the antennae <NUM> may include MIMO signaling capabilities include, e.g., 2x2, 4x4, 6x6, 8x8 or more SISO channels. For example, the antennae <NUM> may include, e.g., phased array antennae for MIMO and microwave signal generation, including, loop and/or patch antenna elements integrated into a printed circuit board (PCB) and embedded in the integrated roofing accessory <NUM>. For example, a wideband polarized patch antenna and in an antenna array that can cover mmWave frequency bands <NUM> applications may be employed, and may be single or dual-polarized. One embodiment the antenna package may a high-density interconnected (HDI) FR-<NUM> printed circuit board (PCB) substrate, or other suitable wideband mmWave antenna array having a size to fit within the integrated roofing accessory <NUM> described above.

Long-Term Evolution (LTE), or <NUM>, is a standard developed by the 3GPP (3rd Generation Partnership Project) for wireless broadband communication for mobile devices and data terminals, based on the Global System for Mobile Communications (GSM)/ Enhanced Data Rates for Global Evolution (EDGE) and Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA) technologies. It increases the capacity and speed using a different radio interface together with core network improvements over prior (<NUM>) standards. However, Worldwide Interoperability for Microwave Access (WiMAX), Evolved HSPA (HSPA+), and LTE may be included as <NUM> technologies. Accordingly, the antennae <NUM> may additionally include GSM, EDGE, UMTS and HSPA frequencies in addition to mmWave frequencies as described above. For example, such <NUM> frequencies may have better range and penetration for reduced signal blockage and dissipation, thus improving long range stability. Accordingly, the <NUM> antenna element so the antennae <NUM> may be used for, e.g., backhaul communication or other long-range uses.

In some embodiments, the antennae <NUM> may be positioned in a location to provide the best line-of-sight to both other antennae <NUM> through <NUM> as well as <NUM>-enabled computing devices. Both height and orientation may play in a role in providing line-of-sight to other devices, with a high location facilitating raising the antennae <NUM> above potential obstructions. Accordingly, as described above, installation as a roofing accessory on residential or commercial roof may provide positioning for facilitating mesh networking with additional antennae <NUM> through <NUM> as well as <NUM> signaling for data transmission to and from computing devices.

Moreover, mmWave antennae <NUM> may require power to operate, and sometime significant amount of power. Indeed, greater power supply may improve signal propagation, or distance with which a signal may maintain throughput and stability. Installation as a roofing accessory facilitates providing roof-mounted photovoltaic panels or mains power, e.g., via a ridge vent or other similar access structure.

In some embodiments, level two components in a module of the SDR <NUM> and software defined network <NUM> can include data link components such as, e.g., a receiver, transmitter, transceiver <NUM> or combination thereof. In some embodiments, the transceiver <NUM> may be included in the electronic devices of the integrated roofing accessory <NUM> to control the antennae <NUM> for frequency control and modulation of emitted signals. Such a transceiver <NUM> may be selected or configured to balance complexity of signals and density or number of concurrent connections or channels with computational complexity, heat and size. In some embodiments, these factors may be balanced to achieve an optimal balance that maximizes signal complexity and number of concurrent connections while maintaining a size and heat output that is sustainable within an integrated roofing accessory <NUM>.

Similarly, cost and circuit complexity/heat output may be balanced against power supply and amplitude of the antennae <NUM>. As more power is supplied, the transceiver <NUM> may generate more heat and consume more energy, but signal propagation may be extended. Additionally, a higher quality, more sensitive and complex transceiver <NUM> may improve signal-to-noise ratios for better signal stability and data transmission.

In some embodiments, the transceiver <NUM> plays an active role in the SDR <NUM> by effectuating at least four sub-layers to the OSI Model layer <NUM>, including, e.g., Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control, Medium Access Control, among others.

The medium access control (MAC) sublayer is the layer that controls the hardware responsible for interaction with the wired, optical or wireless transmission medium. The MAC sublayer and the logical link control (LLC) sublayer together make up the data link layer. Within the data link layer, the LLC provides flow control and multiplexing for the logical link (i.e. EtherType, <NUM>. 1Q VLAN tag etc), while the MAC provides flow control and multiplexing for the transmission medium.

RLC is located on top of the 3GPP MAC-layer and below the PDCP-layer. The main tasks of the RLC protocol are: Transfer of upper layer Protocol Data Units (PDUs) in one of three modes: Acknowledged Mode (AM), Unacknowledged Mode (UM) and Transparent Mode (TM); Error correction through ARQ (only for AM data transfer); Concatenation, segmentation and reassembly of RLC SDUs (UM and AM); Re-segmentation of RLC data PDUs (AM); Reordering of RLC data PDUs (UM and AM); Duplicate detection (UM and AM); RLC SDU discard (UM and AM); and RLC re-establishment.

Protocol error detection and recovery Packet Data Convergence Protocol (PDCP) is specified by 3GPP in TS <NUM> for UMTS, TS <NUM> for LTE and TS <NUM> for <NUM> New Radio (NR). PDCP is located in the Radio Protocol Stack in the UMTS/LTE/<NUM> Air interface on top of the RLC layer.

A SDAP sub-layer is above the PDCP sublayer in SGNR. PDCP is the first sublayer in the 3GPP protocol stack that receives/transmits network layer traffic (TCP/IP traffic). Data Radio Bearer (DRB) is the logical connection used inside the <NUM> protocol stack to carry data PDUs. SDAP functionality is to map quality-of-service (QoS) flow to and from DRB at the PDCP sublayer in both downlink and uplink direction. The main services and functions of SDAP include the following: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL PDUs; and mapping the flow to one of the uplink DRB. Similarly, when a downlink PDU is received at the PDCP and it contains SDAP header which is removed, and the PDU is passed to upper layer.

Accordingly, in some embodiments, the transceiver <NUM> controls the antennae <NUM> for efficient transmission via, e.g., beamforming and MIMO functionality as described above. A beamforming protocol, such as that defined as part of the proposed IEEE <NUM> ad/WiGig standard, may be used to find a path between a cooperating pair of transmitter and receiver antennas. Beamforming techniques in mmWave systems are complex and require significant computing overhead to accomplish.

In some embodiments, the transceiver <NUM> may, therefore, include a selection from transceivers and/or modems integrated or embedded in integrated circuit or system-on-chip design. For example, a <NUM> modem, such as the Qualcomm Snapdragon™ X50, X52 and/or X55 modems, Analog Devices Inc. AD9375, or other suitable modem and transceiver solutions suitable to be integrated into an integrated roofing accessory <NUM> for a SDR <NUM>.

In some embodiments, the antennae <NUM> and <NUM> may be packaged in, e.g., an embedded solution, such as a system-on-chip architecture, however other integrate circuit packaging methodologies may be employed to package the antennae <NUM> and transceiver <NUM> under the cover <NUM> in an electronics compartment <NUM> as the first electronic device and/or the at least one second electronic device <NUM>. In some embodiments, the antennae <NUM> are separate from the transceiver <NUM> and in electronic communication with each via, e.g., copper wiring, or other wiring solution, or via a standardized data interface such as, e.g., PCIe, SATA, NVME, USB, ethernet, Registered Jack (e.g., RJ11), or other data communication interface, such as the wiring <NUM>.

In some embodiments, as a separate electronic device or integrated into the system-on-chip of the transceiver <NUM>, the SDR <NUM> may optionally include a virtual firewall (vFirewall) <NUM>. In some embodiments, the vFirewall <NUM> may regulate data communication between the transceiver <NUM> and the software defined network <NUM> to prevent untrusted or unauthorized data, files, programs, scripts and other information from harming the software defined network <NUM> and software and hardware components therein.

In some embodiments, the vFirewall <NUM> may include a network firewall service or appliance running entirely within a virtualized environment and which provides the usual packet filtering and monitoring provided via a physical network firewall. The vFirewall <NUM> can be realized as a traditional software firewall on a guest virtual machine already running, a purpose-built virtual security appliance designed with virtual network security in mind, a virtual switch with additional security capabilities, or a managed kernel process running within the host hypervisor.

In some embodiments, the vFirewall <NUM> may operate in different modes to provide security services, depending on the point of deployment. For example, the vFirewall <NUM> may operate in either bridge-mode or hypervisor-mode. Both may come shrink wrapped as a virtual security appliance and may install a virtual machine for management purposes.

A virtual firewall operating in bridge-mode acts like its physical-world firewall analog; it sits in a strategic part of the network infrastructure - usually at an inter-network virtual switch or bridge - and intercepts network traffic destined for other network segments and needing to travel over the bridge. By examining the source origin, the destination, the type of packet it is and even the payload the VF can decide if the packet is to be allowed passage, dropped, rejected, or forwarded or mirrored to some other device. Initial entrants into the virtual firewall field were largely bridge-mode, and many offers retain this feature.

By contrast, a virtual firewall operating in hypervisor-mode is not actually part of the virtual network at all, and as such has no physical-world device analog. A hypervisor-mode virtual firewall resides in the virtual machine monitor or hypervisor where it is well positioned to capture VM activity including packet injections. The entire monitored VM and all its virtual hardware, software, services, memory and storage can be examined, as can changes in these. Further, since a hypervisor-based virtual firewall is not part of the network proper and is not a virtual machine its functionality cannot be monitored in turn or altered by users and software limited to running under a VM or having access only to the virtualized network.

In some embodiments, because the vFirewall <NUM> is positioned in the SDR <NUM> at the intersection between the software defined network <NUM> and other antennae <NUM> through <NUM> of a <NUM> mesh network, the vFirewall <NUM> may be configured to operate in bridge mode.

In some embodiments, as a SDR <NUM>, the transceiver <NUM> and vFirewall <NUM> may be implemented as software components within a general-purpose processing device, such as, e.g., a central processing unit (CPU) (e.g., an x86, x64, ARM, RISC-V, PowerPC, MIPS, SPARC, or other complex instruction set computer (CISC) or reduced instruction set computer (RISC) processors), graphical processing unit (GPU), neural processing unit (NPU), field programmable gate array (FPGA), microprocessor, or other processing device or combinations thereof. In some embodiments, different functions of the transceiver <NUM> and vFirewall <NUM> may be configured to be implemented with separate processing components of processor package including multiple processing devices, processing or compute cores, or combinations thereof. For example, the processor package may include, e.g., one or more CPU cores, one or more GPU cores, one or more NPU cores, a digital-to-analog (DAC) converter, an analog-to-digital converter (ADC), a <NUM> model including radio-frequency receiver, transmitter and/or transceiver, cache, on chip storage, random access memory (RAM), as well as data interfaces to interface with one or more additional processor devices, components or packages as well as to interface with the antennae <NUM> via the transceiver <NUM>.

In some embodiments, the processing components of the SDR <NUM> may additionally be configured to integrate the SDR <NUM> into one or more networks, including the software defined network <NUM> and a <NUM> mesh network incorporating additional antennae <NUM> through <NUM> from additional integrated roofing accessories <NUM> and additional <NUM>-enabled computing devices, as well as any other suitable network. Accordingly, the SDR <NUM> may cooperate with, e.g., the software defined network <NUM> to implement networking and communication protocol layers of the OSI Model. For example, such layers may include layer <NUM> for networking, layer <NUM> for transport and layer <NUM> for session control and configuration. Such layers facilitated the SDR <NUM> to communicate with other antennae <NUM> through <NUM> even where the other antennae <NUM> through <NUM> are manufactured and programmed by different entities or using different software and firmware.

In some embodiments, the software defined network <NUM> implements layers <NUM> through <NUM> to establish a platform or standard network to integrate the SDR <NUM> into compute and communication resources. In some embodiments, the software defined network <NUM> implements the layers <NUM> through <NUM> to operate as a control layer for all communication between sub-systems or electronics modules of the software defined network <NUM> (including, e.g., the SDR <NUM> module), multi-access edge computing <NUM>, distributed data components <NUM>, consumer access radio <NUM> (e.g., WiFi, Bluetooth, Zigbee, Z-Wave, <NUM>/LTE, <NUM>(lite), <NUM>, etc.), among other sub-systems and electronics modules of the integrated roofing accessory <NUM> and devices in communication therewith.

In some embodiments, the software defined network <NUM> may integrate the sub-systems and electronics modules into a single system by defining the data traffic within the software defined network <NUM>, e.g., using software-defined common resource management (SD-CRM). The SD-CRM can be used for networking functions and application/service functions. Thus, the SD-CRM can manage transport functions for layers zero through four as well as application functions for layers four and higher. The SD-CRM can provide a platform for network services, network control of service instantiation and management, as well as a programmable environment for resource and traffic management. The SD-CRM also can provide a consolidated network management interface to permit the combination of real time data from the service and network elements with real-time or near real-time control of the forwarding plane. Thus, embodiments of the concepts and technologies described herein can enable near real-time configuration and real-time flow setup, programmability through service and network script-like logic, extensibility for competitive differentiation, standard interfaces, and multi-vendor support, among other features. Interactions between these layers can be based upon policies to determine optimum configuration and rapid adaptation of the network to changing state and changing customer requirements for example, spikes in traffic, network outages (e.g., due to snow storms, blackouts, natural disasters, or the like), adding new services (e.g., VoIP/web RTC, authentication, etc.), maintenance, combinations thereof, or the like.

Accordingly, in some embodiments, the SD-CRM may define what communication will run over each SDR <NUM> module on the software defined network <NUM> (e.g., the SDR <NUM>, the customer access radio <NUM>, among others). In some embodiments, the software defined network <NUM> may extend to additional integrated roofing accessories <NUM> to incorporate the SDRs therein into a common software defined network <NUM>. As a result, the SD-CRM may control traffic between the various SDRs <NUM> of the various integrated roofing accessories <NUM> to form a distributed computing environment for control of multiple SDR <NUM> modules to cooperate within a cohesive <NUM> network. Thus, multiple integrated roofing accessories <NUM> may be combined to create a larger antenna structure, facilitating modular functionality. In some embodiments, once a <NUM> network is created, the SD-CRM defines the traffic that traverses it.

In some embodiments, the SD-CRM of the software defined network <NUM> may be implemented with, e.g., a network switch <NUM> as shown in <FIG>. In some embodiments, the network switch <NUM> may be configured to manage a software defined network <NUM> according to a network protocol, such as, e.g., the OpenFlow protocol, Accordingly, the network switch <NUM> may be a software defined (e.g., logical) switch protocol defined by one or more controllers <NUM>. In some embodiments, however, the switch <NUM> may be a hardware switch or embodied in a specialized hardware device, such as, e.g., a single or multiport Ethernet switch (e.g., a Zodiac FX™ or other similar Ethernet switch), or other network switch device or devices.

In some embodiments, the network switch <NUM> may include one or more flow tables <NUM> and group tables <NUM>, which perform packet lookups and forwarding, and one or more channels <NUM> to the external controller or controllers <NUM>. The switch <NUM> communicates with the controllers <NUM> and the controllers <NUM> manage the switch <NUM> via the switch protocol by, e.g., adding, updating and deleting flow entries in flow tables <NUM>.

In some embodiments, the switch <NUM> includes multiple flow tables <NUM>. Thus, upon receiving packets of network traffic via one or more of the ports <NUM>, the packets are compared in to entries in each flow table <NUM> starting with the first flow table and may continue to additional flow tables of the pipeline. The packet may first start in a table <NUM> and check those entries based on priority. Highest priority will match first (e.g. <NUM>, then <NUM>, then <NUM>). If the flow needs to continue to another table, the packet may be advanced to the table specified in the instructions until a match is found, and the corresponding instructions are executed.

In some embodiments, the ports <NUM> may include physical and/or logical ports. Examples of hardware ports may include, e.g., ethernet interfaces, while logical ports may include, e.g., LGs, tunnels, loopbacks and other logical interfaces.

Referring again to <FIG>, the software defined network <NUM> may include the incorporation of data storage and compute resources. For example, a multi-access edge computing (MEC) <NUM> system may be employed in each integrated roofing accessory <NUM> or in communication with each integrated roofing accessory <NUM> as part of the software defined network <NUM>. In some embodiments, the MEC <NUM> may include a CPU <NUM>, a memory <NUM>, a non-transitory storage device <NUM> among other processing devices and components (e.g., GPUs, NPUs, codecs, DAC, ADC, etc.). In some embodiments, the MEC <NUM> is integrated onto the same board or PCB as the SDR <NUM> module such that, e.g., compute, memory and/or storage resources are shared. However, in some embodiments, the MEC <NUM> may be a separate set of processing resources relative to the SDR <NUM> module.

In some embodiments, the MEC <NUM> may control the software defined network <NUM>, including, e.g., implementing layers <NUM> through <NUM>, and/or layers <NUM> and <NUM> for data presentation and application functionality, respectively. For example, the MEC <NUM> may provide a user application functionality to administer network protocols, security policies, flow tables, group tables, among other software administration functionalities pertaining to the implementation of layers <NUM> through <NUM> described above. Accordingly, the MEC <NUM> is effectively the control module for the software defined network <NUM> implemented by one or more integrated roofing accessories <NUM> with user definable policies via, e.g., suitable user interfaces. Such user interfaces may provide the user with administrative functionality to control the software defined network <NUM> and components therein, as well as to collect and locally store data and service metrics relative to the operation of the components and the software defined network <NUM>. Thus, the MEC <NUM> may include a suitable processing package including the CPU <NUM>, memory <NUM> and non-transitory storage device <NUM> for generating and providing to a user the user interface in a network management console. Such processing package may include, e.g., PCB mounted CPU <NUM>, memory <NUM> and non-transitory storage device <NUM> and/or a system-on-chip, and/or other suitable processing package. For example, the MEC <NUM> may include, e.g., a Raspberry Pi, Arduino, Nvidia TX2, or other configurable processing package.

In some embodiments, multiple integrated roofing accessories <NUM> with respective antennae <NUM> through <NUM> may be networked together using <NUM> signals to create a broader software defined network <NUM>. Such a broader network may be leveraged to implement a distributed datacenter <NUM> across the integrated roofing accessories <NUM> on the network. Accordingly, the software defined network <NUM> may be configured to share storage <NUM> and compute <NUM> resources for distributed processing and storage of user data, e.g., received via the customer access radio <NUM> and shared across integrated roofing accessories <NUM> via antennae <NUM> through <NUM>. Such a distributed datacenter <NUM> may be employed for, e.g., cloud storage, media and data streaming, content distribution (e.g., as a content distribution network (CDN)), among other distributed applications.

In some embodiments, a user may interface directly with the software defined network <NUM> via a <NUM> connection using a <NUM>-enabled computing device, or via the customer access radio <NUM> via a customer access radio enabled device. In some embodiments, the customer access radio <NUM> includes, e.g., a WiFi radio <NUM>. The customer access radio enabled device may include any computing device having hardware and/or software for communicating with the WiFi radio <NUM>. Accordingly, the integrated roofing accessory <NUM> using the software defined network <NUM> may include both <NUM> connectivity as well as WiFi connectivity or other customer access wireless protocol connectivity, for example, for in-home WiFi using the same integrated roofing accessory <NUM> that provides <NUM> carrier or internet-service-provider (ISP) connectivity. In some embodiments, similar to the SDR <NUM>, the customer access radio <NUM> may include a vFirewall <NUM> to enhanced security of the software defined network <NUM>.

In some embodiments, the storage <NUM> may be implemented with suitable storage components such as, e.g., a series for solid state drives (SSD) or M. <NUM> storage drives. <NUM> drives are a newer, smaller, and faster variant of an SSD. The storage <NUM> subsystem may be configured in a Redundant Array of Independent Drives (RAID) variant (<NUM> or <NUM>) or as a Hadoop Distributed Files System (HDFS). Either system provides a level of data security and fault tolerance. HDFS has an advantage with error checking and the ability to assign multiple namenodes. Namenodes are simply indexes to where the data resides. Data Nodes can be configured to store multiple copies of the data across several drives. Namenodes manage data on the data nodes by sector - more granular and removes the need to remove an entire drive from the system like a RAID array. Depending on the RAID level it allows for one or two drive failures and still have the system function normally. However, an additional drive failure would cause catastrophic data loss. So, to prevent data loss, drives will need to be continually replaced.

In comparison, HDFS allows for sector level management per drive. Using HDFS, multiple drives failures does not cause catastrophic failure/data loss. HDFS storage management concern may be on the overall capacity of the system and namenode versus physical drive failure. Therefore, an HDFS managed storage solution may reduce the time and effort required to support an integrated roofing accessory <NUM> platform.

In some embodiments, complimentary to datacenter <NUM> storage <NUM> is compute <NUM>. Compute <NUM> allows applications and services to be written and operate within a distributed space. Like a typical datacenter or cloud infrastructure, compute <NUM> may enable services to be deployed across a distributed network. Unlike primary cloud networks, the distributed datacenter <NUM> of the integrated roofing accessories <NUM> may not have defined services or applications. Rather, the distributed datacenter <NUM> may employ compute <NUM> to have a hypervisor-like service to manage and deploy infrastructure for the user. In some embodiments, each integrated roofing accessory <NUM> may be a network of dense single board computers (SBC) with multiple cores or embedded servers. Advantageously, such compute <NUM> solutions may be resilient to extreme environmental conditions, such as, e.g., high temperatures, low temperatures, moisture and humidity, vibrations, shock, among other environmental conditions. An example of a possible SBC or embedded server may include, e.g., a Grizzly VL-ESU-<NUM>, or other suitable device.

In some embodiments, to support data science workloads, pipelines and models Graphical Processing Units (GPU) may be deployed within the integrated roofing accessory <NUM> in the software defined network <NUM> in much the same manner as the CPU. An example SBC that supports high density GPU may include, e.g., Nvidia Jetson Nano or other suitable device.

In some embodiments, the software defined network <NUM> within and across integrated roofing accessories <NUM> may be included with a power source. In some embodiments, low-power devices may be employed, such as, e.g., systems-on-chip similar to those used in smartphones and other mobile devices. Accordingly, power may be provided via, e.g., on-board batteries, photovoltaic panel mounted to the same roof as the integrated roofing accessory <NUM> or as a cover <NUM> on the integrated roofing accessory <NUM>. However, in some embodiments, to achieve greater range and stability of the <NUM> signal, high power components for a more powerful SDR <NUM> may be employed. Accordingly, in some embodiments, the integrated roofing accessories <NUM> may be connected directly to mains power via, e.g., an AC to DC (AC/DC) converter, or to a larger scale solar array installed on the roof or nearby, or both.

In some embodiments, various components and devices, including <NUM>-enabled computing devices and <NUM>-enabled integrated roofing accessories <NUM> may include or be incorporated, partially or entirely into at least one personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile device, messaging device, data communication device, and so forth.

As used herein, the term "mobile device," or the like, may refer to any portable electronic device that may or may not be enabled with location tracking functionality (e.g., MAC address, Internet Protocol (IP) address, or the like). For example, a mobile electronic device can include, but is not limited to, a mobile phone, Personal Digital Assistant (PDA), Blackberry ™, Pager, Smartphone, smart watch, or any other reasonable mobile electronic device.

In some embodiments, the one or more processors may be implemented as a Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors; x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be dual-core processor(s), dual-core mobile processor(s), and so forth.

In some embodiments, the processing device may include any type of data processing capacity, such as a hardware logic circuit, for example an application specific integrated circuit (ASIC) and a programmable logic, or such as a computing device, for example, a microcomputer or microcontroller that include a programmable microprocessor. In some embodiments, the processing device may include data-processing capacity provided by the microprocessor. In some embodiments, the microprocessor may include memory, processing, interface resources, controllers, and counters. In some embodiments, the microprocessor may also include one or more programs stored in memory.

In some embodiments, as detailed herein, one or more of exemplary inventive computer-based systems/platforms, exemplary inventive computer-based devices, and/or exemplary inventive computer-based components of the present disclosure may obtain, manipulate, transfer, store, transform, generate, and/or output any digital object and/or data unit (e.g., from inside and/or outside of a particular application) that can be in any suitable form such as, without limitation, a file, a contact, a task, an email, a tweet, a map, an entire application (e.g., a calculator), etc. In some embodiments, as detailed herein, one or more of exemplary inventive computer-based systems/platforms, exemplary inventive computer-based devices, and/or exemplary inventive computer-based components of the present disclosure may be implemented across one or more of various computer platforms such as, but not limited to: (<NUM>) AmigaOS, AmigaOS <NUM>; (<NUM>) FreeBSD, NetBSD, OpenBSD; (<NUM>) Linux; (<NUM>) Microsoft Windows; (<NUM>) OpenVMS; (<NUM>) OS X (Mac OS); (<NUM>) OS/<NUM>; (<NUM>) Solaris; (<NUM>) Tru64 UNIX; (<NUM>) VM; (<NUM>) Android; (<NUM>) Bada; (<NUM>) BlackBerry OS; (<NUM>) Firefox OS; (<NUM>) Ios; (<NUM>) Embedded Linux; (<NUM>) Palm OS; (<NUM>) Symbian; (<NUM>) Tizen; (<NUM>) WebOS; (<NUM>) Windows Mobile; (<NUM>) Windows Phone; (<NUM>) Adobe AIR; (<NUM>) Adobe Flash; (<NUM>) Adobe Shockwave; (<NUM>) Binary Runtime Environment for Wireless (BREW); (<NUM>) Cocoa (API); (<NUM>) Cocoa Touch; (<NUM>) Java Platforms; (<NUM>) JavaFX; (<NUM>) JavaFX Mobile; (<NUM>) Microsoft XNA; (<NUM>) Mono; (<NUM>) Mozilla Prism, XUL and XULRunner; (<NUM>). NET Framework; (<NUM>) Silverlight; (<NUM>) Open Web Platform; (<NUM>) Oracle Database; (<NUM>) Qt; (<NUM>) SAP NetWeaver; (<NUM>) Smartface; (<NUM>) Vexi; and/or (<NUM>) Windows Runtime.

In some embodiments, devices and components of the integrated roofing accessories <NUM> of the present disclosure may be configured to utilize hardwired circuitry that may be used in place of or in combination with software instructions to implement features consistent with principles of the disclosure. Thus, implementations consistent with principles of the disclosure are not limited to any specific combination of hardware circuitry and software. For example, various embodiments may be embodied in many different ways as a software component such as, without limitation, a stand-alone software package, a combination of software packages, or it may be a software package incorporated as a "tool" in a larger software product.

For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may be downloadable from a network, for example, a website, as a stand-alone product or as an add-in package for installation in an existing software application.

For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may also be available as a client-server software application, or as a web-enabled software application. For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may also be embodied as a software package installed on a hardware device.

In some embodiments, various devices and components of the integrated roofing accessories <NUM>, such as the MEC <NUM>, may be configured to output to distinct, specifically programmed graphical user interface implementations of the present disclosure (e.g., a desktop, a web app. In various implementations of the present disclosure, a final output may be displayed on a displaying screen which may be, without limitation, a screen of a computer, a screen of a mobile device, or the like. In various implementations, the display may be a holographic display. In various implementations, the display may be a transparent surface that may receive a visual projection. Such projections may convey various forms of information, images, and/or objects. For example, such projections may be a visual overlay for a mobile augmented reality (MAR) application.

<FIG> depicts an example <NUM> transmission signal emitted from an antenna <NUM> of an integrated roofing accessory <NUM> in accordance with aspects of embodiments of the present description.

In some embodiments, <NUM> antennae may be directional in nature, as described above, due to factors such as beamforming and antenna shape. Accordingly, an antenna <NUM> may emit a signal <NUM> in a conical "field-of-view" (FOV) within which the angular beam steering range <NUM> over which the antenna <NUM> can direct a beamformed signal <NUM>. The signal <NUM> is formed as a beam and may be emitted in any direction within the limits of the FOV of the antenna. In some embodiments, the antenna <NUM> may have an FOV defined by the beam steering range <NUM>, such as, e.g., within an angle of incidence within about <NUM> degrees, <NUM> degrees, <NUM> degrees, or <NUM> degrees of a normal incidence relative to a surface of the antenna <NUM>, or other angle of incidence. Thus, the beam steering range <NUM> may cover angles of incidence across about, e.g., <NUM>, <NUM>, <NUM>, <NUM> or other suitable range of angles of incidence of beamformed <NUM> signals emitted from the antenna <NUM>.

<FIG> depicts various integrated roofing accessory antenna placements relative to a roof of a structure in accordance with aspects of embodiments of the present description.

As described above, effectiveness of signal coverage in a physical area is affected by the orientation and position of <NUM> antennae due to the directional nature imposed by beamforming <NUM> signals. Accordingly, integrated roofing accessories <NUM> and associated antennae may be installed on a roof <NUM> as a roofing accessory in one or more of various positions and orientations to best suit the environment.

In some embodiments, an integrated roofing accessory <NUM> may include a coplanar integrated roofing accessory 431a. The coplanar integrated roofing accessory 431a is a roofing accessory shaped package that is installed alongside traditional roofing accessories or roofing material on the roof <NUM> of the structure <NUM>. For example, the coplanar integrated roofing accessory 431a may have a shape matching the shingles of a residential home, thus forming a shingle for the roof, or integrated shingle. Thus, a top surface of the coplanar integrated roofing accessory 431a may be coplanar with the surrounding roofing material.

In some embodiments, the coplanar integrated roofing accessory 431a may have a thickness greater than the surrounding roofing material. In such a case, the coplanar integrated roofing accessory 431a may be inserted into a recess within the roof <NUM> such that a top surface of the coplanar integrated roofing accessory 431a is at a height above a top surface of the roof <NUM> that is coplanar with a top surface of the surrounding roofing material. However, in some embodiments, the coplanar integrated roofing accessory 431a may be installed on the top surface of the roof <NUM> such that the top surface of the coplanar integrated roofing accessory 431a rises to a height above the top surface of the roof <NUM> that is above a height of the top surface of the surrounding roofing material above the top surface of the roof <NUM>.

In some embodiments, the coplanar integrated roofing accessory 431a may have the advantages of being roughly flush with the roof <NUM>, providing a discrete device that homeowners or building owners would find less objectionable, and thus be more likely to install. However, the angle of a slope of the roof <NUM> direct a normal angle of incidence of an antenna of the coplanar integrated roofing accessory 431a upward. As a result, due to the beam steering range <NUM> of the coplanar integrated roofing accessory 431a being finite, the portion of the beam steering range <NUM> that can project a beam formed signal towards a device on the ground is reduced, resulting in less area that may be covered by the coplanar integrated roofing accessory 431a. Indeed, where the roof is horizontal, the beam steering range <NUM> may not extend even towards other integrated roofing accessories because the normal incidence would be directed vertically toward the sky.

Similarly, a ridge vent integrated roofing accessory 431c or front or back face siding integrated roofing accessory 431b may be employed that can be recessed into a surface of the structure <NUM> or mounted on the surface of the structure <NUM> for low profile and discrete installation. However, similar to the coplanar integrated roofing accessory 431a, the directional nature of the <NUM> antenna results in reduced sightlines afforded by the beam steering range <NUM>, and thus reduced coverage. The ridge vent integrated roofing accessory 431c may have better coverage because it may be configured to have two antenna portions, with each portion aligning with the slopes of the roof <NUM> on each side of the ridge, thus multiplying the beam steering range <NUM>. However, each antenna portion nevertheless may have reduced lines of sight to the ground where <NUM>-enabled devices may be located, thus reducing effective coverage in the area.

In some embodiments, to mitigate the coverage loss due to the directionally mounted coplanar integrated roofing accessory 431a, the siding integrated roofing accessory 431b and the ridge vent integrated roofing accessory 431c, multiple roofing accessories may be used on a single roof (<NUM> cell site). For example, the coplanar integrated roofing accessory 431a may be installed on each roof slope of the roof <NUM>, and the siding integrated roofing accessory 431b on each side of the structure, or on each face of the structure extending between roof slopes as a portion of the siding. In some embodiments, alternatively or in addition, to one or more coplanar integrated roofing accessories 431a, one or more siding integrated roofing accessories 431b, one or more ridge vent integrated roofing accessories 431c may be installed in the ridge vent of the roof <NUM>. Thus, antennae from the various roofing accessories are angled in multiple directions to provide overlapping beam steering ranges <NUM> for increased coverage in an area around the structure <NUM>.

Moreover, in some embodiments, the various roofing accessories can be integrated into a mesh network or a common software defined network, such as the software defined network <NUM> described above. As a result, the roofing accessories can share compute and storage resources, and behave as a cohesive system.

Additionally, or alternatively, each of the coplanar integrated roofing accessories 431a and siding integrated roofing accessories 431b may be antennae only or software define radios only, such as the antennae <NUM> and SDR <NUM> described above. Each coplanar integrated roofing accessory 431a and siding integrated roofing accessory 431b may interface with a hub roofing accessory in the ridge vent to centralize compute, storage, and user access radios in the ridge vent integrated roofing accessory 431c. Accordingly, each integrated roofing accessory may represent a modular component of an integrated roofing accessory <NUM> that may be separately detached and applied to various portions of the roof <NUM> to optimize coverage, while a control module including the centralized resources may be located in the ridge vent near access to power and infrastructure within the structure <NUM>.

In some embodiments, a vertical attachment integrated roofing accessory 431d may be employed that extends up from the roof in a vertical direction above the ground and the roof <NUM>. In some embodiments, the vertical attachment integrated roofing accessory 431d may have multiple vertically oriented faces, each having a horizontal angle of normal incidence relative to an antenna. For example, the vertical attachment integrated roofing accessory 431d may have a box configuration with four vertical faces, each vertical face including an antenna. However, any number of faces may be used, such as, e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> or more faces. In some embodiments, the faces may be arranged radially around a center point such that the combination of faces forms a prismatic shape. In some embodiments, the vertically oriented edges of each face may abut the vertically oriented edges of each adjacent face to form an enclosed prism.

In some embodiments, the number of faces may depend on the beam steering range <NUM> of each antenna. For example, where the beam steering range <NUM> includes a <NUM>-degree range (e.g., a maximum angle of incidence of <NUM> degrees relative to the normal incidence), the vertical attachment integrated roofing accessory 431d may be configured with four antennas such that where the beam steering range <NUM> of one antenna ends, the beam steering range <NUM> of an adjacent antenna begins.

In some embodiments, rather than a prismatic arrangement of faces, the vertical attachment integrated roofing accessory 431d may use triangular or trapezoidal faces that are angled downward to the ground, such that the combination of faces form an upside-down pyramid. Such an arrangement of faces directs the beam steering range <NUM> of each antenna to cover a larger area of the ground, thus increasing effective coverage of the vertical attachment roofing accessory 431d. The angle of faces may be selected to balance coverage of the ground with coverage of other structures <NUM> to communicate with other integrated roofing accessories <NUM>. As such, the faces may be oriented such that the beam steering range <NUM> may include a vertical limit of the range that extends to an angle above a horizontal that projects over a highest integrated roofing accessory <NUM> within the signal range of the vertical attachment integrated roofing accessory 431d.

In some embodiments, each face of the vertical attachment integrated roofing accessory 431d may include an antennae <NUM> and/or a SDR <NUM>. In some embodiments, electronics components, e. g, the MEC <NUM>, compute <NUM> and storage <NUM>, and optionally the SDR <NUM>, as well as other electronics components, may be housed in an electronics compartment (e.g., electronics compartment <NUM>) in a centralized location relative to the faces and shared amongst all the faces. The electronics compartment may extend vertically above the roof <NUM>, enclosed by the faces of the vertical attachment integrated roofing accessory 431d. Thus, processing componentry may be reduced and the vertical attachment integrated roofing accessory 431d may be modularized for any number of antennae but only needing one central computing resource hub.

However, the vertical attachment integrated roofing accessory 431d may also or alternatively be a combination of multiple integrated roofing accessories <NUM> configured into a single software defined network <NUM> to share resources amongst each roofing accessory. Such an arrangement results in fewer individual parts and easy plug-and-play construction of vertical attachment integrated roofing accessories 431d, as well as processing and storage redundancy.

Indeed, in some embodiments, the vertical attachment integrated roofing accessory 431d may be formed by arranging multiple siding integrated roofing accessories 431b or coplanar integrated roofing accessories 431a into the prismatic or pyramidal arrangement of faces described above. Similarly, the ridge vent integrated roofing accessory 431c may be two or more coplanar integrated roofing accessories 431a or siding integrated roofing accessories 431b arranged to match the shape of the ridge of the roof. As a result, regardless of which roofing accessory positioning is used, the same integrated roofing accessory <NUM> parts may be employed, only in different arrangements and positions on the roof <NUM>, reducing a number of models and a number of form factors of integrated roofing accessories <NUM>, and thus reducing manufacturing complexity and cost.

In some embodiments, regardless of the location, each integrated roofing accessory, 431a, 431b, 431c and 431d, may be configured to access resources from the structure <NUM> via the ridge vent. For example, the roofing accessories may include wiring or cabling to connect to mains power, roof mounted solar power, in-structure networking, a hardwire backhaul network (e.g., fiber optic cabling), among other resources routed through the structure <NUM> via the ridge vent.

<FIG> illustrates an example <NUM> mesh network using integrated roofing accessories installed on roofs of residential homes according to aspects of embodiments of the present description.

In some embodiments, because <NUM> signals are directional (see, beamforming described above), antenna placement in an area can affect <NUM> signal stability and strength because <NUM> signals may be dependent upon the clearest line of sight for the best possible communication. As such, roof placement for structure-to-structure and the placement on the structure may affect the integrity and strength of the signal.

In some embodiments, each home 40a, 40b and 40c is fitted with a <NUM>-enabled integrated roofing accessory 31a, 31b, and 31c, respectively. The integrated roofing accessories 31a, 31b, and 31c may provide at least two forms of communication: mesh networking with information sharing by signals between each integrated roofing accessory 31a, 31b, and 31c (denoted with dotted lines); and computing device communication providing <NUM> signals to a computing device, such as the <NUM>-enabled vehicle <NUM> (denoted with dashed lines).

In order to deliver reliable connectivity to a user in the presence of obstacles, a mmWave access point network may be built with redundancies of antennae 31a through 31c. There may be enough redundancy such that, in the event of LOS blocking, the network connection of the <NUM>-enabled device can be rapidly rerouted via another (e.g., from antenna 31a to antenna 31b or 31c). In such a mmWave access point network, or mesh network, a cluster of access points (e.g., integrated roofing accessories 31a, 31b, and 31c) may be coordinated to provide uninterrupted connectivity to the <NUM>-enabled device. By using such a cluster of access points, the network may overcome radio-link blockages due to obstacles.

In some embodiments, mesh networking, or the inter-home communication, supports network administration, maintenance and backhaul communication to the carrier. In some embodiments, each structure or home 40a, 40b and 40c may maintain communication with as many structures as possible in the event a structure goes away or there is a better path back to the carrier. Thus, in some embodiments, data transmission from a computing device back to a backhaul infrastructure may be dynamically managed within the network of <NUM>-enabled integrated roofing accessories 31a, 31b, and 31c. For example, a primary data connect for the vehicle <NUM> may be provided by home 40b because the integrated roofing accessories 31b and 31c with line-of-sight (LOS) to the vehicle <NUM> may communicate with each other to determine that integrated roofing accessory 31b has a stronger connection, and thus greater signal strength and signal integrated, resulting in greater speeds, greater stability, and decreased error rates and drop-outs.

As described above, each <NUM>-enabled device (e.g., vehicle <NUM>, a smartphone, a computer, a WiFi hotspot, among other <NUM>-enabled devices) in a mmWave network may be served by a cluster of integrated roofing accessories 31a, 31b, and 31c. In some embodiments, the integrated roofing accessories 31a, 31b, and 31c may be selected to be members of the cluster set of a computing device based on which integrated roofing accessories 31a, 31b, and 31c are accessible by the device.

In some embodiments, each integrated roofing accessory 31a, 31b, and 31c may be considered to be accessible if the device can receive a beacon waveform via the integrated roofing accessory 31a, 31b, and 31c. For example, in some embodiments, the mmWave capable integrated roofing accessories <NUM> may be installed on top of buildings, such as each residential home 40a, 40b and 40c. As a result of the shadowing loss characteristics within the mmWave band, the radio link between a computing device, such as a <NUM>-enabled vehicle <NUM>, and serving access point, antenna 31b and/or antenna 31c, will likely be disrupted if the line-of-sight (LOS) between the vehicle <NUM> and the access point is blocked by obstacles. For example, where the vehicle <NUM> passes close to another building with another antenna 31a, the LOS may be broken by the roof 43a, or the antenna 31a may not have the angular range to direct a beamformed signal to the location of the vehicle <NUM>. Similarly, when a pedestrian (with a <NUM>-enabled device) walks along a sidewalk, the pedestrian's LOS may be blocked by fixed obstacles (such as trees), or may be blocked by moving obstacles (such as large trucks), or may be blocked by other pedestrians. In a campus courtyard or a tourist hotspot, LOS blocking may be caused by crowds. Other types of LOS blocking may be caused by user motions, such as by hand or body rotations.

In some embodiments, among the integrated roofing accessories 31a, 31b, and 31c, one particular integrated roofing accessory (e.g., integrated roofing accessory 31b) can be selected as the serving integrated roofing accessory 31b for the device, e.g., the vehicle <NUM> to prevent or minimize the blocking and other disruptions. In some embodiments, the vehicle <NUM> may select the serving integrate roofing accessory, and/or integrated roofing accessories 31a, 31b or 31c in the mesh network may cooperatively identify the serving roofing accessory based on the strength and stability of test signals using, e.g., a beacon waveform. For example, to select the integrated roofing accessory to serve the vehicle <NUM> or other device, the beacon waveform may be a broadcast beacon or a swept beam beacon, whose reception has a signal-to-noise-ratio (SNR) threshold above a certain threshold or above the beacon waveform of each other integrate roofing accessory 31a, 31b and 31c. Accessibility information of an integrated roofing accessory 31a, 31b, and 31c by a device may indicate the best, e.g., transmit and receive beam weights, the antenna polarization (e.g. horizontal, vertical or circular) and the corresponding signal strengths. The transmit and receive antenna weights having the greatest signal strength and stability may determine the antenna directivity for a multi-element antenna array. The antenna weights can be implemented using either an analog, digital or hybrid implementation. Other implementations of directional antennas could also be supported by this description. For example, a dielectric lens antenna can focus mmWave energy through diffraction similar to how an optical lens focuses light. The antenna directivity of a dielectric lens antenna is controlled by configuring the switching feed elements.

In some embodiments, the beam synchronization may be maintained, e.g., by selecting the best beams for downlink (DL) and uplink (UL) communication with each of the integrated roofing accessories 31a, 31b, and 31c as the vehicle <NUM> moves physically through the network. Based on signal characteristics, e.g., detected by the integrated roofing accessories 31a, 31b and 31c or the vehicle <NUM>, or both, the servicing integrate roofing accessory may be maintained or changed as shadowing, blockage and distance to the vehicle <NUM> changes. For example, the serving roofing accessory may be tested for strength and integrity of signal each, e.g., <NUM> millisecond (ms), <NUM>, <NUM>, <NUM>, <NUM>, <NUM> second, <NUM> seconds, <NUM> seconds, or other testing frequency.

In some embodiments, the maximize the area covered by signals from the integrated roofing accessories 31a, 31b and 31c, the integrated roofing accessories 31a, 31b and 31c may be installed onto the respective roofs 43a, 43b, and 43c in an optimum roofing configuration, such as the configurations described above with reference to <FIG>. In some embodiments, the vertical configuration 431d may provide the greatest angular coverage.

In some embodiments, the mesh network may support backhaul by, e.g., forcing Border Gateway Protocol (BGP). BGP can support fast route switching of large networks. In addition, BGP may function as a routing bridge between <NUM> wireless, <NUM>/LTE/<NUM>(lite) and wired networks. However, other suitable routing protocols may be employed instead or in addition.

<FIG> depicts a diagram illustrative of embodiments of the present description including a residential neighborhood. Based upon statistics and sampling, roofing material is installed on one of three homes in the United States. The distribution may likely be more or less than <NUM> of <NUM>. Generally, when roofing tracks are installed a contractor will choose a brand of roofing accessories for the roofing for most properties.

The circles on the homes represent the structures with the integrated roofing accessory <NUM>. At the bottom of the diagram there are two sources of internet access for a <NUM> Roofing accessory network: Structure-A which is directly connected to fiber back to the carrier and the other, a super cell that connects to Structures A and B via wireless backhaul.

For Structure-A, the primary backhaul and internet access may be provided by the directly connected fiber. Secondary backhaul and internet access will be provided by the wireless supercell. The tertiary network access for Structure-A will come from Structure-B which is wireless connected to the supercell.

Structures-A, B, and C and the other structures with circles represent and participate in the <NUM> Roofing accessory Mesh network. Each blue dot/structure will have multiple dynamic paths/connection to the carrier network and services, plus the internet.

Claim 1:
An integrated roofing accessory (<NUM>) comprising:
- at least one roofing accessory installed on a roof (<NUM>), and
- an <NUM>-infrastructure-supporting electronic component (<NUM>) integrated with the at least one roofing accessory, the electronic component (<NUM>) comprising:
i) at least one transceiver (<NUM>) configured to produce millimeter wave (mmWave) frequency signals using at least one fifth generation cellular networking (<NUM>) protocol,
ii) at least one dielectric antenna (<NUM>, <NUM>, <NUM>, <NUM>) in electrical communication with the at least one transceiver (<NUM>) for emitting the mmWave frequency signals according to the at least one <NUM> protocol,
iii) an edge computing device (<NUM>) having at least one processor (<NUM>) and at least one non-transitory storage (<NUM>) with software to operate the edge computing device (<NUM>) in communication with the at least one transceiver (<NUM>), and
iv) at least one power supply;
wherein the software is configured to cause, when executed, the integrated roofing accessory (<NUM>) to communicate with at least one <NUM> network using the mmWave frequency signals; and
wherein the softwareis further configured to cause, when executed, the <NUM> network to communicate with the computing device.
characterized in that
the integrated roofing accessory (<NUM>) further comprises:
- a compartment (<NUM>), holding:
i) the at least one transceiver (<NUM>),
ii) the at least one dielectric antenna (<NUM>, <NUM>, <NUM>, <NUM>), and
iii) the at least one edge computing device (<NUM>);
wherein a portion of the compartment (<NUM>) comprises a roofing material; and
a frame (<NUM>, <NUM>, <NUM>) connected to the compartment (<NUM>) and to the roof (<NUM>).