WO2014000174A1 - Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante - Google Patents

Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante Download PDF

Info

Publication number
WO2014000174A1
WO2014000174A1 PCT/CN2012/077605 CN2012077605W WO2014000174A1 WO 2014000174 A1 WO2014000174 A1 WO 2014000174A1 CN 2012077605 W CN2012077605 W CN 2012077605W WO 2014000174 A1 WO2014000174 A1 WO 2014000174A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
common
control signaling
subframes
dedicated
Prior art date
Application number
PCT/CN2012/077605
Other languages
English (en)
Inventor
Na WEI
Wei Bai
Jing HAN
Chunyan Gao
Haiming Wang
Shuang TAN
Original Assignee
Renesas Mobile Corporation
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 Renesas Mobile Corporation filed Critical Renesas Mobile Corporation
Priority to PCT/CN2012/077605 priority Critical patent/WO2014000174A1/fr
Publication of WO2014000174A1 publication Critical patent/WO2014000174A1/fr

Links

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/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • the present invention relates to control signaling approaches for terminals with reduced downlink bandwidth. More specifically, the present invention relates to measures (including methods, apparatuses and computer program products) for realizing control signaling approaches for terminals with reduced downlink bandwidth, such as for example machine type communication terminals for (third or fourth generation) wireless communication systems.
  • machine-type communication constitutes a recent trend as well as a market likely to continue expanding in the future.
  • MTC machine-type communication
  • RAT radio access technologies
  • the reduction on downlink bandwidth is considered to be one important factor on reducing the cost and thus improving the competitiveness for MTC devices in third or fourth generation systems such as LTE networks. Accordingly, it is currently agreed on downlink bandwidth reduction for MTC devices, which could be realized by way of (i) reduced bandwidth for both RF and baseband, or (H) reduced bandwidth for baseband only for both data channel and control channels, or (iii) reduced bandwidth for data channel in baseband only while the control channels are still allowed to use the (entire) carrier bandwidth.
  • option (i) might have less chance to be adopted because reducing the bandwidth for RF may not help very much on the cost reduction but will cause too much specification complexity.
  • option (ii) and (iii) the situation would be that a terminal could freely switch its RF to anywhere within the (entire) carrier bandwidth, but could only receive a restricted bandwidth and send to baseband to process it.
  • option (iii) currently appears to be favored, since this will not introduce significant impact on a downlink control channel, but can achieve most of the cost reduction. If the reduced bandwidth is fixed (for example in the center of the carrier bandwidth), such option for bandwidth reduction seems feasible, but the MTC UE could only be scheduled in that center bandwidth range and it will likely generate overload there while plenty of other parts of the carrier bandwidth may be not usable for MTC devices.
  • a natural way for implementation of downlink bandwidth reduction is to configure the MTC deice to use different narrow sub-bands over the frequency to distribute the load of the whole carrier (for example semi- statically).
  • the configured sub-bands can consist of continuous or distributed physical resource blocks (PRB) depending on which bandwidth reduction option is adopted.
  • PRB physical resource blocks
  • MTC devices may not be able to receive them simultaneously. This is specifically problematic for terminals such as MTC devices with narrow reception band which might be configured to off-center resource chunks for load balance purposes.
  • a method comprising monitoring at least one common resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from a network equipment, and monitoring at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated downlink data from the network equipment according to the common control signaling from the network equipment.
  • a method comprising scheduling common control signaling for at least one terminal in at least one common resource chunk in a first sub- band of a downlink carrier bandwidth, and scheduling dedicated downlink data for said at least one terminal in at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling
  • a method comprising monitoring at least one resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from a network equipment, signaling a terminal-specific downlink bandwidth indication to the network equipment, and monitoring at least one resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated control signaling from the network equipment according to the common control signaling from the network equipment and the terminal-specific downlink bandwidth indication
  • a method comprising scheduling common control signaling for at least one terminal in at least one resource chunk in a first sub-band of a downlink carrier bandwidth, and scheduling dedicated downlink data for said at least one terminal in at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth according to
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform : monitoring at least one common resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from a network equipment, and monitoring at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated downlink data from the network equipment according to the common control signaling from the network equipment,
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform: scheduling common control signaling for at least one terminal in at least one common resource chunk in a first sub-band of a downlink carrier bandwidth, and scheduling dedicated downlink data for said at least one terminal in at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform: monitoring at least one resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from a network equipment, signaling a terminal-specific downlink bandwidth indication to the network equipment, and monitoring at least one resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated control signaling from the network equipment according to the common control signaling from the network equipment and the terminal-specific downlink bandwidth indication.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform : scheduling common control signaling for at least one terminal in at least one resource chunk in a first sub-band of a downlink carrier bandwidth, detecting a terminal-specific downlink bandwidth indication from said at least one terminal, and scheduling dedicated control signaling for the at least one terminal in at least one resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling and the terminal-specific downlink bandwidth indication.
  • a computer program product comprising a set of instructions (e.g. computer-executable computer program code) which, when executed on an apparatus or a computer of an apparatus (e.g. an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present invention), is arranged/configured to cause the computer or apparatus to carry out the method according to any one of the aforementioned method-related exemplary aspects of the present invention.
  • a set of instructions e.g. computer-executable computer program code
  • Such computer program product may comprise or be embodied as a (tangible) computer-readable (storage) medium or the like on which the computer-executable computer program code is stored, and/or the program may be directly loadable into an internal memory of the computer or a processor thereof.
  • control signaling approaches for terminals with reduced downlink bandwidth such as for example machine type communication terminals for third or fourth generation communication systems.
  • enhancements are achieved by methods, apparatuses and computer program products enabling control signaling approaches for terminals with reduced downlink bandwidth, such as for example machine type communication terminals for third or fourth generation communication systems.
  • Figure 1 shows a schematic diagram illustrating an exemplary situation of the reception of common control signaling and terminal-dedicated downlink data in different resource chunks, for which exemplary embodiments of the present invention are applicable,
  • Figure 2 shows a schematic diagram illustrating a first example of a procedure according to exemplary embodiments of the present invention
  • Figure 3 shows a schematic diagram illustrating a second example of a procedure according to exemplary embodiments of the present invention
  • Figure 4 shows a schematic diagram illustrating a third example of a procedure according to exemplary embodiments of the present invention
  • Figure 5 shows a schematic diagram illustrating a fourth example of a procedure according to exemplary embodiments of the present invention.
  • Figure 6 shows a schematic block diagram illustrating exemplary apparatuses according to exemplary embodiments of the present invention.
  • a LTE/LTE-Advanced communication system is used as a non-limiting example for the applicability of thus described exemplary embodiments.
  • the description of exemplary embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the invention in any way. Rather, any other network configuration or system deployment, etc. may also be utilized as long as compliant with the features described herein.
  • the present invention and its embodiments may be applicable in any fixed or mobile communication system and/or network deployment with terminals having reduced downlink bandwidth, especially when being configurable to off-center resource chunks.
  • exemplary embodiments of the present invention in general terms, there are provided mechanisms, measures and means for enabling control signaling approaches for terminals with reduced downlink bandwidth, such as for example machine type communication terminals for (third or fourth generation) wireless communication systems.
  • the system bandwidth of one operating carrier is divided into several sub-bands, which can be overlap or non-overlapped.
  • the sub-bands are predefined, or the sub-band division rule is predefined.
  • the sub-band division can be cell-specific or UE-specific, e.g. for different UE category/capability the sub-band size can be different.
  • the PRBs within the same sub-band can be distributed or localized in the frequency domain.
  • any terminal can be configured to use the whole band of the carrier or to be restricted to one or multiple sub-bands.
  • the sub-band to use can be derived implicitly or explicitly.
  • an index of the sub-band may be a function of the terminal identifier, subframe number, number of allocated sub-bands, etc., or a bitmap from a higher layer may be used to indicate the sub-band(s) for a given terminal.
  • Figure 1 shows a schematic diagram illustrating an exemplary situation of the reception of common control signaling and terminal-dedicated downlink data in different resource chunks, for which exemplary embodiments of the present invention are applicable.
  • the time domain is plotted in the horizontal direction
  • the frequency domain is plotted in the vertical direction.
  • the blocks within the illustrated resource chunks are to represent physical resource blocks (PRB), while the arrows are to illustrate a switching between different downlink frequency ranges for reception tuning at a terminal, respectively.
  • PRB physical resource blocks
  • Figure 1 illustrates a problematic situation in which, assuming that the MTC device UE can only receive PRBs on one resource chunk (in a carrier bandwidth or sub-band of e.g. 20 MHz) at a time, the common control signaling (namely, SIB in the present example) and UE-dedicated downlink data are not transmitted on the same resource chunk, which is why the UE is not able to receive them simultaneously.
  • the common control signaling namely, SIB in the present example
  • UE-dedicated downlink data are not transmitted on the same resource chunk, which is why the UE is not able to receive them simultaneously.
  • a given UE is assumed to have assigned a dedicated resource chunk out of resource chinks #1, #2, #4 and #5, while all UEs are assumed to have assigned a common resource chunk, namely resource chunk #3.
  • SI system information
  • the MTC UE When system information (SI) representing a non-limiting example of common control signaling changes, the MTC UE is paged about this SI change, and all MTC UEs which are semi-statically configured to use different bandwidth resource chunks for receiving dedicated downlink data (e.g. on the PDSCH) will need to get to the common bandwidth resource chunk for receiving common control signaling (e.g. on the PDCCH), e.g. the center bandwidth for updated SIB reception. After successfully receiving the updated SIBs, the MTC UEs may get back to the originally configured PDSCH resource chunk for data reception, respectively.
  • SI system information
  • any MTC UE will go automatically back to the common (e.g. center) resource chunk upon paging, triggering, etc., any MTC UE will stay there until common control signaling (i.e. a new configuration, etc. regarding the dedicated (e.g. off-center) resource chunk) is received, and any MTC UE will switch from the common (e.g. center) resource chunk to the dedicated (e.g. off-center) resource chunk upon such receipt of configuration, etc.
  • common control signaling i.e. a new configuration, etc. regarding the dedicated (e.g. off-center) resource chunk
  • the switching gap of any MTC UE in changing the reception resource chunk may be considered, if necessary for implementation, but may (at least in theory as well as for the purpose of the present invention and its embodiments) be assumed to be zero (depending on implementation).
  • the network device transmitting the common control signaling (e.g. an eNB or any other kind of base station or access node) to know when any MTC UE is ready to receive again in its originally configured PDSCH chunk, i.e. to receive again downlink data after being pages for a SIB change, because there are several SIB (re-)transmissions and any MTC UE may successfully receive the SIB in any SIB (re-) transmission, i.e. at different times. Also, it is uncertain for the network device transmitting the common control signaling (e.g. an eNB or any other kind of base station or access node) to know when any MTC UE has actually come to read the SIB, despite being concurrently paged.
  • the common control signaling e.g. an eNB or any other kind of base station or access node
  • the MTC UE prioritizes (reception of) common control signaling over dedicated downlink data and the eNB does not know this, there will happen a loss of information reception for the UE-dedicated downlink transmission.
  • the eNB may not be able to know, if a discontinuous transmission (DTX) of a MTC terminal on the PUCCH is due to the missing of the PDCCH or a PUCCH error, or a resource chunk switch.
  • DTX discontinuous transmission
  • such ambiguity is addressed by ensuring that both the narrow-band terminal and the network device have a corresponding understanding about the resource chunk which is monitored by the narrow-band terminal at any time, i.e. to which frequency range the narrow-band terminal is tuned for downlink reception purposes at any time.
  • Figure 2 shows a schematic diagram illustrating a first example of a procedure according to exemplary embodiments of the present invention.
  • a corresponding procedure comprises an operation of scheduling common control signaling for at least one terminal in at least one common resource chunk in a first sub-band of a downlink carrier bandwidth, and an operation of scheduling dedicated downlink data for said at least one terminal in at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling.
  • a corresponding procedure comprises an operation of monitoring at least one common resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from the network equipment, and monitoring at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated downlink data from the network equipment according to the common control signaling from the network equipment.
  • the first and second sub-bands could be the same or different sub-bands, wherein different sub-bands could be distinct/separate from each other or overlapping each other.
  • the common control signaling is scheduled/monitored in at least one physical resource block in the at least one common resource chunk, and/or the at least one common resource chunk is a center resource chunk in the center of said sub-band or a non-center resource chunk other than a center resource chunk in the center of said sub-band.
  • FIG. 3 shows a schematic diagram illustrating a second example of a procedure according to exemplary embodiments of the present invention.
  • a corresponding procedure according to exemplary embodiments of the present invention comprises an operation of configuring 7605
  • the respective scheduling/monitoring operations are performed in correspondingly configured subframes.
  • the common control signaling is scheduled/monitored in the common signaling subframes in the at least one common resource chunk
  • the dedicated downlink data is scheduled/monitored in the terminal-specific subframes in the at least one dedicated resource chunk.
  • dedicated downlink data is only scheduled in a terminal-specific chunk in the terminal-specific subframes.
  • the eNB and the MTC UE may agree or cooperate in the configuration of subframes for common control signaling and dedicated downlink data.
  • the common signaling subframes are configured to comprise those subframes, in which common control signaling from the network device is possible for the terminal in question, and the terminal-specific subframes are configured to comprise the/all subframes other than the thus configured common signaling subframes.
  • the common signaling subframes may be defined for all possible subframes which might contain common signaling (i.e. a combination union of paging occasions, all SIB windows, RAR windows, etc, while the UE-specific subframes (USF) may be defined for all subframes other than the CSFs.
  • the common signaling subframes are configured to comprise those subframes, in which common control signaling from the network device is possible for the terminal in question, and which have a specific index with a specific periodicity
  • the terminal-specific subframes are configured to comprise the/all subframes other than the thus configured common signaling subframes.
  • the specific index with the specific periodicity for the common signaling subframes may be configured for a specific terminal or a specific group of terminals.
  • a further configuration on the basis of a specific time domain pattern may be additionally applied by restriction to a certain index of subframes with a certain periodicity.
  • the thus configured common signaling subframes are represented by the intersection of the common signaling subframes (CSF) mentioned above and the time domain pattern (i.e. the pattern represented by the specific index with the specific periodicity) for further restriction.
  • the thus restricted subframes constitute a smaller set as compared with the common signaling subframes (CSF) mentioned above.
  • the common signaling subframes (CSF) mentioned above are subframes of the set ⁇ SF#1-SF#50 ⁇ within 100 total subframes, and the configured time domain pattern denotes the first 5 subframes in every 10 subframes, i.e. ⁇ SF#1-SF#5, SF#11- SF#15, SF#21#25, ...)
  • the restricted subframes are represented by the set SF#1- SF#5, SF #11- SF#15, SF#21- SF#25, SF#31- SF #35, and SF#41- SF#45).
  • Such enhanced restriction is effective for improving the probability or number of UE-specific subframes, i.e. configuring less common signaling subframes, at the cost that the MTC UE might miss some common signaling, if the eNB is not transmitting common control signaling in the restricted subframes.
  • the monitoring operations at the MTC UE may be conducted in one of the following options.
  • the MTC may be in (i.e. tuned to) its assigned dedicated (e.g. off-center) resource chunk for the terminal-specific subframes
  • the MTC UE may be in (i.e. tuned to) the common (e.g. center) resource chunk for the configured common signaling subframes.
  • the monitoring of the common control signaling may be terminated and a current resource chunk is switched from the common resource chunk to the dedicated resource chunk at the end of a common signaling subframe.
  • the MTC may be in (i.e. tuned to) its assigned dedicated (e.g. off-center) resource chunk for the terminal-specific subframes
  • the MTC UE may be in (i.e. tuned to) the common (e.g. center) resource chunk or the terminal-specific subframes for the configured common signaling subframes.
  • a current resource chunk is switched from the common resource chunk to the dedicated resource chunk depending on the terminal's needs in terms of detection (receipt) of common control signal, i.e. the MTC UE may stay in the common signaling subframe as long as no common signaling is detected/received.
  • the monitoring of the common control signaling may be terminated and a current resource chunk is switched from the common resource chunk to the dedicated resource chunk upon (correct/successful) detection (or receipt) of common control signaling in the common resource chunk.
  • a discontinuous reception (DRX) operation is applied for common control signaling scheduling/monitoring.
  • such discontinuous reception (DRX) operation may be defined by virtue of a specific PDCCH definition.
  • Such specific PDCCH definition may be such that a PDCCH subframe for a narrow-band terminal should only include the downlink subframe/s and/or the subframe/s include a downlink pilot time slot (DwPTS), among which transmission of dedicated downlink data is expected.
  • the terminal- specific subframes may be configured to comprise physical downlink control channel subframes including downlink subframes and downlink pilot time slot subframes.
  • the PDCCH subframe for a MTC UE may be configured by a network device such as the eNB.
  • a network device such as the eNB.
  • Such configuration is specifically useful for the case that the MTC UE in the common signaling subframes only detects the common search space (CSS).
  • Such case would be in contrast to the common assumption, in which a terminal in common signaling subframes would detect both the common search space (CSS) and the UE-specific search space (USS), while a terminal in terminal-specific subframes would detect only the UE-specific search space (USS).
  • restriction of the terminal to detect only the CSS in the common signaling subframes is effective in terms of reduction in power consumption.
  • such configuration is specifically useful for an uncertain time window in the position (tuning) of the terminal in the case that the terminal could reside in both the common resource chunk and the dedicated resource chunk in the common signaling subframes, as indicated above.
  • this applies when the eNB will not schedule transmission of dedicated downlink data in such uncertain time window.
  • Figure 4 shows a schematic diagram illustrating a third example of a procedure according to exemplary embodiments of the present invention.
  • a corresponding procedure according to exemplary embodiments of the present invention comprises an operation of signaling a common resource chunk indicator from the terminal to the network device upon start or determination of possibility of the monitoring of the common control signaling in the common resource chunk and detecting the same at the network device, and an operation of signaling a dedicated resource chunk indicator from the terminal to the network device upon start or determination of possibility of the monitoring of the dedicated downlink data in the dedicated resource chunk or upon determination of impossibility of decoding detected common control signaling for a predetermined period and detecting the same at the network device.
  • the respective scheduling/monitoring operations are performed accordingly. Namely, the common control signaling is scheduled/monitored upon/after such common resource chunk indicator, and the dedicated downlink data is scheduled/monitored upon/after such common resource chunk indicator.
  • the MTC UE may inform the eNB that it is back in (i.e. tuned to) to the common (e.g. center) resource chunk.
  • This indication may be made by the common resource chunk indicator such as a common band indicator (CBI), which indicates that the terminal starts monitoring or has the possibility of monitoring common control signaling in the common resource chunk.
  • CBI common band indicator
  • the MTC UE may inform the eNB when it leaves the common (e.g. center) resource chunk and is ready to receive in the UE- specific resource chunk.
  • This indication may be made by the dedicated resource chunk indicator such as an UE-specific chunk indicator (USI), which indicates that the terminal starts monitoring or has the possibility of monitoring downlink data in the dedicated resource chunk, or that it is (determined to be) impossible for the terminal to decode detected common control signaling for a predetermined period.
  • USI UE-specific chunk indicator
  • the resource chunk indicator such as the UE-specific chunk indicator (USI) may be defined as an indication from the UE which is not able to successfully decode e.g. SIBs after some certain duration e.g. after start of modification period (e.g. 100ms).
  • the signaling of the resource chunk indicator such as the UE-specific chunk indicator (USI) may be reduced.
  • the signaling of any such assistance indicator e.g. CBI, USI
  • the signaling of the indication e.g. of CBI or USI may be enabled/disabled for each terminal, i.e. on an UE individual basis.
  • signaling of the common resource chunk indicator such as the common band indicator (CBI) and/or signaling of the dedicated resource chunk indicator such as the UE-specific chunk indicator (USI) may be conducted or supported by RRC or MAC or LI signaling .
  • a dynamic indication using terminal- originated assistance information is applied for common control signaling scheduling/monitoring.
  • the MTC UE may send CBI to the eNB after sending the RACH.
  • the eNB/UE may assume CSF for any paging occasion (PO) configured. Yet, it would also be feasible to apply an operation as explained in connection with Figure 3 above.
  • SIB-type common control signaling for each start of a modification period when there is an SI update, the eNB may assume that the MTC UE will go to the common (e.g. center) resource chunk at the start of a new modification period. The MTC UE may send a corresponding indicator to the eNB when it leaves the common (e.g. center) resource chunk and is ready to receive in the dedicated resource chunk.
  • the MTC UE may indicate e.g. CBI or e.g. USI to inform the eNB about its behavior for such occasion.
  • the number of radio frames for a modification period length is equal to modificationPeriodCoeff(2, 4, 8, 16) * defaultPagingCycle(rf 32, rf64, rfl28, rf256).
  • the minimum is 64 radio frames, and the maximum is 4096 radio frames, when system information change and the MTC UE needs to acquire new SIBs.
  • the possible CSFs for MIB are all subframes with SF#0.
  • the possible CSFs for SIBl are all subframes with SF#5.
  • Other SIBs depend on SI window and SI periodicity as follows: Si-Periodicity: ⁇ rf8, rfl6, rf32, rf64, rfl28, rf256, rf512 ⁇ , SI-WindowLength : ⁇ msl, ms2, ms5, mslO, msl5, ms20,ms40 ⁇ ,
  • the worst case could be that all subframes are CSF, while the best case could be that all SIBs (other than SIB1 and MIB) take less than 1% of the subframes acting as CSF. In such extreme case, a newly accessing MTC UE might however have a problem. If taking medium values, it may be assumed that around 15% of the subframes may be needed for the SIBs (other than SIB1 and MIB).
  • FDD's possible CSF may be SF#0, SF#4, SF#5 and SF#9, while TDD's possible CSF may be SF#0, SF#1, SF#5 and SF#6.
  • TDD's possible CSF may be SF#0, SF#1, SF#5 and SF#6.
  • RAR-type common control signaling the RAR's possible CSF may be all subframes after start of the RACH procedure, until the eNB configures a new frequency resource chunk.
  • the USF opportunities are analyzed for the operations according to Figures 3 and 4, i.e. the probability or number of UE-specific subframes as compared with common signaling subframes.
  • the subframe configuration according to Figure 3 with the further (time domain pattern) restriction can further improve the USF opportunity, but only at the cost of MTC UE performance degradation, for example that the MTC UE may miss some SIB message, might take longer to decode all SIBs after SI change as compared with a normal (legacy) UE, etc.
  • the MTC UE needs to tune quite frequently on the common resource chunk (e.g. in the center) or the dedicated resource chunk (e.g. off the center) when USF/CSF is scattered over time. But such operation is quite simple and does not need any signaling. That is, it may be needed to retune the PDSCH reception chunk frequently.
  • any one of these operations according to exemplary embodiments of the present invention is capable of ensuring that both a narrow-band terminal and a network device have a corresponding understanding about the resource chunk which is monitored by the narrowband terminal at any time, i.e. to which frequency range the narrow-band terminal is tuned for downlink reception purposes at any time.
  • the above-mentioned ambiguity in connection with downlink transmission of common control signaling and/or dedicated downlink data is resolved by any one of these operations according to exemplary embodiments of the present invention.
  • a network device such as an eNB or any other kind of base station or access node has to send all transmissions, including both common control signaling and dedicated control signaling, for both MTC UEs and normal (legacy) UEs on the same narrow band resource such as a center resource chunk within a carrier bandwidth or a sub-band thereof.
  • RA random access
  • a corresponding problem could be outlined as follows.
  • all narrow-band MTC UEs need a fixed or pre-defined (narrow-band) frequency resource before accessing a communication network or system and are to be configured to another receive location e.g. for dedicated downlink data for load balance.
  • a MTC UE finds a target cell, it will at least need to read MIB, SIB-1, SIB-2 to camp on the cell.
  • the eNB will need to schedule the SIB- 1/2 on the initial receive location, i.e. the originally configured resource chunk for signaling and data reception, to make sure that the MTC UE could receive it.
  • Both MTC UEs and legacy UEs will do random access on the configured PRACH resource in SIB-2, i.e. on the same resource chunk.
  • the eNB will need to transmit (i.e. to send the messages Msg2 as well as Msg4) on the common initial narrow band (i.e. the originally configured resource chunk) to make sure that all UEs could receive it because the eNB could not know which UE is performing RA procedure in this case.
  • the congestion problem may not be very severe because those are all common control signaling. So, all kinds of terminals will be able to receive and decode such common control signaling, and it is likely that those downlink data/signaling will not be transmitted simultaneously.
  • a PDCCH and a PDSCH will be needed for each UE, respectively.
  • a congestion problem will surely happen because the message Msg4 will need at least one PRB for each UE and the number of MTC UEs is assumed to be large.
  • such problem is addressed by ensuring that the network device is aware of downlink bandwidth characteristics of terminals such as narrow-band terminals.
  • FIG. 5 shows a schematic diagram illustrating a fourth example of a procedure according to exemplary embodiments of the present invention.
  • a corresponding procedure according to exemplary embodiments of the present invention comprises an operation of scheduling common control signaling for at least one terminal in at least one resource chunk in a first sub-band of a downlink carrier bandwidth, an operation of detecting a terminal-specific downlink bandwidth indication from said at least one terminal, and an operation of scheduling dedicated control signaling for the at least one terminal in at least one resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling and the terminal-specific downlink bandwidth indication.
  • a corresponding procedure comprises an operation of monitoring at least one resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from the network equipment, an operation of signaling a terminal-specific downlink bandwidth indication to the network equipment, and an operation of monitoring at least one resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated control signaling from the network equipment according to the common control signaling from the network device and the terminal-specific downlink bandwidth indication.
  • the first and second sub-bands could be the same or different sub-bands, wherein different sub-bands could be distinct/separate from each other or overlapping each other.
  • dedicated control signaling for at least one terminal for which no terminal-specific downlink bandwidth indication is detected, i.e. a terminal other than the illustrated UE, may be scheduled in at least one resource chunk other than the at least one resource chunk in the second sub-band of the downlink carrier bandwidth, in which the dedicated control signaling for the at least one terminal is scheduled, for which the terminal-specific downlink bandwidth indication is detected.
  • dedicated control signaling for legacy (normal) UEs which are operable in the entire carrier bandwidth could be offloaded from the restricted downlink bandwidth of a narrow-band MTC UE or the like.
  • the common control signaling according to Figure 5 may be (included in) a message Msg2, the UE-specific downlink bandwidth indication according to Figure 5 be (included in) a message Msg3, and the dedicated control signaling according to Figure 5 may be (included in) a message Msg4.
  • Msgl may be a random access preamble or the like
  • Msg2 may be a random access response or the like
  • Msg3 may be a connection request, a measurement report, an ACK/IMACK message or the like
  • Msg4 may be a contention resolution message or the like.
  • the way of indicating terminal-specific downlink bandwidth reduction information could vary depending on various factors, such as e.g. the reason why a terminal in question triggers a contention-based random access procedure.
  • the terminal-specific downlink bandwidth indication may be to inform the eNB of the fact that the MTC UE only has reduced bandwidth capability.
  • the terminal-specific downlink bandwidth indication may be indicative of a reduced downlink bandwidth capability of the at least one terminal for the monitoring of resource chunks, and the dedicated control signaling for the at least one terminal may be scheduled in at least one preconfigured initial resource chunk, while dedicated control signaling for terminals other than the at least one terminal may be scheduled in resource chunks other than the at least one preconfigured initial resource chunk.
  • Such terminal-specific downlink bandwidth indication may comprise a predefined indicator or a specific subscriber identity out of a predefined value range or a specific (e.g. system architecture evolution) temporary mobile subscriber identity out of a predefined value range.
  • the MTC UE could include an indicator, e.g. a character string, a number or the like, with one or two bit(s), for example in the message Msg3.
  • the MTC UE will still try to receive the Msg4 and the following other downlink transmissions in the initial receive location (i.e. the originally configured common resource chunk) until a bandwidth configuration or the like is received as dedicated control signaling.
  • the eNB could flexibly transmit the Msg4 and the following other downlink transmissions for other UEs which do not include such indicator e.g. in Msg3, i.e. legacy UEs, in different (e.g. off-center) resource chunks other than the initial receive location for MTC UEs such as the common (e.g. center) resource chunk.
  • the MTC UE will transmit some CCCH signaling to the eNB.
  • the MTC UE could add some few bits in the RC signaling and report to the eNB. This may require some change to the minimum grant size for the Msg3, which currently is 56 bits. But given the fact that the increase number will be very small (i.e. 1 or 2 bit(s)) which will not (significantly) affect the resource allocation, such increase should be quite negligible.
  • the MTC UE could e.g. for the initial access case, randomly select an S-TMSI from a subset of a predefined value range of S-TMSI values such as a set of all possible S-TMSI values.
  • the defined value range of S-TMSIs for MTC UEs should be small enough compared to the total range because legacy UEs may still possibly select the same value by accident, but the eNB will always send the Msg4 and the following other downlink transmissions in the initial receive location (i.e. the originally configured common resource chunk) until a bandwidth configuration or the like is received as dedicated control signaling.
  • the defined value range of S-TMSIs for MTC UEs should be large enough to guarantee that a value collision probability among MTC UEs is low enough.
  • the eNB could set another S-TMSI value to any MTC UE right after the initial access, if deemed appropriate, required or preferable.
  • MTC UEs may randomly select the S-TMSI (having 40 bits) within the range from 0 to 2 ⁇ 10-1 or the range from 0 to 2 ⁇ 20-1 or the range from 0 to 2 ⁇ 15-1 (out of the total possible range from 0 to 2 40-1), in which case legacy UEs will have a probability of less than 0.000001% or 0.001% or 0.00003% for not choosing such range, respectively. So, the eNB will be able to estimate or assume that, if the received S-TMSI in RRC signaling such as in a RRC connection request falls into such range, it is probably a MTC UE signaling this indication.
  • the terminal-specific downlink bandwidth indication may be to assist/support the eNB to decide about a transmission resource allocation for dedicated control signaling for the MTC UE.
  • the terminal-specific downlink bandwidth indication may be indicative of a downlink bandwidth range of the at least one terminal, in which the at least one resource chunk for the monitoring of the dedicated control signaling is located, and the dedicated control signaling for the at least one terminal may be scheduled in the indicated downlink bandwidth range, while dedicated control signaling for terminals other than the at least one terminal may be scheduled in a downlink bandwidth range other than indicated downlink bandwidth range.
  • Such terminal-specific downlink bandwidth indication may comprise an index of the at least one resource chunk and/or at least one subframe in the at least one resource chunk for the monitoring of the dedicated control signaling.
  • the MTC UE could suggest a resource location (i.e. a dedicated resource chunk for scheduling and monitoring of dedicated control signaling such as the message Msg4 and following other downlink transmissions).
  • the intended reception location i.e. the dedicated resource chunk
  • the eNB could include a request for such resource location suggestion from the MTC UE e.g. in the message Msg2, e.g. by using the reserved bit in the RAR exemplifying Msg2.
  • a pre-defined resource location could be used, if the reserved bit in the RAR it set to "1", or a set reserved bit in the RAR could mean that the eNB will follow the MTC UE's resource location suggestion (if any).
  • the MTC UE could randomly select one of (available) subframes e.g. with uniform probability.
  • the eNB could further balance the load of transmissions of dedicated control signaling, e.g. different messages Msg4, to individual MTC UEs among the MTC UEs, if there is are many of such devices trying to access the communication network or system.
  • any MTC UE may try to receive dedicated downlink data in the same resource allocation (i.e. the dedicated resource chunk) until it is configured to perform monitoring/reception in another resource location or chunk.
  • the at least one resource chunk for the scheduling/monitoring of the dedicated control signaling may be defined on the basis of at least one resource chunk and/or at least one physical resource block in the at least one resource chunk for the signaling of the terminal-specific downlink bandwidth indication.
  • the elMB could use some predefined implicit linkage between an uplink transmission resource location e.g. for the message Msg3, and a downlink reception resource location e.g. for Msg4.
  • the MTC UE receives the uplink grant for the message (e.g. Msg3) which is to include the terminal-specific downlink bandwidth indication, e.g. in the message Msg2, it could implicitly know that the following dedicated control signaling (e.g. in the message Msg4) and the following other downlink transmissions will be transmitted on which sub-band or resource chunk thereof until a bandwidth configuration or the like is received as dedicated control signaling.
  • the lowest index of the PRB for Msg3 and the number of the sub-band which was defined for MTC UEs with reduced bandwidth capability could be used. For example, a possible formula for such calculation could be as follows;
  • Index of downlink sub-band (Lowest PRB index for Msg3) modulo (number of the defined sub-band)
  • Any one of these operations according to exemplary embodiments of the present invention is capable of ensuring that a network device is aware of downlink bandwidth characteristics of terminals such as narrow-band terminals. Thereby, the above-mentioned congestion-related problem in connection with downlink transmission of common control signaling and/or dedicated control signaling is resolved by any one of these operations according to exemplary embodiments of the present invention.
  • scheduling complexity for dedicated control signaling may be mitigated at the network device, thus balancing the load of dedicated control signaling to avoid congestion due to the narrow bandwidth of respective terminals, and reducing the probability of a random access failure and/or radio link failure due to congestion in terms of reception of common and/or dedicated control signaling at respective terminals.
  • the above-described procedures and functions may be implemented by respective functional elements, processors, or the like, as described below. While in the foregoing exemplary embodiments of the present invention are described mainly with reference to methods, procedures and functions, corresponding exemplary embodiments of the present invention also cover respective apparatuses, network nodes and systems, including both software and/or hardware thereof.
  • Solid line blocks are basically configured to perform respective operations as described above.
  • the entirety of solid line blocks are basically configured to perform the methods and operations as described above, respectively.
  • the individual blocks are meant to illustrate respective functional blocks implementing a respective function, process or procedure, respectively.
  • Such functional blocks are implementation-independent, i.e. may be implemented by means of any kind of hardware or software, respectively.
  • the arrows and lines interconnecting individual blocks are meant to illustrate an operational coupling there-between, which may be a physical and/or logical coupling, which on the one hand is implementation-independent (e.g. wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional entities not shown.
  • the direction of arrow is meant to illustrate the direction in which certain operations are performed and/or the direction in which certain data is transferred.
  • Figure 6 shows a schematic block diagram illustrating exemplary apparatuses according to exemplary embodiments of the present invention.
  • the thus illustrated apparatus 10 may represent a (part of an) apparatus operable as or in a network device, e.g. a base station or access node such as an elMB or a modem thereof (which may be installed as part thereof, but may also be a separate module, which can be attached to various devices, as described above), and may be configured to perform a procedure and/or functionality as described in conjunction with any one of Figures 1 to 5.
  • the thus illustrated apparatus 20 may represent a (part of an) apparatus operable as or in a terminal having reduced downlink bandwidth, especially being configurable to off-center resource chunks, e.g.
  • a MTC terminal mobile station, user equipment or a modem thereof (which may be installed as part thereof, but may also be a separate module, which can be attached to various devices, as described above), and may be configured to perform a procedure and/or functionality as described in conjunction with any one of Figures 1 to 5.
  • each of the apparatuses comprises at least one processor 11/22, at least one memory 12/22 and at least one interface 13/23, which are connected by a bus 14/24 or the like, and the apparatuses may be connected via a (e.g. wired or wireless) link 30.
  • the link 30 may be a physical and/or logical coupling, which on the one hand is implementation- independent and on the other hand may also comprise an arbitrary number of intermediary functional entities not shown in Figure 6 (such as a relay or the like).
  • the processor 11/21 and/or the interface 13/23 may be facilitated for communication over a (hardwire or wireless) link, respectively.
  • the interface 13/23 may comprise a suitable receiver or a suitable transmitter- receiver combination or transceiver, which is coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively.
  • the interface 13/23 is generally configured to communicate with another apparatus, i.e. the interface thereof.
  • the memory 12/22 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the exemplary embodiments of the present invention.
  • the respective devices/apparatuses may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.
  • the processor or some other means
  • the processor is configured to perform some function
  • this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently imp!ementable by specifically configured means for performing the respective function (i.e.
  • the expression "processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as "means for xxx-ing").
  • the two apparatuses with are to cooperate with each other may be configured as follows.
  • the processor i.e.
  • the at least one processor 11, with the at least one memory 12 and the computer program code) of the apparatus 10 may be configured to perform scheduling common control signaling for at least one terminal in at least one common resource chunk in a first sub- band of a downlink carrier bandwidth, and scheduling dedicated downlink data for said at least one terminal in at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling, and the processor (i.e.
  • the at least one processor 21, with the at least one memory 22 and the computer program code may be configured to perform monitoring at least one common resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from a network equipment, and monitoring at least one dedicated resource chunk in a second sub-band of a downlink carrier bandwidth for dedicated downlink data from the network equipment according to the common control signaling from the network equipment.
  • the individual apparatuses may be configured such that:
  • the common control signaling is scheduled/monitored in at least one physical resource block in the at least one common resource chunk, and/or
  • - signaling of a common resource chunk indicator from the terminal to the network equipment is conducted upon start or determination of possibility of the monitoring of the common control signaling in the common resource chunk
  • signaling of a dedicated resource chunk indicator from the terminal to the network equipment is conducted upon start or determination of possibility of the monitoring of the dedicated downlink data in the dedicated resource chunk or upon determination of impossibility of decoding detected common control signaling for a predetermined period.
  • the processor i.e. the at least one processor 11, with the at least one memory 12 and the computer program code
  • the processor may be configured to perform scheduling common control signaling for at least one terminal in at least one resource chunk in a first sub-band of a downlink carrier bandwidth, detecting a terminal-specific downlink bandwidth indication from said at least one terminal, and scheduling dedicated control signaling for the at least one terminal in at least one resource chunk in a second sub-band of a downlink carrier bandwidth according to the common control signaling and the terminal-specific downlink bandwidth indication
  • the processor i.e. the at least one processor 11, with the at least one memory 12 and the computer program code
  • the at least one processor 21, with the at least one memory 22 and the computer program code may be configured to perform monitoring at least one resource chunk in a first sub-band of a downlink carrier bandwidth for common control signaling from a network equipment, signaling a terminal-specific downlink bandwidth indication to the network equipment, and monitoring at least one resource chunk in a second sub- band of a downlink carrier bandwidth for dedicated control signaling from the network equipment according to the common control signaling from the network equipment and the terminal-specific downlink bandwidth indication.
  • the individual apparatuses may be configured such that:
  • the terminal-specific downlink bandwidth indication is indicative of a reduced downlink bandwidth capability of a terminal for the monitoring of resource chunks, and/or
  • the terminal-specific downlink bandwidth indication comprises a predefined indicator or a specific subscriber identity out of a predefined value range or a specific system architecture evolution temporary mobile subscriber identity out of a predefined value range, and/or
  • the terminal-specific downlink bandwidth indication is indicative of a downlink bandwidth range of a terminal, in which the at least one resource chunk for the monitoring of the dedicated control signaling is located, and/or
  • the terminal-specific downlink bandwidth indication comprises an index of the at least one resource chunk and/or at least one subframe in the at least one resource chunk for the monitoring of the dedicated control signaling, and/or
  • At least one resource chunk for the monitoring of the dedicated control signaling is defined on the basis of at least one resource chunk and/or at least one physical resource block in the at least one resource chunk for the signaling of the terminal-specific downlink bandwidth indication.
  • a system may comprise any conceivable combination of the thus depicted devices/apparatuses and other network elements, which are configured to cooperate as described above.
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any structural means such as a processor or other circuitry may refer to one or more of the following : (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) combinations of circuits and software (and/or firmware), such as (as applicable) : (i) a combination of processor(s) or (ii) portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • any procedural step or functionality is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Such software may be software code independent and can be specified using any known or future developed programming language, such as e.g. Java, C++, C, and Assembler, as long as the functionality defined by the method steps is preserved.
  • Such hardware may be hardware type independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor- Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components.
  • MOS Metal Oxide Semiconductor
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS BiCMOS
  • ECL Emitter Coupled Logic
  • TTL Transistor- Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field-programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP
  • a device/apparatus may be represented by a semiconductor chip, a chipset, system in package, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device/apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor.
  • a device may be regarded as a device/apparatus or as an assembly of more than one device/apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • Apparatuses and/or means or parts thereof can be implemented as individual devices, but this does not exclude that they may be implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • the present invention also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.
  • the present invention and/or exemplary embodiments thereof provide measures for realizing control signaling approaches for terminals with reduced downlink bandwidth, such as for example machine type communication terminals for wireless communication systems.
  • Such measures may exemplarily comprise, at a terminal side, monitoring different resource chunks in a sub-band of a downlink carrier bandwidth for common control signaling and dedicated downlink data from a network device and, at a network side, scheduling common control signaling and dedicated downlink data for at least one terminal in different resource chunks in the sub-band of the downlink carrier bandwidth.
  • E-UTRAN base station E-UTRAN base station
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network

Landscapes

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

Abstract

La présente invention concerne des mesures pour réaliser des approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante, tels que, par exemple, des terminaux de communication de type machine pour des systèmes de communication sans fil. De telles mesures peuvent comprendre à titre d'exemple, du côté du terminal, la surveillance de différents blocs de ressources dans une sous-bande d'une largeur de bande de porteuse en liaison descendante pour une signalisation de commande commune et de données de liaison descendante dédiées provenant d'un équipement de réseau et, du côté du réseau, la planification d'une signalisation de commande commune et de données de liaison descendante dédiées pour au moins un terminal dans différents blocs de ressource dans la sous-bande de la largeur de bande de porteuse en liaison descendante.
PCT/CN2012/077605 2012-06-27 2012-06-27 Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante WO2014000174A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/077605 WO2014000174A1 (fr) 2012-06-27 2012-06-27 Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/077605 WO2014000174A1 (fr) 2012-06-27 2012-06-27 Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante

Publications (1)

Publication Number Publication Date
WO2014000174A1 true WO2014000174A1 (fr) 2014-01-03

Family

ID=49782041

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/077605 WO2014000174A1 (fr) 2012-06-27 2012-06-27 Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante

Country Status (1)

Country Link
WO (1) WO2014000174A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016071765A1 (fr) * 2014-11-07 2016-05-12 Alcatel Lucent Saut de sous-bande d'espace de recherche spécifique d'équipement utilisateur de canal amélioré de commande de liaison descendante physique pour dispositif de communication de type machine
CN105766013A (zh) * 2014-11-07 2016-07-13 华为技术有限公司 信息传输方法和装置
WO2016200238A1 (fr) * 2015-06-11 2016-12-15 Lg Electronics Inc. Procédé et appareil pour configurer un internet des objets cellulaire dans un système de communication sans fil
WO2017052297A1 (fr) * 2015-09-23 2017-03-30 Lg Electronics Inc. Procédé et appareil permettant d'exécuter une procédure d'accès aléatoire
CN108293226A (zh) * 2015-11-19 2018-07-17 Sk电信有限公司 用于在移动通信系统中选择核心网络的方法和设备
EP3442148A1 (fr) * 2017-08-11 2019-02-13 Panasonic Intellectual Property Corporation of America Adaptation de la partie de bande passante dans des communications de liaison descendante
CN111052836A (zh) * 2018-08-07 2020-04-21 联发科技股份有限公司 用于初始下行链路带宽部分的配置的装置和方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1622413A2 (fr) * 2004-07-26 2006-02-01 Samsung Electronics Co., Ltd. Procédé et dispositif de plannification d'un terminal d'utilisateur dans une région de transfert souple pour la transmission de paquets en voie montante
WO2006113712A1 (fr) * 2005-04-20 2006-10-26 Interdigital Technology Corporation Procede et dispositif destines a l'ordonnancement des transmissions par l'intermediaire d'une voie specialisee amelioree
WO2008024889A2 (fr) * 2006-08-22 2008-02-28 Qualcomm Incorporated Procédé et appareil de surveillance des canaux d'octroi dans une communication sans fil
CN101442813A (zh) * 2008-12-25 2009-05-27 北京天碁科技有限公司 一种hsupa业务初始建链阶段的上行同步和功率控制方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1622413A2 (fr) * 2004-07-26 2006-02-01 Samsung Electronics Co., Ltd. Procédé et dispositif de plannification d'un terminal d'utilisateur dans une région de transfert souple pour la transmission de paquets en voie montante
WO2006113712A1 (fr) * 2005-04-20 2006-10-26 Interdigital Technology Corporation Procede et dispositif destines a l'ordonnancement des transmissions par l'intermediaire d'une voie specialisee amelioree
WO2008024889A2 (fr) * 2006-08-22 2008-02-28 Qualcomm Incorporated Procédé et appareil de surveillance des canaux d'octroi dans une communication sans fil
CN101442813A (zh) * 2008-12-25 2009-05-27 北京天碁科技有限公司 一种hsupa业务初始建链阶段的上行同步和功率控制方法

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016071765A1 (fr) * 2014-11-07 2016-05-12 Alcatel Lucent Saut de sous-bande d'espace de recherche spécifique d'équipement utilisateur de canal amélioré de commande de liaison descendante physique pour dispositif de communication de type machine
US20160135176A1 (en) * 2014-11-07 2016-05-12 Alcatel Lucent Enhanced physical downlink control channel user equipment specific search space subband hopping for machine type communication device
CN105766013A (zh) * 2014-11-07 2016-07-13 华为技术有限公司 信息传输方法和装置
CN105766013B (zh) * 2014-11-07 2019-12-24 华为技术有限公司 信息传输方法和装置
US10505690B2 (en) 2014-11-07 2019-12-10 Huawei Technologies Co., Ltd. Information transmission method and apparatus
US9655110B2 (en) 2014-11-07 2017-05-16 Alcatel Lucent Enhanced physical downlink control channel user equipment specific search space subband hopping for machine type communication device
EP3200495A4 (fr) * 2014-11-07 2017-11-08 Huawei Technologies Co., Ltd. Procédé et appareil d'émission d'informations
JP2017533682A (ja) * 2014-11-07 2017-11-09 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 情報伝送方法および装置
US11218272B2 (en) 2014-11-07 2022-01-04 Huawei Technologies Co., Ltd. Information transmission method and apparatus
WO2016200238A1 (fr) * 2015-06-11 2016-12-15 Lg Electronics Inc. Procédé et appareil pour configurer un internet des objets cellulaire dans un système de communication sans fil
US10568103B2 (en) 2015-06-11 2020-02-18 Lg Electronics Inc. Method and apparatus for communicating with a network on cellular internet-of-things carriers
US20180279373A1 (en) * 2015-09-23 2018-09-27 Lg Electronics Inc. Method and apparatus for performing random access procedure
WO2017052297A1 (fr) * 2015-09-23 2017-03-30 Lg Electronics Inc. Procédé et appareil permettant d'exécuter une procédure d'accès aléatoire
CN108293226A (zh) * 2015-11-19 2018-07-17 Sk电信有限公司 用于在移动通信系统中选择核心网络的方法和设备
EP3442148A1 (fr) * 2017-08-11 2019-02-13 Panasonic Intellectual Property Corporation of America Adaptation de la partie de bande passante dans des communications de liaison descendante
WO2019030335A1 (fr) * 2017-08-11 2019-02-14 Panasonic Intellectual Property Corporation Of America Adaptation de partie de largeur de bande dans des communications de liaison descendante
RU2763778C2 (ru) * 2017-08-11 2022-01-11 Панасоник Интеллекчуал Проперти Корпорейшн Оф Америка Адаптация части полосы пропускания на нисходящей линии связи
US11265961B2 (en) 2017-08-11 2022-03-01 Panasonic Intellectual Property Corporation Of America Bandwidth part adaptation in downlink communications
EP4175214A1 (fr) * 2017-08-11 2023-05-03 Panasonic Intellectual Property Corporation of America Adaptation de partie de bande passante dans des communications de liaison descendante
US11659618B2 (en) 2017-08-11 2023-05-23 Panasonic Intellectual Property Corporation Of America Bandwidth part adaptation in downlink communications
US12022561B2 (en) 2017-08-11 2024-06-25 Panasonic Intellectual Property Corporation Of America Bandwidth part adaptation in downlink communications
CN111052836A (zh) * 2018-08-07 2020-04-21 联发科技股份有限公司 用于初始下行链路带宽部分的配置的装置和方法
CN111052836B (zh) * 2018-08-07 2023-05-23 联发科技股份有限公司 用于初始下行链路带宽部分的配置的用户设备和方法

Similar Documents

Publication Publication Date Title
US11129190B2 (en) Method for performing random access procedure and apparatus therefor
US11729834B2 (en) Method for performing random access procedure and apparatus therefor
CN111357380B (zh) 与无线通信中的随机接入相关的改进
CN110754127B (zh) 无线通信系统中根据bwp或波束切换配置控制信道的方法和装置
US20220174584A1 (en) Access Method of Wireless Communication Network
US11202271B2 (en) Synchronization across transmitting nodes using shared radio frequency spectrum
CN110234166B (zh) 用于在无线通信系统中执行随机接入过程的方法和设备
WO2014000174A1 (fr) Approches de signalisation de commande pour des terminaux ayant une largeur de bande réduite en liaison descendante
US10542492B2 (en) Method for DRX in unlicensed band, and device using same
US9867183B2 (en) Communication method and wireless device for supporting variable bandwidth
US9491781B2 (en) Random access channel enhancement for carrier aggregation with different uplink/downlink configuration
KR20180011175A (ko) 면허 지원 액세스에서의 스케줄링
KR102152514B1 (ko) 업링크 전송을 위한 lbt
US20230027824A1 (en) Signal transmission/reception method for wireless communication, and apparatus therefor
US20180139733A1 (en) Method for transmitting and receiving signal using wireless frame for low-delay communication, and apparatus for same
OA20416A (en) Improvements Related To Random Access In Wireless Communications

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: 12879759

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: 12879759

Country of ref document: EP

Kind code of ref document: A1