SERVICES IN CONNECTION WITH RECEPTION OF AN EM SIGNAL

BACKGROUND

[0001] Augmented reality technologies for eyewear and head mounted apparatuses have traditionally required significant computational power to function. This comes as no surprise as positioning, connectivity, orientation, direction, and image capture and recognition technologies all can concur to drain batteries more quickly. As such, processing and power constraints lead to larger form factors, weight, cost as well as more frequent recharging cycles which reduce usability.

[0002] As described in U.S. Patent Application US9704132 "Method, System and Apparatus for Adapting the Functionalities of a Connected Object Associated with a User ID," filed on 01-1 1-2014, a connected object can be a proxy for a user or it can configure in accordance with a user profile.

[0003] iBeacon is a protocol that allows mobile apps to listen for signals from beacons in the physical world and react accordingly. In essence, iBeacon technology allows Mobile Apps to understand their position on a micro-local scale, and deliver hyper-contextual content to users based on location. The underlying communication technology is Bluetooth Low Energy (BLE). Bluetooth Low Energy is a wireless personal area network technology used for transmitting data over short distances. iBeacon technology consists of "Advertisements", or small packets of data, broadcast at a regular interval by dedicated devices or other BLE-enabled devices (e.g., smartphones or tablets) via radio waves. Beacons that want to be "discovered" can broadcast, or "Advertise" self-contained packets of data in set intervals. These packets are meant to be collected by devices like smartphones, where they can be used for a variety of smartphone applications to trigger things like push messages, app actions, and prompts. The iBeacon standard calls for an optimal broadcast interval of 100 ms.

[0004] An advertising packet consists of four main pieces of information.

[0005] · UUID: This is a 16 byte string used to differentiate a group of related beacons. For example, if Coca-Cola maintained a network of beacons in a chain of grocery stores, all Coca-Cola beacons would share the same UUID and a dedicated App would know which advertisements come from Coca-Cola beacons.

[0006] · Major: This is a 2 byte string used to distinguish a smaller subset of beacons within the larger group. For example, if Coca-Cola had four beacons in a particular grocery store, all four would have the same Major. This allows Coca-Cola to know exactly which store its customer is in.

[0007] · Minor: This is a 2 byte string meant to identify individual beacons. Keeping with the Coca-Cola example, a beacon at the front of the store would have its own unique Minor. This allows Coca-Cola's dedicated app to know exactly where the customer is in the store. [0008] · Tx Power: This is used to determine proximity (distance) from the beacon. TX power is defined as the strength of the signal exactly 1 meter from the device. This has to be calibrated and hardcoded in advance. Devices can then use this as a baseline to give a rough distance estimate.

[0009] All patents, patent applications, (including U.S. 9,092,898 and US 2016-0005233 Al), standards and published documents mentioned in this patent application are incorporated by reference. Furthermore, where a definition or use of a term in a document that is incorporated by reference is inconsistent with the definition of that term provided herein, the definition of that term provided herein applies and the definition of that term in the reference does not apply. Plurality shall mean one or more.

BRIEF DESCRIPTION OF THE DRAWINGS

[0001] Reference is made to the descriptions in connection with the accompanying drawings in which figures 1 to 22 generally describe various ways and techniques in which a multi-antenna device can detect the direction of arrival of an EM signal. Figure 23 to 27 describe generally user case scenarios.

[0002] FIGURE 1 represents various explanatory antenna radiation patterns plot and configurations;

[0003] FIGURE 2 represents various graphs plotting direction of arrival and RSSI deriving from software simulations for a simplified configuration at multiple wavelengths and a variety of distances;

[0004] FIGURE 3 shows a graph representing the impact of a human head on the previous configuration;

[0005] FIGURE 4 represents an embodiment based on a four antennas configuration;

[0006] FIGURE 5 is an embodiment based on a four antennas configuration, tilting, and lobe shaping;

[0007] FIGURE 6 is an embodiment for an algorithm to detect the direction of arrival of EM;

[0008] FIGURE 7 represents an embodiment based on a six antennas configuration, and lobe shaping;

[0009] FIGURE 8 is an embodiment for an algorithm to detect the direction of arrival of EM;

[0010] FIGURE 9 represents the System Overview of a prototype implementing the directional finding;

[0011] FIGURE 10 represents conceptual timing diagram for BLE advertising and BLE scanning;

[0012] FIGURE 11 represents a representative Algorithm pipeline;

[0013] FIGURE 12 represents a system architecture with RF switch;

[0014] FIGURE 13 represents a scanning mode with switching time interleaved;

[0015] FIGURE 14 represents the adopted standard to identify the beacon position;

[0016] FIGURE 15 represents our representative antenna radiation pattern at 2.45GHz;

[0017] FIGURE 16 represents considered beacon positions;

[0018] FIGURE 17 represents received RSSI value as function of the antenna orientation;

[0019] FIGURE 18 represents represents filtering with SampleBufferLength = 3; [0020] FIGURE 19 represents filtering with SampleBufferLength = 10;

[0021] FIGURE 20 represents raw RSSI values measured from two beacons separated by 60° at d=l .5m.

[0022] FIGURE 21 represents a novel configuration of antennas to mitigate polarization effects.

[0023] FIGURE 22 represents using power splitter and parasitic antennas to improve performances;

[0024] FIGURE 23 represents a directional navigation embodiment based on a breadcrumbs technique;

[0025] FIGURE 24 represents a directional navigation embodiment based on a breadcrumbs technique;

[0026] FIGURE 25 represents augmentation implementations based on parameters and/or classes;

[0027] FIGURE 26 represents augmentation and actuation embodiments;

[0028] FIGURE 27 represents augmentation and actuation embodiments;

DETAILED DESCRIPTON OF THE DRAWINGS

[0029] Embodiments of the present invention are understood by referring to figures 1 through 27.

[0030] In one embodiment, the solution can be based on common radio emission modules such as BLE and asymmetric radiation patterns of antennas. U.S. 9,092,898 focuses on a novel multiple antenna arrangement integrated into a head-mounted apparatus (HMA) system, which is then used to filter, process, and display augmented reality information associated with local radio emitting objects ,e.g. iBeacons, or any object that is capable of broadcasting at least some an ID including RF-IDs and WiFi modules.

[0031] FIGURE 1 describes one of the possible embodiments based on asymmetries of radiation patterns in antennas. The representation of radiated or received power as a function of direction is a radiation pattern.

[0032] Radiation pattern depends on the type of antenna. For instance, Figure 1 shows the radiation pattern of a dipole antenna in Radiation Pattern 102. This is an example of a donut shaped or toroidal radiation pattern. In this case, along the z-axis, which would correspond to the radiation directly overhead the antenna, there is very little power transmitted/received. In the x-y plane (perpendicular to the z-axis), the radiation is maximum. These plots are useful for visualizing which directions the antenna radiates/receives. Typically, because it is simpler, the radiation patterns are plotted in 2D. In this case, the patterns are given as "slices". Standard spherical coordinates are used, where polar angle Θ is the angle measured off the z-axis, and φ, is the azimuth angle, i.e., the angle measured counterclockwise off the x-axis.

[0033] Dipole antennas are just one of the many possibilities to implement various embodiments of this invention. Antennas exhibiting strong asymmetries in the radiation pattern on at least one plane can be used to implement different embodiments of this invention. A dipole, at least theoretically, has a zero gain along its axis. Dipoles have also different radiation patterns according to their lengths as compared to wavelength. This is described in Graph 103. In certain implementations, it is desirable to employ shorter dipole antennas such as ¼ wavelengths to diminish the blind spot of the dipole antenna's radiation pattern along its axis. This may improve the directionality that can be obtained by comparing received signal strengths.

