Radio bearer identification for self backhauling and relaying in advanced lte. RU patent 2508611.

FIELD: radio engineering, communication.

SUBSTANCE: reduction in overhead is achieved by providing a more efficient mechanism for user terminal and bearer identification as compared to using GTP-u and associated UDP/IP headers.

EFFECT: reducing overhead for LTE relaying, which saves radio resources on the backhaul link.

8 cl, 14 dwg

The level of technology

The adoption of many jumps proposed for systems of standard Long Term Evolution (long-term development of LTE) to improve the coverage and capacity of LTE networks. In systems with many cellular jumps information transfer between the base station and the user terminal (UT) can be done with lots of jumps with additional intermediate nodes. There are different types of intermediate nodes. Repeaters operate at the Level of 1, strengthening the received signal. Repeaters decode adopted the transport unit before shipment and request retransmission of HARQ if necessary, respectively, operate at Level 2. Transit AutoConnect is a technology Level relay 3 to improve the coverage and data rates LTE network. The terms "repeater" and "retransmission"as used in this description, refer to the relay and level 2, and level 3, unless otherwise specified.

When using the relay packets from many terminals appear in total unidirectional channel transit connections, which carries traffic for many terminal user between the base station (eNB) and the repeater. To ensure the possibility of multiplexing users on the channel transit connection between the base station and repeater need to relay, after receiving the package, delivered received packets to the proper account in the direction of descending channel. Tunneled between the base station and repeater unidirectional channel user is identified by title GTP-u package. The disadvantage of this approach is that the title should be transferred via transit connection with the creation of excess of official information on . In addition, existing mechanisms seal header, for example, the Robust Header Compression (seal header, RoHC)cannot be used to reduce the insider information due to tunneling GTP. Official information from the header of the GTP-u and associated header UDP/IP leads to unnecessary waste of scarce radio resources.

The essence of the invention

The present invention relates to a method and apparatus for identification unidirectional channel and the user terminal, which reduce service information for the relay in LTE (level 2 and level 3), which saves channel transit connection. The reduction of official information is achieved through the provision of a more efficient mechanism for the identification of unidirectional channel and the user terminal in comparison with headings GTP-u and associated header UDP/IP.

One of the options for implementation by means of the alarm ID unidirectional radio channel and the user terminal at the levels of the Protocol UP (PDCP, RLC and MAC) radio channel provided the opportunity to identify unidirectional channel and the user terminal. In this embodiment, you can completely remove headers GTP-u and associated UDP/IP and provide an opportunity to seal the header of the IP packets to the end user directly on a canal transit connection.

In the second variant of implementation through the introduction of additional Protocol level UP on the channel above the level Protocol convergence packet data (PDCP), which replaces the unnecessary headers GTP and associated UDP/IP specific field identification number unidirectional channel to reduce proprietary information related to these headings, provided the opportunity to identify unidirectional channel and the user terminal. At this level, the Protocol can also be sealed packet headers of the end user, or they can be sealed at the level of PDCP canal transit connection with the assumption that the field identification number unidirectional channel can be transparently passed through the seal header.

In the third embodiment provided the opportunity to identify unidirectional channel and the user terminal through the introduction of a level seal header in the tunnel GTP, which are sealed packages IP end-user. In this embodiment can be used headers GTP-u and related headers, UDP/IP, and a common Protocol service information, however, is low, especially if the channel transit connection seal is used header levels UDP/IP.

Brief description of drawings

Figure 1 shows the approximate communication system with lots of jumps.

Figure 2 shows the approximate architecture of the Protocol for the communication system with lots of jumps.

Figure 3 shows a sample architecture of the Protocol for the communication system with lots of jumps, in which the information on a site-specific user unidirectional channel fit in the Protocol level of the radio channel, for example, the level of PDCP, RLC or MAC.

