KR20100032001A - Method and apparatus for requesting bandwidth at the multi hop relay network - Google Patents

Abstract

PURPOSE: A method and an apparatus for requesting bandwidth in a multi hop relay network are provided to request uplink bandwidths according to each group, thereby reducing overhead and delay. CONSTITUTION: A group generator(220A) groups uplink bandwidth requests to generate groups. The uplink bandwidth requests include at least one connection ID generated from at least one terminal. A group bandwidth request message generator(220B) generates bandwidth request messages according to each group according to whether uplink packets exist about each group.

Description

Method and apparatus for requesting bandwidth in multi-hop relay network {METHOD AND APPARATUS FOR REQUESTING BANDWIDTH AT THE MULTI HOP RELAY NETWORK}

The present invention relates to a method and apparatus for requesting bandwidth in a multi-hop relay network. More specifically, the relay according to the present invention requests the uplink bandwidth request when one or more terminals request an uplink bandwidth having one or more connection IDs. The present invention relates to a bandwidth request method for requesting a base station to a base station by grouping according to a set criterion and an apparatus (relay) for performing the same.

In the next-generation mobile communication, it is expected that a lot of communication will be performed through a relay station, rather than a base station serving all regions. By installing these relays, you can expand coverage and increase capacity. Unlike analog repeaters or digital repeaters used in conventional cellular systems, the relay system is capable of radio resource management in consideration of interference and resource conditions. As a result, a good link can be secured to improve capacity, and a service can be provided to a terminal located in a shadow area, thereby improving coverage.

When the terminal requests uplink bandwidth to the base station through such a relay, the relay requests individually according to one or more connection IDs transmitted from one or more terminals. In this case, the request may use the MAC signaling header type 1 provided by IEEE 802.16e. In the related art, one or more terminals belonging to a specific relay area request an uplink bandwidth to a relay according to a connection ID corresponding to each service generated, and the relay receiving the request again according to a relay connection ID corresponding to a connection ID of the terminal. Requests uplink bandwidth to the base station. Therefore, when an uplink bandwidth is individually requested for each generated connection ID, overhead is generated because polling resources for uplink bandwidth request transmission are individually allocated.

Therefore, there is a need for a scheme for a terminal or a relay to efficiently request uplink bandwidth.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object thereof is to reduce the overhead required for a relay to request and allocate an uplink bandwidth to a base station in a multi-hop relay network.

It is still another object of the present invention to provide a bandwidth request method for requesting a base station for a required bandwidth by grouping a request based on a predetermined criterion of a relay that receives a request for uplink bandwidth according to one or more connection IDs from one or more terminals. The purpose is.

The bandwidth request method of the present invention for solving the above problems comprises the steps of receiving an uplink bandwidth request message having at least one connection ID generated from at least one terminal, the connection ID of the received uplink bandwidth request message Analyzing and grouping, generating a group-specific bandwidth request message for each group generated by the grouping and transmitting the generated group-specific bandwidth request message to the base station. In this case, the generating of the bandwidth request message for each group may include determining whether an uplink packet exists and, if the uplink packet exists, request a connection ID of the uplink packet and request uplink bandwidth to a group. And determining whether a connection ID is groupable. If the uplink packet is present, the bandwidth request message for each group is generated using a general MAC header and an extended subheader concatenated thereto. If the packet does not exist, the conventional uplink bandwidth request message is used as it is or modified.

In the bandwidth request method of the present invention, the terminal generates and transmits an uplink bandwidth request message having one or more connection IDs to the relay, and when the relay receives the uplink bandwidth request message, analyzes and groupes the connection IDs. And generating a bandwidth request message for each group for each group generated by the grouping, and transmitting the bandwidth request message to the base station, and the base station receives the bandwidth request message for each group to uplink the bandwidth required by each terminal. And assigning through a map.

In addition, in the multi-hop relay network of the present invention, a relay device for processing a bandwidth request includes a group generator for generating a group by grouping uplink bandwidth requests having one or more connection IDs generated from one or more terminals and an uplink for each group. And a bandwidth request message generator for each group generating a bandwidth request message for each group according to the existence of the link packet.

