Method for relaying of base station, method for relaying of terminal and method for transmitting

CROSS-REFERENCE TO RELATED APPLICATION

p-0002This application claims priority to and the benefit of Korean Patent Application No. 10-2011-0019667, No. 10-2011-0031328, No. 10-2011-0043142, No. 10-2011-0068537, No. 10-2011-0068538, No. 10-2011-0068536, No. 10-2011-0068545, No. 10-2011-0068711, No. 10-2011-0112477, No. 10-2011-0112479, No. 10-2012-0022061, No. 10-2012-0022063, No. 10-2012-0022062, No. 10-2012-0022059, and No. 10-2012-0022060 filed in the Korean Intellectual Property Office on Mar. 4, 2011, Apr. 5, 2011, May 6, 2011, Jul. 11, 2011, Jul. 11, 2011, Jul. 11, 2011, Jul. 11, 2011, Jul. 12, 2011, Oct. 31, 2011, Oct. 31, 2011, Mar. 2, 2012, Mar. 2, 2012, Mar. 2, 2012, Mar. 2, 2012, and Mar. 2, 2012, respectively, the entire contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

p-0003(a) Field of the Invention The present invention relates to a method of relaying in a base station, a method of relaying in a terminal, and a method of transmitting in a terminal.

p-0004(b) Description of the Related Art

p-0005When a disaster or accident occurs, important parts of societal infrastructure may be broken or damaged. Various communication facilities such as wireless phones, wired phones, and the Internet network are important parts of societal infrastructure, and when such a communication facility is broken or damaged in a disaster or accident situation, societal congestion increases and restoration of society may be difficult. Therefore, in such a case, high reliability support of a means to quickly recover or replace a communication facility is important. In a high reliability support, a mobile communication system (HR-Network) should satisfy the following requirements.

p-0006First, the HR-Network should satisfy backward compatibility with an existing system, i.e., a system such as a Wireless MAN-OFDMA or Wireless MAN-Advanced Interface. Next, an HR-base station (HR-BS), an HR-mobile station (HR-MS), and an HR-relay station (HR-RS) should be able to perform a multi-mode operation that performs a role of other stations in addition to the respective roles thereof.

p-0007Even when an HR-BS, an HR-RS, or a wireless link is unavailable, i.e., even when a single point of failure (SPOF) occurs, communication should be maintained. Direct communication between other HR-MSs should be able to be performed. Multicast transmission, i.e., enhanced multicast communication, should be available within a network, and path management that manages path setting and forwarding for data transmission/reception should be available.

p-0008Particularly, for multi-mode operation, an HR-BS performs a role of an

p-0009HR-RS according to a situation of a backhaul link, or when an HR-BS or an HR-RS is absent, an HR-MS should perform a role of an HR-BS or an HR-RS. However, in the conventional art, only requirements for a multi-mode operation exist, and because technology regarding a method of continuously providing a service while a multi-mode operation does not exist, countermeasures are needed.

SUMMARY OF THE INVENTION

p-0010The present invention has been made in an effort to provide a method of relaying in a BS (base station), a method of relaying in a terminal (MS), and a method of transmitting in an MS having advantages of continuously servicing to a subordinate MS through a multi-mode operation when a backhaul link of a BS is damaged in a communication system, and more particularly, performing a role of a relay station (RS) as a BS establishes a relay link with an adjacent BS and smoothly restoring to an original BS when a backhaul link is recovered.

p-0011The present invention has been made in an effort to further provide a method of relaying in a BS, a method of relaying in an MS, and a method of transmitting in an MS having advantages of performing a smooth communication business as an MS performs a role of a BS or an RS.

p-0012The present invention has been made in an effort to further provide a method of relaying in a BS, a method of relaying in an MS, and a method of transmitting in an MS having advantages of transmitting a control message and continuously performs a transmission service when an MS performs a role of a BS or an RS in a communication system.

p-0013An exemplary embodiment of the present invention provides a method of relaying in a BS including: establishing, when a backhaul link of a first BS is damaged, a relay link using a second BS, which is an adjacent BS of the first BS as a serving BS; and releasing the relay link after the backhaul link is recovered

p-0014The release of the relay link may include transmitting, by the second BS, a handover request message that requests to perform handover to the first BS to an MS.

p-0015The release of the relay link may be performed through the recovered backhaul link.

p-0016An MS may wait until the first BS operates as a BS, and when the first BS operates as a BS, the MS may perform network reentry.

p-0017Another embodiment of the present invention provides a method of relaying in a BS, the method including: establishing, when a backhaul link of a first BS is damaged, a relay link between a first BS and a second BS, which is a serving BS; and notifying, by the first BS, the second BS that damage of the backhaul link is recovered, wherein the notifying of the second BS is performed through the recovered backhaul link.

p-0018Yet another embodiment of the present invention provides a method of relaying in a BS, the method including: scanning, when a backhaul link of a first BS is damaged, a downlink channel; synchronizing with a second BS that is connected to the backhaul link; acquiring a downlink parameter or an uplink parameter; performing ranging; and forming an operation parameter necessary for a relay link.

p-0019The method may further include: performing authentication, authority verification, and password exchange, if necessary; and performing re-registration with the second BS, if necessary.

p-0020Yet another embodiment of the present invention provides a method of relaying in a BS, the method including: establishing, by a first BS, a relay link with a second BS that is connected to a backhaul link; and providing, by the first BS, a service.

p-0021The method may further include notifying a subordinate apparatus to perform handover of establishment of the relay link, if necessary.

p-0022Yet another embodiment of the present invention provides a method of relaying in a BS, the method including: transmitting, by a first BS in which a backhaul link is damaged, a relay establishment request message to a second BS in which a backhaul link is connected; and receiving, by the first BS, a relay establishing response message including acceptance, rejection, and re-request from the second BS.

p-0023Yet another embodiment of the present invention provides a method of relaying in an MS, the method including: reporting, by the MS, a capability of the MS for a role of an RS to a BS; and performing, by the MS, a role of the RS.

p-0024The reporting of a capability of the MS may be performed in a process in which the MS performs initial access; and the performing of a role of the RS may be determined by the BS.

p-0025Yet another embodiment of the present invention provides a method of relaying in an MS, the method including: receiving, by the MS, a relay establishing request message from a BS; and transmitting, by the MS, a relay establishing response message to the BS.

p-0026The relay establishing request message may include a relay mode including a time-division transmit & receive (TTR) mode or a simultaneous transmit & receive (STR) mode.

p-0027The method may further include operating, by the MS, as an RS as a relay link is established to the MS, wherein the operating of as an RS may include maintaining, by the MS, a function of the MS.

p-0028Yet another embodiment of the present invention provides a method of relaying in an MS, the method including: transmitting, by the MS to which a relay link is established, a relay link release request message to a BS; and receiving, by the MS, a relay link release response message from the BS.

p-0029The relay link release response message may include an action time, and the method may further include transmitting, by the MS, a re-request to the BS after the action time has expired.

p-0030The MS may release a relay mode immediately or after the action time is complete, after the relay link release response message is received.

p-0031The relay link release response message may include a rejection, and the MS may maintain the relay link when the MS receives the rejection.

p-0032Yet another embodiment of the present invention provides a method of transmitting in an MS, the method including: operating the MS in a multi-mode; and transmitting a control message for supporting the multi-mode to a subordinate apparatus.

p-0033The transmitting of a control message may be performed when a backhaul link is damaged or recovered.

p-0034The transmitting of a control message may be performed in at least one of when a backhaul link is damaged or recovered, when it is necessary to reconfigure a parameter of at least one of a physical layer PHY and an MAC layer while the MS maintains a relay link as the backhaul link is unavailable, and when notifying establishment, release, or a change of the multi-mode to the subordinate apparatus, and when it is necessary to reconfigure a parameter of at least one of a physical layer PHY and an MAC layer may include at least one of power down, power reduction, and a frequency allocation (FA) change.

p-0035Yet another embodiment of the present invention provides a method of transmitting in a BS, the method including: operating the BS in a multi-mode; and transmitting a control message for supporting the multi-mode to a subordinate apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

p-0036<figref idrefs="DRAWINGS">FIG. 1</figref> is a diagram illustrating a general communication situation.

p-0037<figref idrefs="DRAWINGS">FIG. 2</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to an exemplary embodiment of the present invention.

p-0038<figref idrefs="DRAWINGS">FIG. 3</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention.

p-0039<figref idrefs="DRAWINGS">FIG. 4</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention.

p-0040<figref idrefs="DRAWINGS">FIG. 5</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention.

p-0041<figref idrefs="DRAWINGS">FIG. 6</figref> is a flowchart illustrating a method of operating a BS when a backhaul link is recovered according to another exemplary embodiment of the present invention.

p-0042<figref idrefs="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a method of operating a BS when a backhaul link is recovered according to another exemplary embodiment of the present invention.

p-0043<figref idrefs="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a method of relaying in a BS according to an exemplary embodiment of the present invention.

p-0044<figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart illustrating a method of relaying in a BS according to another exemplary embodiment of the present invention.

p-0045<figref idrefs="DRAWINGS">FIG. 10</figref> is a flowchart illustrating a method of relaying in an MS according to another exemplary embodiment of the present invention.

p-0046<figref idrefs="DRAWINGS">FIG. 11</figref> is a flowchart illustrating a method of transmitting in an MS according to another exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

p-0047In the following detailed description, only certain exemplary embodiments of the present invention have been shown and described, simply by way of illustration. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. Accordingly, the drawings and description are to be regarded as illustrative in nature and not restrictive. Like reference numerals designate like elements throughout the specification.

p-0048In the entire specification, a mobile station (MS) may indicate a terminal, a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS), an access terminal (AT), user equipment (UE), an advanced mobile station (AMS), and a high reliability mobile station (HR-MS), and may include an entire function or a partial function of the terminal, the MT, the SS, the PSS, the AT, the UE, the AMS, and the HR-MS.

p-0049Further, a base station (BS) may indicate a node B, an evolved node B (eNode B), an access point (AP), a radio access station (RAS), a base transceiver station (BTS), a mobile multihop relay (MMR)-BS, an advanced base station (ABS), a high reliability base station (HR-BS), a relay station (RS) that performs a function of the BS, an advanced relay station (ARS), and a high reliability relay station (HR-RS) that performs a function of the BS, and may include an entire function or a partial function of the node B, the eNode B, the AP, the RAS, the BTS, the MMR-BS, the ABS, the HR-BS, the RS, the ARS, and the HR-RS.

p-0050Hereinafter, a method of relaying in a base station will be described in detail with reference to the drawings.

p-0051<figref idrefs="DRAWINGS">FIG. 1</figref> is a diagram illustrating a general communication situation,

p-0052<figref idrefs="DRAWINGS">FIG. 2</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to an exemplary embodiment of the present invention,

p-0053<figref idrefs="DRAWINGS">FIG. 3</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention,

p-0054<figref idrefs="DRAWINGS">FIG. 4</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention, and

p-0055<figref idrefs="DRAWINGS">FIG. 5</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention.

p-0056Referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, a general communication system includes a server <b>400</b> that manages BSs <b>110</b> and <b>120</b>, an MS <b>210</b> that transmits and receives to and from the BS <b>110</b>, and an MS <b>220</b> that communicates with the BS <b>110</b> through an RS <b>310</b> to which a relay link is established. In this case, the BSs <b>110</b> and <b>120</b> are connected by a backhaul link.

p-0057When a backhaul link of the BS <b>110</b> is collapsed, the BS <b>110</b> temporally establishes a relay link with the BS <b>120</b> and performs a role of an RS. In this case, the BS <b>110</b> should provide a continuous service to a subordinate RS <b>310</b> in which a relay link is established with the BS <b>110</b>, a subordinate MS <b>210</b> that transmits and receives to and from the BS <b>110</b>, and a subordinate MS <b>220</b> that is connected to the RS <b>310</b>.

p-0058<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a case where the BS <b>110</b> is recognized as a BS by the subordinate RS <b>310</b> or the subordinate MS <b>210</b> even if a backhaul link of the BS <b>110</b> is collapsed.

p-0059In <figref idrefs="DRAWINGS">FIG. 2</figref>, the BS <b>110</b> and the BS <b>120</b> establish a relay link and notify the subordinate MS <b>210</b> of such a fact, or performs a role of a BS without notification of such a fact and services only data that should be transmitted to a superordinate server <b>400</b> through a relay link with the BS <b>120</b>. In this case, the BS <b>110</b> performs a function of a BS while maintaining configuration information for operating a previous BS or performs a role of a BS based on a new network configuration information that it receives from the BS <b>120</b>.

p-0060<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates a case where the BS <b>110</b> requests handover to the BS <b>120</b> from the subordinate RS <b>310</b> or the subordinate MS <b>210</b> when a backhaul link of the BS <b>110</b> is collapsed. In response to a handover request of the BS <b>110</b>, the subordinate RS <b>310</b> and the subordinate MS <b>210</b> perform handover to the BS <b>120</b> or temporally stop communication until relay link establishment of the BS <b>110</b> is complete. Further, in order to perform an efficient handover process, the BS <b>110</b> shares MAC context information with the BS <b>120</b> of the subordinate RS <b>310</b> and the subordinate MS <b>210</b> between the BS <b>120</b> and the BS <b>110</b>. The BS <b>110</b> performs such sharing through a backhaul link before the backhaul link is collapsed, and performs such sharing through a preset relay link if the backhaul link is collapsed. When a backhaul link is recovered, a relay link that is established with the BS <b>120</b> is unnecessary and thus the BS <b>110</b> performs relay link release. In this case, the BS <b>110</b> requests callback handover that calls back the subordinate RS <b>310</b> or the subordinate MS <b>210</b> in which handover to the BS <b>120</b> is performed from the BS <b>120</b>, thereby returning the subordinate RS <b>310</b> or the subordinate MS <b>210</b> from the BS <b>120</b>.

p-0061<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a case where the BS <b>110</b> is recognized as an RS by the subordinate RS <b>310</b> or the subordinate MS <b>210</b> when a backhaul link of the BS <b>110</b> is collapsed.

p-0062In this case, the BS <b>110</b> performs a role as a subordinate RS of the BS <b>120</b>. That is, the BS <b>110</b> may perform a method of establishing a new relay link with the subordinate RS <b>310</b> or a method of reusing a previously established relay link.

p-0063<figref idrefs="DRAWINGS">FIG. 5</figref> illustrates a case where the BS <b>110</b> requests handover to the BS <b>120</b> from the subordinate RS <b>310</b> or the subordinate MS <b>210</b> if the BS <b>110</b> needs to change its operation mode to an RS operation mode when a backhaul link of the BS <b>110</b> is collapsed. In response thereto, the subordinate MS <b>210</b> performs handover to the BS <b>120</b> or temporally stops communication until relay link establishment of the BS <b>110</b> is complete. In order to start a relay link with the BS <b>110</b>, the subordinate RS <b>310</b> temporally stops communication. In order to perform an efficient handover process, the BS <b>110</b> shares MAC context information with the BS <b>120</b> of the subordinate RS <b>310</b> and the subordinate MS <b>210</b> between the BS <b>120</b> and the BS <b>110</b>. In this case, the BS <b>110</b> may perform a sharing procedure, as in a case of <figref idrefs="DRAWINGS">FIG. 3</figref>, perform release when a backhaul link is recovered, and perform callback handover to the BS <b>120</b>.

