Apparatus for moving relay interference mitigation in mobile, for example, cellular communication networks

The present invention relates generally to mobile communication networks and more particularly to mobile communication networks whose base stations are not stationary.

BACKGROUND FOR THIS DISCLOSURE

Published PCT Application No. WO2011092698 describes a cellular communication system with moving base stations and methods and apparatus useful in conjunction therewith.

“LTE, The UMTS Long Term Evolution: From Theory to Practice”, by Wiley, is a treatise on certain aspects of mobile (LTE, e.g.) communications. Certain of the prior art drawings in this application are taken from this treatise, e.g. from the 2011 version.

The disclosures of all publications and patent documents mentioned in the specification and materials appended thereto, and of the publications and patent documents cited therein directly or indirectly, are hereby incorporated by reference.

SUMMARY OF CERTAIN EMBODIMENTS

Certain embodiments of the present invention seek to provide apparatus and methods useful for enhanced moving relay interference mitigation in mobile e.g. cellular networks.

Certain embodiments of the present invention seek to provide moving relay interference mitigation in mobile e.g. cellular networks using Time and Frequency Separation which may be algorithmic.

Certain embodiments of the present invention seek to provide moving relay interference mitigation in mobile e.g. cellular networks using Separation Via a Dedicated Scheduler.

Certain embodiments of the present invention seek to provide moving relay interference mitigation in mobile e.g. cellular networks using Separation in Time Using MBSFN Channels.

Certain embodiments of the present invention seek to provide moving relay interference mitigation in mobile e.g. cellular networks using Separation Via a Dedicated Scheduler Integrated with MBSFN-based separation.

Certain embodiments of the present invention seek to provide an improved radio resource subsystem which may reside within a moving relay’s relay resource manager.

Certain embodiments of the present invention seek to provide alternative schemes for using radio resources allocations/manipulations to mitigate interferences which might otherwise hamper operation of the moving relays network. Radio resources may include some or all of: center frequency, bandwidth, time (e.g. frame timing), transmitted power, antenna beam. Using certain radio resources allocations/manipulations to mitigate interferences in conventional networks which lack moving relays, is known.

Certain embodiments of the present invention are particularly suited to moving relays which are more compact than conventional relays such as LTE standard or artist4G relays in which, often, only 60-80dB of isolation/separation are needed.

Certain embodiments of the present invention provide isolation/separation in a moving relay network at a level of 100-120dB. (whereas in others only 60-80dB is needed).

Also provided is a computer program comprising computer program code means for performing any of the methods shown and described herein when said program is run on a computer; and a computer program product, comprising a typically non-transitory computer-usable or -readable medium or computer readable storage medium, typically tangible, having a computer readable program code embodied therein, said computer readable program code adapted to be executed to implement any or all of the methods shown and described herein. It is appreciated that any or all of the computational steps shown and described herein may be computer-implemented. The operations in accordance with the teachings herein may be performed by a computer specially constructed for the desired purposes or by a general purpose computer specially configured for the desired purpose by a computer program stored in a typically nontransitory computer readable storage medium.

Any suitable processor, display and input means may be used to process, display e.g. on a computer screen or other computer output device, store, and accept information such as information used by or generated by any of the methods and apparatus shown and described herein; the above processor, display and input means including computer programs, in accordance with some or all of the embodiments of the present invention. Any or all functionalities of the invention shown and described herein, such as but not limited to steps of flowcharts, may be performed by a conventional personal computer processor, workstation or other programmable device or computer or electronic computing device or processor, either general-purpose or specifically constructed, used for processing; a computer display screen and/or printer and/or speaker for displaying; machine-readable memory such as optical disks, CDROMs, magnetic-optical discs or other discs; RAMs, ROMs, EPROMs, EEPROMs, magnetic or optical or other cards, for storing, and keyboard or mouse for accepting. The term process as used above is intended to include any type of computation or manipulation or transformation of data represented as physical, e.g. electronic, phenomena which may occur or reside e.g. within registers and /or memories of a computer or processor. The term processor includes a single processing unit or a plurality of distributed or remote such units.

The above devices may communicate via any conventional wired or wireless digital communication means, e.g. via a wired or cellular telephone network or a computer network such as the Internet.

The apparatus of the present invention may include, according to certain embodiments of the invention, machine readable memory containing or otherwise storing a program of instructions which, when executed by the machine, implements some or all of the apparatus, methods, features and functionalities of the invention shown and described herein. Alternatively or in addition, the apparatus of the present invention may include, according to certain embodiments of the invention, a program as above which may be written in any conventional programming language, and optionally a machine for executing the program such as but not limited to a general purpose computer which may optionally be configured or activated in accordance with the teachings of the present invention. Any of the teachings incorporated herein may wherever suitable operate on signals representative of physical objects or substances.

The embodiments referred to above, and other embodiments, are described in detail in the next section.

Any trademark occurring in the text or drawings is the property of its owner and occurs herein merely to explain or illustrate one example of how an embodiment of the invention may be implemented.

Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions, utilizing terms such as, processing, computing, estimating, selecting, ranking, grading, calculating, determining, generating, reassessing, classifying, generating, producing, stereo-matching, registering, detecting, associating, superimposing, obtaining or the like, refer to the action and/or processes of a computer or computing system, or processor or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories, into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices. The term “computer” should be broadly construed to cover any kind of electronic device with data processing capabilities, including, by way of non-limiting example, personal computers, servers, computing system, communication devices, processors (e.g. digital signal processor (DSP), microcontrollers, field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc.) and other electronic computing devices.