In this case, the grouping in each of the above methods and apparatus is characterized by grouping by at least one criterion of service type, amount of bandwidth requested, priority, and delay.

When the relay according to the embodiment of the present invention requests the uplink bandwidth from the base station, the uplink bandwidth request according to one or more connection IDs received from one or more terminals is grouped according to a predetermined criterion, and then the required bandwidth for each group is requested. As a result, overhead is reduced as compared with the case of requesting bandwidth according to an individual connection ID.

The terminology of the embodiments of the present invention is to be in accordance with the IEEE 802.16e / j standard, but is not necessarily limited thereto.

In addition, according to the IEEE 802.16j standard, the connection ID used by the terminal is assigned from the relay as an identifier for identifying a service generated in the terminal, and the connection ID used by the relay is an identifier corresponding to the terminal connection ID one-to-one. Although allocated from the base station, in the embodiment of the present invention, both the terminal connection ID and the relay connection ID will be referred to as a connection ID.

The embodiment of the present invention is also applicable to multi-hops in which a plurality of relay stations (RSs) exist, but for the sake of simplicity, two-hops, that is, one relay The case where is applied is described as an example. It will be readily appreciated by those skilled in the art that the uplink bandwidth request method in the two hops can be applied to the multi hops.

The uplink bandwidth request according to an embodiment of the present invention means that the terminal requests the base station for the bandwidth required to perform a service generated in the terminal, and the bandwidth request for each group relays an uplink bandwidth request transmitted from the terminal. Means receiving and grouping bandwidth according to a predetermined criterion.

In the following description, a specific embodiment of an uplink bandwidth request is described by dividing it into a first embodiment and a second embodiment. In this case, the first embodiment is a method in which a relay generates a bandwidth request message for each group when the uplink packet does not exist and transmits it to the base station. In the second embodiment, all uplink packets are present when the uplink packet exists. A method of requesting bandwidth to a base station using an extension header concatenated with a generic MAC header included in the.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that, in the drawings, the same components are denoted by the same reference symbols as possible. Further, the detailed description of well-known functions and constructions that may obscure the gist of the present invention will be omitted.

1 is a schematic diagram schematically showing a method for requesting an uplink bandwidth in a relay network according to an embodiment of the present invention. The relay network of the present invention includes a terminal 110, a relay 120, and a base station 130.

The terminal 110 requests an uplink bandwidth to the base station 130 through the relay 120 and receives an uplink map (UL MAP) transmitted from the base station 130 through the relay 120. . In this case, the terminal 110 requests the relay 120 for an uplink bandwidth required for each connection ID for each service generated in the terminal. In this case, the uplink map refers to a MAC (Media Access Control) management message which is located at the front of each frame for resource allocation for each terminal and informs the terminal of the result of dynamically allocated resources.

In this case, the uplink bandwidth request may be performed by transmitting a bandwidth request message (bandwidth request header) of the IEEE 802.16e system. Since the format and specification for the bandwidth request message are described in IEEE 802.16e draft, detailed description thereof will be omitted below.

The uplink bandwidth request is transmitted to the base station 130 through the relay 120. In addition, the terminal 110 receives an uplink map including information on scheduling of uplink resources transmitted from the base station 130 through the relay 120. Upon receiving the uplink map, the terminal 110 transmits data based on the assigned slot and the time point of the slot to be transmitted.

Terminal 110 according to an embodiment of the present invention is capable of multi-connection and multi-QoS service. In other words, the terminal 110 may maintain one or more connection IDs according to a plurality of services at the same time point, in which case the QoS classes of the connection IDs may be the same or different.

In addition, when there is at least one connection ID to service, if a group can be formed under a predetermined criterion, the terminal 110 may generate the bandwidth request message for each group and transmit the group to the relay 120 by grouping the one or more connection IDs. have.

In FIG. 1, the terminal 110A requests uplink bandwidth based on a connection ID 1 and a connection ID 2 according to two services, and the terminal 110B based on a connection ID 3 and a connection ID 4 according to two services. Requesting the uplink bandwidth, the terminal (110C) has shown an example of requesting the uplink bandwidth based on the connection ID 5, connection ID 6, connection ID 7 according to the three services. As such, each terminal requests the required bandwidth based on the connection ID.