p-0064When a backhaul link is collapsed, in order for the BS <b>110</b> to temporally perform a role of an RS with the adjacent BS <b>120</b> through a relay link and to retuen its mode from an RS operation mode to an original BS mode, a procedure that notifies or deregisters corresponding contents to the server <b>400</b> or the adjacent BS <b>120</b> to an original BS mode is necessary. Before starting a release action, the BS <b>110</b> enables the subordinate MS <b>210</b> or the subordinate RS <b>310</b> to perform handover to another BS, or instructs to request a service to another BS or an RS. Alternatively, when it is unnecessary to receive a service from an adjacent BS or an RS until a release action completion time, the MS <b>210</b> waits until the BS <b>110</b> in a present RS operation mode returns back to the original BS and performs network reentry after release, thereby resuming a service.

p-0065In this way, according to an exemplary embodiment of the present invention, when a backhaul link of a BS is damaged, the BS establishes a relay link with an adjacent BS and performs a role of an RS, thereby performing a smooth communication function.

p-0066Hereinafter, a method of releasing a relay link according to another exemplary embodiment of the present invention will be described in detail with reference to <figref idrefs="DRAWINGS">FIGS. 6 and 7</figref>.

p-0067<figref idrefs="DRAWINGS">FIG. 6</figref> is a flowchart illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to an exemplary embodiment of the present invention, <figref idrefs="DRAWINGS">FIG. 3</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention, <figref idrefs="DRAWINGS">FIG. 4</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention, and <figref idrefs="DRAWINGS">FIG. 5</figref> is a diagram illustrating an example in which a BS establishes a relay link when a backhaul link is damaged according to another exemplary embodiment of the present invention.

p-0068Referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, a general communication system includes a server <b>400</b> that manages BSs <b>110</b> and <b>120</b>, an MS <b>210</b> that transmits and receives to and from the BS <b>110</b>, and an MS <b>220</b> that communicates with the BS <b>110</b> through an RS <b>310</b> to which a relay link is established. In this case, the BSs <b>110</b> and <b>120</b> are connected by a backhaul link.

p-0069If a backhaul link of the BS <b>110</b> is collapsed, the BS <b>110</b> temporally establishes a relay link with the BS <b>120</b>, and the BS <b>110</b> performs a role of an RS. In this case, the BS <b>110</b> should provide a continuous service to the subordinate RS <b>310</b> in which a relay link is established with the BS <b>110</b>, the subordinate MS <b>210</b> that transmits and receives to and from the BS <b>110</b>, and the subordinate MS <b>220</b> that is connected to the RS <b>310</b>.

p-0070When a backhaul link is collapsed, in order for the BS <b>110</b> to temporally perform a role of an RS with the adjacent BS <b>120</b> through a relay link and to retuen its mode from an RS operation mode to an original BS mode, it is necessary to notify or deregister corresponding contents to the server <b>400</b> or the adjacent BS <b>120</b>. Before starting a release action, the BS <b>110</b> enables the subordinate MS <b>210</b> or the subordinate RS <b>310</b> to perform handover to another BS, or instructs to request a service from another BS or an RS. Alternatively, when it is unnecessary to receive a service from an adjacent BS or an RS until a release action completion time, the MS <b>210</b> waits until the BS <b>110</b> in a present RS operation mode returns back to an original BS and performs network reentry after release, thereby resuming a service.

p-0071In this way, according to an exemplary embodiment of the present invention, when a backhaul link of a BS is damaged, the BS establishes a relay link with an adjacent BS and performs a role of an RS, thereby performing a smooth communication operation.

p-0072Hereinafter, a method of releasing a relay link according to another exemplary embodiment of the present invention will be described in detail with reference to <figref idrefs="DRAWINGS">FIGS. 6 and 7</figref>.

p-0073<figref idrefs="DRAWINGS">FIG. 6</figref> is a flowchart illustrating a method of operating a BS when a backhaul link is recovered according to an exemplary embodiment of the present invention, and <figref idrefs="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a method of operating a BS when a backhaul link is recovered according to another exemplary embodiment of the present invention.

p-0074Because the backhaul link was recovered, a necessary process upon performing a release action with recovery of a backhaul link may be performed using the backhaul link or using an already established relay link. Further, when recovery of the backhaul link is predicted, a necessary process may be previously performed through an already established relay link.

p-0075Referring to <figref idrefs="DRAWINGS">FIGS. 6 and 7</figref>, the relay mode BS <b>110</b> to perform deregistration first transmits a deregistration request message (DREG-REQ) to the adjacent BS <b>120</b> (S<b>611</b> and S<b>711</b>).

p-0076The BS <b>110</b> transmits a handover request message (HO-CMD) to the adjacent BS <b>120</b> while requesting deregistration from the subordinate MS <b>210</b> (S<b>612</b> and S<b>712</b>). In this case, the BS <b>120</b> stores MS related information and quickly resumes a service for the MS <b>210</b> that returns to a service zone. Further, the BS <b>110</b> transmits information of a recommended BS <b>120</b> when performing handover, a callback handover available time, and a service resumption start time after the BS <b>110</b> is converted to a BS mode to the MS <b>210</b>, thereby assisting service resumption.

p-0077When the BS <b>110</b> is converted to a BS mode, if the MS <b>210</b> cannot perform handover to the BS <b>120</b> or the RS <b>310</b> until a service resumption start time, if the MS <b>210</b> is in a state such as a sleep mode or an idle mode, or if it is unnecessary to perform handover, the BS <b>110</b> stays in a present cell until a service resumption start time, and after being converted to a BS mode, the BS <b>110</b> performs network reentry.

p-0078The BS <b>110</b> requests to establish a relay link with the BS <b>120</b> from the subordinate RS <b>310</b>. In this case, the BS <b>110</b> stores corresponding subordinate RS related information and restores a relay link when a service to the BS is resumed. In this case, the BS <b>110</b> transmits information of the BS <b>120</b>, callback handover available time, and a service resumption start time after changing its mode to a BS mode to the subordinate RS <b>310</b>, thereby assisting service resumption.

p-0079Thereafter, the BS <b>120</b> transmits a deregistration response message (DREG-RSP) to the BS <b>110</b> (S<b>613</b> and S<b>713</b>). For this purpose, at least one of the following conditions should be satisfied.

p-0080First, in order to transmit a DREG-RSP, the MS <b>210</b> within the BS <b>110</b> should complete handover to the BS <b>120</b>. Next, the RS <b>310</b> within the BS <b>110</b> should complete setting of a relay link with the BS <b>120</b>. Next, a specific timer, i.e., a release completion estimation time, is established regardless of whether the MS <b>210</b> performs handover to the BS <b>120</b>, and a corresponding timer should expire (S<b>713</b>).

p-0081When the release is complete, the BS <b>110</b> no longer operates in a relay mode, releases a relay link with the BS <b>120</b>, and operates as a BS.

p-0082Thereafter, in a process of releasing a relay link, the BS <b>110</b> requests a message, i.e., a callback handover request message (Callback-REQ), that requests to return the RS <b>310</b> that performs handover to the BS <b>120</b> or that establishes a relay link to the BS <b>110</b>, from the BS <b>120</b> (S<b>614</b>). In this case, the BS <b>110</b> may quickly resume a service or request related information from the BS <b>120</b> and receive related information from the BS <b>120</b> using the MS <b>210</b> and the RS <b>310</b> related information that is stored upon previously releasing. Further, the BS <b>110</b> requests the stored information from the MS <b>210</b> and performs optimum handover to the MS <b>210</b> that performs callback handover.

p-0083Thereafter, the BS <b>120</b> transmits an HO-CMD to the MS <b>210</b> (S<b>615</b>). Further, after handover is complete, communication between the MS <b>210</b> and the BS <b>110</b> is resumed (S<b>616</b> and S<b>716</b>).

p-0084A procedure in which the BS <b>110</b> releases a relay link may be performed by a request of the BS <b>110</b>, but a relay link of the BS <b>110</b> may be released by a request of the BS <b>120</b>. In this case, the BS <b>120</b> forwards a DREG-RSP to the BS <b>110</b> and performs the above-described release process in response thereto and establishes a relay link with another BS, or the BS <b>120</b> operates as a network that performs a role without backhaul link communication i.e., a standalone network. In this case, when a BS establishes a relay link with another BS, an RS performs handover between BSs, and an operation in which an RS performs handover may be performed equally to or similarly to operation in which an MS performs handover. In a process of performing release, a timer such as a request duration (REQ-Duration) is included in a DREG-RSP, and when a corresponding timer has expired, a deregistration request message is retransmitted, or after a backhaul link and a relay link coexist, a time point at which deregistration of a relay link is complete may be notified. Further, the BS <b>120</b> may reject release. In this case, the BS <b>110</b> may maintain a relay link with the BS <b>120</b>. A release estimated time of a backhaul link may be a time corresponding to an REQ-Duration.

p-0085In this way, according to an exemplary embodiment of the present invention, when a backhaul link of a BS is damaged, the BS performs a role of an RS by establishing a relay link with an adjacent BS, and a mode of the BS is returned back to an original BS mode after a backhaul link is recovered, thereby performing a smooth communication operation.

p-0086Hereinafter, a method of managing the subordinate MS <b>210</b> in a process of establishing a relay link while the BS <b>110</b> performs a BS service will be described in detail with reference to <figref idrefs="DRAWINGS">FIGS. 8 and 9</figref>.

p-0087<figref idrefs="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a method of relaying in a BS according to an exemplary embodiment of the present invention, and <figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart illustrating a method of relaying in a BS according to another exemplary embodiment of the present invention.

p-0088Unlike the step in which a conventional RS establishes a relay link when a backhaul link of a BS is damaged, a relay link is established through the following process.

p-0089First, a BS scans a downlink channel (S<b>210</b>), and the BS synchronizes with a BS that is connected to a backhaul link (S<b>220</b>). Thereafter, the BS acquires a downlink and uplink parameter from a superframe header (S<b>230</b>). Thereafter, the BS performs ranging (S<b>240</b>), and the BS starts a relay link using a relay establishing request message (AAI-MMRS-REQ)/RSP message. The BS performs authentication, authority verification, and password exchange, if necessary (S<b>250</b>), and because the BS is being already serviced, such a process may be omitted. Further, the BS performs (re)registration with the BS, if necessary (S<b>260</b>), and because the BS is being already serviced, a registration procedure may be omitted. Thereafter, the BS forms an operation parameter (S<b>270</b>).

p-0090Referring again to <figref idrefs="DRAWINGS">FIG. 3</figref>, a process of establishing a relay link with another BS includes a step of starting relay link establishment including capability negotiation according to a capability of a BS in which a backhaul link is disconnected (S<b>310</b>), i.e., a step of using an AAI-MMRS-REQ/RSP message, a step of completing relay link establishment (S<b>320</b>), i.e., step of forming an operation parameter, a step of managing a relay link after setting is complete (S<b>330</b>), and a step of releasing a relay link (S<b>340</b>).

p-0091First, the start step (S<b>310</b>) including a relay link establishment capability report of a BS will be described.

p-0092Setting of a relay link between a BS (hereinafter, a subordinate BS) in which a backhaul link is disconnected and a BS (hereinafter, a superordinate BS) in which a backhaul link is connected or an RS may be performed by a request of the subordinate BS or may be performed as the superordinate BS requests to the subordinate BS. The subordinate BS may operate with time-division transmit and receive (TTR) or simultaneous transmit and receive (STR) according to a capability of a BS.

p-0093Such a capability may be shared by an interface through a backbone network between BSs before a backhaul link is disconnected, and may be shared in a situation in which a backhaul link is disconnected or immediately before a disconnection of a backhaul link is predicted. In a situation in which a backhaul link is disconnected, such a capability may be shared in a process of requesting and responding to relay link establishment.

p-0094In a TTR mode, a capability report including a transmit/receive transition gap (TTG), i.e., a minimum receive-to-transmit turnaround gap, and a receive/transmit transition gap (RTG), i.e., a minimum transmit-to-receiver turnaround gap, is additionally transmitted. Further, after a relay link is established, corresponding information may be considered in setting a frame format.

p-0095In an STR mode, a capability report including a frequency for a relay link and a frequency for servicing a subordinate MS after establishment of a relay link may be transmitted. When a capability between BSs or a configuration parameter is included with a backhaul link, if a ranging process is complete, it is regarded as a start of relay link establishment of a subordinate BS, and by performing only a configuration step of an operation parameter, relay link establishment may be complete.

p-0096When it is requested to set a relay link from a superordinate BS to a subordinate BS, a capability report may be generally usefully used, and additional information TTG/RTG after establishment of the relay link may be included in a process in which the subordinate BS responds to a request of the superordinate BS.

p-0097For relay link establishment, according to another exemplary embodiment of the present invention, in addition to a method of setting a relay link of an RS that is defined in the existing conventional art, a relay establishment request message and a response message may be included. A relay establishment request message AAI-MMRS-REQ and a relay establishment response message (AAI-MMRS-RSP) are shown in Tables 1 and 2, respectively.

