Method and apparatus for distributing software

FIELD OF THE DISCLOSURE

The subject disclosure relates to a method and apparatus for distributing software.

BACKGROUND

As smart phones and other portable devices increasingly become ubiquitous, and data usage increases, macrocell base station devices and existing wireless infrastructure in turn require higher bandwidth capability in order to address the increased demand. To provide additional mobile bandwidth, small cell deployment is being pursued, with microcells and picocells providing coverage for much smaller areas than traditional macrocells.

In addition, most homes and businesses have grown to rely on broadband data access for services such as voice, video and Internet browsing, etc. Broadband access networks include satellite, 4G or 5G wireless, power line communication, fiber, cable, and telephone networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a block diagram illustrating an example, non-limiting embodiment of a guided-wave communications system in accordance with various aspects described herein.

FIG. 2 is a block diagram illustrating an example, non-limiting embodiment of a transmission device in accordance with various aspects described herein.

FIG. 3 is a graphical diagram illustrating an example, non-limiting embodiment of an electromagnetic field distribution in accordance with various aspects described herein.

FIG. 4 is a graphical diagram illustrating an example, non-limiting embodiment of an electromagnetic field distribution in accordance with various aspects described herein.

FIG. 5A is a graphical diagram illustrating an example, non-limiting embodiment of a frequency response in accordance with various aspects described herein.

FIG. 5B is a graphical diagram illustrating example, non-limiting embodiments of a longitudinal cross-section of an insulated wire depicting fields of guided electromagnetic waves at various operating frequencies in accordance with various aspects described herein.

FIG. 6 is a graphical diagram illustrating an example, non-limiting embodiment of an electromagnetic field distribution in accordance with various aspects described herein.

FIG. 7 is a block diagram illustrating an example, non-limiting embodiment of an arc coupler in accordance with various aspects described herein.

FIG. 8 is a block diagram illustrating an example, non-limiting embodiment of an arc coupler in accordance with various aspects described herein.

FIG. 9A is a block diagram illustrating an example, non-limiting embodiment of a stub coupler in accordance with various aspects described herein.

FIG. 9B is a diagram illustrating an example, non-limiting embodiment of an electromagnetic distribution in accordance with various aspects described herein.

FIGS. 10A and 10B are block diagrams illustrating example, non-limiting embodiments of couplers and transceivers in accordance with various aspects described herein.

FIG. 11 is a block diagram illustrating an example, non-limiting embodiment of a dual stub coupler in accordance with various aspects described herein.

FIG. 12 is a block diagram illustrating an example, non-limiting embodiment of a repeater system in accordance with various aspects described herein.

FIG. 13 illustrates a block diagram illustrating an example, non-limiting embodiment of a bidirectional repeater in accordance with various aspects described herein.

FIG. 14 is a block diagram illustrating an example, non-limiting embodiment of a waveguide system in accordance with various aspects described herein.

FIG. 15 is a block diagram illustrating an example, non-limiting embodiment of a guided-wave communications system in accordance with various aspects described herein.

FIGS. 16A & 16B are block diagrams illustrating an example, non-limiting embodiment of a system for managing a power grid communication system in accordance with various aspects described herein.

FIG. 17A illustrates a flow diagram of an example, non-limiting embodiment of a method for detecting and mitigating disturbances occurring in a communication network of the system of FIGS. 16A and 16B.

FIG. 17B illustrates a flow diagram of an example, non-limiting embodiment of a method for detecting and mitigating disturbances occurring in a communication network of the system of FIGS. 16A and 16B.

FIG. 18 is a block diagram illustrating an example, non-limiting embodiment of a guided-wave communications system that implements a de-centralized software distribution process in accordance with various aspects described herein.

FIG. 19 illustrates a block diagram illustrating another example, non-limiting embodiment of a guided-wave communications system that implements a de-centralized software distribution process in accordance with various aspects described herein.

FIG. 20 illustrates a flow diagram of an example, non-limiting embodiment of a method of distributing software in accordance with various aspects described herein.

FIG. 21 is a block diagram of an example, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

FIG. 22 is a block diagram of an example, non-limiting embodiment of a mobile network platform in accordance with various aspects described herein.

FIG. 23 is a block diagram of an example, non-limiting embodiment of a communication device in accordance with various aspects described herein.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the various embodiments. It is evident, however, that the various embodiments can be practiced without these details (and without applying to any particular networked environment or standard).

In an embodiment, a guided wave communication system is presented for sending and receiving communication signals such as data or other signaling via guided electromagnetic waves. The guided electromagnetic waves include, for example, surface waves or other electromagnetic waves that are bound to or guided by a transmission medium. It will be appreciated that a variety of transmission media can be utilized with guided wave communications without departing from example embodiments. Examples of such transmission media can include one or more of the following, either alone or in one or more combinations: wires, whether insulated or not, and whether single-stranded or multi-stranded; conductors of other shapes or configurations including wire bundles, cables, rods, rails, pipes; non-conductors such as dielectric pipes, rods, rails, or other dielectric members; combinations of conductors and dielectric materials; or other guided wave transmission media.

The inducement of guided electromagnetic waves on a transmission medium can be independent of any electrical potential, charge or current that is injected or otherwise transmitted through the transmission medium as part of an electrical circuit. For example, in the case where the transmission medium is a wire, it is to be appreciated that while a small current in the wire may be formed in response to the propagation of the guided waves along the wire, this can be due to the propagation of the electromagnetic wave along the wire surface, and is not formed in response to electrical potential, charge or current that is injected into the wire as part of an electrical circuit. The electromagnetic waves traveling on the wire therefore do not require a circuit to propagate along the wire surface. The wire therefore is a single wire transmission line that is not part of a circuit. Also, in some embodiments, a wire is not necessary, and the electromagnetic waves can propagate along a single line transmission medium that is not a wire.

More generally, “guided electromagnetic waves” or “guided waves” as described by the subject disclosure are affected by the presence of a physical object that is at least a part of the transmission medium (e.g., a bare wire or other conductor, a dielectric, an insulated wire, a conduit or other hollow element, a bundle of insulated wires that is coated, covered or surrounded by a dielectric or insulator or other wire bundle, or another form of solid, liquid or otherwise non-gaseous transmission medium) so as to be at least partially bound to or guided by the physical object and so as to propagate along a transmission path of the physical object. Such a physical object can operate as at least a part of a transmission medium that guides, by way of an interface of the transmission medium (e.g., an outer surface, inner surface, an interior portion between the outer and the inner surfaces or other boundary between elements of the transmission medium), the propagation of guided electromagnetic waves, which in turn can carry energy, data and/or other signals along the transmission path from a sending device to a receiving device.

Unlike free space propagation of wireless signals such as unguided (or unbounded) electromagnetic waves that decrease in intensity inversely by the square of the distance traveled by the unguided electromagnetic waves, guided electromagnetic waves can propagate along a transmission medium with less loss in magnitude per unit distance than experienced by unguided electromagnetic waves.

Unlike electrical signals, guided electromagnetic waves can propagate from a sending device to a receiving device without requiring a separate electrical return path between the sending device and the receiving device. As a consequence, guided electromagnetic waves can propagate from a sending device to a receiving device along a transmission medium having no conductive components (e.g., a dielectric strip), or via a transmission medium having no more than a single conductor (e.g., a single bare wire or insulated wire). Even if a transmission medium includes one or more conductive components and the guided electromagnetic waves propagating along the transmission medium generate currents that flow in the one or more conductive components in a direction of the guided electromagnetic waves, such guided electromagnetic waves can propagate along the transmission medium from a sending device to a receiving device without requiring a flow of opposing currents on an electrical return path between the sending device and the receiving device.

In a non-limiting illustration, consider electrical systems that transmit and receive electrical signals between sending and receiving devices by way of conductive media. Such systems generally rely on electrically separate forward and return paths. For instance, consider a coaxial cable having a center conductor and a ground shield that are separated by an insulator. Typically, in an electrical system a first terminal of a sending (or receiving) device can be connected to the center conductor, and a second terminal of the sending (or receiving) device can be connected to the ground shield. If the sending device injects an electrical signal in the center conductor via the first terminal, the electrical signal will propagate along the center conductor causing forward currents in the center conductor, and return currents in the ground shield. The same conditions apply for a two terminal receiving device.

In contrast, consider a guided wave communication system such as described in the subject disclosure, which can utilize different embodiments of a transmission medium (including among others a coaxial cable) for transmitting and receiving guided electromagnetic waves without an electrical return path. In one embodiment, for example, the guided wave communication system of the subject disclosure can be configured to induce guided electromagnetic waves that propagate along an outer surface of a coaxial cable. Although the guided electromagnetic waves will cause forward currents on the ground shield, the guided electromagnetic waves do not require return currents to enable the guided electromagnetic waves to propagate along the outer surface of the coaxial cable. The same can be said of other transmission media used by a guided wave communication system for the transmission and reception of guided electromagnetic waves. For example, guided electromagnetic waves induced by the guided wave communication system on an outer surface of a bare wire, or an insulated wire can propagate along the bare wire or the insulated bare wire without an electrical return path.

Consequently, electrical systems that require two or more conductors for carrying forward and reverse currents on separate conductors to enable the propagation of electrical signals injected by a sending device are distinct from guided wave systems that induce guided electromagnetic waves on an interface of a transmission medium without the need of an electrical return path to enable the propagation of the guided electromagnetic waves along the interface of the transmission medium.

It is further noted that guided electromagnetic waves as described in the subject disclosure can have an electromagnetic field structure that lies primarily or substantially outside of a transmission medium so as to be bound to or guided by the transmission medium and so as to propagate non-trivial distances on or along an outer surface of the transmission medium. In other embodiments, guided electromagnetic waves can have an electromagnetic field structure that lies primarily or substantially inside a transmission medium so as to be bound to or guided by the transmission medium and so as to propagate non-trivial distances within the transmission medium. In other embodiments, guided electromagnetic waves can have an electromagnetic field structure that lies partially inside and partially outside a transmission medium so as to be bound to or guided by the transmission medium and so as to propagate non-trivial distances along the transmission medium. The desired electronic field structure in an embodiment may vary based upon a variety of factors, including the desired transmission distance, the characteristics of the transmission medium itself, and environmental conditions/characteristics outside of the transmission medium (e.g., presence of rain, fog, atmospheric conditions, etc.).

Various embodiments described herein relate to coupling devices, that can be referred to as “waveguide coupling devices”, “waveguide couplers” or more simply as “couplers”, “coupling devices” or “launchers” for launching and/or extracting guided electromagnetic waves to and from a transmission medium at millimeter-wave frequencies (e.g., 30 to 300 GHz), wherein the wavelength can be small compared to one or more dimensions of the coupling device and/or the transmission medium such as the circumference of a wire or other cross sectional dimension, or lower microwave frequencies such as 300 MHz to 30 GHz. Transmissions can be generated to propagate as waves guided by a coupling device, such as: a strip, arc or other length of dielectric material; a horn, monopole, rod, slot or other antenna; an array of antennas; a magnetic resonant cavity, or other resonant coupler; a coil, a strip line, a waveguide or other coupling device. In operation, the coupling device receives an electromagnetic wave from a transmitter or transmission medium. The electromagnetic field structure of the electromagnetic wave can be carried inside the coupling device, outside the coupling device or some combination thereof. When the coupling device is in close proximity to a transmission medium, at least a portion of an electromagnetic wave couples to or is bound to the transmission medium, and continues to propagate as guided electromagnetic waves. In a reciprocal fashion, a coupling device can extract guided waves from a transmission medium and transfer these electromagnetic waves to a receiver.

According to an example embodiment, a surface wave is a type of guided wave that is guided by a surface of a transmission medium, such as an exterior or outer surface of the wire, or another surface of the wire that is adjacent to or exposed to another type of medium having different properties (e.g., dielectric properties). Indeed, in an example embodiment, a surface of the wire that guides a surface wave can represent a transitional surface between two different types of media. For example, in the case of a bare or uninsulated wire, the surface of the wire can be the outer or exterior conductive surface of the bare or uninsulated wire that is exposed to air or free space. As another example, in the case of insulated wire, the surface of the wire can be the conductive portion of the wire that meets the insulator portion of the wire, or can otherwise be the insulator surface of the wire that is exposed to air or free space, or can otherwise be any material region between the insulator surface of the wire and the conductive portion of the wire that meets the insulator portion of the wire, depending upon the relative differences in the properties (e.g., dielectric properties) of the insulator, air, and/or the conductor and further dependent on the frequency and propagation mode or modes of the guided wave.

According to an example embodiment, the term “about” a wire or other transmission medium used in conjunction with a guided wave can include fundamental guided wave propagation modes such as a guided waves having a circular or substantially circular field distribution, a symmetrical electromagnetic field distribution (e.g., electric field, magnetic field, electromagnetic field, etc.) or other fundamental mode pattern at least partially around a wire or other transmission medium. In addition, when a guided wave propagates “about” a wire or other transmission medium, it can do so according to a guided wave propagation mode that includes not only the fundamental wave propagation modes (e.g., zero order modes), but additionally or alternatively non-fundamental wave propagation modes such as higher-order guided wave modes (e.g., 1^storder modes, 2^ndorder modes, etc.), asymmetrical modes and/or other guided (e.g., surface) waves that have non-circular field distributions around a wire or other transmission medium. As used herein, the term “guided wave mode” refers to a guided wave propagation mode of a transmission medium, coupling device or other system component of a guided wave communication system.

For example, such non-circular field distributions can be unilateral or multi-lateral with one or more axial lobes characterized by relatively higher field strength and/or one or more nulls or null regions characterized by relatively low-field strength, zero-field strength or substantially zero-field strength. Further, the field distribution can otherwise vary as a function of azimuthal orientation around the wire such that one or more angular regions around the wire have an electric or magnetic field strength (or combination thereof) that is higher than one or more other angular regions of azimuthal orientation, according to an example embodiment. It will be appreciated that the relative orientations or positions of the guided wave higher order modes or asymmetrical modes can vary as the guided wave travels along the wire.

As used herein, the term “millimeter-wave” can refer to electromagnetic waves/signals that fall within the “millimeter-wave frequency band” of 30 GHz to 300 GHz. The term “microwave” can refer to electromagnetic waves/signals that fall within a “microwave frequency band” of 300 MHz to 300 GHz. The term “radio frequency” or “RF” can refer to electromagnetic waves/signals that fall within the “radio frequency band” of 10 kHz to 1 THz. It is appreciated that wireless signals, electrical signals, and guided electromagnetic waves as described in the subject disclosure can be configured to operate at any desirable frequency range, such as, for example, at frequencies within, above or below millimeter-wave and/or microwave frequency bands. In particular, when a coupling device or transmission medium includes a conductive element, the frequency of the guided electromagnetic waves that are carried by the coupling device and/or propagate along the transmission medium can be below the mean collision frequency of the electrons in the conductive element. Further, the frequency of the guided electromagnetic waves that are carried by the coupling device and/or propagate along the transmission medium can be a non-optical frequency, e.g. a radio frequency below the range of optical frequencies that begins at 1 THz.

As used herein, the term “antenna” can refer to a device that is part of a transmitting or receiving system to transmit/radiate or receive wireless signals.

In accordance with one or more embodiments, a waveguide system includes a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, including receiving, from a second waveguide system, first electromagnetic waves via a transmission medium, where the first electromagnetic waves are guided by the transmission medium without utilizing an electrical return path, where the first electromagnetic waves have a non-optical frequency range, where the first electromagnetic waves convey data, where the data comprises a software, and where the software is received by the waveguide system from the second waveguide system without being received directly from a network source server that originated the software. The waveguide system can adjust operations at the waveguide system according to the software. In one embodiment, the waveguide system can also transmit, to a third waveguide system, second electromagnetic waves via the transmission medium, where the second electromagnetic waves are guided by the transmission medium without utilizing the electrical return path, where the second electromagnetic waves have the non-optical frequency range, and where the second electromagnetic waves convey the data.

In accordance with one or more embodiments, a method includes authenticating, by a first network device, a second network device according to authentication information received from the second network device. The method includes responsive to an authentication of the second network device, receiving, by the first network device from the second network device, a software; and adjusting operations at the first network device according to the software. The method includes providing, by the first network device, a digital signature to the software to generate an adjusted software, where the digital signature indicates that the first network device has received the software. The method includes transmitting, to a third network device, the adjusted software.

In accordance with one or more embodiments, a machine-readable storage device includes instructions, which when executed by a processor of a network device cause the processor to perform operations including monitoring for an expiration of software operating at the first network device and, responsive to a determination that the software has expired, transmitting update requests to a group of network devices. The processor can, responsive to the update requests, receive first and second softwares from the group of network devices. The processor can compare the first and second software. The processor can, responsive to a determination that the first software is a later version than the second software, adjust operations at the first network device according to the first software. The transmitting of the update requests does not include providing the update requests to a network source server that originated the first software.

Referring now to FIG. 1, a block diagram 100 illustrating an example, non-limiting embodiment of a guided wave communications system is shown. In operation, a transmission device 101 receives one or more communication signals 110 from a communication network or other communications device that includes data and generates guided waves 120 to convey the data via the transmission medium 125 to the transmission device 102. The transmission device 102 receives the guided waves 120 and converts them to communication signals 112 that include the data for transmission to a communications network or other communications device. The guided waves 120 can be modulated to convey data via a modulation technique such as phase shift keying, frequency shift keying, quadrature amplitude modulation, amplitude modulation, multi-carrier modulation such as orthogonal frequency division multiplexing and via multiple access techniques such as frequency division multiplexing, time division multiplexing, code division multiplexing, multiplexing via differing wave propagation modes and via other modulation and access strategies.

The communication network or networks can include a wireless communication network such as a mobile data network, a cellular voice and data network, a wireless local area network (e.g., WiFi or an 802.xx network), a satellite communications network, a personal area network or other wireless network. The communication network or networks can also include a wired communication network such as a telephone network, an Ethernet network, a local area network, a wide area network such as the Internet, a broadband access network, a cable network, a fiber optic network, or other wired network. The communication devices can include a network edge device, bridge device or home gateway, a set-top box, broadband modem, telephone adapter, access point, base station, or other fixed communication device, a mobile communication device such as an automotive gateway or automobile, laptop computer, tablet, smartphone, cellular telephone, or other communication device.

In an example embodiment, the guided wave communication system 100 can operate in a bi-directional fashion where transmission device 102 receives one or more communication signals 112 from a communication network or device that includes other data and generates guided waves 122 to convey the other data via the transmission medium 125 to the transmission device 101. In this mode of operation, the transmission device 101 receives the guided waves 122 and converts them to communication signals 110 that include the other data for transmission to a communications network or device. The guided waves 122 can be modulated to convey data via a modulation technique such as phase shift keying, frequency shift keying, quadrature amplitude modulation, amplitude modulation, multi-carrier modulation such as orthogonal frequency division multiplexing and via multiple access techniques such as frequency division multiplexing, time division multiplexing, code division multiplexing, multiplexing via differing wave propagation modes and via other modulation and access strategies.