The relay 120 receives the uplink bandwidth request transmitted from the terminal 110 and groups the received bandwidth according to a predetermined criterion and requests the base station 130 for the required bandwidth for each group. In other words, the relay 120 does not request a bandwidth from the base station 130 for each uplink bandwidth request based on one or more connection IDs transmitted from the terminal 110, but instead receives a plurality of received bandwidth requests on a predetermined basis. Grouping according to the request for bandwidth to the base station 130 for each group.

In FIG. 1, the relay 120 receives an uplink bandwidth request for each connection ID transmitted from each of the terminals 110A, 110B, and 110C, and then selects group 1 (connection ID 1 and connection ID 3) according to a predetermined criterion. An example of classifying into group 2 (connection ID 2, connection ID 4) and the like is illustrated. After the classification, the relay 120 requests the base station 130 for a bandwidth required for each group. As such, the relay 120 may request bandwidth for one or more connection IDs at a time, rather than requesting bandwidth for each connection ID, thereby reducing the overhead that may occur in the relay 120.

The base station 130 receives the bandwidth request for each group transmitted from the relay 120 and identifies the relay 120 that has transmitted it through the connection ID included in the bandwidth request for each group. The base station 130 generates an uplink map including information on bandwidth required by each terminal 110, a slot allocated to each terminal 110, and a timing point of a slot to be transmitted, to the relay 120. send.

According to an embodiment of the present invention, there may be two cases in which the relay 120 requests the uplink bandwidth to the base station 130. The first embodiment is a method in which the relay 120 generates a bandwidth request message for each group and transmits it to the base station 130 when there is no uplink packet. FIGS. 2 to 5 illustrate the first embodiment. Shown.

The second embodiment is a method for requesting a bandwidth from a base station using an extension header concatenated with a generic MAC header included in all uplink packets when an uplink packet exists. 6 shows a general MAC header and its extended header format used in the second embodiment.

<First Embodiment>

First, Figure 2 is a block diagram showing the internal structure of the relay 120 according to the first embodiment of the present invention. The relay 120 includes a wireless communication unit 210 and a control unit 220 as shown in FIG. 2, in which case the control unit 220 includes a group generator 220A and a bandwidth request message generator 20B for each group. ).

First, the wireless communication unit 210 may include an RF transmitter for upconverting and amplifying a frequency of a transmitted signal, and an RF receiver for low noise amplifying and downconverting a received signal. The wireless communication unit 210 according to the embodiment of the present invention receives an uplink bandwidth request message transmitted from the terminal 110 and transmits it to the control unit 220, and transmits the bandwidth request message for each group generated by the relay 120 to the base station. Send to 130. In addition, the wireless communication unit 210 receives an uplink map including information on uplink bandwidth allocation transmitted from the base station and transmits the uplink map to the terminal 110 again.

The controller 220 controls the overall operation of the relay 120. In particular, the controller 220 according to an embodiment of the present invention may include a group generator 220A and a bandwidth message generator 220B for each group.

The group generator 220A groups uplink bandwidth requests based on one or more connection IDs received through the wireless communication unit 210 of the relay 120 according to a predetermined criterion. In this case, the criteria for grouping one or more channel link bandwidth requests may be a type of service, an amount of bandwidth required, a priority, a latency, and the like, among the information included in the connection ID. In other words, whether the bandwidth request is for a kind of service such as voice call, data service, video service, etc. (type of service), the total size of the bandwidth request for uplink is the same (amount of bandwidth), emergency such as 119 call The criteria for grouping one or more bandwidth requests may be whether the bandwidth request for the situation (priority) or whether data transmission should be made in real time or non-real time (delay). However, this is merely an example of the grouping criteria and is not necessarily limited thereto.

