[go: up one dir, main page]

WO2010070385A1 - Attribution de sous-trames pour noeud relais - Google Patents

Attribution de sous-trames pour noeud relais Download PDF

Info

Publication number
WO2010070385A1
WO2010070385A1 PCT/IB2008/055400 IB2008055400W WO2010070385A1 WO 2010070385 A1 WO2010070385 A1 WO 2010070385A1 IB 2008055400 W IB2008055400 W IB 2008055400W WO 2010070385 A1 WO2010070385 A1 WO 2010070385A1
Authority
WO
WIPO (PCT)
Prior art keywords
frame
sub
type
hybrid
downlink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IB2008/055400
Other languages
English (en)
Inventor
Zhenhong Li
Haifeng Wang
Bin Zhou
Jing Xu
Wei Ni
Wei Zhou
Gang Wu
Jorma Lilleberg
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Nokia Inc
Original Assignee
Nokia Siemens Networks Oy
Nokia Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Siemens Networks Oy, Nokia Inc filed Critical Nokia Siemens Networks Oy
Priority to PCT/IB2008/055400 priority Critical patent/WO2010070385A1/fr
Publication of WO2010070385A1 publication Critical patent/WO2010070385A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15557—Selecting relay station operation mode, e.g. between amplify and forward mode, decode and forward mode or FDD - and TDD mode