The present invention may be described, merely for clarity, in terms of terminology specific to particular programming languages, operating systems, browsers, system versions, individual products, and the like. It will be appreciated that this terminology is intended to convey general principles of operation clearly and briefly, by way of example, and is not intended to limit the scope of the invention to any particular programming language, operating system, browser, system version, or individual product.

Elements separately listed herein need not be distinct components and alternatively may be the same structure.

Any suitable input device, such as but not limited to a sensor, may be used to generate or otherwise provide information received by the apparatus and methods shown and described herein. Any suitable output device or display may be used to display or output information generated by the apparatus and methods shown and described herein. Any suitable processor may be employed to compute or generate information as described herein e.g. by providing one or more modules in the processor to perform functionalities described herein. Any suitable computerized data storage e.g. computer memory may be used to store information received by or generated by the systems shown and described herein. Functionalities shown and described herein may be divided between a server computer and a plurality of client computers. These or any other computerized components shown and described herein may communicate between themselves via a suitable computer network.

BRIEF DESCRIPTION OF THE DRAWINGS AND APPENDIX

Figs. 3 - 5, 9, 17, 19 - 22, 27 - 32, 40 - 47, 63, 67 - 70, 78, 83 - 86, 87 88 illustrate various components of the present invention which may be provided together or separately, according to certain embodiments.

Appendix I is a complete copy of specification, claims and figures of Israeli

Patent Application No. 218046 A multi-directional relay architecture and apparatus and methods of operation useful in conjunction therewith filed 12 February 2012.

Certain of the prior art drawings in this application such as Figs. 20a-b, 31, 40 41, 67 are taken from “LTE, The UMTS Long Term Evolution: From Theory to Practice”, by Wiley, e.g. from the 2011 version.

Computational components described and illustrated herein can be implemented in various forms, for example, as hardware circuits such as but not limited to custom VLSI circuits or gate arrays or programmable hardware devices such as but not limited to FPGAs, or as software program code stored on at least one intangible computer readable medium and executable by at least one processor, or any suitable combination thereof. A specific functional component may be formed by one particular sequence of software code, or by a plurality of such, which collectively act or behave or act as described herein with reference to the functional component in question. For example, the component may be distributed over several code sequences such as but not limited to objects, procedures, functions, routines and programs and may originate from several computer files which typically operate synergistically.

Data can be stored on one or more intangible computer readable media stored at one or more different locations, different network nodes or different storage devices at a single node or location.

It is appreciated that any computer data storage technology, including any type of storage or memory and any type of computer components and recording media that retain digital data used for computing for an interval of time, and any time of information retention technology, may be used to store the various data provided and employed herein. Suitable computer data storage or information retention apparatus may include apparatus which is primary, secondary, tertiary or off-line; which is of any type or level or amount or category of volatility, differentiation, mutability, accessibility, addressability, capacity, performance and energy use; and which is based on any suitable technologies such as semiconductor, magnetic, optical, paper and others.

ר

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

Appendix I is a complete copy of specification, claims and figures of Israeli Patent Application No. 218046 A multi-directional relay architecture and apparatus and methods of operation useful in conjunction therewith filed 12 February 2012. Aspects of this technology may be useful in implementing the following alternatives, i.e. Alternative 3 or 4 as described herein. Also, terminology herein may for example be defined in accordance with the teachings of Appendix I.

Published PCT Application No. WO2011092698 describes a cellular communication system with moving base stations and methods and apparatus useful in conjunction therewith. It is appreciated that mutatis mutandis, any suitable mobile or cellular communication protocol may be employed. This technology, or other known technologies in which the base station or access point is mobile, optionally in conjunction with the teachings of Appendix I herein, is also termed herein MAN (Moving Access Network) technology. A moving relay according to such technology, except as described herein, including the following co-located components: base station and mobile device functionalities and a relay resource manager (rRM) including a radio resource subsystem having a radio resource manager, is also termed herein a MAN, or a MAN node. The term “co-located” is intended to include any apparatus in which the above components all move together such that their relative locations remain constant or that are all physically connected.

It should be highlighted that all techniques, methods and examples described in the following can be implemented also in a network in which some or all relays are static. Fig. 3 illustrates one embodiment of a DL Physical layer Fig. 4 illustrates one embodiment of a UL Physical layer

Fig. 5 illustrates one embodiment of Channels (e.g. transport and Phy) and Layers.

<td> Radio link</td><td> Channel type</td><td> Channel</td><td> Physical Channel</td><td> Purpose</td>

<td> Uplink</td><td> TrCh (between MAC and Phy)</td><td> UL-SCH</td><td> PUSCH</td><td> Carries user UL data</td>

<td></td><td></td><td> RACH</td><td> PRACH</td><td> UE establish connection</td>

<td></td><td> Control Information</td><td> UCI (Uplink Control Information)</td><td> PUSCH</td><td> Scheduling request, HARQ, CQI</td>

<td></td><td></td><td></td><td> PUCCH</td><td></td>

<td> Downlink</td><td> TrCh</td><td> DL-SCH</td><td> PDSCH</td><td> Carries user UL data / RRC</td>