The bandwidth request message generation unit 220B for each group generates a bandwidth request message for each group including information on the amount of bandwidth, the identifier for each group and the amount of bandwidths requested by the grouped connection IDs. In this case, the identifier for each group may be displayed as a connection ID arbitrarily selected in each group, or may be displayed as a group identifier previously negotiated between the base station 130 and the relay 120. The pre-negotiated identifier is, for example, the base station 130 and the relay 120 may be previously identified for a high priority group, a low priority group, a group requiring real-time data transmission, a group requiring non-real-time data transmission, and the like. It may be an identifier used by designating an identifier. The amount of bandwidth included in the bandwidth request message for each group simply adds up the total amount of bandwidths requested by each connection ID.

3 is a diagram illustrating a process in which the relay 120 groups bandwidth requests for connection IDs received from the terminals 110 according to a predetermined criterion.

For ease of explanation, it is assumed that three terminals of the first terminal 305, the second terminal 310, and the third terminal 315 exist in the terminal requesting the uplink bandwidth. A connection ID 1 305A, a connection ID 2 305B, and a connection ID 3 305C are generated in the first terminal 305, and a connection ID 4 310A and a connection ID 5 (in the second terminal 310). 310B), connection ID 6 (310C) is generated, the connection ID 7 (315A), connection ID 8 (315B), connection ID 9 (315C), connection ID 10 (315D) generated in the third terminal 315. Assume

First, connection IDs 1 to 10 corresponding to a generated service are assigned to the first terminal 305, the second terminal 310, and the third terminal 315, respectively. In this case, the shaded connection ID in FIG. 3 is a connection ID that needs to request uplink bandwidth. Each terminal requests a bandwidth required for the relay 120 using an uplink bandwidth request message.

According to an embodiment of the present invention, each terminal 305, 310, 315, if there is at least one connection ID to service, if a group can be formed under a certain criterion, the group of the at least one connection ID group each group It is also possible to generate a bandwidth request message and send it to the relay. For example, when the service types of connection ID 1 305A and connection ID 3 305C of the first terminal 305 of FIG. 3 are the same, each of connection ID 1 305A and connection ID 3 305C may be used. Rather than requesting the uplink bandwidth, the uplink bandwidth may be requested for the grouped connection IDs 1 and 3 at once.

The relay 120 receiving the bandwidth request stores the received bandwidth request in a buffer for a certain period. When the set period elapses, the group generator 220A of the relay 120 groups the received bandwidth requests according to a predetermined criterion. The criteria for grouping the received bandwidth requests may be a type of service, an amount of bandwidth required, a priority, a latency, and the like, as described above, but is not necessarily limited thereto.

In FIG. 3, Group 1 has Connection ID 1 (305A) and Connection ID 4 (310A), Group 2 has Connection ID 3 (305C) and Connection ID 6 (310C), and Group 3 has Connection ID 8 (315B) and Connection It can be confirmed that ID 9 (315C) is included.

The bandwidth request message generator 220B for each group generates a bandwidth request message for each group. In this case, the generated bandwidth request message for each group includes information on the bandwidth of the sum of the amount of each bandwidth requested by the group ID and the grouped connection ID.

As can be seen in FIG. 3, the bandwidth request messages for Group 1, Group 2, and Group 3 are each group's bandwidth request message 325 of Group 1 and Group 2's bandwidth request according to grouped connection IDs, respectively. Message 330 is generated as a group-specific bandwidth request message 335 of the group 3 and transmitted to the base station 130. Then, the base station 130 identifies each group through the connection ID of the bandwidth request message for each group, and allocates the bandwidth required by the terminals to each terminal through the uplink map.

4 is a diagram illustrating an example of a format of a bandwidth request message for each group that a relay transmits to a base station 130 when there is no uplink packet.

In the message format of FIG. 4, when HT = 1 and EC = 0, this indicates that the message is an uplink bandwidth request message. In the conventional uplink bandwidth request message, a connection ID allocated to each service required by a terminal is recorded in a connection ID field, and a bandwidth required by the connection ID is recorded in a bandwidth request field.