As part of the disclosure, a number of software simulations have been performed to generate the graphs depicted. The simulation scenario consists of the following components: 1) A radio emitting object (e.g. a smart phone running an iBeacon application) sends outs an ID signal. The transmission uses iBeacon protocol at 2.4 GHz. 2) The ID signal is received by the multiple antennas on the HMA at different strengths. 3) The user is alerted to objects of interest via his or her HMA based upon the received radio emitting object signals as well as the HMA user's filters. Dipoles antennas consist of conductive linear material and therefore they can be integrated e.g. in regular eyewear. In particular, for integration into glasses, full wave, half wave and quarter wave dipoles are relevant; with Bluetooth transmission at 2.4 GHz, their length is 12.5 cm, 6.25 cm, and 3.125 cm, respectively. Layers made of absorbing material such as can shape lobes and patterns of antennas. Not all antennas in the configuration need to be the same length. For example, it could be useful to have a Front Antenna 257 working at half wave while Lateral Antennas 258 and 259 at one quarter wave. Many combinations are possible. The following parameters for the Bluetooth radio signal have been used to perform the simulations and to generate the graphs in Figure 2, Figure 3, Figure 4, Figure 5 and Figure 7: · frequency: 2.4 GHz · transmission power: 10 dBm (10 mW). Bluetooth and iBeacon standards allow power values up to 20 dBm (100 mW), related literature reports that actual value is decided according to the power budget of iBeacon objects. · antenna type at transmitter side: isotropic · packet size: 31 byte (iBeacon protocol) · physical bitrate: 1 Mb/s (Bluetooth protocol) · packet transmission int.: 350 ms · receiver sensitivity: -90 dBm [3] · path loss: power inversely proportional to square of the distance ( Friis).

[0034] For each case study depicted in Figure 2, Figure 3, Figure 4, Figure 5 and Figure 7, the power received by each antenna of the head mounted display is a function of: · the angle of arrival (denoted as a) varying from 0 to 360 degrees (with 10 degrees increments); · distance from iBeacon source and glasses center (denoted as d) varying from 0.5 m to 100 m; · elevation of the iBeacon source: in the same glasses plane (h = 0), 1.5 m above (h = 1.5), 1.5 m below (h = -1.5).

FIGURE 2 represents a series of graphs deriving from a series of software simulations on Antenna Configuration 101 and equivalent Antenna Configuration 104. The configuration consists of three dipole antennas; one placed frontally and one for each lateral arm. Possible dipole lengths (i.e., from 3.125 cm to 12.5 cm) are compatible with an head mounted structure.

[0035] Graphs 201 display received power on each antenna as a function of the angle of arrival of the signal, with distance 1.5 m and different dipole types. Quarter wave dipoles provide larger coverage in the receiving section and a narrower coverage in the non-receiving sections. In some implementations, it can be convenient to use quarter wave dipoles to improve the discrimination that can be obtained via the blind spot that is aligned with the dipole antenna since the blind spot is narrower.

[0036] Graphs 202 display received power on each antenna as a function of the angle of arrival of the signal, and three different distances, i.e., 1.5 m, 20 m and 100 m. Received power decreases with distance but at 100 m it is in the order of microwatts which is commonly elaborated as an input a by commercial receiver electronics s described in the paper "M. Magno, V. Jelicic, B. Srbinovski, V. Bilas, E. Popovici, and L. Benini, "Design, implementation, and performance evaluation of a flexible low latency nanowatt wake-up radio receiver," IEEE Transactions on Industrial Informatics, vol. 12, no. 2, pp. 633-644, April 2016.

[0037] FIGURE 3 displays the same configuration of antennas on the Head Mounted Apparatus but we introduced the modeling of radio absorption by user's head. According to literature, human tissues reduce radio power of at least 8 dB according to the paper T. Alves, B. Poussot, and J. M. Laheurte, "Analytical propagation modeling of ban channels based on the creeping-wave theory," IEEE Transactions on Antennas and Propagation, vol. 59, no. 4, pp. 1269 - 1274, April 2011. This fact leads to a lobes attenuation.

[0038] As shown in Antenna Configuration 301 and Graph 302, the absorption effect of the head creates an asymmetry in the radiation pattern of lateral antennas and introduces a difference in the received power values of left and right antennas depending on the position of the radio source.

[0039] As a consequence of this asymmetry, a possible embodiment of a direction detection technique is follows: 1) compute the difference (DLR) between received power on left antenna and on right antenna (hereinafter DLR); 2) if DLR is positive then the source is on the left; 3) if DLR is negative then the source is on the right. In some implementations, using power difference for direction detection has the following advantages: sign (i.e., positive vs. negative) detection can be performed by low-priced hardware; power difference is more robust to electro-magnetic noise which is assumed to affect both antennas in a similar way (and therefore is eliminated by difference operation); power difference is independent of source power and obstacles between source and glasses.

[0040] In some implementations, by using received power from three antennas we may need to distinguish if the source is positioned in front or behind the user. The power received by the frontal antenna and attenuated by the head, can be generated by a weak source in front of the head or by a strong source behind the head. In one implementation, a possible solution consists in the introduction of a gyro and/or a compass to detect a rotation of the head toward the left or the right. The knowledge of the position of the antennas around the head and the knowledge of the rotation of the head resolves the ambiguity by computing time derivatives of RSSI at each antenna to distinguish front/back. For example, by turning the head to the right, the right temple antenna will experience a surge in RSSI while the left temple antenna experiences a decrease because of the shielding of the head: the EM source is in the back. In some implementations, the shielding adsorbent material positioned between the head and the antennas can accentuate the difference between normalized lobe and the head attenuated lobe (Antenna Configuration 301).

[0041] FIGURE 4 describes an extension of the multi-antenna system in which an additional Front Antenna 404 is added in Antenna Configuration 401. A Frontal Absorbing Layer 402 is introduced between the two antennas Front Antenna 404 and Front Antenna 403 so that their radiation patterns become different along the front / back axis. In some implementations, it can be useful if the absorbing layer can attenuate radio power in the Bluetooth frequency of at least 8 dB. Antenna 406 and Antenna 405 are temple antennas and in certain implementations are positioned on the same plane as the frontal left and frontal right antennas.

[0042] The received power on frontal antennas is shown as a result of a software simulation Graph 410. Graph 410 shows that independently from signal strength at the source and interferences between source and glasses, in some implementations, the sign of power difference (RSSI) received at each antenna allows to detect if the source is in front of the user or behind. All antennas in the simulation are quarter wave dipoles. Two quarter-length front antennas, Front Antenna 404 and Front Antenna 403, fit regular eyewear models. In summary, as shown in Diagram 420, the four-antennas configuration allows to identify four arrival zones by performing subtractions computations. When two or more iBeacons are vertically aligned, such as iBeacons on shelves of a retail shop, it might be useful to be able to vertically discriminate angles of arrival.

[0043] FIGURE 5 consists in a modification of previous multi antenna system in which lateral antennas are 45 degrees tilted in the opposite direction and Absorbing Layer 503 and 504 is added under Left Antenna 506 and above right antenna as shown in Antenna Configuration 501 and equivalent Antenna Configuration 502, which is an aerial view of Antenna Configuration 501.

These two changes in the antenna configuration as compared to Antenna Configuration 401, namely the tilting and the addition of absorbing layers, introduce a vertical asymmetry in lateral radiation patterns ( Antenna Configuration 501). Graph 510 and 520 show RSSI on each antenna as a function of the angle of arrival of the signal and elevation. The Adsorbing Layers 503 and 504 are ideal for the purpose of the software simulation generating the graphs. In Graph 520 source is 1.5 m above, in Graph 510 source is 1.5 m below the horizon at a distance of 20 m. The asymmetry of lateral radiation patterns allows obtaining a set of conditions to detect both horizontal and vertical orientation of the angle of arrival as shown in Figure 6. FIGURE 6 represents a possible algorithm for the detection of the angles, both horizontal and vertical that is derived from deductions and observations of patterns of Graph 520 and Graph 510. The terms "Small" and "Big" refer to a comparison operation with respect to a certain threshold that can be deducted from simulations or field tests. "Small" and "big" derive from different inclinations of the antennas as compared to the source that is positioned either below or above the horizon, 1.5 m at a distance of 20 m.

[0044] The last row reports conditions to assess that user actually centered the RF emitter with his/her glasses. In one implementation, the radio-emitting object is located centrally in the field of view of the glasses. As discussed in previous sections and applications and patents incorporated by reference an outputs (guidance or content) can be generated also considering offsets and corrections with respect to the dotted line. In Antenna Arrangement 501 and Antenna Arrangement 502, the dotted line represents the imaginary line on which an RF emitter would ideally be centered. Ideally, when the user has centered the RF emitter, the difference of measured RSSI deriving from Left Antenna 506 minus Right Antenna 507 will be zero, while the difference between RSSI measured at Front Left 403 and Front Right 404 will be positive.