Figure 4 shows a sample architecture of the Protocol for the communication system with lots of jumps, in which the information on a site-specific user unidirectional channel fit in the Protocol level above the level PDCP.

Figure 5 shows a sample architecture of the Protocol for the communication system with lots of jumps, in which the information on a site-specific user unidirectional channel fit the level of compaction header in the tunnel GTP between the donor base station and repeater.

Figure 6 shows the approximate procedure conducted by the donor base station in the system of communications with multiple jumps to insert information for the identification of unidirectional channel in packages of a descending channel and forward packets in a downward channel relay for transfer to the user's terminal through the repeater.

Figure 7 shows the approximate procedure conducted by the donor base station in the system of communications with multiple jumps to display and forward packets ascending channel, taken from a repeater, the service gateway in the network core.

On Fig.8 shows the approximate procedure conducted by a transponder in the system of communications with multiple jumps to insert information for the identification of unidirectional channel packages upward channel and forward packets downward channel the donor base station to transfer to the service gateway in the network core.

Figure 9 shows the approximate procedure conducted by a transponder in the system of communications with multiple jumps to forward packets descending channel, which is taken from the donor base station, the terminal of the user.

Figure 10 shows the approximate procedure conducted by the donor base station in the system of communication with lots of jumps, for sealing and forward packets in a downward channel relay for transfer to the user's terminal through the repeater.

Figure 11 shows the approximate procedure conducted by the donor base station in the system of communication with lots of jumps, for loosening and forward packets ascending channel, taken from a repeater, the service gateway in the network core.

On fig.12 shows the approximate procedure conducted by a transponder in the system of communication with lots of jumps, for sealing and forward packets upward channel the donor base station to transfer to the service gateway.

On fig.13 shows the approximate procedure conducted by a transponder in the system of communication with lots of jumps, for loosening and forward packets descending channel, which is taken from the donor base station, the terminal of the user.

On figure 14 shows the approximate donor base station and repeater for the communication system with lots of jumps.

Detailed description

Figure 1 shows a sample network of 10 communication, stated in the General reference item 10, which uses the relay with the transit . A network of 10 communication contains a basic 14 network and network of 16 radio access. Basic 14, the network includes site maintenance gateway (S-GW) 15, provides a network connection to the packet data, for example, with a network of Internet. S-GW 15 routes the traffic to the user terminals 20 and of them and functions within the network of 10 communication. A network of 16 radio access contains many base stations 18 that provide zone in the relevant cells 12 network 10 communication. In the figures there are two base stations 18: base station with the transit or some other type of device called in this description relay 18a, and the donor base station 18b. Repeater 18a wirelessly connected to the core network 14 through donor base station 18b. used to channel transit AutoConnect between relay 18a and the donor base station 18b, based on identical radio technology used to communicate with terminals 20 user, perhaps with some additional extensions that optimize for application of transit connection. As an example, when the donor base station 18b and repeater 18a use LTE radio to communicate with terminals 20 user inside the cell, for canal transit AutoConnect should also be a radio channel on the basis of LTE or, at least, LTE-like radio channel.

The present invention provides a method for the identification of terminal 20 user served by the retransmitter 18a through donor base station 18b both upstream channel, and for communication on the downlink. For understanding the present invention below is a brief overview of the architecture of the Protocol stack. Figure 2 shows one approximate architecture of the pass-through transfer Protocol stack, where the donor base station 18b hides repeater 18a of the core network 14. Accordingly, the terminal 20 user served by the retransmitter 18a, visible from the rest of the network 10 as an accepted directly through the donor base station 18b. Transmission downlink (DL) can be followed right to the left in figure 2. You can see that the packages of the descending channel to terminal 20 user first will be tunnelled from the gateway (S-GW) 15 in the backbone network 14 the donor base station 18b (downlink), as the S-GW 15 believes that the terminal 20 user is connected to the base station 18b. There is one tunnel GTP for each unidirectional channel terminal user.