However, the bandwidth request message for each group according to the first embodiment of the present invention uses the same format of the conventional uplink bandwidth request message, but changes the purpose of each field. In other words, a group representative identifier that can represent a group is recorded in the connection ID field 410. In this case, the group representative identifier may be a connection ID or a pre-negotiated group identifier arbitrarily selected in each group as described above. The base station identifies each group through the connection ID recorded in the connection ID field 410, and allocates bandwidth to each terminal based on the connection ID. In addition, the bandwidth request field 420 records the total amount of bandwidth requested by one or more connection IDs belonging to each group. In this case, the total amount of bandwidth is simply the sum of the bandwidths required by one or more connection IDs. The relay 120 may simultaneously request the total bandwidth requested by the plurality of connection IDs through one message.

5 is a diagram illustrating another example of a format of a bandwidth request message for each group that a relay transmits to a base station 130 when there is no uplink packet.

Conventional bandwidth request messages include HT field 1 bit, EC field 1 bit, type 3 bits, bandwidth request field 19 bits (BR MSB 11 bits and BR LSB bits), connection ID field 16 bits (CID MSB 8 bits and CID LSB 8). Bits), which has a size of 48 bits, that is, 6 bytes of 8 bits of the HCS field.

In the above embodiment, one bit of the bits allocated to the conventional bandwidth request field is switched to the type field to record the bandwidth request identifier 510 for each group indicating that the bandwidth is requested for each group. In the remaining fields, as in the case of FIG. 4, a group representative identifier representing a group is recorded in the connection ID field 520, and in the bandwidth request field 530, a total bandwidth of one or more connection IDs belonging to each group is requested. Record the amount. The relay 120 may simultaneously request the total bandwidth requested by the plurality of connection IDs through one message using the changed group-specific bandwidth request message.

In this case, although FIG. 5 illustrates an example in which 1 bit allocated to the bandwidth request field is switched to the type field, it is not necessarily limited thereto, and 1 bit allocated to the connection ID field or the HCS field is assigned to the type field. It is also possible to switch to batch.

Second Embodiment

The internal structure of the relay 120 and the grouping concept of the uplink bandwidth according to the second embodiment are the same as those shown in FIGS. 2 and 3. However, the second embodiment differs from the first embodiment in that a group-specific bandwidth request message is generated using the general MAC header 602 present in the uplink packet and the extended subheader 604 concatenated thereto.

6 is a diagram illustrating an example of a format of a bandwidth request message for each group according to the second embodiment of the relay 120 transmitting to the base station 130 when an uplink packet exists.

Every uplink packet includes a generic MAC header (602). In this embodiment, the bandwidth of the connection IDs grouped using the uplink packet is to be requested.

As shown in FIG. 6, when the Extended Subheader Field (ESF) 610 of the general MAC header is set to 1, it means that the extended subheader 604 is connected to the general MAC header 602. The connection ID 620 means a connection ID transmitting an uplink packet. In this case, the connection ID 620 should be able to form a group based on the same criteria as connection IDs for requesting an uplink bandwidth to the group. That is, even when transmitting an uplink packet, if the connection ID 620 cannot be grouped into the same group as the connection ID constituting the group, an uplink bandwidth request should be performed according to the first embodiment. When the grouping is possible, the connection ID 620 may be used as a group representative identifier representing a group formed based on the same criteria.

The extended subheader 604 concatenated to the general MAC header 602 may include an extended subheader group length field 630, an extended subheader type field 640, a request bandwidth field 650, and the like. In this case, an identifier indicating the total length of the subheader group is recorded in the extended subheader group length (630) field. In the Extended subheader type (640) field, a usage identifier for identifying a subheader's purpose is recorded. In the request bandwidth field 650, the total bandwidth required by the group represented by the connection ID is required. The amount of is recorded.

The base station 130 then detects that the extended subheader for the corresponding group is concatenated (ESF = 1) through the connection ID 620 and the ESF 610 of the generic MAC header 602, and the extended subheader The length of the group 630 can be known from the group length field of, and after confirming the usage (640, bandwidth request) of the concatenated extended subheader from the type of the extended subheader, Through the amount, it is possible to determine the total amount of bandwidth requested by the group (CID). Then, the base station 130 generates an uplink map by allocating bandwidth for each terminal 110 based on the connection ID CID, and transmits the uplink map to the relay 120.

<Uplink Bandwidth Request Flowchart>