[0045] The first column "Left-Right" describes the differences in power received by the Left Antenna 506 as compared to Right Antenna 507 when these antennas are coupled with ideal Adsorbing Layers 503 and 504. The differences can be positive or negative and can be of different values, "small" or "big". Threshold values can define "small" and "big" according to simulations and field tests. The second column, "Front Left - Front Right", describes the measured RSSI difference between Front Left 403 and Front Right 404 antennas to eliminate the front/back ambiguity. The third column, "Horizontal Orientation", describes the position of the EM source, namely the ninety degrees sectors on the horizontal plane where the source is positioned relatively to Antenna Configuration 501. The fourth column, "Vertical Elevation" describes the vertical position of the RF source as compared to the horizontal plane where the glasses are located.

[0076] All these indications can be used to guide the user, who is wearing, e.g., Antenna Configuration 501, to adjust his or her head and receive indications of the relative position of the RF source. In certain implementations the adjustments indications (relative orientation of the wearable device comparatively to the RF emitter) and/or the augmentation message, can be in the form of an optical, a haptic or auditory stimulus. Adjustments indications can be indications of the relative position and orientation of the device. A haptic vibration on right temple can signal, e.g., that something of interest is on the right according to a user profile.

[0077] FIGURE 7 describes Antenna Configuration 700 where tilting is removed and a vertical discrimination capability is obtained by adding two additional lateral antennas. All antennas are 3.125 cm long (quarter waver for a 2.4 GHz transmission) and are aligned with glasses temples. Grap 710 and 720 show differential power received at each pair of six antennas as a function of the angle of arrival of the signal and elevation. In Graph 710 the source is 1.5 m above. In Graph 720 the source is 1.5 m below. The vertical asymmetry of lateral radiation patterns that is obtained by means RF adsorbent material allows obtaining a set of conditions to detect both horizontal and vertical orientation of the angle of arrival. The six antennas are: Front Left 403, Front Right 404, A Left 702, A Right 704, Left 701, Right 703 ("A" indicates adsorbent material ).

[0078] FIGURE 8 shows that vertical asymmetry of lateral radiation patterns allows obtaining a set of conditions to detect both horizontal and vertical orientation of the angle of arrival. In particular, the last row reports conditions to fulfill to center the EM source. "K" indicates a threshold.

FIGURE 9 (and following) represents the System Overview of a head mounted apparatus prototype implementing some of the concepts. Fig. 9 shows an overview of the target system, where three kind of connections can be identified: 1) BLE connection between the beacon and the antennas on the glasses. 2) An I2C bus connection between the electronic elements on the UMA. The I2C bus connects multiple modules (slaves) controlling the BLE antennas with a master that runs the directional finding algorithm. Additional antennas can be used to estimate the presence of the beacon in the back or to evaluate other beacon proprieties not strictly related with directionality, such as the polarization. 3) A BLE connection between the master and an external device (called server from now on): such device will be used to configure the glasses at runtime and to exchange any other kind of information with the UMA (e.g. internet content associated with the beacon). A server may show the result of the directional finding algorithm. The slave elements can filter the RSSI values and offload this information to a master that can run the directional finding algorithms. Many other modules can expand this baseline architecture for the UMA.

[0079] FIGURE 10 represents a timing diagram for BLE advertising and BLE scanning. The purpose of a Bluetooth beacon is to "advertise" its presence to the neighbor Bluetooth "scanners". BLE Beacons advertise on three specific channels: 37, 38 and 39. Depending on the target power efficiency of advertising device (e.g. ultra-low power beacon), advertising events may be quite infrequent. On the other hand, mobile phones, usually advertise more frequently because of their "unlimited power budget".

[0080] Advertising packets are sent periodically on each advertising channel, the transmission of the packet in sequence through channels 37 38 and 39 delineates an advertising event. The time interval between consecutive advertising events has both a fixed (Advlnterval) and a random (AdvDelay) delay component in order to avoid possible packet collisions. The beacon vendors currently span the power/responsiveness tradeoff by enlarging or shortening this interval, thus defining a design parameter that we cannot control. [0081] The receivers within the slaves may act in a similar way: they consecutively scan the three channels. Different setting are achievable by changing ScanWindow and Scanlnterval delay. By setting Scan Window = Scanlnterval the receiver may work in "continuous scanning mode" at cost of power.

[0082] FIGURE 11 represents a possible algorithm pipeline. It's a procedure with optional feedback loops and data filtering capabilities to compensate signal flaws. The input RSSI acquired from the beacon can be noisy because of objects in the environment and the reflective nature of surrounding materials; it's necessary to filter dirty inputs via dedicated software. The components of the algorithm are detailed below.

[0083] ACQUISITION/ ADAPTION includes low level procedures running within the software stack in the receiving modules. Software stack can be configured to operate in scanning mode to receive the advertising packet form beacons. A Smartphone can advertise more frequently and at higher power.

[0084] The RSSI acquisition rate is strictly related to the remote beacon configuration: most of the commercial beacon advertise with a really low frequency (few times each second) to save power.

[0085] STATIC FILTER is composed by buffer structure (one for each beacon) of dynamic dimension that cleans the input stream of RSSI data by applying some statistical method such as returning the average of the last N acquired RSSI values or applying regression algorithm on those data.

[0086] LOCALIZATION is implemented in the master module. Once RSSI values from all the slaves are received, the master calculates the iBeacon position (e.g. left-front, centered, left-front, left-back, right-back).

[0087] Using three antennas left, right and frontal, a possible localization algorithm estimates the beacon position: S sac-cm- centers

[0088] Furthermore left and right positions can be determined comparing which is the higher RSSI between Because of the head attenuation, discriminating between left and right is possible, while front position requires a ^RSS! fr^t dominating above others.

[0089] VIEW includes the implementation of visual software and run on the server. Depending on the parameters, the visualizer can be more or less selective, thus restricting or enlarging the detection angle. FIGURE 12 represents system architecture with RF switch. Instead of using three independent measurements of the three or more antennas, we can use a time division system where the RSSI measurements occur in a round robin fashion. We envision and want a response time lower than 3s. However, response time as well as correctness of the centering algorithm are affected by parameters not always controllable at the design time: 1) emitted RF power and 2) advertising rate. These parameters can change depending from the beacon being a low-power device or a high power mobile phone. Receiver parameters are: 1) Parameters of the scanning procedure; 2) Type of antennas; 3) Quality of the received signal; 4) RSSI calculation delay (may change depending on the receiver technology). Received RF power may change depending on the polarization of emitting object. Computational parameters are: 1) Buffer sizes and slave latency; 2) I2C bus delay; 3) Master computational complexity and delay. 4) Number of beacon (many beacons slow down the system). To avoid communication errors on the I2C bus, each message has a checksum byte.

[0090] The proposed software architecture has been provided with optional features at the visualizer level, to prevent the generation of false positive results by checking multiple times the state of the system before generating an output. This feature may lead to performance penalties in terms of response time.

[0091] A concern of using multiple BLE SoCs is related with their power efficiency and the resulting impact on the battery lifetime. In general, the power cost related with BLE Rx/Tx is expected to be much higher than the computational cost. Different solutions, both hardware and software, can be implemented.

[0092] Software improvements include the capability of turning ON and OFF BLE SoCs thus reducing the power consumption when the glasses are idle. Sleep capability differs depending on the adopted SoCs and their hardware configuration. BLE SoCs from different vendors predispose different services to put/restore the device in/from sleep mode through automatic or on demand software procedures.

[0093] Software-controlled sleep mode access can open the doors to a working scenario where only one SoC (e.g. the master) scans the presence of advertising beacons in the near field while all the slaves are in sleep mode. Slave receivers wake up only when necessary. In a different scenario the UMA device can be put in low power mode while the scanning operation is performed by an associated device (e.g. smartphone).

[0094] Note that in the former case the wake up can be managed entirely on the UMA through interrupt procedures, while in the second case custom wireless procedures (e.g. use of appropriate wake up receivers) are required to boot-up the system from the external device.

[0095] To further minimize the power cost, the computational capability I2C of the slaves should be as low as possible because it is accounted 3 or 4 times in the overall power balance (depending on the number of antennas). Reducing the hardware support for the slaves is a critical decision because acquisition and filtering procedures described previously are implemented by slaves (while I2C master is in charge of collecting RSSI values and determine UMA orientation). Slaves could require a lot of memory space, because multiple instances of buffers are required depending on the maximum number of beacons. We expect a tradeoff between power consumption and visible beacons. In a possible improvement, the master could fill the slave's white list in order to consider just a subset of "high interests" beacons while filtering all other beacons. A version of the UMA Prototype can use SaBLE-x BLE modules from LSR for the slaves (CC2640 SoC) and BLE-113 module from Silicon Labs for the master (CC2541 SoC). [0096] FIGURE 13 represents a scanning mode with switching time interleaved. To minimize the number of BLE devices an RF switch can select different antennas and route the RF signals to a unique receiver module. A possible new architecture is presented in Fig.13 : the unique slave receiver controls the RF switch and select one of the antennas, it demodulated the signal information and generates an RSSI value that is passed to the master through a point-to-point I2C communication. The switching mechanism is critical. An ideal system should interleave scanning and switching activities thus enforcing the protocol consistency. We want to avoid switching to another antenna while the receiver is scanning data.