Definitions

  • This description relates to the communication of information, and more specifically the communication of information via a relay node.
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • LTE-Advanced a new radio access technique
  • LTE is expected to improve end-user throughput, increase sector capacity, reduce user plane latency, and consequently offer superior user experience with full mobility.
  • the Evolved UMTS Terrestrial Radio Access (E-UTRA) standard typically includes the air interface of 3GPP's LTE for mobile networks.
  • An E-UTRA network or, as it is occasionally referred to, a LTE network includes a network that is substantially in compliance with the LTE standards, their derivatives, or predecessors (hereafter, "the LTE standard” or "Release 8 standard”).
  • the LTE standard or "Release 8 standard”
  • 3rd Generation Partnership Project Technical Specification Group Radio Access Network
  • Evolved Universal Terrestrial Radio Access (E-UTRA) Physical Channels and Modulation (Release SJ, 3GPP TS 36.211 V8.4.0 (2008-09), Sept. 2008.
  • a method may comprise determining, by a base station, whether the base station is operating as part of a system comprising a relay node. If so, in one embodiment, selecting a frame structure, from a set of at least one predetermined frame structure, to employ to regulate communication between nodes with the system.
  • the selected frame structure may comprise hybrid sub-frames and access sub-frames.
  • the method may include communicating user data with at least one user equipment node during the access sub- frames.
  • the method may comprise communicating with the relay node during the hybrid sub-frames.
  • an apparatus may comprise a processor and a transceiver.
  • the processor may be configured to determine whether the apparatus is operating as part of a system comprising a relay node. If so, in various embodiments, the processor may also be configured to select a frame structure, from a set of at least one predetermined frame structure, to employ to regulate communication between nodes with the system. In some embodiments, the selected frame structure comprises hybrid sub-frames and access sub-frames.
  • the transceiver may be configured to communicate user data with at least one user equipment nodes during the access sub-frames. In one embodiment, the transceiver may be configured to communicate user data with the relay node during the hybrid sub-frames.
  • a method may comprise determining which frame structure, of a predefined set of at least one frame structure, is being employed by a base station.
  • a relay node may be configured to relay communication between the base station and a remote user equipment node.
  • the method may include selecting a frame structure to be employed by the relay node, based upon the frame structure employed by the base station.
  • the method may include communicating data between the base station and relay node during a hybrid sub-frame comprised in the frame structure employed by the base station.
  • the method may include communicating data between the relay node and the remote user equipment node during an access sub-frame comprised in the frame structure employed by the base station.
  • an apparatus may comprise a processor and a transceiver.
  • the processor may be configured to determine which frame structure, of a predefined set of at least one frame structure, is being employed by the base station.
  • the processor further be configured to select a frame structure to be employed by the apparatus, based upon the frame structure employed by the base station.
  • the transceiver may be configured to relay information between a base station and a remote user equipment node.
  • the transceiver may be configured to communicate data between the base station and apparatus during a hybrid sub-frame comprised in the frame structure employed by the base station.
  • the transceiver may be configured to communicate data between the apparatus and the remote user equipment node during an access sub-frame comprised in the frame structure employed by the base station.
  • FtG 1 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FIG 2 is block diagrams of example embodiments of systems in accordance with the disclosed subject matter.
  • F(G 3 is a block diagram of an example embodiment of an apparatus in accordance with the disclosed subject matter.
  • FIG 4 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FlG 5 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FlG 6 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FIG 7 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FlG 8 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FlG 9 is a table of an example embodiment of a set of frame structures in accordance with the disclosed subject matter.
  • FIG 10 is a table of an example embodiment of a set of frame structures in accordance with known art.
  • FlG 11 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • FIG 12 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • FIG 1 is a block diagram of a wireless network 102 including an evolved Node Bs (eNBs) or base station (BS) 104 and user equipment (UE) or mobile stations (MSs) 106, 108, 110, according to an example embodiment.
  • eNBs evolved Node Bs
  • BS base station
  • UE user equipment
  • MSs mobile stations
  • Each of the MSs 106, 108, 110 may be associated with BS 104, and may transmit data in an uplink (UL) direction to BS 104, and may receive data in a downlink (DL) direction from BS 104, for example.
  • UL uplink
  • DL downlink
  • mobile stations 106, 108 and 110 may be coupled to base station 104 via relay stations or relay nodes, for example.
  • the base station 104 may be connected via wired or wireless links to another network (not shown), such as a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, etc..
  • the base station 104 may be coupled or connected with the other network 120 via an access network controller (ASN) or gateway (GW) 112 that may control, monitor, or limit access to the other network.
  • ASN access network controller
  • GW gateway
  • FIG 2 is block diagrams of example embodiments of systems 200 (Fig. 2a) and 201 (Fig. 2b) in accordance with the disclosed subject matter.
  • both systems 200 and 201 may include a plurality of MSs or UEs 206, 208, and 210, a base station 220, and a relay node (RN) 222.
  • the BS 220 may provide a wireless network 212 within a given range.
  • the relay node 222 may provide a wireless network 214 within a given range.
  • the range of the wireless networks may be determined by various factors, such as, the power output of the BS or RN, the attenuation of the signals experience by physical objects in the environment (e.g., walls, trees, etc.), other interference, etc., although, it is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • a relay node 222 may act similarly to a secondary or supplemental BS.
  • the relay node 222 may be configured to relay or re-transmit communication between the BS 220 and a remote UE (RUE) ⁇ e.g., RUEs 206 and 208).
  • RUE remote UE
  • UEs directly connected or in communication with the BS 220 may be referred to as local UEs (e.g., LUE 210).
  • the RN 222 may include substantially fixed relay nodes, mobile relay nodes, or include other types of relay nodes.
  • the relay node 222 may be configured to extend the range of the wireless network, such as illustrated by system 200 of Fig. 2a.
  • the range of the RN provided wireless network 214 may lie substantially outside of the BS provided network 212, such that UEs may connect to a wireless network even when outside the range of the BS 220.
  • the RN 222 may be configured to increase the capacity of the wireless network, such as illustrated by system 201 of Fig. 2b.
  • the range of the RN provided wireless network 214 may lie substantially within mat of the BS provided network 212, such that a number of UEs (e.g., RUEs 206 and 208) user data may be serviced by the RN 222, increasing the UE servicing capacity of the system 201 as a whole.
  • UEs e.g., RUEs 206 and 208
  • the communication link 216 between the BS 220 and the RN 222 may be referred to as a relay link.
  • the communication links 218 between the UEs (e.g., UEs 206, 208, and 210) and their respective servicing or providing nodes (e.g., RN 222 and BS 220) may be referred to access links.
  • FIG 3 is a block diagram of an example embodiment of a system or apparatus 301 in accordance with the disclosed subject matter.
  • the apparatus or wireless station 301 e.g., base station 220, user equipment 206, relay station 222, etc.
  • the apparatus or wireless station 301 may include, for example, an RF (radio frequency) or wireless transceiver 302, including a transmitter to transmit signals and a receiver to receive signals, a processor or baseband processor 304 to execute instructions or software and control transmission and receptions of signals, and a memory 306 to store data and/or instructions.
  • RF radio frequency
  • wireless transceiver 302 including a transmitter to transmit signals and a receiver to receive signals, a processor or baseband processor 304 to execute instructions or software and control transmission and receptions of signals, and a memory 306 to store data and/or instructions.
  • Processor 304 may also make decisions or determinations, generate frames or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 304 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 302.
  • Processor 304 may control transmission of signals or messages over a wireless network, and may receive signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 302, for example).
  • Processor 304 may be programmable and capable of executing software, firmware, or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 304 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 304 and transceiver 302 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 308 may execute software and instructions, and may provide overall control for the station 301, and may provide control for other systems not shown in FIG 3, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 301, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 304, or other controller or processor, performing one or more of the functions or tasks described above.
  • FIG 10 is a table of an example embodiment of a set of frame structures 1010 in accordance with known art.
  • an eNB or BS may coordinate the transmission of data within a system.
  • the BS may accomplish this coordination by allocating slices of time in which a MS or UE may send or receive data.
  • these time slices may be referred to a sub- frames.
  • three types of sub-frames may exist, as downlink (D or DL) sub-frame for transferring data from the BS to the UEs, an uplink (U or UL) sub-frame for transmitting data from the UEs to the BS, and a special (S) sub-frame for, among other things, transmitting control information and providing a gap or silent period for switching the transceiver from send to receive, or vice versa.
  • D or DL sub-frame for transferring data from the BS to the UEs
  • U or UL sub-frame for transmitting data from the UEs to the BS
  • S special sub-frame for, among other things, transmitting control information and providing a gap or silent period for switching the transceiver from send to receive, or vice versa.
  • a set of predefined frame structures may be defined.
  • a "frame structure" may include a predefined order in which DL, UL, and S sub-frames may occur within a half-frame or full frame.
  • Fig. 10 illustrates a set of 7 frame structures 1000, 1001, 1002, 1003, 1004, 1005, and 1006 that may be selected by a BS in one specific illustrative embodiment based upon the Release 8 standard; although, it is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • FIG 4 is a block diagram of an example embodiment of a system 400 in accordance with the disclosed subject matter.
  • the system 400 may include a BS 402, at least one LUE 404, a RN 406, and at least one RUE 408.
  • the BS 402 may be in direct communication with the LUE 404 and the RN 406.
  • the RN 406 may be in direct communication with the RUE 408.
  • the system 400 may produce and employ the frame structure illustrated in Fig. 4.
  • the system 400 may make use of a protocol that employs frames 410 comprising 10 sub-frames (e.g., sub-frame 412).
  • each frame 410 may conceptually divided into two half frames (e.g., half frame 409) of 5 sub-frames.
  • a frame 410 may include a period of substantially 10ms.
  • the half-frame 409 may include a period of substantially 5ms
  • each sub-frame may include a period of substantially lms.
  • the system 400 or BS 402 may produce or employ different versions of the above sub-frame types.
  • the system 400 or BS 402 may employ access sub-frames (e.g., access DL sub-frames, access UL, sub-frames) in which communication occurs only between the BS 402 and the LUE 404, via the respective access link.
  • access sub-frames e.g., access DL sub-frames, access UL, sub-frames
  • the system 400 or BS 402 may employ hybrid sub-frames (e.g., hybrid DL sub-frames, hybrid UL sub-frames) in which communication occurs between the BS 402 and the LUE 404, and the BS 402 and the RN 406, via both the access link and relay link, respectively.
  • hybrid sub-frames e.g., hybrid DL sub-frames, hybrid UL sub-frames
  • the path of communication is i llustrated by a communication pair (e.g., BS -> LUE), in which the transmitting node or device (e.g., BS 402) is written first, and the receiving node or device (e.g., LUE 404) is written second.
  • the arrows also denote the direction of communication, from transmitting to receiving.
  • DL sub-frames include sub- frames in which the BS 402 transmits information to the LUE 404 or RN 406, and/or the RN 406 transmits information to the RUE 408.
  • UL sub-frames include sub-frames in which the BS 402 receives information from the LUE 404 or RN 406, and/or the RN 406 receives information from the RUE 408. It is noted, that different devices may experience different sub-frame types (e.g. access DL sub-frame, hybrid UL sub-frame, etc.) within the same sub-frame time period (e.g., sub-frame 416 may include a hybrid UL sub-frame types for BS 402, LUE 404, and RN 406, but an access DL sub-frame with respect to RUE 408).
  • sub-frame types e.g. access DL sub-frame, hybrid UL sub-frame, etc.
  • Fig. 4 illustrates a frame structure 401 that may be, in various embodiments, similar to the Release 8 standard frame structure 1001 of Fig. 10. In various embodiments, this frame structure 401 may repeat every 5 sub-frames or each half-frame.
  • the sub-frame types of sub-frame 422 may be equal to the sub-frame types of sub-frame 412, and sub-frame 424 to sub-frame 414, sub-frame 426 to sub-frame 416, sub-frame 428 to sub-frame 418, sub-frame 430 to sub-frame 420, and so on as the system continues to operate or until a new frame structure is selected.
  • this may be referred to as the "switch-point periodicity" referring to the number of times the transceiver of the BS 402 switches from DL to UL (or vice versa) and, therefore, in various embodiments, the period of time between Special (S) sub-frames (e.g., sub-frame 414, sub-frame 424).
  • S Special
  • the BS 402 may select a frame structure from a predetermined set of frame structures (e.g., the set illustrated by Fig. 9). In various embodiments, the BS 402 may also select between two sets of frame structures, a first set that include frame structures for use with a RN (e.g., Table 910 of Fig. 9), and a second set for use without a RN (e.g., Table 1010 of Fig. 10). In some embodiments, the BS 402 may then employ this selected frame structure for purposes of resource (e.g. , DL and UL sub-frames or resource blocks) allocation and the timing of communication within the system. In various embodiments, the RN 406 and LUE 404 may detect the frame structure selected by the BS 402.
  • resource e.g. , DL and UL sub-frames or resource blocks
  • the BS 402 may select the frame structure 401 illustrated in Fig. 4.
  • the frame structure 401 may include a hybrid DL sub-frame type during sub-frame 412.
  • the BS 402 may transmit data to the LUE 404 and the RN 406.
  • the RUE 408 may effectively transmit no information or maintain an idle state. In various embodiments, this may be accomplished by the RN 406 informing the RUE 408 that a DL sub-frame type is occurring (causing the RUE 408 to "listen" and not transmit), but the RN 406 may refrain from communicating with the RUE 408.
  • the frame structure 401 may include a special (S) sub-frame type for all devices during the sub-frame 414.
  • S sub-frame type is discussed in more detail in reference to Figs. 6, 7, 8, and 9.
  • the frame structure 401 may include a hybrid UL sub-frame type during sub-frame 416.
  • the BS 402 may receive data from both the LUE 404 and the RN 406.
  • the RUE 408 may effectively transmit no information or maintain an idle state. In various embodiments, this may be accomplished by the RN 406 informing the RUE 408 that a DL sub-frame type is occurring, as described above. In one embodiment, the RN 406 may substantially simultaneously transmit information to both the BS 402 and the RUE 408.
  • the frame structure 401 may include an access UL sub-frame type during sub-frame 418.
  • the BS 402 may receive data, via the access link, from the LUE 404, but not the RN 406 (which employs a relay link with BS 402).
  • the RUE 408 may transmit information to the RN 406, via its respective access link.
  • the frame structure 401 may include an access DL sub-frame type during sub-frame 420.
  • the BS 402 may transmit data, via the access link, to the LUE 404, but not the RN 406 (which employs a relay link with BS 402).
  • the RN 406 may transmit information to the RUE 408, via its respective access link.
  • FIG 5 is a block diagram of an example embodiment of a system 500 in accordance with the disclosed subject matter.
  • the system 500 may include a BS 402, at least one LUE 404, a RN 406, and at least one RUE 408.
  • the BS 402 may be in direct communication with the LUE 404 and the RN 406.
  • the RN 406 may be in direct communication with the RUE 408.
  • the system 500 may produce and employ the frame structure illustrated in Fig. 5.
  • Fig. 5 illustrates a frame structure 501 that may be, in various embodiments, similar to the Release 8 standard frame structure 1001 of Fig. 10.
  • this frame structure 501 may repeat every 5 sub-frames or each half-frame.
  • the sub-frame types of sub-frame 522 may be equal to the sub-frame types of sub-frame 512, and sub-frame 524 to sub-frame 514, sub-frame 526 to sub-frame 516, sub-frame 528 to sub-frame 518, sub-frame 530 to sub-frame 520, and so on as the system continues to operate or until a new frame structure is selected.
  • the BS 402 may select the frame structure 50] illustrated in Fig. 5.
  • the frame structure 501 may include an access DL sub-frame type during sub-frame 512.
  • the BS 402 may transmit information to the LUE 404, via their access link.
  • the RN 406 may transmit information to the RUE 408, via their access link, as described above.
  • the frame structure 501 may include an S sub- frame type during sub-frame 514, as described above.
  • the frame structure 501 may include a hybrid UL sub-frame type during the sub-frame 516.
  • the BS 402 may receive information from both the LUE 402 and the RN 406, as described above.
  • the frame structure 501 may include an access UL sub-frame type during the sub-frame 518.
  • the LUE 404 may transmit information to the BS 402, via their access link.
  • the RUE 408 may transmit information to the RN 406, via their access link, as described above.
  • the frame structure 501 may include a hybrid DL sub-frame type during sub-frame 520, as described above.
  • FIG 6 is a block diagram of an example embodiment of a system 600 in accordance with the disclosed subject matter.
  • the system 600 may include a BS 402, at least one LUE 404, a RN 406, and at least one RUE 408.
  • the BS 402 may be in direct communication with the LUE 404 and the RN 406.
  • the RN 406 may be in direct communication with the RUE 408.
  • the system 600 may produce and employ the frame structure illustrated in Fig. 6.
  • Fig. 6a illustrates a frame structure 601 that may be, in various embodiments, similar to the Release 8 standard frame structure 1001 of Fig. 10.
  • this frame structure 601 may repeat every 5 sub-frames or each half-frame.
  • the sub-frame types of sub-frame 622 may be equal to the sub-frame types of sub-frame 612, and sub-frame 624 to sub-frame 614, sub-frame 626 to sub-frame 616, sub-frame 628 to sub-frame 618, sub-frame 630 to sub-frame 620, and so on as the system continues to operate or until a new frame structure is selected.
  • the BS 402 may select the frame structure 60] illustrated in Fig. 6.
  • the frame structure 601 may include an access DL sub-frame type during sub-frame 612, as described above.
  • the frame structure 601 may include an S sub-frame type during sub-frame 614.
  • the frame structure 601 may include an access UL sub-frame type during sub-frame 616, as described above.
  • the frame structure 601 may include a hybrid UL sub-frame type during the sub-frame 618, as described above.
  • the frame structure 601 may also include a hybrid DL sub-frame type during the sub-frame 620, as described above.
  • Fig. 6b illustrates an embodiment of system 600 and frame structure 601 b in which the RN 406 is employed in the system in a non-transparent mode.
  • Fig. 2a illustrates an embodiment of such a system.
  • the RN is configured to extend the range of the BS.
  • the BS 402 may not be able to transmit directly to the RUE 408. Therefore, the RUE 408 may receive control information from the RN 406.
  • frame structure 601b is used to illustrate the concept of non-transparent relaying, the disclosed subject matter is not limited to this illustrative embodiment.
  • the special (S) sub-frame type (e.g. , as occurring during sub-frame 614) may include at least three fields or time periods: Downlink Pilot Timeslot (Dw or DwPTS) 692, Guard Period (GP) 694, and Uplink Pilot Timeslot (Up or UpPTS) 696. In some embodiments, these periods may include control information.
  • Dw or DwPTS Downlink Pilot Timeslot
  • GP Guard Period
  • Uplink Pilot Timeslot Up or UpPTS 696.
  • these periods may include control information.
  • the DwPTS 692 may include various control signaling from the controlling node (e.g., BS 402, RN 406) to the respective controlled nodes (e.g., LUE 404, RUE 408).
  • the DwPTS 692 may include a Physical Downlink Control Channel (PDCCH) portion, and a Physical Downlink Shared Channel (PDSCH) portion (not shown).
  • the PDCCH may include scheduling assignments and other control information.
  • the PDSCH may include higher layer control information (e.g., system information, a synchronization signal, etc.) or user data.
  • the GP 694 may include a period of time in which transmission and reception are muted or not scheduled to occur. In various embodiments, such a time period may allow re-configuration of the antenna or transceiver of a device from receiver to a transmitter or vice versa. In various embodiments, the GP 694 may also account for transmission time between devices (e.g., eNB & UE, BS or MS, etc.).
  • devices e.g., eNB & UE, BS or MS, etc.
  • the UpPTS 696 may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), and a Physical Random Access Channel (PRACH), similar to the DwPTS 692, as described above.
  • the UpPTS 696 may include various control signaling to the controlling node (e.g., BS 402, RN 406) from the respective controlled nodes (e.g., LUE 404, RUE 408).
  • the controlling node e.g., BS 402, RN 406
  • the respective controlled nodes e.g., LUE 404, RUE 408.
  • the system 600 may operate in a non-transparent mode.
  • the BS 402 may transmit and receive control information to and from the LUE 404.
  • the RN 406 may transmit and receive control information to and from the RUE 408.
  • two sets of controlling information may be communicated, a BS 402 centric set and a RN 406 centric set.
  • the respective UEs LUE 404 and RUE 408 may scan the communication channel for these control signals.
  • a DL sub-frame type directly preceding the S sub-frame type.
  • an access DL sub-frame type may be preferred, in which two communication channels are established prior to the S sub-frame type.
  • FIG. 7 is a block diagram of an example embodiment of a system 700 in accordance with the disclosed subject matter.
  • the system 700 may include a BS 402, at least one LUE 404, a RN 406, and at least one RUE 408.
  • the BS 402 may be in direct communication with the LUE 404 and the RN 406.
  • the RN 406 may be in direct communication with the RUE 408.
  • the system 700 may produce and employ the frame structure illustrated in Fig. 7.
  • Fig. 7a illustrates a frame structure 701 that may be, in various embodiments, similar to the Release 8 standard frame structure 1001 of Fig. 10.
  • this frame structure 701 may repeat every 5 sub-frames or each half-frame.
  • the sub-frame types of sub-frame 722 may be equal to the sub-frame types of sub-frame 712, and sub-frame 724 to sub-frame 714, sub-frame 726 to sub-frame 716, sub-frame 728 to sub-frame 718, sub-frame 730 to sub-frame 720, and so on as the system continues to operate or until a new frame structure is selected.
  • the BS 402 may select the frame structure 701 illustrated in Fig. 7.
  • the frame structure 701 may include a hybrid DL sub-frame type during sub-frame 712, as described above.
  • the frame structure 701 may include an S sub-frame type during sub-frame 714.
  • the frame structure 701 may include an access UL sub-frame type during sub-frame 716, as described above.
  • the frame structure 701 may include a hybrid UL sub-frame type during the sub-frame 718, as described above.
  • the frame structure 701 may also include an access DL sub-frame type during the sub-frame 720, as described above.
  • Fig. 7b illustrates an embodiment of system 700 and frame structure 701b in which the RN 406 is employed in the system in a transparent mode.
  • Fig. 2b illustrates an embodiment of such a system.
  • the RN is configured to increase the capacity of the BS.
  • the BS 402 may be able to transmit directly to the RUE 408. Therefore, the RUE 408 may receive control information from the BS 402.
  • frame structure 701b is used to illustrate the concept of transparent relaying, the disclosed subject matter is not limited to this illustrative embodiment.
  • the special (S) sub-frame type (e.g., as occurring during sub-frame 714) may include at least three fields or time periods: Downlink Pilot Timeslot (Dw or DwPTS) 792, Guard Period (GP) 794, and Uplink Pilot Timeslot (Up or UpPTS) 796. As described above, in some embodiments, these periods may include control information.
  • Dw or DwPTS Downlink Pilot Timeslot
  • GP Guard Period
  • Up or UpPTS Uplink Pilot Timeslot
  • these periods may include control information.
  • the system 700 may operate in a transparent mode.
  • the BS 402 may transmit and receive control information to and from both the LUE 404 and the RUE 408.
  • the RN 406 may Idle or otherwise remain silent (as illustrated by highlighted sub-frame 798). In various embodiments, this may allow the RN 406 to not interfere with the transmission of the other devices.
  • the RN 406 may receive control information from the BS 402 and the RUE 408.
  • FIG 8 is a block diagram of an example embodiment of a system 800 in accordance with the disclosed subject matter.
  • the system 800 may include a BS 402, at least one LUE 404, a RN 406, and at least one RUE 408.
  • the BS 402 may be in direct communication with the LUE 404 and the RN 406.
  • the RN 406 may be in direct communication with the RUE 408.
  • the system 800 may produce and employ the frame structure illustrated in Fig. 8.
  • Fig. 8 illustrates frame structures 801 a and 801b that may be, in various embodiments, similar to the Release 8 standard frame structure 1003 of Fig. 10.
  • Fig. 8 also illustrates frame structures 801c and 801d that may be, in various embodiments, similar to the Release 8 standard frame structure 1004 of Fig. 10.
  • this frame structures 801a, 801b, 801c and 801 d may repeat every 10 sub- frames or each frame. Therefore, no explicit repetition is illustrated.
  • Fig. 8a illustrates frame structure 80 Ia for a non-transparent configuration of system 800.
  • Fig. 8b illustrates frame structure 801b for a non-transparent configuration of system 800, but with the DwPTS 692, GP 694, and UpPTS 696 portions detailed.
  • Fig. 8c illustrates frame structure 801c for a transparent configuration of system 800.
  • Fig. 8d illustrates frame structure 80 Id for a transparent configuration of system 800, but with the DwPTS 792, GP 794, and UpPTS 796 portions detailed.
  • frame structures 801a and 80b include a hybrid DL sub-frame type during sub-frame 812
  • frame structures 801c and 801 d include an access DL sub-frame type during sub-frame 812.
  • both frame structure embodiments 801a/b and 801c/d may include a S sub-frame type (of non-transparent or transparent configuration respectively) during sub-frame 814, an access UL sub-frame type during sub-frames 816 and 818, a hybrid UL sub-frame during sub-frame 820, an access DL sub-frame type during sub-frame 822, 824, and 826, and a hybrid DL sub-frame type during sub-frames 828 and 830.
  • S sub-frame type of non-transparent or transparent configuration respectively
  • FIG 9 is a table 910 of an example embodiment of a set of frame structures in accordance with the disclosed subject matter, as described above.
  • the set of frame structures may be employed for use in a system including a relay node (RN).
  • the set of frame structures may include 8 frame structures 901, 902, 903, 904, 905, 906, 907, and 908.
  • the frame structures may make use of or employ hybrid DL sub-frames (HD), hybrid UL sub-frames (HU), access DL sub-frames (AD), access UL sub-frames (AU), and special (S) sub-frames.
  • HD hybrid DL sub-frames
  • HU hybrid UL sub-frames
  • AD access DL sub-frames
  • AU access UL sub-frames
  • S special sub-frames
  • frame structures 901, 902, 903, and 904 have the same DL-UL allocation or ratio
  • the different distribution of access sub-frames and hybrid sub-frames amongst the frame structures may, in various embodiments, differently impact system performance (e.g., round trip time (RTT), Hybrid automatic repeat-request (HARQ)-process number, spectrum efficiency, etc.)
  • RTT round trip time
  • HARQ Hybrid automatic repeat-request
  • a receiving node e.g., a RN
  • the proper sub-frame type e.g., an access DL sub-frame
  • an ACK message may be transmitted back to the original sending device (e.g., the RUE).
  • the RTT for the transmittal of information (by a source node) until the receipt (again by the source node) of an ACK or NACK message confirming the information was properly (or not) received by the destination node may vary based upon the frame structure selected.
  • the BS may switch transmission/reception during the GP of the S sub-frame
  • the RN may be required to switch operating modes (UL-to-DL, and vice versa) more often depending on the frame structure employed. Such concerns may impact the efficiency of a system and may determine or influence the selection of a frame structure.
  • the frame structure 903 may be selected and employed. Such an embodiment may be advantageous because, in various embodiments, the number of switch points (UL-to-DL, and vice versa) encountered by the RN may be less than frame structures 902 or 904. Also, in some embodiments in which the processing time for the RUE is sufficiently small ⁇ e.g., less than 2ms) the RTT for RUE communications may be less than frame structure 901 ⁇ e.g., 15 or 20 ms versus 25 ms).
  • the frame structure 908 may be selected and employed. Such an embodiment may be advantageous because, in various embodiments, the RTT of the average RUE-related transmission may be less than frame structure 906 ⁇ e.g., 20ms DL or 30 ms UL versus 30 ms DL and UL). Furthermore, in various embodiments, the RTT of the average LUE-related transmission may be unaffected compared to RTT from comparable frame structures of Table 1010 of Fig. 10.
  • the frame structures 901 or 904 may be selected or employed. Such embodiments may be advantageous because, in various embodiments, the Shared Channel portions of the S sub-frame may be shared between the BS and RN, resulting in lower overhead and a short latency in the UE cell search procedure, bi various embodiments, the frame structure 604 may be preferred because the number of switch points experienced by the RN may be lower than frame structure 601 and, if the processing time for the RUE is sufficiently small (e.g., less than 2ms) the RTT for RUE communications may be less the frame structure 901 ⁇ e.g., 20 or 25 ms versus 25 ms).
  • the frame structures 905 and 907 may be selected and employed. Such an embodiment may be advantageous because, in various embodiments, the RTT of the average RUE-related transmission may be less than frame structures 905 (e.g., 20ms DL or 30 ms UL versus 30 ms DL and UL). Furthermore, in one embodiment, a legacy non-RN aware UE may be serviced by a RN (which the legacy UE may see as a BS) as the frame structures 905 and 907 may be backwards compatible with prior standards.
  • a legacy non-RN aware UE may be serviced by a RN (which the legacy UE may see as a BS) as the frame structures 905 and 907 may be backwards compatible with prior standards.
  • FIG 11 is a flow chart of an example embodiment of a technique 1100 in accordance with the disclosed subject matter, bi various embodiments, the technique 1100 may be performed by the system of Figs. 1 or 2, the apparatus of Fig. 3, as described above. In some embodiments, the technique 1100 may be used with a frame structures as illustrated by Figs. 4, 5, 6, 7, 8 and/or 9, as described above.
  • Block 1102 illustrates that, in one embodiment, a base station may determine whether or not the BS is operating in a system including a relay station, as described above. In various embodiments, determining may include receiving a message from the RN. In various embodiments, the action(s) illustrated by this block may be performed by various elements, such as the BS 104 of Fig. 1, the BS 220 of Fig. 2, the apparatus 301, and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • Block 1104 illustrates that, in one embodiment, if the system includes both a BS and RN, the BS may select a frame structure, from a set of predetermined frame structures, to employ to regulate communication between nodes with the system, as described above. In various embodiments, if the system does not include an RN, a frame structure may be selected from second set of frame structures (e.g., the set illustrated by Fig. 10), as described above.
  • Block 1105 illustrates that, in one embodiment, the selected frame structure of Block 1104 may include hybrid sub-frames and access sub-frames, as described above.
  • selecting may include selecting a frame structure that periodically repeats, for example, every half-frame, every frame, etc..
  • selecting may include selecting a frame structure substantially similar to one illustrated by Figs. 4, 5, 6, 7, 8 and/or 9.
  • selecting may include determining if the RN is operating in a transparent or non-transparent mode, as described above.
  • selecting a first frame structure e.g., a frame structure such as frame structures 903, 906, or 908 of Fig. 9, etc.
  • selecting a second frame structure e.g., a frame structure such as frame structures 901 , 904, 905, or 907 of Fig. 9, etc.
  • Blocks 1104 and 1105 may be performed by various elements, such as the BS 104 of Fig. 1 , the BS 220 of Fig. 2, the apparatus 301 , and/or the processor 304 of Fig. 3, as described above.
  • Block 1106 illustrates that, in one embodiment, the BS may communicate user data with at least one user equipment node during the access sub-frames, as described above.
  • “user data” includes data that is moved essentially as cargo or payload information between nodes of the network, as opposed to control or configuration data.
  • the BS may communicate user data only with the UE nodes during the access sub-frames, as described above.
  • Block 1108 illustrates that, in one embodiment, the BS may communicate with the relay node and/or a local user equipment node during the hybrid sub-frames, as described above.
  • the action(s) illustrated by this block may be performed by various elements, such as the BS 104 of Fig. 1, the BS 220 of Fig. 2, the apparatus 301, and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • FIG 12 is a flow chart of an example embodiment of a technique 1200 in accordance with the disclosed subject matter.
  • the technique 1200 may be performed by the system of Figs. 1 or 2, the apparatus of Fig. 3, as described above.
  • the technique 1200 may be used with a frame structures as illustrated by Figs. 4, 5, 6, 7, 8 and/or 9, as described above.
  • Block 1202 illustrates that, in one embodiment, a RN may determine which frame structure, of a predefined set of frame structures, is being employed by a base station (BS), as described above. In various embodiments, determining may include receiving a control signal from the BS. In various embodiments, the action(s) illustrated by this block may be performed by various elements, such as the RN 222 of Fig. 2, the apparatus 301, and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • Block 1204 illustrates that, in one embodiment, the RN may select a frame structure to be employed by the relay node, based upon the frame structure employed by the BS, as described above.
  • selecting may include using a frame structure associated, possibly in a 1-to-l mapping, with the frame structure employed by the BS.
  • selecting may include receiving a dictated frame structure from the BS.
  • selecting may include determining if the RN is configured to operate in a transparent or non-transparent mode. In such an embodiment, if the RN is configured to operate in a transparent mode, refraining from transmitting a downlink pilot u ' meslot during a special sub-frame type, as described above. Conversely, if the RN is configured to operate in a non-transparent mode, the RN may, in one embodiment, transmit its own DwPTS during the S sub-frame timeslot, as described above. In various embodiments, the action(s) illustrated by this block may be performed by various dements, such as the RN 222 of Fig. 2, the apparatus 301, and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • Block 1206 illustrates that, in one embodiment, the RN may be allocated, , an B S- to- RN downlink sub-frame that will occur during the hybrid sub-frame as described above.
  • the BS may allocate a BS-to-RN downlink hybrid sub-frame to the RN.
  • the RN may not allocate any resource blocks or units to communicate with the RUE during that time.
  • this allocation may have the effect of substantially silencing the RUE or causing the RUE to refrain from transmitting during this sub-frame time slot, as described above.
  • the action(s) illustrated by this block may be performed by various elements, such as the RN 222 of Fig. 2, the apparatus 301, and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • Block 1208 illustrates that, in one embodiment, the RN may communicate data between the BS and RN during a hybrid sub-frame included in the frame structure employed by the BS, as described above. In various embodiments, the RN may not communicate with the BS for various reasons (e.g., no data to communicate, etc.). In various embodiments, communicating may include receiving, by the RN, data from the BS during a hybrid downlink sub-frame, as described above. In another embodiment, communicating may include transmitting, to the BS, data from the RN during a hybrid uplink sub-frame, as described above. In various embodiments, the action(s) illustrated by this block may be performed by various elements, such as the RN 222 of Fig. 2, the apparatus 301 , and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • Block 1210 illustrates that, in one embodiment, the BS may not communicate traffic or payload data to the RUE during the allocated BS-to-RN downlink hybrid sub-frame, as described above. In various embodiments, this may have the effect of leaving the RUE in an idle or silenced state during that sub-frame's time slot, as described above. In various embodiments, the action(s) illustrated by this block may be performed by various elements, such as the RN 222 of Fig. 2, the apparatus 301 , and/or the transceiver 302 or me processor 304 of Fig. 3, as described above.
  • Block 1212 illustrates that, in one embodiment, the RN may communicate data between the RN and the RUE during an access sub-frame included in the frame structure employed by the BS, as described above.
  • the RN may not communicate with the RUE for various reasons (e.g. , no data to communicate, the RUE may be in a power saving mode, etc.). It is also understood mat the communication may be bi-directional and the direction may be based upon whether or not the sub-frame is an uplink or downlink sub-frame, as described above.
  • the action(s) illustrated by this block may be performed by various elements, such as the RN 222 of Fig. 2, the apparatus 301, and/or the transceiver 302 or the processor 304 of Fig. 3, as described above.
  • Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
  • data processing apparatus e.g., a programmable processor, a computer, or multiple computers.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
  • Method steps may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FEKJA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FEKJA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry.
  • Implementations may be implemented in a computing system that includes components interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon un aspect général, l'invention porte sur un procédé consistant à déterminer dans une station de base si ladite station de base fonctionne dans le cadre d'un système comprenant un nœud relais et, le cas échéant, dans un mode de réalisation particulier, à sélectionner une structure de trame dans un ensemble d'au moins une structure de trame prédéterminée destinée à la régulation de la communication entre les nœuds du système. Dans divers modes de réalisation, la structure de trame sélectionnée peut comprendre des sous-trames hybrides et des sous-trames d'accès. Dans certains modes de réalisation, le procédé comprend la communication de données utilisateur avec au moins un nœud d'équipement utilisateur pendant les sous-trames d'accès. Dans divers modes de réalisation, le procédé comprend une communication avec le nœud relais pendant les sous-trames hybrides.