FIG. 7 illustrates that a relay 120 that receives an uplink bandwidth request from a plurality of terminals 110A and 110B in a multi-hop relay network according to an embodiment of the present invention groups the same and requests the base station 130 for the bandwidth for each group. This is a flow chart showing the process.

First, the plurality of terminals 110A and 110B request the relay 120 for the uplink bandwidth required by the connection ID in steps S710A and S710B, respectively. In this case, steps S710A and S710B merely indicate that a bandwidth is requested to the relay 120 from one or more terminals, and is not necessarily limited to the transmission order.

After receiving a bandwidth request from at least one terminal, the relay 120 groups the uplink bandwidth request according to a predetermined criterion in step S720. In this case, the relay 120 may group bandwidth requests for connection IDs according to a predetermined criterion such as grouping for the same type of service (for example, voice communication, data communication, and video communication).

After the grouping process is performed, the relay 120 generates a bandwidth request message for each group including information on the required bandwidth size for each group in step S730. In this case, the relay 120 may request bandwidth by generating a bandwidth request message for each group when the uplink does not exist (first embodiment), and when the uplink exists, the relay 120 is included in all uplink packets. It is also possible to request bandwidth (second embodiment) using an extension header concatenated with a general MAC header. The relay 120 transmits the bandwidth request message for each group to the base station 130 in step S740.

After receiving the bandwidth request message for each group transmitted from the relay 120, the base station 130 identifies the group through the connection ID. In addition, the base station 130 generates an uplink map for allocating a bandwidth required for each terminal 110A and 110B in step S750. In operation S760, the base station 130 transmits the generated uplink map to the relay 120.

The relay 120 receives the uplink map transmitted from the base station 130 and transmits the uplink map transmitted from the base station in steps S770A and S770B to the first terminal 110A and the second terminal 110B. . Then, the first terminal 110A and the second terminal 110B receiving the uplink map identify the uplink bandwidth allocated to the uplink map.

FIG. 8 is a flowchart illustrating a process in which a relay 120 receives an uplink bandwidth request from a terminal, groups the same, and requests the group-specific bandwidth from the base station 130 again. Hereinafter, a description will be given with reference to FIGS. 3 and 8.

First, the relay 120 determines whether a bandwidth request message is received from the terminal in step S810. In this case, as described in FIG. 3, the relay 120 receives a bandwidth request according to one or more connection IDs generated from one or more terminals. When the relay 120 receives the bandwidth request message from the terminal, the relay 120 temporarily stores the message received in step S820 in a buffer. The bandwidth request messages stored in the buffer are grouped according to a predetermined criterion after a certain period of time, and are converted into bandwidth request messages for each group.

The relay 120 repeats steps S810 to S820 until a specific period elapses, stores a bandwidth request message received from one or more terminals in a buffer, and detects that the specific period has elapsed in step S830. Then, in step S840, the relay 120 groups bandwidth requests for one or more terminals according to a predetermined criterion. Since the criteria for grouping have already been mentioned, a detailed description thereof will be omitted.

The relay 120 generates a bandwidth request message 325, 330, 335 for each group for the uplink bandwidth request for each group classified in the previous step in step S850, and the bandwidth request for each group generated in step S860. The message is transmitted to the base station 130. A detailed process for the S850 will be described later.

The relay 120 that transmits the bandwidth request message for each group to the base station 130 determines whether to receive the uplink map from the base station 130 in step S870. The uplink map includes information on slots allocated by the mobile station from the base station, timings of slots to be transmitted and bandwidth allocated thereto. When the relay 120 receives the uplink map in step S870, the relay 120 transmits the received uplink map to each terminal.

9 is a flowchart specifically illustrating a process of step S850 in which the relay 120 according to an embodiment of the present invention groups a bandwidth request received from each terminal according to a predetermined criterion to generate a bandwidth request message for each group. In this case, it is assumed that the format of the bandwidth request message for each group that the relay 120 generates when the uplink packet does not exist is in accordance with FIG. 5. Hereinafter, with reference to FIGS. 5, 6 and 9 will be described.