[0097] Software procedures need to control the low lever stack layer. This allows a proper management of the scanning intervals and a consequent generation of the control signal for the RF switch.

[0098] System latency is another issue. As depicted in Fig 13, while we are listening for a specific channel we are also referencing to a specific antenna, therefore the total time required to sweep all the antennas is 1 a sc ^& tr ⁱ tervai _^ his means that the time required to run the directional finding algorithm (latency) is 3 times larger than using a plurality of BLE with three antennas. It is not possible to excessively shorten the scanWindow. ScanWindow is periodically activated on channels 37-38-39. Given that Beacons also advertise using these three channels in sequence, to ensure a correct reception of the advertising messages within the scanWindow, this should be typically larger than ss*:

[0099] ⁼ A vlntervat - AdvDsla

[00100] This amount of time can be partially random to avoid packet collisions and it is often quite long in order to reduce the beacon energy cost. Furthermore, it should be considered that an RF switch has a switching time of approximately one hundred of nanosecond and a non-negligible latency (signal lag).

[00101] Another drawback is given by the fact that given an antenna we analyze the same channel (e.g. front antenna and channel 37 in Fig. 13). This means that noise on a specific channel will affect a single antenna, while in a friendly scenario the noise is amortized among all the antennas. To spread possible noise effect to all the antennas, RF switch can be triggered every two scanlntervals. This solution increases the latency but in a continuous working scenario we can compensate since the software application can queue dedicated buffers, one for each antenna, independently and in an asynchronous fashion.

[00102] FIGURE 14 Represents the standard to identify the beacon position. For all the following experiments the AR glasses are provided with n antennas while one or more beacons are in the near field.

[00103] As shown in the figure, beacon position with respect to the glasses is identified by d and h (distances expressed in meters) while glasses orientation is based on the direction of clock indicators (from the user point of view). For example, 12h means that a user wearing the glasses has a beacon straight ahead, while 9h means that a beacon is 90° on the left. We experienced that the antenna setup plays a fundamental role in maximizing the received RSSI value. We performed several experiment to find the best setup. The antenna used in this demo is a MOLEX 2.4/5GHz Balance Flex Antenna. Despite it should generate a perfect toroidal radiation pattern, it suffers of some effects which make the radiation pattern asymmetric.

[00104] FIGURE 15 represents antenna radiation pattern at 2.45GHz datasheet of the MOLEX antenna.

[00105] FIGURE 16 represents considered beacon positions. User wears the HMA and changes orientation with respect to the beacon that is kept in fixed position. The relative beacon positions are h3, h2, hi, hi 2, hi 1, hlO, h9 and h6 (beacon back).

FIGURE 17 represents received RSSI value as function of the orientation at d=1.5m and d=3m. RSSI values: (blue), ^SSSi n$kt (red) and (green). Frontal position and its orthogonal left and right positions (hi 2, h9 and h3 respectively) can be detected because the RSSI generated by the closer antenna dominates the others. At h2 and hlO (60° from center) the closer antenna RSSI value roughly matches BSS!fr t. At hi and hl l (30° from center) spread by lOdB on average. This orientation can be distinguished from hl2 where an average separation of 15dB is experienced between ^R5 ^ ⁱ fivnt and others RSSI values. At d=1.5m h6 orientation, # ^5S ¼*r dominates and ^SSS! ieft is moderately high: the cause is that left and right antenna are not receiving from the minimum radiation angle because of the small distance. This effect tends to disappear with distance.

At d=3m h6 orientation none of the RSSI is dominating. That is a really interesting condition to filter beacons on the back of the user. In any case it is improbable to report an average 15dB separation between RSStfr * and which is promising to avoid ambiguity between hl2 and h6. These considerations can be used to calibrate the software and represent a good starting point for an application with a sensibility of less than 30°. This means that iBeacons that are separated by an angle of 30° can be distinguished.

[00106] FIGURE 18 represents filtering with SampleBufferLength = 3. The filtered data becomes cleaner as the buffer size increases but the system reactivity decreases. When the user changes the orientation a less sharp variation of the RSSI values is experienced. This can generate a delay in the application displayer.

[00107] FIGURE 19 represents filtering with SampleBufferLength = 10. We empirically demonstrated the importance of applying a SampleBufferLength>3 to get a clean result on the displayer. The benefit of filtering is demonstrable by comparing raw data and filtered RSSI values. The front antenna is sampling on three different channels 37-38-39 which suffer different noise, thus the raw data are quite spread. This effect is strongly attenuated by applying SampleBuffer. As a result the minimum separation between ^ifm t and other RSSI value becomes larger when filtering is applied and this results in a stable evaluation of the results. [00108] FIGURE 20 represents raw RSSI values measured from two beacons separated by 60° at d=1.5m. For this experiment we placed a beacon (Bl) in position hi 1-1.5m, and another beacon B2 in position hl- 1.5m, meaning that beacons are separated by an angle of 60°. User P0 wears the glasses and rotates from h9 to h3. Top and bottom Fig. 24 show the RSSI values measured "in parallel" from beacon Bland B2 respectively. When considering the beacon results separately, relative beacons are detected. However, analyzing all the RSSI values received in conjunction from both beacon is not a trivial job. There are two possibilities that the algorithm must take into account: 1) which is the centered beacon; and 2) which is the closer beacon. To determine which is the centered beacon a new metric called Centrallndex is introduced: its mauve is maximized if the beacon is at 12h.

[00109] B&acim cente ed ^ RSSIfr _c > {S SIi _S f E5Si _r i _sn - _t ) Cmtr&lR ige

[00110] That in other words means that = _must e higher than threshold value called C-mir «!««¾»

[00111] Comparison between absolute RSSI value is performed to determine which is the closer beacon.

[00112] In general, it is difficult to simply consider absolute RSSI values to determine the centeredness of a beacon, because the environment plays a fundamental role in absorbing or amplifying the receiver Bluetooth signal, thus applying several undesired variability effects on the absolute RSSI value.

[00113] A possible algorithm considers absolute RSSI values only when multiple beacons have a similar Frontallndex. In this case the comparison between the absolute values will lead the visualizer to show the closest beacon. For example, this may happen if more beacons are located at hl2 but at different distances, in this case the user will visualize the closest one.

FIGURE 21 represents a novel configuration of antennas where Vertical Antenna 2101 and 2102 are added. Polarization of the emitting source is important. If the position of the beacon can be controlled, the discrimination algorithm can be simpler as well as the HMA prototype (including only the antennas receiving the correct polarization). If the beacon cannot be controlled, the use of antennas that can serve multiple- polarizations is advisable. RSSI variations in a non-controlled environment can be large. Consequently, RSSI values should be averaged and the number of samples used for the average by the algorithm should be optimized. RSSI variations are also related to the distance between the beacon and the glasses and consequent multipath effect. The usage of Vertical Antenna 2101 and 2102 can signal the direction estimation algorithm that the emitting source is polarized vertically when, e.g., the RSSI received at those antennas is higher than the horizontally positioned antennas such as Antennas 2104, 2105, 2106. This information can be used to tell the direction detection algorithm that data received from certain antennas might deserve a higher weight as compared to data received from antennas with opposite polarization.

[00114] FIGURE 22 shows one possible way to increase the performances of the frontal antenna by replacing a single antenna on the front with an antenna array composed by two elements (or more) to increase the directivity. Two frontal elements in the array configuration are placed, e.g., at about 6 cm one from the other (lambda/2 at 2.4 GHz) on the same plane. To exploit the array configuration, two antenna elements can be fed through an in-phase Power Splitter 2210. The splitter can be a resistive power splitter with SMA ports. By using a two-antenna array, such as Antenna 2201 and Antenna 2202, we experienced a 5 dB increment in the maximum direction of the dipole "doughnut" and a narrower radiation lobe. Antennas of higher length can also be used. Antennas 2201 and 2202 can be substituted by a half wave antenna.

[00115] Parasitic Antennas 2204 and 2203 can be used to "affect" Antennas 2206 and 2205 by creating a more marked hole in the radiation pattern of Antennas 2206 and 2205 in the direction H12.