The most obvious way forward the packets to the donor base station 18b in terminal 20 user is converting incoming tunnel GTP in the outbound tunnel GTP in the direction of the repeater 18a through mutually unambiguous mapping, that is, on the canal transit connection there is also one tunnel GTP for each unidirectional channel terminal user. Base station 18b shows the packages in General unidirectional channel transit connections, packages of many terminals 20 user are sent to the same one-way channel per channel transit connection. You can have many unidirectional radio transit connections for different QoS classes. After receiving packets in repeater 18a repeater 18a displays the packages in the appropriate unidirectional radio channels terminal user on the channel between the repeater 18a and terminal 20 based user ID of the tunnel GTP (TEID).

Despite the fact that the architecture of the Protocol, shown in figure 2, provides a basis for understanding the present invention, the specialists in this field of technology will be clear that the above principles apply to other implementations of the architecture of the Protocol transit AutoConnect. The present invention, in General, applicable to any alternatives, where the donor base station 18b can identify forward-only channels the user terminal, which include incoming packets. To perform this identification does not necessarily require that the tunnels GTP, outgoing from the SGW 15 and belonging to individual unidirectional channels user terminal, resulted in the donor base station 18b, as shown above in figure 2. For example, in the implementations of the Protocol, where the tunnel runs transparently through donor base station 18b, base station 18b can identify forward-only channels the user terminal through monitoring ID pass through the tunnels.

During normal transfer of data from the base station 18b in terminal 20 user terminal 20 user is addressed via PDCCH (physical control channel downward channel) for transmission on the DL and programs on UL. When data is transferred between the donor base station 18b and the repeater 18a, convenient address repeater 18a instead of individual terminals 20 user PDCCH. Otherwise, the distribution of PDCCH must be passed separately for each terminal 20 user that is not acceptable, because it is assumed that the system LTE PDCCH is a limited resource.

For the decision to transfer, shown in figure 2, the base station 18b shows the packets from many terminals 20 user unidirectional channel transit connection. Repeater 18a must be able to deliver the received packets to terminal 20 the proper user. User terminal and the corresponding unidirectional radio channel can be identified through the tunnel ID GTP. To ensure the possibility of multiplexing terminal 20 users on the channel transit connection between the base station 18b and the repeater 18a need to relay 18a, after receiving the package, tied received packets with the appropriate terminal 20 user. One solution is to define the identification number of the user terminal of the header GTP-u packets received from the S-GW 15. The disadvantage of this approach is that the title should be transferred via transit connections and, accordingly, create unnecessary service information on . In addition, a mechanism of sustainable errors seal header (RoHC) not applicable the bits service information. Official information from the header of the GTP-u and associated header UDP/IP, consequently, leads to unnecessary waste of scarce radio resources.

The present invention by providing a more effective framework for the identification of unidirectional channel and the user terminal in comparison with headings GTP-u and associated header UDP/IP reduces the technical information to be relayed to the LTE networks (level 2 and level 3). The resulting reduction service information saves channel transit connection.

In the first variant of implementation, as shown in figure 3, by means of inclusion ID unidirectional channel and the user terminal in one of the levels (PDCP, RLC and MAC) Protocol plane user (UP) on the radio channel between the donor base station 18b and the repeater 18a provided the opportunity to identify unidirectional channel and the user terminal. For the convenience of the levels of the Protocol UP on the radio channel in this description are called the levels of the Protocol of the radio channel, because these levels are defined applicable specification of the radio interface. In the first variant of the implementation of the tunnel GTP ends in the donor base station 18b. The donor base station 18b completely removes headers GTP-u and associated UDP/IP connectivity to seal the header of the IP packets to the end user directly on a canal transit connection. The donor base station 18b includes the ID of the unidirectional channel and the user terminal inside one of Protocol levels plane user of the radio interface for ensuring the possibility to display in the downward channel in repeater 18a of incoming one-way channel of transit connection-specific user terminal unidirectional channel and in an upward channel in the base station 18b of unidirectional channel transit connection-specific user terminal tunnel GTP.

