[go: up one dir, main page]

US9246662B2 - Mechanisms addressing dynamic component carrier change in relay systems - Google Patents

Mechanisms addressing dynamic component carrier change in relay systems Download PDF

Info

Publication number
US9246662B2
US9246662B2 US14/356,190 US201114356190A US9246662B2 US 9246662 B2 US9246662 B2 US 9246662B2 US 201114356190 A US201114356190 A US 201114356190A US 9246662 B2 US9246662 B2 US 9246662B2
Authority
US
United States
Prior art keywords
interface
reconfiguration
update information
update
message
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.)
Active, expires
Application number
US14/356,190
Other languages
English (en)
Other versions
US20140307586A1 (en
Inventor
Shun Liang Zhang
Lei Du
Simone Redana
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 Technologies Oy
Original Assignee
Nokia Solutions and Networks Oy
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 Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Publication of US20140307586A1 publication Critical patent/US20140307586A1/en
Assigned to NOKIA SOLUTIONS AND NETWORKS OY reassignment NOKIA SOLUTIONS AND NETWORKS OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: REDANA, SIMONE, DU, LEI, ZHANG, SHUN LIANG
Application granted granted Critical
Publication of US9246662B2 publication Critical patent/US9246662B2/en
Assigned to NOKIA TECHNOLOGIES OY reassignment NOKIA TECHNOLOGIES OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA SOLUTIONS AND NETWORKS OY
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0085—Timing of allocation when channel conditions change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • 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/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H04B7/15542—Selecting at relay station its transmit and receive resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04W72/0406—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

Definitions

  • the present invention relates to mechanisms addressing dynamic component carrier change in relay systems.
  • it addresses activities and signaling of entities and/or devices forming part of such relay systems such as a relay node and associated network transceiver station.
  • a relay node RN acts as a transceiver station (like evolved Node_B, eNB) towards a terminal device (such as a user equipment, UE).
  • a terminal device such as a user equipment, UE.
  • UE user equipment
  • a relay node relays or propagates signals it receives from a network transceiver device which is referred to as “donor” evolved Node_B, DeNB, and which insofar “donates” resources to the relay node.
  • LTE/LTE-A is referred to as a mere example only and that other standards may apply relaying. Hence, insofar as such other standards and/or systems apply relaying in a similar environment as discussed herein below, principles and/or embodiments taught by this invention may likewise be applicable to such other environments under another standard/system. In order to prevent the description from becoming too complex, however, for explanatory purposes, reference is made to LTE/LTE-A, and at least partly also the corresponding terminology is applied.
  • the relay node RN acts as a UE from the DeNB point of view, while it behaves as an eNB for UEs served by the RN. Therefore, the RN supports eNB functionality as well as UE functionality.
  • FIG. 1 shows an exemplary architecture of a relaying system and elements constituting the relay system and interfaces there between.
  • mobility management entities/serving gateways MME/S-GW are connected to an evolved Node_B, eNB, or a Donor evolved Node_B, DeNB.
  • a connection from a MME/S-GW towards an eNB is achieved via an interface S1
  • a connection from an MME/S-GW towards a Donor eNB, DeNB is accomplished using an interface S11.
  • a Donor eNB may act as a “conventional” eNB as well as a Donor eNB, DeNB, this one is connected via both interfaces S1 and S11 to a respective MME/S-GW.
  • a Un interface interconnects a relay node RN and a Donor eNB, DeNB.
  • the Un interface carries the X2 interface and S1 interface between the RN and the DeNB.
  • the interfaces used for interconnection also represent to a certain extent the layer in the OSI (open system interconnection) signaling model on which these interfaces are applied.
  • the relay node RN, the eNB, and the DeNB at least constitute the evolved UTRAN (E-UTRAN), i.e. the evolved universal terrestrial radio access network.
  • the relay node relays signaling to and from a terminal such as user equipment UE from and to the DeNB.
  • the interface between the user equipment UE and the relay node RN is referred to as Uu interface, which is the same interface as between an eNB and a UE.
  • Uu interface The interface between the user equipment UE and the relay node RN
  • the interface or link between UE and RN is also referred to as access link
  • the interface between RN and DeNB, in particular the Un interface thereof is referred to as backhaul link
  • the interface or link between DeNB and UE is also referred to as direct link.
  • a relay node thus represents a device comprising a transceiver device, configured to communicate via a first interface (access link) Uu with a terminal and via a second interface (backhaul link) Un with a remote network device DeNB.
  • a relay system One critical issue of a relay system is the capacity of the backhaul link, which may be shared by many relay nodes.
  • the backhaul link of relay system is a potential bottleneck of relay system.
  • Applying principles of carrier aggregation CA to the relay system has not been investigated in Release 10 of LTE. Given that a framework for CA and a basic process of CA operation has meanwhile been determined by 3GPP in Rel10, but not for relay systems, it is useful to investigate the potential issues on applying CA also to relay systems.
  • Dynamic component carrier change may affect the access link as well as backhaul link, i.e. a change on the access link may impact the backhaul link and vice versa.
  • multiple component carriers could be applied to backhaul link only, or to relay access link only, or to both relay access link and backhaul link.
  • the UE When carrier aggregation is configured, the UE only has one RRC (radio resource control) connection with the network.
  • RRC connection establishment/re-establishment/handover one serving cell provides the NAS (network access stratum) mobility information (e.g. TAI (timing advance information)), and at RRC connection re-establishment/handover, one serving cell provides the security input.
  • This cell is referred to as the Primary Cell (PCell).
  • the carrier corresponding to the PCell is the Downlink Primary Component Carrier (DL PCC), while in the uplink it is the Uplink Primary Component Carrier (UL PCC).
  • SCells Secondary Cells can be configured to form together with the PCell a set of serving cells.
  • the carrier corresponding to an SCell is a Downlink Secondary Component Carrier (DL SCC) while in the uplink it is an Uplink Secondary Component Carrier (UL SCC).
  • DL SCC Downlink Secondary Component Carrier
  • UL SCC Uplink Secondary Component Carrier
  • a SCell can be activated and deactivated dynamically by the network side (control entities) based on downlink DL and uplink UL traffic requirement of terminals such as UEs.
  • the radio resource control, RRC, reconfiguration process has been improved to add/modify/release secondary cells SCells of a UE and specific MAC CE (media access control control elements) have been introduced to activate/deactivate the configured secondary cells.
  • the carrier aggregation can in principle be applied to the Uu radio link between RN and UE (access link). Likewise, by taking RN as a normal UE the carrier aggregation can in principle also be applied to the Un radio link between DeNB and RN (backhaul link).
  • the Rel.10 specifications support CA on the backhaul and access fink but what is done on one link does not have to impact the other link. This makes CA not usable in relay deployment because we need to have disjoint sets of CCs for the backhaul and access links.
  • FIGS. 2 to 5 are used as possible examples.
  • “Inband” refers to a scenario in which the backhaul link and access link rely on the same component carrier CC
  • “outband” refers to a scenario in which the backhaul link and access link rely on a different component carrier CC.
  • FIG. 2 illustrates a change from inband to outband relay system on CC 1 .
  • the RN indicates its resource partitioning request on CC 1 to DeNB because CC 1 is also used as PCell on the access link towards the UE (see FIG. 2( a )).
  • the RN may decide to change the PCell of the UE over access link from CC 1 to CC 3 due to some reasons, such as interference avoidance (see FIG. 2( b )).
  • the issue is how to inform the DeNB that resource partitioning request on CC 1 is not needed anymore during the operation period.
  • FIG. 3 illustrates a change from outband to inband relay system on CC 1 .
  • the relay system is changed from outband system to inband system on CC 1 .
  • the resource partitioning would be necessary on CC 1 .
  • a resource partitioning request is only informed to DeNB during RRC connection establishment process, i.e. in the RRC Connection Setup Complete message. After that it is not necessary to change a resource partitioning request because the support of carrier aggregation in relay deployment was not a requirement in Release 10. Therefore, the existing mechanism specified in Rel.10 for a single CC used, both on the access and backhaul link (other CCs can be used on the backhaul and access links but they have to be different), can't be used to solve the issue of a relay system with multiple component carriers on the access link that are also used on the backhaul link.
  • a CC change on a RN's backhaul link is also possible.
  • the following figures show possible scenarios of a change on a relay node's backhaul link during relay operation mode.
  • a resource partitioning is provided by the DeNB to the RN via RN Reconfiguration message.
  • the message contains the Frequency-Division-Duplex (FDD)/Time-Division-Duplex (TDD) subframe configuration (the resource partitioning, FDD is case of FDD system or TDD in case of TDD system) and the Relay-Physical Downlink Control Channel (R-PDCCH) configuration.
  • the message can also be used to convey the System Information Block Type1 (SIB1) and System Information Block Type2 (SIB2).
  • FIG. 4 illustrates a change from outband to inband relay system on CC 1 due to a component carrier change on the backhaul link.
  • the RN indicates its resource partitioning request to DeNB.
  • the additional CC that is also used on the access link (as CC 1 in the example shown in FIG. 4( b )) is needed to be activated on the backhaul link due to some reasons, it is not addressed how the DeNB knows about the RN's capability, i.e. whether resource partitioning is needed, on CC 1 and how it provides appropriate configuration accordingly. Additionally, if resource partitioning is needed for more than one component carriers, how to provide the configuration is another problem.
  • FIG. 5 illustrates a change from inband to outband relay system on CC 1 due to a component carrier change on the backhaul link.
  • a SCell (CC 1 as shown in FIG. 5( a )) is removed on the backhaul link.
  • CC 1 the resource partitioning on the RN's access link is not necessary anymore. It is thus an issue to provide for means to release the configured Un subframe info applied on RN's access link.
  • resource partitioning is applied for more than one component carriers, how to change the configurations is another problem.
  • the configured RN subframe configuration (on the backhaul link) including the FDD/TDD subframe configuration and the R-PDCCH configuration are only released when the RRC connection is released. Hence, it is not considered a good solution to terminate the entire RRC connection that is shared by all CCs on the backhaul link.
  • a device comprising a transceiver device, configured to communicate via a second interface with a remote device configured to communicate via a first interface with a terminal, wherein communication via the first and/or second interface is configured to operate based on aggregation of plural individual component carriers, and a control device, configured to perform, per component carrier: receiving of update information pertaining to at least the first interface from the remote device, sending of reconfiguration instructions to the remote device for being applied on the first interface, and initiation of reconfiguration of the second interface based on the received update information and/or reconfiguration instructions sent to the remote device.
  • a method comprising: communicating via a second interface with a remote device configured to communicate via a first interface with a terminal, wherein communication via the first and/or second interface is configured to operate based on aggregation of plural individual component carriers, and performing, per component carrier: receiving update information pertaining to at least the first interface from the remote device, sending reconfiguration instructions to the remote device for being applied on the first interface, and initiating reconfiguration of the second interface based on the received update information and/or reconfiguration instructions sent to the remote device.
  • a fifth aspect of the present invention there are provided computer program products comprising computer-executable components which, when the program is run on a computer, are configured to execute the method aspects according to the third and the fourth aspect disclosed in relation to the operation of the relay node RN and the donor eNB DeNB, respectively.
  • the above computer program product/products may be embodied as a computer-readable storage medium.
  • the methods, devices and computer program products described in this document use, at least in exemplary embodiments, some methods which enable the negotiation and configuration for an added, released or modified component carrier on either the access link or backhaul link. These enable to provide for proper resource partitioning on the backhaul and access link in relay systems even during operation of the relay system. They remove the need to tear down an entire RRC connection and to rebuild a new RRC connection, thus at least temporarily disruption the RRC connection. Rather, at least individual ones of the proposed exemplary scenarios allow for a continuous operation of the relay systems using carrier aggregation even when a change in component carriers on either the access link or backhaul link occurs or needs to be initiated.
  • performance improvement is based on those methods, devices and computer program products enabling continuous operation of the relay systems using carrier aggregation even when a change in component carriers on either the access link or backhaul link occurs or needs to be initiated.
  • FIG. 1 illustrates an exemplary architecture of a relaying system
  • FIG. 2 illustrates a change from inband to outband relay system on CC 1 due to a component carrier change on the access link;
  • FIG. 3 illustrates a change from outband to inband relay system on CC 1 due to a component carrier change on the access link;
  • FIG. 4 illustrates a change from outband to inband relay system on CC 1 due to a component carrier change on the backhaul link
  • FIG. 5 illustrates a change from inband to outband relay system on CC 1 due to a component carrier change on the backhaul link
  • FIG. 6 illustrates an RRC based approach as an exemplary embodiment
  • FIG. 7 illustrates an X2 application protocol based approach as another exemplary embodiment
  • FIG. 8 illustrates a MAC based approach as another exemplary embodiment
  • FIG. 9 illustrates an enhanced RRC process to handle CC change on RN's backhaul link as another exemplary embodiment
  • FIG. 10 illustrates a RN capability transfer process as another exemplary embodiment.
  • the invention is implemented in a relay system comprising a relay node device, RN, and a remote network device (i.e. a Donor eNB), interfacing each other via a second interface (backhaul link), while the relay node interface a terminal such as UE via a first interface (access link).
  • a relay node device RN
  • a remote network device i.e. a Donor eNB
  • Carrier aggregation CA providing primary and secondary component carriers PCell, SCell, or CC in general, is applicable on both, the access link as well as the backhaul link.
  • relay system is described below with reference to a system based on LTE/LTE-A, the methods, devices and computer program products presented herein are generally applicable to other systems and/or standards may be applied to such relay systems applying carrier aggregation, while principles taught by at least exemplary embodiments relating to this invention remain applicable.
  • Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic.
  • the software, application logic and/or hardware generally reside on devices and or subsets like transceivers and/or modems thereof and/or controllers associated thereto.
  • the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media.
  • a “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or smart phone, or user equipment.
  • the present invention relates in particular but without limitation to mobile communications, for example to relay system environments based on carrier aggregation under WCDMA, LTE, WIMAX and WLAN and can advantageously be implemented in relay nodes RN and/or donor eNBs, DeNB,s connectable to such networks. That is, it can be implemented as/in chipsets to connected devices, and/or modems thereof.
  • the different functions discussed herein may be performed in a different order and/or concurrently with each other.
  • one or more of the above-described functions may be optional or may be combined.
  • FIGS. 6 to 8 Embodiments Related to Access Link Related Scenarios
  • a relay node RN indicates to a donor eNB, DeNB, whether a RN subframe configuration (including FDD/TDD subframe configuration and R-PDCCH configuration) is required for the backhaul CCs due to the changes on the access link.
  • a new RRC layer process is defined, and it is initiated for the RN to indicate (upon it has detected, S 61 , one or more changes on the access link that occurred or are necessary to occur and resource partitioning needs to be updated) a change request, S 62 , for RN subframe configuration (from not necessary to necessary or vice versa).
  • a change is detected/signaled per CC depending on the activation or deactivation of the CC on the access link.
  • the RN Upon deciding to activate or deactivate one or more CC on the access link, in case the resource partitioning information informed to the DeNB during startup phase (or RRC connection establishment) needs to be updated, the RN sends (S 62 ) a RRC message (such as RRC Reconfiguration Request) to the DeNB to inform the changed resource partitioning request on each CC that will be impacted.
  • the RN can also propose a FDD/TDD subframe configuration, and/or also an R-PDCCH configuration, for these CCs, i.e. at least one of a FDD/TDD subframe and an R-PDCCH configuration. That is, a corresponding the update information is sent only when the device configuration needs to be changed due to a change concerning a component carrier on the first interface.
  • the RN sends the resource partitioning need also for CCs not yet used on the backhaul link but that are configured on the backhaul link such that when the DeNB activates them, it already knows whether it has to apply resource partitioning or not on these CCs. That is, the RN sends the resource partitioning request update related to active CCs on the access link that are also active on the backhaul link.
  • the above mentioned option enables the RN to send the resource partitioning request update related to active CCs on the access link that are also active or inactive (but configured) on the backhaul link.
  • the RN decides to release one or more CC on the access link the resource partitioning is not needed anymore for these CCs.
  • the resource partitioning is needed if these CCs are also active on the backhaul link.
  • the RN wants to activate one or more CCs on the access link, it informs the DeNB that the resource partitioning is necessary on these CCs if these CCs are also active on the backhaul link.
  • the RN can also send a proposal for the FDD/TDD sub-frame configuration on these CCs on the access link, for example based on the capacity needed on the access link.
  • the proposed FDD/TDD sub-frame configuration can be also sent for CCs already activated but for which the RN would prefer to change the resource partitioning.
  • the DeNB upon receipt thereof, can accept, deny or modify the CC changes on the access link indicated by such request (including the need for the resource partitioning and the proposed FDD/TDD sub-frame configuration) based on backhaul load status or other consideration such as interference, and replies to the RN with a response RRC message (S 64 ).
  • the corresponding FDD/TDD sub-frame configuration info for the related CC is provided (S 65 ). If not accepted, the DeNB rejects the changes and the RN should not activate/deactivate the corresponding CCs on the access link.
  • the DeNB determines/releases the FDD/TDD sub-frame configuration applied on the corresponding CCs of the backhaul link immediately upon receiving the RRC message from the RN, and—in any case—informs the RN (S 63 & S 65 ) about the RN sub-frame configuration for each CC.
  • Such message is acknowledged in a signaling “RN Reconfiguration Complete”, S 66 , from the RN to the DeNB.
  • RN Upon reception of a response message (S 64 ) and/or (re-)configuration message (S 65 ) from the DeNB and initiation of the response message (S 66 ), RN initiates CC activation/deactivation on the access link (S 67 a ) and applies the updated RN subframe configurations.
  • DeNB Upon reception of a response message (S 66 ) from the RN, DeNB applies the updated RN subframe configurations (S 67 b ).
  • Messages of S 64 and S 65 may optionally be combined into a single message.
  • a variant consists of having the decision to add or release a CC on the access link at the RN and apply these changes without the need to be accepted/denied/modified by the DeNB. Stated in other words, the changes are always and unconditionally accepted.
  • the DeNB upon receiving the RRC Reconfiguration Request (in S 62 ) decides the RN sub-frame configuration for the CCs that need to be changed on the access link and provides them to the RN. In this case, the message S 64 is not sent from the DeNB to the RN.
  • the UE capability message is sent from the UE to the eNB when requested or required by the eNB.
  • the RN indicates its updated capability actively to the DeNB instead of just providing its capability info to DeNB when required or requested by the DeNB.
  • the capability message can be used when one or more change on the access link occurred or is necessary to occur and resource partitioning needs to be updated.
  • the RN sends the resource partitioning need also for CCs not yet used on the backhaul link but that are configured on the backhaul link such that when the DeNB activates them, it already knows whether it has to apply resource partitioning or not on these CCs.
  • the RN In case of any CC change (CC adding or removing or modification) on its access link, the RN indicates the updated CCs status on its access link, and also the updated resource partitioning request on related CCs as the updated capability info to DeNB actively, i.e. based on his own initiative upon detecting the change or need for change. Then, based on the updated capability info of the RN, the DeNB may provide updated RN subframe configurations (including FDD/TDD subframe configuration and R-PDCCH configuration) to the RN accordingly. Besides, upon the reception of the unsolicited UE capability info message from the RN, the DeNB may reply with a message to confirm the message has been received correctly. This message could also contain the acceptance or rejection (or any potential modification) of the proposed changes or simply confirm the reception of the UE capability message, depending on the implementation variant (see exemplary embodiment 1).
  • the RN may indicate the updated resource partitioning request of related CCs in the X2AP/S1AP message together with an optional proposed FDD/TDD sub-frame configuration.
  • the RN sends the resource partitioning need also for CCs not yet used on the backhaul link but that are configured on the backhaul link such that when the DeNB activates them, it already knows whether it has to apply resource partitioning or not on these CCs.
  • DeNB Upon receiving the X2AP/S1AP message of S 72 , DeNB transfers (S 73 ) to its RRC layer the received application protocol layer information on CCs change and/or updated resource partitioning request info and the proposed FDD/TDD sub-frame configuration of the related CCs. In case the CCs activation/deactivation on the access link is acceptable (S 75 ), the DeNB provides (S 76 ) RN sub-frames configuration (including FDD/TDD subframe configuration and R-PDCCH configuration) of the concerned CCs to the RN. As shown in the particular example of FIG.
  • the DeNB decides to release (deactivate), S 74 , the configured RN sub-frames applied on the corresponding CC of the backhaul link immediately upon receiving the S1AP/X2AP message.
  • the release is done (S 78 a , S 78 b ) only upon sending/receiving the confirmation from the RN, in S 77 , that the updated RN subframe configurations have been received.
  • the RN Upon reception of RN subframe (re-)configuration info of related CCs (carried by a RRC message) or S1AP/X2AP response message (S 76 , optionally acknowledged by a message, S 77 ), the RN initiates CC adding/removal/modification process on the access link (S 78 ) and applies the received RN subframe configurations.
  • FIG. 7 is related to use X2-AP messages, in a similar way it would be with S1-AP messages, where S1 eNB Configuration Update and S1 eNB Configuration Update Ack messages are used.
  • a new MAC CE Media Access Control Control Element
  • SCell/PCell activation or deactivation the changed resource partitioning request can be easily derived
  • a potentially resulting proposed RN subframe configuration including FDD/TDD sub-frame configuration and R-PDCCH configuration
  • the RN initiates, S 82 , a MAC process to indicate the change request on the access link by the new IE (information element) included in a MAC message to the DeNB, potentially together with a proposed RN subframe configuration (including FDD/TDD sub-frame configuration and R-PDCCH configuration) on these CCs.
  • the RN sends the resource partitioning need also for CCs not yet used on the backhaul fink but that are configured on the backhaul link such that when the DeNB activates them, it already knows whether it has to apply resource partitioning or not on these CCs.
  • a resource partitioning update is necessary, so that the RN may release the CC first, then informs the change to its DeNB by the MAC message or wait for the acceptance or rejection from DeNB depending on the implemented variant (see exemplary embodiment 1).
  • the DeNB Upon reception of the MAC message (S 82 ) to indicate the activation/deactivation of one or more CCs on the access link (that corresponds to inform a changed resource partitioning request) and optionally the proposed FDD/TDD sub-frame configuration, the DeNB replies to the RN with a message to confirm, reject or modify the change or simply with an acknowledge message, S 84 (dependent on the implemented variant). DeNB forwards to its RRC layer the info on CC change and/or updated resource partitioning request of related CCs and/or proposed FDD/TDD sub-frame configuration. The DeNB initiates a RRC process to provide RN subframe configuration info (including FDD/TDD subframe configuration and R-PDCCH configuration) of related CCs to the RN, S 85 .
  • RN subframe configuration info including FDD/TDD subframe configuration and R-PDCCH configuration
  • DeNB decides to release the RN sub-frame configuration applied on the corresponding CCs of backhaul link immediately upon receiving the MAC message, S 83 .
  • the release is done (S 87 a , S 87 b ) when the DeNB receives the confirmation (S 86 ) that the updated RN subframe configurations have been received at the RN.
  • the response can be included in message S 85 (as is FIG. 8 ) or in message S 84
  • the RN Upon reception of the response message (MAC message and/or RRC configuration message) from DeNB, S 84 , S 85 , the RN initiates the PCell or SCell change on its access link and applies the updated RN subframe configurations, S 87 a.
  • the response message MAC message and/or RRC configuration message
  • FIGS. 9 to 10 ( FIGS. 9 to 10 )
  • the DeNB (instead of RN) detects one or more CC change on the backhaul link that occurred or is necessary to occur in terms of the component carriers used and RN subframe configurations need to be updated accordingly. Then, the DeNB issues a change request for resource partitioning (from not necessary to necessary or vice versa). A change is detected/signaled per CC depending on the activation or deactivation of the CC on the backhaul link.
  • the DeNB issues a RRC Connection reconfiguration message, S 91 , towards the RN.
  • the RN informs, S 92 , its updated resource partitioning request info, to the DeNB by a RRC message, such as RRC Connection Reconfiguration Complete message.
  • RRC message such as RRC Connection Reconfiguration Complete message.
  • Other information can also be included in the message, like antenna isolation capability on the concerned CC, activation/deactivation status of related CCs, etc.
  • the RN could release the resource partitioning that was applied on the CC autonomously, if there is any.
  • the DeNB Based on the updated capability information related to the concerned CC received from the RN, the DeNB initiates a RN Reconfiguration process, S 93 , to provide updated configuration info, such as RN subframe configuration of the concerned CC, on per CC basis to the RN. Acknowledgement will be sent in a message, S 94 .
  • the configured RN subframe info will be applied either immediately after receiving the reconfiguration message S 93 (as expressed by the dotted box labeled S 96 a ) or after receiving a related MAC CE activating/deactivating the CC S 95 .
  • S 96 a and S 96 are two options illustrated in the same figure.). This corresponds to configure the subframes used for the backhaul link as MBSFN subframes on the access link.
  • the DeNB upon detection of a change or need for change, intends to activate one or more additional SCells on the backhaul link during RN operation phase, and the RN's requirements on resource partitioning for the concerned CC(s) is unknown. Then, the DeNB initiates UE Capability enquiry process to ask, S 101 , the RN related capability, such as resource partitioning need of concerned CCs, optionally also the preferred FDD/TDD subframe configuration and R-PDCCH configuration on these CCs. antenna isolation capability of concerned CCs, supported CCs on RN access link, etc
  • the RN Upon reception of UE Capability enquiry message in S 101 , the RN replies, in S 102 , to the DeNB with UE Capability Information (or equivalently RN Capability Information) message to inform its related capabilities, such as resource partitioning needs of supported CCs, optionally the preferred FDD/TDD subframe configuration on these CCs, antenna isolation capability of supported CCs, supported CC(s) on RN access link, etc.
  • UE Capability Information or equivalently RN Capability Information
  • the RN sends the resource partitioning need also for CCs not yet used on the backhaul link but that are configured on the backhaul link such that when the DeNB activates them, it already knows whether it has to apply resource partitioning or not on these CCs.
  • the DeNB can configure the new activated SCells on RN backhaul link appropriately, or decide to add/release/modify other CCs based on received RN Capability Information.
  • the proposed method is adopted in the related standard specifications, it is detectable using a protocol analyzer.
  • relay systems can benefit efficiently from enhancements attributable to carrier aggregation applied on the access and backhaul interface of the relay systems.
  • the present invention proposes methods and devices to further improve relay systems operating on the basis of carrier aggregation on the access as well as on the backhaul link.
  • a relay node as a device, comprising a transceiver device, configured to communicate via a first interface with a terminal and via a second interface with a remote network device, wherein communication via the first and/or second interface is configured to operate based on aggregation of plural individual component carriers, and a control device, configured to perform, per component carrier: detection of a change concerning a component carrier on the first interface, sending, responsive thereto, of update information pertaining to at least the first interface towards the remote network device, reception of reconfiguration instructions, implied by the detected change, to be applied on the first interface, and initiation of reconfiguration of the first interface based on the received instructions.
  • Similar approach is applied to a donor eNB as well as to corresponding methods and computer program products.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