FIGURE 23 represents one embodiment of an aspect of the present invention. Wearable equipment or handheld equipment can be configured via software and hardware modules to detect the direction of arrival of an EM radiation of equipment such as an iBeacon module or Smartphone when, e.g., in advertising mode. The EM radiation signal may come from fixed stations such as Emitting Objects 2302, 2303, 2304, 2305, 2306. These Emitting Objects have EM Range 2310, 2311, 2312, 2313. In some implementations, at least some of these emitting objects have an overlapping radiation area so that UE 155 can sometimes receive the EM emission contemporaneously form two Emitting Objects when positioned within said overlapping radiation areas. In certain implementations, all of these objects are iBeacons stations. UE 155 is representative of a direction finding equipment that can be here a wearable or an handheld device. In this case, it is a head-mounted apparatus capable of direction finding. In other implementations, the system and the UE can use a mix of radio standards, to acquire directional information. For example, a mix of Wi-Fi and Bluetooth stations can be used for the directional guidance. In certain implementations, as described in Fig 23 and Fig. 24, the directionality finder capability of UE 155 and an intelligent distribution of emitting objects can provide a useful and alternative technique to overcome limitations or complications associated to indoor and/or outdoor positioning and navigation. A breadcrumb technique can be used to guide UE 155 to object A (for example a shop in a mall) represented in Figure 23. This technique consists in following a trail of Emitting Objects to arrive to a location by following intermediate steps.

[00116] In one implementation, described in Fig. 23 UE 155 is paired with UE 165 and both are used and worn by the same user Bob. The person skilled in the art will know that in certain implementations, UE 165 may disappear and UE 155 will be able to communicate directly with Server 2300. In this implementation, UE 155 will provide the direction finding capability and UE 165 will provide communications with Server 2300 and, at least in part, computation capabilities associated to the direction finding hardware mounted on UE 155. Communications between UE 165 and UE 155 can occur via Link 2326 (e.g. Bluetooth) and communication with Server 2300 via Link 2320 (e.g. LTE).

[00117] As an example, Bob is in a shopping mall and desires to reach location A. UE 165 can send an inquiry to Server 2300. Server 2300 by means of Controller 2301, Memory 2302 and an algorithm stored therein, will retrieve and calculate the sequence path of objects that UE 165 + UE 155 (Bob) must follow to reach location A. UE 165 may receive said sequence via Link 2320. In case UE 165 deviates from said sequence path of Emitting Objects (EO) or an Emitting Object in the sequence becomes not available, UE 165 may request and receive an updated path from Server 100. In certain implementations, UE 165 may not need to ping Server 2300 for updates because UE 165 may download in part or in its entirety the database of emitting objects for the area in which it is located. Updates and recalculations to reach a desired location may occur at least in part locally at UE 165 and or on Server 2300.

[00118] In an exemplary embodiment, UE 165 + UE155 (Bob) will be directed in sequence toward Emitting Object 2302, Emitting Object 2303, Emitting Object 2304, Emitting Object 2305, and Emitting Object 2306 to reach location A. The navigation system's UX-UI (either on UE 155 or UE 165) may consist in providing a directional indication toward the next waypoint in the sequence of emitting objects (EO). When UE 155 can receive the EM emission of the next emitting object, an algorithm may calculate the time in which to switch the UX-UI indications from the current indication of the previous EO (e.g. 2302) to the next EO (EO 2303) in the current breadcrumb trail using ,e.g., the RSSI level of the next emitting object. This process can be repeated for all emitting objects: 2303, 2304, 2305, 2306 until Bob reaches destination.

[00119] In certain implementations, the Emitting Objects can be controlled, programmed, or configured by means of Links 2321, 2322, 2323, 2324, and 2325. The Emitting Objects can be programmed to emit EM energy at predetermined levels or using predetermined emission sectors. They can be programmed to convey predetermined information to the user. They can also be activated only when they are needed. For example, the query originated by UE 165 to reach Location A may direct Server 100 to activate those EOs that are useful and needed to create the trail. Server 2300 can also regulate emission power of said EOs. In certain implementations, EOs can emit EM signals according to sectors. So for example, the same fixed EO can emit an EM with an ID code in one sector and another ID code in another sector. [00120] Emitting Objects can have functionalities such as the reception of surrounding signals from nearby Emitting Objects or User Equipment. This information can be conveyed to Server 2300 and/or UE 165 + UE 155. In one implementation, if one of the Emitting Objects such as, e.g., Emitting Object 2304 stops functioning said failure could be detected by surrounding Emitting Objects 2303 and 2305 and then conveyed to Server 2300 and/or UE 165. An algorithm stored in Memory 100 may direct Emitting Objects 2303 and 2305 to increase their emission power to compensate for said failures. UE 165 may continuously update Server 2300 on which neighboring Emitting Objects UE 155 is capable of receiving.

[00121] In certain implementations, Emitting Objects 2302, 2303, 2304, 2305 and 2306 do not communicate with Server 2300 but their position is known to Server 2300. An algorithm in Memory 2302 will function according the assumption that the data associated to EOs are correct and updated.

[00122] Figure 23 represents an embodiment where all Emitting Objects are fixed. In fact, in certain implementations, some links in the chain of emitting objects may come, at least temporarily, from Emitting Objects that are mobile such as a UE apparatuses when they are useful to assist the navigation of Bob. To support this functionality, in certain implementations, said UE 155 apparatus (via UE 165) or UE 165 apparatus may report to Server 2300 the list of Emitting Objects (neighbor objects) they are able to receive.

[00123] In a situation where two Emitting Objects receive said UE apparatus but cannot receive each other, a mobile UE apparatus could be used according to an algorithm, e.g., on Server 2300 or UE 165 to bridge a gap in the chain that is needed for the directional navigation. The person skilled in the art will understand that hybrid scenarios are possible where fixed and movable equipment contribute to act as reference points during a directional navigation. An handover, namely when UE 165 + UE 155 stops providing directions with reference to an old Emitting Object and starts providing directions with reference to a new Emitting Object, can be controlled by an algorithm in UE 165, UE 155, or alternatively in Server 2300 via Links 2320 and 2326. The direction instructions to Bob (who is wearing UE 155 and in the case carrying UE 165) to reach Object A where EO 2306 is located can be provided in multiple ways. Just as examples: UE 165 or UE 155 can produce an audio feed to Bob telling him if UE 155 center field of view is centering or is left or right of the Emitting Object 2302

[00124] FIGURE 24 represents a dynamic embodiment of what described in Figure 23. In this implementation, the emitting objects are UE hardware that are not fixed but can move around, such as UE 2432, 2433, 2434 and 2435. At least some of these UE emits an EM signal such as a Bluetooth signal having radio horizon Range 2440, 2441, and 2442. In this case UE 155 is capable of communicating directly with Server 2300 without an intermediate equipment (UE 165). Links 2450, 2451, 2452, 2453, 2454, 2426 are only exemplary links. The Base Station 135 as well as the cloud represented in the figure are proxyes for hardware and communication equipment capable of connecting servers and mobile equipment.

[00125] In certain implementations users of UE 2432, 2433, 2434 and 2435 may have all joined a common session area (defined by a geofence) and/or event and/or session. In certain implementations 2432, 2433, 2434 and 2435 might give permissions to upload on Server 2300 the list of surrounding emitting objects and the RSSIs that they receive. This may allow an algorithm in Server 2300 to rely on UE 2432, 2433, 2434, and 2435 to enable directional navigation.

[00126] In one example, user of UE 155 wants to meet with user of UE 2435. UEs 2432, 2433, 2434, 2435 may continuously or periodically update Server 2300 on which neighboring UEs or EO they are capable of receiving (neighbor list and RSSIs). For example, when Server 2300 receives a request from user of UE 155 to meet with user of UE 2435, it may provide a first indication of which neighboring UE user should follow that is useful to get closer to the final destination, e.g., UE 2440. Along the breadcrumb path and over time, the list of UEs can vary according to many parameters. In certain implementations, UE 155, 2432, 2433, 2434, 2435 may provide to Server 2300 with not only a list of surrounding emitting neighboring equipment via Links 2450, 2451, 2452, 2453, 2454, that can be used to extrapolate a path but also with indications associated to the strength of the EM signals received. Therefore, for example, while choosing between two UEs that can both receive UE 2433 an algorithm in Server 2300 or in UE 531 may indicate as most useful the one that reports a stronger signal received from UE 2433 because it is closer to the next step in the trail. Other parameters can be used additionally to RSSI. The iBeacon standard has a distance determination algorithm built in that can be used for improving the efficiency of the sequence trail.