To insert ID unidirectional channel and the user terminal at the level of PDCP can be used two different approaches. A first approach in the header PDCP introduced a separate field for the identification of unidirectional channel terminal user. This field indicates what unidirectional air terminal of the user should be given packet repeater 18a for downlink and what is the tunnel GTP package must be passed to the base station 18b to communicate upstream channel. In this approach, or do private PDCP mechanism (i.e. mechanisms (times)seals and (de)header encryption) for each unidirectional channel user terminal (multiplexing below PDCP), or alternatively, perform one mechanism PDCP for each unidirectional channel transit connections (multiplexing above PDCP). In this approach, changes may be required to standardize the Protocol PDCP.

The second approach is to insert ID unidirectional channel and the user terminal in the level of PDCP is to re-use, in a canal transit connection, the existing field CID (context) in the Protocol seal header as identification field unidirectional channel terminal user to specify, in what specific to the user terminal tunnel GTP (uplink) and unidirectional channel (downlink) should be displayed package, adopted via transit connection. Field CID Protocol seal header is generally used to identify the application threads. In this approach the field CID is used in the Protocol seal header on the channel of transit connection for identification unidirectional channel user terminal, which requires that the different tunnels GTP/unidirectional radio terminal user have always been appointed to different values CID (possibly ~65000 values). The mapping between tunnels GTP/one-way radio user terminal and CID can either be hard-coded, for example, RB id 1 uses the CID 1-20, or it can clearly be signaled between relay 18a and the base station 18b, or it can be configured using the system operation and maintenance. Possible signaling protocols include alarm RRC and S1/X2. An alternative to hard-coding and explicit alarm is implicit assignment display CID <-> RB/GTP, for example, on the basis of the order in which unidirectional pipes are installed, or some other scheme. The advantage of this approach is that it does not prescribe changes to standardize the Protocol PDCP.

In the event of existence of one mechanism PDCP for each unidirectional channel the user terminal in the donor base station 18b (i.e. multiplexing is performed below PDCP), which means that encryption and seal header run independently for each unidirectional channel the user terminal in the donor base station 18b, repeater 18a can skip decrypt/ when forwarding between radio transit connections and channel the user terminal. Instead relayed 18a node can simply display and forward PDU PDCP between the incoming and outgoing unidirectional channels without any additional processing PDCP.

It should be noted that one PDU RLC may contain a top-level packages linked from different unidirectional radio terminal user. Consequently, the number of fields to identify unidirectional channel the user terminal in the header of the RLC shall be equal to the number of units PDU top-level, linked from various terminals 20 user PDU RLC. To the size of the header remained a small, should provide the ability to dynamically set the size of the field to identify unidirectional channel terminal user in each PDU RLC, depending on the specific coupled PDU top level.

The ID of a specific user terminal unidirectional channel can also be inserted in the alarm level MAC. In this approach in the header MAC introduces a separate field for the identification of unidirectional radio terminal user. The introduction of a new field in the header MAC can be solved through the expansion of existing fields logical channel identifier (LCID) in the header MAC using a specific UE ID of the terminal. This field indicates what unidirectional air terminal of the user should be given packet repeater 18a (downlink)and what is the tunnel GTP package must be passed to the base station 18b (uplink). This decision assumes that each unidirectional channel terminal user marks the private PDCP mechanism (i.e. mechanisms (times)seals and (de)header encryption) and mechanism RLC (multiplexing is performed on the levels MAC). In this approach, changes may be required to standardize the Protocol MAC.

It should be noted that one PDU MAC can contain packages of top-level multiplexed from different unidirectional radio terminal user. Consequently, the number of fields to identify unidirectional channel the user terminal in the header of the MAC shall be equal to the number of units PDU top-level from different terminals 20 user in this PDU MAC. To save the header area should provide the ability to dynamically set the size of the field to identify unidirectional channel terminal user in each PDU MAC, depending on the specific multiplex PDU top level.