The transmission medium 125 can include a cable having at least one inner portion surrounded by a dielectric material such as an insulator or other dielectric cover, coating or other dielectric material, the dielectric material having an outer surface and a corresponding circumference. In an example embodiment, the transmission medium 125 operates as a single-wire transmission line to guide the transmission of an electromagnetic wave. When the transmission medium 125 is implemented as a single wire transmission system, it can include a wire. The wire can be insulated or uninsulated, and single-stranded or multi-stranded (e.g., braided). In other embodiments, the transmission medium 125 can contain conductors of other shapes or configurations including wire bundles, cables, rods, rails, pipes. In addition, the transmission medium 125 can include non-conductors such as dielectric pipes, rods, rails, or other dielectric members; combinations of conductors and dielectric materials, conductors without dielectric materials or other guided wave transmission media. It should be noted that the transmission medium 125 can otherwise include any of the transmission media previously discussed.

Further, as previously discussed, the guided waves 120 and 122 can be contrasted with radio transmissions over free space/air or conventional propagation of electrical power or signals through the conductor of a wire via an electrical circuit. In addition to the propagation of guided waves 120 and 122, the transmission medium 125 may optionally contain one or more wires that propagate electrical power or other communication signals in a conventional manner as a part of one or more electrical circuits.

Referring now to FIG. 2, a block diagram 200 illustrating an example, non-limiting embodiment of a transmission device is shown. The transmission device 101 or 102 includes a communications interface (I/F) 205, a transceiver 210 and a coupler 220.

In an example of operation, the communications interface 205 receives a communication signal 110 or 112 that includes data. In various embodiments, the communications interface 205 can include a wireless interface for receiving a wireless communication signal in accordance with a wireless standard protocol such as LTE or other cellular voice and data protocol, WiFi or an 802.11 protocol, WIMAX protocol, Ultra Wideband protocol, Bluetooth protocol, Zigbee protocol, a direct broadcast satellite (DBS) or other satellite communication protocol or other wireless protocol. In addition or in the alternative, the communications interface 205 includes a wired interface that operates in accordance with an Ethernet protocol, universal serial bus (USB) protocol, a data over cable service interface specification (DOCSIS) protocol, a digital subscriber line (DSL) protocol, a Firewire (IEEE 1394) protocol, or other wired protocol. In additional to standards-based protocols, the communications interface 205 can operate in conjunction with other wired or wireless protocol. In addition, the communications interface 205 can optionally operate in conjunction with a protocol stack that includes multiple protocol layers including a MAC protocol, transport protocol, application protocol, etc.

In an example of operation, the transceiver 210 generates an electromagnetic wave based on the communication signal 110 or 112 to convey the data. The electromagnetic wave has at least one carrier frequency and at least one corresponding wavelength. The carrier frequency can be within a millimeter-wave frequency band of 30 GHz-300 GHz, such as 60 GHz or a carrier frequency in the range of 30-40 GHz or a lower frequency band of 300 MHz-30 GHz in the microwave frequency range such as 26-30 GHz, 11 GHz, 6 GHz or 3 GHz, but it will be appreciated that other carrier frequencies are possible in other embodiments. In one mode of operation, the transceiver 210 merely upconverts the communications signal or signals 110 or 112 for transmission of the electromagnetic signal in the microwave or millimeter-wave band as a guided electromagnetic wave that is guided by or bound to the transmission medium 125. In another mode of operation, the communications interface 205 either converts the communication signal 110 or 112 to a baseband or near baseband signal or extracts the data from the communication signal 110 or 112 and the transceiver 210 modulates a high-frequency carrier with the data, the baseband or near baseband signal for transmission. It should be appreciated that the transceiver 210 can modulate the data received via the communication signal 110 or 112 to preserve one or more data communication protocols of the communication signal 110 or 112 either by encapsulation in the payload of a different protocol or by simple frequency shifting. In the alternative, the transceiver 210 can otherwise translate the data received via the communication signal 110 or 112 to a protocol that is different from the data communication protocol or protocols of the communication signal 110 or 112.

In an example of operation, the coupler 220 couples the electromagnetic wave to the transmission medium 125 as a guided electromagnetic wave to convey the communications signal or signals 110 or 112. While the prior description has focused on the operation of the transceiver 210 as a transmitter, the transceiver 210 can also operate to receive electromagnetic waves that convey other data from the single wire transmission medium via the coupler 220 and to generate communications signals 110 or 112, via communications interface 205 that includes the other data. Consider embodiments where an additional guided electromagnetic wave conveys other data that also propagates along the transmission medium 125. The coupler 220 can also couple this additional electromagnetic wave from the transmission medium 125 to the transceiver 210 for reception.

The transmission device 101 or 102 includes an optional training controller 230. In an example embodiment, the training controller 230 is implemented by a standalone processor or a processor that is shared with one or more other components of the transmission device 101 or 102. The training controller 230 selects the carrier frequencies, modulation schemes and/or guided wave modes for the guided electromagnetic waves based on feedback data received by the transceiver 210 from at least one remote transmission device coupled to receive the guided electromagnetic wave.

In an example embodiment, a guided electromagnetic wave transmitted by a remote transmission device 101 or 102 conveys data that also propagates along the transmission medium 125. The data from the remote transmission device 101 or 102 can be generated to include the feedback data. In operation, the coupler 220 also couples the guided electromagnetic wave from the transmission medium 125 and the transceiver receives the electromagnetic wave and processes the electromagnetic wave to extract the feedback data.

In an example embodiment, the training controller 230 operates based on the feedback data to evaluate a plurality of candidate frequencies, modulation schemes and/or transmission modes to select a carrier frequency, modulation scheme and/or transmission mode to enhance performance, such as throughput, signal strength, reduce propagation loss, etc.

Consider the following example: a transmission device 101 begins operation under control of the training controller 230 by sending a plurality of guided waves as test signals such as pilot waves or other test signals at a corresponding plurality of candidate frequencies and/or candidate modes directed to a remote transmission device 102 coupled to the transmission medium 125. The guided waves can include, in addition or in the alternative, test data. The test data can indicate the particular candidate frequency and/or guide-wave mode of the signal. In an embodiment, the training controller 230 at the remote transmission device 102 receives the test signals and/or test data from any of the guided waves that were properly received and determines the best candidate frequency and/or guided wave mode, a set of acceptable candidate frequencies and/or guided wave modes, or a rank ordering of candidate frequencies and/or guided wave modes. This selection of candidate frequenc(ies) or/and guided-mode(s) are generated by the training controller 230 based on one or more optimizing criteria such as received signal strength, bit error rate, packet error rate, signal to noise ratio, propagation loss, etc. The training controller 230 generates feedback data that indicates the selection of candidate frequenc(ies) or/and guided wave mode(s) and sends the feedback data to the transceiver 210 for transmission to the transmission device 101. The transmission device 101 and 102 can then communicate data with one another based on the selection of candidate frequenc(ies) or/and guided wave mode(s).

In other embodiments, the guided electromagnetic waves that contain the test signals and/or test data are reflected back, repeated back or otherwise looped back by the remote transmission device 102 to the transmission device 101 for reception and analysis by the training controller 230 of the transmission device 101 that initiated these waves. For example, the transmission device 101 can send a signal to the remote transmission device 102 to initiate a test mode where a physical reflector is switched on the line, a termination impedance is changed to cause reflections, a loop back mode is switched on to couple electromagnetic waves back to the source transmission device 102, and/or a repeater mode is enabled to amplify and retransmit the electromagnetic waves back to the source transmission device 102. The training controller 230 at the source transmission device 102 receives the test signals and/or test data from any of the guided waves that were properly received and determines selection of candidate frequenc(ies) or/and guided wave mode(s).

While the procedure above has been described in a start-up or initialization mode of operation, each transmission device 101 or 102 can send test signals, evaluate candidate frequencies or guided wave modes via non-test such as normal transmissions or otherwise evaluate candidate frequencies or guided wave modes at other times or continuously as well. In an example embodiment, the communication protocol between the transmission devices 101 and 102 can include an on-request or periodic test mode where either full testing or more limited testing of a subset of candidate frequencies and guided wave modes are tested and evaluated. In other modes of operation, the re-entry into such a test mode can be triggered by a degradation of performance due to a disturbance, weather conditions, etc. In an example embodiment, the receiver bandwidth of the transceiver 210 is either sufficiently wide or swept to receive all candidate frequencies or can be selectively adjusted by the training controller 230 to a training mode where the receiver bandwidth of the transceiver 210 is sufficiently wide or swept to receive all candidate frequencies.

Referring now to FIG. 3, a graphical diagram 300 illustrating an example, non-limiting embodiment of an electromagnetic field distribution is shown. In this embodiment, a transmission medium 125 in air includes an inner conductor 301 and an insulating jacket 302 of dielectric material, as shown in cross section. The diagram 300 includes different gray-scales that represent differing electromagnetic field strengths generated by the propagation of the guided wave having an asymmetrical and non-fundamental guided wave mode.

In particular, the electromagnetic field distribution corresponds to a modal “sweet spot” that enhances guided electromagnetic wave propagation along an insulated transmission medium and reduces end-to-end transmission loss. In this particular mode, electromagnetic waves are guided by the transmission medium 125 to propagate along an outer surface of the transmission medium—in this case, the outer surface of the insulating jacket 302. Electromagnetic waves are partially embedded in the insulator and partially radiating on the outer surface of the insulator. In this fashion, electromagnetic waves are “lightly” coupled to the insulator so as to enable electromagnetic wave propagation at long distances with low propagation loss.

As shown, the guided wave has a field structure that lies primarily or substantially outside of the transmission medium 125 that serves to guide the electromagnetic waves. The regions inside the conductor 301 have little or no field. Likewise regions inside the insulating jacket 302 have low field strength. The majority of the electromagnetic field strength is distributed in the lobes 304 at the outer surface of the insulating jacket 302 and in close proximity thereof. The presence of an asymmetric guided wave mode is shown by the high electromagnetic field strengths at the top and bottom of the outer surface of the insulating jacket 302 (in the orientation of the diagram)—as opposed to very small field strengths on the other sides of the insulating jacket 302.

The example shown corresponds to a 38 GHz electromagnetic wave guided by a wire with a diameter of 1.1 cm and a dielectric insulation of thickness of 0.36 cm. Because the electromagnetic wave is guided by the transmission medium 125 and the majority of the field strength is concentrated in the air outside of the insulating jacket 302 within a limited distance of the outer surface, the guided wave can propagate longitudinally down the transmission medium 125 with very low loss. In the example shown, this “limited distance” corresponds to a distance from the outer surface that is less than half the largest cross sectional dimension of the transmission medium 125. In this case, the largest cross sectional dimension of the wire corresponds to the overall diameter of 1.82 cm, however, this value can vary with the size and shape of the transmission medium 125. For example, should the transmission medium 125 be of a rectangular shape with a height of 0.3 cm and a width of 0.4 cm, the largest cross sectional dimension would be the diagonal of 0.5 cm and the corresponding limited distance would be 0.25 cm. The dimensions of the area containing the majority of the field strength also vary with the frequency, and in general, increase as carrier frequencies decrease.

It should also be noted that the components of a guided wave communication system, such as couplers and transmission media can have their own cut-off frequencies for each guided wave mode. The cut-off frequency generally sets forth the lowest frequency that a particular guided wave mode is designed to be supported by that particular component. In an example embodiment, the particular asymmetric mode of propagation shown is induced on the transmission medium 125 by an electromagnetic wave having a frequency that falls within a limited range (such as Fc to 2Fc) of the lower cut-off frequency Fc for this particular asymmetric mode. The lower cut-off frequency Fc is particular to the characteristics of transmission medium 125. For embodiments as shown that include an inner conductor 301 surrounded by an insulating jacket 302, this cutoff frequency can vary based on the dimensions and properties of the insulating jacket 302 and potentially the dimensions and properties of the inner conductor 301 and can be determined experimentally to have a desired mode pattern. It should be noted however, that similar effects can be found for a hollow dielectric or insulator without an inner conductor. In this case, the cutoff frequency can vary based on the dimensions and properties of the hollow dielectric or insulator.

At frequencies lower than the lower cut-off frequency, the asymmetric mode is difficult to induce in the transmission medium 125 and fails to propagate for all but trivial distances. As the frequency increases above the limited range of frequencies about the cut-off frequency, the asymmetric mode shifts more and more inward of the insulating jacket 302. At frequencies much larger than the cut-off frequency, the field strength is no longer concentrated outside of the insulating jacket, but primarily inside of the insulating jacket 302. While the transmission medium 125 provides strong guidance to the electromagnetic wave and propagation is still possible, ranges are more limited by increased losses due to propagation within the insulating jacket 302—as opposed to the surrounding air.

Referring now to FIG. 4, a graphical diagram 400 illustrating an example, non-limiting embodiment of an electromagnetic field distribution is shown. In particular, a cross section diagram 400, similar to FIG. 3 is shown with common reference numerals used to refer to similar elements. The example shown corresponds to a 60 GHz wave guided by a wire with a diameter of 1.1 cm and a dielectric insulation of thickness of 0.36 cm. Because the frequency of the guided wave is above the limited range of the cut-off frequency of this particular asymmetric mode, much of the field strength has shifted inward of the insulating jacket 302. In particular, the field strength is concentrated primarily inside of the insulating jacket 302. While the transmission medium 125 provides strong guidance to the electromagnetic wave and propagation is still possible, ranges are more limited when compared with the embodiment of FIG. 3, by increased losses due to propagation within the insulating jacket 302.

Referring now to FIG. 5A, a graphical diagram illustrating an example, non-limiting embodiment of a frequency response is shown. In particular, diagram 500 presents a graph of end-to-end loss (in dB) as a function of frequency, overlaid with electromagnetic field distributions 510, 520 and 530 at three points for a 200 cm insulated medium voltage wire. The boundary between the insulator and the surrounding air is represented by reference numeral 525 in each electromagnetic field distribution.

As discussed in conjunction with FIG. 3, an example of a desired asymmetric mode of propagation shown is induced on the transmission medium 125 by an electromagnetic wave having a frequency that falls within a limited range (such as Fc to 2Fc) of the lower cut-off frequency Fc of the transmission medium for this particular asymmetric mode. In particular, the electromagnetic field distribution 520 at 6 GHz falls within this modal “sweet spot” that enhances electromagnetic wave propagation along an insulated transmission medium and reduces end-to-end transmission loss. In this particular mode, guided waves are partially embedded in the insulator and partially radiating on the outer surface of the insulator. In this fashion, the electromagnetic waves are “lightly” coupled to the insulator so as to enable guided electromagnetic wave propagation at long distances with low propagation loss.

At lower frequencies represented by the electromagnetic field distribution 510 at 3 GHz, the asymmetric mode radiates more heavily generating higher propagation losses. At higher frequencies represented by the electromagnetic field distribution 530 at 9 GHz, the asymmetric mode shifts more and more inward of the insulating jacket providing too much absorption, again generating higher propagation losses.

Referring now to FIG. 5B, a graphical diagram 550 illustrating example, non-limiting embodiments of a longitudinal cross-section of a transmission medium 125, such as an insulated wire, depicting fields of guided electromagnetic waves at various operating frequencies is shown. As shown in diagram 556, when the guided electromagnetic waves are at approximately the cutoff frequency (f_c) corresponding to the modal “sweet spot”, the guided electromagnetic waves are loosely coupled to the insulated wire so that absorption is reduced, and the fields of the guided electromagnetic waves are bound sufficiently to reduce the amount radiated into the environment (e.g., air). Because absorption and radiation of the fields of the guided electromagnetic waves is low, propagation losses are consequently low, enabling the guided electromagnetic waves to propagate for longer distances.

As shown in diagram 554, propagation losses increase when an operating frequency of the guide electromagnetic waves increases above about two-times the cutoff frequency (f_c)—or as referred to, above the range of the “sweet spot”. More of the field strength of the electromagnetic wave is driven inside the insulating layer, increasing propagation losses. At frequencies much higher than the cutoff frequency (f_c) the guided electromagnetic waves are strongly bound to the insulated wire as a result of the fields emitted by the guided electromagnetic waves being concentrated in the insulation layer of the wire, as shown in diagram 552. This in turn raises propagation losses further due to absorption of the guided electromagnetic waves by the insulation layer. Similarly, propagation losses increase when the operating frequency of the guided electromagnetic waves is substantially below the cutoff frequency (f_c), as shown in diagram 558. At frequencies much lower than the cutoff frequency (f_c) the guided electromagnetic waves are weakly (or nominally) bound to the insulated wire and thereby tend to radiate into the environment (e.g., air), which in turn, raises propagation losses due to radiation of the guided electromagnetic waves.

Referring now to FIG. 6, a graphical diagram 600 illustrating an example, non-limiting embodiment of an electromagnetic field distribution is shown. In this embodiment, a transmission medium 602 is a bare wire, as shown in cross section. The diagram 300 includes different gray-scales that represent differing electromagnetic field strengths generated by the propagation of a guided wave having a symmetrical and fundamental guided wave mode at a single carrier frequency.

In this particular mode, electromagnetic waves are guided by the transmission medium 602 to propagate along an outer surface of the transmission medium—in this case, the outer surface of the bare wire. Electromagnetic waves are “lightly” coupled to the wire so as to enable electromagnetic wave propagation at long distances with low propagation loss. As shown, the guided wave has a field structure that lies substantially outside of the transmission medium 602 that serves to guide the electromagnetic waves. The regions inside the conductor 625 have little or no field.

Referring now to FIG. 7, a block diagram 700 illustrating an example, non-limiting embodiment of an arc coupler is shown. In particular a coupling device is presented for use in a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1. The coupling device includes an arc coupler 704 coupled to a transmitter circuit 712 and termination or damper 714. The arc coupler 704 can be made of a dielectric material, or other low-loss insulator (e.g., Teflon, polyethylene, etc.), or made of a conducting (e.g., metallic, non-metallic, etc.) material, or any combination of the foregoing materials. As shown, the arc coupler 704 operates as a waveguide and has a wave 706 propagating as a guided wave about a waveguide surface of the arc coupler 704. In the embodiment shown, at least a portion of the arc coupler 704 can be placed near a wire 702 or other transmission medium, (such as transmission medium 125), in order to facilitate coupling between the arc coupler 704 and the wire 702 or other transmission medium, as described herein to launch the guided wave 708 on the wire. The arc coupler 704 can be placed such that a portion of the curved arc coupler 704 is tangential to, and parallel or substantially parallel to the wire 702. The portion of the arc coupler 704 that is parallel to the wire can be an apex of the curve, or any point where a tangent of the curve is parallel to the wire 702. When the arc coupler 704 is positioned or placed thusly, the wave 706 travelling along the arc coupler 704 couples, at least in part, to the wire 702, and propagates as guided wave 708 around or about the wire surface of the wire 702 and longitudinally along the wire 702. The guided wave 708 can be characterized as a surface wave or other electromagnetic wave that is guided by or bound to the wire 702 or other transmission medium.

A portion of the wave 706 that does not couple to the wire 702 propagates as a wave 710 along the arc coupler 704. It will be appreciated that the arc coupler 704 can be configured and arranged in a variety of positions in relation to the wire 702 to achieve a desired level of coupling or non-coupling of the wave 706 to the wire 702. For example, the curvature and/or length of the arc coupler 704 that is parallel or substantially parallel, as well as its separation distance (which can include zero separation distance in an embodiment), to the wire 702 can be varied without departing from example embodiments. Likewise, the arrangement of arc coupler 704 in relation to the wire 702 may be varied based upon considerations of the respective intrinsic characteristics (e.g., thickness, composition, electromagnetic properties, etc.) of the wire 702 and the arc coupler 704, as well as the characteristics (e.g., frequency, energy level, etc.) of the waves 706 and 708.