PCT/IB2008/055400 2008-12-17 2008-12-17 Attribution de sous-trames pour noeud relais Ceased WO2010070385A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2008/055400 WO2010070385A1 (fr) 2008-12-17 2008-12-17 Attribution de sous-trames pour noeud relais

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2008/055400 WO2010070385A1 (fr) 2008-12-17 2008-12-17 Attribution de sous-trames pour noeud relais

Publications (1)

Publication Number Publication Date
WO2010070385A1 true WO2010070385A1 (fr) 2010-06-24

Family

ID=42268368

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2008/055400 Ceased WO2010070385A1 (fr) 2008-12-17 2008-12-17 Attribution de sous-trames pour noeud relais

Country Status (1)

Country Link
WO (1) WO2010070385A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110267992A1 (en) * 2009-01-05 2011-11-03 Lg Electronics Inc. Method for relaying data performed by a relay station in wireless communication system based on tdd
US8953467B2 (en) 2008-09-08 2015-02-10 Nokia Corporation Adaptive transmission modes for transparent relay
CN110036663A (zh) * 2016-10-07 2019-07-19 Idac控股公司 在移动网络中实施有限移动性的方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Relaying for LTE-Advanced", 3GPP TSG RAN WG1 MEETING #55 R1-084136, November 2008 (2008-11-01), XP050317431, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_55/Docs/> *
GANG SHEN ET AL.: "Adaptive Multi-hop Relay Frame Structure in IEEE 802.16m", IEEE 802.16 BROADBAND WIRELESS ACCESS WORKING GROUP, 17 March 2008 (2008-03-17), pages 1 - 7, XP003026422, Retrieved from the Internet <URL:http://wirelessman.org/tgm/contrib/C80216m-08_198r1.doc> [retrieved on 20090707] *
YONGKANG LIU ET AL: "Relay Enhanced Architecture for Broadband Wireless Access Networks", 2007, XP031157825, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4379045> [retrieved on 20090706] *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8953467B2 (en) 2008-09-08 2015-02-10 Nokia Corporation Adaptive transmission modes for transparent relay
US20110267992A1 (en) * 2009-01-05 2011-11-03 Lg Electronics Inc. Method for relaying data performed by a relay station in wireless communication system based on tdd
US8942101B2 (en) * 2009-01-05 2015-01-27 Lg Electronics Inc. Method for relaying data performed by a relay station in wireless communication system based on TDD
CN110036663A (zh) * 2016-10-07 2019-07-19 Idac控股公司 在移动网络中实施有限移动性的方法
US11540187B2 (en) 2016-10-07 2022-12-27 Idac Holdings, Inc. Methods for enforcing limited mobility in mobile network
US11843985B2 (en) 2016-10-07 2023-12-12 Interdigital Patent Holdings, Inc. Methods for enforcing limited mobility in mobile network
US12245318B2 (en) 2016-10-07 2025-03-04 Interdigital Patent Holdings, Inc. Methods for enforcing limited mobility in mobile network

