Method and apparatus of receiving different types of subframes in mobile communication system

Abstract

A method and base station in a wireless communication system are 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.

Claims

1. A method by a terminal in a wireless communication system, the method comprising: receiving, at the terminal, system information including information associated with a sub-frame configuration of a multimedia broadcast multicast service single frequency network (MBSFN) sub-frame; receiving, at the terminal, a dedicated message including information to be used for identifying whether to detect a physical downlink control channel (PDCCH) in a sub-frame of an MBSFN sub-frame for decoding a physical downlink shared channel (PDSCH) in the sub-frame of the MBSFN sub-frame; determining whether to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame based on the information; identifying whether the sub-frame of the MBSFN sub-frame is used for an MBSFN transmission or a positioning reference signal transmission; in case that the terminal determines to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame, performing detection of the PDCCH in the sub-frame of the MBSFN sub-frame except that the sub-frame is used for the MBSFN transmission or the positioning reference signal transmission; and in case that the terminal determines not to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame, not performing detection of the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH.

2. The method of claim 1, further comprising: in case that the terminal determines to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame, decoding the PDSCH in the sub-frame of the MBSFN sub-frame.

3. The method of claim 1, further comprising: receiving downlink control information including PDSCH scheduling information for receiving the PDSCH in the sub-frame of the MBSFN sub-frame based on detection of the PDCCH in the sub-frame of the MBSFN sub-frame.

4. The method of claim 1, wherein the dedicated message is included in a radio resource control (RRC) message.

5. The method of claim 1, wherein the terminal supports receiving the PDSCH in the sub-frame of the MBSFN sub-frame, in case that the terminal determines to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MB SFN sub-frame.

6. The method of claim 1, wherein a Rel-10 version allows to transmit the PDSCH in the sub-frame of the MBSFN sub-fame.

7. A terminal in a wireless communication system, the terminal comprising: a transceiver for transmitting and receiving signals; and a controller configured to: receive, via the transceiver, system information including information associated with a sub-frame configuration of a multimedia broadcast multicast service single frequency network (MBSFN) sub-frame, receive, via the transceiver, a dedicated message including information to be used for identifying whether to detect a physical downlink control channel (PDCCH) in a sub-frame of an MBSFN sub-frame for decoding a physical downlink shared channel (PDSCH) in the sub-frame of the MBSFN sub-frame, determine whether to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame based on the information, identify whether the sub-frame of the MBSFN sub-frame is used for an MBSFN transmission or a positioning reference signal transmission, in case that the controller determines to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame, perform detection of the PDCCH in the sub-frame of the MBSFN sub-frame except that the sub-frame is used for the MBSFN transmission or the positioning reference signal transmission, and in case that the controller determines not to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame, not perform detection of the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH.

8. The terminal of claim 7, wherein the transceiver is further configured to decode the PDSCH in the sub-frame of the MBSFN sub-frame in case that the controller determines to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame.

9. The terminal of claim 7, wherein the controller is further configured to: receive downlink control information including PDSCH scheduling information for receiving the PDSCH in the sub-frame of the MBSFN sub-frame based on detection of the PDCCH in the sub-frame of the MBSFN sub-frame.

10. The terminal of claim 7, wherein the dedicated message is included in a radio resource control (RRC) message.

11. The terminal of claim 7, wherein the terminal supports receiving the PDSCH in the sub-frame of the MBSFN sub-frame, in case that the controller determines to detect the PDCCH in the sub-frame of the MBSFN sub-frame for decoding the PDSCH in the sub-frame of the MBSFN sub-frame.

12. The terminal of claim 7, wherein a Rel-10 version allows to transmit the PDSCH in the sub-frame of the MBSFN sub-fame.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a diagram illustrating a structure of a downlink frame used in the LTE system;

(2) FIG. 2 is a flowchart illustrating the new terminal procedure in the method according to an embodiment of the present invention; and

(3) FIG. 3 is a block diagram illustrating the configuration of the terminal according to an embodiment of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

(4) 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.

(5) In the present disclosure, the description is directed to the LTE system for convenience purpose.

(6) 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.

(7) 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.

(8) FIG. 2 is a flowchart illustrating the new terminal procedure in the method according to an embodiment of the present invention.

(9) 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.

(10) 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.

(11) 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.

(12) 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.

(13) 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.

(14) 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.

(15) - An eNB does not support unicast-data over MBSFN subframes, e.g. Rel8/9 eNBs.

(16) - Certain MBSFN subframes are already used for other purposes such as MBSFN transmission, PRS transmission, etc.

(17) - An eNB scheduler can decide not to use MBSFN subframes for unicast data.

(18) 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.

(19) Proposal 1: RRC should inform whether unicast data over MBSFN subframe is supported or not.

(20) Overall procedure:

(21) 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).

(22) If the information is TRUE:

(23) 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).

(24) Meanwhile if the information is FALSE:

(25) 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).

(26) 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.

(27) Proposal 2: RRC should inform which MBSFN subframes are used for unicast data.

(28) Overall procedure:

(29) 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).

(30) MBSFN-SubframeConfigList-PDSCH-r10 ::=SEQUENCE 55 MBSFN-SubframeConfigIndex INTEGER (0. . . n) subframeAllocation-PDSCH BIT STRING (0..m)

(31) }

(32) The UE behavior:

(33) 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.

(34) 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.

(35) 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.

(36) MBSFN subframe configuration information is broadcasted by system information.

(37) 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.

(38) Proposal 3: This information is signaled by system information.

(39) Possible extensions:

(40) 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.

(41) However, we can extend it into multiple levels of blind decodes for future use.

(42) 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

(43) FIG. 3 is a block diagram illustrating the configuration of the terminal according to an embodiment of the present invention.

(44) 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.

(45) 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.

(46) 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.

(47) 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.

(48) 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.