The guided wave 708 stays parallel or substantially parallel to the wire 702, even as the wire 702 bends and flexes. Bends in the wire 702 can increase transmission losses, which are also dependent on wire diameters, frequency, and materials. If the dimensions of the arc coupler 704 are chosen for efficient power transfer, most of the power in the wave 706 is transferred to the wire 702, with little power remaining in wave 710. It will be appreciated that the guided wave 708 can still be multi-modal in nature (discussed herein), including having modes that are non-fundamental or asymmetric, while traveling along a path that is parallel or substantially parallel to the wire 702, with or without a fundamental transmission mode. In an embodiment, non-fundamental or asymmetric modes can be utilized to minimize transmission losses and/or obtain increased propagation distances.

It is noted that the term parallel is generally a geometric construct which often is not exactly achievable in real systems. Accordingly, the term parallel as utilized in the subject disclosure represents an approximation rather than an exact configuration when used to describe embodiments disclosed in the subject disclosure. In an embodiment, substantially parallel can include approximations that are within 30 degrees of true parallel in all dimensions.

In an embodiment, the wave 706 can exhibit one or more wave propagation modes. The arc coupler modes can be dependent on the shape and/or design of the coupler 704. The one or more arc coupler modes of wave 706 can generate, influence, or impact one or more wave propagation modes of the guided wave 708 propagating along wire 702. It should be particularly noted however that the guided wave modes present in the guided wave 706 may be the same or different from the guided wave modes of the guided wave 708. In this fashion, one or more guided wave modes of the guided wave 706 may not be transferred to the guided wave 708, and further one or more guided wave modes of guided wave 708 may not have been present in guided wave 706. It should also be noted that the cut-off frequency of the arc coupler 704 for a particular guided wave mode may be different than the cutoff frequency of the wire 702 or other transmission medium for that same mode. For example, while the wire 702 or other transmission medium may be operated slightly above its cutoff frequency for a particular guided wave mode, the arc coupler 704 may be operated well above its cut-off frequency for that same mode for low loss, slightly below its cut-off frequency for that same mode to, for example, induce greater coupling and power transfer, or some other point in relation to the arc coupler's cutoff frequency for that mode.

In an embodiment, the wave propagation modes on the wire 702 can be similar to the arc coupler modes since both waves 706 and 708 propagate about the outside of the arc coupler 704 and wire 702 respectively. In some embodiments, as the wave 706 couples to the wire 702, the modes can change form, or new modes can be created or generated, due to the coupling between the arc coupler 704 and the wire 702. For example, differences in size, material, and/or impedances of the arc coupler 704 and wire 702 may create additional modes not present in the arc coupler modes and/or suppress some of the arc coupler modes. The wave propagation modes can comprise the fundamental transverse electromagnetic mode (Quasi-TEM₀₀), where only small electric and/or magnetic fields extend in the direction of propagation, and the electric and magnetic fields extend radially outwards while the guided wave propagates along the wire. This guided wave mode can be donut shaped, where few of the electromagnetic fields exist within the arc coupler 704 or wire 702.

Waves 706 and 708 can comprise a fundamental TEM mode where the fields extend radially outwards, and also comprise other, non-fundamental (e.g., asymmetric, higher-level, etc.) modes. While particular wave propagation modes are discussed above, other wave propagation modes are likewise possible such as transverse electric (TE) and transverse magnetic (TM) modes, based on the frequencies employed, the design of the arc coupler 704, the dimensions and composition of the wire 702, as well as its surface characteristics, its insulation if present, the electromagnetic properties of the surrounding environment, etc. It should be noted that, depending on the frequency, the electrical and physical characteristics of the wire 702 and the particular wave propagation modes that are generated, guided wave 708 can travel along the conductive surface of an oxidized uninsulated wire, an unoxidized uninsulated wire, an insulated wire and/or along the insulating surface of an insulated wire.

In an embodiment, a diameter of the arc coupler 704 is smaller than the diameter of the wire 702. For the millimeter-band wavelength being used, the arc coupler 704 supports a single waveguide mode that makes up wave 706. This single waveguide mode can change as it couples to the wire 702 as guided wave 708. If the arc coupler 704 were larger, more than one waveguide mode can be supported, but these additional waveguide modes may not couple to the wire 702 as efficiently, and higher coupling losses can result. However, in some alternative embodiments, the diameter of the arc coupler 704 can be equal to or larger than the diameter of the wire 702, for example, where higher coupling losses are desirable or when used in conjunction with other techniques to otherwise reduce coupling losses (e.g., impedance matching with tapering, etc.).

In an embodiment, the wavelength of the waves 706 and 708 are comparable in size, or smaller than a circumference of the arc coupler 704 and the wire 702. In an example, if the wire 702 has a diameter of 0.5 cm, and a corresponding circumference of around 1.5 cm, the wavelength of the transmission is around 1.5 cm or less, corresponding to a frequency of 70 GHz or greater. In another embodiment, a suitable frequency of the transmission and the carrier-wave signal is in the range of 30-100 GHz, perhaps around 30-60 GHz, and around 38 GHz in one example. In an embodiment, when the circumference of the arc coupler 704 and wire 702 is comparable in size to, or greater, than a wavelength of the transmission, the waves 706 and 708 can exhibit multiple wave propagation modes including fundamental and/or non-fundamental (symmetric and/or asymmetric) modes that propagate over sufficient distances to support various communication systems described herein. The waves 706 and 708 can therefore comprise more than one type of electric and magnetic field configuration. In an embodiment, as the guided wave 708 propagates down the wire 702, the electrical and magnetic field configurations will remain the same from end to end of the wire 702. In other embodiments, as the guided wave 708 encounters interference (distortion or obstructions) or loses energy due to transmission losses or scattering, the electric and magnetic field configurations can change as the guided wave 708 propagates down wire 702.

In an embodiment, the arc coupler 704 can be composed of nylon, Teflon, polyethylene, a polyamide, or other plastics. In other embodiments, other dielectric materials are possible. The wire surface of wire 702 can be metallic with either a bare metallic surface, or can be insulated using plastic, dielectric, insulator or other coating, jacket or sheathing. In an embodiment, a dielectric or otherwise non-conducting/insulated waveguide can be paired with either a bare/metallic wire or insulated wire. In other embodiments, a metallic and/or conductive waveguide can be paired with a bare/metallic wire or insulated wire. In an embodiment, an oxidation layer on the bare metallic surface of the wire 702 (e.g., resulting from exposure of the bare metallic surface to oxygen/air) can also provide insulating or dielectric properties similar to those provided by some insulators or sheathings.

It is noted that the graphical representations of waves 706, 708 and 710 are presented merely to illustrate the principles that wave 706 induces or otherwise launches a guided wave 708 on a wire 702 that operates, for example, as a single wire transmission line. Wave 710 represents the portion of wave 706 that remains on the arc coupler 704 after the generation of guided wave 708. The actual electric and magnetic fields generated as a result of such wave propagation may vary depending on the frequencies employed, the particular wave propagation mode or modes, the design of the arc coupler 704, the dimensions and composition of the wire 702, as well as its surface characteristics, its optional insulation, the electromagnetic properties of the surrounding environment, etc.

It is noted that arc coupler 704 can include a termination circuit or damper 714 at the end of the arc coupler 704 that can absorb leftover radiation or energy from wave 710. The termination circuit or damper 714 can prevent and/or minimize the leftover radiation or energy from wave 710 reflecting back toward transmitter circuit 712. In an embodiment, the termination circuit or damper 714 can include termination resistors, and/or other components that perform impedance matching to attenuate reflection. In some embodiments, if the coupling efficiencies are high enough, and/or wave 710 is sufficiently small, it may not be necessary to use a termination circuit or damper 714. For the sake of simplicity, these transmitter 712 and termination circuits or dampers 714 may not be depicted in the other figures, but in those embodiments, transmitter and termination circuits or dampers may possibly be used.

Further, while a single arc coupler 704 is presented that generates a single guided wave 708, multiple arc couplers 704 placed at different points along the wire 702 and/or at different azimuthal orientations about the wire can be employed to generate and receive multiple guided waves 708 at the same or different frequencies, at the same or different phases, at the same or different wave propagation modes.

FIG. 8, a block diagram 800 illustrating an example, non-limiting embodiment of an arc coupler is shown. In the embodiment shown, at least a portion of the coupler 704 can be placed near a wire 702 or other transmission medium, (such as transmission medium 125), in order to facilitate coupling between the arc coupler 704 and the wire 702 or other transmission medium, to extract a portion of the guided wave 806 as a guided wave 808 as described herein. The arc coupler 704 can be placed such that a portion of the curved arc coupler 704 is tangential to, and parallel or substantially parallel to the wire 702. The portion of the arc coupler 704 that is parallel to the wire can be an apex of the curve, or any point where a tangent of the curve is parallel to the wire 702. When the arc coupler 704 is positioned or placed thusly, the wave 806 travelling along the wire 702 couples, at least in part, to the arc coupler 704, and propagates as guided wave 808 along the arc coupler 704 to a receiving device (not expressly shown). A portion of the wave 806 that does not couple to the arc coupler propagates as wave 810 along the wire 702 or other transmission medium.

In an embodiment, the wave 806 can exhibit one or more wave propagation modes. The arc coupler modes can be dependent on the shape and/or design of the coupler 704. The one or more modes of guided wave 806 can generate, influence, or impact one or more guide-wave modes of the guided wave 808 propagating along the arc coupler 704. It should be particularly noted however that the guided wave modes present in the guided wave 806 may be the same or different from the guided wave modes of the guided wave 808. In this fashion, one or more guided wave modes of the guided wave 806 may not be transferred to the guided wave 808, and further one or more guided wave modes of guided wave 808 may not have been present in guided wave 806.

Referring now to FIG. 9A, a block diagram 900 illustrating an example, non-limiting embodiment of a stub coupler is shown. In particular a coupling device that includes stub coupler 904 is presented for use in a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1. The stub coupler 904 can be made of a dielectric material, or other low-loss insulator (e.g., Teflon, polyethylene and etc.), or made of a conducting (e.g., metallic, non-metallic, etc.) material, or any combination of the foregoing materials. As shown, the stub coupler 904 operates as a waveguide and has a wave 906 propagating as a guided wave about a waveguide surface of the stub coupler 904. In the embodiment shown, at least a portion of the stub coupler 904 can be placed near a wire 702 or other transmission medium, (such as transmission medium 125), in order to facilitate coupling between the stub coupler 904 and the wire 702 or other transmission medium, as described herein to launch the guided wave 908 on the wire.

In an embodiment, the stub coupler 904 is curved, and an end of the stub coupler 904 can be tied, fastened, or otherwise mechanically coupled to a wire 702. When the end of the stub coupler 904 is fastened to the wire 702, the end of the stub coupler 904 is parallel or substantially parallel to the wire 702. Alternatively, another portion of the dielectric waveguide beyond an end can be fastened or coupled to wire 702 such that the fastened or coupled portion is parallel or substantially parallel to the wire 702. The fastener 910 can be a nylon cable tie or other type of non-conducting/dielectric material that is either separate from the stub coupler 904 or constructed as an integrated component of the stub coupler 904. The stub coupler 904 can be adjacent to the wire 702 without surrounding the wire 702.

Like the arc coupler 704 described in conjunction with FIG. 7, when the stub coupler 904 is placed with the end parallel to the wire 702, the guided wave 906 travelling along the stub coupler 904 couples to the wire 702, and propagates as guided wave 908 about the wire surface of the wire 702. In an example embodiment, the guided wave 908 can be characterized as a surface wave or other electromagnetic wave.

It is noted that the graphical representations of waves 906 and 908 are presented merely to illustrate the principles that wave 906 induces or otherwise launches a guided wave 908 on a wire 702 that operates, for example, as a single wire transmission line. The actual electric and magnetic fields generated as a result of such wave propagation may vary depending on one or more of the shape and/or design of the coupler, the relative position of the dielectric waveguide to the wire, the frequencies employed, the design of the stub coupler 904, the dimensions and composition of the wire 702, as well as its surface characteristics, its optional insulation, the electromagnetic properties of the surrounding environment, etc.

In an embodiment, an end of stub coupler 904 can taper towards the wire 702 in order to increase coupling efficiencies. Indeed, the tapering of the end of the stub coupler 904 can provide impedance matching to the wire 702 and reduce reflections, according to an example embodiment of the subject disclosure. For example, an end of the stub coupler 904 can be gradually tapered in order to obtain a desired level of coupling between waves 906 and 908 as illustrated in FIG. 9A.

In an embodiment, the fastener 910 can be placed such that there is a short length of the stub coupler 904 between the fastener 910 and an end of the stub coupler 904. Maximum coupling efficiencies are realized in this embodiment when the length of the end of the stub coupler 904 that is beyond the fastener 910 is at least several wavelengths long for whatever frequency is being transmitted.

Turning now to FIG. 9B, a diagram 950 illustrating an example, non-limiting embodiment of an electromagnetic distribution in accordance with various aspects described herein is shown. In particular, an electromagnetic distribution is presented in two dimensions for a transmission device that includes coupler 952, shown in an example stub coupler constructed of a dielectric material. The coupler 952 couples an electromagnetic wave for propagation as a guided wave along an outer surface of a wire 702 or other transmission medium.

The coupler 952 guides the electromagnetic wave to a junction at x₀via a symmetrical guided wave mode. While some of the energy of the electromagnetic wave that propagates along the coupler 952 is outside of the coupler 952, the majority of the energy of this electromagnetic wave is contained within the coupler 952. The junction at x₀couples the electromagnetic wave to the wire 702 or other transmission medium at an azimuthal angle corresponding to the bottom of the transmission medium. This coupling induces an electromagnetic wave that is guided to propagate along the outer surface of the wire 702 or other transmission medium via at least one guided wave mode in direction 956. The majority of the energy of the guided electromagnetic wave is outside or, but in close proximity to the outer surface of the wire 702 or other transmission medium. In the example shown, the junction at x₀forms an electromagnetic wave that propagates via both a symmetrical mode and at least one asymmetrical surface mode, such as the first order mode presented in conjunction with FIG. 3, that skims the surface of the wire 702 or other transmission medium.

It is noted that the graphical representations of guided waves are presented merely to illustrate an example of guided wave coupling and propagation. The actual electric and magnetic fields generated as a result of such wave propagation may vary depending on the frequencies employed, the design and/or configuration of the coupler 952, the dimensions and composition of the wire 702 or other transmission medium, as well as its surface characteristics, its insulation if present, the electromagnetic properties of the surrounding environment, etc.

Turning now to FIG. 10A, illustrated is a block diagram 1000 of an example, non-limiting embodiment of a coupler and transceiver system in accordance with various aspects described herein. The system is an example of transmission device 101 or 102. In particular, the communication interface 1008 is an example of communications interface 205, the stub coupler 1002 is an example of coupler 220, and the transmitter/receiver device 1006, diplexer 1016, power amplifier 1014, low noise amplifier 1018, frequency mixers 1010 and 1020 and local oscillator 1012 collectively form an example of transceiver 210.

In operation, the transmitter/receiver device 1006 launches and receives waves (e.g., guided wave 1004 onto stub coupler 1002). The guided waves 1004 can be used to transport signals received from and sent to a host device, base station, mobile devices, a building or other device by way of a communications interface 1008. The communications interface 1008 can be an integral part of system 1000. Alternatively, the communications interface 1008 can be tethered to system 1000. The communications interface 1008 can comprise a wireless interface for interfacing to the host device, base station, mobile devices, a building or other device utilizing any of various wireless signaling protocols (e.g., LTE, WiFi, WiMAX, IEEE 802.xx, etc.) including an infrared protocol such as an infrared data association (IrDA) protocol or other line of sight optical protocol. The communications interface 1008 can also comprise a wired interface such as a fiber optic line, coaxial cable, twisted pair, category 5 (CAT-5) cable or other suitable wired or optical mediums for communicating with the host device, base station, mobile devices, a building or other device via a protocol such as an Ethernet protocol, universal serial bus (USB) protocol, a data over cable service interface specification (DOCSIS) protocol, a digital subscriber line (DSL) protocol, a Firewire (IEEE 1394) protocol, or other wired or optical protocol. For embodiments where system 1000 functions as a repeater, the communications interface 1008 may not be necessary.

The output signals (e.g., Tx) of the communications interface 1008 can be combined with a carrier wave (e.g., millimeter-wave carrier wave) generated by a local oscillator 1012 at frequency mixer 1010. Frequency mixer 1010 can use heterodyning techniques or other frequency shifting techniques to frequency shift the output signals from communications interface 1008. For example, signals sent to and from the communications interface 1008 can be modulated signals such as orthogonal frequency division multiplexed (OFDM) signals formatted in accordance with a Long-Term Evolution (LTE) wireless protocol or other wireless 3G, 4G, 5G or higher voice and data protocol, a Zigbee, WIMAX, UltraWideband or IEEE 802.11 wireless protocol; a wired protocol such as an Ethernet protocol, universal serial bus (USB) protocol, a data over cable service interface specification (DOCSIS) protocol, a digital subscriber line (DSL) protocol, a Firewire (IEEE 1394) protocol or other wired or wireless protocol. In an example embodiment, this frequency conversion can be done in the analog domain, and as a result, the frequency shifting can be done without regard to the type of communications protocol used by a base station, mobile devices, or in-building devices. As new communications technologies are developed, the communications interface 1008 can be upgraded (e.g., updated with software, firmware, and/or hardware) or replaced and the frequency shifting and transmission apparatus can remain, simplifying upgrades. The carrier wave can then be sent to a power amplifier (“PA”) 1014 and can be transmitted via the transmitter receiver device 1006 via the diplexer 1016.

Signals received from the transmitter/receiver device 1006 that are directed towards the communications interface 1008 can be separated from other signals via diplexer 1016. The received signal can then be sent to low noise amplifier (“LNA”) 1018 for amplification. A frequency mixer 1020, with help from local oscillator 1012 can downshift the received signal (which is in the millimeter-wave band or around 38 GHz in some embodiments) to the native frequency. The communications interface 1008 can then receive the transmission at an input port (Rx).

In an embodiment, transmitter/receiver device 1006 can include a cylindrical or non-cylindrical metal (which, for example, can be hollow in an embodiment, but not necessarily drawn to scale) or other conducting or non-conducting waveguide and an end of the stub coupler 1002 can be placed in or in proximity to the waveguide or the transmitter/receiver device 1006 such that when the transmitter/receiver device 1006 generates a transmission, the guided wave couples to stub coupler 1002 and propagates as a guided wave 1004 about the waveguide surface of the stub coupler 1002. In some embodiments, the guided wave 1004 can propagate in part on the outer surface of the stub coupler 1002 and in part inside the stub coupler 1002. In other embodiments, the guided wave 1004 can propagate substantially or completely on the outer surface of the stub coupler 1002. In yet other embodiments, the guided wave 1004 can propagate substantially or completely inside the stub coupler 1002. In this latter embodiment, the guided wave 1004 can radiate at an end of the stub coupler 1002 (such as the tapered end shown in FIG. 4) for coupling to a transmission medium such as a wire 702 of FIG. 7. Similarly, if guided wave 1004 is incoming (coupled to the stub coupler 1002 from a wire 702), guided wave 1004 then enters the transmitter/receiver device 1006 and couples to the cylindrical waveguide or conducting waveguide. While transmitter/receiver device 1006 is shown to include a separate waveguide—an antenna, cavity resonator, klystron, magnetron, travelling wave tube, or other radiating element can be employed to induce a guided wave on the coupler 1002, with or without the separate waveguide.