Similar Documents

Publication Publication Date Title
US12010708B2 (en) System and method for supporting inter-band carrier aggregation with different UL/DL TDD configurations
US9648619B2 (en) Method for relaying data in wireless communication system based on time division duplex
KR102117024B1 (ko) 무선 통신 시스템의 통신 방법 및 장치
CN102318227B (zh) 在中继站与基站之间发送/接收数据的方法
CN102282781B (zh) 在无线电通信系统中使用mbsfn子帧的信号传输方法
US20160381680A1 (en) User terminal, radio base station and radio communication method
KR102102649B1 (ko) 무선 접속 시스템에서 ack/nack 전송 방법 및 이를 위한 장치
US20110176461A1 (en) Determining configuration of subframes in a radio communications system
US20130272169A1 (en) Harq for dynamic change of the tdd ul/dl configuration in lte tdd systems
KR20190017656A (ko) 무선 통신 시스템에서 sfi (slot format information) 충돌을 처리하기 위한 방법 및 장치
EP3603256B1 (fr) Noeud de réseau et procédé dans un réseau de télécommunications sans fil
US20200244406A1 (en) Method for handling an adaptive retransmission in a wireless communication system and device therefor
SG177260A1 (en) Method and apparatus for synchronous harq operation and interference avoidance
IL262071A (en) Radio network junction, wireless device and methods performed in them
US9929833B2 (en) Method for transmitting a HARQ feedback and device therefor
US20200296735A1 (en) Retransmission of messages using a non-orthogonal multiple access (noma) communication system
WO2010070385A1 (fr) Attribution de sous-trames pour noeud relais
KR20160000749A (ko) 이동 통신 시스템에서 스케줄링 및 피드백 방법 및 장치
US9706385B1 (en) Systems and methods for configuring device to device communication
CN101919178A (zh) Fdd通信网络的转发节点和终端设备及运行其的方法
KR20160018289A (ko) D2d 신호를 고려한 무선 통신 방법 및 장치
HK1218810A1 (zh) 在3gpp lte网络中操作的中央处理单元和由其执行的方法
HK1177996A (en) Method and apparatus for synchronous harq operation and interference avoidance

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08878864

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08878864

Country of ref document: EP

Kind code of ref document: A1