[00127] Generally, an optimum breadcrumb trail can be determined by balancing the least number of UE/EO to reach the destination and the readings of RSSIs between said UE or EO (how strong they receive each other) since weak links can disappear while Bob is on his route.

[00128] In certain implementations, UE belongs to closed classes and or groups so that only equipment and/or users that support directional navigation within a predetermined group can benefit from the support of mobile equipment within the same group or class. One of the reasons is that, for example, UE may have to report periodically to Server 100 the list of surrounding UEs to be able to support and be supported for the directional navigation functionality. In certain implementations, the reporting of said list in one area or within a certain mesh network can be activated according to different scenarios and algorithms.

[00129] In one implementation, the system or a UE may request the activation of the reporting of the neighbors list to Server 2300 for all the UEs within a predefined distance form said UE. In another implementation, there is no predetermined distance but the requirement of reporting may expand with a geometric progression from the originating UE until a predetermined destination UE is reported to be part of at least one of the neighbors list of the geometrically expanding group generated by the query. The query may be limited to a predetermined number of hops or branches from the originating UE. If the destination UE is not contained within any of the neighbors list, the query may return a null value. In other implementations, the query may be defined not only by an instant search but also by a search that lasts for a period of time. If within said period, one of the UEs that is part of the geometrically expanding group (or simply by a group of UEs that are part the service) reports the reception of said destination UE as a neighbor, originating UE will be alerted and/or a directional breadcrumb path can be provided.

[00130] FIGURE 25 represents implementations based on parameters and/or classes. In one implementation, UE 155 is augmented reality glasses or (simply an HMA). In other implementations, UE 155 can be a handheld device working according to the same EM direction detection principles. Both classes of apparatuses (handheld and wearable) may contain modules such as a positioning module, a gyro module, a compass module that can be used to support an array of functionalities described in the following paragraphs. In this case, two different users wear or carry UE 155 and 165.

[00131] In one embodiment, if UE 155 centers UE 165, content can be pushed to UE 165 (e.g. a business card of user of UE 155) or an indication of appreciation of user of UE 155 toward user of UE 165 (e.g. a "like"). This "like" indication can be delivered instantaneously or according to parameters such as distance of UE 155 from UE 165, distance from where the like indication occurred, or time elapsed. This can be used by an intelligent dating application. Users may receive a log of the likes they have received and act upon later.

[00132] Certain content or interactions can be reserved only to situations where two users mutually center each other with their UE. For example, two users whose apparatuses both signal to Server 2300 a mutual centering (each user is in the field of view or the other user) may trigger reserved functionalities.

[00133] In one embodiment, the argumentation indicia that are outputted by UE 155 when Emitting Object 2501 is in the field of view of UE 155 depend not only from a code associated with the emitting object but also from a contemporaneous reading of a compass module in UE 155. For example, an augmented indication to turn to the right may occur if compass module of UE 155 reads an orientation of UE 155 value between 240 degrees and 300 degrees while Emitting Object 2501 is in the field of view of UE 155 and is centered. Equivalently, an indication to turn left may occur if compass module of UE 155 reads a direction of arrival compass value between 60 degrees and 120 degrees. [00134] In another implementation, the augmentation indicia may depend not only from a code associated with the emitting object (UE or EO) but also from the geographical position of UE 155.

[00135] In another implementation, the augmentation indicia may depend from a membership-to-a predetermined-group-of-users parameter to which user of UE 155 and/or user of UE 165 belong. User of UE

165 may be paying a fee for his information or an advertisement to be augmented by UE 155.

[00136] In another implementation, the augmentation indicia may depend not only from a code associated with the emitting object (EO or UE) but also from cinematic qualities of the emitting object. This can be accomplished in many different ways. The examples are not exhaustive. UE 155 may detect the motion of

UE 165 and therefore it enables the augmentation of the EM signal it receives from UE 165. In another implementation, only if UE 165 detects a movement of itself via for example its own Compass / Gyro /

Accelerometer it will emit an EM signal necessary for augmentation.

[00137] In another implementation, UE 165 will transmit an EM signal that will contain data pertaining to UE 165 such as for example cinematic data of UE 165. This signal can be transmitted via Link 2571 directly to UE 155. In one implementation, at least one data block will contain data and parameters pertaining to cinematic data. Said cinematic data may influence augmentation of UE 155 in relation to UE 165.

[00138] In another implementation, UE 165 may provide instantaneous or semi -instantaneous data pertaining to its status, e.g. cinematic data or position data to Server 2300 via Link 2570. UE 155 via Link 2573 may retrieve these data when needed. Alternatively, data provided by UE 165 will affect augmentation related to UE 165. UE 155 will retrieve via Link 2573 only the effects of such influence. In some implementations cinematic data will provide safety features prohibiting augmentation when certain cinematic situations are detected. For example, if UE 155 is worn in a moving car, augmentation can be barred.

[00139] The augmentation functionality may occur according to a Hierarchy. Augmentation Classes 2511, 2512, 2513, 2514 and 2515 represent classes of augmentation such as for example, professional networking, games, dating, sightseeing information, and cinematic data and related information that are associated to a code or an ID. Other classes are possible. The same ID that is received by UE 155 via Link 2571 or Link 2572 may belong to multiple classes and UE 155 could be associated to multiple classes.

[00140] In order to avoid conflicts, a Hierarchy of classes is used so that a class will have priority in the augmentation over another class. User associated to UE 155, entity associated to Emitting Object 2501, user associated to UE 165 and/or an Administrator of the service controlling Server 2300 can establish a hierarchy among classes both to be augmented or displayed. Some rules may involve interrelation of classes. [00141] In another implementation, the hierarchy may involve a hierarchy among users. For example, two users that compete for augmentation by UE 155 may be subordinated to each other. In another implementation, the augmentation hierarchy may involve a seniority system among users, a premium user system, or a points system among users. If more than one equipment is within Angle 2590 and in the field of view of user of UE 155 and they do compete for an augmentation by UE 155, said hierarchy among users and/or apparatuses, and/or classes may resolve which ID UE 155 will augment.

[00142] In certain implementations, once the augmentation associated to an emitting object is outputted, a timer might be initiated so that the same augmentation is not outputted for a period. When two augmentation indicia (IDs) compete, the one that has been displayed most recently may take lower priority.

[00143] In certain implementations, the final augmentation may depend on multiple steps. For example, UE 165 may emit a code or an ID that may fall under Augmentation Class 2511 and said ID be comprised within boundaries defined at Location Memory 2521, e.g. augmentation for a dynamic object such as a mobile phone. The next step could be investigating Augmentation Class 2512, e.g. pertaining to geographical areas, to check for example if the position of UE 155 affects the augmentation. If UE 155 is in one area as defined by Location Memory 2522, the augmentation might be affected. For example, it is allowed.

[00144] The next step could be to check for conditions represented in Augmentation Class 2513. For example, the augmentation could be different according to the fact that user associated to UE 165 is a male or a female. This occurrence can be communicated to Server23 via Link 2570 and Link 2578. The augmentation by UE 155 could be different depending on a male versus a female being associated to UE 165.

[00145] The person skilled in the art will understand that Augmentation Classes 2514 and 2515 could be used as additional modifiers of the ultimate augmentation. Data included may pertain to both the augmenting apparatus UE 155 and/or the emitting apparatus such as Emitting Object 2501 and UE 165 of Fig. 25.

[00146] Examples may include data received from hardware modules such as location modules, gyro modules, and compass modules of both emitting hardware or augmenting hardware. In another embodiment, they may derive from data in user profiles associated with Emitting Object 2501, UE 165 and/or UE 155. Other examples may include conditions and data associated with an administrator of a service that can be inputted in Memory 2302 via Link 2574 and 2575. For example, a company may activate user of UE 165 as an agent for that company. This is described in U.S. 9,286,610 and US 2015-0199547 Al concerning both location based services, activation of agents, and customization of connected objects such as augmented reality equipment. In Fig. 25 Administrator Equipment 2511 represents said administrator. [00147] Once an administrator has activated UE 165 as an agent for a company. UE 155 may output augmentation indicia indicating that user of UE 165 is an agent and a representative for a product or a service of that company. As discussed, with reference to Augmentation Classes and Location Memories, Location Memory 2524 in Augmentation Class 2514 main contain data related to products, authorizations and spatial boundaries associated to agent's UE 165. Class 2515 and Location Memory 2525 may concern preferences for augmentations for products, services, and companies of user of UE 155.