In an embodiment, stub coupler 1002 can be wholly constructed of a dielectric material (or another suitable insulating material), without any metallic or otherwise conducting materials therein. Stub coupler 1002 can be composed of nylon, Teflon, polyethylene, a polyamide, other plastics, or other materials that are non-conducting and suitable for facilitating transmission of electromagnetic waves at least in part on an outer surface of such materials. In another embodiment, stub coupler 1002 can include a core that is conducting/metallic, and have an exterior dielectric surface. Similarly, a transmission medium that couples to the stub coupler 1002 for propagating electromagnetic waves induced by the stub coupler 1002 or for supplying electromagnetic waves to the stub coupler 1002 can, in addition to being a bare or insulated wire, be wholly constructed of a dielectric material (or another suitable insulating material), without any metallic or otherwise conducting materials therein.

It is noted that although FIG. 10A shows that the opening of transmitter receiver device 1006 is much wider than the stub coupler 1002, this is not to scale, and that in other embodiments the width of the stub coupler 1002 is comparable or slightly smaller than the opening of the hollow waveguide. It is also not shown, but in an embodiment, an end of the coupler 1002 that is inserted into the transmitter/receiver device 1006 tapers down in order to reduce reflection and increase coupling efficiencies.

Before coupling to the stub coupler 1002, the one or more waveguide modes of the guided wave generated by the transmitter/receiver device 1006 can couple to the stub coupler 1002 to induce one or more wave propagation modes of the guided wave 1004. The wave propagation modes of the guided wave 1004 can be different than the hollow metal waveguide modes due to the different characteristics of the hollow metal waveguide and the dielectric waveguide. For instance, wave propagation modes of the guided wave 1004 can comprise the fundamental transverse electromagnetic mode (Quasi-TEM₀₀), where only small electrical and/or magnetic fields extend in the direction of propagation, and the electric and magnetic fields extend radially outwards from the stub coupler 1002 while the guided waves propagate along the stub coupler 1002. The fundamental transverse electromagnetic mode wave propagation mode may or may not exist inside a waveguide that is hollow. Therefore, the hollow metal waveguide modes that are used by transmitter/receiver device 1006 are waveguide modes that can couple effectively and efficiently to wave propagation modes of stub coupler 1002.

It will be appreciated that other constructs or combinations of the transmitter/receiver device 1006 and stub coupler 1002 are possible. For example, a stub coupler 1002′ can be placed tangentially or in parallel (with or without a gap) with respect to an outer surface of the hollow metal waveguide of the transmitter/receiver device 1006′ (corresponding circuitry not shown) as depicted by reference 1000′ of FIG. 10B. In another embodiment, not shown by reference 1000′, the stub coupler 1002′ can be placed inside the hollow metal waveguide of the transmitter/receiver device 1006′ without an axis of the stub coupler 1002′ being coaxially aligned with an axis of the hollow metal waveguide of the transmitter/receiver device 1006′. In either of these embodiments, the guided wave generated by the transmitter/receiver device 1006′ can couple to a surface of the stub coupler 1002′ to induce one or more wave propagation modes of the guided wave 1004′ on the stub coupler 1002′ including a fundamental mode (e.g., a symmetric mode) and/or a non-fundamental mode (e.g., asymmetric mode).

In one embodiment, the guided wave 1004′ can propagate in part on the outer surface of the stub coupler 1002′ and in part inside the stub coupler 1002′. In another embodiment, the guided wave 1004′ can propagate substantially or completely on the outer surface of the stub coupler 1002′. In yet other embodiments, the guided wave 1004′ can propagate substantially or completely inside the stub coupler 1002′. In this latter embodiment, the guided wave 1004′ can radiate at an end of the stub coupler 1002′ (such as the tapered end shown in FIG. 9) for coupling to a transmission medium such as a wire 702 of FIG. 9.

It will be further appreciated that other constructs the transmitter/receiver device 1006 are possible. For example, a hollow metal waveguide of a transmitter/receiver device 1006″ (corresponding circuitry not shown), depicted in FIG. 10B as reference 1000″, can be placed tangentially or in parallel (with or without a gap) with respect to an outer surface of a transmission medium such as the wire 702 of FIG. 4 without the use of the stub coupler 1002. In this embodiment, the guided wave generated by the transmitter/receiver device 1006″ can couple to a surface of the wire 702 to induce one or more wave propagation modes of a guided wave 908 on the wire 702 including a fundamental mode (e.g., a symmetric mode) and/or a non-fundamental mode (e.g., asymmetric mode). In another embodiment, the wire 702 can be positioned inside a hollow metal waveguide of a transmitter/receiver device 1006′ (corresponding circuitry not shown) so that an axis of the wire 702 is coaxially (or not coaxially) aligned with an axis of the hollow metal waveguide without the use of the stub coupler 1002—see FIG. 10B reference 1000′″. In this embodiment, the guided wave generated by the transmitter/receiver device 1006′″ can couple to a surface of the wire 702 to induce one or more wave propagation modes of a guided wave 908 on the wire including a fundamental mode (e.g., a symmetric mode) and/or a non-fundamental mode (e.g., asymmetric mode).

In the embodiments of 1000″ and 1000′″, for a wire 702 having an insulated outer surface, the guided wave 908 can propagate in part on the outer surface of the insulator and in part inside the insulator. In embodiments, the guided wave 908 can propagate substantially or completely on the outer surface of the insulator, or substantially or completely inside the insulator. In the embodiments of 1000″ and 1000′″, for a wire 702 that is a bare conductor, the guided wave 908 can propagate in part on the outer surface of the conductor and in part inside the conductor. In another embodiment, the guided wave 908 can propagate substantially or completely on the outer surface of the conductor.

Referring now to FIG. 11, a block diagram 1100 illustrating an example, non-limiting embodiment of a dual stub coupler is shown. In particular, a dual coupler design is presented for use in a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1. In an embodiment, two or more couplers (such as the stub couplers 1104 and 1106) can be positioned around a wire 1102 in order to receive guided wave 1108. In an embodiment, one coupler is enough to receive the guided wave 1108. In that case, guided wave 1108 couples to coupler 1104 and propagates as guided wave 1110. If the field structure of the guided wave 1108 oscillates or undulates around the wire 1102 due to the particular guided wave mode(s) or various outside factors, then coupler 1106 can be placed such that guided wave 1108 couples to coupler 1106. In some embodiments, four or more couplers can be placed around a portion of the wire 1102, e.g., at 90 degrees or another spacing with respect to each other, in order to receive guided waves that may oscillate or rotate around the wire 1102, that have been induced at different azimuthal orientations or that have non-fundamental or higher order modes that, for example, have lobes and/or nulls or other asymmetries that are orientation dependent. However, it will be appreciated that there may be less than or more than four couplers placed around a portion of the wire 1102 without departing from example embodiments.

It should be noted that while couplers 1106 and 1104 are illustrated as stub couplers, any other of the coupler designs described herein including arc couplers, antenna or horn couplers, magnetic couplers, etc., could likewise be used. It will also be appreciated that while some example embodiments have presented a plurality of couplers around at least a portion of a wire 1102, this plurality of couplers can also be considered as part of a single coupler system having multiple coupler subcomponents. For example, two or more couplers can be manufactured as single system that can be installed around a wire in a single installation such that the couplers are either pre-positioned or adjustable relative to each other (either manually or automatically with a controllable mechanism such as a motor or other actuator) in accordance with the single system.

Receivers coupled to couplers 1106 and 1104 can use diversity combining to combine signals received from both couplers 1106 and 1104 in order to maximize the signal quality. In other embodiments, if one or the other of the couplers 1104 and 1106 receive a transmission that is above a predetermined threshold, receivers can use selection diversity when deciding which signal to use. Further, while reception by a plurality of couplers 1106 and 1104 is illustrated, transmission by couplers 1106 and 1104 in the same configuration can likewise take place. In particular, a wide range of multi-input multi-output (MIMO) transmission and reception techniques can be employed for transmissions where a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1 includes multiple transceivers and multiple couplers.

It is noted that the graphical representations of waves 1108 and 1110 are presented merely to illustrate the principles that guided wave 1108 induces or otherwise launches a wave 1110 on a coupler 1104. The actual electric and magnetic fields generated as a result of such wave propagation may vary depending on the frequencies employed, the design of the coupler 1104, the dimensions and composition of the wire 1102, as well as its surface characteristics, its insulation if any, the electromagnetic properties of the surrounding environment, etc.

Referring now to FIG. 12, a block diagram 1200 illustrating an example, non-limiting embodiment of a repeater system is shown. In particular, a repeater device 1210 is presented for use in a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1. In this system, two couplers 1204 and 1214 can be placed near a wire 1202 or other transmission medium such that guided waves 1205 propagating along the wire 1202 are extracted by coupler 1204 as wave 1206 (e.g. as a guided wave), and then are boosted or repeated by repeater device 1210 and launched as a wave 1216 (e.g. as a guided wave) onto coupler 1214. The wave 1216 can then be launched on the wire 1202 and continue to propagate along the wire 1202 as a guided wave 1217. In an embodiment, the repeater device 1210 can receive at least a portion of the power utilized for boosting or repeating through magnetic coupling with the wire 1202, for example, when the wire 1202 is a power line or otherwise contains a power-carrying conductor. It should be noted that while couplers 1204 and 1214 are illustrated as stub couplers, any other of the coupler designs described herein including arc couplers, antenna or horn couplers, magnetic couplers, or the like, could likewise be used.

In some embodiments, repeater device 1210 can repeat the transmission associated with wave 1206, and in other embodiments, repeater device 1210 can include a communications interface 205 that extracts data or other signals from the wave 1206 for supplying such data or signals to another network and/or one or more other devices as communication signals 110 or 112 and/or receiving communication signals 110 or 112 from another network and/or one or more other devices and launch guided wave 1216 having embedded therein the received communication signals 110 or 112. In a repeater configuration, receiver waveguide 1208 can receive the wave 1206 from the coupler 1204 and transmitter waveguide 1212 can launch guided wave 1216 onto coupler 1214 as guided wave 1217. Between receiver waveguide 1208 and transmitter waveguide 1212, the signal embedded in guided wave 1206 and/or the guided wave 1216 itself can be amplified to correct for signal loss and other inefficiencies associated with guided wave communications or the signal can be received and processed to extract the data contained therein and regenerated for transmission. In an embodiment, the receiver waveguide 1208 can be configured to extract data from the signal, process the data to correct for data errors utilizing for example error correcting codes, and regenerate an updated signal with the corrected data. The transmitter waveguide 1212 can then transmit guided wave 1216 with the updated signal embedded therein. In an embodiment, a signal embedded in guided wave 1206 can be extracted from the transmission and processed for communication with another network and/or one or more other devices via communications interface 205 as communication signals 110 or 112. Similarly, communication signals 110 or 112 received by the communications interface 205 can be inserted into a transmission of guided wave 1216 that is generated and launched onto coupler 1214 by transmitter waveguide 1212.

It is noted that although FIG. 12 shows guided wave transmissions 1206 and 1216 entering from the left and exiting to the right respectively, this is merely a simplification and is not intended to be limiting. In other embodiments, receiver waveguide 1208 and transmitter waveguide 1212 can also function as transmitters and receivers respectively, allowing the repeater device 1210 to be bi-directional.

In an embodiment, repeater device 1210 can be placed at locations where there are discontinuities or obstacles on the wire 1202 or other transmission medium. In the case where the wire 1202 is a power line, these obstacles can include transformers, connections, utility poles, and other such power line devices. The repeater device 1210 can help the guided (e.g., surface) waves jump over these obstacles on the line and boost the transmission power at the same time. In other embodiments, a coupler can be used to jump over the obstacle without the use of a repeater device. In that embodiment, both ends of the coupler can be tied or fastened to the wire, thus providing a path for the guided wave to travel without being blocked by the obstacle.

Turning now to FIG. 13, illustrated is a block diagram 1300 of an example, non-limiting embodiment of a bidirectional repeater in accordance with various aspects described herein. In particular, a bidirectional repeater device 1306 is presented for use in a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1. It should be noted that while the couplers are illustrated as stub couplers, any other of the coupler designs described herein including arc couplers, antenna or horn couplers, magnetic couplers, or the like, could likewise be used. The bidirectional repeater 1306 can employ diversity paths in the case of when two or more wires or other transmission media are present. Since guided wave transmissions have different transmission efficiencies and coupling efficiencies for transmission medium of different types such as insulated wires, un-insulated wires or other types of transmission media and further, if exposed to the elements, can be affected by weather, and other atmospheric conditions, it can be advantageous to selectively transmit on different transmission media at certain times. In various embodiments, the various transmission media can be designated as a primary, secondary, tertiary, etc. whether or not such designation indicates a preference of one transmission medium over another.

In the embodiment shown, the transmission media include an insulated or uninsulated wire 1302 and an insulated or uninsulated wire 1304 (referred to herein as wires 1302 and 1304, respectively). The repeater device 1306 uses a receiver coupler 1308 to receive a guided wave traveling along wire 1302 and repeats the transmission using transmitter waveguide 1310 as a guided wave along wire 1304. In other embodiments, repeater device 1306 can switch from the wire 1304 to the wire 1302, or can repeat the transmissions along the same paths. Repeater device 1306 can include sensors, or be in communication with sensors (or a network management system 1601 depicted in FIG. 16A) that indicate conditions that can affect the transmission. Based on the feedback received from the sensors, the repeater device 1306 can make the determination about whether to keep the transmission along the same wire, or transfer the transmission to the other wire.

Turning now to FIG. 14, illustrated is a block diagram 1400 illustrating an example, non-limiting embodiment of a bidirectional repeater system. In particular, a bidirectional repeater system is presented for use in a transmission device, such as transmission device 101 or 102 presented in conjunction with FIG. 1. The bidirectional repeater system includes waveguide coupling devices 1402 and 1404 that receive and transmit transmissions from other coupling devices located in a distributed antenna system or backhaul system.

In various embodiments, waveguide coupling device 1402 can receive a transmission from another waveguide coupling device, wherein the transmission has a plurality of subcarriers. Diplexer 1406 can separate the transmission from other transmissions, and direct the transmission to low-noise amplifier (“LNA”) 1408. A frequency mixer 1428, with help from a local oscillator 1412, can downshift the transmission (which is in the millimeter-wave band or around 38 GHz in some embodiments) to a lower frequency, such as a cellular band (˜1.9 GHz) for a distributed antenna system, a native frequency, or other frequency for a backhaul system. An extractor (or demultiplexer) 1432 can extract the signal on a subcarrier and direct the signal to an output component 1422 for optional amplification, buffering or isolation by power amplifier 1424 for coupling to communications interface 205. The communications interface 205 can further process the signals received from the power amplifier 1424 or otherwise transmit such signals over a wireless or wired interface to other devices such as a base station, mobile devices, a building, etc. For the signals that are not being extracted at this location, extractor 1432 can redirect them to another frequency mixer 1436, where the signals are used to modulate a carrier wave generated by local oscillator 1414. The carrier wave, with its subcarriers, is directed to a power amplifier (“PA”) 1416 and is retransmitted by waveguide coupling device 1404 to another system, via diplexer 1420.

An LNA 1426 can be used to amplify, buffer or isolate signals that are received by the communication interface 205 and then send the signal to a multiplexer 1434 which merges the signal with signals that have been received from waveguide coupling device 1404. The signals received from coupling device 1404 have been split by diplexer 1420, and then passed through LNA 1418, and downshifted in frequency by frequency mixer 1438. When the signals are combined by multiplexer 1434, they are upshifted in frequency by frequency mixer 1430, and then boosted by PA 1410, and transmitted to another system by waveguide coupling device 1402. In an embodiment bidirectional repeater system can be merely a repeater without the output device 1422. In this embodiment, the multiplexer 1434 would not be utilized and signals from LNA 1418 would be directed to mixer 1430 as previously described. It will be appreciated that in some embodiments, the bidirectional repeater system could also be implemented using two distinct and separate unidirectional repeaters. In an alternative embodiment, a bidirectional repeater system could also be a booster or otherwise perform retransmissions without downshifting and upshifting. Indeed in example embodiment, the retransmissions can be based upon receiving a signal or guided wave and performing some signal or guided wave processing or reshaping, filtering, and/or amplification, prior to retransmission of the signal or guided wave.

Referring now to FIG. 15, a block diagram 1500 illustrating an example, non-limiting embodiment of a guided wave communications system is shown. This diagram depicts an exemplary environment in which a guided wave communication system, such as the guided wave communication system presented in conjunction with FIG. 1, can be used.

To provide network connectivity to additional base station devices, a backhaul network that links the communication cells (e.g., macrocells and macrocells) to network devices of a core network correspondingly expands. Similarly, to provide network connectivity to a distributed antenna system, an extended communication system that links base station devices and their distributed antennas is desirable. A guided wave communication system 1500 such as shown in FIG. 15 can be provided to enable alternative, increased or additional network connectivity and a waveguide coupling system can be provided to transmit and/or receive guided wave (e.g., surface wave) communications on a transmission medium such as a wire that operates as a single-wire transmission line (e.g., a utility line), and that can be used as a waveguide and/or that otherwise operates to guide the transmission of an electromagnetic wave.

The guided wave communication system 1500 can comprise a first instance of a distribution system 1550 that includes one or more base station devices (e.g., base station device 1504) that are communicably coupled to a central office 1501 and/or a macrocell site 1502. Base station device 1504 can be connected by a wired (e.g., fiber and/or cable), or by a wireless (e.g., microwave wireless) connection to the macrocell site 1502 and the central office 1501. A second instance of the distribution system 1560 can be used to provide wireless voice and data services to mobile device 1522 and to residential and/or commercial establishments 1542 (herein referred to as establishments 1542). System 1500 can have additional instances of the distribution systems 1550 and 1560 for providing voice and/or data services to mobile devices 1522-1524 and establishments 1542 as shown in FIG. 15.

Macrocells such as macrocell site 1502 can have dedicated connections to a mobile network and base station device 1504 or can share and/or otherwise use another connection. Central office 1501 can be used to distribute media content and/or provide internet service provider (ISP) services to mobile devices 1522-1524 and establishments 1542. The central office 1501 can receive media content from a constellation of satellites 1530 (one of which is shown in FIG. 15) or other sources of content, and distribute such content to mobile devices 1522-1524 and establishments 1542 via the first and second instances of the distribution system 1550 and 1560. The central office 1501 can also be communicatively coupled to the Internet 1503 for providing internet data services to mobile devices 1522-1524 and establishments 1542.

Base station device 1504 can be mounted on, or attached to, utility pole 1516. In other embodiments, base station device 1504 can be near transformers and/or other locations situated nearby a power line. Base station device 1504 can facilitate connectivity to a mobile network for mobile devices 1522 and 1524. Antennas 1512 and 1514, mounted on or near utility poles 1518 and 1520, respectively, can receive signals from base station device 1504 and transmit those signals to mobile devices 1522 and 1524 over a much wider area than if the antennas 1512 and 1514 were located at or near base station device 1504.