<td></td><td></td><td> BCH</td><td> PBSCH</td><td> MIB</td>

<td></td><td></td><td> PCH</td><td> PDSCH</td><td> Paging</td>

<td></td><td></td><td> MCH</td><td> PMCH</td><td> Multicast</td>

<td></td><td> Control Information</td><td> CFI (Control Format Indicator)</td><td> PCFICH</td><td> Number of symbols are used for PDCCH in a subframe</td>

<td></td><td></td><td> HI( HARQ Indicator)</td><td> PHICH</td><td> Ack/Nack feedback to the UE for the uplink blocks</td>

<td></td><td></td><td> DCI (Downlink Control Information)</td><td> PDCCH</td><td> PUSCH grant, PDSCH assignment,</td>

<td></td><td></td><td></td><td> P-SS S-SS</td><td> Synchronization</td>

<td></td><td></td><td></td><td> RS</td><td> Channel estimation</td>

Referring now to Fig. 9, a MAN (Moving Access Network) refers herein to a network which includes at least one moving relay. MAN includes moving relay nodes that operate adjacent to each other. Each node typically implements two transmit/receive channels over the same frequency band (also known as in-band backhauling):

• Access channels (from/to an LTE subscriber) and/or • Backhauling channels (from/to the next LTE site/node/relay/BS)

This proximity of channels in each moving relay and of adjacent Moving relays generates several mutual interference types:

1. From the DL transmit channel of the rBS to the rUE receiver and/or

2. From the UL transmit channel of the rUE to the rBS receiver and/or

3. From the DL channel of the rBS to DL channels of adjacent Moving relays (at UEs receivers) and/or

4. From the UL channel of the rBS-served UEs (mobile devices) to UL channels of adjacent Moving relays UEs (at rBSs/BSs receivers).

In figure 9 interference types 1-4 are shown (as dashed bold arrows). It can be seen that interference type 1 can happen between DL transmitted by the rBS and rUE reception from either a static BS or from other relay rBS. It can be also seen that interference type 2 can happen between UL transmitted by the rUE and rBS reception from its served UE(s) or rUE(s).

The main objective is: Reduce some or all of the above mutual interferences and enable the proper operation of all Moving relays. In the rest of the description we will focus on the first two interference types as the latter two are partly handled by the standard and the base-stations.

The interference can affect all type of channels of the protocol/standard being used. The interference reduction can be realized by enhancing the isolation/separation between the backhauling and access channels used by the relay. In example, in LTE, Signals and Channels that their isolation needs to be enhanced in the DL Physical Layer may include some or all of:

• P-SS, s-ss • Reference Signal (DMRS, CRS) • PDSCH • PBCH • PDCCH • MBSFN if PMCH is employed • PCFICH • PHICH

In example, in LTE, Signals and Channels that their isolation needs to be enhanced in the UL Physical Layer may include some or all of:

• DMRS • SRS • PUSCH • PUCCH • PRACH

It should be noted that at moving relay the problem if mutual interference can be more serious than in the case of static relays because in the case of moving relays the scenario is dynamic and changing all the time. In addition, in the case of moving relays, the size of the power amplifier and antenna of the rBS can be smaller that the power amplifier and antenna that can be mounted on static infrastructure, a fact that can make interference type 2 more severe (especially when the power amplifier and antenna of rBS and rUE are similar in their performance). In the case of multi-hop (multi-layers hierarchical) network there such interference can occur between two adjacent relays, in addition to interference between static BS and relay.

To separate between the access channels and the backhauling channels, it may be necessary to isolate between them to more than 100 dB.

Any of the following methods can be used to reach the required isolation:

• Separation/isolation in space and frequency • Separation/isolation in time using a dedicated scheduler • Separation/isolation in time using MBSFN channels • Combinations of some, part of or all the above methods.

To separate access channels (3+4 interference types mentioned above), it is customary to solve the problem using mechanisms built-in in the standards or in the equipment, for example:

• Intelligent scheduler • Placing the base station in proximity to the mobile devices • Allocate frequencies according to the distance from the base station • SON (Self Organizing Network)

There are several ways to mitigate type 1 and/or 2 interferences. Each of the following paragraphs describes an example of alternative for that, and states briefly some guidelines and features of each solution. In the rest of the detailed description, each of these solutions will be elaborated.

Alternative 1 - Separation in Space and Frequency

The required isolation may be accomplished with some or all of the following three components:

50-65dB separation can be achieved by - antenna assembly that separates between the access and backhaul channels/antennas.

30-35dB separation can be achieved by - interference cancelling mechanism that can cancel the interference signal and extract the wanted signal.

30-40dB separation can be achieved by - managing frequency resources, i.e. separating in the frequency domain between access and backhauling channels.

Alternative 2 - Time Separation Using a Dedicated Scheduler

Implementing dedicated scheduler in the base station functionality (rBS) of the relay.

The scheduler may split individual frequency and time resources (resource blocks = RBs) among channels having a potential for interference.

For example: rUE can transmit over the uplink in the RB(s) which rBS does not listen to and vice versa; that is, rBS can transmit over DL in RB(s), which rUE does not listen to (i.e. which are not allocated for the rUE).

The solution may require coordination between the static base stations and the mobile base stations (i.e. rBSs) that interface externally with the scheduler.

Alternative 3 - Separation in Time Using MBSFN Channels

Using standard MBSFN channels that enable sending broadcast data for mobile