In the second embodiment of the present invention, as depicted in figure 4, through the introduction of additional Protocol level UP above the level of PDCP, which replaces the headers GTP and associated UDP/IP specific field to identify unidirectional channel to reduce proprietary information related to these headings, provided the opportunity to identify unidirectional channel and the user terminal. To reduce service information, useful to provide an opportunity to seal the header of packets end user. Seal header can be performed on a new Protocol level UP. Alternatively, seal header can occur at the level of PDCP canal transit connection with the assumption that the field is to identify the unidirectional channel you can pass transparently through the seal header.

Seal header on a new level Protocol eliminates the need to perform seal header level PDCP canal transit connection. Hence, the field identification number unidirectional channel may be sent as part of the header seal the title. This approach is similar to the first variant implementation using the level PDCP for transmission identification unidirectional channel and the user terminal. The difference is that this approach doesn't require modification of the existing level of PDCP canal transit connection.

If the seal header is PDCP, at the level of PDCP should be ignored identification field to a unidirectional channel added at a higher level. One approach to solve this problem is to explicitly configure level PDCP to ignore the first of the last N bytes in which the transferred identification unidirectional channel and the user terminal. Alternatively, the identification of a unidirectional channel and terminal user can attach the trailer (end) of the IP packet. In General, the limit is ignored algorithm seal header that more attention will be paid at the beginning of the package. This implies that the algorithm seal header does not depend on the length of the IP packet. In case if the algorithm seal header depends on the length of the IP packet, you may need to upper level has modified the length field of the IP (for example, by adding a fixed number of bytes), and other fields, for example, of the length field in the TCP/UDP, and IP checksum etc.

In the second variant the implementation of all the multiplexing of different unidirectional channels terminal user is above PDCP, which means that the object PDCP exists for each unidirectional channel transit connection (not for each one-way channel of a user terminal).

In the third variant of implementation, as shown in figure 5, is provided to identify unidirectional channel and the user terminal through the introduction of a level seal header in the tunnel GTP, which are sealed packages IP end-user. More specifically, to seal the title GTP-u is introduced level PDCP seal header (HC-PDCP). It was noted that additional level of seals header does not necessarily mean a new Protocol headers, for example, headers PDCP. In a typical implementation of this can be achieved through the performance of conventional sealing device the IP header (for example, RoHC) at the two ends of the channel, which replace the field of the IP header of (parts of) their compacted form. In this embodiment headers can be stored GTP-u and related headers, UDP/IP, because objects HC-PDCP channel transit connection compress headers GTP/UDP/IP. Repeater 18a may depend on the header GTP-u to determine the mapping between tunnels GTP and unidirectional radio terminal user. Possible protocols for configuration seal header inside the tunnel GTP can be alarm RRC or GTP-c or alarm S1.