The person skilled in the art will understand that the augmentation indicia that will be outputted by UE 155 may depend from the concurrent occurrence of many parameters and factors where the final augmentation can be the result of a condition tree that may involve, in sequence or in parallel, a plurality of different Augmentation Classes and Location Memories and Parameters in cascade. Conditions, boundaries, parameters, and data in Augmentation Database 2580 contained in Memory 2302 can be updated periodically by administrators, users, and hardware/software systems or equipment. Portions of Augmentation Database 2580 and/or actuation algorithms can be distributed among a plurality of hardware and memory modules.

[00148] FIGURE 26 represents embodiment aspects of the present invention that exemplifies a few concepts where common household appliances are targets devices. Inventive concepts can be extended to other current or future devices that are connected to the internet, e.g., connected cars.

[00149] In certain implementations, UE 165 may incorporate concepts that are described at least in Fig. 1 and 3, where, e.g., antennas having an asymmetric pattern such as dipoles are orthogonally positioned into an handheld device, e.g., a smart phone such that, when at least one dipole receives an RSSI that is proximate to zero or below a predetermined threshold, and at least another orthogonally placed antenna receives an RSSI value that is above a predetermined threshold algorithm determines that a pairing can occur and information or commands can be exchanged. An algorithm can determine that UE 165 is aiming at, e.g., Connected TV 2610 on Axis 2608. Connected TV 2610 is associated to EM Source 2606 that emits an ID representative of Connected TV 2610. In certain implementations, if UE 165 is aiming at Connected TV 2610, UE 165 may download/activate a menu so that Connected TV 2610 is controlled via UE 165.

[00150] In this implementation UE 155 is an UMA (head mounted apparatus) capable of detecting the direction of arrival of emitting sources. UE 175 is a Smartphone that is paired to UE 155 via a Bluetooth connection Link 2672. UE 175 associated to UE 155 can provide functionalities associated to the connected objects that are paired via UE 155. For example, UE 175 can represent content (video/audio) or can provide menu functionalities such that connected objects that are paired via UE 155 are then controlled via UE 175. [00151] In some scenarios, the pairing may not be automatic but it may occur according to predetermined algorithms. UE 165 (or an algorithm on a cloud) may determine that multiple connected devices can be paired and it may provide the user with a list of possible devices with which to pair via Visual Indicator 2604. In another implementation, once UE 165 determines it is aiming at EM Source 2606, it may send a request to Connected TV 2610 via Link 2601 for pairing. Connected TV 2610 may represent via a Visual Indicator 2605 a code that user of UE 165 may have to punch in to enable the pairing. This can be used to avoid connected objects to be inadvertently or maliciously paired with user equipment that should not be paired, e.g. from an adjacent room of a Hotel. Once a pairing has occurred, e.g. with UE 165, EM Source 2606 may cease to transmit so that other UEs cannot pair to the same connected object until UE 165 un-pairs.

[00152] In other implementations, a connected object can be paired with multiple UEs. In one implementation, a device can remain paired only for a period. A manual un-pairing via UE 165 can be used. In another implementation, an un-pairing may occur because another device takes over the control of the connected object. This may occur because that object has a higher status as compared UE 165. Hierarchies of users or equipments can be created so that lower status apparatus will un-pair when a higher status apparatus asks for paring to the same object. In certain implementations, the un-pairing may occur via the same procedure with which the pairing has occurred, namely the alignment of the device to the EM source for a period or the pairing to another device. In certain implementations, when a device is paired, there is no need for alignment to control objects or receive content. In other implementations, the alignment is a requisite. In certain implementations, the first time a UE is paired to a connected object such as Connected TV 2610 or Connected Refrigerator 2618, software can be downloaded to UE 165 or UE 175 or UE 155 so that, for example, the interaction with these connected objects is sped up in the future, having UE already downloaded drivers or interaction menus. Said software may stay on said user equipment permanently or for a predetermined period unless a new pairing or an interaction with the connected object occurs. In certain implementations, the pairing and un-pairing can be instantaneous so that, e.g., by orienting UE 155 toward either Connected TV 2610 on Axis 2607 or by orienting UE 155 toward Connected Refrigerator 2618 (or Emitting Source 2609) on Axis 2611, different menus and information will appear on UE 175 that will concern either the Connected TV or the Connected Refrigerator.

[00153] As a matter of illustration follows an exemplary flow of data, instructions and commands to allow the 1) pairing, 2) usage, and 3) un-pairing of UE 155 & UE 175 with a connected appliance such as Connected Refrigerator 2618. The person skilled in the art will understand that some steps can be skipped, modified or added to augment the usability, security and/or safety. [00154] User of UE 175 (that is paired to UE 155 via Link 2672) activates a software application to activate the algorithms for the direction-detection via antennas strategically positioned on UE 155. User aims UE 155 toward EM Source 2609 on Axis 2611. If UE 175 determines that UE 155 is positioned for at least a period on axis 2611, UE 175 may send a request to Server 2300 via Links 2671, 2670, 143, 144 and Core Network/ Internet 130 and Cloud 905 to download software and/or data to be able to control / receive information concerning the connected object. Once the software/data is downloaded and Server 2300 has given permissions to receive information or to control Connected Refrigerator 2618, in this implementation, there is no need for UE 155 to keep aiming toward Axis 2611. UE 175 may now control or receive information about the connected object. Cloud 905 represents networks equipment. To cause the un-pairing, user of UE 155 & UE 175, UE 155 aims again its device toward Axis 2611 and could be prompted to confirm the un-pairing via a visual prompt. In certain implementations, Connected Refrigerator 2618 may also un-pair from UE 175 if UE 175 pairs with another connected object. Server 2300 may trigger the new pairing and the un-pairing from the old connected object.

[00155] In certain implementations, the same connected object can be paired to more than one device. For example, UE 175 and UE 165 can be paired to the same Connected TV 2610. Visual Indicator 2605, both on Connected TV 2610 and Connected Refrigerator 2618, can produce indications of what commands are produced and/or indicate the user who is responsible for those commands. As discussed, in case of multiple pairings hierarchies and protocols can be followed so that higher-level users may have a higher influence. Many of the techniques applied to mediate the influence of users over connected objects are discussed in patents U.S. 8,489, 119, U.S. 8,909,256, U.S. 9, 148,484, U.S. 9,473,582 of the same inventor. They are incorporated by reference in their entirety. A smart phone or augmented reality glasses can be working according to preferences, settings, permissions and hierarchies that are associated to an individual user.

[00156] The emitting EM source that is associated with connected appliances or connected objects can be turned on or off manually or according to various algorithms and parameters. For example, a movement sensor may sense that a user is in proximity and activate EM Source 2606 and/or EM Source 2609 for at least a predetermined period. If EM Source is part of a Connected Car, said EM source may emit only if the car (connected object) is moving or is active (e.g., engine running) or according other parameters. The person skilled in the art will understand that many different scenarios are possible for different connected objects and purposes. For example, EM Source may start emitting only if receives information about surrounding devices having a capability to pair with them. For example, let us imagine that in a street there are contemporaneously connected taxi and UE 155. Server 2300 may receive information concerning the position of said UE 155 and said connected taxi. One algorithm may determine that user of UE 155 or 165 is trying to pair. For example, 1) UE 165 may signal via Link 2601 that a pairing application has been activated in proximity; 2) UE 165 may signal that it is held steady by user horizontally on a horizontal plane; 3) An inertial measurement Unit/ Compass / Gyroscope 2776 signals that UE 155 is worn, handled, or is steady.

[00157] An exemplary implementation with a connected car may consist in 1) a user aiming his UE toward e.g. a taxi, 2) receiving information about the rating of the driver, 3) requesting the services of the taxi so that the driver receives a position and/or a picture of the requesting user. Alternatively, an implementation with a connected & autonomous car may consist in 1) a user aiming his UE toward said connected & autonomous car, 2) initiating a request for services to said connected & autonomous car to approach by communicating user's current position and user's desired destination via Server 2300.