It is noted that FIG. 15 displays three utility poles, in each instance of the distribution systems 1550 and 1560, with one base station device, for purposes of simplicity. In other embodiments, utility pole 1516 can have more base station devices, and more utility poles with distributed antennas and/or tethered connections to establishments 1542.

A transmission device 1506, such as transmission device 101 or 102 presented in conjunction with FIG. 1, can transmit a signal from base station device 1504 to antennas 1512 and 1514 via utility or power line(s) that connect the utility poles 1516, 1518, and 1520. To transmit the signal, radio source and/or transmission device 1506 upconverts the signal (e.g., via frequency mixing) from base station device 1504 or otherwise converts the signal from the base station device 1504 to a microwave band signal and the transmission device 1506 launches a microwave band wave that propagates as a guided wave traveling along the utility line or other wire as described in previous embodiments. At utility pole 1518, another transmission device 1508 receives the guided wave (and optionally can amplify it as needed or desired or operate as a repeater to receive it and regenerate it) and sends it forward as a guided wave on the utility line or other wire. The transmission device 1508 can also extract a signal from the microwave band guided wave and shift it down in frequency or otherwise convert it to its original cellular band frequency (e.g., 1.9 GHz or other defined cellular frequency) or another cellular (or non-cellular) band frequency. An antenna 1512 can wireless transmit the downshifted signal to mobile device 1522. The process can be repeated by transmission device 1510, antenna 1514 and mobile device 1524, as necessary or desirable.

Transmissions from mobile devices 1522 and 1524 can also be received by antennas 1512 and 1514 respectively. The transmission devices 1508 and 1510 can upshift or otherwise convert the cellular band signals to microwave band and transmit the signals as guided wave (e.g., surface wave or other electromagnetic wave) transmissions over the power line(s) to base station device 1504.

Media content received by the central office 1501 can be supplied to the second instance of the distribution system 1560 via the base station device 1504 for distribution to mobile devices 1522 and establishments 1542. The transmission device 1510 can be tethered to the establishments 1542 by one or more wired connections or a wireless interface. The one or more wired connections may include without limitation, a power line, a coaxial cable, a fiber cable, a twisted pair cable, a guided wave transmission medium or other suitable wired mediums for distribution of media content and/or for providing internet services. In an example embodiment, the wired connections from the transmission device 1510 can be communicatively coupled to one or more very high bit rate digital subscriber line (VDSL) modems located at one or more corresponding service area interfaces (SAIs—not shown) or pedestals, each SAI or pedestal providing services to a portion of the establishments 1542. The VDSL modems can be used to selectively distribute media content and/or provide internet services to gateways (not shown) located in the establishments 1542. The SAIs or pedestals can also be communicatively coupled to the establishments 1542 over a wired medium such as a power line, a coaxial cable, a fiber cable, a twisted pair cable, a guided wave transmission medium or other suitable wired mediums. In other example embodiments, the transmission device 1510 can be communicatively coupled directly to establishments 1542 without intermediate interfaces such as the SAIs or pedestals.

In another example embodiment, system 1500 can employ diversity paths, where two or more utility lines or other wires are strung between the utility poles 1516, 1518, and 1520 (e.g., for example, two or more wires between poles 1516 and 1520) and redundant transmissions from base station/macrocell site 1502 are transmitted as guided waves down the surface of the utility lines or other wires. The utility lines or other wires can be either insulated or uninsulated, and depending on the environmental conditions that cause transmission losses, the coupling devices can selectively receive signals from the insulated or uninsulated utility lines or other wires. The selection can be based on measurements of the signal-to-noise ratio of the wires, or based on determined weather/environmental conditions (e.g., moisture detectors, weather forecasts, etc.). The use of diversity paths with system 1500 can enable alternate routing capabilities, load balancing, increased load handling, concurrent bi-directional or synchronous communications, spread spectrum communications, etc.

It is noted that the use of the transmission devices 1506, 1508, and 1510 in FIG. 15 are by way of example only, and that in other embodiments, other uses are possible. For instance, transmission devices can be used in a backhaul communication system, providing network connectivity to base station devices. Transmission devices 1506, 1508, and 1510 can be used in many circumstances where it is desirable to transmit guided wave communications over a wire, whether insulated or not insulated. Transmission devices 1506, 1508, and 1510 are improvements over other coupling devices due to no contact or limited physical and/or electrical contact with the wires that may carry high voltages. The transmission device can be located away from the wire (e.g., spaced apart from the wire) and/or located on the wire so long as it is not electrically in contact with the wire, as the dielectric acts as an insulator, allowing for cheap, easy, and/or less complex installation. However, as previously noted conducting or non-dielectric couplers can be employed, for example in configurations where the wires correspond to a telephone network, cable television network, broadband data service, fiber optic communications system or other network employing low voltages or having insulated transmission lines.

It is further noted, that while base station device 1504 and macrocell site 1502 are illustrated in an embodiment, other network configurations are likewise possible. For example, devices such as access points or other wireless gateways can be employed in a similar fashion to extend the reach of other networks such as a wireless local area network, a wireless personal area network or other wireless network that operates in accordance with a communication protocol such as a 802.11 protocol, WIMAX protocol, UltraWideband protocol, Bluetooth protocol, Zigbee protocol or other wireless protocol.

Referring now to FIGS. 16A & 16B, block diagrams illustrating an example, non-limiting embodiment of a system for managing a power grid communication system are shown. Considering FIG. 16A, a waveguide system 1602 is presented for use in a guided wave communications system, such as the system presented in conjunction with FIG. 15. The waveguide system 1602 can comprise sensors 1604, a power management system 1605, a transmission device 101 or 102 that includes at least one communication interface 205, transceiver 210 and coupler 220.

The waveguide system 1602 can be coupled to a power line 1610 for facilitating guided wave communications in accordance with embodiments described in the subject disclosure. In an example embodiment, the transmission device 101 or 102 includes coupler 220 for inducing electromagnetic waves on a surface of the power line 1610 that longitudinally propagate along the surface of the power line 1610 as described in the subject disclosure. The transmission device 101 or 102 can also serve as a repeater for retransmitting electromagnetic waves on the same power line 1610 or for routing electromagnetic waves between power lines 1610 as shown in FIGS. 12-13.

The transmission device 101 or 102 includes transceiver 210 configured to, for example, up-convert a signal operating at an original frequency range to electromagnetic waves operating at, exhibiting, or associated with a carrier frequency that propagate along a coupler to induce corresponding guided electromagnetic waves that propagate along a surface of the power line 1610. A carrier frequency can be represented by a center frequency having upper and lower cutoff frequencies that define the bandwidth of the electromagnetic waves. The power line 1610 can be a wire (e.g., single stranded or multi-stranded) having a conducting surface or insulated surface. The transceiver 210 can also receive signals from the coupler 220 and down-convert the electromagnetic waves operating at a carrier frequency to signals at their original frequency.

Signals received by the communications interface 205 of transmission device 101 or 102 for up-conversion can include without limitation signals supplied by a central office 1611 over a wired or wireless interface of the communications interface 205, a base station 1614 over a wired or wireless interface of the communications interface 205, wireless signals transmitted by mobile devices 1620 to the base station 1614 for delivery over the wired or wireless interface of the communications interface 205, signals supplied by in-building communication devices 1618 over the wired or wireless interface of the communications interface 205, and/or wireless signals supplied to the communications interface 205 by mobile devices 1612 roaming in a wireless communication range of the communications interface 205. In embodiments where the waveguide system 1602 functions as a repeater, such as shown in FIGS. 12-13, the communications interface 205 may or may not be included in the waveguide system 1602.

The electromagnetic waves propagating along the surface of the power line 1610 can be modulated and formatted to include packets or frames of data that include a data payload and further include networking information (such as header information for identifying one or more destination waveguide systems 1602). The networking information may be provided by the waveguide system 1602 or an originating device such as the central office 1611, the base station 1614, mobile devices 1620, or in-building devices 1618, or a combination thereof. Additionally, the modulated electromagnetic waves can include error correction data for mitigating signal disturbances. The networking information and error correction data can be used by a destination waveguide system 1602 for detecting transmissions directed to it, and for down-converting and processing with error correction data transmissions that include voice and/or data signals directed to recipient communication devices communicatively coupled to the destination waveguide system 1602.

Referring now to the sensors 1604 of the waveguide system 1602, the sensors 1604 can comprise one or more of a temperature sensor 1604a, a disturbance detection sensor 1604b, a loss of energy sensor 1604c, a noise sensor 1604d, a vibration sensor 1604e, an environmental (e.g., weather) sensor 1604f, and/or an image sensor 1604g. The temperature sensor 1604a can be used to measure ambient temperature, a temperature of the transmission device 101 or 102, a temperature of the power line 1610, temperature differentials (e.g., compared to a setpoint or baseline, between transmission device 101 or 102 and 1610, etc.), or any combination thereof. In one embodiment, temperature metrics can be collected and reported periodically to a network management system 1601 by way of the base station 1614.

The disturbance detection sensor 1604b can perform measurements on the power line 1610 to detect disturbances such as signal reflections, which may indicate a presence of a downstream disturbance that may impede the propagation of electromagnetic waves on the power line 1610. A signal reflection can represent a distortion resulting from, for example, an electromagnetic wave transmitted on the power line 1610 by the transmission device 101 or 102 that reflects in whole or in part back to the transmission device 101 or 102 from a disturbance in the power line 1610 located downstream from the transmission device 101 or 102.

Signal reflections can be caused by obstructions on the power line 1610. For example, a tree limb may cause electromagnetic wave reflections when the tree limb is lying on the power line 1610, or is in close proximity to the power line 1610 which may cause a corona discharge. Other obstructions that can cause electromagnetic wave reflections can include without limitation an object that has been entangled on the power line 1610 (e.g., clothing, a shoe wrapped around a power line 1610 with a shoe string, etc.), a corroded build-up on the power line 1610 or an ice build-up. Power grid components may also impede or obstruct with the propagation of electromagnetic waves on the surface of power lines 1610. Illustrations of power grid components that may cause signal reflections include without limitation a transformer and a joint for connecting spliced power lines. A sharp angle on the power line 1610 may also cause electromagnetic wave reflections.

The disturbance detection sensor 1604b can comprise a circuit to compare magnitudes of electromagnetic wave reflections to magnitudes of original electromagnetic waves transmitted by the transmission device 101 or 102 to determine how much a downstream disturbance in the power line 1610 attenuates transmissions. The disturbance detection sensor 1604b can further comprise a spectral analyzer circuit for performing spectral analysis on the reflected waves. The spectral data generated by the spectral analyzer circuit can be compared with spectral profiles via pattern recognition, an expert system, curve fitting, matched filtering or other artificial intelligence, classification or comparison technique to identify a type of disturbance based on, for example, the spectral profile that most closely matches the spectral data. The spectral profiles can be stored in a memory of the disturbance detection sensor 1604b or may be remotely accessible by the disturbance detection sensor 1604b. The profiles can comprise spectral data that models different disturbances that may be encountered on power lines 1610 to enable the disturbance detection sensor 1604b to identify disturbances locally. An identification of the disturbance if known can be reported to the network management system 1601 by way of the base station 1614. The disturbance detection sensor 1604b can also utilize the transmission device 101 or 102 to transmit electromagnetic waves as test signals to determine a roundtrip time for an electromagnetic wave reflection. The round trip time measured by the disturbance detection sensor 1604b can be used to calculate a distance traveled by the electromagnetic wave up to a point where the reflection takes place, which enables the disturbance detection sensor 1604b to calculate a distance from the transmission device 101 or 102 to the downstream disturbance on the power line 1610.

The distance calculated can be reported to the network management system 1601 by way of the base station 1614. In one embodiment, the location of the waveguide system 1602 on the power line 1610 may be known to the network management system 1601, which the network management system 1601 can utilize to determine a location of the disturbance on the power line 1610 based on a known topology of the power grid. In another embodiment, the waveguide system 1602 can provide its location to the network management system 1601 to assist in the determination of the location of the disturbance on the power line 1610. The location of the waveguide system 1602 can be obtained by the waveguide system 1602 from a pre-programmed location of the waveguide system 1602 stored in a memory of the waveguide system 1602, or the waveguide system 1602 can determine its location using a GPS receiver (not shown) included in the waveguide system 1602.

The power management system 1605 provides energy to the aforementioned components of the waveguide system 1602. The power management system 1605 can receive energy from solar cells, or from a transformer (not shown) coupled to the power line 1610, or by inductive coupling to the power line 1610 or another nearby power line. The power management system 1605 can also include a backup battery and/or a super capacitor or other capacitor circuit for providing the waveguide system 1602 with temporary power. The loss of energy sensor 1604c can be used to detect when the waveguide system 1602 has a loss of power condition and/or the occurrence of some other malfunction. For example, the loss of energy sensor 1604c can detect when there is a loss of power due to defective solar cells, an obstruction on the solar cells that causes them to malfunction, loss of power on the power line 1610, and/or when the backup power system malfunctions due to expiration of a backup battery, or a detectable defect in a super capacitor. When a malfunction and/or loss of power occurs, the loss of energy sensor 1604c can notify the network management system 1601 by way of the base station 1614.

The noise sensor 1604d can be used to measure noise on the power line 1610 that may adversely affect transmission of electromagnetic waves on the power line 1610. The noise sensor 1604d can sense unexpected electromagnetic interference, noise bursts, or other sources of disturbances that may interrupt reception of modulated electromagnetic waves on a surface of a power line 1610. A noise burst can be caused by, for example, a corona discharge, or other source of noise. The noise sensor 1604d can compare the measured noise to a noise profile obtained by the waveguide system 1602 from an internal database of noise profiles or from a remotely located database that stores noise profiles via pattern recognition, an expert system, curve fitting, matched filtering or other artificial intelligence, classification or comparison technique. From the comparison, the noise sensor 1604d may identify a noise source (e.g., corona discharge or otherwise) based on, for example, the noise profile that provides the closest match to the measured noise. The noise sensor 1604d can also detect how noise affects transmissions by measuring transmission metrics such as bit error rate, packet loss rate, jitter, packet retransmission requests, etc. The noise sensor 1604d can report to the network management system 1601 by way of the base station 1614 the identity of noise sources, their time of occurrence, and transmission metrics, among other things.

The vibration sensor 1604e can include accelerometers and/or gyroscopes to detect 2D or 3D vibrations on the power line 1610. The vibrations can be compared to vibration profiles that can be stored locally in the waveguide system 1602, or obtained by the waveguide system 1602 from a remote database via pattern recognition, an expert system, curve fitting, matched filtering or other artificial intelligence, classification or comparison technique. Vibration profiles can be used, for example, to distinguish fallen trees from wind gusts based on, for example, the vibration profile that provides the closest match to the measured vibrations. The results of this analysis can be reported by the vibration sensor 1604e to the network management system 1601 by way of the base station 1614.

The environmental sensor 1604f can include a barometer for measuring atmospheric pressure, ambient temperature (which can be provided by the temperature sensor 1604a), wind speed, humidity, wind direction, and rainfall, among other things. The environmental sensor 1604f can collect raw information and process this information by comparing it to environmental profiles that can be obtained from a memory of the waveguide system 1602 or a remote database to predict weather conditions before they arise via pattern recognition, an expert system, knowledge-based system or other artificial intelligence, classification or other weather modeling and prediction technique. The environmental sensor 1604f can report raw data as well as its analysis to the network management system 1601.

The image sensor 1604g can be a digital camera (e.g., a charged coupled device or CCD imager, infrared camera, etc.) for capturing images in a vicinity of the waveguide system 1602. The image sensor 1604g can include an electromechanical mechanism to control movement (e.g., actual position or focal points/zooms) of the camera for inspecting the power line 1610 from multiple perspectives (e.g., top surface, bottom surface, left surface, right surface and so on). Alternatively, the image sensor 1604g can be designed such that no electromechanical mechanism is needed in order to obtain the multiple perspectives. The collection and retrieval of imaging data generated by the image sensor 1604g can be controlled by the network management system 1601, or can be autonomously collected and reported by the image sensor 1604g to the network management system 1601.

Other sensors that may be suitable for collecting telemetry information associated with the waveguide system 1602 and/or the power lines 1610 for purposes of detecting, predicting and/or mitigating disturbances that can impede the propagation of electromagnetic wave transmissions on power lines 1610 (or any other form of a transmission medium of electromagnetic waves) may be utilized by the waveguide system 1602.

Referring now to FIG. 16B, block diagram 1650 illustrates an example, non-limiting embodiment of a system for managing a power grid 1653 and a communication system 1655 embedded therein or associated therewith in accordance with various aspects described herein. The communication system 1655 comprises a plurality of waveguide systems 1602 coupled to power lines 1610 of the power grid 1653. At least a portion of the waveguide systems 1602 used in the communication system 1655 can be in direct communication with a base station 1614 and/or the network management system 1601. Waveguide systems 1602 not directly connected to a base station 1614 or the network management system 1601 can engage in communication sessions with either a base station 1614 or the network management system 1601 by way of other downstream waveguide systems 1602 connected to a base station 1614 or the network management system 1601.

The network management system 1601 can be communicatively coupled to equipment of a utility company 1652 and equipment of a communications service provider 1654 for providing each entity, status information associated with the power grid 1653 and the communication system 1655, respectively. The network management system 1601, the equipment of the utility company 1652, and the communications service provider 1654 can access communication devices utilized by utility company personnel 1656 and/or communication devices utilized by communications service provider personnel 1658 for purposes of providing status information and/or for directing such personnel in the management of the power grid 1653 and/or communication system 1655.

FIG. 17A illustrates a flow diagram of an example, non-limiting embodiment of a method 1700 for detecting and mitigating disturbances occurring in a communication network of the systems of FIGS. 16A & 16B. Method 1700 can begin with step 1702 where a waveguide system 1602 transmits and receives messages embedded in, or forming part of, modulated electromagnetic waves or another type of electromagnetic waves traveling along a surface of a power line 1610. The messages can be voice messages, streaming video, and/or other data/information exchanged between communication devices communicatively coupled to the communication system 1655. At step 1704 the sensors 1604 of the waveguide system 1602 can collect sensing data. In an embodiment, the sensing data can be collected in step 1704 prior to, during, or after the transmission and/or receipt of messages in step 1702. At step 1706 the waveguide system 1602 (or the sensors 1604 themselves) can determine from the sensing data an actual or predicted occurrence of a disturbance in the communication system 1655 that can affect communications originating from (e.g., transmitted by) or received by the waveguide system 1602. The waveguide system 1602 (or the sensors 1604) can process temperature data, signal reflection data, loss of energy data, noise data, vibration data, environmental data, or any combination thereof to make this determination. The waveguide system 1602 (or the sensors 1604) may also detect, identify, estimate, or predict the source of the disturbance and/or its location in the communication system 1655. If a disturbance is neither detected/identified nor predicted/estimated at step 1708, the waveguide system 1602 can proceed to step 1702 where it continues to transmit and receive messages embedded in, or forming part of, modulated electromagnetic waves traveling along a surface of the power line 1610.