Another potential alternative to this option is the lack of extra level seal header (HC-PDCP) in the tunnel, the GTP and the expansion of profiles seal Protocol header PDCP canal transit connections so that it can process seal headers tunnel GTP/UDP/IP Protocol header IP end-user together. This requires new profiles seals for the algorithm seal header RoHC (Reliable sealing of the header that can handle TCP/UDP headers (end-user) and GTP as headers enlargement during compaction.

Specialists in the field of technology will be clear that the nodes in the network 10, shown in figure 2-5 may contain specially programmed computer systems that are programmed for the above operation. Computer systems can contain one or more processors, microcontrollers, hardware or combination of them together with the storage memory and programming commands necessary for the above operation.

6 and Fig.7 shows the functioning of the donor base station 18b in one exemplary embodiment. In this embodiment ID information is inserted in the Protocol packets radio channels transmitted on the multiplex channel transit connection between the donor base station 18b and the repeater 18a.

Figure 6 shows a sample procedure 100 undertaken by the donor base station 18b to forward packets descending channel, which is designed to terminal 20 user. Procedure 100 begins when the donor base station 18b takes a packet of data from the gateway 15 to specific user tunnel for delivery to terminal 20 user (step 102). The donor base station 18b displays the tunnel ID for a specific user of the tunnel is specific to a user identifier used in the channel between the repeater 18a and the donor base station 18b (phase 104), and forwards the packet data repeater 18a on the multiplex channel transit connections in one or more packages radio channel Protocol (phase 106). Base station 18b inserts a specific user ID, at least in one of Protocol packet radio channel to ensure the ability of the repeater 18a identify the terminal 20 user that this packet of data (phase 108). As noted earlier, is specific to a user ID may contain specific to the user ID of a unidirectional channel, which identifies specific unidirectional radio channel assigned to the user terminal. Specific to the user ID of the unidirectional radio channel can be inserted in the header PDCP, title RLC or MAC header Protocol packet radio channel. Repeater 18a further forwards the packet to terminal 20 user specified for specific user unidirectional air.

On Fig.8 shows a sample procedure 200 to forward packets for the downlink taken from the donor base station 18b, in terminal 20 user. Procedure 200 begins when the relay 18a takes a packet of data from a terminal 20 user (step 202). Repeater 18a forwards the packet data to the donor base station 18b on the multiplex channel transit connections in one or more packages radio channel Protocol (phase 204). Repeater 18a inserts a specific user ID, at least in one of Protocol packet radio channel to ensure the ability of the donor base station 18b identify the user's terminal, for which the package is targeted data (phase 206). As noted earlier, is specific to a user ID may contain specific to the user ID of a unidirectional channel, which identifies specific unidirectional radio channel assigned to the user terminal. Specific to the user ID of the unidirectional radio channel can be inserted in the header PDCP, title RLC or MAC header Protocol packet radio channel.

The donor base station 18b further forwards the packet to the gateway 15. Figure 9 shows a sample procedure 250 carried out relay 18a to forward packets for the downlink taken from the donor base station 18b, in terminal 20 user. Procedure 250 begins when the relay 18a takes a packet of data from the donor base station 18b on the multiplex channel transit connections in one or more packages radio channel Protocol (phase 252). Before sending the data packet repeater 18a inserts a specific user ID, at least in one of Protocol packet radio channel. Repeater 18a determines the user's terminal, which must make the package data based on specific for the user ID of the inserted header at least one of the packages radio channel Protocol (phase 254), and sends this data to the identified user terminal (phase 256).

Figure 10 and figure 11 shows the functioning of the donor base station 18b in an alternate embodiment. In this embodiment tunnel header data packets transferred across the specific user tunnel from serving gateway 15, compacted for transmission via transit connection between the donor base station 18b and the repeater 18a.

Figure 10 shows a sample procedure 300 undertaken by the donor base station 18b to forward packets received from servicing gateway 15, repeater 18a. Procedure 300 begins when the donor base station 18b receives a packet through the tunnel GTP from serving gateway 15 (phase 302). The donor base station 18b it will decapsulate the data and compacts the header (phase 304). The donor base station determines the user's terminal, for which the package is targeted data based on the ID of the tunnel header GTP-u, received from the gateway 15, and displays the data package, adopted for the incoming tunnel from serving gateway 15, in the outbound tunnel in the direction of the repeater 18a (phase 306). The donor base station 18b encapsulates the condensed data packet tunnel packet, and forwards the packet data repeater 18a (phase 308). Outbound tunnel is specific to the user through the tunnel in the channel transit connection between the donor base station 18b and the repeater 18a. Before transferring to the repeater 18a the donor base station 18b inserts a specific user ID in the tunnel header to ensure the ability of the repeater identify the terminal 20 user (step 310).

Figure 11 shows a sample procedure 350, carried out by the donor base station 18b to forward packets upstream channel, taken from the repeater 18a via transit connection to the gateway 15. Procedure 350 begins when the donor base station 18a takes a packet of data from the repeater 18a on the unidirectional air transit connections (phase 352). In this embodiment is assumed that the transmission of data packets via transit connection tunneling Protocol is used, for example, GTP, and that the packet header data is sealed relay 18a before transmission. After receiving a data packet the donor base station 18b sealed packet data (phase 354) and packet header data (phase 356). The donor base station 18b defines the outbound tunnel towards the service gateway 15 (phase 358), and forwards the packet to the specific user tunnel between the donor base station 18b and service gateway 15 (phase 360). The donor base station can determine the outbound tunnel on the basis of a specific user ID, enclosing the header of the GTP-u, taken from the repeater 18a.

On fig.12 shows the approximate procedure conducted by a transponder in the system of communication with lots of jumps, for sealing and forward packets upward channel the donor base station 18b to transfer to the service gateway. The procedure begins when a repeater 18a takes a packet of data over the air from the terminal 20 user (step 402). Repeater 18a compacts packet header data (phase 404) and encapsulates the data in the package GTP, for transmission to the donor base station 18b (phase 406). Repeater 18a inserts a specific user ID in the header GTP (phase 408), and forwards the encapsulated and sealed packet of data to the donor base station 18b (phase 410).

On fig.13 shows a sample procedure 450 implemented relay 18a in the communication system with lots of jumps, for loosening and forward packets descending channel, which is taken from the donor base station, the terminal of the user. Repeater 18a takes a packet of data from the donor base station, encapsulated in a packet GTP (phase 452). Repeater 18a it will decapsulate the data and packet header data (phase 454). The donor base station 18b defines terminal 20 user, send the data packet, based on the header GTP (phase 456), and the corresponding tunnel towards the gateway 15 (phase 458). The donor base station 18b further forwards a packet of data to the identified terminal 20 user through the air stage 460).