[00158] FIGURE 27 represents one possible embodiment where UE 155 can be used, e.g., at least to control a connected Light Bulb 2701 or to receive data. The person skilled in the art will understand that this is representative of a universe of applications ranging from controlling settings of appliances, such as thermostats and TVs, to control blinds, open doors, operate elevators and more. Lenses 2720 can be regular glass lenses and the glasses. The information or the menu may appear on UE 175. UE 155 may not have Lenses 2720. Content may be delivered via paired UE 175. In certain implementations, a Mini Display 2700 can be added in the field of view of UE 155. Said Mini Display 2700 can be attached to Lever 2701 that is attached to a hinge of UE 155. Said hinge can be movable or fixed. If it is movable, in one implementation, said Mini Display 2700 can be raised and lowered into the field of view of UE 155. In some implementations, when a visual augmentation is available, UE 155 may provide an acoustic indication.

Augmentation may consist in audible data that are conveyed to user via Audio Modules 2702. In some implementations, audible data is information about people or objects to help, for example, users who are visually impaired using the breadcrumbs technique described in Fig. 23. Some users may broadcast an ID that is associated to their name via their smart phone or a wearable badge so that when a user who is wearing UE 155 is aiming at those users, he will be able to hear, via Audio Modules 2702, the name of said user or other information associated to said user via Link 2771, 2770, 143, 144. This can be accomplished by UE 155 signaling to Server 2300 that it is aligned with EM source and Server 2300 directing hardware associated with EM Source to deliver its content. Art 2781 can be any other object such as a picture, a statue or other.

[00159] In certain implementations, UE 155 or UE 175 may pre-store content in a memory module and deliver it to user of UE 155 only when UE 155 is aligned with the EM source or fulfills other conditions as, e.g., the ones discussed in Fig. 25. Alternatively, a pre-fetch-based scenario can be used. A user entering a room will start collecting IDs of nearby iBeacons via his UE 155 (or UE associated to the HMA via Bluetooth such as UE 175). Those IDs will be reported to Server 2300 that will send the content associated to those IDs already to UE 155 (or UE 175). Only when user of UE 155 fulfills the directionality condition, UE 155 (or UE 175) will deliver the content to user. In other implementations, the content can be retrieved locally directly from emitting objects in connectivity mode.

[00160] An exemplary scenario is provided with objects that can be recognized by a visually impaired person via the directional-based technology coupled with audio augmentation. In one implementation, the scenario is a museum and the glasses can be used to provide an explanatory audio file about Art 2781 to a visitor whenever he aims UE 155 at EM Source 2782. In this implementation, Art 2781 is an unconnected object and EM Source is an ID emitter where the ID is associated to content stored in a memory. As discussed with reference for example to Fig. 25, the audio file that can be received at UE 155 about Art 2781 does not need to be the same for all users. The audio file that is played by UE 155 or UE 175 can be in the language of the user according to a user profile that is stored in Memory 2302. In case of a connected object such as a monitor, content can be adapted to the user profile.

[00161] Returning to the example of Light Bulb 2701, in one implementation, the audible data that is received via Link 2770 and 2771 can be instructions on how to operate the appliance that is in line of sight or field of view of a user wearing UE 155. In certain implementations, EM source that is associated with Light Bulb 2701 is placed nearby the appliance such as, for example, EM Source 2709. Visual Indicator 2711 may provide a visual feedback and/or instructions to user when UE 155 is paired with Light Bulb 2701.

[00162] In other implementations, connected object and EM Source are not placed in the same place. For example, Light Bulb 2701 can be controlled and operated when user aims UE 155 at Control Panel 2793 that is hosting EM Source 2798 and Visual Indicator 2790. In this case, user of UE 155 may not aim at the appliance but to Control Panel 2793 and it may receive content on how to operate the appliance via Visual Indicator 2790 or, as discussed, via acoustic feedback delivered via Link 2771.

[00163] As a basic example of the technology, here follows one of the many possible logical flows on how to dim and/or turn on and off Light Bulb 2701. User aims UE 155 toward EM Source 2709 for a predetermined period. A system of antennas (Antennas 257, 258, 259) with asymmetric radiation patterns receives EM energy from EM Source 2709. If Antenna 259 and 258 receive RSSI values from said source that are below predetermined thresholds while Antenna 257 receives values above a predetermined threshold it may proceed to the next steps. UE 155 via Links 2771, 2770, 143, 144 communicates to Server 2300 that it is requesting control of Light Bulb 2701 by communicating the ID received by EM Source 2709. If allowed by permissions and hierarchical rules an algorithm will allow the pairing of UE 155 with Light Bulb 2701. This pairing can be communicated to user via Visual Indicator 2711 by means of Links 144, 143, 2772, 2773 so that, for example, a light may turn from red to green when the pairing is active.

[00164] In certain implementations, to control Light Bulb 2701 software running on UE 155 must at least initially determine that UE is aimed at EM Source 2709. If said software determines that said condition of alignment is satisfied it may ,e.g., translate up-down and left-right movements of the head into commands that are sent to Server 2300 first and to Light Bulb 2701 through Links 2771, 2770, 143, 144, 2772, 2773. As an example, an Up movement of the head (i.e. UE goes from alignment with EM Source to UP position) that is recorded by a Compass / Gyroscope in UE 155 may correspond to a command to Light Bulb 2701 to turn on. Vice versa, a down movement from alignment to Down position may correspond to a command to Light Bulb 2701 to turn off. The dimming of the light may correspond to movements to the left or to the right of UE 155. A UX-UI expert will understand that the possibilities are numerous. For example, Visual Indicator 2711 can display submenus / instructions so that the orientations of UE 155 will allow the navigation into complex menus. Voice commands can also be integrated so that, e.g., when a voice command is coupled with the alignment of UE 155 to an EM Source linked to a connected device said connected device would obey to the voice commands. Voice commands may also work after the initial pairing. User may also aim at Light Bulb 2701 for a predetermined period, user may receive a green visual indication that light bulb is ready to receive a command. Available commands can be visualized via Visual Indicator 2711. Light Bulb 2701 may turn off when user pronounces the word "off.

[00165] Another example is an elevator equipped with Control Panel 2793. Visual Indicator 2790 may provide a visual / audio feedback that UE 155 is paired and that floors 1 through 10 are available. User pronounces "ten" and said command will translate into a command for the elevator to move to the tenth floor. Visual feedback, options and menus, can be integrated with audio indicia.

As discussed, the possibilities for implementations are numerous and the examples are just explanatory. For example, Server 2300 does not need to be remote or even exist. Connected objects, unconnected objects and/or system intelligence can be aggregated in the same location. Software enabling voice recognition, movement recognition, decisional algorithms, can be distributed accordingly. For example, the voice command can be translated into an actuation command in Server 2300, UE 155 or Control Panel 2793 or elsewhere. Profiles, permissions, restrictions, algorithms, processing functionalities and other can be distributed across the system, from UE to Server 2300 or concentrated in a few modules within the hardware that provides content or functionalities. [00166] Permissions to operate or receive information about connected objects or unconnected objects (as in the case of Art 2781), modalities of operations of said connected/unconnected objects, hierarchies of operation, personalization of menus or commands or feedbacks can all derive from profiles associated to users or administrators. For example, not all Objects can be available to all users. Modalities of interaction, permissions or information can be different for different users. One way to associate UE 155 with a user profile is described in Patent Application US 2015-0199547 Al that is incorporated by reference herein. Let us imagine for example that user is now in proximity of an unconnected object such as Art 2781. UE 155 has been paired with said user' profile. When UE 155 is aiming at EM Source 2782, UE 155 may send to Server 2300 both an ID related to Art 2781 and an ID related to said user. A datagram contained in Memory 2302 may associate settings, permissions, or preferences of said Art 2781 in relation to user. If one of the preferences in the profile is for example the German language, Server 2300 will select a German audio file to be played via said Audio Modules 2702 or via UE 175 that is paired to UE 155. In different implementations, for the audio file to be played, UE 155 may or may not need to maintain its aiming toward EM Source 2782 once the pairing has been established. Emitting objects might be part of groups so that, for example, once permissions and preferences have been established with one representative emitting object they are established for all of the objects in the group. Also, as discussed before, once an authorization or pairing has been established with one of the emitting objects of the group a pre-fetching can occur.

[00167] The same concept can be applied concerning areas and events. UE 155 may pre-fetch content associated to users or objects that are associated to a location or to an event so that the delay between aiming and outputting of the augmentation is minimized. The same concept can be applied using IDs of surrounding emitting objects such as Bluetooth sources of nearby users. UE 155 may preload content associated to those sources for a smoother user experience. UE 155 may also provide indications to user on where to aim with his HMA or Smartphone to output that content.

[00168] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. While the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications that may be made without departing from the scope of the present invention. Plurality means one or more.