US14/356,190 2011-11-04 2011-11-04 Mechanisms addressing dynamic component carrier change in relay systems Active 2032-01-23 US9246662B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/081788 WO2013063792A1 (fr) 2011-11-04 2011-11-04 Mécanismes gérant le changement dynamique de porteuses constitutives dans des systèmes relais

Publications (2)

Publication Number Publication Date
US20140307586A1 US20140307586A1 (en) 2014-10-16
US9246662B2 true US9246662B2 (en) 2016-01-26

Family

ID=48191222

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/356,190 Active 2032-01-23 US9246662B2 (en) 2011-11-04 2011-11-04 Mechanisms addressing dynamic component carrier change in relay systems

Country Status (3)

Country Link
US (1) US9246662B2 (fr)
EP (1) EP2774436B1 (fr)
WO (1) WO2013063792A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150372801A1 (en) * 2014-06-18 2015-12-24 Qualcomm Incorporated Apparatus and method for capability update in wireless communication
US10362525B2 (en) * 2014-09-15 2019-07-23 Intel IP Corporation Apparatus, system and method of relay backhauling with millimeter wave carrier aggregation
US20240007165A1 (en) * 2020-05-29 2024-01-04 Qualcomm Incorporated Channel state reporting for full duplex transmissions

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9191098B2 (en) * 2011-01-14 2015-11-17 Telefonaktiebolaget L M Ericsson (Publ) Capability reporting for relay nodes in wireless networks
WO2013002690A1 (fr) * 2011-06-29 2013-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Attribution de sous-porteuse dans un système de communication sans fil
US10045391B2 (en) 2013-06-28 2018-08-07 Nokia Technologies Oy Methods, apparatuses and computer program products for prose communication
EP3025540A4 (fr) 2013-07-26 2017-03-15 Intel IP Corporation Signalisation d'informations d'interférence pour aider un matériel utilisateur
US20160302115A1 (en) * 2013-12-04 2016-10-13 Telefonaktiebolaget Lm Ericsson (Publ) Backhaul of Client Network Nodes
KR101724232B1 (ko) 2015-05-26 2017-04-06 엘지전자 주식회사 무선 통신 시스템에서 단말에 의해 수행되는 링크 해제 방법 및 상기 방법을 이용하는 단말
US20180234163A1 (en) * 2015-08-13 2018-08-16 Ntt Docomo, Inc. Relay device and relay method
WO2017030483A1 (fr) * 2015-08-14 2017-02-23 Telefonaktiebolaget Lm Ericsson (Publ) Procédés d'exploitation de nœuds de réseau dans un réseau de communication, et nœuds de réseau les mettant en œuvre
GB2543280A (en) * 2015-10-13 2017-04-19 Tcl Communication Ltd Radio access network interworking
US20190021084A1 (en) * 2017-07-12 2019-01-17 Futurewei Technologies, Inc. System And Method For Backhaul and Access In Beamformed Communications Systems
CN111656852B (zh) * 2017-11-30 2023-10-17 诺基亚技术有限公司 用于5g网络中的回程的方法和装置
CN111526543A (zh) * 2019-02-02 2020-08-11 索尼公司 电子设备、通信方法和存储介质
US11910239B1 (en) * 2020-12-18 2024-02-20 Sprint Spectrum Lp Assigning component carriers for relay nodes
CN112954767B (zh) * 2021-03-24 2023-07-18 北京智芯微电子科技有限公司 一种无线通信方法与系统、存储介质、通信装置
CN118104269A (zh) * 2021-10-22 2024-05-28 株式会社Ntt都科摩 无线中继装置以及通信方法

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025340A2 (fr) 2009-08-31 2011-03-03 Lg Electronics Inc. Procédé d'utilisation d'une composante porteuse par une station relais dans un système multiporteuses, et station relais
WO2011051921A2 (fr) 2009-10-30 2011-05-05 Nokia Corporation Communications de liaison optimisées pour système de communication sans fil en paquets avec relais évolué
US20120307715A1 (en) * 2010-02-12 2012-12-06 Mitsubishi Electric Corporation Mobile communication system
US20130142136A1 (en) * 2011-10-21 2013-06-06 Samsung Electronics Co., Ltd. Methods and apparatus for adaptive wireless backhaul and networks
US8755326B2 (en) * 2009-12-10 2014-06-17 Lg Electronics Inc. Repeater apparatus for simultaneously transceiving signals in a wireless communication system, and method for same
US8811268B2 (en) * 2010-01-13 2014-08-19 Pantech Co., Ltd. Apparatus and method for configuring component carrier in wireless communication system
US20140301371A1 (en) * 2011-11-04 2014-10-09 Mitsubishi Electric Corporation Mobile communication system
US8995393B2 (en) * 2011-01-12 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) Methods and network nodes for signalling of complementary assistance data
US9083497B2 (en) * 2011-03-04 2015-07-14 Lg Electronics Inc. Method and device for setting backhaul link subframe in wireless communication system having carrier aggregation technique applied thereto
US9112644B2 (en) * 2009-04-09 2015-08-18 Lg Electronics Inc. Signal transmission method and apparatus in a relay communication system

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9112644B2 (en) * 2009-04-09 2015-08-18 Lg Electronics Inc. Signal transmission method and apparatus in a relay communication system
WO2011025340A2 (fr) 2009-08-31 2011-03-03 Lg Electronics Inc. Procédé d'utilisation d'une composante porteuse par une station relais dans un système multiporteuses, et station relais
WO2011051921A2 (fr) 2009-10-30 2011-05-05 Nokia Corporation Communications de liaison optimisées pour système de communication sans fil en paquets avec relais évolué
US8755326B2 (en) * 2009-12-10 2014-06-17 Lg Electronics Inc. Repeater apparatus for simultaneously transceiving signals in a wireless communication system, and method for same
US8811268B2 (en) * 2010-01-13 2014-08-19 Pantech Co., Ltd. Apparatus and method for configuring component carrier in wireless communication system
US20120307715A1 (en) * 2010-02-12 2012-12-06 Mitsubishi Electric Corporation Mobile communication system
US8995393B2 (en) * 2011-01-12 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) Methods and network nodes for signalling of complementary assistance data
US9083497B2 (en) * 2011-03-04 2015-07-14 Lg Electronics Inc. Method and device for setting backhaul link subframe in wireless communication system having carrier aggregation technique applied thereto
US9130720B2 (en) * 2011-03-04 2015-09-08 Lg Electronics Inc. Method and device for setting backhaul link subframe in wireless communication system having carrier aggregation technique applied thereto
US20130142136A1 (en) * 2011-10-21 2013-06-06 Samsung Electronics Co., Ltd. Methods and apparatus for adaptive wireless backhaul and networks
US20140301371A1 (en) * 2011-11-04 2014-10-09 Mitsubishi Electric Corporation Mobile communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
International Search Report dated Aug. 16, 2012 corresponding to International Patent Application No. PCT/CN2011/081788.
Volker Braun et al., "Relay Networks Specific Resource Management Features", D3.3-v2.0.doc, chapter 3.3.1, May 2, 2011, pp. 1-87.

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150372801A1 (en) * 2014-06-18 2015-12-24 Qualcomm Incorporated Apparatus and method for capability update in wireless communication
US10841070B2 (en) 2014-06-18 2020-11-17 Qualcomm Incorporated Apparatus and method for capability update in wireless communication
US10362525B2 (en) * 2014-09-15 2019-07-23 Intel IP Corporation Apparatus, system and method of relay backhauling with millimeter wave carrier aggregation
US20240007165A1 (en) * 2020-05-29 2024-01-04 Qualcomm Incorporated Channel state reporting for full duplex transmissions
US12224834B2 (en) * 2020-05-29 2025-02-11 Qualcomm Incorporated Channel state reporting for full duplex transmissions