First, the relay 120 groups the bandwidth requests for one or more terminals according to a predetermined criterion, and then, in step S905, determines whether an uplink packet exists. The relay 120 generates a bandwidth request message for each group if no uplink packet exists, and the extended subheader 604 of the general MAC header 602 included in all uplink packets if the uplink packet exists. ) Includes bandwidth request information for each group.

When the relay 120 determines that there is no uplink packet in step S905, the relay 120 generates a bandwidth request message for each group in step S910 or below. That is, the relay 120 records the bandwidth request identifier 510 for each group which can identify that the bandwidth is requested for each group in step S910. In this case, the relay 120 may increase the type field of the conventional bandwidth request message by one bit to record the bandwidth request identifier 510 for each group. In addition, the relay 120 records an arbitrary connection ID that can represent a group in the connection ID field 520 in step S915. The base station 130 identifies the group based on the connection ID and allocates the bandwidth based on the group. After recording any connection ID, the relay 120 records the bandwidth required for each group in the bandwidth request field 530 in step S920.

The steps S910 to S920 merely illustrate an example of a process in which each field of the bandwidth request message for each group is recorded, but are not necessarily limited to the order thereof.

If the relay 120 determines that there is an uplink packet in step S905, it is determined in step S925 whether the connection ID of the uplink packet and the connection ID requesting uplink bandwidth to the group can be grouped on the same basis. do. When the relay 120 determines that the grouping is possible, the ESF field 610 of the general MAC header 602 included in the uplink packet is set to 1 in step S930. This means that the extended subheader 604 is concatenated with the generic MAC header 602. In operation S935, the relay 120 records the total length of the subheader group in the extended subheader group length field 630 and identifies the use of the subheader in the extended subheader type field 640 in step S940. Record the usage identifier. In operation S920, the relay 120 records the bandwidth requested for each group in the request bandwidth field 650.

If the relay 120 determines in step S925 that the connection ID of the uplink packet and the connection ID requesting the uplink bandwidth to the group cannot be grouped on the same basis, even if the uplink packet exists, the bandwidth request for each group is requested. The process of generating steps S910 to S920 is performed.

Steps S925 to S940 also represent an example of a process in which each field of the general MAC header and the extended subheader included in the uplink packet is recorded, but is not necessarily limited to this order.

The embodiments of the present invention disclosed in the present specification and drawings are merely illustrative of specific embodiments of the present invention and are not intended to limit the scope of the present invention in order to facilitate understanding of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical idea of the present invention can be carried out in addition to the embodiments disclosed herein.

1 is a schematic diagram illustrating a method for requesting an uplink bandwidth in a relay network according to an embodiment of the present invention.

2 is a block diagram showing the internal structure of a relay 120 according to an embodiment of the present invention.

3 is a diagram illustrating a process in which a relay 120 groups bandwidth requests for connection IDs received from terminals 110 according to a predetermined criterion.

 4 illustrates an example of a format of a bandwidth request message for each group that a relay transmits to a base station 130 when there is no uplink packet.

5 illustrates another example of a format of a bandwidth request message for each group that a relay transmits to a base station 130 when there is no uplink packet.

FIG. 6 illustrates an example of a format of a bandwidth request message for each group that the relay 120 transmits to the base station 130 when an uplink packet exists.

FIG. 7 illustrates that a relay 120 that receives an uplink bandwidth request from one or more terminals 110A and 110B in a multi-hop relay network according to an embodiment of the present invention groups the same and requests the base station 130 for the group-specific bandwidth. Flowchart showing the process.

FIG. 8 is a flowchart illustrating a process in which a relay 120 receives an uplink bandwidth request from a terminal, groups the same, and requests the group-specific bandwidth from the base station 130 again.

9 is a flowchart specifically illustrating a process of step S850 in which the relay 120 according to an embodiment of the present invention groups a bandwidth request received from each terminal according to a predetermined criterion to generate a bandwidth request message for each group.

Claims (17)