p-0098<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="84pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="84pt" align="left" /><colspec colname="4" colwidth="28pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry>Con-</entry></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>dition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="84pt" align="left" /><colspec colname="2" colwidth="21pt" align="char" char="." /><colspec colname="3" colwidth="84pt" align="left" /><colspec colname="4" colwidth="28pt" align="left" /><tbody valign="top"><row><entry>Request Relay mode</entry><entry>1</entry><entry>0b0: TTR relay mode</entry><entry>Always</entry></row><row><entry /><entry /><entry>0b1: STR relay mode</entry><entry>present</entry></row><row><entry>If (this request is</entry><entry /><entry /><entry /></row><row><entry>subordinate station</entry><entry /><entry /><entry /></row><row><entry>initiated request) {</entry><entry /><entry /><entry /></row><row><entry> If (request relay mode ==</entry><entry /><entry /><entry /></row><row><entry> 0b0) {</entry><entry /><entry /><entry /></row><row><entry>  ARSTTG</entry><entry>6</entry><entry>ARSTTG value (μs).</entry><entry /></row><row><entry /><entry /><entry>It shall be less</entry><entry /></row><row><entry /><entry /><entry>than 50 μs.</entry><entry /></row><row><entry>  ARSRTG</entry><entry>6</entry><entry>ARSRTG value (μs).</entry><entry /></row><row><entry /><entry /><entry>It shall be less</entry><entry /></row><row><entry /><entry /><entry>than 50 μs.</entry><entry /></row><row><entry> } else if (request</entry><entry /><entry /><entry /></row><row><entry> relay mode == 0b1) {</entry><entry /><entry /><entry /></row><row><entry>  Duplex mode support</entry><entry>2</entry><entry>If bit 0 = 1, FDD supports</entry><entry /></row><row><entry> indication</entry><entry /><entry>If bit 1 = 1, TDD supports</entry><entry /></row><row><entry>  for (i=1;</entry><entry /><entry>N-frequency is the</entry><entry /></row><row><entry> i&lt;=N-frequency; i++) {</entry><entry /><entry>number of available</entry><entry /></row><row><entry /><entry /><entry>frequencies to communicate</entry><entry /></row><row><entry /><entry /><entry>[1..16].</entry><entry /></row><row><entry>   Carrier frequency</entry><entry>10</entry><entry>Indicates the carrier</entry><entry /></row><row><entry /><entry /><entry>frequency in unit</entry><entry /></row><row><entry /><entry /><entry>of 100 KHz.</entry><entry /></row><row><entry>  }</entry><entry /><entry /><entry /></row><row><entry> }</entry><entry /><entry /><entry /></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0099<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="63pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="105pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 2</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="63pt" align="left" /><colspec colname="2" colwidth="21pt" align="char" char="." /><colspec colname="3" colwidth="105pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><tbody valign="top"><row><entry>If (the response is</entry><entry /><entry /><entry>Present when</entry></row><row><entry>transmitted by</entry><entry /><entry /><entry>superordinate HR-BS</entry></row><row><entry>HR-BS) {</entry><entry /><entry /><entry>responds to the</entry></row><row><entry /><entry /><entry /><entry>subordinate station</entry></row><row><entry /><entry /><entry /><entry>initiated request.</entry></row><row><entry> Response code</entry><entry>2</entry><entry>0b00: in response to the</entry><entry /></row><row><entry /><entry /><entry>AAI-MMRS-REQ message</entry><entry /></row><row><entry /><entry /><entry>to accept the request</entry><entry /></row><row><entry /><entry /><entry>0b01: in response to the</entry><entry /></row><row><entry /><entry /><entry>AAI-MMRS-REQ message</entry><entry /></row><row><entry /><entry /><entry>to allow to transmit</entry><entry /></row><row><entry /><entry /><entry>subordinate station</entry><entry /></row><row><entry /><entry /><entry>initiated AAI-ARE-REQ</entry><entry /></row><row><entry /><entry /><entry>after action time expires</entry><entry /></row><row><entry /><entry /><entry>0b10: in response to the</entry><entry /></row><row><entry /><entry /><entry>AAI-MMRS-REQ message</entry><entry /></row><row><entry /><entry /><entry>to reject the request 0b11: reserved</entry><entry /></row><row><entry> If (response</entry><entry /><entry /><entry /></row><row><entry>code == 0b01) {</entry><entry /><entry /><entry /></row><row><entry>  Action time</entry><entry>4</entry><entry>LSBs of the superframe</entry><entry>Always present</entry></row><row><entry /><entry /><entry>number when the</entry><entry /></row><row><entry /><entry /><entry>subordinate station</entry><entry /></row><row><entry /><entry /><entry>transmits AAI-MMRS-REQ</entry><entry /></row><row><entry /><entry /><entry>message.</entry><entry /></row><row><entry> }</entry><entry /><entry /><entry /></row><row><entry>} else {</entry><entry /><entry /><entry>Present when</entry></row><row><entry /><entry /><entry /><entry>subordinate station</entry></row><row><entry /><entry /><entry /><entry>responds to the</entry></row><row><entry /><entry /><entry /><entry>superordinate HR-BS</entry></row><row><entry /><entry /><entry /><entry>initiated request.</entry></row><row><entry> If (received</entry><entry /><entry /><entry>// TTR mode</entry></row><row><entry> request relay</entry><entry /><entry /><entry /></row><row><entry> mode == 0b0) {</entry><entry /><entry /><entry /></row><row><entry>  ARSTTG</entry><entry>6</entry><entry>ARSTTG value (μs). It</entry><entry>Shall be present if</entry></row><row><entry /><entry /><entry>shall be less than 50 μs.</entry><entry>action code == 0b0 in</entry></row><row><entry /><entry /><entry /><entry>AAI-MMRS-REQ.</entry></row><row><entry>  ARSRTG</entry><entry>6</entry><entry>ARSRTG value (μs). It</entry><entry>Shall be present if</entry></row><row><entry /><entry /><entry>shall be less than 50 μs.</entry><entry>action code == 0b0 in</entry></row><row><entry /><entry /><entry /><entry>AAI-MMRS-REQ.</entry></row><row><entry> } else if</entry><entry /><entry /><entry>// STR mode</entry></row><row><entry> (received</entry><entry /><entry /><entry /></row><row><entry> request relay</entry><entry /><entry /><entry /></row><row><entry> mode == 0b1) {</entry><entry /><entry /><entry /></row><row><entry>  Duplex mode</entry><entry>2</entry><entry>If bit 0 = 1, FDD supports</entry><entry>Always present</entry></row><row><entry> support</entry><entry /><entry>If bit 1 = 1, TDD supports</entry><entry /></row><row><entry> indication</entry><entry /><entry /><entry /></row><row><entry>  for (i=1;</entry><entry /><entry>N-frequency is the number</entry><entry /></row><row><entry> i&lt;=N-frequency;</entry><entry /><entry>of available frequencies to</entry><entry /></row><row><entry> i++) {</entry><entry /><entry>communicate [1..16].</entry><entry /></row><row><entry>  Carrier</entry><entry>10</entry><entry>Indicates the carrier</entry><entry /></row><row><entry> frequency</entry><entry /><entry>frequency in unit of 100 KHz.</entry><entry /></row><row><entry>  }</entry><entry /><entry /><entry /></row><row><entry> }</entry><entry /><entry /><entry /></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0100In this case, in order to set a relay link, a new MS or an RS is prevented from entering a subordinate BS, and until setting of a relay link is complete, it is notified to the subordinate MS that a service is unavailable in order to set a relay link, and handover to the superordinate BS or another BS is performed to the subordinate MS, or after waiting until relay link establishment is complete, and a relay link is established and then after a BS service is started, communication may be resumed.

p-0101Relay establishment may be requested by a subordinate BS or by a superordinate BS. In this case, a situation in which a backhaul link is disconnected may be notified to a subordinate MS in which a service is already being performed, relay link establishment of a superordinate BS may be started, and when a plurality of frequencies exist, the subordinate MS may be started through a frequency in which a service is not performed.

p-0102Hereinafter, a case by a request of the subordinate BS at the step of starting relay link establishment (S<b>310</b>) will be described in detail.

p-0103When relay link establishment is started by the subordinate BS, a relay establishment request message that is shown in Table 1 includes an RS mode TTR or STR upon establishing a relay link and additional information (RS TTG, RS RTG for TTR, and frequency information for STR) necessary for operating a corresponding mode, and requests relay establishment from the superordinate BS.

p-0104In response thereto, the superordinate BS sends an acceptance, a rejection, or a re-request of a request through a relay establishment response message that is shown in Table 2. In this case, the superordinate BS may maintain relay link establishment by immediately accepting upon accepting or may stop relay link establishment by immediately rejecting. Further, upon accepting or rejecting, the superordinate BS may notify a relay link establishment start time point or a re-request together with an action time that is shown in Table 2.

p-0105The subordinate BS, having received a rejection including an immediate rejection or an action time, may re-request after an action time in order to resume a request for relay link establishment or may request relay link establishment to another adjacent BS when a relay link may be set with a corresponding BS.

p-0106According to another exemplary embodiment of the present invention, when establishment of a relay link of a subordinate BS is requested, if a multi-mode MS or an RS in which a relay link with a superordinate BS is set exists, by releasing a relay link of a corresponding RS or the multi-mode MS, interference of a relay link within a cell may be avoided. In this case, the superordinate BS transmits information of a subordinate MS in which a multi-mode MS or an RS to which a relay link is established services to a subordinate BS through a relay link in a process of establishing a relay link or after a relay link is established. For this purpose, the superordinate BS should store subordinate MS information of a multi-mode MS or a previous RS.

p-0107Hereinafter, a case by a request of a superordinate BS at the step of starting relay link establishment (S<b>310</b>) will be described in detail.

p-0108When the superordinate BS requests relay link establishment from the subordinate BS, as in a case where the subordinate BS recognizes a situation in which a backhaul link is disconnected through a backhaul network, the superordinate BS requests relay link establishment together with a relay mode TTR or STR to from subordinate BS, as shown in Table 1.

p-0109In this case, the subordinate BS includes information necessary for the requested relay mode in frequency information for an RS TTG and an RS RTG for TTR and STR, as shown in Table 2, and responds. In this case, a relay mode that is requested by the subordinate BS may refer to an applicable relay mode that shares BSs using a backhaul network before a backhaul link is disconnected.

p-0110The subordinate BS may accept or reject a relay link establishment start by a request of the superordinate BS the same as or similar to a relay link establishment started by a request of the subordinate BS, but when the superordinate BS requests, a response message that the subordinate BS transmits is generally regarded as acceptance. In this case, in order to establish a relay link, the superordinate BS may release a relay link of another RS or a multi-mode MS and start establishment or release while establishing, and requests a subordinate MS of a multi-mode MS or an RS in which a previous relay link is established to perform handover to a BS that newly establishes a relay link. In this case, in order to perform efficient handover, the superordinate BS transmits information of the subordinate MS to the subordinate MS through the relay link in a establishment process of a relay link or after establishing a relay link.

p-0111Hereinafter, a message form and a related parameter in IEEE 802.16e and IEEE 802.16j systems will be described in detail.

p-0112In the IEEE 802.16e and IEEE 802.16j systems, because various relay links can be established, corresponding information may be included. The corresponding information TLV for MMRS-REQ/RSP may include information that is shown in Table 3.

p-0113<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="77pt" align="center" /><colspec colname="2" colwidth="140pt" align="left" /><thead><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Parameter</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>1</entry><entry>RS operational mode</entry></row><row><entry>2</entry><entry>Response code</entry></row><row><entry>3</entry><entry>Station Information</entry></row><row><entry>4</entry><entry>RSRTG</entry></row><row><entry>5</entry><entry>RSTTG</entry></row><row><entry>6</entry><entry>Minimum RS forwarding delay in</entry></row><row><entry /><entry>direct relay zone</entry></row><row><entry>7</entry><entry>Minimum RS forwarding delay</entry></row><row><entry>8</entry><entry>Supported second RS carrier</entry></row><row><entry /><entry>configurations</entry></row><row><entry>9</entry><entry>Action Time</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0114An RS operational mode from Table 3 is shown in Table 4.

p-0115<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="21pt" align="center" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="119pt" align="left" /><colspec colname="4" colwidth="49pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 4</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>1</entry><entry>2</entry><entry>Bit 0: access zone preamble</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry>transmission support</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>Bit 1: MBS Data Synchronization with</entry><entry /></row><row><entry /><entry /><entry>pre-defined relative transmission</entry><entry /></row><row><entry /><entry /><entry>time (6.3.23.3)</entry><entry /></row><row><entry /><entry /><entry>Bit 2: MBS data synchronization</entry><entry /></row><row><entry /><entry /><entry>with target transmission time (6.3.23.3)</entry><entry /></row><row><entry /><entry /><entry>Bit 3: cooperative relay support</entry><entry /></row><row><entry /><entry /><entry>Bit 4: support of a second carrier</entry><entry /></row><row><entry /><entry /><entry>frequency at RS (see 8.4.4.7.2.2)</entry><entry /></row><row><entry /><entry /><entry>Bit 5: support STR RS operation (see</entry><entry /></row><row><entry /><entry /><entry>8.4.4.7.2.3)</entry><entry /></row><row><entry /><entry /><entry>Bits 6-9: Maximum number of HARQ</entry><entry /></row><row><entry /><entry /><entry>channels supported in UL_DCH</entry><entry /></row><row><entry /><entry /><entry>Bit 10: FDD support in access link</entry><entry /></row><row><entry /><entry /><entry>Bit 11: H-FDD support in access link</entry><entry /></row><row><entry /><entry /><entry>Bit 12: FDD support in relay link</entry><entry /></row><row><entry /><entry /><entry>Bit 13: H-FDD support in relay link</entry><entry /></row><row><entry /><entry /><entry>Bit 14-15: Reserved</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0116A response code is included in an MMRS-RSP message that is transmitted in response to an MMRS-REQ message, and may include information of Table 5 (response code).

p-0117<tables id="TABLE-US-00005" num="00005"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="112pt" align="left" /><colspec colname="4" colwidth="49pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 5</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>2</entry><entry>1</entry><entry>Bit 0: to accept the request</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>Bit 1: to allow retransmit after action</entry><entry /></row><row><entry /><entry /><entry>time expires</entry><entry /></row><row><entry /><entry /><entry>Bit 2: to reject the request</entry><entry /></row><row><entry /><entry /><entry>Bits 3-7: reserved</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0118When a message is scheduled by CID that is managed by an RS from an MS to a BS, station information may include information that is shown in Table 6 (station information).

p-0119<tables id="TABLE-US-00006" num="00006"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="112pt" align="left" /><colspec colname="4" colwidth="49pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 6</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>3</entry><entry>10</entry><entry>Bits 0-47: SS MAC address</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry>Bits 48-63: SS basic CID</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>Bits 64-79: SS primary management</entry><entry /></row><row><entry /><entry /><entry>CID</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0120Further, when a response code of Table 4 that is included in an MM-RS-RSP message is 0x00, a response code is included in the MM-RS-RSP message.

p-0121RSRTG/RSTTG is included, as shown in Table 7, upon requesting or upon approving (when a response code is 0x00) the request regardless of a relay operational mode.

p-0122<tables id="TABLE-US-00007" num="00007"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="14pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="56pt" align="center" /><colspec colname="4" colwidth="63pt" align="left" /><colspec colname="5" colwidth="63pt" align="left" /><thead><row><entry namest="1" nameend="5" rowsep="1">TABLE 7</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry /><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>4</entry><entry>10</entry><entry>RSRTG in μs</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry /><entry /><entry>MM-RS-RSP</entry></row><row><entry /><entry>5</entry><entry>10</entry><entry>RSTTG in μs</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry /><entry /><entry>MM-RS-RSP</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0123In minimum RS forwarding delay in a direct relay zone and a minimum RS forwarding delay scheduling centralizing mode, upon requesting or upon approving (when a response code is 0x00) the request, a response code may be included, as shown in Table 8 (minimum RS forwarding delay TLV).

p-0124<tables id="TABLE-US-00008" num="00008"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="21pt" align="center" /><colspec colname="2" colwidth="28pt" align="left" /><colspec colname="3" colwidth="119pt" align="left" /><colspec colname="4" colwidth="49pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 8</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>6</entry><entry>variable</entry><entry>The RS downlink process delay is a</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry>compound TLV value that encapsulates</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>TLVs that may be transmitted by</entry><entry /></row><row><entry /><entry /><entry>HR-MS to act as HR-RS. RS</entry><entry /></row><row><entry /><entry /><entry>forwarding delay in DL direct relay</entry><entry /></row><row><entry /><entry /><entry>zone (unit: OFDMA symbols) and/or</entry><entry /></row><row><entry /><entry /><entry>RS forwarding delay in UL</entry><entry /></row><row><entry /><entry /><entry>direct relay zone (unit: OFDMA</entry><entry /></row><row><entry /><entry /><entry>symbols) may be included</entry><entry /></row><row><entry /><entry /><entry>(see 11.8.19).</entry><entry /></row><row><entry>7</entry><entry>variable</entry><entry>The RS downlink process delay is a</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry>compound TLV value that encapsulates</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>TLVs that may be transmitted by</entry><entry /></row><row><entry /><entry /><entry>HR-MS to act as HR-RS. RS</entry><entry /></row><row><entry /><entry /><entry>forwarding delay in DL zone and/or</entry><entry /></row><row><entry /><entry /><entry>RS forwarding delay in UL zone</entry><entry /></row><row><entry /><entry /><entry>may be included (see 11.8.20).</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0125A supported second RS carrier configuration is information that is included in an STR relay operational mode and may be included, as shown in Table 9, upon requesting or upon approving (when a response code is 0x00) the request.

p-0126<tables id="TABLE-US-00009" num="00009"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="21pt" align="center" /><colspec colname="2" colwidth="28pt" align="left" /><colspec colname="3" colwidth="119pt" align="left" /><colspec colname="4" colwidth="49pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 9</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>8</entry><entry>variable</entry><entry>The supported second RS carrier</entry><entry>MM-RS-REQ,</entry></row><row><entry /><entry /><entry>configuration is a compound TLV</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>value that encapsulates TLVs that may</entry><entry /></row><row><entry /><entry /><entry>be transmitted by HR-MS to act</entry><entry /></row><row><entry /><entry /><entry>as HR-RS.</entry><entry /></row><row><entry /><entry /><entry>Predefined second carrier configurations</entry><entry /></row><row><entry /><entry /><entry>or undefined subbands to be</entry><entry /></row><row><entry /><entry /><entry>supported by the HR-RS</entry><entry /></row><row><entry /><entry /><entry>(See 11.8.3.5.24).</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0127An action time is a value that is included in an MMRS-RSP message, and when a response code is 0x01 in response to an MMRS-REQ message, the action time is included in an MMRS-RSP message, as shown in Table 10 (action time), and when a corresponding time has expired, the action time may be requested again.

p-0128<tables id="TABLE-US-00010" num="00010"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="112pt" align="left" /><colspec colname="4" colwidth="49pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 10</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Type</entry><entry>Length</entry><entry>Value</entry><entry>Scope</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>9</entry><entry>1</entry><entry>Bits 0-3: 4-bit LSBs of frame number</entry><entry>MM-RS-RSP</entry></row><row><entry /><entry /><entry>to allow the request after action</entry><entry /></row><row><entry /><entry /><entry>time expires.</entry><entry /></row><row><entry /><entry /><entry>Bits 4-7: reserved</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0129Hereinafter, the step of completing relay link establishment (S<b>320</b>) will be described in detail.

p-0130In order to set a relay link, upon establishing the relay link, the superordinate BS transmits a message including setting control information to a subordinate MS for establishing a relay link, as shown in Table 4, according to a relay mode TTR or STR.

p-0131In this case, the superordinate BS may generate a preamble through a preamble index and a frequency that are included in the message, and designate a frequency of an access zone to manage a subordinate MS after a relay link is established or designate a relay zone for communication with a superordinate BS.

p-0132The subordinate BS may use a preamble index in which the subordinate BS has been previously used before a relay link is established, i.e., before a backhaul link is disconnected. Further, the superordinate BS allocates STID and FID to the subordinate BS and thus determines whether STID and FID are data for the subordinate BS or data for a subordinate MS of the subordinate BS. Alternatively, data may be distinguished through a relay forwarding extended header, which is an extension header for relay to a MAC header.

p-0133A superframe number action that is included in a message when transmitting a establishment control message may be used for notifying a relay link start time point.

p-0134In order for the superordinate BS and the subordinate BS to set a relay zone for communication, the relay zone may be set by a procedure that is performed when the RS initially enters the BS.

p-0135A relay configuration control message is shown in Table 11.

p-0136<tables id="TABLE-US-00011" num="00011"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="154pt" align="left" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="161pt" align="left" /><colspec colname="4" colwidth="98pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 11</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Conditions</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="154pt" align="left" /><colspec colname="2" colwidth="28pt" align="char" char="." /><colspec colname="3" colwidth="161pt" align="left" /><colspec colname="4" colwidth="98pt" align="left" /><tbody valign="top"><row><entry>If (subordinate RS (including</entry><entry /><entry /><entry>// TTR mode</entry></row><row><entry>HR-MS acting as RS) is TTR</entry></row><row><entry>relay mode) {</entry></row><row><entry>AAI_Relay_zone_AMS_allocation_indicator</entry><entry>1</entry><entry>0b0: The ABS does not</entry><entry>Always present</entry></row><row><entry /><entry /><entry>allocate resources to the</entry></row><row><entry /><entry /><entry>AMS in the AAI DL Relay</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>0b1: The ABS may allocate</entry></row><row><entry /><entry /><entry>resources to the AMS in</entry></row><row><entry /><entry /><entry>the AAI DL Relay zone.</entry></row><row><entry>MIMO Midamble indication</entry><entry>1</entry><entry>0b0: MIMO midamble is</entry><entry>Always present</entry></row><row><entry>in</entry><entry /><entry>not transmitted in AAI DL</entry></row><row><entry>AAI DL Relay zone</entry><entry /><entry>Relay zone.</entry></row><row><entry /><entry /><entry>0b1: MIMO midamble is</entry></row><row><entry /><entry /><entry>transmitted in AAI DL</entry></row><row><entry /><entry /><entry>Relay zone.</entry></row><row><entry /><entry /><entry>If</entry></row><row><entry /><entry /><entry>AAI_Relay_zone_AMS_allocation_indicator ==</entry></row><row><entry /><entry /><entry>0b0,</entry></row><row><entry /><entry /><entry>this field is set to 0b1.</entry></row><row><entry>Superframe Number Action</entry><entry>4</entry><entry>LSBs of the superframe</entry><entry>Always present</entry></row><row><entry /><entry /><entry>number when ARS start</entry></row><row><entry /><entry /><entry>ARS operation and apply</entry></row><row><entry /><entry /><entry>the PHY operational</entry></row><row><entry /><entry /><entry>parameters.</entry></row><row><entry>R_IdleTime</entry><entry>11</entry><entry>Unit is 0.1 μs</entry><entry>Always present</entry></row><row><entry>If (ABS allocates resource</entry></row><row><entry>for periodic ranging in AAI</entry></row><row><entry>UL Relay zone) {</entry></row><row><entry>Allocation periodicity of the</entry><entry>2</entry><entry>Indicates the periodicity of</entry><entry>Present when ABS</entry></row><row><entry>S-RCH</entry><entry /><entry>the S-RCH allocation.</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>0b00: Every frame</entry><entry>periodic ranging in AAI UL</entry></row><row><entry /><entry /><entry>0b01: The second frame in</entry><entry>Relay zone.</entry></row><row><entry /><entry /><entry>every superframe</entry></row><row><entry /><entry /><entry>0b10: The second frame in</entry></row><row><entry /><entry /><entry>every 4^thsuperframe, i.e.,</entry></row><row><entry /><entry /><entry>mod(superframe number,</entry></row><row><entry /><entry /><entry>4) = 0</entry></row><row><entry /><entry /><entry>0b11: The second frame in</entry></row><row><entry /><entry /><entry>every 8^thsuperframe, i.e.,</entry></row><row><entry /><entry /><entry>mod(superframe number,</entry></row><row><entry /><entry /><entry>8) = 0</entry></row><row><entry>Subframe offset of the</entry><entry>2</entry><entry>Indicates the subframe</entry><entry>Present when ABS</entry></row><row><entry>S-RCH</entry><entry /><entry>offset (OSF) of the S-RCH</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>allocation. The range of</entry><entry>periodic ranging in AAI UL</entry></row><row><entry /><entry /><entry>values is 0 ≦· OSF ≦· 3.</entry><entry>Relay zone.</entry></row><row><entry /><entry /><entry>S-RCH is allocated in the</entry></row><row><entry /><entry /><entry>(OSF + UAZ) subframe.</entry></row><row><entry>Start RP code information of</entry><entry>4</entry><entry>Indicates the ks which is</entry><entry>Present when ABS</entry></row><row><entry>the S-RCH</entry><entry /><entry>the parameter controlling</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>the start root index of the</entry><entry>periodic ranging in AAI</entry></row><row><entry /><entry /><entry>RP codes rs0.</entry><entry>UL Relay zone.</entry></row><row><entry /><entry /><entry>r_s0= 6k_s+ 1</entry></row><row><entry /><entry /><entry>The range of values is</entry></row><row><entry /><entry /><entry>0 ≦ k_s≦ 15.</entry></row><row><entry>NPE</entry><entry>2</entry><entry>Indicates the number of</entry><entry>Present when ABS</entry></row><row><entry /><entry /><entry>periodic code (NPE)</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>according to Table 917.</entry><entry>periodic ranging in AAI</entry></row><row><entry /><entry /><entry /><entry>UL Relay zone.</entry></row><row><entry>}</entry></row><row><entry>If (ABS allocates resource</entry></row><row><entry>for BR channel in AAI UL</entry></row><row><entry>Relay zone) {</entry></row><row><entry>UL BW REQ channel</entry><entry>2</entry><entry>Indicates the number and</entry><entry>Present when ABS</entry></row><row><entry>information</entry><entry /><entry>the location of UL AAI</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>subframe where the UL</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>BW REQ channels are</entry><entry>zone.</entry></row><row><entry /><entry /><entry>allocated.</entry></row><row><entry /><entry /><entry>0b00: i-th UL AAI subframe</entry></row><row><entry /><entry /><entry>of UL relay zone in the first</entry></row><row><entry /><entry /><entry>frame in every superframe</entry></row><row><entry /><entry /><entry>0b01: i-th UL AAI subframe</entry></row><row><entry /><entry /><entry>of UL relay zone in the first</entry></row><row><entry /><entry /><entry>and second frame in every</entry></row><row><entry /><entry /><entry>superframe</entry></row><row><entry /><entry /><entry>0b10: i-th UL AAI subframe</entry></row><row><entry /><entry /><entry>of UL relay zone in every</entry></row><row><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry>0b11: i-th and i + 1-th UL</entry></row><row><entry /><entry /><entry>AAI subframes of UL relay</entry></row><row><entry /><entry /><entry>zone in every frame</entry></row><row><entry /><entry /><entry>Here, i-th is “first” if UL</entry></row><row><entry /><entry /><entry>R-RTI = 0 and i-th is</entry></row><row><entry /><entry /><entry>“second” if UL R-RTI = Ts.</entry></row><row><entry>UL BW REQ channel</entry><entry>4</entry><entry>The DRU index for UL BW</entry><entry>Present when ABS</entry></row><row><entry>allocation</entry><entry /><entry>REQ channel within FPi</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>defined by “Frequency</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>partition location for UL</entry><entry>zone.</entry></row><row><entry /><entry /><entry>control channels” in S-SFH</entry></row><row><entry /><entry /><entry>SP1.</entry></row><row><entry>Bandwidth request backoff</entry><entry>4</entry><entry>Initial backoff window size</entry><entry>Present when ABS</entry></row><row><entry>start</entry><entry /><entry>for contention BRs,</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>expressed as a power of 2.</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>Values of n range 0-15</entry><entry>zone.</entry></row><row><entry /><entry /><entry>(the highest</entry></row><row><entry /><entry /><entry>order bits shall be unused</entry></row><row><entry /><entry /><entry>and set to 0).</entry></row><row><entry>Bandwidth request backoff</entry><entry>4</entry><entry>Final backoff window size</entry><entry>Present when ABS</entry></row><row><entry>end</entry><entry /><entry>for contention BRs,</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>expressed as a power of 2.</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>Values of n range from</entry><entry>zone.</entry></row><row><entry /><entry /><entry>0-15.</entry></row><row><entry>}</entry></row><row><entry>If</entry></row><row><entry>(AAI_Relay_zone_AMS_allocation_indicator ==</entry></row><row><entry>0b0){</entry></row><row><entry>R_DCASSB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>subband-based CRUs in</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>FP0 for AAI DL Relay</entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.3.2</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_DCASMB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>miniband-based CRUs in</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>FP0 for AAI DL Relay</entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.3.2</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_DCASi</entry><entry>3/2/1</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>total allocated CRUs, in a</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>unit of a subband, for FPi (i ></entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>0) for AAI DL Relay zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.3.2</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 3 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 2 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 1 bit</entry></row><row><entry>R_UCASSB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>total allocated CRUs, in a</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>unit of a subband, for FPi (i ></entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>0) for AAI DL Relay zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.5.1</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_UCASMB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>miniband-based CRUs in</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>FP0 for AAI UL Relay</entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.5.1</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_UCASi</entry><entry>3/2/1</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>total allocated CRUs, in a</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>unit of a subband, for FPi (i ></entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>0) for AAI UL Relay zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.5.1</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 3 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 2 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 1 bit</entry></row><row><entry>}</entry></row><row><entry>}</entry><entry /><entry /><entry>// TTR mode only</entry></row><row><entry>If (subordinate HR-MS is</entry></row><row><entry>multimode MS acting as</entry></row><row><entry>HR-RS) {</entry></row><row><entry> SA-PREAMBLE index</entry><entry>10</entry><entry /><entry>Always present</entry></row><row><entry> MS    functionality</entry><entry>1</entry><entry>0b0: MS functionality is</entry><entry>Always present</entry></row><row><entry> maintenance indication</entry><entry /><entry>maintained after role</entry></row><row><entry /><entry /><entry>change.</entry></row><row><entry /><entry /><entry>0b1: MS functionality is not</entry></row><row><entry /><entry /><entry>maintained.</entry></row><row><entry> Cell bar information</entry><entry>1</entry><entry>If Cell bar bit == 0b1, this</entry><entry>Always present</entry></row><row><entry /><entry /><entry>cell shall not be allowed</entry></row><row><entry /><entry /><entry>network entry or reentry.</entry></row><row><entry> If (subordinate HR-MS</entry></row><row><entry> acting as STR relay mode)</entry></row><row><entry> {</entry></row><row><entry>  Frame configuration index</entry><entry>6</entry><entry>The mapping between</entry><entry>Always present</entry></row><row><entry /><entry /><entry>value of this index and</entry></row><row><entry /><entry /><entry>frame configuration is</entry></row><row><entry /><entry /><entry>listed in Table 806, Table</entry></row><row><entry /><entry /><entry>807, and Table 808.</entry></row><row><entry>  FFT size indication</entry><entry>2</entry><entry>0b00: 2048 FFT</entry><entry>Always present</entry></row><row><entry /><entry /><entry>0b01: 1024 FFT</entry></row><row><entry /><entry /><entry>0b10: 512 FFT</entry></row><row><entry /><entry /><entry>0b11: reserved</entry></row><row><entry>  DL carrier frequency for</entry><entry>10</entry><entry>Indicates the DL carrier</entry><entry>Present if needed</entry></row><row><entry>  BS and RS (F_BR_{<sub2>—</sub2>}_DL)</entry><entry /><entry>frequency in unit of 100 KHz</entry></row><row><entry /><entry /><entry>for MS acting as RS.</entry></row><row><entry /><entry /><entry>Used to receive from</entry></row><row><entry /><entry /><entry>HR-BS in the DL relay</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry>  UL carrier frequency for</entry><entry>10</entry><entry>Indicates the UL carrier</entry><entry>Present if needed</entry></row><row><entry>  BS and RS (F_BR_{<sub2>—</sub2>}_UL)</entry><entry /><entry>frequency in unit of 100 KHz</entry></row><row><entry /><entry /><entry>for MS acting as RS.</entry></row><row><entry /><entry /><entry>Used to transmit to HR-BS</entry></row><row><entry /><entry /><entry>in the UL relay zone.</entry></row><row><entry>  DL carrier frequency for</entry><entry>10</entry><entry>Indicates the DL carrier</entry><entry>Shall be present if F_RM_{<sub2>—</sub2>}_DLis</entry></row><row><entry>  RS and MS (F_RM_{<sub2>—</sub2>}_DL)</entry><entry /><entry>frequency in unit of 100 KHz</entry><entry>different from that of</entry></row><row><entry /><entry /><entry>for MS acting as RS in</entry><entry>HR-BS' DL access zone.</entry></row><row><entry /><entry /><entry>FDD. If the duplex mode</entry></row><row><entry /><entry /><entry>is TDD, this carrier is used</entry></row><row><entry /><entry /><entry>for DL/UL.</entry></row><row><entry /><entry /><entry>Used to transmit to</entry></row><row><entry /><entry /><entry>subordinate HR-MS in the</entry></row><row><entry /><entry /><entry>DL in FDD.</entry></row><row><entry /><entry /><entry>Used to transmit/receive</entry></row><row><entry /><entry /><entry>to/from subordinate</entry></row><row><entry /><entry /><entry>HR-MS in TDD.</entry></row><row><entry>  UL carrier frequency for</entry><entry>10</entry><entry>Indicates the UL carrier</entry><entry>Shall be present if F_RM_{<sub2>—</sub2>}_ULis</entry></row><row><entry>  RS and MS (F_RM_{<sub2>—</sub2>}_UL)</entry><entry /><entry>frequency in unit of 100 KHz</entry><entry>different from that of</entry></row><row><entry /><entry /><entry>for MS acting as RS in</entry><entry>HR-BS' UL access zone.</entry></row><row><entry /><entry /><entry>FDD.</entry></row><row><entry /><entry /><entry>Used to transmit to</entry></row><row><entry /><entry /><entry>subordinate HR-MS in the</entry></row><row><entry /><entry /><entry>UL in FDD.</entry></row><row><entry>  Superframe Number</entry><entry>4</entry><entry>LSBs of the superframe</entry><entry>Always present</entry></row><row><entry>  Action</entry><entry /><entry>number when HR-RS start</entry></row><row><entry /><entry /><entry>RS operation and apply the</entry></row><row><entry /><entry /><entry>PHY operational</entry></row><row><entry /><entry /><entry>parameters.</entry></row><row><entry> }</entry></row><row><entry>}</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0137In IEEE 802.16e and IEEE 802.16j systems, RCD/RS-Config-CMD that is defined in corresponding systems may be reused instead of Table 11. In this case, as described above, the superordinate BS may transmit a relay configuration control message to a subordinate MS and a subordinate BS to configure a relay link.

p-0138Hereinafter, the step of managing a relay link (S<b>330</b>) will be described in detail.

p-0139Relay link management, i.e., information update, may be performed in a handover process when updating through a configuration control message that is shown in Table 4 or when changing a relay link to another BS.

p-0140A process of updating relay link configuration information at the step of managing a relay link (S<b>330</b>) will be described in detail.

p-0141After a relay link is established, the subordinate BS or the superordinate BS notifies a configuration information change of the subordinate BS or a configuration information change of the superordinate BS to each other, thereby enabling to perform a continuous service. In this case, in order to prepare a configuration information change, before a configuration information change, the subordinate BS or the superordinate BS previously transmits configuration information change and notifies a time point at which a corresponding configuration information change is applied to a superframe or a frame number action that is included in Table 4. Alternatively, after configuration information is changed, the subordinate BS or the superordinate BS may notify the subordinate MS of a corresponding fact. In this case, the corresponding fact may be notified through a message (RCD, RS-Config-CMD in 802.16Rev3, Table 11) including system information, SFH, and a control channel.

p-0142Hereinafter, a relay link change at the step of managing a relay link (S<b>330</b>) will be described in detail.

p-0143For movement of a relay mode MS and mitigation of interference with an RS or an MS in which a relay link is formed at a periphery, a corresponding relay link may be moved to another BS. In this case, when changing a relay link frequency of the subordinate BS, or when changing a relay link, the relay link may be changed to a new superordinate BS. In this case, by transmitting information of a subordinate MS while servicing to a new superordinate BS, a continuous service can be performed and a relay link change may be notified to a subordinate MS, and handover to a subordinate MS may be guided or it may be notified to wait to a subordinate MS until a relay link change is complete.

p-0144Hereinafter, the step of releasing a relay link (S<b>340</b>) will be described in detail.

p-0145The relay link is released through a request of the superordinate BS or a request of the subordinate BS, or when it is necessary to change a superordinate BS of the relay link, the relay link may be released, and the relay link may be established again with a new BS. When the relay link is released, a resource or a connection of a subordinate MS that receives a service of the subordinate BS is deregistered or corresponding connection or resource allocation information is forwarded to an adjacent BS or an RS including a superordinate BS, thereby continuously performing a service.

p-0146First, a case of relay link release requested by a superordinate BS at the step of releasing a relay link (S<b>340</b>) will be described.

p-0147In order to release a relay link of a subordinate BS in which the relay link is established, the superordinate BS unsolicitely transmits a relay link release response message (Table 6). In response thereto, the subordinate BS to which a relay link is established transmits a relay link release request message (Table 5) and releases the relay link. In this case, when the superordinate BS requests, a relay link release time point together with an action time in Table 6 may be notified, and when a corresponding time has expired, a request message (Table 5) is transmitted as a response.

p-0148In this case, while releasing a relay link with a corresponding subordinate BS, by establishing the relay link with another RS or a multi-mode MS, subordinate MS information of the subordinate BS may be transmitted. Alternatively, when a disconnected backhaul link is available again, the subordinate BS may perform the above-described procedure through a backbone network.

p-0149Hereinafter, a case of releasing a subordinate BS request relay link at the step of releasing a relay link (S<b>340</b>) will be described.

p-0150When the subordinate BS needs to release a relay link like when a disconnected backhaul link is available again, the subordinate BS transmits a request message (Table 5). In response thereto, the superordinate BS responds regarding acceptance and an action time through a response message (Table 6). When the superordinate BS accepts, the superordinate BS may deregister by immediate acceptance or release after an action time in order to establish a relay link with another RS or an MS. Further, the superordinate BS may reject or allow a re-request including an action time. When the subordinate BS receives a rejection to a response message or receives a response including an action time, the subordinate BS may maintain a relay link, or when an action time has expired, the subordinate BS may re-request and release the relay link. Alternatively, when a disconnected backhaul link is available again, the subordinate BS may perform the above-described procedure through a backbone network.

p-0151Hereinafter, a case of releasing a relay link due to movement of an MS at the step of releasing a relay link (S<b>340</b>) will be described.

p-0152In the MS, mobility is generally considered. As a multi-mode MS to which a relay link is set moves, when interference with another RS or an MS to which a relay link is set occurs, the relay link should be released. Further, in order to continuously perform a service of a subordinate MS of a subordinate BS in which a relay link has been established, the superordinate BS requests relay link established to another RS or a multi-mode MS within the BS or a relay link may be established by the RS or the multi-mode MS instead of the subordinate BS.

p-0153In addition, when requesting relay link release, the following information is included and a reason of requesting release may be notified. First, corresponding information indicates when no subordinate MS exists, when a battery is approaching a predefined threshold level, when an interference level is overwhelming, and when normal power-off is initiated.

p-0154Table 12 illustrates a relay link release request message

p-0155(AAI-MMRL-REQ), and Table 13 illustrates a relay link release response message (AAI-MMRL-RSP).

p-0156<tables id="TABLE-US-00012" num="00012"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="77pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="84pt" align="left" /><colspec colname="4" colwidth="35pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 12</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Release_Request_Code</entry><entry>2</entry><entry>Used to indicate the</entry><entry>Always</entry></row><row><entry /><entry /><entry>purpose of this message.</entry><entry>present</entry></row><row><entry /><entry /><entry>0b00: multimode release</entry></row><row><entry /><entry /><entry>0b01: response for the</entry></row><row><entry /><entry /><entry>unsolicited AAI-MMRL-</entry></row><row><entry /><entry /><entry>RSP message by the</entry></row><row><entry /><entry /><entry>HR-BS</entry></row><row><entry /><entry /><entry>0b10: reject the unsolicited</entry></row><row><entry /><entry /><entry>AAI-MMRL-RSP message</entry></row><row><entry /><entry /><entry>by the HR-BS. This code is</entry></row><row><entry /><entry /><entry>applicable only when UL</entry></row><row><entry /><entry /><entry>data is pending</entry></row><row><entry /><entry /><entry>transmission.</entry></row><row><entry /><entry /><entry>0b11: reserved</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0157<tables id="TABLE-US-00013" num="00013"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="112pt" align="left" /><colspec colname="4" colwidth="35pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 13</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Action code</entry><entry>2</entry><entry>Used to indicate the purpose of this</entry><entry>Always</entry></row><row><entry /><entry /><entry>message.</entry><entry>present</entry></row><row><entry /><entry /><entry>0b00: HR-MS shall immediately</entry></row><row><entry /><entry /><entry>terminate multimode service and</entry></row><row><entry /><entry /><entry>return to its original HR-MS mode.</entry></row><row><entry /><entry /><entry>0b01: HR-MS shall terminate</entry></row><row><entry /><entry /><entry>multimode service and return</entry></row><row><entry /><entry /><entry>its original HR-MS mode when</entry></row><row><entry /><entry /><entry>the action time expires.</entry></row><row><entry /><entry /><entry>0b10: In response to an AAI-MMRL-</entry></row><row><entry /><entry /><entry>REQ message to allow HR-MS to</entry></row><row><entry /><entry /><entry>transmit MS-initiated request after</entry></row><row><entry /><entry /><entry>action time expires.</entry></row><row><entry /><entry /><entry>0b11: In response to an AAI-MMRL-</entry></row><row><entry /><entry /><entry>REQ message to reject the request</entry></row><row><entry /><entry /><entry>of HR-MS.</entry></row><row><entry>If  (action</entry></row><row><entry>code  ==</entry></row><row><entry>0b01  or</entry></row><row><entry>0b10) {</entry></row><row><entry> Action time</entry><entry>4</entry><entry>LSBs of the superframe number when</entry><entry>Always</entry></row><row><entry /><entry /><entry>HR-RS starts releasing the multimode</entry><entry>present</entry></row><row><entry /><entry /><entry>or transmit AAI-MMRL-REQ</entry></row><row><entry /><entry /><entry>message.</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0158According to the present exemplary embodiment, in a communication system, when a backhaul link of a BS is damaged, the BS establishes a relay link with an adjacent BS and performs a role of an RS, thereby performing a smooth communication operation.

p-0159Hereinafter, a method of relaying in an MS according to another exemplary embodiment of the present invention will be described.

p-0160<figref idrefs="DRAWINGS">FIG. 10</figref> is a flowchart illustrating a method of relaying in an MS according to an exemplary embodiment of the present invention.

p-0161Relay link management for performing a role of an RS of the MS includes a capability report of an MS (may include a start of relay link establishment), relay link establishment start (MS-initiated, BS/RS-initiated), relay link establishment completion, relay link management (may include information update of a set link and a relay link change), and relay link release.

p-0162First, the step of reporting a capability of an MS (S<b>410</b>) will be described in detail.

p-0163In the present exemplary embodiment, a subordinate MS of the BS is described, and an exemplary embodiment of the present invention can be applied to a subordinate MS of an RS instead of the BS.

p-0164In a multi-mode operation, in order to request relay link establishing to an MS having a capability of a multi-mode operation of a subordinate MS of the BS, the BS determines whether the MS performs a role of an RS and should manage a corresponding MS. For this purpose, in a process of performing initial access, the MS may transmit a capability report message, as shown in Table 1.

p-0165<tables id="TABLE-US-00014" num="00014"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="70pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 14</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Multimode</entry><entry>2</entry><entry>If bit 0 = 1, TTR mode</entry><entry>If the MS is capable of</entry></row><row><entry>capability</entry><entry /><entry>supports.</entry><entry>supporting relay mode.</entry></row><row><entry /><entry /><entry>If bit 1 = 1, STR mode</entry></row><row><entry /><entry /><entry>supports.</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0166Further, in a process in which the MS performs handover to a target BS, a process in which a serving BS notifies capability of a relay role of a target BS or a process in which a corresponding MS should report a capability to a target BS upon performing handover may be included within a handover action.

p-0167When notifying a relay role capability, if a relay role can be performed, a relay mode, for example, a time-division transmit and receive (TTR) mode or a simultaneous transmit and receive (STR) mode, is included and notified, or in a TTR mode, a transmit/receive transition gap (TTG), for example, a minimum receive-to-transmit turnaround gap and a receive/transmit transition gap (RTG), for example, a minimum transmit-to-receiver turnaround gap (RTG), are additionally included and transmitted, and after a relay link is set, corresponding information may be considered in setting a frame format. In an STR mode, a frequency for a relay link and a frequency for servicing a subordinate MS upon performing a relay role may be included and transmitted.

p-0168A capability report may be generally useful when the BS requests relay link establishment to the MS, and additional information TTG or RTG in a relay role performing capability may be included in a process in which the MS responds when the BS requests.

p-0169Hereinafter, the step of starting relay link establishment (S<b>420</b>) will be described.

p-0170The step of starting relay link establishment (S<b>420</b>) is requested by an MS or a BS, and in this case, a used relay establishment request message may be the same as that of Table 15, and a relay establishment response message may be the same as that of Table 16.

p-0171Hereinafter, a method of starting MS request relay link establishment at the step of starting relay link establishment (S<b>420</b>) will be described in detail.

p-0172When relay link establishment is started by the MS, an RS mode TTR or STR to be established and additional information necessary for operation of a corresponding mode, for example, frequency information for an RS TTG and RSs RTG and STR, is included in an AAI-MMRS-REQ, as shown in Table 1, and is requested from the BS.

p-0173In response thereto, the BS may respond as acceptance, rejection, or re-request of a request through an AAI-MMRS-RSP, as shown in Table 16. Upon accepting, by immediately accepting, relay link establishment is continuously performed, or by immediately rejecting, relay link establishment is stopped, or upon accepting or rejecting, a relay link establishment start time point or re-request including an action time that is shown in Table 16 may be notified.

p-0174When an MS, having received a rejection including an immediate rejection or an action time, can re-request after an action time in order to resume a request for relay link establishment or can perform handover to an adjacent BS, after handover to a corresponding BS is performed, the MS may request relay link establishment.

p-0175Further, when the MS requests, if a multi-mode MS or an RS in which a relay link with a BS has already been set exists, by deregistering a corresponding RS or a relay link of a multi-mode MS, interference of a relay link within a cell may be avoided. In this case, the BS may transmit information of an MS in which a multi-mode MS or an RS to which a relay link is set services to an MS to generate a relay link. For this purpose, the BS should store subordinate MS information of a multi-mode MS or a previous RS.

p-0176A method of starting BS request relay link establishment at the step of starting relay link establishment (S<b>420</b>) will be described in detail.

p-0177When requesting relay link establishment from the MS by the BS, the BS requests relay link establishment including a relay mode from the MS, as shown in Table 2.

p-0178<tables id="TABLE-US-00015" num="00015"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="105pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="112pt" align="left" /><colspec colname="4" colwidth="35pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 15</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="105pt" align="left" /><colspec colname="2" colwidth="21pt" align="char" char="." /><colspec colname="3" colwidth="112pt" align="left" /><colspec colname="4" colwidth="35pt" align="left" /><tbody valign="top"><row><entry>Request Relay mode</entry><entry>1</entry><entry>0b0: TTR relay mode</entry><entry>Always</entry></row><row><entry /><entry /><entry>0b1: STR relay mode</entry><entry>present</entry></row><row><entry>If (this request is subordinate</entry></row><row><entry>station initiated request) {</entry></row><row><entry> If (request relay mode ==</entry></row><row><entry> 0b0) {</entry></row><row><entry>  ARSTTG</entry><entry>6</entry><entry>ARSTTG value (μs). It shall be less</entry></row><row><entry /><entry /><entry>than 50 μs.</entry></row><row><entry>  ARSRTG</entry><entry>6</entry><entry>ARSRTG value (μs). It shall be less</entry></row><row><entry /><entry /><entry>than 50 μs.</entry></row><row><entry> } else if (request relay mode ==</entry></row><row><entry> 0b1) {</entry></row><row><entry>  Duplex mode support</entry><entry>2</entry><entry>If bit 0 = 1, FDD supports</entry></row><row><entry> indication</entry><entry /><entry>If bit 1 = 1, TDD supports</entry></row><row><entry>  for (i=1; i&lt;=N-frequency;</entry><entry /><entry>N-frequency is the number of</entry></row><row><entry> i++) {</entry><entry /><entry>available frequencies to communicate</entry></row><row><entry /><entry /><entry>[1 . . . 16].</entry></row><row><entry>   Carrier frequency</entry><entry>10</entry><entry>Indicates the carrier frequency in unit</entry></row><row><entry /><entry /><entry>of 100 KHz.</entry></row><row><entry>  }</entry></row><row><entry> }</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0179In this case, the MS includes information necessary for a requested relay mode in frequency information for an RS TTG and RSs RTG and STR, as shown in Table 16, and responds. Even in this case, the MS may accept or reject like an MS request relay link establishment start, but generally, when the BS requests, the MS regards a response message as acceptance.

p-0180<tables id="TABLE-US-00016" num="00016"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="91pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 16</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="28pt" align="char" char="." /><colspec colname="3" colwidth="91pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><tbody valign="top"><row><entry>If (the response is</entry><entry /><entry /><entry>Present when</entry></row><row><entry>transmitted  by</entry><entry /><entry /><entry>superordinate HR-BS</entry></row><row><entry>HR-BS) {</entry><entry /><entry /><entry>responds the</entry></row><row><entry /><entry /><entry /><entry>subordinate station</entry></row><row><entry /><entry /><entry /><entry>initiated request.</entry></row><row><entry> response code</entry><entry>2</entry><entry>0b00: in response to the</entry></row><row><entry /><entry /><entry>AAI-MMRS-REQ message</entry></row><row><entry /><entry /><entry>to accept the request</entry></row><row><entry /><entry /><entry>0b01: in response to the</entry></row><row><entry /><entry /><entry>AAI-MMRS-REQ message</entry></row><row><entry /><entry /><entry>to allow to transmit</entry></row><row><entry /><entry /><entry>subordinate station</entry></row><row><entry /><entry /><entry>initiated AAI-ARE-REQ</entry></row><row><entry /><entry /><entry>after action time expires</entry></row><row><entry /><entry /><entry>0b10: in response to the</entry></row><row><entry /><entry /><entry>AAI-MMRS-REQ message</entry></row><row><entry /><entry /><entry>to reject the request</entry></row><row><entry /><entry /><entry>0b11: reserved</entry></row><row><entry> If  (response</entry></row><row><entry>code == 0b01) {</entry></row><row><entry>  Action time</entry><entry>4</entry><entry>LSBs of the superframe</entry><entry>Always present</entry></row><row><entry /><entry /><entry>number when the</entry></row><row><entry /><entry /><entry>subordinate station</entry></row><row><entry /><entry /><entry>transmits AAI-MMRS-REQ</entry></row><row><entry /><entry /><entry>message.</entry></row><row><entry> }</entry></row><row><entry>} else {</entry><entry /><entry /><entry>Present when</entry></row><row><entry /><entry /><entry /><entry>subordinate station</entry></row><row><entry /><entry /><entry /><entry>responds to the</entry></row><row><entry /><entry /><entry /><entry>superordinate HR-BS</entry></row><row><entry /><entry /><entry /><entry>initiated request.</entry></row><row><entry> If  (received</entry><entry /><entry /><entry>// TTR mode</entry></row><row><entry> request  relay</entry></row><row><entry> mode == 0b0) {</entry></row><row><entry>  ARSTTG</entry><entry>6</entry><entry>ARSTTG value (μs). It</entry><entry>Shall be present if</entry></row><row><entry /><entry /><entry>shall be less than 50 μs.</entry><entry>action code == 0b0 in</entry></row><row><entry /><entry /><entry /><entry>AAI-MMRS-REQ.</entry></row><row><entry>  ARSRTG</entry><entry>6</entry><entry>ARSRTG value (μs). It</entry><entry>Shall be present if</entry></row><row><entry /><entry /><entry>shall be less than 50 μs.</entry><entry>action code == 0b0 in</entry></row><row><entry /><entry /><entry /><entry>AAI-MMRS-REQ.</entry></row><row><entry> }  else  if</entry><entry /><entry /><entry>// STR mode</entry></row><row><entry> (received</entry></row><row><entry> request  relay</entry></row><row><entry> mode == 0b1) {</entry></row><row><entry>  Duplex mode</entry><entry>2</entry><entry>If bit 0 = 1, FDD supports</entry><entry>Always present</entry></row><row><entry> support</entry><entry /><entry>If bit 1 = 1, TDD supports</entry></row><row><entry> indication</entry></row><row><entry>  for    (i=1;</entry><entry /><entry>N-frequency is the number</entry></row><row><entry> i&lt;=N-frequency;</entry><entry /><entry>of available frequencies to</entry></row><row><entry> i++) {</entry><entry /><entry>communicate [1 . . . 16].</entry></row><row><entry>   Carrier</entry><entry>10</entry><entry>Indicates the carrier</entry></row><row><entry>  frequency</entry><entry /><entry>frequency in unit of 100 KHz.</entry></row><row><entry>  }</entry></row><row><entry>  }</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0181In this case, in order to set a relay link, a BS may deregister a relay link of another RS or a multi-mode MS and start establishment or release of a relay link while establishing, and may request a subordinate MS of a multi-mode MS or an RS in which a previous relay link is set to perform handover from an MS that newly establishes a relay link. In this case, in order to perform efficient handover, information of a subordinate MS may be transmitted to an MS that newly establishes a relay link through a relay link in a process of configuration a relay link or after a relay link is established.

p-0182Hereinafter, the step of completing relay link configuration (S<b>430</b>) will be described.

p-0183In order to configure a relay link, upon establishing a relay link, the BS transmits a message including configuration control information for configuration a relay link to the MS, as shown in Table 17, according to a relay mode TTR or STR.

p-0184<tables id="TABLE-US-00017" num="00017"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="154pt" align="left" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="161pt" align="left" /><colspec colname="4" colwidth="98pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 17</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Conditions</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="154pt" align="left" /><colspec colname="2" colwidth="28pt" align="char" char="." /><colspec colname="3" colwidth="161pt" align="left" /><colspec colname="4" colwidth="98pt" align="left" /><tbody valign="top"><row><entry>If (subordinate RS (including</entry><entry /><entry /><entry>// TTR mode</entry></row><row><entry>HR-MS acting as RS) is TTR</entry></row><row><entry>relay mode) {</entry></row><row><entry>AAI_Relay_zone_AMS_allocation_indicator</entry><entry>1</entry><entry>0b0: The ABS does not</entry><entry>Always present</entry></row><row><entry /><entry /><entry>allocate resources to the</entry></row><row><entry /><entry /><entry>AMS in the AAI DL Relay</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>0b1: The ABS may allocate</entry></row><row><entry /><entry /><entry>resources to the AMS in</entry></row><row><entry /><entry /><entry>the AAI DL Relay zone.</entry></row><row><entry>MIMO midamble indication</entry><entry>1</entry><entry>0b0: MIMO midamble is</entry><entry>Always present</entry></row><row><entry>in</entry><entry /><entry>not transmitted in AAI DL</entry></row><row><entry>AAI DL Relay zone</entry><entry /><entry>Relay zone.</entry></row><row><entry /><entry /><entry>0b1: MIMO midamble is</entry></row><row><entry /><entry /><entry>transmitted in AAI DL</entry></row><row><entry /><entry /><entry>Relay zone.</entry></row><row><entry /><entry /><entry>If</entry></row><row><entry /><entry /><entry>AAI_Relay_zone_AMS_allocation_indicator ==</entry></row><row><entry /><entry /><entry>0b0,</entry></row><row><entry /><entry /><entry>this field is set to 0b1.</entry></row><row><entry>Superframe Number Action</entry><entry>4</entry><entry>LSBs of the superframe</entry><entry>Always present</entry></row><row><entry /><entry /><entry>number when ARS start</entry></row><row><entry /><entry /><entry>ARS operation and apply</entry></row><row><entry /><entry /><entry>the PHY operational</entry></row><row><entry /><entry /><entry>parameters.</entry></row><row><entry>R_IdleTime</entry><entry>11</entry><entry>Unit is 0.1 μs</entry><entry>Always present</entry></row><row><entry>If (ABS allocates resource</entry></row><row><entry>for periodic ranging in AAI</entry></row><row><entry>UL Relay zone) {</entry></row><row><entry>Allocation periodicity of the</entry><entry>2</entry><entry>Indicates the periodicity of</entry><entry>Present when ABS</entry></row><row><entry>S-RCH</entry><entry /><entry>the S-RCH allocation.</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>0b00: Every frame</entry><entry>periodic ranging in AAI UL</entry></row><row><entry /><entry /><entry>0b01: The second frame in</entry><entry>Relay zone</entry></row><row><entry /><entry /><entry>every superframe</entry></row><row><entry /><entry /><entry>0b10: The second frame in</entry></row><row><entry /><entry /><entry>every 4^thsuperframe, i.e.,</entry></row><row><entry /><entry /><entry>mod(superframe number,</entry></row><row><entry /><entry /><entry>4) = 0</entry></row><row><entry /><entry /><entry>0b11: The second frame in</entry></row><row><entry /><entry /><entry>every 8^thsuperframe, i.e.,</entry></row><row><entry /><entry /><entry>mod(superframe number,</entry></row><row><entry /><entry /><entry>8) = 0</entry></row><row><entry>Subframe offset of the</entry><entry>2</entry><entry>Indicates the subframe</entry><entry>Present when ABS</entry></row><row><entry>S-RCH</entry><entry /><entry>offset (OSF) of the S-RCH</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>allocation. The range of</entry><entry>periodic ranging in AAI UL</entry></row><row><entry /><entry /><entry>values is 0 ≦· OSF ≦· 3.</entry><entry>Relay zone.</entry></row><row><entry /><entry /><entry>S-RCH is allocated in the</entry></row><row><entry /><entry /><entry>(OSF + UAZ) subframe.</entry></row><row><entry>Start RP code information of</entry><entry>4</entry><entry>Indicates the ks which is</entry><entry>Present when ABS</entry></row><row><entry>the S-RCH</entry><entry /><entry>the parameter controlling</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>the start root index of the</entry><entry>periodic ranging in AAI</entry></row><row><entry /><entry /><entry>RP codes rs0.</entry><entry>UL Relay zone</entry></row><row><entry /><entry /><entry>r_s0= 6k_s+ 1</entry></row><row><entry /><entry /><entry>The range of values is</entry></row><row><entry /><entry /><entry>0 ≦ k_s≦ 15.</entry></row><row><entry>NPE</entry><entry>2</entry><entry>Indicates the number of</entry><entry>Present when ABS</entry></row><row><entry /><entry /><entry>periodic codes (NPE)</entry><entry>allocates resource for</entry></row><row><entry /><entry /><entry>according to the Table 917.</entry><entry>periodic ranging in AAI</entry></row><row><entry /><entry /><entry /><entry>UL Relay zone</entry></row><row><entry>}</entry></row><row><entry>If (ABS allocates resource</entry></row><row><entry>for BR channel in AAI UL</entry></row><row><entry>Relay zone) {</entry></row><row><entry>UL BW REQ channel</entry><entry>2</entry><entry>Indicates the number and</entry><entry>Present when ABS</entry></row><row><entry>information</entry><entry /><entry>the location of UL AAI</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>subframes where the UL</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>BW REQ channels are</entry><entry>zone.</entry></row><row><entry /><entry /><entry>allocated.</entry></row><row><entry /><entry /><entry>0b00: i-th UL AAI subframe</entry></row><row><entry /><entry /><entry>of UL relay zone in the first</entry></row><row><entry /><entry /><entry>frame in every superframe</entry></row><row><entry /><entry /><entry>0b01: i-th UL AAI subframe</entry></row><row><entry /><entry /><entry>of UL relay zone in the first</entry></row><row><entry /><entry /><entry>and second frame in every</entry></row><row><entry /><entry /><entry>superframe</entry></row><row><entry /><entry /><entry>0b10: i-th UL AAI subframe</entry></row><row><entry /><entry /><entry>of UL relay zone in every</entry></row><row><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry>0b11: i-th and i + 1-th UL</entry></row><row><entry /><entry /><entry>AAI subframes of UL relay</entry></row><row><entry /><entry /><entry>zone in every frame</entry></row><row><entry /><entry /><entry>Where i-th is “first” if UL</entry></row><row><entry /><entry /><entry>R-RTI = 0 and i-th is</entry></row><row><entry /><entry /><entry>“second” if UL R-RTI = Ts.</entry></row><row><entry>UL BW REQ channel</entry><entry>4</entry><entry>The DRU index for UL BW</entry><entry>Present when ABS</entry></row><row><entry>allocation</entry><entry /><entry>REQ channel within FPi</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>defined by “Frequency</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>partition location for UL</entry><entry>zone</entry></row><row><entry /><entry /><entry>control channels” in S-SFH</entry></row><row><entry /><entry /><entry>SP1.</entry></row><row><entry>Bandwidth request backoff</entry><entry>4</entry><entry>Initial backoff window size</entry><entry>Present when ABS</entry></row><row><entry>start</entry><entry /><entry>for contention BRs,</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>expressed as a power of 2.</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>Values of n range 0-15</entry><entry>zone.</entry></row><row><entry /><entry /><entry>(the highest</entry></row><row><entry /><entry /><entry>order bits shall be unused</entry></row><row><entry /><entry /><entry>and set to 0).</entry></row><row><entry>Bandwidth request backoff</entry><entry>4</entry><entry>Final backoff window size</entry><entry>Present when ABS</entry></row><row><entry>end</entry><entry /><entry>for contention BRs,</entry><entry>allocates resource for BR</entry></row><row><entry /><entry /><entry>expressed as a power of 2.</entry><entry>channel in AAI UL Relay</entry></row><row><entry /><entry /><entry>Values of n range from</entry><entry>zone.</entry></row><row><entry /><entry /><entry>0-15.</entry></row><row><entry>}</entry></row><row><entry>If</entry></row><row><entry>(AAI_Relay_zone_AMS_allocation_indicator ==</entry></row><row><entry>0b0){</entry></row><row><entry>R_DCASSB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>subband-based CRUs in</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>FP0 for AAI DL Relay</entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.3.2</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_DCASMB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>miniband-based CRUs in</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>FP0 for AAI DL Relay</entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.3.2</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_DCASi</entry><entry>3/2/1</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>total allocated CRUs, in a</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>unit of a subband, for FPi (i ></entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>0) for AAI DL Relay zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.3.2</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 3 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 2 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 1 bit</entry></row><row><entry>R_UCASSB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>total allocated CRUs, in a</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>unit of a subband, for FPi (i ></entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>0) for AAI DL Relay zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.5.1</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_UCASMB0</entry><entry>5/4/3</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>miniband-based CRUs in</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>FP0 for AAI UL Relay</entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.5.1</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 5 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 4 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 3 bits</entry></row><row><entry>R_UCASi</entry><entry>3/2/1</entry><entry>Indicates the number of</entry><entry>Present when</entry></row><row><entry /><entry /><entry>total allocated CRUs, in a</entry><entry>AAI_Relay_zone_AMS_—</entry></row><row><entry /><entry /><entry>unit of a subband, for FPi (i ></entry><entry>allocation_indicator == 0b0.</entry></row><row><entry /><entry /><entry>0) for AAI UL Relay zone.</entry></row><row><entry /><entry /><entry>See 16.6.3.5.1</entry></row><row><entry /><entry /><entry>Cell-specific resource</entry></row><row><entry /><entry /><entry>mapping.</entry></row><row><entry /><entry /><entry>For 2048 FFT size, 3 bits</entry></row><row><entry /><entry /><entry>For 1024 FFT size, 2 bits</entry></row><row><entry /><entry /><entry>For 512 FFT size, 1 bit</entry></row><row><entry>}</entry></row><row><entry>}</entry><entry /><entry /><entry>// TTR mode only</entry></row><row><entry>If (subordinate HR-MS is</entry></row><row><entry>multimode MS acting as</entry></row><row><entry>HR-RS) {</entry></row><row><entry> SA-PREAMBLE index</entry><entry>10</entry><entry /><entry>Always present</entry></row><row><entry> MS    functionality</entry><entry>1</entry><entry>0b0: MS functionality is</entry><entry>Always present</entry></row><row><entry> maintenance indication</entry><entry /><entry>maintained after role</entry></row><row><entry /><entry /><entry>change</entry></row><row><entry /><entry /><entry>0b1: MS functionality is not</entry></row><row><entry /><entry /><entry>maintained</entry></row><row><entry> Cell bar information</entry><entry>1</entry><entry>If Cell bar bit == 0b1, this</entry><entry>Always present</entry></row><row><entry /><entry /><entry>cell shall not be allowed</entry></row><row><entry /><entry /><entry>network entry or reentry</entry></row><row><entry> If  (subordinate  HR-MS</entry></row><row><entry> acting as STR relay mode)</entry></row><row><entry> {</entry></row><row><entry>  Frame configuration index</entry><entry>6</entry><entry>The mapping between</entry><entry>Always present</entry></row><row><entry /><entry /><entry>value of this index and</entry></row><row><entry /><entry /><entry>frame configuration is</entry></row><row><entry /><entry /><entry>listed in Table 806, Table</entry></row><row><entry /><entry /><entry>807, and Table 808.</entry></row><row><entry>  FFT size indication</entry><entry>2</entry><entry>0b00: 2048 FFT</entry><entry>Always present</entry></row><row><entry /><entry /><entry>0b01: 1024 FFT</entry></row><row><entry /><entry /><entry>0b10: 512 FFT</entry></row><row><entry /><entry /><entry>0b11: reserved</entry></row><row><entry>  DL carrier frequency for</entry><entry>10</entry><entry>Indicates the DL carrier</entry><entry>Present if needed</entry></row><row><entry>  BS and RS (F_BR_{<sub2>—</sub2>}_DL)</entry><entry /><entry>frequency in unit of 100 KHz</entry></row><row><entry /><entry /><entry>for MS acting as RS.</entry></row><row><entry /><entry /><entry>Used to receive from</entry></row><row><entry /><entry /><entry>HR-BS in the DL relay</entry></row><row><entry /><entry /><entry>zone.</entry></row><row><entry>  UL carrier frequency for</entry><entry>10</entry><entry>Indicates the UL carrier</entry><entry>Present if needed</entry></row><row><entry>  BS and RS (F_BR_{<sub2>—</sub2>}_UL)</entry><entry /><entry>frequency in unit of 100 KHz</entry></row><row><entry /><entry /><entry>for MS acting as RS.</entry></row><row><entry /><entry /><entry>Used to transmit to HR-BS</entry></row><row><entry /><entry /><entry>in the UL relay zone.</entry></row><row><entry>  DL carrier frequency for</entry><entry>10</entry><entry>Indicates the DL carrier</entry><entry>Shall be present if F_RM_{<sub2>—</sub2>}_DLis</entry></row><row><entry>  RS and MS (F_RM_{<sub2>—</sub2>}_DL)</entry><entry /><entry>frequency in unit of 100 KHz</entry><entry>different from that of</entry></row><row><entry /><entry /><entry>for MS acting as RS in</entry><entry>HR-BS' DL access zone.</entry></row><row><entry /><entry /><entry>FDD. If the duplex mode</entry></row><row><entry /><entry /><entry>is TDD, this carrier is used</entry></row><row><entry /><entry /><entry>for DL/UL.</entry></row><row><entry /><entry /><entry>Used to transmit to</entry></row><row><entry /><entry /><entry>subordinate HR-MS in the</entry></row><row><entry /><entry /><entry>DL in FDD.</entry></row><row><entry /><entry /><entry>Used to transmit/receive</entry></row><row><entry /><entry /><entry>to/from subordinate</entry></row><row><entry /><entry /><entry>HR-MS in TDD.</entry></row><row><entry>  UL carrier frequency for</entry><entry>10</entry><entry>Indicates the UL carrier</entry><entry>Shall be present if F_RM_{<sub2>—</sub2>}_ULis</entry></row><row><entry>  RS and MS (F_RM_{<sub2>—</sub2>}_UL)</entry><entry /><entry>frequency in unit of 100 KHz</entry><entry>different from that of</entry></row><row><entry /><entry /><entry>for MS acting as RS in</entry><entry>HR-BS' UL access zone.</entry></row><row><entry /><entry /><entry>FDD.</entry></row><row><entry /><entry /><entry>Used to transmit to</entry></row><row><entry /><entry /><entry>subordinate HR-MS in the</entry></row><row><entry /><entry /><entry>UL in FDD.</entry></row><row><entry>  Superframe   Number</entry><entry>4</entry><entry>LSBs of the superframe</entry><entry>Always present</entry></row><row><entry>  Action</entry><entry /><entry>number when HR-RS start</entry></row><row><entry /><entry /><entry>RS operation and apply the</entry></row><row><entry /><entry /><entry>PHY operational</entry></row><row><entry /><entry /><entry>parameters.</entry></row><row><entry> }</entry></row><row><entry>}</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0185In this case, a preamble is generated through a preamble index and a frequency that are included in a message, and after a relay link is set, a frequency of an access zone to manage a subordinate MS may be designated or a relay zone for communication with a BS may be designated.

p-0186Further, the message includes information about whether a multi-mode MS operates an RS mode through a relay link while maintaining a function of the MS after a relay link is set. When an MS function should be maintained, the BS performs a service for maintaining an MS function through a relay zone with a corresponding relay mode MS.

p-0187Because a relay mode MS that performs an MS function performs a service with a BS through a relay zone, it is necessary to determine whether data are for relay or for a relay mode MS.

p-0188In this case, by newly allocating FID for relaying or by additionally allocating STID and FID for new relay while maintaining STID and FID that are allocated to the MS, data may be distinguished. Alternatively, data may be distinguished through a relay forwarding extended header, which is an extension header for relay to a MAC header.

p-0189A superframe number action that is included in a message when transmitting a configuration control message may be used for notifying a relay link start time point. In this case, because a control message that is transmitted before start of a relay link is transmitted before a relay zone is generated, the control message is transmitted from a BS to a downlink frame zone, and after a relay link is set, when transmission of a control message is necessary, the control message is transmitted through a relay zone.

p-0190Hereinafter, the step of managing a relay link (S<b>440</b>) will be described.

p-0191Relay link management is the step of updating information and may be updated through a configuration control message or may be performed in a handover process when changing a relay link to another BS, as shown in Table 17.

p-0192A process of updating relay link configuration information at the step of managing a relay link (S<b>440</b>) will be described.

p-0193After a relay link is set, a change of configuration information of a relay mode MS or a configuration information change of a BS is notified and thus configuration information change contents for servicing a relay link and a subordinate MS are notified and a continuous service can be thus performed. In this case, in order to prepare a configuration information change, the configuration information change may be previously transmitted before a configuration information change, and a time point at which a corresponding configuration information change is applied to a superframe number action that is included in Table 17 may be notified. Alternatively, after configuration information is changed, a corresponding fact may be notified to a subordinate MS. In this case, a corresponding fact may be notified through a message including system information, SFH, or a control channel.

p-0194A process of changing a relay link at the step of managing a relay link (S<b>440</b>) will be described.

p-0195For movement of a relay mode MS or for mitigation of interference with an MS or an RS in which a relay link is formed at a periphery, movement of a corresponding relay link to another BS, i.e., handover of a relay mode MS may be performed.

p-0196In this case, a frequency of a relay link of an MS is changed, or upon performing handover, a relay link may be changed to a target BS. In this case, by transmitting information of a subordinate MS while performing a service to a target BS, a continuous service may be performed, a relay link change may be notified to a subordinate MS, and handover may be guided to a subordinate MS, or it may be notified to await to a subordinate MS until a relay link change is complete.

p-0197Hereinafter, the step of releasing a relay link (S<b>450</b>) will be described in detail.

p-0198The relay link may be released through a request of a BS or through a request of an MS. Further, when a relay link with a BS cannot be continuously maintained due to movement, i.e., handover of an MS, the relay link is deregistered, and a relay link with a new BS may be set again. In this case, the relay link may be changed to a target BS. When the relay link is released, a connection or a resource of a subordinate MS that receives a service of a relay mode MS is deregistered or corresponding connection or resource allocation information is forwarded to an adjacent BS or an RS, and thus a service can be continuously performed.

p-0199Hereinafter, relay link release by a request of a BS at the step of releasing a relay link (S<b>450</b>) will be described.

p-0200In order to release a relay link of a multi-mode MS to which a relay link is established, the BS unsolicitely transmits an AAI-MMRL-REQ, as shown in Table 18.

p-0201<tables id="TABLE-US-00018" num="00018"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="77pt" align="left" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="77pt" align="left" /><colspec colname="4" colwidth="35pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 18</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Release_Request_Code</entry><entry>2</entry><entry>Used to indicate the</entry><entry>Always</entry></row><row><entry /><entry /><entry>purpose of this message.</entry><entry>present</entry></row><row><entry /><entry /><entry>0b00: multimode release</entry></row><row><entry /><entry /><entry>0b01: response for</entry></row><row><entry /><entry /><entry>the unsolicited</entry></row><row><entry /><entry /><entry>AAI-MMRL-RSP</entry></row><row><entry /><entry /><entry>message by the HR-BS</entry></row><row><entry /><entry /><entry>0b10: reject for</entry></row><row><entry /><entry /><entry>the unsolicited</entry></row><row><entry /><entry /><entry>AAI-MMRL-RSP</entry></row><row><entry /><entry /><entry>message by the</entry></row><row><entry /><entry /><entry>HR-BS. This code is</entry></row><row><entry /><entry /><entry>applicable only when</entry></row><row><entry /><entry /><entry>UL data is pending</entry></row><row><entry /><entry /><entry>transmission.</entry></row><row><entry /><entry /><entry>0b11: reserved</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0202In response thereto, an MS to which a relay link is set transmits an AAI-MMRL-RSP and releases the relay link, as shown in Table 19. In this case, when the BS requests, the MS may notify the BS of a relay link release time point together with an action time that is included in Table 6, and when a corresponding time has expired, the MS transmits a request message (Table 18) as a response. In this case, while a relay link with a corresponding MS is released, the BS establishes a relay link with another RS or a multi-mode MS, and may transmit subordinate MS information of an MS that releases a relay link to a corresponding RS or the multi-mode MS.

p-0203<tables id="TABLE-US-00019" num="00019"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="126pt" align="left" /><colspec colname="4" colwidth="35pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 19</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Action</entry><entry>2</entry><entry>Used to indicate the purpose of this</entry><entry>Always</entry></row><row><entry>code</entry><entry /><entry>message.</entry><entry>present</entry></row><row><entry /><entry /><entry>0b00: HR-MS shall immediately terminate</entry></row><row><entry /><entry /><entry>multimode service and return to its</entry></row><row><entry /><entry /><entry>original HR-MS mode.</entry></row><row><entry /><entry /><entry>0b01: HR-MS shall terminate multimode</entry></row><row><entry /><entry /><entry>service and return to its original HR-MS</entry></row><row><entry /><entry /><entry>mode when the action time expires.</entry></row><row><entry /><entry /><entry>0b10: In response to an AAI-MMRL-REQ</entry></row><row><entry /><entry /><entry>message to allow HR-MS to transmit</entry></row><row><entry /><entry /><entry>MS-initiated request after the action time</entry></row><row><entry /><entry /><entry>expires.</entry></row><row><entry /><entry /><entry>0b11: In response to an AAI-MMRL-REQ</entry></row><row><entry /><entry /><entry>message to reject the request of HR-MS.</entry></row><row><entry>If (action</entry></row><row><entry>code ==</entry></row><row><entry>0b01 or</entry></row><row><entry>0b10) {</entry></row><row><entry> Action</entry><entry>4</entry><entry>LSBs of the superframe number when</entry><entry>Always</entry></row><row><entry> time</entry><entry /><entry>HR-RS starts releasing the multimode or</entry><entry>present</entry></row><row><entry /><entry /><entry>transmit AAI-MMRL-REQ message.</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0204Release of an MS request relay link at the step of releasing a relay link (S<b>450</b>) will be described.

p-0205When releasing a relay link due to a power problem or movement of an MS, the MS transmits an AAI-MMRL-REQ to a BS, as shown in Table 5. In response thereto, the BS responds with the AAI-MMRL-REQ including acceptance or not and an action time, as shown in Table 19.

p-0206When the BS accepts upon responding, the BS may deregister by immediately accepting, deregister after an action time in order to set a relay link with another RS or MS, reject, or allow a re-request including an action time. When the MS receives a rejection in a response message or receives a response including an action time, the MS may maintain a relay link or release a relay link by a re-request when an action time has expired.

p-0207Release of a relay link due to movement of an MS at the step of releasing a relay link (S<b>450</b>) will be described.

p-0208In the MS, mobility is generally considered. When a multi-mode MS to which a relay link is set experiences interference with an MS or another RS to which a relay link is set by movement or moves to an adjacent cell, the multi-mode MS should release the relay link. Alternatively, when a multi-mode MS moves to an adjacent cell, the multi-mode MS may maintain a relay link with a corresponding BS. When the multi-mode MS moves to an adjacent cell, the multi-mode MS generally performs handover. Therefore, the multi-mode MS may perform a process of releasing a relay link while performing handover or include relay link release related information in a handover message.

p-0209Further, in order to continuously perform a service of a subordinate MS of an MS to which a relay link is set, the BS may request setting of a relay link to a multi-mode MS within the BS or a relay link may be set by a multi-mode MS. When it is more useful to set a relay link with an adjacent BS than a relay link that is set with a present BS, an MS in which handover is performed or in which a moving relay link is set may continuously maintain a relay link with the adjacent BS and convert a BS to which a relay link is set. In this case, as a serving BS transmits relay link related information to an adjacent BS, a relay link that is set with the adjacent BS may be maintained or the adjacent BS may transmit relay link configuration information.

p-0210According to the present exemplary embodiment, in a communication system, an MS performs a role of a BS or an RS, thereby smoothly performing a multi-operational mode.

p-0211When a backhaul link is damaged, the MS may operate as a BS or an RS, and such an MS is referred to as a multi-mode MS. Hereinafter, a method of transmitting in an MS will be described in detail with reference to <figref idrefs="DRAWINGS">FIG. 11</figref>.

p-0212<figref idrefs="DRAWINGS">FIG. 11</figref> is a flowchart illustrating a method of transmitting in an MS according to an exemplary embodiment of the present invention.

p-0213A change event occurs in the MS <b>200</b> (S<b>510</b>). Here, the change event indicates when a backhaul link is in an unavailable (disconnection, collapse) state or when a backhaul link is recovered, when resetting a backhaul link due to periodic transmission or change of configuration information of a physical layer PHY or a MAC layer in a multi-mode operation state, when converting to a multi-mode or when converting from a multi-mode to an original mode, when it is necessary to notify power down or reduction or power on or increasing, and when frequency allocation (FA) is changed.

p-0214In such a case, the MS <b>200</b> transmits a control message to a subordinate apparatus, for example, another MS, a BS, or an RS (S<b>520</b>). In this case, the control message is transmitted through a downward control channel or with another previously defined method such as broadcast, multicast, or unicast.

p-0215In the present exemplary embodiment, it is described that an MS transmits a control message, but when a necessary event occurs, an infrastructure station other than an MS may transmit a control message to a subordinate apparatus.

p-0216Such a control message (MM-ADV) may be transmitted in a form including information that is illustrated in Table 20 or 21. Table 20 is formed based on an IEEE 802.16.1 system, and Table 21 is formed based on an IEEE 802.16Rev3 system.

p-0217<tables id="TABLE-US-00020" num="00020"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="98pt" align="left" /><colspec colname="4" colwidth="42pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 20</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /><entry /></row><row><entry>Field</entry><entry>(bits)</entry><entry>Value/Description</entry><entry>Condition</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="21pt" align="char" char="." /><colspec colname="3" colwidth="98pt" align="left" /><colspec colname="4" colwidth="42pt" align="left" /><tbody valign="top"><row><entry>Action Type</entry><entry>3</entry><entry>Used to indicate the purpose of</entry><entry>Mandatory</entry></row><row><entry /><entry /><entry>this message.</entry></row><row><entry /><entry /><entry>0b000: Reconfiguration of</entry></row><row><entry /><entry /><entry>HR-BS/RS including multimode</entry></row><row><entry /><entry /><entry>BS/RS</entry></row><row><entry /><entry /><entry>0b001: Restart of HR-BS/RS</entry></row><row><entry /><entry /><entry>including multimode BS/RS</entry></row><row><entry /><entry /><entry>0b010: Power down (including</entry></row><row><entry /><entry /><entry>FA down) of HR-BS/RS</entry></row><row><entry /><entry /><entry>including multimode BS/RS</entry></row><row><entry /><entry /><entry>0b011: Power reduction of</entry></row><row><entry /><entry /><entry>HR-BS/RS including multimode</entry></row><row><entry /><entry /><entry>BS/RS</entry></row><row><entry /><entry /><entry>0b100: Backhaul link down of</entry></row><row><entry /><entry /><entry>HR-BS</entry></row><row><entry /><entry /><entry>0b101: Backhaul link up of</entry></row><row><entry /><entry /><entry>HR-BS</entry></row><row><entry /><entry /><entry>0b110: FA change of HR-BS/RS</entry></row><row><entry /><entry /><entry>including multimode BS/RS</entry></row><row><entry /><entry /><entry>0b111: Multimode service end</entry></row><row><entry /><entry /><entry>of HR-MS</entry></row><row><entry>If (Action Type</entry><entry /><entry /><entry>//</entry></row><row><entry>== 0b000) {</entry><entry /><entry /><entry>reconfigu-</entry></row><row><entry /><entry /><entry /><entry>ration</entry></row><row><entry> New IDcell</entry><entry>10</entry><entry>New IDcell that the ABS will</entry><entry>Optional</entry></row><row><entry /><entry /><entry>use after the reconfiguration</entry></row><row><entry /><entry /><entry>process.</entry></row><row><entry> Frame</entry><entry>6</entry><entry>New mapping between value of</entry><entry>Optional</entry></row><row><entry> configuration</entry><entry /><entry>this index and frame</entry></row><row><entry> index</entry><entry /><entry>configuration is listed in Table</entry></row><row><entry /><entry /><entry>806, Table 807, and Table 808.</entry></row><row><entry> Unavailable</entry><entry>8</entry><entry>Start of unavailable time in unit </entry><entry>Mandatory</entry></row><row><entry> Start Time</entry><entry /><entry>of frame.</entry></row><row><entry> (UST)</entry></row><row><entry>Unavailable</entry><entry>8</entry><entry>Interval of unavailable time in</entry><entry>Mandatory</entry></row><row><entry>Time Interval</entry><entry /><entry>unit of superframe.</entry></row><row><entry>(UTI)</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// restart</entry></row><row><entry>Type == 0b001)</entry></row><row><entry>{</entry></row><row><entry> Unavailable</entry><entry>8</entry><entry>Start of unavailable time in unit</entry><entry>Mandatory</entry></row><row><entry> Start Time</entry><entry /><entry>of frame.</entry></row><row><entry> (UST)</entry></row><row><entry> Unavailable</entry><entry>8</entry><entry>Interval of unavailable time in</entry><entry>Mandatory</entry></row><row><entry>Time Interval</entry><entry /><entry>unit of superframe.</entry></row><row><entry>(UTI)</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// power</entry></row><row><entry>Type == 0b010)</entry><entry /><entry /><entry>down</entry></row><row><entry>{</entry></row><row><entry> Time of Power</entry><entry>8</entry><entry>Expected time when the</entry><entry>Mandatory</entry></row><row><entry> Down</entry><entry /><entry>HR-BS will be powered down</entry></row><row><entry /><entry /><entry>in units of frame.</entry></row><row><entry> Expected</entry><entry>8</entry><entry>Expected uptime of BS in units</entry><entry>Optional</entry></row><row><entry> uptime of BS</entry><entry /><entry>of superframe.</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// power</entry></row><row><entry>Type == 0b011)</entry><entry /><entry /><entry>reduction</entry></row><row><entry>{</entry></row><row><entry> Tx Power</entry><entry>10</entry><entry>dB value of Tx power reduction.</entry><entry>Mandatory</entry></row><row><entry> Reduction</entry></row><row><entry> Expected time</entry><entry>8</entry><entry>Expected resource adjustment</entry></row><row><entry> of power</entry><entry /><entry>time in units of frame.</entry></row><row><entry> reduction</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// backhaul</entry></row><row><entry>Type == 0b100)</entry><entry /><entry /><entry>link down</entry></row><row><entry>{</entry></row><row><entry> Time of</entry><entry>8</entry><entry>Expected time when the</entry><entry>Optional</entry></row><row><entry> backhaul link</entry><entry /><entry>backhaul link will be down in</entry></row><row><entry> down</entry><entry /><entry>units of superframe.</entry></row><row><entry> Expected time</entry><entry>8</entry><entry>Expected time in unit of LSB of</entry><entry>Optional</entry></row><row><entry> of backhaul</entry><entry /><entry>superframe when backhaul</entry></row><row><entry> link available</entry><entry /><entry>link will be available of HR-BS</entry></row><row><entry /><entry /><entry>either itself or via neighbor</entry></row><row><entry /><entry /><entry>HR-BS.</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// backhaul</entry></row><row><entry>Type == 0b101)</entry><entry /><entry /><entry>link up</entry></row><row><entry>{</entry></row><row><entry> Expected time</entry><entry>8</entry><entry>Expected time in unit of LSB of</entry><entry>Optional</entry></row><row><entry> of backhaul</entry><entry /><entry>superframe when the HR-BS</entry></row><row><entry> link up</entry><entry /><entry>restarts service without any help</entry></row><row><entry /><entry /><entry>of neighbor BS using relay link</entry></row><row><entry /><entry /><entry>but the HR-BS' backhaul link.</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// FA change</entry></row><row><entry>Type ==</entry></row><row><entry>0b110){</entry></row><row><entry>FA index</entry><entry>8</entry><entry>FA index</entry><entry>Mandatory</entry></row><row><entry>Expected</entry><entry>8</entry><entry>Expected current FA downtime</entry></row><row><entry>downtime of</entry><entry /><entry>in units of frame.</entry></row><row><entry>current FA</entry></row><row><entry>Expected</entry><entry>8</entry><entry>Expected uptime of new FA in</entry><entry>Optional</entry></row><row><entry>uptime of new</entry><entry /><entry>units of superframe.</entry></row><row><entry>FA</entry></row><row><entry>} else if (Action</entry><entry /><entry /><entry>// multimode</entry></row><row><entry>Type == 0b111)</entry><entry /><entry /><entry>service end</entry></row><row><entry>{</entry></row><row><entry> Expected time</entry><entry>8</entry><entry>Expected time in unit of LSB of</entry><entry>Optional</entry></row><row><entry> of backhaul</entry><entry /><entry>superframe when the HR-MS</entry></row><row><entry> link up</entry><entry /><entry>releases the multimode service</entry></row><row><entry /><entry /><entry>and allows subordinate MS</entry></row><row><entry /><entry /><entry>to perform handover to other</entry></row><row><entry /><entry /><entry>infrastructure.</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0218<tables id="TABLE-US-00021" num="00021"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="77pt" align="left" /><colspec colname="2" colwidth="35pt" align="center" /><colspec colname="3" colwidth="105pt" align="left" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE 21</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Syntax</entry><entry>Size (bit)</entry><entry>Notes</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>MM-ADV message</entry><entry>—</entry><entry>—</entry></row><row><entry>format ( ) {</entry></row><row><entry> Management Message</entry><entry>8</entry><entry>—</entry></row><row><entry> Type = xx</entry></row><row><entry> Action Type</entry><entry>3</entry><entry>Used to indicate the purpose of</entry></row><row><entry /><entry /><entry>this message.</entry></row><row><entry /><entry /><entry>0b000: Reconfiguration of</entry></row><row><entry /><entry /><entry>HR-BS/RS including multimode</entry></row><row><entry /><entry /><entry>BS/RS</entry></row><row><entry /><entry /><entry>0b001: Restart of HR-BS/RS</entry></row><row><entry /><entry /><entry>including multimode BS/RS</entry></row><row><entry /><entry /><entry>0b010: Power down (including FA</entry></row><row><entry /><entry /><entry>down) of HR-BS/RS including</entry></row><row><entry /><entry /><entry>multimode BS/RS</entry></row><row><entry /><entry /><entry>0b011: Power reduction of</entry></row><row><entry /><entry /><entry>HR-BS/RS including multimode</entry></row><row><entry /><entry /><entry>BS/RS</entry></row><row><entry /><entry /><entry>0b100: Backhaul link down of</entry></row><row><entry /><entry /><entry>HR-BS</entry></row><row><entry /><entry /><entry>0b101: Backhaul link up of HR-BS</entry></row><row><entry /><entry /><entry>0b110: FA change of HR-BS/RS</entry></row><row><entry /><entry /><entry>including multimode BS/RS</entry></row><row><entry /><entry /><entry>0b111: Multimode service end of</entry></row><row><entry /><entry /><entry>HR-MS</entry></row><row><entry> reserved</entry><entry>5</entry></row><row><entry> TLV encodings for</entry><entry>variable</entry><entry>TLV-specific</entry></row><row><entry> MM-ADV</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0219The MM-ADV includes, particularly, a corresponding situation and a start time point, an end time point, and a situation duration of a corresponding situation, and transmits the corresponding situation and the start time point, the end time point, and the situation duration of the corresponding situation to a subordinate apparatus.

p-0220As shown in Tables 20 and 21, when PHY/MAC configuration information is changed, the control message includes the changed information and may be transmitted. Further, even when transmission power is changed, the control message includes the changed transmission power and may be transmitted, and when one of a plurality of frequencies is unavailable, the control message may include corresponding frequency information and an unavailable period.

p-0221Table 20 represents a reason for information transmission, i.e., an action type with only one transmission reason, but may complexly express a plurality of transmission reasons with a method of expressing a corresponding action type in a form of a bitmap and include information.

p-0222Thereafter, the subordinate apparatus <b>500</b>, having received the MM-ADV, performs a continuous service by enabling an apparatus including a BS, an RS, or a multi-mode MS that transmits/receives data to perform handover to another apparatus with reference to unavailability and change periods of a service or waits until a time at which a corresponding apparatus resumes a service, and resumes a service (S<b>530</b>).

p-0223Particularly, when the MS terminates a role of a BS or an RS, the MS requests a subordinate apparatus to perform handover to another BS or an RS. When changing a function of an MS to a role of a BS and an RS, by transmitting information of a subordinate apparatus to an MS to perform a role of a corresponding BS and RS, handover can be efficiently performed.

p-0224Further, when the MS terminates a role of a BS or an RS, the MS performs only an original function thereof and thus the MS may be set to prevent another cell or an MS to perform initial access from connecting, and for example, sets a cell bar bit within SFH of IEEE 802.16m and transmits the MM-ADV.

p-0225Further, an RS, an MS that performs a role of an RS, or a BS that establishes a relay link due to a disconnection of a backhaul link receives changed system configuration information from a superordinate BS through a relay link and transmits a MM-ADV that is suggested in the present invention. Corresponding system configuration information may be forwarded in a process of setting a relay link.

p-0226In another exemplary embodiment, a BS or an RS to which a relay link is established, a BS or an RS that operates in a network, or a multi-mode MS acting as a BS may notify a subordinate MS that the BS, the RS, or the multi-mode MS operates in a multi-mode. In this case, the state may be included in the MM-ADV, but connection of an MS attempting to enter from the outside may be prevented or may be limited. In order to perform this, a cell bar bit may be set within SFH of IEEE 802.16m or another field may be newly defined, for example, may be newly included in SFH or SCD, or may be included within DCD of IEEE 802.16-2009. Further, by allocating a specific preamble index to an MS having no backhaul link in a network or acting as an RS or a BS, a corresponding fact may be notified to a subordinate MS or an MS that is scheduled to enter. In order to previously limit entry, a method NBR-ADV of notifying information including information of an adjacent BS may be used. Further, in order to limit entry, when scanning an adjacent BS, different conditions from those of a general BS and RS may be notified to a subordinate MS.

p-0227TLV that is shown in Table 21 exists in a form of Table 22, and includes the following information.

p-0228<tables id="TABLE-US-00022" num="00022"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="28pt" align="left" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="28pt" align="center" /><colspec colname="4" colwidth="133pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 22</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Name</entry><entry>Type</entry><entry>Length</entry><entry>Value</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Time to</entry><entry>1</entry><entry>1</entry><entry>Start time of the action in unit of 8-bit LSBs</entry></row><row><entry>start the</entry><entry /><entry /><entry>of frame number.</entry></row><row><entry>action</entry><entry /><entry /><entry>Indicates the unavailable time due to</entry></row><row><entry /><entry /><entry /><entry>reconfiguration 0b000, restart 0b001,</entry></row><row><entry /><entry /><entry /><entry>power down 0b010, backhaul link down</entry></row><row><entry /><entry /><entry /><entry>0b100, or FA change 0b110.</entry></row><row><entry /><entry /><entry /><entry>It also indicates the time for power</entry></row><row><entry /><entry /><entry /><entry>reduction 0b011 or expected backhaul</entry></row><row><entry /><entry /><entry /><entry>linkup 0b111.</entry></row><row><entry>Time</entry><entry>2</entry><entry>1</entry><entry>Time for the action in unit of 8-bit LSBs of</entry></row><row><entry>during</entry><entry /><entry /><entry>frame number.</entry></row><row><entry>action</entry><entry /><entry /><entry>If acting type is set to 0b000, 0b001, or</entry></row><row><entry /><entry /><entry /><entry>0b100, it is the unavailable time interval.</entry></row><row><entry /><entry /><entry /><entry>After this time, during action, the BS will</entry></row><row><entry /><entry /><entry /><entry>reconfigure 0b000, restart service 0b001,</entry></row><row><entry /><entry /><entry /><entry>or backhaul link available either by itself or</entry></row><row><entry /><entry /><entry /><entry>via a neighbor HR-BS 0b100.</entry></row><row><entry>DCD</entry><entry>3</entry><entry>variable</entry><entry>The DCD_setting is a compound TLV</entry></row><row><entry>setting</entry><entry /><entry /><entry>value that encapsulates TLVs from the BS'</entry></row><row><entry /><entry /><entry /><entry>DCD message that may be transmitted in</entry></row><row><entry /><entry /><entry /><entry>the advertised BS downlink channel after</entry></row><row><entry /><entry /><entry /><entry>reconfiguration.</entry></row><row><entry>UCD</entry><entry>4</entry><entry>variable</entry><entry>The UCD_setting is a compound TLV</entry></row><row><entry>setting</entry><entry /><entry /><entry>value that encapsulates TLVs from the BS'</entry></row><row><entry /><entry /><entry /><entry>UCD message that may be transmitted in</entry></row><row><entry /><entry /><entry /><entry>the advertised BS downlink channel after</entry></row><row><entry /><entry /><entry /><entry>reconfiguration.</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0229When an action type is 0b000, 0b001, 0b010, and 0b011, a “time to start the action” is included, and additionally, even when an action type is 0b101, 0b110, and 0b110, a “time to start the action” may be included. In this case, the time to start the action is a time point at which a corresponding situation occurs and indicates a frame number or an LSB of a frame number.

p-0230Further, when an action type is 0b000, 0b001, and 0b011, a time during action is included, and additionally, even when an action type is 0b010, 0b100, and 0b110, a time during action may be added. In this case, the time during action indicates a time at which a corresponding situation occurs.

p-0231When an action type is 0b000, a new PHY/MAC parameter change value is included, and a previous value is updated to a new value.

p-0232When an action type is 0b011, reduced transmission power may be included.

p-0233When an action type is 0b110, a changed frequency allocation index (FA index) is included and thus a frequency allocation change may be performed.

p-0234According to the present exemplary embodiment, in a communication system, when an MS performs a role of a BS or an RS, a method of transmitting a control message is provided, and by continuously performing a transmission service, communication can be smoothly maintained.

p-0235While this invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.