Field of the Invention
The present invention relates to a wireless communication system and, in particular, to an operation method and apparatus of a high version (Rel-10) terminal in case of existence of MBSFN subframe supporting unicast in the high version (Rel-10) network of Long Term Evolution (LTE) system in which terminals with different versions (Releases 8, 9, 10, etc.) coexist.
Description of the Related Art
With the rapid advance of the wireless communication technology, the communication systems have evolved to the 4th Generation mobile communication system represented by LTE system. In the LTE system, the data is transmitted in unit of frame having a length of 10 msec, a frame consisting of 10 subframes.
In
For unicast data transmission/reception, the resource allocation information indicating the resource allocated for transmission/reception is carried on the Physical Downlink Control Channel (PDCCH) and the real data is carried on the Physical Downlink Shared Channel (PDSCH). The terminal determines whether there is any resource allocation information addressed thereto on the PDCCH before attempt receiving real data.
In this case, the LTE Rel-10 terminal has to check the PDCCH carrying the resource allocation information for the MBSFN subframe in order to receive PDSCH through even the MBSFN subframe. However, if the LTE Rel-10 terminal has to check PDCCH in every MBSFN subframe, this may cause unnecessary operation depending on whether the MBSFN subframe carries terminal-specific unicast data or multicast/broadcast data.
The present disclosure has been made in an effort to address this problem, and it is an object of the present disclosure to provide a method for a terminal to receive data in a situation where different type subframes exist in the wireless communication system including networks operating with different versions of LTE.
In the case that the new version (Rel-10 or later) terminal is in a new version network, the terminal receives information on whether PDSCH reception over MBSFN subframe through broadcast or unicast is supportable from the new version network and, if supportable, takes operation for interpreting PDCCH for receiving PDSCH over MBSFN subframe and, otherwise if not supportable, skips corresponding operation in MBSFN subframe.
In the disclosed method, the new version terminal operating in a new version network reduces unnecessary operation for data reception when unicast data transmission is not supported in the network, depending on whether the network supports unicast data transmission in MBSFN subframe, resulting in reduction of power consumption.
In accordance with an aspect of the present invention, a method by a base station in a wireless communication system is provided. The method includes transmitting, to a terminal, system information including information associated with a sub-frame configuration of multimedia broadcast multicast service single frequency network (MBSFN) sub-frames, identifying whether the transmission mode of the terminal is a first transmission mode or a second transmission mode, transmitting, to the terminal, dedicated message including configuration information of the identified transmission mode of the terminal, transmitting, to the terminal, control information in a physical downlink control channel (PDCCH) and data in a physical downlink shared channel (PDSCH) in a first sub-frame of the MBSFN sub-frames, if the terminal is configured in the first transmission mode, and transmitting, to the terminal, the control information in the PDCCH and the data in the PDSCH in a second sub-frame of a non-MBSFN sub-frames, if the terminal is configured in the second transmission mode.
In accordance with an aspect of the present invention, a base station in a wireless communication system is provided. The base station includes a transceiver and a controller. The transceiver is for transmitting and receiving signals. The controller is configured to control to transmit, to a terminal, system information including information associated with a sub-frame configuration of multimedia broadcast multicast service single frequency network (MBSFN) sub-frame, identify whether the transmission mode of the terminal is a first transmission mode or a second transmission mode, transmit, to the terminal, dedicated message including configuration information of the identified transmission mode of the terminal, transmit, to the terminal, control information in a physical downlink control channel (PDCCH) and data in a physical downlink shared channel (PDSCH) in a first sub-frame of the MBSFN sub-frames, if the terminal is configured in the first transmission mode, and transmit, to the terminal, the control information in the PDCCH and the data in the PDSCH in a second sub-frame of a non-MBSFN sub-frames, if the terminal is configured in the second transmission mode.
In the following, detailed description of well-known functions and structures incorporated herein may be omitted to avoid obscuring the subject matter of the present invention. Exemplary embodiments of the present invention are described with reference to the accompanying drawings in detail.
In the present disclosure, the description is directed to the LTE system for convenience purpose.
There are several releases of LTE and among them the legacy Rel-8 and Rel-9 do not support PDSCH reception in MBSFN subframe. Accordingly, the legacy terminal does not attempt decoding PDCCH for receiving Downlink Control Information (DCI) including PDSCH scheduling information for receiving PDSCH in MBSFN subframe.
In the Rel-10 or later system, however, it is allowed to transmit PDSCH in MBSFN subframe. In this case, unlike the legacy terminal which takes no action for MBSFN subframe because it cannot receive PDSCH in MBSFN subframe, the new terminal has to take an action for receiving PDSCH to acquire DCI including scheduling information for receiving PDSCH in MBSFN subframe. In the following description, new terminal denotes an LTE Rel-10 terminal, i.e. the terminal capable of receiving PDSCH in MBSFN subframes.
The new version terminal receives a downlink frame structure in System Information Block broadcast by a base station at step 203. The downlink frame structure is transmitted in the form of a bitmap indicating positions of MBSFN subframes.
Next, the terminal receives information on whether the base station supports PDSCH over MBSFN subframe at step 205. The PDSCH over MBSFN subframe supportability can be broadcasted in the system information of the base station or transmitted to the individual terminals through respective control messages. The PDSCH over MBSFN subframe supportability information can be transmitted in a Radio Resource Control (RRC) message explicitly with a newly defined indicator or implicitly with a legacy information (e.g. predefined channel configuration information, transmission mode information, etc.). Steps 203 and 250 can be performed in opposite order. In the case of legacy network or legacy base station, the supportability information on PDSCH over MBSFN is not transmitted. If no supportability information on PDSCH over MBSFN is received, the UE assumes that the base station does not support PDSCH of MBSFN.
If it is determined at step 207 that PDSCH over MBSFN subframe is supported, the UE receives PDCCH including DCI, at step 209, for receiving PDSCH in MBSFN subframes based on the information received at step 205.
If it is determined at step 207 that PDSCH over MBSFN subframe is not supported or if no supportability information on PDSCH over MBSFN subframe is received, the terminal takes no action for receiving PDSCH in MBSFN subframe. In this case, the terminal does not perform any operation for receiving PDSCH.
PDSCH can be transmitted to Rel-10 UEs in MBSFN subframes. In this disclosure, it will be discussed that whether there needs any RRC information in order to support that behaviour more efficiently.
PDSCH can be transmitted to Rel-10 UEs in MBSFN subframes. However due to the following reasons, PDSCH may not be transmitted in all or certain MBSFN subframes under the eNB.
- An eNB does not support unicast-data over MBSFN subframes, e.g. Rel8/9 eNBs.
- Certain MBSFN subframes are already used for other purposes such as MBSFN transmission, PRS transmission, etc.
- An eNB scheduler can decide not to use MBSFN subframes for unicast data.
Without the knowledge to distinguish the cases above, the Rel-10 UE needs to monitor PDCCH to detect DL assignment DCI in every MBSFN subframe. This UE behavior would lead unnecessary power consumption of the UE due to additional blind decodes of PDCCHs compared to Rel-8/9. Therefore, it would be good if RRC signaling is used to inform the Rel-10 UE whether this behavior is supported or not in the eNB. If it is signaled as “not support”, then the Rel-10 UE would not perform blind decodes of PDCCHs in order to detect DL assignment DCI in the configured MBSFN subframes. Meanwhile, the Rel-10 UE would perform blind decodes of PDCCHs in order to detect DL assignment DCI in the configured MBSFN subframes only when it is signaled as “support”.
Proposal 1: RRC should inform whether unicast data over MBSFN subframe is supported or not.
Overall procedure:
1-bit information (e.g. Support of unicast over MBSFN subframe) would be included in the system information/UE dedicated message (from the eNB to the cell or the UE).
If the information is TRUE:
The Rel-10 UE will perform additional blind decodes of PDCCHs in order to detect DL assignment DCI in every MBSFN subframe (in addition to UL assignment DCI).
Meanwhile if the information is FALSE:
The Rel-10 UE does not need to perform additional blind decodes of PDCCHs in order to detect DL assignment DCI in any MBSFN subframe. (The Rel-10 UE will follow the Rel-8/9 UE behavior, i.e. do blind decodes of PDCCH only to detect UL assignment DCI in all MBSFN subframe).
However, the above proposal mainly solves the case i) only. If unicast data over MBSFN subframe is supported, e.g. Rel10 eNB, the Rel-10 UE should do additional blind decodes of PDCCHs over all MBSFN subframes although only some MBSFN subframes are used for actual unicast-data due to ii) or iii) reasons. Thus, it may be better to signal which MBSFN subframes are actually used for unicast data. Then the Rel-10 UE will only do additional blind decodes of PDCCHs over the indicated MBSFN subframes. However, it is also true it would increase the size of the information.
Proposal 2: RRC should inform which MBSFN subframes are used for unicast data.
Overall procedure:
Following information (e.g. MBSFN-SubframeConfigList-PDSCH-r10) would be included in the system information/UE dedicated message (from the eNB to the cell or the UE).
MBSFN-SubframeConfigList-PDSCH-r10 ::=SEQUENCE 55
}
The UE behavior:
Check the MBSFN-SubframeConfiglndex value and the corresponding radioframeAllocationPeriod, radioframeAllocationOffset, and subframeAllocation. MBSFN-SubframeConfiglndex information is to know MBSFN subframe configuration, i.e. which subframe is configured for MBSFN-subframe.
Then check the subframeAllocation-PDSCH. The bit order is same as subframeAllocation in MBSFN-SubframeConfig. If it is “1”, this means corresponding MBSFN subframe can be used for PDSCH transmission. So, the Rel-10 UE will perform additional blind decodes of PDCCHs in order to detect DL assignment DCI in this MBSFN subframe (in addition to UL assignment DCI). If it is “0”, this means corresponding MBSFN subframe is not be used for PDSCH transmission. So, the Rel-10 UE will follow the Rel-8/9 UE behavior, i.e. do blind decodes of PDCCH only to detect UL assignment DCI, in this MBSFN subframe.
This information can be signaled either by system information or UE dedicated message. Considering the following aspects, we assume it is more reasonable to send this information by system information.
MBSFN subframe configuration information is broadcasted by system information.
Rel-10 UEs would use CSI-RS in MBSFN subframe where PDSCH is transmitted and RANI has agreed CSI-RS configuration information is cell specific so it would be broadcasted by system information.
Proposal 3: This information is signaled by system information.
Possible extensions:
In this document, we have divided 2 level of blind decodes (i.e. blind decodes for DL assignment in addition to UL assignment or blind decodes only for UL assignment) to be performed dependent on the signaling.
However, we can extend it into multiple levels of blind decodes for future use.
For example, group A of blind decodes, group B of blind decodes, and group C of blind decodes. In the case, the signaling should be extended to inform whether group A of blind decodes in certain subframes (e.g. MBSFN subframes) is supported/which subframe is actually used for group A blind decodes, or group B of blind decodes in certain subframes (e.g. MBSFN subframes) is supported/which subframe is actually used for group B blind decodes, or group C of blind decodes in certain subframes (e.g. MBSFN subframes) is supported/which subframe is actually used for group C blind decodes. Then the UE would do the corresponding blind decodes in the indicated subframes
The terminal communicates data with higher layer 305 and transmits/receives control messages through a control message processor 207. The terminal multiplexes the control signals or data by means of the multiplexer/demultiplexer 303 and transmits the multiplex result by means of the transceiver 301 under the control of the controller 309. The terminal demultiplexes the physical signal received by the transceiver 301, by means of the multiplexer/demultiplexer 303, and transfers the demultiplexed signals to the higher layer 305 or control message processor 307 under the control of the controller 309.
In the present disclosure, the terminal receives MBSFN subframe configuration information broadcasted by the base station and receives the supportability information on PDSCH over MBSFN subframe through broadcast or unicast. Such a control message is received, the control message processor 307 transfers to the controller 309 the information on whether each subframe is normal or MBSFN subframe and whether PDSCH over MBSFN subframe is supported in order to determine whether to receive PDCCH for receiving PDSCH at every subframe. That is, if PDSCH over MBSFN subframe is supported, the terminal performs operation for receiving PDSCH even in MBSFN subframes and, otherwise PDSCH over MBSFN subframe is not supported, performs no action for receiving PDSCH in MBSFN subframes.
Although the block diagram of the terminal is directed to the case where the function blocks are responsible for different functions, the present invention is not limited thereto. For example, the controller 309 may perform the functions of the control message processor 307.
In the disclosed method, the network notifies the new version terminal whether it supports PDSCH over MBSFN subframe so as to avoid unnecessary reception operation for receiving PDSCH over MBSFN subframe, resulting in reduction of power consumption.
Although exemplary embodiments of the present invention have been described in detail hereinabove with specific terminology, this is for the purpose of describing particular embodiments only and not intended to be limiting of the invention. While particular embodiments of the present invention have been illustrated and described, it would be obvious to those skilled in the art that various other changes and modifications can be made without departing from the spirit and scope of the invention.
This is a continuation application of a prior application Ser. No. 15/404,971, filed Jan. 12, 2017; which is a continuation of U.S. patent application Ser. No. 14/877,575, filed Oct. 7, 2015; which is a continuation of U.S. patent application Ser. No. 14/660,152, filed Mar. 17, 2015, which issued as U.S. Pat. No. 9,420,585 on Aug. 16, 2016; which is a continuation of U.S. patent application Ser. No. 14/610,421, filed Jan. 30, 2015, which issued as U.S. Pat. No. 9,426,805 on Aug. 23, 2016; which is a continuation of U.S. patent application Ser. No. 13/884,185, filed on May 8, 2013, which issued as U.S. Pat. No. 9,432,992 on Aug. 30, 2016; which claimed the benefit under 35 U.S.C. § 371 of an International application filed on Nov. 8, 2011, and assigned application number PCT/KR2011/008458; which claimed the benefit of a U.S. Provisional application filed on Nov. 8, 2010, in the U.S. Patent and Trademark Office and assigned Ser. No. 61/411,115; and is related to U.S. patent application Ser. No. 14/877,628, filed Oct. 7, 2015, which issued as U.S. Pat. No. 9,456,445 on Sep. 27, 2016, and is related to U.S. patent application Ser. No. 14/877,492, filed Oct. 7, 2015, which issued as U.S. Pat. No. 9,462,584 on Oct. 4, 2016, the entire disclosures of which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
9185683 | Lee, II | Nov 2015 | B2 |
9215054 | Han | Dec 2015 | B2 |
9510323 | Lee, II | Nov 2016 | B2 |
20040180675 | Choi et al. | Sep 2004 | A1 |
20060268774 | Kangas et al. | Nov 2006 | A1 |
20070086437 | Difazio et al. | Apr 2007 | A1 |
20090252077 | Khandekar et al. | Oct 2009 | A1 |
20090323957 | Luo | Dec 2009 | A1 |
20100009687 | Koivisto et al. | Jan 2010 | A1 |
20100172311 | Agrawal et al. | Jul 2010 | A1 |
20100189027 | Ishida et al. | Jul 2010 | A1 |
20100195622 | Buchmayer et al. | Aug 2010 | A1 |
20100232346 | Yu et al. | Sep 2010 | A1 |
20100232546 | Yu et al. | Sep 2010 | A1 |
20100238845 | Love et al. | Sep 2010 | A1 |
20100265870 | Cai et al. | Oct 2010 | A1 |
20100273506 | Stern-Berkowitz | Oct 2010 | A1 |
20100285792 | Chen et al. | Nov 2010 | A1 |
20100303013 | Khandekar et al. | Dec 2010 | A1 |
20100322135 | Van Lieshout et al. | Dec 2010 | A1 |
20100323684 | Cai et al. | Dec 2010 | A1 |
20100329171 | Kuo et al. | Dec 2010 | A1 |
20100330992 | Bhattacharjee | Dec 2010 | A1 |
20110013574 | Hsu | Jan 2011 | A1 |
20110053490 | Wu | Mar 2011 | A1 |
20110081854 | Kuo et al. | Apr 2011 | A1 |
20110103291 | Wiberg et al. | May 2011 | A1 |
20110110316 | Chen et al. | May 2011 | A1 |
20110111781 | Chen | May 2011 | A1 |
20110141987 | Nam et al. | Jun 2011 | A1 |
20110170496 | Fong et al. | Jul 2011 | A1 |
20110194477 | Damnjanovic et al. | Aug 2011 | A1 |
20110194478 | Lee et al. | Aug 2011 | A1 |
20110200137 | Han et al. | Aug 2011 | A1 |
20110235584 | Chen et al. | Sep 2011 | A1 |
20110243056 | Jen | Oct 2011 | A1 |
20110267997 | Seo et al. | Nov 2011 | A1 |
20110273994 | Lin | Nov 2011 | A1 |
20110275363 | Kwon et al. | Nov 2011 | A1 |
20110299449 | Kwon et al. | Dec 2011 | A1 |
20120014286 | Wang et al. | Jan 2012 | A1 |
20120033650 | Ahn | Feb 2012 | A1 |
20120039292 | Lee et al. | Feb 2012 | A1 |
20120082119 | Chung et al. | Apr 2012 | A1 |
20120093051 | Xu | Apr 2012 | A1 |
20120099536 | Lee et al. | Apr 2012 | A1 |
20120122472 | Krishnamurthy | May 2012 | A1 |
20120207084 | Seo et al. | Aug 2012 | A1 |
20120213137 | Jeong et al. | Aug 2012 | A1 |
20130039284 | Marinier et al. | Feb 2013 | A1 |
20130044664 | Nory et al. | Feb 2013 | A1 |
20130083736 | Yin et al. | Apr 2013 | A1 |
20130094411 | Zhang | Apr 2013 | A1 |
20130121216 | Chen et al. | May 2013 | A1 |
20130242973 | Bertrand et al. | Sep 2013 | A1 |
20150189622 | Jang et al. | Jul 2015 | A1 |
20170163433 | Luo | Jun 2017 | A1 |
Number | Date | Country |
---|---|---|
101577858 | Nov 2009 | CN |
101848420 | Sep 2010 | CN |
102036171 | Apr 2011 | CN |
6306104 | Apr 2018 | JP |
2009-133444 | Nov 2009 | WO |
2010-082752 | Jul 2010 | WO |
2010-121194 | Oct 2010 | WO |
2010-124431 | Nov 2010 | WO |
2010-127300 | Nov 2010 | WO |
Entry |
---|
Panasonic, “Transmission mode and RS types supported in Un link”, 3GPP TSG RAN WG1 Meeting #64 R1-110776 Taipei, Taiwan, Feb. 21-25, 2011. |
Dahlman, Erik et al. 3G Evolution: LTE for Mobile Broadband. Elsevier Korea L.L.C., Translated Edition ISBN 9788972838630, Apr. 10, 2010. See section 11.7. |
3GPP, ‘3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Relaease 9).’ 3GPP TS 36.213 V9.2.0, Jun. 2010. (Retrieved from the Internet on May 17, 2012: < URL: http://www.3gpp.org/ftp/Specs/html-info/36213.htm >) See section 7. |
Samsung, Independent configuration of Rel-10 features, R1-105411, 3GPP, Oct. 5, 2010. |
Samsung, Issues on DL RS Design for Higher Order MIMO, R1-084169, 3GPP, Nov. 4, 2008. |
NEC Group, Search space design and RE mapping for the Non-interleaved R-PDCCH transmission with CRS and DMRS, R1-104534, 3GPP, Aug. 17, 2010. |
LG Electronics Inc., Remaining Issues for PDSCH Starting Point Indication with Cross-Carrier Scheduling, R1-103954, 3GPP, Jun. 23, 2010. |
Huawei et al: “Unicast transmission in MBSFN sub frames”, 3GPP Draft; R1-093826 Unicast Transmission in MBSFN Subframes, 3rd Generation Partnership Project(3GPP), Mobile Competence Centre; 650, Route Des Lucioles; F-06921 Sophia-Antipolis Cedex; France, no. Miyazaki; Oct. 12, 2009, Oct. 12, 2009, XP050388336. |
Samsung, Reception of unicast data over MBSFN subframes, 3GPP TSG-RAN WG2#72 R2-106590, Nov. 15-19, 2010. |
Qualcomm Incorporated, Remaining details of PCFICH with cross-carrier scheduling, 3GPP TSG-RAN WG1#61b R1-103530, Jun. 28-Jul. 2, 2010. |
CMCC, ZTE, ETRI, Further discussion on deployment of both relay and MBMS, 3GPP TSG-RAN WG2:♯71bis R2-105677, Oct. 11-15, 2010. |
Nokia Siemens Networks, Nokia, Further Aspects of Control Channel for Relay Backhaul link, 3GPP TSG-RAN WG1#57b R1-092565, 3GPP, Los Angeles, U.S., Jun. 29, 2009. |
Japanese Office Action dated Sep. 3, 2018, issued in Japanese Patent Application No. 2017-232438. |
Ericsson, R1-080621, Physical-layer parameters to be configured by RRC, 3GPP TSG RAN WG2 #61, 2008.02.0. |
Korean Office Action dated Dec. 18, 2018, issued in Korean Patent Application No. 10-2013-7008650. |
CMCC, R1-091831, Considerations on eNB-to-Relay backhaul design, 3GPP TSG RAN WG1 #57, Apr. 28, 2009. |
Nortel, R1-091384, Discussion paper on the control channel and data channel optimization for relay link, 3GPP TSG RAN WG1 #56bis, Mar. 17, 2009. |
Korean Office Action dated Apr. 12, 2019, issued in Korean Patent Application No. 10-2019-7002246. |
Number | Date | Country | |
---|---|---|---|
20180146477 A1 | May 2018 | US |
Number | Date | Country | |
---|---|---|---|
61411115 | Nov 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15404971 | Jan 2017 | US |
Child | 15873608 | US | |
Parent | 14877575 | Oct 2015 | US |
Child | 15404971 | US | |
Parent | 14660152 | Mar 2015 | US |
Child | 14877575 | US | |
Parent | 14610421 | Jan 2015 | US |
Child | 14660152 | US | |
Parent | 13884185 | US | |
Child | 14610421 | US |