Also Published As

Publication number Publication date
US20140307586A1 (en) 2014-10-16
WO2013063792A1 (fr) 2013-05-10
EP2774436B1 (fr) 2017-01-11
EP2774436A4 (fr) 2015-03-25
EP2774436A1 (fr) 2014-09-10

Similar Documents

Publication Publication Date Title
US9246662B2 (en) Mechanisms addressing dynamic component carrier change in relay systems
US11737001B2 (en) Layer 2 relay user equipment mobility
EP3481135B1 (fr) Procédé et dispositif pour configurer double connectivité
EP3689096B1 (fr) Procédés et dispositifs pour la préservation d'un pdcp nr lors d'une reprise/suspension de rrc
EP3178287B1 (fr) Procédé de désactivation de cellules secondaires pendant une procédure de changement de groupe de cellules secondaires et dispositif s'y rapportant
EP3791679B1 (fr) Protocoles et architectures pour double connectivité nr-nr (nr-dc)
EP2869633B1 (fr) Procédé, système, et dispositif pour exécuter une commutation
EP2878157B1 (fr) Procédé destiné à être utilisé dans la communication de dispositif à dispositif et système de communication sans fil
US11395205B2 (en) Method and apparatus for performing DC based handover
US20180227819A1 (en) Method and apparatus for performing partial handover for continuous data transmission in wireless communication system
US20140301370A1 (en) Wireless telecommunication network
US9179376B2 (en) Relay node handover method, base station, and communication system
US11903058B2 (en) RRC timer for layer 2 UE-to-network relay
US20180027456A1 (en) Base station
CN110169125A (zh) 未来无线电网络中的辅助节点变更信令
WO2012100626A1 (fr) Procédé et dispositif de traitement de ressoures basés sur la commutation de noeuds de relais
CN102763346B (zh) 中继网络中的工作模式切换方法、基站、中继节点及通讯系统
US10708891B2 (en) Method for establishing evolved packet system bearer and base station
CN102811468A (zh) 中继切换安全保护方法、基站及中继系统
CN105491680B (zh) 网络节点
EP3373694B1 (fr) Dispositif de communications et procédé de gestion de communications dans une connectivité double
CN102752820A (zh) 小区切换方法及系统
JP7761768B2 (ja) 通信制御方法
WO2024026132A1 (fr) Gestion d'alignement temporel avec de multiples récepteurs dans un système de communication sans fil
WO2023066230A1 (fr) Procédé et appareil utilisés dans un nœud de communication pour une communication sans fil

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: NOKIA SOLUTIONS AND NETWORKS OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHANG, SHUN LIANG;DU, LEI;REDANA, SIMONE;SIGNING DATES FROM 20151020 TO 20151022;REEL/FRAME:037282/0678

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: NOKIA TECHNOLOGIES OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA SOLUTIONS AND NETWORKS OY;REEL/FRAME:047271/0806

Effective date: 20180702

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8