On figure 14 shows the approximate donor base station 18b and repeater 18a in the system of communications with multiple jumps. Base station 18b contains a network interface 22 for connection to the service gateway 15, receive / transmit radio station 24 to communicate wirelessly transit connection with repeater 18a and schema 26 processing for the implementation of the protocols for a packet, as described in this document. Network interface 22, for example, might include Ethernet interface. Receiving-transmitting radio station 24 can be configured for the implementation of the known wireless protocols, such as LTE, WCDMA and WiMAX, without modifications to the channel transit connection. Diagram 26 processing contains one or more processors, hardware or combination of them and memory for implementation of procedures for the shipment, as shown in figure 6-7 and figure 10-11. Repeater 18a also includes a receive / transmit radio station 28 and schema 30 processing. The transceiver is used for communication with the donor base station 18b, and with the user's terminal. Diagram 30 processing contains one or more processors, hardware or combination of them and memory for implementation of procedures for the shipment, as shown in Fig.7-Fig.8 and fig.12-fig.13.

LTE Version 10, probably includes the solution of the transit AutoConnect, if you want a low level of official information on the channel transit connection. When applying the model of the invention to the decision to rebroadcast or transit in the system LTE Protocol service information is reduced. This implies a more efficient use of radio resource and, consequently, improved system performance. The amount of winnings is implemented by the reduction of official information, depends on the size of the package. For transferring very large packages a number of extra bits has little effect. However, for services like VoIP, with smaller IP packets win is significant.

The present invention may, of course, be done in certain ways, different from those set forth in this description, without departing from the scope and essential features of the invention. Real options for implementation, therefore, should be regarded in all respects as illustrative and not restrictive, and it is assumed that all changes within the value and equivalence accompanying the claims covered by it.