A bandwidth request method in a multi-hop relay network, Receiving an uplink bandwidth request message having at least one connection ID generated from at least one terminal; Grouping according to the connection ID included in the uplink bandwidth request message, and generating a bandwidth request message for each group for each group generated by the grouping; And And transmitting the generated bandwidth request message for each group to a base station. The method of claim 1, The connection ID includes information of a service type, a requested amount of bandwidth, priority, and delay, and the grouping is performed by at least one of the information. The method of claim 1, wherein generating the bandwidth request message for each group comprises: Determining whether an uplink packet exists; And Determining whether a connection ID of the uplink packet and a connection ID requesting an uplink bandwidth to a group can be grouped when the uplink packet exists. Request method. The method of claim 3, wherein the uplink packet is present and the grouping is possible. The bandwidth request message for each group is generated using a general MAC header and an extended subheader concatenated thereto. The method of claim 4, wherein the generic MAC header includes a connection ID field in which a group representative identifier is recorded. The extended subheader includes a type field indicating a bandwidth request for each group, and a bandwidth request field in which the total bandwidth required by the group is recorded. The method of claim 3, wherein the uplink packet does not exist or the uplink packet exists but the grouping is not possible. The bandwidth request message for each group includes a connection ID field in which a group representative identifier is recorded and a bandwidth request field in which a total amount of bandwidth requested by the one or more connection IDs is described. Request method. The method of claim 3, wherein the uplink packet does not exist. The bandwidth request message for each group includes a type field indicating a bandwidth request for each group, a connection ID field for recording a group representative identifier, and a bandwidth request field for describing the total amount of bandwidth requested by the one or more connection IDs. Bandwidth request method in a multi-hop relay network. The method of claim 1, Receiving an uplink map transmitted from a base station; And And allocating an uplink uplink bandwidth according to a terminal included in the uplink map to the one or more terminals. The method of claim 1, The uplink bandwidth request message is a bandwidth request method in a multi-hop relay network, characterized in that grouped according to at least one connection ID generated in the terminal. A bandwidth request method in a multi-hop relay network including a terminal, a relay, and a base station, Generating, by the terminal, an uplink bandwidth request message having one or more connection IDs and transmitting the generated uplink bandwidth request message to the relay; When the relay receives the uplink bandwidth request message, analyzes and groups the connection IDs, and generates a bandwidth request message for each group generated by the grouping and transmits the bandwidth request message to the base station; And And receiving, by the base station, the bandwidth request message for each group and allocating a bandwidth required by each terminal through an uplink map. A relay device for processing bandwidth requests in a multi-hop relay network, A group generation unit for generating a group by grouping an uplink bandwidth request having at least one connection ID generated from at least one terminal; And a group-specific bandwidth request message generator for generating a corresponding group-specific bandwidth request message according to the presence or absence of an uplink packet for each group. The method of claim 11, The connection ID includes information of a service type, a requested amount of bandwidth, a priority, and a delay, and the grouping is performed by at least one of the information. The method of claim 11, wherein when an uplink packet exists and a connection ID for requesting an uplink bandwidth to a group and a connection ID of the uplink packet are groupable, The bandwidth request message for each group is generated using a general MAC header and an extended subheader concatenated thereto. The method of claim 13, wherein the generic MAC header includes a connection ID field in which a group representative identifier is recorded. The extended subheader may include a type field in which the extended subheader indicates a bandwidth request for each group, and a bandwidth request field in which the total bandwidth required by the group is recorded. 12. The method of claim 11, wherein if no uplink packet is present, The bandwidth request message for each group includes a connection ID field in which a group representative identifier is recorded and a bandwidth request field in which a total amount of bandwidth requested by the one or more connection IDs is described. Device. 12. The method of claim 11, wherein an uplink packet does not exist or an uplink packet exists, but a connection ID requesting an uplink bandwidth cannot be grouped into a connection ID and a group of the uplink packet. The bandwidth request message for each group includes a type field indicating a bandwidth request for each group, a connection ID field for recording a group representative identifier, and a bandwidth request field for describing the total amount of bandwidth requested by the one or more connection IDs. Relay device in a multi-hop relay network. The method of claim 11, The uplink bandwidth request is relayed according to at least one connection ID generated in the terminal relay device in a multi-hop relay network, characterized in that.

Images