TV transmissions.

Dividing the frame into 10 subframes for backhauling and access.

Use of the MBSFN subframes as a backhauling subframe (downlink) for transmitting messages upstream and downstream.

May require using base stations functionality (rBS) and mobile devices (rUE) that support MBSFN (i.e. as of 3GPP LTE Release 9).

May require developing dedicated MAC (medium access control) and network communication layers over the MBSFN PHY (physical) layer.

Alternative 4 - Integration of a Dedicated Scheduler and MBSFN

Combination of alternatives 1, 2 and 3.

Using dedicated scheduler for:

• Dynamically allocating time-deflected (shifted) subframes in DL • Dynamically allocating PUSCH and PUCCH channels

Using MBSFN channels as almost blank subframes in DL (due to lack of transmission of CRS in MBSFN).

Additional separation in space and frequency (Alternative 1) can be added to increase the performance (i.e. enlarging the range and coverage area).

Use of an antenna and IC mechanisms to isolate control and CRS messages.

It may be possible to waive the need to deflect (shift) time in DL.

Alternative 1 in detail - Time and Frequency Separation

As mentioned above, the required isolation may be accomplished with some or all of three components: special antenna assembly, interference cancelling mechanisms and managing frequency resources.

Fig. 17

Separation in Time and Frequency - Special Antenna Assembly

The solution is based on the making isolation and separation between access and backhauling antennas in the same assembly, by using several physical dimensions separation.

In the figure a result of simulation of such a special antenna assembly is shown.

The X-axis is the frequency dimension and the Y-axis is the isolation between the access and backhauling antennas. It can be seen that in this realization, at the lower frequencies (i.e. 2-2.3 GHz) and at the higher frequencies (2.66-3GHz), an isolation of more than 50dB can be achieved.

Separation in Time and Frequency - Interferences Cancellation

Using signal processing interference cancellation technology to cancel interferences. Known such techniques can reach cancellation capabilities of up to 35 dB.

Fig. 19a+19b

Separation in Time and Frequency - Frequencies Management

The spectrum is allocated to several frequency bands that optionally include a guard band.

Fig. 19a: Example of 4 x 5 MHz = 20 MHz

Distribution into color graphs, each color representing a frequency band

In 5 MHz, there are effectively two colors (black/solid and dashed)

A difference of 5 MHz may be required between neighbors if no adequate filters are used.

It is possible to resolve this by dividing into more colors (with less bandwidth) as depicted in fig. 19b.

As a result of the moving relays scenario, it may be necessary to use a method to allocate frequencies dynamically caused by the proximity of neighboring moving relays approaching the relay and operating with the same color (center frequency). These methods are some of the embodiments of this invention. As an example, a relay that can monitor two adjacent relays, can detect that those two adjacent relays are operating in the same center frequency, and coordinating them so that one of them will change its center frequency to a free center frequency.

Figs. 20a-b: (From Artist4G d3.4_v2.0)

Separation in Time and Frequency - Frequency Separation

Fig. 21 (From Artist4G d3.4_v2.0)

Separation in Time and Frequency - Frequency Separation and antenna isolation requirement

With only one antenna capable of an isolation of 65 dB, it is possible to reach a range up to 500 m; with 85 dB it is possible to reach a range of 1.5 km (SINR = 6 dB). Again, the analyzed scenario of standard static relay having only one layer of relays (connected to the static base stations) doesn't require high isolation as the case of moving relays, especially i.e. in a hierarchical multi-hop topology.

Fig. 22

Separation in Time and Frequency - Interfacing with a Static Network