1. The method of multiplexing of data packets for multiple user terminal one unidirectional air on the transit connection between the donor base station and repeater in the communication system with lots of jumps, and mentioned method contains the stages at which: taken by the specific user tunnel connection with the gateway, tunneling package, including the tunnel header and encapsulated data packet for delivery to one of the mentioned terminal user package data of the tunnel package, seal the packet header data, send referred to package data with the sealed header from the donor base station in the repeater on the multiplex unidirectional air transit connections specific to the user the tunnel for the user terminal.

3. The method of multiplexing packages for a variety of terminal user on a single one-way radio channel on the transit connection between the donor base station and repeater in the communication system with lots of jumps, and mentioned method contains the stages at which: take referred to relay data packet from one of the mentioned terminal user seal the title of the mentioned data packet and send referred to package data with the mentioned sealed the title of the repeater to the donor base station in one or more packages Protocol of the radio channel through the tunnel unidirectional channel transit connection.

4. The method of multiplexing packages for a variety of terminal user on a single one-way radio channel on the transit connection between the donor base station and repeater in the communication system with lots of jumps, and mentioned method contains the stages at which: take referred to relay data package for delivery to one of the mentioned terminal user through the tunnel unidirectional channel transit connections from the donor base station, and mentioned data packet is sealed tunnel header, mentioned tunnel header, define the user's terminal, for which the package is targeted data based on specific for the user ID of the inserted mentioned tunnel header referred to the donor base station, and submit the said packet of data in the user's terminal.

5. The donor base station (18b) for multiplexing of data packets for multiple terminal user on a single unidirectional channel per transit the connection between the donor base station (18b) and the repeater (18a) in the communication system with lots of jumps, and the donor base station (18b) contains the schema (30) processing and receive / transmit radio (26), the scheme (30) processing is configured for: reception, specific for tunnel-user connection to the gateway (15), tunnel package including tunnel header and encapsulated data packet for delivery to one of the mentioned terminal user data packet from the tunnel package, seal header data packet forwarding the mentioned data packet with the sealed header from the donor base station (18b) the repeater (18a) on the multiplex unidirectional air transit connections specific to the user the tunnel for the user terminal.

6. The donor base station (18b) for multiplexing packages for a variety of terminal user on a single one-way radio channel on the transit connection between the donor base station (18b) and the repeater (18a) in the communication system with lots of jumps, and the donor base station (18b) contains the schema (30) processing and receive / transmit radio (26), the scheme (30) processing is configured for: receiving a data packet that has sealed the title of the repeater (18a) on the multiplex unidirectional air transit connections, uncompress the header of the mentioned package of data, encapsulate the mentioned data packet tunnel package and shipment referred tunnel package with the above mentioned condensed heading to the gateway (15) through specific to a user's tunnel, corresponding to an identified user terminal.

7. Repeater (18a) for multiplexing packages for a variety of terminal user on a single one-way radio channel on the transit connection between the donor base station (18b) and mentioned relay (18a) in the communication system with lots of jumps, with repeater (18a) contains a receive / transmit radio station (24), the network interface (22) and schema (26) processing, with the scheme (26) processing is configured for: receiving a data packet from one of the mentioned terminal user seal header mentioned data packet and forward referred to package data with the mentioned sealed the title of referred repeater (18a) the donor base station (18b) in one or more packages Protocol radio channel through the tunnel unidirectional channel transit connection.

8. Repeater (18a) for multiplexing packages for a variety of terminal user on a single one-way radio channel on the transit connection between the donor base station (18b) and mentioned relay (18a) in the communication system with lots of jumps, with repeater (18a) contains a receive / transmit radio station (24), the network interface (22) and schema (26) processing, with the scheme (26) processing is configured for: receiving a data packet for delivery to one of the mentioned terminal user through the tunnel a one-way channel transit connections from the donor base station (18b), and the mentioned data packet is sealed tunnel header, uncompress the mentioned tunnel header, terminal definition of the user for which packets of data based on specific for the user ID of the inserted mentioned tunnel header referred to the donor base station (18b), and forwarding the said package data in the user's terminal.