Patent Application
20120207078
Embodiments of the invention relate to a method and apparatus which use protocols and has particular, but not exclusive, application to communication systems which include relay nodes.
A communication system can be seen as a facility that enables communication sessions between two or more entities such as mobile communication devices and/or other stations associated with the communication system. A communication system and a compatible communication device typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. For example, the standard or specification may define if a communication device is provided with a circuit switched carrier service or a packet switched carrier service or both. Communication protocols and/or parameters which shall be used for the connection are also typically defined. For example, the manner how the communication device can access the communication system and how communication shall be implemented between communicating devices, the elements of the communication network and/or other communication devices is typically based on predefined communication protocols.
In a wireless communication system at least a part of the communication between at least two stations occurs over a wireless link. Examples of wireless systems include public land mobile networks (PLMN), satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN). The coverage of wireless systems can be divided into cells, and are therefore often referred to as cellular systems.
A user can access the communication system by means of an appropriate communication device. A communication device of a user is often referred to as user equipment (UE). A communication device is provided with an appropriate signal receiving and transmitting arrangement for enabling communications with other parties. Typically a communication device is used for enabling the users thereof to receive and transmit communications such as speech and data. In wireless systems a communication devices provides a transceiver station that can communicate with e.g. a base station of an access network servicing at least one cell and/or another communications device. Depending on the context, a communication device or user equipment may also be considered as being a part of a communication system. In certain applications, for example in ad-hoc networks, the communication system can be based on use of a plurality of user equipment capable of communicating with each other.
The communication may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services include two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. The user may also be provided broadcast or multicast content. Non-limiting examples of the content include downloads, television and radio programs, videos, advertisements, various alerts and other information.
3rd Generation Partnership Project (3GPP) is standardizing an architecture that is known as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. The aim is to achieve, inter alfa, reduced latency, higher user data rates, improved system capacity and coverage, and reduced cost for the operator. A further development of the LTE is referred to herein as LTE-Advanced. The LTE-Advanced aims to provide further enhanced services by means of even higher data rates and lower latency with reduced cost. The various development stages of the 3GPP LTE specifications are referred to as releases.
Since the new spectrum bands for international mobile telecommunications (IMT) contain higher frequency bands and LTE-Advanced is aiming at a higher data rate, coverage of one Node B (base station) can be limited due to the high propagation loss and limited energy per bit. Relaying has been proposed as a possibility to enlarge the coverage. Apart from this goal of coverage extension, introducing relay concepts may also help in the provision of high-bit-rate coverage in a high shadowing environment, reducing average radio-transmission power at the User Equipment (UE). This may lead to long battery life, enhanced cell capacity and effective throughput, e.g., increasing cell-edge capacity, balancing cell load, enhancing overall performance, and reducing deployment costs of radio access networks (RAN). The relaying would be provided by entities referred to as Relay stations (RSs) or Relay Nodes (RNs). The relay nodes can be fixed or mobile, for example mounted to a high-speed train. In some systems the relay stations may be opportunistically available user equipment/mobile terminals that are not owned by the network itself.
According to one embodiment there is provided a method comprising: receiving data in at least one link layer message from a first access node at a second access node, said first access node being associated with the second node; determining if said data is to be sent to a third access node; and, sending the data in at least one internet protocol message to the third access node.
The first access node may be a relay node and/or and the second access node is may be a base station.
The first access node and second access node may be part of the same sub-network.
The interface between the second access node and third access node may be a X2 type interface and/or the said internet protocol message may be an X2 type message.
According to another embodiment, there is provided a method comprising: receiving data in at least one internet protocol message at a first base station from a second base station; determining if said data is to be sent to a node associated with the first base station; and sending the data in at least one link layer message to a node.
The node may be a relay node.
The interface between the first base station and second base station may be a an X2 type interface and/or the said internet protocol message may be an X2 type message.
According to another embodiment there is provided a computer program comprising program code means adapted to perform the method of embodiments when the program is run on a processor and a computer readable medium comprising a such computer programs.
According to another embodiment there is provided an access node or processor therefor, having means to receive data in at least one link layer message from a second access node associated with said access node; determining if said data is to be sent to a third access node; and sending the data in at least one Internet protocol message to the third access node.
The access node may be a base station and/or said second access node may be a relay node.
The access node may be part of the same sub-network as the second access node.
The interface between the access node and third access node may be an X2 type interface and/or the said Internet protocol message may be an X2 type message.
According to another embodiment there is provided a base station or processor therefor, having: means to receive data in at least one Internet protocol message from a second base station; and means to determine if said data is to be sent to a node associated with the first base station; and means to send the data in at least one link layer message to a node.
The node may be a relay node.
The interface between the base station and second base station may be an X2 type interface and/or the said Internet protocol message may be an X2 type message.
The link layer may be a Medium Access Control layer.
The link layer message may include routing information. The routing information may comprise one or more of global cell or node identity information. The routing information may include parameters to enable flow separation in the user plane. The routing information may include Tunnel End Point Identifier parameters.
The link layer message may include a modified X2-AP or Protocol Data Unit layer of an X2 type message.
For a better understanding of some embodiments of the invention, reference will be made by way of example only to the accompanying drawings in which:
a and 7b show flow diagrams illustrating certain embodiments.
As specified in 3GPP TR 36.814 (Third Generation Partnership Project) relaying is considered as one of the potential techniques for LTE-A where a RN is wirelessly connected to the radio-access network via a donor cell. Some embodiments of the invention are described in the context of the LTE-A proposals. However, other embodiments of the invention can be used in any other scenario which for example requires or uses one or more relays.
Reference is made to
The UE or any other suitable communication device can be used for accessing various services and/or applications provided via a communication system. In wireless or mobile communication systems the access is provided via an access interface between mobile communication devices (UE) 6 and an appropriate wireless access system. The UE 6 can typically access wirelessly a communication system via at least one base station. The communication devices can access the communication system based on various access techniques, such as code division multiple access (CDMA), or wideband CDMA (WCDMA), the latter technique being used by communication systems based on the third Generation Partnership Project (3GPP) specifications. Other examples include time division multiple access (TDMA), frequency division multiple access (FDMA), space division multiple access (SDMA) and so on. In a wireless system a network entity such as a base station provides an access node for communication devices.
Each UE may have one or more radio channels open at the same time and may receive signals from more than one base station and/or other communication device.
In certain applications, L3 or higher layer relay nodes may be used. L3 is layer 3 of the OSI model and is responsible for source to destination data delivery including routing. Such a relay node may be similar to a base station. In a L3 relay the RN is assumed to have a scheduling capability for the access links of the UEs which are registered to that relay node.
In some applications, there may be an issue of backwards compatibility for earlier versions of the standard. For example in one embodiment, from UE's viewpoint, the serving network node should serve Release 8 (of the 3GPP standard) user equipment. Due to this requirement the relays may support at least some and in some embodiments all of the main eNB functions.
In some applications, a system using relays may be arranged such that at most two hops are allowed in the system (e.g. eNB-UE or eNB-RN-UE) and in other applications of relay systems, there may be more than two hops where for example, relays are able to communicate with each other.
There are currently four potential candidate architectures proposed in 3GPP RAN2 WG. In type 1 architecture, the Relay Node is viewed as an eNB by the UE. A “type 1” RN has been proposed, which is an in-band relaying node having a separate physical cell ID (identity), support of HARQ (Hybrid Automatic Repeat Request) feedback and backward compatibility to Release 8 (Rel 8) UEs.
It has been proposed that the X2 interface should be supported by the Relay Node. The X2 interface is the direct connection between two eNBs and allows information such as load information or the like to be exchanged.
In a RAN2 #65bis meeting part of 3GPP, RAN 2 agreed with the definition for the nodes and the interfaces as shown generally in
The wireless interface 10 between the RN 4 and the donor e-NB 2 is the Un link interface. The link may be considered as backhaul link.
The “Load Indication” procedure and message in an X2 interface are defined within the X2 AP specification of 3GPP TR36.423. The X2 interface may be typically used as the interface between two eNBs. The purpose of the Load Indication procedure is to transfer load and interference co-ordination information between intra-frequency neighbouring eNBs. The procedure may use non UE-associated signalling.
Some discussions in 3GPP indicate the use of X2 architecture using a “local breakout” which means using IP-routed transport for X2 already in Un. In the relay node any control or user plane signalling may thus be transported between relay nodes and Donor eNB on top of the IP Layer (Internet Protocol). Such an approach as standardised in 3GPP Rel8, maximises X2 interface similarity between network elements/access nodes (which do not include relay nodes), and also between network elements/access nodes where one or more of these includes a relay node. However this approach includes several layers of additional protocols which serve no purposes between relay nodes and/or between the relays node and other access nodes such as eNBs and Donor eNB and may be at the expense of radio resource efficiency in particular across radio interfaces such as Un. However, it should be appreciated that there may be advantages in this arrangement.
As far as the control plane is concerned, the Transport Network Layer comprises a stack of (sub-)layers which are the physical layer, 25c, the data link layer 26c, the IP layer 27c and the SCTP (stream control transmission protocol) layer 28. In the Radio Network Layer there is an X2-AP layer 31. In the Transport Network Layer of the User Plane are also physical and data link layers, 25u and 26u respectively, an IP layer 27u and a UDP (User datagram protocol) layer and a GTP-U (GPRS (General Packet radio service) tunneling protocol—for user data) layer. In the Radio Network Layer is a User Plane PDU (Protocol Data Unit) When such a protocol stack as shown is used in systems which include relay nodes (i.e. having relay architecture), any relay node may be regarded as an eNB. The end point IP and SCTP for the control plane of X2 interface may be a relay node or eNB (i.e, RN2 or DeNB1 or DeNB2 or RN3 or any eNB). Also UDP and GTP-U layer end points for the user plane will be the same as in the control plane.
This approach, as mentioned, may create a lot of unnecessary overhead over the interface for the Un link (i.e between eNBs and relay nodes). IP or SCTP layers for the protocols Un interface may not be needed. IP layers are only needed between access nodes such as DeNB1 and DeNB2 to route the packets. As Un link may be a peer-to-peer interface over radio, the use of SCTP and IP may waste radio resource unnecessarily.
Also to use the existing protocol, local break out from RN creates complexity for the RN and donor eNB. This is because the RN has to implement IP stack including its configuration functionality and donor eNB has to provide IP routing functionality and support routing protocols.
In some embodiments of the invention, a simplified protocol stack may be used for communication between relay nodes and access nodes and/or between relay nodes; i.e. over the X2/Un interface. In some embodiments there may be a reduced protocol stack in which there may be less layers (or sub-layers) in the protocol stack.
In one embodiment, such a modified protocol is used where the SCTP and IP layers are removed from the protocol stack. In one embodiment simplified routing information is instead incorporated into the modified X2-Application protocol. In one embodiment this routing information may take the form of global cell identifier (ID) of the source and target eNBs. In an embodiment such information may be added in the X2-AP (AP is Application Protocol) layer (message header) to help the (X2) message routing. Thus in certain embodiments the X2-AP layer message is modified.
In addition or alternatively, there may be no IP layer in the Transport Network Layer of the User Plane. Additionally or alternatively the IP layer may be omitted for the User plane, as the IP layer may not be needed over the X2 interface; (e.g. across Un links) and, either GTP-U and UDP layers can be used instead. In a further modification, the UDP layer may be omitted.
Alternatively or additionally, a modified PDU 32 layer may be utilised. In one embodiment this modified PDU layer may have only routing information such as a Tunnel End Point Identifier (TEID) instead of entire GTP-U layer to be used over a Un interface.
Various other options according to other embodiments would be clear to the skilled person.
One feature may be provided in some embodiments there is a reduced number of sub-layer(s) and/or reduced complexity of the protocols used across X2 interfaces (or Un links), than is used between e.g. eNBs or between other access nodes.
Therefore, according to certain embodiments, when communicating between eNBs conventional protocol arrangements, (i.e. conventional protocol stack) may be used. Modified protocol stacks according to some embodiment (such as the
As already mentioned, in some embodiments of the invention, appropriate routing parameters may be utilised/added in a modified protocol e.g. in the X2-AP layer. The parameter(s) may be for example in one embodiment Tunnel End Point Identifier (TEID) to enable flow separation in the user plane across relay X2/Un links. As relay nodes are typically connected to only one donor eNB, the relay node may be able to send an (e.g. X2) message or modified (X2) message to donor NB with the correct target cell ID.
One embodiment will now be described with reference to
In Step S1, the donor eNB 50 receives a message from another eNB 52. This may be an X2 type message and may include an identity (ID) parameter of the target cell/destination/node.
In Step S2, the donor eNB 50 then decides whether this message is to be routed to a appropriate network element under its own responsibility, such as one or more further relay nodes 53 or user equipment/further node 54, or to a neighbouring eNB 51. This may achieve this by determining if the message ID is destined for a network element under responsibility of the eNB; e.g. relay node 53.
In Step S3, after it is determined that the message has to be sent to a neighbouring eNB instead, such as eNB 51, eNB 50 uses a standard protocol in step S5, (e.g. that which is typically used for X2 interfaces), for forwarding the message. Existing SCTP and IP layers in the protocol stack may be used (e.g. the conventional protocol stack is used). The receiving eNB receives the message as any other X2 message. The message may be “consumed” if it is destined for eNB 50.
If it is determined at step S2 that the message is for a relay node or other node under the responsibility of eNB 50, for example relay node 53, eNB 50 forwards the packet as it is received in Step 4. If the packet is arrived from outside of eNB 50 and contains SCTP and IP. eNB modifies the conventional protocol stack to remove the SCTP and IP. In one embodiment this may include removing SCTP and IP layers. Further modification of one or more remaining layers may be made.
In step S5 the (e.g. X2) message is sent using this modified protocol stack to the appropriate network element e.g. relay node 53. It may be sent based on the Un transport mechanism (Un may have a Medium Access Control (MAC) layer scheduling mechanism to send and receive packets).
b shows a flow diagram where in step S1 a message is sent from the relay node to an eNB. In step S2 it is determined if the message includes ID information as to whether the message is destined for a network element under responsibility of the donor eNB (e.g. a second relay node). If this is the case the message is forwarded to the appropriate relay node as received as in step S4. If not the protocol is amended and forwarded to the relay node using this modified protocol as in step S3.
As mentioned, in some of the above embodiments, SCTP and/or IP layers may not be required. Because of this reduction in control and associated data, the packets which are transmitted over Un link can be smaller thus saving valuable radio resources. Also as this architecture may not require local break-out which means using IP-routed transport for X2 already in Un. In the donor eNB, it can simplify the donor eNB implementation.
The required data processing apparatus and functions of a relay node and a base station apparatus as well as an appropriate communication device may be provided by means of one or more data processors. The above described functions may be provided by separate processors or by an integrated processor. The data processing may be distributed across several data processing modules. A data processor may be provided by means of, for example, at least one chip. Appropriate memory capacity can also be provided in the relevant nodes. An appropriately adapted computer program code product or products may be used for implementing the embodiments, when loaded on an appropriate data processing apparatus, for example in a processor apparatus associated with the base station, processing apparatus associated with relay node and/or a data processing apparatus associated with a UE. The program code product for providing the operation may be stored on, provided and embodied by means of an appropriate carrier medium. An appropriate computer program can be embodied on a computer readable record medium. A possibility is to download the program code product via a data network.
It is noted that whilst embodiments have been described in relation to LTE, similar principles can be applied to any other communication system where relaying is employed. Therefore, although certain embodiments were described above by way of example with reference to certain exemplifying architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.
It should be noted that although embodiments of the invention have been described in the context of relative high carrier frequencies, embodiments of the invention can be used with lower frequency carriers.
It is also noted herein that while the above describes exemplifying embodiments of the invention, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/EP2009/058132 | 6/29/2009 | WO | 00 | 3/19/2012 |