If the static base stations are allocated 5 MHz, then it is possible to treat the base station as a relay station (case #1).

Since the BCH channels are in six central RBs, than i.e. 5 MHz (or 1.4 or 3 MHz) allocations not residing in the center 1.4 MHz of the SBS bandwidth can be made for the relays, and 20 MHz BS bandwidth may remain for the static network (case #2).

In some cases, the separation may not be enough because of interference to the PDCCH of the SBS (Static BS).

Separation in Time and Frequency may be characterized by some or all of the following:

May require changes to only L3 of rBS and rUE

Supports simple interface with the static network

May require changing the frequency of the base station functionality (while in operation and serving UEs) due to the dynamic scenario and the possibility for frequency collision between moving relays that approach each other.

Special antennas assembly.

Alternative 2 in detail - Separation Using a Dedicated Scheduler

Fig. 27

Dedicated Scheduler

The scheduler is responsible for allocating RB to UL and DL by the base station With a dedicated scheduler, it is possible to separate between the backhauling and access channels in time and frequency

The example has four users and two rUEs allocated to each TTI in different base stations

Fig. 28:

Dedicated Scheduler - Synch signals and PBCH Channel

In the first subframe of each frame of the main six RBs of the allocated bandwidth Without significant separation, rUE cannot synchronize and even receive BCH channel of neighboring stations because rBS interferes with its BCH channel

It is possible to separate by shifting the subframe of access and backhauling so no overlap between Synch signals and BCHs are apparent.

Fig. 29

Dedicated Scheduler - PDCCH Channel

The PDCCH channel is present through the entire bandwidth; therefore rBS may interfere with the reception of the PDCCH of rUE from another rBS

It is possible to solve this problem conventionally by separating in time only (subframe or symbol resolution), or by cancelling the PDCCH in some subframes using interference cancellation techniques.

Fig. 30

Dedicated Scheduler - PDCCH Channel

It is possible to solve this problem conventionally by moving 15-16 symbols in each relay with respect to the transmission of the other relays nearby.

Suitable for three colors in MIMO 2*2 and more colors in SISO mode.

Interferences of RS to B-CH and P-SS can be resolved using orthogonal antenna ports.

Fig. 31

Dedicated Scheduler - R-PDCCH

To prevent shifting or cancellation of certain PDCCH symbols, the standard added R-PDCCH. R-PDCCH is in a fixed RE in the PDSCH channel

R is relevant to Rei. 10 and up

Fig. 32

Dedicated Scheduler - PUCCH • In PUCCH, it is possible to separate in both frequency and in time • In RACH, it is possible to separate in both time and frequency (6 RB) • In SRS, it is possible to separate in time only (as it may be required to make measurements over the entire frequency)

Dedicated Scheduler - Coordination • It may be necessary to coordinate among the base stations of the relays, and between them and the static stations to send messages uplink and downlink o It may be necessary to synchronize the time between base stations to properly operate the scheduler in each o It may be necessary to adjust free slots to transmit PDCCH and PBCH o It may be necessary to adjust free subframes to transmit access and backhauling o A dedicated adjustment channel may be required to allocate channels and transfer allocations at a rate that is suitable for the scheduler

Dedicated Scheduler - Uplink Adjustment d in the uplink, transmission occurs by receiving a grant from the base station; it may be necessary to coordinate between the base station that serves rUE and [the one that serves] rUE and rBS o It is possible to allocate static/semi-static GBR/SPS channels in advance

Dedicated Scheduler - Interfacing with a Static Network

O If it is required to connect the rUE to the static network and it is not possible to control the scheduler of its base station:

o It is possible to add an IC mechanism in rUE and rBS to cope with interferences in ODCCH and PUCCH and move PBCH in time &amp;#9632; It is not definite that the IC mechanism provides the required separation o It is possible to add a UE proxy similar to the MBSFN solution o It is possible to add a base station whose scheduler can be controlled o Using a different band or small deviation (within the standard) in frequency to add separation

Separation Using a Dedicated Scheduler may be characterized by some or all of the following:

Use of nearly standardized channels

Includes the possibility for idle in rUE

Possible separation in the UL frequency provided it is possible to control the allocation of PUCCH

May require changes in PHY or relying on advanced standards (Rei. 10)

Alternative 3 in detail - Separation Using MBSFN for Transmission

Fig. 40

MBMS Architecture

Fig. 42

Distribution into Subframes d The standard defines subframes that can handle MBSFN transmissions o Some of the subframes contain control signals; therefore, they can only transmit access (subframes 0,4,5,9 in FDD and 0,1,2,5,6,9 in TDD).

Fig. 43

Frame Structure d The MBSFN channel takes an entire subframe, except for PDCCH o The MBSFN channel has unique DMRSs; there is no transmission of CRSs that are in the PDCCH area

Fig. 44 is generally self-explanatory.

Fig. 45

Using MBSFN -DL

Fig. 46

Using MBSFN -UL

Fig. 47

Using MBSFN - Example of reuse of subframes (#3,7,9) between two separated groups of relays (two right-side relays and two left-side relays) that both are connected to the static base station.

MBSFN Separation - Dedicated Communications Layer d A dedicated communications layer may be required on the multicast radio bearer;

it may be used to transmit backhauling messages

Q The communications layer includes MAC and network layers similar to the MAC layers in a mesh network d It is possible to make channel measurements based on the MBSFN’s RS or via another method (TPC, DFS) in higher layers

MBSFN Separation may be characterized by some or all of the following:

Does not affect the bandwidth of UL

Q May require one amplifier for rBS only

O Significant flexibility in color reuse

Q Does not require full rUE but mainly an MBSFN receiver

May require time synchronization between moving relays

Q Addition of a UE proxy

Q Implementing dedicated MESH-type Layers 2 + 3

Implementing dedicated handover mechanisms

Alternative 4 in detail - Integrated Solution: Dedicated Scheduler, Empty MBSFN and Space and Space Separation

Architecture

MBSFN Separation

Similar to Alternative 2

With the possibility of making measurements more easily in backhauling subframes

May require time synchronization between moving relays

May require base stations that support MBSFN

May require interfaces to modify symbols timing

Comparison between the Alternatives may yield some or all of the following differences:

<td></td><td> Frequency + Space</td><td> Dedicated Scheduler</td><td> MBSFN</td><td> Integrated</td>

<td> Hardware requirements may include:</td><td> Dedicated antenna, IC, base station and standard dongle</td><td> Base station, dedicated dongle + Re (elCIC), synchronization clock</td><td> MBSFN-based case station and dongle, synchronization clock</td><td> Dedicated base station and dongle, elCIC + Re (MBSFN), synchronization clock</td>

<td> Required features may include:</td><td> Dedicated antenna; manager for allocating frequency resources</td><td> Dedicated scheduler and interfaces for BS and rUE Manager for managing allocation of RBs in DL and UL Solution for synchronization and BCH channels</td><td> Dedicated scheduler + MAC Manager for managing the allocation of subframes</td><td> Dedicated scheduled and interfaces for BS and rUE Manager for managing allocation of RBs in DL and UL Solution for synchronization and BCH channels</td>

Comparison between the Alternatives may yield some or all of the following differences:

<td></td><td> Frequency and Space</td><td> Dedicated Scheduler</td><td> MBSFN</td><td> Integrated</td>

<td> Operation with an existing network</td><td> Simple</td><td> May require coordination with a scheduler of the static network May require scheduler with a blank subframe</td><td> May require UE proxy</td><td> May require coordination in UL In DL it is possible to rely on the MBSFN map</td>

<td> Characteristi css</td><td> Changes in rUE, rBS only in Layer 3 Standard SBS Use of DL for DS and ULfor US</td><td> Use of DL in DS and UL in US Flexibility of bitrates Possible separation in the UL frequency provided it is possible to control the allocation of PUCCH</td><td> May require an amplifier in rBS only No need for rUE, mainly an MBSFN receiver Use of DL for DS and DL for US (does not affect UL) Based on the standards Very flexible in reuse colors</td><td> Similar to solution 2 including improvement in RS measurements in channels defined as MBSFN almost blank subframe</td>

Comparison between the alternatives may yield some or all of the following differences:

<td></td><td> Frequency and Space</td><td> Dedicated Scheduler</td><td> MBSFN</td><td> Integrated</td>

<td> Disadvantages</td><td> Dedicated antenna and IC Low bandwidth (rigid distribution of the frequency) Dedicated solution to replace the main frequency</td><td> Changes in rUE, rBS in Layer 1 May require synchronization between all base stations (rBS, SBS) May require (rBS, sBS) scheduler with blank subframe Separation in DL only at the time level</td><td> May require for MBSFN supported in Rei. 9 May require synchronization between all base stations (rBS, SBS) Addition of rUE proxy for the static network Addition of dedicated Layers 2 + 3 May require Dedicated measurement and handover mechanisms Separation in time only</td><td> May require for MBSFN supported in Rei. 9 May require synchronization between all base stations (rBS, SBS) May require interfaces to change timings to Layer 1 and rBS</td>

Elaboration of Alternatives 3 and 4

Separation in Time through MBSFN Channels for Relaying, according to certain embodiments, is now described.

Fig. 63

Alternative 3

Alternative 3 - Using MBSFN -DL: e.g. as per Fig. 45.

Fig. 46 illustrates Alternative 3 - Using MBSFN -UL and an example.

Fig. 67

MBMS in LTE and the allocation of functionalities to the different parts of the relay (rBS and rRM).

Fig. 68

Alternative 3 - rRM Structure and interfaces.

Fig. 69

Alternative 3 - Local Service of two relays.

Fig. 70

Alternative 3 - B ackhauling Support. In this example a link between two mobile devices each connected to different relay is described.

® Step 0 - payload is sent over the standard air interface from mobile device to rBS.

d Step 1 - the payload is then transferred from the rBS over the SI interface to the Virtual Core Subsystem of the relay located inside the rRM. The Virtual Core Subsystem then transfers the payload to the P-GW inside the Stand-Alone Subsystem (local core).

O Step 2 - The P-GW understand that this payload is destined to different core and then is encapsulate it and send it to the target core. This message is then transferred to the Virtual Core Subsystem and from there it is routed internally to the Tunneling Subsystem (S/S).

Q Step 3 - The Tunneling S/S first add a MESH header with the destination node of the message. In addition, it by questioning the Routing and QOS S/S and Radio Resource S/S, determines the radio subframe (time-slot) and MRB it should use and add the appropriate MBSFN Header. Then it transfer the message to the rBS for transmission in MBSFN channel.

O Step 4 - The rBS decapsulate the MBSFN header and transmit the rest of the message over the required MBSFN subframe. This message is received by the destined rUE, which transfers the message to the Tunneling S/S.

d Step 5 - The Thuneling S/S decapsulate the MESH header and determines that the destination is the Stand-Alone S/S (local core). Then it transfers the rest of the message to the Stand-Alone S/S through the Virtual Core S/S.

O Step 6 - The Virtual Core S/S then transfers the data, using GTP standard tunnel to the local rBS.

Q Step 7 - The rBS transmit the payload over the standard air interface.

Alternative 3 - Tunneling Subsystem is characterized by some or all of the following:

d Responsible for introducing messages in the relay network, e.g.:

o S1 or moving relay control messages o Connects between the destination address and MRB, adds the corresponding header (including encryption), and sends it over Ml to a virtual core subsystem o Responsible for adding a proprietary mesh header to the relays network, for example, in case of a multihop d Receives MBSFN messages from rUE e.g.

o Separates between SI or Moving relay messages d Manages queues and sends Ack/Nack ® Sends multihop messages to NH

O Decapsulate/opens messages

Alternative 3 - Virtual Core Subsystem is characterized by some or all of the following:

Q Switch point between data from the EPC; may require encapsulation to Ml that goes to the tunneling subsystems, and data from the ECP and then directly to the rBS d Switch point between a disconnect state (sends to a standalone EPC) and a connect state (stationary EPC)

O Analyzes network traffic to identify various states e.g.:

o Active bearers o Disconnect or no disconnect state

Alternative 3 - Standalone Subsystem is characterized by some or all of the following:

O Provides EPC in case of a disconnection from the static network ® When operating with distributed EPCs, provides communication services to all users that registered or are registered in the base station, [and to] other users registered in the local EPC or in other EPCs

Alternative 3 - Routing and QoS Subsystem is characterized by some or all of the following:

d Responsible for QoS and routing in the multihop system o Manages the routing table to the multihop network o Receives updates of records from the radio resource subsystem and from other routing agents in the system o Manages the mesh routing method o Responsible for load control, management of the number of registered users, allocation of larger backhauling bandwidth/ with higher frequency

Alternative 3 - Radio Resource Subsystem

G Responsible for managing MRBs e.g.:

o Creates MRBs o Manages allocations and erases channels &amp;#9632; For example, as a result of bandwidth requests or topology changes o Coordination and registration with neighboring stations o Radio measurements for the backhauling network

Alternative 3 - Synchronization Subsystem ® Time synchronization at an open level, from a symbol between base stations (also in disconnected state); and/or d Time synchronization with the radio resource subsystem and with rUE

Alternative 3 - Adding Core Stationary

O MBSFN gateway:

o Converts SI to Ml and/or o Manages the mesh network into several UE proxies and/or o Manages the MRB of the static base stations

O UE proxy

Fig. 78: Dedicated Gain Control, is typically characterized by one or more of the following:

d Using a mechanism similar to Limiter, Blanking, MGC (Manual Gain Control) or

IAGC (Instantaneous Automatic GC) to normalize the signal received in rUE, d rUE synchronizes to the adjacent rBS’ signal but receives MBSFN transmissions of the neighbor base station while the adjacent rBS is silent d I.e. 80 dB attenuator that can operate at 0.1 micro can be used.

Alternative 3 - Base Station Requirements may include some or all of:

Support of MBSFN and Ml, M3 interface or similar

Q Support of dynamic changes in SIB 13 of the rBS from external-to-rBS source (using the interface between the Radio Resource S/S to the rBS) d Support of several service areas of MBSFN O Extended CP operation (in MBSFN areas) d Interfacing with an external clock for Synch d Support of blank MBSFN subframe d There is no RS in an empty transmission of MBSFN

Alternative 3 - rUE Requirements may include some or all of: d Support receiving standard MBSFH channels Q Possibility to cope with transmission ® Synchronization of the receive power for the data area only (without control area)

Q Extended CP operation d Possibility to read SIB 13 without attachment

Scheduler Separation Using Empty MBSFN Channels

Alternative 4 - Integration of a Dedicated Scheduler and MBSFN d Dedicated scheduler for effecting some or all of the following:

Q Dynamic allocation of time-diverted subframes in DL ® Dynamic allocation of PUSCH and PUCCH channels in UL, and/or Q Use of MBSFN channels as almost blank subframes in DL e.g.

d Useful due to lack of CRS transmission in MBSFN

Fig. 83

Dedicated Scheduler - UL example.

Fig. 84

Dedicated Scheduler - DL may be characterized by at least one of the following:

d Movement of 15-16 symbols (forward and backward) in each hop to solve the problem of running over BCH, PDCCH

O Use of MBSFN to silence PDSCH area of the subframe and reducing the content in PDCCH as much as possible.

O Optional addition of a dedicated interferences cancellation or dedicated gain control mechanisms to cancel/lower interferences.

Fig. 85

Alternative 4 - RRM Structure and interfaces.

Fig. 86

Alternative 4 - Backhauling Support

Alternative 4 - Tunneling Subsystem , is typically characterized by one or more of the following:

• Responsible for introducing messages [in/to] the relays network o SI or Moving relay control messages and/or • Receives and sends backhauling messages via rUE o Separates between SI or Moving relay control messages and/or • Encrypts/opens messages

Alternative 4 - Virtual Core Subsystem, is typically characterized by one or more of the following:

O Switch point between data from the EPC; may require encapsulation to SI, then goes to the tunneling subsystems, and between data from the ECP and then directly to the rBS and/or

Q Switch point between a disconnect state (sends to a standalone EPC) and a connect state (stationary EPC) and/or ® Analyzes network traffic to identify various states o Active bearers o Disconnect or no disconnect state

Alternative 4 - Standalone Subsystem, is typically characterized by one or more of the following:

® Provides EPC in case of a disconnection from the static network, and/or

Q When operating with decentralized EPCs, provides communication services to all users that registered or are registered in the base station, [and to] other users registered in the local EPC or in other EPCs

Alternative 4 - Routing and QoS Subsystem, is typically characterized by one or more of the following:

O Responsible for QoS and routing in the multihop system o Manages the routing table to the multihop network, and/or o Receives updates of records from the radio resource subsystem and from other routing agents in the system and/or o Manages the tree of hierarchies and/or o Responsible for at least one of: load control, management of the number of registered users, allocation of larger backhauling bandwidth/ with higher frequency

Alternative 4 - Radio Resource Subsystem, is typically characterized by one or more of the following:

• Responsible for managing the radio resources of rBS o Marks silent and transmission areas in UL/DL and/or o Coordinates and logs with neighboring stations and/or o Receives and measures neighbors via rUE/rBS and/or o Determines the symbol for commencing transmission

Alternative 4 - Synchronization Subsystem, is typically characterized by one or more of the following:

d Time synchronization at an open level, from a symbol between base stations (also in disconnected state) and/or ® Time synchronization with the radio resource subsystem and with rUE

Alternative 4 - Base Station Requirements may include some or all of:

d Support of blank MBSFN subframe transmission

Q Support of dynamic changes in SIB 13 and/or

Q Support of synchronization of the first symbol and/or

Q Interfacing with an external clock and/or d External handover command and/or d Control of frequency allocation of PUCCH, PUSCH and SRS frequency and/or ® Control of time allocation of PDSCH, SRS, PRACH and/or d Control of allocation of PDCCH (option).

Alternative 4 - rUE Requirements may include some or all of:

Q Support of MCH allocation identification

Q Possibility to read SIB 13 d Executes measurements and sends them to rRM

Figs. 87 and 88 illustrate a DL and a UL resource (time and frequency) grid, respectively, and an optional method for separating between SBS and rBS (base station functionality) in both UL and DL (uplink and downlink).

The term “mobile (communication) device” as used herein is intended to include but not be limited to any of the following: mobile telephone, smart phone, playstation, iPad, TV, remote desktop computer, game console, tablet, mobile e.g. laptop or other computer terminal, embedded remote unit.

Methods depicted herein by flowcharts may comprise some or all of the illustrated steps, suitably ordered e.g. as illustrated.

It is appreciated that terminology such as mandatory, required, need and must refer to implementation choices made within the context of a particular implementation or application described herewithin for clarity and are not intended to be limiting since in an alternative implantation, the same elements might be defined as not mandatory and not required or might even be eliminated altogether.

It is appreciated that software components of the present invention including programs and data may, if desired, be implemented in ROM (read only memory) form including CD-ROMs, EPROMs and EEPROMs, or may be stored in any other suitable typically non-transitory computer-readable medium such as but not limited to disks of various kinds, cards of various kinds and RAMs. Components described herein as software may, alternatively, be implemented wholly or partly in hardware, if desired, using conventional techniques. Conversely, components described herein as hardware may, alternatively, be implemented wholly or partly in software, if desired, using conventional techniques.

Included in the scope of the present invention, inter alia, are electromagnetic signals carrying computer-readable instructions for performing any or all of the steps of any of the methods shown and described herein, in any suitable order; machine-readable instructions for performing any or all of the steps of any of the methods shown and described herein, in any suitable order; program storage devices readable by machine, tangibly embodying a program of instructions executable by the machine to perform any or all of the steps of any of the methods shown and described herein, in any suitable order; a computer program product comprising a computer useable medium having computer readable program code, such as executable code, having embodied therein, and/or including computer readable program code for performing, any or all of the steps of any of the methods shown and described herein, in any suitable order; any technical effects brought about by any or all of the steps of any of the methods shown and described herein, when performed in any suitable order; any suitable apparatus or device or combination of such, programmed to perform, alone or in combination, any or all of the steps of any of the methods shown and described herein, in any suitable order; electronic devices each including a processor and a cooperating input device and/or output device and operative to perform in software any steps shown and described herein; information storage devices or physical records, such as disks or hard drives, causing a computer or other device to be configured so as to carry out any or all of the steps of any of the methods shown and described herein, in any suitable order; a program pre-stored e.g. in memory or on an information network such as the Internet, before or after being downloaded, which embodies any or all of the steps of any of the methods shown and described herein, in any suitable order, and the method of uploading or downloading such, and a system including server/s and/or client/s for using such; and hardware which performs any or all of the steps of any of the methods shown and described herein, in any suitable order, either alone or in conjunction with software. Any computer-readable or machine-readable media described herein is intended to include non-transitory computeror machine-readable media.

Any computations or other forms of analysis described herein may be performed by a suitable computerized method. Any step described herein may be computer-implemented. The invention shown and described herein may include (a) using a computerized method to identify a solution to any of the problems or for any of the objectives described herein, the solution optionally include at least one of a decision, an action, a product, a service or any other information described herein that impacts, in a positive manner, a problem or objectives described herein; and (b) outputting the solution.

The scope of the present invention is not limited to structures and functions specifically described herein and is also intended to include devices which have the capacity to yield a structure, or perform a function, described herein, such that even though users of the device may not use the capacity, they are if they so desire able to modify the device to obtain the structure or function.

Features of the present invention which are described in the context of separate embodiments may also be provided in combination in a single embodiment.

For example, a system embodiment is intended to include a corresponding process embodiment. Also, each system embodiment is intended to include a server-centered “view” or client centered “view”, or “view” from any other node of the system, of the entire functionality of the system , computer-readable medium, apparatus, including only those functionalities performed at that server or client or node.

Conversely, features of the invention, including method steps, which are described for brevity in the context of a single embodiment or in a certain order may be provided separately or in any suitable subcombination or in a different order, e.g. is used herein in the sense of a specific example which is not intended to be limiting. Devices, apparatus or systems shown coupled in any of the drawings may in fact be integrated into a single platform in certain embodiments or may be coupled via any appropriate wired or wireless coupling such as but not limited to optical fiber, Ethernet, Wireless LAN, HomePNA, power line communication, cell phone, PDA, Blackberry GPRS, Satellite including GPS, or other mobile delivery. It is appreciated that in the description and drawings shown and described herein, functionalities described or illustrated as systems and sub-units thereof can also be provided as methods and steps therewithin, and functionalities described or illustrated as methods and steps therewithin can also be provided as systems and sub-units thereof. The scale used to illustrate various elements in the drawings is merely exemplary and/or appropriate for clarity of presentation and is not intended to be limiting.