If at step 1708 a disturbance is detected/identified or predicted/estimated to occur, the waveguide system 1602 proceeds to step 1710 to determine if the disturbance adversely affects (or alternatively, is likely to adversely affect or the extent to which it may adversely affect) transmission or reception of messages in the communication system 1655. In one embodiment, a duration threshold and a frequency of occurrence threshold can be used at step 1710 to determine when a disturbance adversely affects communications in the communication system 1655. For illustration purposes only, assume a duration threshold is set to 500 ms, while a frequency of occurrence threshold is set to 5 disturbances occurring in an observation period of 10 sec. Thus, a disturbance having a duration greater than 500 ms will trigger the duration threshold. Additionally, any disturbance occurring more than 5 times in a 10 sec time interval will trigger the frequency of occurrence threshold.

In one embodiment, a disturbance may be considered to adversely affect signal integrity in the communication systems 1655 when the duration threshold alone is exceeded. In another embodiment, a disturbance may be considered as adversely affecting signal integrity in the communication systems 1655 when both the duration threshold and the frequency of occurrence threshold are exceeded. The latter embodiment is thus more conservative than the former embodiment for classifying disturbances that adversely affect signal integrity in the communication system 1655. It will be appreciated that many other algorithms and associated parameters and thresholds can be utilized for step 1710 in accordance with example embodiments.

Referring back to method 1700, if at step 1710 the disturbance detected at step 1708 does not meet the condition for adversely affected communications (e.g., neither exceeds the duration threshold nor the frequency of occurrence threshold), the waveguide system 1602 may proceed to step 1702 and continue processing messages. For instance, if the disturbance detected in step 1708 has a duration of 1 msec with a single occurrence in a 10 sec time period, then neither threshold will be exceeded. Consequently, such a disturbance may be considered as having a nominal effect on signal integrity in the communication system 1655 and thus would not be flagged as a disturbance requiring mitigation. Although not flagged, the occurrence of the disturbance, its time of occurrence, its frequency of occurrence, spectral data, and/or other useful information, may be reported to the network management system 1601 as telemetry data for monitoring purposes.

Referring back to step 1710, if on the other hand the disturbance satisfies the condition for adversely affected communications (e.g., exceeds either or both thresholds), the waveguide system 1602 can proceed to step 1712 and report the incident to the network management system 1601. The report can include raw sensing data collected by the sensors 1604, a description of the disturbance if known by the waveguide system 1602, a time of occurrence of the disturbance, a frequency of occurrence of the disturbance, a location associated with the disturbance, parameters readings such as bit error rate, packet loss rate, retransmission requests, jitter, latency and so on. If the disturbance is based on a prediction by one or more sensors of the waveguide system 1602, the report can include a type of disturbance expected, and if predictable, an expected time occurrence of the disturbance, and an expected frequency of occurrence of the predicted disturbance when the prediction is based on historical sensing data collected by the sensors 1604 of the waveguide system 1602.

At step 1714, the network management system 1601 can determine a mitigation, circumvention, or correction technique, which may include directing the waveguide system 1602 to reroute traffic to circumvent the disturbance if the location of the disturbance can be determined. In one embodiment, the waveguide coupling device 1402 detecting the disturbance may direct a repeater such as the one shown in FIGS. 13-14 to connect the waveguide system 1602 from a primary power line affected by the disturbance to a secondary power line to enable the waveguide system 1602 to reroute traffic to a different transmission medium and avoid the disturbance. In an embodiment where the waveguide system 1602 is configured as a repeater the waveguide system 1602 can itself perform the rerouting of traffic from the primary power line to the secondary power line. It is further noted that for bidirectional communications (e.g., full or half-duplex communications), the repeater can be configured to reroute traffic from the secondary power line back to the primary power line for processing by the waveguide system 1602.

In another embodiment, the waveguide system 1602 can redirect traffic by instructing a first repeater situated upstream of the disturbance and a second repeater situated downstream of the disturbance to redirect traffic from a primary power line temporarily to a secondary power line and back to the primary power line in a manner that avoids the disturbance. It is further noted that for bidirectional communications (e.g., full or half-duplex communications), repeaters can be configured to reroute traffic from the secondary power line back to the primary power line.

To avoid interrupting existing communication sessions occurring on a secondary power line, the network management system 1601 may direct the waveguide system 1602 to instruct repeater(s) to utilize unused time slot(s) and/or frequency band(s) of the secondary power line for redirecting data and/or voice traffic away from the primary power line to circumvent the disturbance.

At step 1716, while traffic is being rerouted to avoid the disturbance, the network management system 1601 can notify equipment of the utility company 1652 and/or equipment of the communications service provider 1654, which in turn may notify personnel of the utility company 1656 and/or personnel of the communications service provider 1658 of the detected disturbance and its location if known. Field personnel from either party can attend to resolving the disturbance at a determined location of the disturbance. Once the disturbance is removed or otherwise mitigated by personnel of the utility company and/or personnel of the communications service provider, such personnel can notify their respective companies and/or the network management system 1601 utilizing field equipment (e.g., a laptop computer, smartphone, etc.) communicatively coupled to network management system 1601, and/or equipment of the utility company and/or the communications service provider. The notification can include a description of how the disturbance was mitigated and any changes to the power lines 1610 that may change a topology of the communication system 1655.

Once the disturbance has been resolved (as determined in decision 1718), the network management system 1601 can direct the waveguide system 1602 at step 1720 to restore the previous routing configuration used by the waveguide system 1602 or route traffic according to a new routing configuration if the restoration strategy used to mitigate the disturbance resulted in a new network topology of the communication system 1655. In another embodiment, the waveguide system 1602 can be configured to monitor mitigation of the disturbance by transmitting test signals on the power line 1610 to determine when the disturbance has been removed. Once the waveguide system 1602 detects an absence of the disturbance it can autonomously restore its routing configuration without assistance by the network management system 1601 if it determines the network topology of the communication system 1655 has not changed, or it can utilize a new routing configuration that adapts to a detected new network topology.

FIG. 17B illustrates a flow diagram of an example, non-limiting embodiment of a method 1750 for detecting and mitigating disturbances occurring in a communication network of the system of FIGS. 16A and 16B. In one embodiment, method 1750 can begin with step 1752 where a network management system 1601 receives from equipment of the utility company 1652 or equipment of the communications service provider 1654 maintenance information associated with a maintenance schedule. The network management system 1601 can at step 1754 identify from the maintenance information, maintenance activities to be performed during the maintenance schedule. From these activities, the network management system 1601 can detect a disturbance resulting from the maintenance (e.g., scheduled replacement of a power line 1610, scheduled replacement of a waveguide system 1602 on the power line 1610, scheduled reconfiguration of power lines 1610 in the power grid 1653, etc.).

In another embodiment, the network management system 1601 can receive at step 1755 telemetry information from one or more waveguide systems 1602. The telemetry information can include among other things an identity of each waveguide system 1602 submitting the telemetry information, measurements taken by sensors 1604 of each waveguide system 1602, information relating to predicted, estimated, or actual disturbances detected by the sensors 1604 of each waveguide system 1602, location information associated with each waveguide system 1602, an estimated location of a detected disturbance, an identification of the disturbance, and so on. The network management system 1601 can determine from the telemetry information a type of disturbance that may be adverse to operations of the waveguide, transmission of the electromagnetic waves along the wire surface, or both. The network management system 1601 can also use telemetry information from multiple waveguide systems 1602 to isolate and identify the disturbance. Additionally, the network management system 1601 can request telemetry information from waveguide systems 1602 in a vicinity of an affected waveguide system 1602 to triangulate a location of the disturbance and/or validate an identification of the disturbance by receiving similar telemetry information from other waveguide systems 1602.

In yet another embodiment, the network management system 1601 can receive at step 1756 an unscheduled activity report from maintenance field personnel. Unscheduled maintenance may occur as result of field calls that are unplanned or as a result of unexpected field issues discovered during field calls or scheduled maintenance activities. The activity report can identify changes to a topology configuration of the power grid 1653 resulting from field personnel addressing discovered issues in the communication system 1655 and/or power grid 1653, changes to one or more waveguide systems 1602 (such as replacement or repair thereof), mitigation of disturbances performed if any, and so on.

At step 1758, the network management system 1601 can determine from reports received according to steps 1752 through 1756 if a disturbance will occur based on a maintenance schedule, or if a disturbance has occurred or is predicted to occur based on telemetry data, or if a disturbance has occurred due to an unplanned maintenance identified in a field activity report. From any of these reports, the network management system 1601 can determine whether a detected or predicted disturbance requires rerouting of traffic by the affected waveguide systems 1602 or other waveguide systems 1602 of the communication system 1655.

When a disturbance is detected or predicted at step 1758, the network management system 1601 can proceed to step 1760 where it can direct one or more waveguide systems 1602 to reroute traffic to circumvent the disturbance. When the disturbance is permanent due to a permanent topology change of the power grid 1653, the network management system 1601 can proceed to step 1770 and skip steps 1762, 1764, 1766, and 1772. At step 1770, the network management system 1601 can direct one or more waveguide systems 1602 to use a new routing configuration that adapts to the new topology. However, when the disturbance has been detected from telemetry information supplied by one or more waveguide systems 1602, the network management system 1601 can notify maintenance personnel of the utility company 1656 or the communications service provider 1658 of a location of the disturbance, a type of disturbance if known, and related information that may be helpful to such personnel to mitigate the disturbance. When a disturbance is expected due to maintenance activities, the network management system 1601 can direct one or more waveguide systems 1602 to reconfigure traffic routes at a given schedule (consistent with the maintenance schedule) to avoid disturbances caused by the maintenance activities during the maintenance schedule.

Returning back to step 1760 and upon its completion, the process can continue with step 1762. At step 1762, the network management system 1601 can monitor when the disturbance(s) have been mitigated by field personnel. Mitigation of a disturbance can be detected at step 1762 by analyzing field reports submitted to the network management system 1601 by field personnel over a communications network (e.g., cellular communication system) utilizing field equipment (e.g., a laptop computer or handheld computer/device). If field personnel have reported that a disturbance has been mitigated, the network management system 1601 can proceed to step 1764 to determine from the field report whether a topology change was required to mitigate the disturbance. A topology change can include rerouting a power line 1610, reconfiguring a waveguide system 1602 to utilize a different power line 1610, otherwise utilizing an alternative link to bypass the disturbance and so on. If a topology change has taken place, the network management system 1601 can direct at step 1770 one or more waveguide systems 1602 to use a new routing configuration that adapts to the new topology.

If, however, a topology change has not been reported by field personnel, the network management system 1601 can proceed to step 1766 where it can direct one or more waveguide systems 1602 to send test signals to test a routing configuration that had been used prior to the detected disturbance(s). Test signals can be sent to affected waveguide systems 1602 in a vicinity of the disturbance. The test signals can be used to determine if signal disturbances (e.g., electromagnetic wave reflections) are detected by any of the waveguide systems 1602. If the test signals confirm that a prior routing configuration is no longer subject to previously detected disturbance(s), then the network management system 1601 can at step 1772 direct the affected waveguide systems 1602 to restore a previous routing configuration. If, however, test signals analyzed by one or more waveguide coupling device 1402 and reported to the network management system 1601 indicate that the disturbance(s) or new disturbance(s) are present, then the network management system 1601 will proceed to step 1768 and report this information to field personnel to further address field issues. The network management system 1601 can in this situation continue to monitor mitigation of the disturbance(s) at step 1762.

In the aforementioned embodiments, the waveguide systems 1602 can be configured to be self-adapting to changes in the power grid 1653 and/or to mitigation of disturbances. That is, one or more affected waveguide systems 1602 can be configured to self-monitor mitigation of disturbances and reconfigure traffic routes without requiring instructions to be sent to them by the network management system 1601. In this embodiment, the one or more waveguide systems 1602 that are self-configurable can inform the network management system 1601 of its routing choices so that the network management system 1601 can maintain a macro-level view of the communication topology of the communication system 1655.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIGS. 17A and 17B, respectively, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Turning now to FIG. 18, a system 1800 is illustrated in which software can be efficiently distributed throughout a network or a targeted portion thereof utilizing network devices 1806. The software can be directed to the network devices 1806 and/or other devices, including customer premises equipment and/or end user devices such as located at residence 1835. System 1800 provides for a de-centralized process that distributes software and/or that locally validates the software being distributed. The distributed software can be any type of software that includes executable instructions. The software can be updates to existing software at the network device, software that is associated with or usable by existing software at the network device, and/or software that is unrelated to software existing at the network device. Many of the examples herein describe a de-centralized process and system for distributing software updates (or patches), however, the exemplary embodiments can be utilized for any type of software that may or may not be an update to software already existing at the network device(s). In one or more embodiments, the distributed software can be used for adjusting operations at the network device(s). The operations being adjusted can vary and can include changing the operation of the operating system at the network device, providing new functions at the network device, adjusting existing functions at the network device, changing communication protocols (e.g., transmitting protocols, security protocols, authentication protocols, encryption protocols, and so forth) utilized by the network device, and so forth.

The communication system 1800 provides for a peer-to-peer (p2p) model where network nodes can be active agents in obtaining or distributing software updates without the necessity of direct communication of updates from a network source. In one embodiment, the network devices 1806 can poll other network device(s), such as located at parent pathway nodes, for information on software update versions to determine whether an update is available and if so, when to install the software update.

In one embodiment, the network devices 1806 can be network nodes that are dynamically organized into a configuration from an update root node down to terminal nodes, and intermediate nodes can act as update servers for child nodes further along the communication path.

In another embodiment, an update management or source server can provide an initial update package (e.g., including desired update(s), upgrade(s), and/or patch(es)) into a targeted network (e.g., providing services to end user devices, m2m, IoT or similar devices) at a designated update root node(s). Various distribution processes can then be implemented. For example, the designated update root node (e.g., network device 1806A) can propagate the software update down or through a tree-like topology to other network devices and other terminal nodes.

In another example, other network node(s) in the network can be selected, either randomly or based on one or more criteria, as a starting point for the P2P distribution of the software update. For instance, the initial drop of the software update can be over a wired network to a selected network device. In another example, the initial drop of the software update can be via a wireless network, such as a cellular network. In another embodiment, multiple initial drop points (e.g., selected network devices) can be utilized. For instance, if the targeted local network is large and/or the software update is urgent, system 1800 can utilize two or more initial drop points (e.g., located at opposing ends of a targeted network), which can then propagate the software update (e.g., to separate sections of the network) and can reduce the overall distribution time to all nodes and/or devices.

In one embodiment, the network can be divided or otherwise categorized into portions to facilitate propagation of the software updates. For example, neighborhoods or sub-networks 1825 (only one of which is shown) can be designated according to a group of network devices 1806 (only four of which are shown) that provide a service area for communication devices located in or otherwise associated with particular areas. The particular network devices 1806 and the resulting service area can be selected based on various factors including one or more of boundaries of a physical neighborhood, premises having common characteristics or interests (e.g., proximity to same stores, attractions, public services, user demographics and so forth), similar infrastructure in a particular area, and so forth. In one embodiment, some or all devices of the group of network devices 1806 can be the closest network nodes that provide communication services to the premises in the designated area, such as a residence 1835. The neighborhood network can provide a contiguous service area or can provide separated sub-service areas that make up the designated area. The premises served by the neighborhood network can include various types of premises including residential houses and/or buildings, commercial stores and facilities, government buildings, public areas and so forth. In a de-centralized fashion, software updates can be propagated, such as at the same or overlapping time period, over multiple designated neighborhood networks 1825. In addition to distributing software updates, system 1800 can be used for various types of communications including voice, video, data and/or messaging.

System 1800 can include network devices 1806 of various numbers (four of which are illustrated) and in various configurations (for ease of illustration being depicted in a straight path). In one embodiment, each of the network devices 1806 can be a network node. In another embodiment, the network devices 1806 can be a plurality of waveguide systems, such as waveguide systems 1806A-1806D. Waveguide systems 1806A-1806D can be nodes of a wired network, which, for example, can include power lines 1802 as a transmission medium. In one embodiment, the waveguide systems 1806A-1806D can enable electromagnetic waves to be received at a physical interface of a transmission medium without utilizing an electrical return path, where the electromagnetic waves are guided by the transmission medium, and where the electromagnetic waves have a non-optical frequency range. The electromagnetic waves can carry or convey various information, such as software updates, authentication information, and so forth. While the communication device(s) illustrated in system 1800 are network devices and, particularly, waveguide systems, one or more of the exemplary embodiments can also include other types of devices coupled with a wired network and/or a wireless network that enable a de-centralized distribution of software updates.

One or more of the waveguide systems 1806A-1806D (or other devices operating as the network devices) can include a processor 1816 that can perform various functions including one or more of authenticating other network devices; receiving and/or transmitting software updates (e.g., without the need to directly receive the software update from a network source server); adjusting operations according to software updates; providing a digital signature to the software update to generate an adjusted software update where the digital signature indicates that the network device has received and/or installed the software update; comparing software updates to determine which software update is to be utilized and/or to be forwarded to another network device(s); transmitting update requests to another network device or to a group of network devices without providing the update request to a network source server that originated the software update; determining a latest version of software updates being stored by other network devices; determining an applicability of the software update to the operations of the particular network device where the adjusting of the operations at the network device is responsive to a determination that the software update is applicable to the operations of the network device; identifying network devices from a group of digital signatures included with a software update; comparing the identified network devices to expected network devices along an expected communication path of the software update; determining a hierarchical configuration of network devices; discarding particular software updates according to a determination that a network device is a parent node and that another network device is a child node; monitoring for an expiration of software operating at the network device; and/or transmitting an update request to another network device responsive to determining that software has expired. In one embodiment, a first non-root node network device can receive a software update from a second-non-root node network device without directly receiving the software update from a root node network device (e.g., a patch drop point in the network).

The processor 1816 can be a separate device in communication with, or otherwise coupled to, the waveguide guide systems 1806A-1806D (as shown with respect to waveguide systems 1806B and 1806D) or can be integrated with the waveguide systems, such as shown with respect to waveguide systems 1806A and 1806C.

In one embodiment, the waveguide system 1806B can be a closest network node to a subset of the group of recipient devices (e.g., a recipient device located at premises 1835) and can deliver information to the premises 1835, as well as deliver the information to a next adjacent node (e.g., third waveguide system 1806C) for further delivery to other devices of the group of recipient devices and/or to other network devices of the neighborhood network 1825.

In one embodiment, waveguide system 1806A can be an edge node of the neighborhood network that receives data including a software update from an external network device 1850 and that determines that the data is to be distributed to other network devices 1806.

Turning now to FIG. 19, system 1900 is illustrated which includes an access network 1918 coupled with a core network 1932 and with a group of network servers 1850 to deliver communication services to customer premises equipment and/or end user devices 1925. Any number of network servers 1850 can be used for providing services that enable peer-to-peer authentication between network devices 1806 in the access network 1918, as well as a de-centralized propagation of software updates throughout the access network and/or to the devices 1925. In one embodiment, the network servers 1850 can be part of the core network 1932. The network devices 1806 can be waveguide systems and/or can be other types of network devices, including routers and/or DSLAMs.

In one embodiment, the network device(s) 1806A can be selected as an initial drop point for distributing a software update 1960 throughout the access network 1918. The selection process can be based on various criteria, including the configuration of the access network 1918, the position of the network device 1806A in a hierarchy of network devices, the capabilities of the network device, the type of software update 1960, and so forth. In another embodiment, the selection of the network device 1806A as the initial drop point can be based on past update distributions. For example, timing performance (e.g., time to complete the distribution to all or some of the network devices) can be monitored for different initial drop points to determine which network drop point(s) most effectively and efficiently previously distributed software updates. The network server 1850 can provide the network device 1806A the software update 1960 utilizing wireless and/or wired communications.

In one embodiment, system 1900 can transmit the software update 1960 in a store-and-forward model between peer nodes (e.g., the network devices 1806) that are mutually authenticating each other. The initial drop node (e.g., network device 1806A) can propagate the software update 1960 it to its neighbor node(s), each of the network nodes applying the software update as appropriate (given that some software updates might not apply to all devices, but only to some types thereof) and then forwarding the software update to the next adjacent node(s). The software update 1960 can be transmitted from node to node (e.g., from network device 1806A to network device(s) 1806B to network device(s) 1806B and so on), in a peer-to-peer communication and viral-type fashion without needing to directly receive the software update from the source originating it (e.g., network server 1850) and/or without communicating with the source (e.g., without transmitting a receipt acknowledgement to the network server 1850). In one embodiment, each of the network devices 1806 can authenticate each other with mutual authentication thereby preventing or reducing sending/receiving software updates to/from a possibly malicious or compromised node.

In another embodiment, system 1900 can implement an update ready check. For example, each or some of the network nodes (e.g., network devices 1806) can maintain a version list of update histories, such as to support roll backs. Software update versions can have a date of issue and/or a date of expiry. When a network device 1806 determines that its current software version is expired, the network device can initiate an update. In one embodiment, a network device can, independent of or prior to version expiry, periodically poll other network devices, such as at parent nodes (all or some), for their current version number (or other information that indicates the identity of the version being utilized at the other network device). In some instances, such as where a local network is large and parent pathways are long, an upper limit on the hierarchy tree can be utilized. For example, each network device 1806B may only check the status of a maximum number of network devices located at parent network nodes before validating a software update. If a number of network devices 1806 at the parent nodes (e.g., satisfying a threshold) have a more up-to-date version of the software update 1960 then the current network device can request the software update (e.g., from one of the polled network devices at the parent nodes) and can trigger an update during the next maintenance window.

In another embodiment, system 1900 can implement an update check. For example, network devices can validate the source of the software update 1960 by authenticating the network devices at parent node(s) that the software update was received from. As a software update 1960 is transmitted from the network server 1850 through a path of network nodes (where the network devices are located), each network device can digitally sign (or otherwise provide an indication that the network device has received the software update) the update package. Before installing the software update 1960, a network device can validate the digital signatures of all the network devices on the path, such as based on a comparison to a list of expected network devices along the path. In one embodiment, any software update that fails these tests can be discarded. The software update package can be digitally signed, and receiving devices can check the signature, so tampering for all software update packages can be detected without delay, and tampered or forged software updates can be removed.

In another embodiment, system 1900 can implement conflict prevention. For example, network devices can have alternate means of receiving software updates. For instance, a single network node may have redundancy within the network either through another path way to a different node, to be used in the event of a failure, or through a separate transport mechanism. Examples can include out of band management pathways and/or the mobility network. In this embodiment, a network device can validate multiple paths to different update root nodes from which the software update is being received. In one embodiment, one pathway can be designated as a parent pathway by a priority selection process. In the event of a failure on the parent pathway, an alternate pathway to the update root node can be selected. In this example, a network device that has received a software update from an alternate path can communicate the existence of the software update to all its parent nodes, triggering a query by each parent node for an updated software version. In one embodiment, to prevent update loops, where a network device receives information about a software update from both parent and child nodes, the software update file may only be accepted from the parent pathway. In the event that a network node fails on a parent pathway, and a secondary pathway exists, then if that secondary path leads to a parent node earlier in the path it can be selected. Continuing with this example, the software update can then be received from the immediate parent node on the alternate pathway. When the primary pathway is restored, a child node may have a more current version of the software update than its parent nodes. The child node (or another node along the path) can then trigger an update request to all the nodes on the parent pathway, which can then start the process of obtaining the most up-to-date version of the software update.

Various authentication methods can be used as part of the de-centralized distribution of software updates. In one embodiment, waveguide system 1806A (e.g., operating as an edge element or update root node) can be validated (e.g., by another waveguide system or a network server) according to an identification in an inventory database and/or an association with a specific network modification request. In another embodiment, waveguide system 1806B (e.g., operating as a non-edge element or a non-update root node) can be validated (e.g., by another waveguide system or a network server) according to an identification in an inventory database, being mapped to a valid location in the topology of its corresponding root node (waveguide system operating as an edge element), and/or having a specific upstream waveguide system which can be an edge element or a non-edge element. As an example, component services can be implemented by network servers 1850, including an inventory service, a deployment service, and a modification management service that can be utilized for this validation process.

In one embodiment, whenever customers are added to the communication services provided via system 1900, they are introduced as terminal nodes at the end of the transport pathway that are provided via the non-edge waveguide systems. In one embodiment, a terminal node can be user equipment as in an LTE use case, or can be a modem supporting a home network, cable, or voice services. Other security protocols can be implemented to prevent bogus clients joining the network by confirming identity using existing protocols, such as LTE or DOCSIS3.0 AAA protocols, and/or querying a customer profile service before allowing registration.

In one or more embodiments, peer-to-peer authentication between network devices can be performed, such as described in U.S. application Ser. No. 14/737,983, the disclosure of which is hereby incorporated by reference.

The example of system 1900 describes particular components and examples of handshake protocols, however, the peer-to-peer authentication being utilized or a portion thereof can be extended to other transport networks. Further, a subset of the exemplary protocols can be used and other protocols and components, based on the underlying transport technology specifics, can also be utilized with the exemplary embodiments.

Turning now to FIG. 20, a flow diagram of an example, non-limiting embodiment of a method 2000, is shown. In particular, a method is presented for use with one or more functions and features presented in conjunction with FIGS. 1-19. Method 2000 enables distributing software updates in a de-centralized process. Systems 1800 and 1900 of FIGS. 18, 19 are described with respect to waveguide systems and method 2000 can be performed in conjunction with these systems. However, one or more embodiments of method 2000 (including all or some of the features described herein) can be performed using other types of network components and/or other architectures including in a wired network and/or a wireless network. Method 2000 is described as being performed by one or more network devices.

At 2005, a network device operating as a node of a network can receive data of various types, including voice, video, and/or messaging. The data can include a software update. In one embodiment, the network device can be operating as a non-edge node and the data can be received from an adjacent network node, such as along a path extending from or to an edge node (or update root node). In another embodiment, the network device can be operating as an edge node and the data can be received from an external network device positioned outside of the neighborhood network.

At 2010, the network device can determine if the received software update is a valid update. In one embodiment, the network device can perform authentication, such as mutual authentication, with the network device that transmitted the software update (e.g., an adjacent network node). In one embodiment, the network device can detect or otherwise identify digital signature(s) or other indicia that are provided with the software update. The digital signatures can be provided by other network devices that have received and forwarded the software update. In this example, the network device can compare these identified network devices with expected network devices that should have been along the communication path.

In the event that a software update is determined to be invalid then at 2015 the software update can be discarded or otherwise flagged as invalid. In one embodiment, a notification can be generated and transmitted to other network devices and/or to a network server so that further investigation or actions can be performed with respect to the invalid software update.

If on the other hand, the software update is determined to be valid then at 2020 the software update can be implemented or otherwise installed at the network device, so as to adjust operations of the network device. In one embodiment, the network device can determine whether the software update is applicable to the particular network device. For example, the software update can be directed to particular types of network devices but not to other types. In another example, the network device may already be updated with the received software update and/or may have a more up-to-date version of the software.

At 2025, the network device can provide a digital signature or other indicia that indicates that the network device has received the software update. In one embodiment, the digital signature or other indicia can indicate whether or not the transmitting network device implemented the software update. The added digital signature can then be utilized by a receiving network device to validate the software update. At 2030, the software update can be transmitted by the network device to one or more other network devices, such as adjacent network node(s).

In one embodiment, the network devices can be waveguide systems that transmit and receive electromagnetic waves at a physical interface of a transmission medium, wherein the electromagnetic waves are guided by the transmission medium without utilizing an electrical return path, wherein the electromagnetic waves have a non-optical frequency range, and wherein the authentication information, the software update and/or the adjusted software update are conveyed via the electromagnetic waves. In another embodiment, multiple software updates can be received by a network device from multiple other network devices (e.g., along a single communication path or along several communication paths). In this example, the software updates can be compared and the latest version of the software update can be utilized. In one embodiment, a first network device, responsive to determining that a software update received from a second network device is out-of-date or not the latest version, can notify the second network device of the existence of (or provide to the second network device) the more-up-to-date version of the software update.

In one embodiment, the network device can transmit an update request to one network device or to a group of network devices, where the transmitting of the update request does not include providing the update request to a network source server that originated the software update. In this example, the network device can determine a latest version of the software update being stored by each of the group of network device and can then obtain that latest version from the particular network device. In one embodiment, the network device can determine a hierarchical configuration of other network devices and can discard particular software updates according to a determination as to whether the update was received from a parent node (e.g., keep the update) or a child node (discard the update). In one embodiment, the network device can monitor for an expiration of software operating at the network device, and, responsive to a determination that the software has expired, transmit an update request to another network device, where the transmitting of the update request does not include providing the update request to a network source server that originated the software update,

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 20, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

In one embodiment, each network device can maintain a ‘last known good configuration’. In order to prevent update flapping, roll backs can require additional validation that the current update has been fixed before a reinstall is initiated. In one embodiment, if multiple updates are available, a protocol can be used to check the types of each update. If a series of updates is required to be applied in order, the network device can do so. If a fresh update replaces all prior updates, the earlier updates can be discarded unless needed for a ‘last known good configuration’.

In one embodiment, even when an update package is correctly received by a network device, and its integrity is verified (e.g., via digital signatures), more checking can be performed to assure upgrade-only patching, so the device goes to the most recent version, and not to an older patch which might actually re-instate a vulnerability. An increasing release number can be associated with each software update and checked by each receiving network device. In one embodiment, for emergency situations when reverting to a slightly older version is actually required in operation, the update can have a new, increased version number, to facilitate checking.

In one embodiment, accounting for differences in actual hardware can be performed. For example, software updates may not apply to network devices on a parent path if the network devices are manufactured by different vendors or if the actual hardware is not certified for the update. All network devices can still support the update protocols so that they can communicate updates downstream. In heterogeneous environments, network devices can apply a majority controls polling rule to account for this possibility.

In one embodiment, gold standard auditing can be performed. For example, all the nodes in the network can be polled on their current configuration to ensure that they are indeed compliant with current versions and configuration parameters. Deviations from a gold standard can be reported to system logs and can generate alerts. In one embodiment, transaction-based processing of updates can be performed. For example, update operations can be transactional (e.g., either the full update installation is completed, or none of it is installed). If an update fails, the network device can roll back to a valid state and/or can return to an active state.

In one embodiment, patch propagation for non-like devices communicating to pass along the update can be performed. For example, a local IoT network can comprise devices of different types, (e.g., in a smart home, there are many types of appliances and devices that communicate with one another). A new software update can be for a specific type of device, and not apply to other types. In this example, the software update can include an indicator that specifies the type of device(s) it targets. After the initial drop, the receiving network device can inspect the indicator, and then pass the software update along to network devices that can use it. This can be implemented through device self-awareness and the receiving network device also knows the device type of its neighbors. When receiving a software update, the receiving network device can compare the patch's applicable device type indicator with the known types of its downstream network devices, and then can send the patch to applicable devices only. This example can save propagation time and resources. Devices that are along a required path and that receive non-applicable software updates for relaying them further down still save processing time as they only need to inspect the patch indicator, but not the entire software update.

In one embodiment, the exemplary systems and methods can reduce network usage along with dependency on centralized update management. The distributed update management of the exemplary embodiments can support self-healing and self-managing networks that are more robust in the face of failure and that can propagate corrections through the network automatically. For example, the exemplary embodiments can reduce wide area network usage. For instance, large updates can be sent only once—from the central server to the drop node(s)—instead of to each node individually. This cuts down significantly the Wide Area Network (WAN) communications, saving WAN bandwidth (which is typically lower than local capacity). The exemplary embodiments can reduce the load on central servers from communication and processing. For example, the central servers do not need to communicate with each network device, thereby reducing their communication load. Also there is no need to receive and process responses from all network devices, thereby reducing processing load for the central servers.

Referring now to FIG. 21, there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. In order to provide additional context for various embodiments of the embodiments described herein, FIG. 21 and the following discussion are intended to provide a brief, general description of a suitable computing environment 2100 in which the various embodiments of the subject disclosure can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

As used herein, a processing circuit includes processor as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.

The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and doesn't otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which can comprise computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 21, the example environment 2100 for transmitting and receiving signals via or forming at least part of a base station (e.g., base station devices 1504, macrocell site 1502, or base stations 1614) or central office (e.g., central office 1501 or 1611). At least a portion of the example environment 2100 can also be used for transmission devices 101 or 102. The example environment can comprise a computer 2102, the computer 2102 comprising a processing unit 2104, a system memory 2106 and a system bus 2108. The system bus 2108 couples system components including, but not limited to, the system memory 2106 to the processing unit 2104. The processing unit 2104 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 2104.

The system bus 2108 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 2106 comprises ROM 2110 and RAM 2112. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 2102, such as during startup. The RAM 2112 can also comprise a high-speed RAM such as static RAM for caching data.

The computer 2102 further comprises an internal hard disk drive (HDD) 2114 (e.g., EIDE, SATA), which internal hard disk drive 2114 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 2116, (e.g., to read from or write to a removable diskette 2118) and an optical disk drive 2120, (e.g., reading a CD-ROM disk 2122 or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive 2114, magnetic disk drive 2116 and optical disk drive 2120 can be connected to the system bus 2108 by a hard disk drive interface 2124, a magnetic disk drive interface 2126 and an optical drive interface 2128, respectively. The interface 2124 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 2102, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 2112, comprising an operating system 2130, one or more application programs 2132, other program modules 2134 and program data 2136. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 2112. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems. Examples of application programs 2132 that can be implemented and otherwise executed by processing unit 2104 include the diversity selection determining performed by transmission device 101 or 102.

A user can enter commands and information into the computer 2102 through one or more wired/wireless input devices, e.g., a keyboard 2138 and a pointing device, such as a mouse 2140. Other input devices (not shown) can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 2104 through an input device interface 2142 that can be coupled to the system bus 2108, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor 2144 or other type of display device can be also connected to the system bus 2108 via an interface, such as a video adapter 2146. It will also be appreciated that in alternative embodiments, a monitor 2144 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 2102 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 2144, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 2102 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 2148. The remote computer(s) 2148 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 2102, although, for purposes of brevity, only a memory/storage device 2150 is illustrated. The logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 2152 and/or larger networks, e.g., a wide area network (WAN) 2154. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 2102 can be connected to the local network 2152 through a wired and/or wireless communication network interface or adapter 2156. The adapter 2156 can facilitate wired or wireless communication to the LAN 2152, which can also comprise a wireless AP disposed thereon for communicating with the wireless adapter 2156.

When used in a WAN networking environment, the computer 2102 can comprise a modem 2158 or can be connected to a communications server on the WAN 2154 or has other means for establishing communications over the WAN 2154, such as by way of the Internet. The modem 2158, which can be internal or external and a wired or wireless device, can be connected to the system bus 2108 via the input device interface 2142. In a networked environment, program modules depicted relative to the computer 2102 or portions thereof, can be stored in the remote memory/storage device 2150. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer 2102 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.

FIG. 22 presents an example embodiment 2200 of a mobile network platform 2210 that can implement and exploit one or more aspects of the disclosed subject matter described herein. In one or more embodiments, the mobile network platform 2210 can generate and receive signals transmitted and received by base stations (e.g., base station devices 1504, macrocell site 1502, or base stations 1614), central office (e.g., central office 1501 or 1611), or transmission device 101 or 102 associated with the disclosed subject matter. Generally, wireless network platform 2210 can comprise components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, wireless network platform 2210 can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform 2210 comprises CS gateway node(s) 2222 which can interface CS traffic received from legacy networks like telephony network(s) 2240 (e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network 2270. Circuit switched gateway node(s) 2222 can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s) 2222 can access mobility, or roaming, data generated through SS7 network 2270; for instance, mobility data stored in a visited location register (VLR), which can reside in memory 2230. Moreover, CS gateway node(s) 2222 interfaces CS-based traffic and signaling and PS gateway node(s) 2218. As an example, in a 3GPP UMTS network, CS gateway node(s) 2222 can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s) 2222, PS gateway node(s) 2218, and serving node(s) 2216, is provided and dictated by radio technology(ies) utilized by mobile network platform 2210 for telecommunication.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) 2218 can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can comprise traffic, or content(s), exchanged with networks external to the wireless network platform 2210, like wide area network(s) (WANs) 2250, enterprise network(s) 2270, and service network(s) 2280, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform 2210 through PS gateway node(s) 2218. It is to be noted that WANs 2250 and enterprise network(s) 2260 can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s) 2217, packet-switched gateway node(s) 2218 can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s) 2218 can comprise a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment 2200, wireless network platform 2210 also comprises serving node(s) 2216 that, based upon available radio technology layer(s) within technology resource(s) 2217, convey the various packetized flows of data streams received through PS gateway node(s) 2218. It is to be noted that for technology resource(s) 2217 that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s) 2218; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s) 2216 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s) 2214 in wireless network platform 2210 can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can comprise add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by wireless network platform 2210. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s) 2218 for authorization/authentication and initiation of a data session, and to serving node(s) 2216 for communication thereafter. In addition to application server, server(s) 2214 can comprise utility server(s), a utility server can comprise a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through wireless network platform 2210 to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) 2222 and PS gateway node(s) 2218 can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN 2250 or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to wireless network platform 2210 (e.g., deployed and operated by the same service provider), such as the distributed antennas networks shown in FIG. 1(s) that enhance wireless service coverage by providing more network coverage. Repeater devices such as those shown in FIGS. 7, 8, and 9 also improve network coverage in order to enhance subscriber service experience by way of UE 2275.

It is to be noted that server(s) 2214 can comprise one or more processors configured to confer at least in part the functionality of macro network platform 2210. To that end, the one or more processor can execute code instructions stored in memory 2230, for example. It is should be appreciated that server(s) 2214 can comprise a content manager 2215, which operates in substantially the same manner as described hereinbefore.

In example embodiment 2200, memory 2230 can store information related to operation of wireless network platform 2210. Other operational information can comprise provisioning information of mobile devices served through wireless platform network 2210, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory 2230 can also store information from at least one of telephony network(s) 2240, WAN 2250, enterprise network(s) 2270, or SS7 network 2260. In an aspect, memory 2230 can be, for example, accessed as part of a data store component or as a remotely connected memory store.

In order to provide a context for the various aspects of the disclosed subject matter, FIG. 22, and the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the disclosed subject matter also can be implemented in combination with other program modules. Generally, program modules comprise routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

FIG. 23 depicts an illustrative embodiment of a communication device 2300. The communication device 2300 can serve as an illustrative embodiment of devices such as mobile devices and in-building devices referred to by the subject disclosure (e.g., in FIGS. 15, 16A and 16B).

The communication device 2300 can comprise a wireline and/or wireless transceiver 2302 (herein transceiver 2302), a user interface (UI) 2304, a power supply 2314, a location receiver 2316, a motion sensor 2318, an orientation sensor 2320, and a controller 2306 for managing operations thereof. The transceiver 2302 can support short-range or long-range wireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, or cellular communication technologies, just to mention a few (Bluetooth® and ZigBee® are trademarks registered by the Bluetooth® Special Interest Group and the ZigBee® Alliance, respectively). Cellular technologies can include, for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise. The transceiver 2302 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 2304 can include a depressible or touch-sensitive keypad 2308 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 2300. The keypad 2308 can be an integral part of a housing assembly of the communication device 2300 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®. The keypad 2308 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 2304 can further include a display 2310 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 2300. In an embodiment where the display 2310 is touch-sensitive, a portion or all of the keypad 2308 can be presented by way of the display 2310 with navigation features.

The display 2310 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 2300 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The touch screen display 2310 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 2310 can be an integral part of the housing assembly of the communication device 2300 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.

The UI 2304 can also include an audio system 2312 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 2312 can further include a microphone for receiving audible signals of an end user. The audio system 2312 can also be used for voice recognition applications. The UI 2304 can further include an image sensor 2313 such as a charged coupled device (CCD) camera for capturing still or moving images.

The power supply 2314 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 2300 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.

The location receiver 2316 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 2300 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 2318 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 2300 in three-dimensional space. The orientation sensor 2320 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 2300 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).

The communication device 2300 can use the transceiver 2302 to also determine a proximity to a cellular, WiFi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 2306 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 2300.

Other components not shown in FIG. 23 can be used in one or more embodiments of the subject disclosure. For instance, the communication device 2300 can include a slot for adding or removing an identity module such as a Subscriber Identity Module (SIM) card or Universal Integrated Circuit Card (UICC). SIM or UICC cards can be used for identifying subscriber services, executing programs, storing subscriber data, and so on.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can comprise random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Some of the embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. For example, artificial intelligence can be used in optional training controller 230 evaluate and select candidate frequencies, modulation schemes, MIMO modes, and/or guided wave modes in order to maximize transfer efficiency. The embodiments (e.g., in connection with automatically identifying acquired cell sites that provide a maximum value/benefit after addition to an existing communication network) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of the each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence (class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to a predetermined criteria which of the acquired cell sites will benefit a maximum number of subscribers and/or which of the acquired cell sites will add minimum value to the existing communication network coverage, etc.

As used in some contexts in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.

Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Moreover, terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used herein, terms such as “data storage,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.

What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via one or more intervening items. Such items and intervening items include, but are not limited to, junctions, communication paths, components, circuit elements, circuits, functional blocks, and/or devices. As an example of indirect coupling, a signal conveyed from a first item to a second item may be modified by one or more intervening items by modifying the form, nature or format of information in a signal, while one or more elements of the information in the signal are nevertheless conveyed in a manner than can be recognized by the second item. In a further example of indirect coupling, an action in a first item can cause a reaction on the second item, as a result of actions and/or reactions in one or more intervening items.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement which achieves the same or similar purpose may be substituted for the embodiments described or shown by the subject disclosure. The subject disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure. For instance, one or more features from one or more embodiments can be combined with one or more features of one or more other embodiments. In one or more embodiments, features that are positively recited can also be negatively recited and excluded from the embodiment with or without replacement by another structural and/or functional feature. The steps or functions described with respect to the embodiments of the subject disclosure can be performed in any order. The steps or functions described with respect to the embodiments of the subject disclosure can be performed alone or in combination with other steps or functions of the subject disclosure, as well as from other embodiments or from other steps that have not been described in the subject disclosure. Further, more than or less than all of the features described with respect to an embodiment can also be utilized.

Number	Name	Date	Kind
2685068	Goubau	Jul 1954	A
2852753	Walter et al.	Sep 1958	A
2867776	Wilkinson, Jr.	Jan 1959	A
2912695	Cutler	Nov 1959	A
2921277	Goubau	Jan 1960	A
3201724	Hafner	Aug 1965	A
3566317	Hafner	Feb 1971	A
5889449	Fiedziuszko	Mar 1999	A
6239377	Nishikawa et al.	May 2001	B1
6839846	Mangold et al.	Jan 2005	B2
7009471	Elmore	Mar 2006	B2
7043271	Seto et al.	May 2006	B1
7055148	Marsh et al.	May 2006	B2
7280033	Berkman et al.	Oct 2007	B2
7345623	McEwan et al.	Mar 2008	B2
7567154	Elmore	Jul 2009	B2
7584470	Barker et al.	Sep 2009	B2
7590404	Johnson et al.	Sep 2009	B1
7716660	Mackay et al.	May 2010	B2
7734717	Saarimäki et al.	Jun 2010	B2
7937699	Schneider et al.	May 2011	B2
8159385	Farneth et al.	Apr 2012	B2
8212635	Miller, II et al.	Jul 2012	B2
8237617	Johnson et al.	Aug 2012	B1
8253516	Miller, II et al.	Aug 2012	B2
8269583	Miller, II et al.	Sep 2012	B2
8316364	Stein et al.	Nov 2012	B2
8344829	Miller et al.	Jan 2013	B2
8407687	Moshir et al.	Mar 2013	B2
8516470	Joshi et al.	Aug 2013	B1
8516474	Lamba et al.	Aug 2013	B2
8736502	Mehr et al.	May 2014	B1
8782195	Foti	Jul 2014	B2
8897697	Bennett et al.	Nov 2014	B1
8984113	Li et al.	Mar 2015	B2
9094407	Matthieu	Jul 2015	B1
9113347	Henry	Aug 2015	B2
9209902	Willis, III et al.	Dec 2015	B2
9312919	Barzegar et al.	Apr 2016	B1
9461706	Bennett et al.	Oct 2016	B1
9490869	Henry	Nov 2016	B1
9509415	Henry et al.	Nov 2016	B1
9520945	Gerszberg et al.	Dec 2016	B2
9525524	Barzegar et al.	Dec 2016	B2
9544006	Henry et al.	Jan 2017	B2
9564947	Stuckman et al.	Feb 2017	B2
9577306	Willis, III et al.	Feb 2017	B2
9608692	Willis, III et al.	Mar 2017	B2
9608740	Henry et al.	Mar 2017	B2
9615269	Henry et al.	Apr 2017	B2
9627768	Henry et al.	Apr 2017	B2
9628116	Willis, III et al.	Apr 2017	B2
9640850	Henry et al.	May 2017	B2
9653770	Henry et al.	May 2017	B2
9680670	Henry et al.	Jun 2017	B2
9692101	Henry et al.	Jun 2017	B2
9705561	Henry et al.	Jul 2017	B2
9705571	Gerszberg et al.	Jul 2017	B2
9742462	Bennett et al.	Aug 2017	B2
9748626	Henry et al.	Aug 2017	B2
9749053	Henry et al.	Aug 2017	B2
9722318	Adriazola et al.	Sep 2017	B2
9768833	Fuchs et al.	Sep 2017	B2
9769020	Henry et al.	Sep 2017	B2
9780834	Henry et al.	Oct 2017	B2
9793951	Henry et al.	Oct 2017	B2
9793954	Bennett et al.	Oct 2017	B2
9847566	Henry et al.	Dec 2017	B2
9853342	Henry et al.	Dec 2017	B2
9860075	Gerszberg et al.	Jan 2018	B1
9865911	Henry et al.	Jan 2018	B2
9866309	Bennett et al.	Jan 2018	B2
9871282	Henry et al.	Jan 2018	B2
9871283	Henry et al.	Jan 2018	B2
9876264	Barnickel et al.	Jan 2018	B2
9876570	Henry et al.	Jan 2018	B2
9876605	Henry et al.	Jan 2018	B1
9882257	Henry et al.	Jan 2018	B2
9893795	Willis et al.	Feb 2018	B1
9912381	Bennett et al.	Mar 2018	B2
9917341	Henry et al.	Mar 2018	B2
9991580	Henry et al.	Jun 2018	B2
9997819	Bennett et al.	Jun 2018	B2
9998172	Barzegar et al.	Jun 2018	B1
9998870	Bennett et al.	Jun 2018	B1
9999038	Barzegar et al.	Jun 2018	B2
10003364	Willis, III et al.	Jun 2018	B1
10009063	Gerszberg et al.	Jun 2018	B2
10009065	Henry et al.	Jun 2018	B2
10009901	Gerszberg	Jun 2018	B2
10027397	Kim	Jul 2018	B2
10027427	Vannucci et al.	Jul 2018	B2
10033107	Henry et al.	Jul 2018	B2
10033108	Henry et al.	Jul 2018	B2
10044409	Barzegar et al.	Aug 2018	B2
10051483	Barzegar et al.	Aug 2018	B2
10051488	Vannucci et al.	Aug 2018	B1
10062970	Vannucci et al.	Aug 2018	B1
20020091807	Goodman et al.	Jul 2002	A1
20020197979	Vanderveen	Dec 2002	A1
20040113756	Mollenkopf et al.	Jun 2004	A1
20050042989	Ho et al.	Feb 2005	A1
20050258920	Elmore et al.	Nov 2005	A1
20070226779	Yokomitsu et al.	Sep 2007	A1
20080064331	Washiro	Mar 2008	A1
20080130639	Costa-Requena et al.	Jun 2008	A1
20080133922	William	Jun 2008	A1
20080211727	Elmore et al.	Sep 2008	A1
20080252541	Diaz et al.	Oct 2008	A1
20090079660	Elmore et al.	Mar 2009	A1
20090258652	Lambert et al.	Oct 2009	A1
20100225426	Unger et al.	Sep 2010	A1
20100277003	Von Novak et al.	Nov 2010	A1
20110110404	Washiro	May 2011	A1
20110132658	Miller, II et al.	Jun 2011	A1
20110187578	Farneth et al.	Aug 2011	A1
20130064311	Turner et al.	Mar 2013	A1
20130326494	Nunez et al.	Dec 2013	A1
20140007076	Kim et al.	Jan 2014	A1
20140189677	Curzi et al.	Jul 2014	A1
20140207844	Mayo et al.	Jul 2014	A1
20140285277	Herbsommer et al.	Sep 2014	A1
20140317229	Hughes et al.	Oct 2014	A1
20150099555	Krishnaswamy et al.	Apr 2015	A1
20150156266	Gupta	Jun 2015	A1
20150195349	Cardamore	Jul 2015	A1
20160080839	Fuchs et al.	Mar 2016	A1
20160112093	Barzegar	Apr 2016	A1
20160164571	Bennett et al.	Jun 2016	A1
20160182096	Panioukov et al.	Jun 2016	A1
20160315662	Henry	Oct 2016	A1
20160359541	Bennett	Dec 2016	A1
20160359546	Bennett	Dec 2016	A1
20160359547	Bennett et al.	Dec 2016	A1
20160360533	Bennett et al.	Dec 2016	A1
20160365966	Bennett et al.	Dec 2016	A1
20170012667	Bennett	Jan 2017	A1
20170018856	Henry et al.	Jan 2017	A1
20170033465	Henry et al.	Feb 2017	A1
20170033953	Henry et al.	Feb 2017	A1
20170033954	Henry et al.	Feb 2017	A1
20170075677	Gross et al.	Mar 2017	A1
20170079037	Gerszberg et al.	Mar 2017	A1
20170079038	Gerszberg et al.	Mar 2017	A1
20170079039	Gerszberg et al.	Mar 2017	A1
20170085003	Johnson et al.	Mar 2017	A1
20170093693	Barzegar et al.	Mar 2017	A1
20170110795	Henry	Apr 2017	A1
20170110804	Henry et al.	Apr 2017	A1
20170229782	Adriazola et al.	Aug 2017	A1
20180048497	Henry et al.	Feb 2018	A1
20180054232	Henry et al.	Feb 2018	A1
20180054233	Henry et al.	Feb 2018	A1
20180054234	Stuckman et al.	Feb 2018	A1
20180062886	Paul et al.	Mar 2018	A1
20180069594	Henry et al.	Mar 2018	A1
20180069731	Henry et al.	Mar 2018	A1
20180076982	Henry et al.	Mar 2018	A1
20180076988	Willis, III et al.	Mar 2018	A1
20180077709	Gerszberg	Mar 2018	A1
20180108997	Henry et al.	Apr 2018	A1
20180108998	Henry et al.	Apr 2018	A1
20180108999	Henry et al.	Apr 2018	A1
20180115040	Bennett et al.	Apr 2018	A1
20180115058	Henry et al.	Apr 2018	A1
20180115060	Bennett et al.	Apr 2018	A1
20180115075	Bennett et al.	Apr 2018	A1
20180115081	Johnson et al.	Apr 2018	A1
20180123207	Henry et al.	May 2018	A1
20180123208	Henry et al.	May 2018	A1
20180123643	Henry et al.	May 2018	A1
20180123836	Henry et al.	May 2018	A1
20180143819	Gross et al.	May 2018	A1
20180151957	Bennett et al.	May 2018	A1
20180159195	Henry et al.	Jun 2018	A1
20180159196	Henry et al.	Jun 2018	A1
20180159197	Henry et al.	Jun 2018	A1
20180159228	Britz et al.	Jun 2018	A1
20180159229	Britz	Jun 2018	A1
20180159230	Henry et al.	Jun 2018	A1
20180159232	Henry et al.	Jun 2018	A1
20180159235	Wolniansky	Jun 2018	A1
20180159238	Wolniansky	Jun 2018	A1
20180159240	Henry et al.	Jun 2018	A1
20180159243	Britz et al.	Jun 2018	A1
20180166761	Henry et al.	Jun 2018	A1
20180166784	Johnson et al.	Jun 2018	A1
20180166785	Henry et al.	Jun 2018	A1
20180166787	Johnson et al.	Jun 2018	A1
20180167130	Vannucci	Jun 2018	A1
20180167927	Beattie, Jr. et al.	Jun 2018	A1

Number	Date	Country
2515560	Feb 2007	CA
20140104097	Aug 2014	KR
2011137793	Nov 2011	WO
2013123445	Aug 2013	WO
2015006636	Jan 2015	WO
2015052478	Apr 2015	WO
2015052480	Apr 2015	WO
2017048417	Mar 2017	WO
2018106455	Jun 2018	WO
2018106684	Jun 2018	WO
2018106915	Jun 2018	WO

	Number	Date	Country
Parent	15872643	Jan 2018	US
Child	16134488		US
Parent	14853297	Sep 2015	US
Child	15872643		US

Method and apparatus for distributing software

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Disclaimer

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATION(S)

US Referenced Citations (191)

Foreign Referenced Citations (11)

Non-Patent Literature Citations (28)

Related Publications (1)

Continuations (2)

Entry
PCT/US16/46315 International Preliminary Report on Patentability, dated Jan. 26, 2018, pp. 1-32.
“Article 34 Amendment and Demand filed Jul. 14, 2017”, PCT Application No. PCT/US16/46315 filed Aug. 10, 2016, 1-15.
“International Search Report and Written Opinion”, PCT/US2016/046315, dated Nov. 3, 2016.
“International Search Report and Written Opinion”, PCT/US2018/015634, dated Jun. 25, 2018, 8 pages.
Akalin, Tahsin et al., “Single-Wire Transmission Lines at Terahertz Frequencies”, IEEE Transactions on Microwave Theory and Techniques, vol. 54, No. 6, 2006, 2762-2767.
Alam, M. N. et al., “Novel Surface Wave Exciters for Power Line Fault Detection and Communications”, Department of Electrical Engineering, University of South Carolina, Antennas and Propagation (APSURSI), 2011 IEEE International Symposium, IEEE, 2011, 1-4.
Barlow, H. M. et al., “Surface Waves”, 621.396.11 : 538.566, Paper No. 1482 Radio Section, 1953, pp. 329-341.
Chen, Dong et al., “A trust management model based on fuzzy reputation for internet of things”, Computer Science and Information Systems 8.4: 12071228, Abstract Only, 2011, 1 page.
Corridor Systems, “A New Approach to Outdoor DAS Network Physical Layer Using E-Line Technology”, Mar. 2011, 5 pages.
Covington, Michael J. et al., “Threat implications of the internet of things”, 2013 5th International Conference on IEEE Cyber Conflict (CyCon), Abstract Only, 2013, 1 page.
Elmore, Glenn et al., “A Surface Wave Transmission Line”, QEX, May/Jun. 2012, pp. 3-9.
Elmore, Glenn, “Introduction to the Propagating Wave on a Single Conductor”, www.corridor.biz, Jul. 27, 2009, 30 pages.
Fenye, Bao et al., “Dynamic trust management for internet of things applications”, Proceedings of the 2012 international workshop on Selfaware internet of things. ACM, Abstract Only, 2012, 1 page.
Friedman, M et al., “Low-Loss RF Transport Over Long Distances”, IEEE Transactions on Microwave Theory and Techniques, vol. 49, No. 2, Feb. 2001, 8 pages.
Goubau, Georg et al., “Investigation of a Surface-Wave Line for Long Distance Transmission”, 1952, 263-267.
Goubau, Georg et al., “Investigations with a Model Surface Wave Transmission Line”, IRE Transactions on Antennas and Propagation, 1957, 222-227.
Goubau, Georg, “Open Wire Lines”, IRE Transactions on Microwave Theory and Techniques, 1956, 197-200.
Goubau, Georg, “Single-Conductor Surface-Wave Transmission Lines”, Proceedings of the I.R.E., 1951, 619-624.
Goubau, Georg, “Surface Waves and Their Application to Transmission Lines”, Radio Communication Branch, Coles Signal Laboratory, Mar. 10, 1950, 1119-1128.
Goubau, Georg, “Waves on Interfaces”, IRE Transactions on Antennas and Propagation, Dec. 1959, 140-146.
Han, Chong et al., “crosslayer communication module for the Internet of Things”, Computer Networks 57.3: 622633, Abstract Only, 2013, 1 page.
Petrovsky, Oleg, “The Internet of Things: A Security Overview”, www.druva.com, Mar. 31, 2015, 3 pages.
Ren-Bin, Zhong et al., “Surface plasmon wave propagation along single metal wire”, Chin. Phys. B, vol. 21, No. 11, May 2, 2012, 9 pages.
Saied, Yosra Ben et al., “Trust management system design for the internet of things: a contextaware and multiservice approach”, Computers & Security 39: 351365, Abstract Only, 2013, 2 pages.
Sommerfeld, A., “On the propagation of electrodynamic waves along a wire”, Annals of Physics And Chemistry New Edition, vol. 67, No. 2, 1899, 72 pages.
Theoleyr, Fabrice, “Internet of Things and M2M Communications”, books.google.com, ISBN13: 9788792982483, Book—description only, Apr. 17, 2013, 1 page.
Wang, Hao et al., “Dielectric Loaded Substrate Integrated Waveguide (SIW)—Plan Horn Antennas”, IEEE Transactions on Antennas and Propagation, IEEE Service Center, Piscataway, NJ, US, vol. 56, No. 3, Mar. 1, 2010, 640-647.
Wang, Kanglin, “Dispersion of Surface Plasmon Polaritons on Metal Wires in the Terahertz Frequency Range”, Physical Review Letters, PRL 96, 157401, 2006, 4 pages.