HUE035205T2 - Downlink resource scheduling - Google Patents
Downlink resource scheduling Download PDFInfo
- Publication number
- HUE035205T2 HUE035205T2 HUE12846485A HUE12846485A HUE035205T2 HU E035205 T2 HUE035205 T2 HU E035205T2 HU E12846485 A HUE12846485 A HU E12846485A HU E12846485 A HUE12846485 A HU E12846485A HU E035205 T2 HUE035205 T2 HU E035205T2
- Authority
- HU
- Hungary
- Prior art keywords
- subframe
- pairing
- paired
- frame
- cif
- Prior art date
Links
- 238000000034 method Methods 0.000 claims abstract description 10
- 230000005540 biological transmission Effects 0.000 claims description 26
- 238000013507 mapping Methods 0.000 claims description 23
- 230000002776 aggregation Effects 0.000 claims description 15
- 238000004220 aggregation Methods 0.000 claims description 15
- 239000000969 carrier Substances 0.000 claims description 12
- 238000004891 communication Methods 0.000 claims description 11
- 101100365003 Mus musculus Scel gene Proteins 0.000 claims 1
- 230000011664 signaling Effects 0.000 claims 1
- 239000002131 composite material Substances 0.000 abstract 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 7
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 5
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 3
- 241000251468 Actinopterygii Species 0.000 description 2
- 150000001875 compounds Chemical class 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 239000004599 antimicrobial Substances 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000366 juvenile effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000003449 preventive effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000002054 transplantation Methods 0.000 description 1
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/14—Two-way operation using the same type of signal, i.e. duplex
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/022—Site diversity; Macro-diversity
- H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/0404—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas the mobile station comprising multiple antennas, e.g. to provide uplink diversity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/0413—MIMO systems
- H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
- H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
- H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
- H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
- H04B7/0621—Feedback content
- H04B7/0626—Channel coefficients, e.g. channel state information [CSI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/007—Unequal error protection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0076—Distributed coding, e.g. network coding, involving channel coding
- H04L1/0077—Cooperative coding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1861—Physical mapping arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2647—Arrangements specific to the receiver only
- H04L27/2655—Synchronisation arrangements
- H04L27/2662—Symbol synchronisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2647—Arrangements specific to the receiver only
- H04L27/2655—Synchronisation arrangements
- H04L27/2668—Details of algorithms
- H04L27/2673—Details of algorithms characterised by synchronisation parameters
- H04L27/2675—Pilot or known symbols
-
- 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 signalling, i.e. of overhead other than pilot signals
-
- 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 signalling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0078—Timing of allocation
-
- 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/22—Arrangements affording multiple use of the transmission path using time-division multiplexing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/24—Cell structures
- H04W16/28—Cell structures using beam steering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/02—Power saving arrangements
- H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
- H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/06—TPC algorithms
- H04W52/14—Separate analysis of uplink or downlink
- H04W52/146—Uplink power control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
- H04W52/242—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account path loss
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
- H04W56/0015—Synchronization between nodes one node acting as a reference for the others
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/02—Arrangements for increasing efficiency of notification or paging channel
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/12—Arrangements providing for calling or supervisory signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
- H04L1/0026—Transmission of channel quality indication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2626—Arrangements specific to the transmitter only
- H04L27/2646—Arrangements specific to the transmitter only using feedback from receiver for adjusting OFDM transmission parameters, e.g. transmission timing or guard interval length
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
- H04L5/0035—Resource allocation in a cooperative multipoint environment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
- H04W52/243—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account interferences
- H04W52/244—Interferences in heterogeneous networks, e.g. among macro and femto or pico cells or other sector / system interference [OSI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
- H04W52/34—TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/02—Selection of wireless resources by user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/14—WLL [Wireless Local Loop]; RLL [Radio Local Loop]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
- Radio Transmission System (AREA)
Abstract
Description
(12) EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention (51) IntCI.: of the grant of the patent: H04J 11100 <2006 01> H04B 7126 <2006 01> 19.04.2017 Bulletin 2017/16 H04L 5l00<200601> (21) Application number: 12846485.6 (86) International application number: PCT/US2012/031036 (22) Date of filing: 28.03.2012 (87) International publication number: WO 2013/066385 (10.05.2013 Gazette 2013/19)(12) IntCI .: of the grant of the patent: H04J 11100 <2006 01> H04B 7126 <2006 01> 19.04.2017 Bulletin 2017/16 H04L 5l00 <200601 > (21) Application number: 12846485.6 (86) International application number: PCT / US2012 / 031036 (22) Date of filing: 28.03.2012 (87) International publication number: WO 2013/066385 (10.05.2013 Gazette 2013/19)
(54) DOWNLINK RESOURCE SCHEDULING(54) DOWNLINK RESOURCE SCHEDULING
RESSOURCENZUWEISUNG IN DER ABWARTSSTRECKE PLANIFICATION DE RESSOURCE DE LIAISON DESCENDANTE (84) Designated Contracting States: · SAMSUNG: "Data scheduling in CA with different AL AT BE BG CH CY CZ DE DK EE ES FI FR GB TDD UL-DL configurations", 3GPP DRAFT;RESSOURCENZUWEISUNG IN DER ABWARTSSTRECKE PLANIFICATION DE RESSOURCE DE LIAISON DESCENDANTE (84) Designated Contracting States: · SAMSUNG: "Data scheduling in CA with different AL AT BE BG CH CY CZ DE DK EE ES FI FR GB TDD UL-DL configurations", 3GPP DRAFT ;
GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO R1-113082 TDD DATA SCHEDULING, 3RD PL PT RO RS SE SI SK SM TR GENERATION PARTNERSHIP PROJECT(3GPP),MS HR MT MT MT MT MT MT MT NO MT 11-113082 TDD DATA SCHEDULING, 3RD PL PT RO RS SE SI SK SM TR GENERATION PARTNERSHIP PROJECT (3GPP)
MOBILE COMPETENCE CENTRE ; 650, ROUTEMOBILE COMPETENCE CENTER; 650, ROUTE
(30) Priority: 04.11.2011 US 201161556109 P DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Zhuhai; (43) Date of publication of application: 20111010, 4 October 2011 (2011-10-04), 10.09.2014 Bulletin 2014/37 XP050538229, [retrieved on 2011-10-04] • MEDIATEK INC: "Cross-carrier scheduling on (73) Proprietor: Intel Corporation different TDD configurations", 3GPP DRAFT;(30) Priority: 04.11.2011 US 201161556109 P DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCE, vol. RAN WG1, no. Zhuhai; (43) Date of publication of the application: 20111010, 4 October 2011 (2011-10-04), 10.09.2014 Bulletin 2014/37 XP050538229, [retrieved on 2011-10-04] • Cross-carrier scheduling is (73) Proprietor: Intel Corporation different TDD configurations, 3GPP DRAFT;
Santa Clara, CA 95054 (US) R1-113048_CROSS-CARRIER_SCHEDULING_DISanta Clara, CA 95054 (US) R1-113048_CROSS-CARRIER_SCHEDULING_DI
FF_TD D_CONFIG, 3RD GENERATIONFF_TD D_CONFIG, 3RD GENERATION
(72) Inventors: PARTNERSHIP PROJECT (3GPP), MOBILE(72) Inventors: PARTNERSHIP PROJECT (3GPP), MOBILE
• HE, Hong COMPETENCE CENTRE ; 650, ROUTE DES• HE, Hong COMPETENCE CENTER; 650, ROUTE DES
Beijing 100190 (CN) LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS • FWU, Jong-Kae CEDEX ; FRANCE, vol. RAN WG1, no. Zhuhai;Beijing 100190 (CN) LUCIOLES; F-06921 SOPHIA-ANTIPOLIS • FWU, Jong-Kae CEDEX; FRANCE, vol. RAN WG1, no. Zhuhai;
Sunnyvale, California 94087 (US) 20111010, 4 October 2011 (2011-10-04), XP050538207, [retrieved on 2011-10-04] (74) Representative: HGF Limited · POTEVIO: "Consideration on simultaneous tx/rxSunnyvale, California 94087 (US) 20111010, 4 October 2011 (2011-10-04), XP050538207, [retrieved on 2011-10-04] (74) Representative: HGF Limited · POTEVIO: "Consideration is simultaneous tx / rx
Fountain Precinct on different bands with different UL-DLFountain Precinct on different bands with different UL-DL
Balm Green configurations", 3GPP DRAFT; R1-113024Balm Green Configurations, 3GPP DRAFT; R1-113024
Sheffield S1 2JA (GB) CONSIDERATION ON SIMULTANEOUS TX-RXSheffield S1 2JA (GB) CONSIDERATION ON SIMULTANEOUS TX-RX
ON DIFFERENT BANDS WITH DIFFERENT UL-DLON DIFFERENT BANDS WITH DIFFERENT UL-DL
(56) References cited: CONFIGURATIONS, 3RD GENERATION(56) References: CONFIGURATIONS, 3RD GENERATION
EP-A2-2 738 965 KR-A-20110 058 665 PARTNERSHIP PROJECT (3GPP), MOBILEEP-A2-2 738 965 KR-A-20110 058 665 PARTNERSHIP PROJECT (3GPP), MOBILE
KR-A- 20110 109 812 COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Zhuhai; 20111010, 3 October 2011 (2011-10-03), XP050538063, [retrieved on 2011-10-03]KR-A- 20110 109 812 COMPETENCE CENTER; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCE, vol. RAN WG1, no. Zhuhai; 20111010, 3 October 2011 (2011-10-03), XP050538063, [retrieved on 2011-10-03]
Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). • ALCATEL-LUCENT SHANGHAI BELL ETAL: · ITRI:’Discussions on UL-DL TDD configurations "Specification impact of Inter-band Carrier for inter-band CA.’ 3GPP TSG-RAN WG1 aggregation with different TDD UL-DL MEETING #66BIS 10 October2011, XP050538536 configurations", 3GPP DRAFT; R1-113313_ Retrieved from the Internet: SPEC IMPACT CC-SPECIFIC TDD <URL:http://www.3gpp.org/ftp/ CONFIGURATION, 3RD GENERATION tsg-ran/WG1-RL1/TSGRL66b/Docs/R1-11337l.zi PARTNERSHIP PROJECT (3GPP), MOBILE p > [retrieved on 2012-10-22] COMPETENCE CENTRE ; 650, ROUTE DES · 3GPP: ’3rd Generation Partnership Project; LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS Technical Specification Group Radio Access CEDEX ; FRANCE, vol. RAN WG1, no. Zhuhai; Network; Evolved Universal Terrestrial Radio 20111010, 6 October 2011 (2011-10-06), Access (E-UTRA) and Evolved Universal XP050538585, [retrieved on 2011-10-06] Terrestrial Radio Access Network (E-UTRAN);Note: Within a period of nine months from the date of publication of the publication of the European Patent Office of the Implementing Regulations. Notice of opposition to the opposition has been paid. (Art. 99 (1) European Patent Convention). • ALCATEL-LUCENT SHANGHAI BELL ETAL: · ITRI: 'Discussions is UL-DL TDD Configurations' Specification of Inter-Band Carrier for Inter-Band CA.' 3GPP TSG-RAN WG1 aggregation with different TDD UL-DL MEETING # 66BIS 10 October2011, XP050538536 configurations ", 3GPP DRAFT; R1-113313_Retrieved from the Internet: SPEC IMPACT CC-SPECIFIC TDD <URL: http: //www.3gpp.org/ftp/ CONFIGURATION, 3RD GENERATION tsgran / WG1-RL1 / TSGRL66b / Docs / R1-11337l.zi PARTNERSHIP PROJECT (3GPP), MOBILE p> [retrieved on 2012-10-22] COMPETENCE CENTER; 650, ROUTE DES · 3GPP: The 3rd Generation Partnership Project; LUCIOLES; F-06921 SOPHIA-ANTIPOLIS Technical Specification Group Radio Access CEDEX; FRANCE, vol. RAN WG1, no. Zhuhai; Network; Evolved Universal Terrestrial Radio 2011-1010, Access (E-UTRA) and Evolved Universal XP050538585, [retrieved on 2011-10-06] Terrestrial Radio Access Network (E-UTRAN);
• NTT DOCOMO: "PCFICH for Cross-Carrier Overall description; Stage 2 (Release 10).’ 3GPP• NTT DOCOMO: "PCFICH for Cross-Carrier Overall description; Stage 2 (Release 10)." 3GPP
Assignment", 3GPP DRAFT; R1-103243 PCFICH, TS 36.300 V10.3.0 March 2011, XP055129322 3RD GENERATION PARTNERSHIP PROJECT Retrieved from the Internet: (3GPP), MOBILE COMPETENCE CENTRE ; 650, <URL:http://www.3gpp.org/ ftp/tsg-ran/WG2 ROUTE DES LUCIOLES ; F-06921 RL2/Specifications/201103-draft SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN specs-after_RAN_51/ draft_36300-a30.zip> WG1, no. Montreal, Canada; 20100510, 4 May [retrieved on 2012-10-23] 2010 (2010-05-04), XP050420273, [retrieved on 2010-05-04]Assignment ", 3GPP DRAFT; R1-103243 PCFICH, TS 36.300 V10.3.0 March 2011, XP055129322 3RD GENERATION PARTNERSHIP PROJECT: (3GPP), MOBILE COMPETENCE CENTER; 650, <URL: //www.3gpp. org / ftp / tsg-ran / WG2 ROUTE DES LUCIOLES; F-06921 RL2 / Specifications / 201103-draft SOPHIA-ANTIPOLIS CEDEX; FRANCE, vol. RAN specs-after_RAN_51 / draft_36300-a30.zip> WG1, from Montreal, Canada ; 20100510, 4 May [retrieved on 2012-10-23] 2010 (2010-05-04), XP050420273, [retrieved on 2010-05-04]
Descriptiondescription
Field [0001] Embodiments of the present invention relate generally to the field of communications, and more particularly, to downlink resource scheduling in wireless communication networks.Field Embodiments of the present invention relate to the field of communications, and more particularly to downlink resource scheduling in wireless communication networks.
Background [0002] In 3rd Generation Partnership Project (3 GPP) long-term evolution (LTE) Release 10 (March 2011), which may also be referred to as LTE-Advanced (LTE -A), heterogeneous networks (HetNets) are relied upon to provide high-throughput communications. HetNets may include cells of different power class, e.g., macro, pico, orfemto, and access class, e.g., open or closed-subscribergroup (CSG). To accommodate for lack of intercell interference coordination (ICIC) control signaling in 3 GPP LTE Release 8 (September 2009), multicarrier operation with cross-carrier scheduling was provided. This would allow for the control information applicable to a subframe of a first component carrier, being transmitted in the corresponding subframe of another component carrier that was deemed more reliable. A single sub-frame cross-carrier scheduling operation is facilitated by use of a carrier identification field (CIF) of UE dedicated downlink control information (DO) to provide improved control reliability and enable enhanced ICIC (elCIC) for HetNets.Background 3rd Generation Partnership Project (3 GPP) Long-term evolution (LTE) Release 10 (March 2011), which may also be referred to as LTE-Advanced (LTE-A), heterogeneous networks (HetNets) are relied upon to provide high-throughput communications. HetNets may include cells of different power classes, e.g., macro, pico, orphemto, and access class, e.g., open or closed-subscribergroup (CSG). Multicarrier operation with cross-carrier scheduling was provided to accommodate for intercell interference coordination (ICIC) in 3 GPP LTE Release 8 (September 2009). This is an alternative to the first component carrier that was considered to be more reliable. A single sub-frame cross-carrier scheduling operation is facilitated by a carrier identification field (CIF) of UE dedicated downlink control information (DO) to provide improved control and enable enhanced ICIC (elCIC) for HetNets.
[0003] In 3 GPP LTE Release 11, each component carrier may have its own time-division duplexing (TDD) uplink-downlink (UL-DL) configuration. However, aggregation of carriers with different TDD UL-DL configurations may complicate cross-carrier scheduling. SAMSUNG: "Data scheduling in CA with different TDD UL-DL configurations", 3GPP DRAFT; R1-113082 TDD DATA SCHEDULING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), vol. RAN WG1, no. Zhuhai; 20111010, 4 October 2011 (2011-10-04) describes an approach to support interband CA for TDD with different uplink-downlink configurations on different bands.In 3 GPP LTE Release 11, each component carrier may have its own time-division duplexing (TDD) uplink downlink (UL-DL) configuration. However, aggregation of carriers with different TDD UL-DL configurations may complicate cross-carrier scheduling. SAMSUNG: "Data scheduling in CA with different TDD UL-DL configurations", 3GPP DRAFT; R1-113082 TDD DATA SCHEDULING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), vol. RAN WG1, no. Zhuhai; 2011-1010, October 4, 2011 (2011-10-04) on different bands.
Brief Description of the Drawings [0004] Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.Brief Description of the Drawings Embodiments will be readily understood by the following drawings. This is a reference numerals designate like structural elements. Embodiments are illustrated by the example of the drawings of the accompanying drawings.
Figure 1 schematically illustrates a wireless communication network in accordance with various embodiments. Figures 2(a) - 2(c) schematically illustrate scheduling scenarios in accordance with various embodiments.Figure 1 schematically illustrating a wireless communication network in the various embodiments. Figures 2 (a) - 2 (c) schematically illustrate scheduling scenarios in in with various embodiments.
Figure 3 illustrates a multi-subframe cross carrier scheduling (MSCC) table in accordance with various embodiments. Figure 4 illustrates MSCC tables in accordance with various embodiments.Figure 3 illustrates a multi-subframe cross carrier scheduling (MSCC) table iniant with various embodiments. Figure 4 illustrates the MSCC tables iniant with various embodiments.
Figure 5 illustrates an MSCC scheduling of a radio frame in accordance with various embodiments.Figure 5 illustrates an MSCC scheduling of a radio frame in various embodiments.
Figure 6 is a flowchart illustrating an operation of a user equipment in accordance with various embodiments. Figure 7 is a flowchart illustrating an operation of a base station in accordance with various embodiments.Figure 6 is a flowchart illustrating the operation of a user equipment in a variety of embodiments. Figure 7 is a flowchart illustrating the operation of a station station in various with various embodiments.
Figure 8 schematically depicts an example system in accordance with various embodiments.Figure 8 schematically depicts an in system with various embodiments.
Detailed Description [0005] Illustrative embodiments of the present disclosure include, but are not limited to, methods, systems, and apparatuses for downlink resource scheduling in wireless networks.Detailed Description Illustrative embodiments of the present disclosure include, but are not limited to, methods, systems, and apparatus for wireless networking.
[0006] Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternate embodiments may be practiced with only some of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.[0006] Various aspects of the present invention are to be found in the art. However, it will be the skilled in the art. For the purpose of explanation, specific numbers, materials, and configurations are set forth in the following paragraph. However, it will be the one that is skilled in the art. In other instances, well-known features are omitted or simplified.
[0007] Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.[0007] Further, various operations will be described as multiple discrete operations; however, the order is to be construed as to be impeded. In particular, these operations need to be carried out in the order of presentation.
[0008] The phrase "in some embodiments" is used repeatedly. The phrase generally does not refer to the same embodiments; however, it may. The terms "comprising," "having,"The phrase "in some embodiments" is usedlenly. The phrase generally does not refer to the same embodiments; however, it may. The terms "some," "having,"
and "including" are synonymous, unless the context dictates otherwise. The phrase "A and/or B" means (A), (B), or (A and B). The phrase "A/B" means (A), (B), or (A and B), similar to the phrase "A and/or B". The phrase "at least one of A, B and C" means (A), (B), (C), (A and B), (A and C), (B and C) or (A, B and C). The phrase "(A) B" means (B) or (A and B), that is, A is optional.and "including" are synonymous, unless the context dictates otherwise. The phrase "A and / or B" means (A), (B), or (A and B). The phrase "A / B" means (A), (B), or (A and B), similar to the phrase "A and / or B". The term "at least one of A, B and C" means (A), (B), (C), (A and B), (A and C), (B and C) or (A, B and C) ). The phrase "(A) B" means (B) or (A and B), that is, A is optional.
[0009] Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a wide variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described, without departing from the scope of the embodiments of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. As used herein, the term "module" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.Although it is appreciated, it will be appreciated by those who are interested in the art of a variety of alternatives and / or equivalent implementations. the scope of the presentations. This application is intended to cover any of the implementations discussed herein. (Used, dedicated, group) and / or memory (shared, dedicated) , or group of programs that execute one or more software or firmware, and / or combinational logic circuit, and / or.
[0010] Figure 1 schematically illustrates a wireless communication network 100 in accordance with various embodiments. Wireless communication network 100 (hereinafter "network 100") may be an access network of a 3rd Generation Partnership Project (3GPP) long-term evolution advanced (LTE-A) network such as evolved universal mobile telecommunication system (UMTS) terrestrial radio access network (E-UTRAN). The network 100 may include a base station, e.g., enhanced node base station (eNB) 104, configured to wirelessly communicate with a mobile terminal, e.g., user equipment (UE) 108. While embodiments of the present invention are described with reference to an LTE-A network, some embodiments may be used with other types of wireless access networks.[0010] Figure 1 schematically illustrating a wireless communication network 100 initing with various embodiments. Wireless communication network 100 (LTE-A) network such as evolved universal mobile telecommunication system (UMTS) terrestrial radio access network (E-UTRAN). The network 100 may include: a node base station (eNB) 104, configured to wirelessly communicate with a terminal, eg, user equipment (UE). LTE-A network, some implementations of wireless access networks.
[0011] In embodiments in which the UE 108 is capable of utilizing carrier aggregation (CA), a number of component carriers (CCs) may be aggregated for communication between the eNB 104 and the UE 108. In an initial connection establishment, the UE 108 may connect with a primary serving cell (Pcell) of the eNB 104 utilizing a primary CC, which may also be referred to as CC 0. This connection may be used for various functions such as security, mobility, configuration, etc. Subsequently, the UE 108 may connect with one or more secondary serving cells (Scells) of the eNB 104 utilizing one or more secondary CCs. These connections may be used to provide additional radio resources.A number of component carriers (CCs) may be aggregated for communication between the eNB 104 and the UE 108. In an initial connection establishment, the UE 108 is a capable of utilizing carrier aggregation (CA). 108 may use a primary CC, which may also be used as CC 0. Subsequently, the UE 108 may connect with one or more secondary cells (Scells) of the eNB 104 utilizing one or more secondary CCs. These connections may also be used to provide additional radio resources.
[0012] In some embodiments, one or more additional eNBs, e.g., eNB 112, may be employed, e.g., in a HetNet configuration. In some embodiments, the eNBs of a HetNet may each have different power and/or access classes. For example, in one embodiment the eNB 104 may be a relatively high-power base station such as a macro eNB, while the eNB 112 may be a relatively low-power base station, e.g., a pico eNB and/or femto eNB.In some embodiments, one or more additional eNBs, e.g., eNB 112, may be employed, e.g., in a HetNet configuration. In some embodiments, the eNBs of a NtNet may have different power and / or access classes. For example, in the eNB 112 may be a relatively low-power base station, e.g., a pico eNB and / or femto eNB.
[0013] eNB 112 may have a Pcell and one or more Scell(s) similar to eNB 104. However, the same CCs will not be used for Pcells for the two base stations of the HetNet. For example, if the eNB 104 has CC_0 for its Pcell and CC_1 for its Scell, eNB 112 may have CC_1 for its Pcell and CC_0 for its Scell.ENB 112 may have a Pcell and one or more Scell (s) to eNB 104. For example, if the eNB 104 has a CC_0 for its Pc and its CC_1 for its Scell.
[0014] The UE 108 may include a receiver module 120, a decoder module 124, a scheduling module 128, and a transmitter module 132 coupled with one another at least as shown. In some embodiments, the decoder module 124 and/or scheduling module 128 may be incorporated into the receiver module 120. Briefly, the decoder module 124 may operate to decode downlink transmissions received via the Pcell or the Scell, while the scheduling module may operate to identify transmissions, within the downlink, that are scheduled for the UE 108. The receiver module 120 and transmitter module 132 may each be further coupled with one or more of a plurality of antennas 132 of the UE 108.The UE 108 may include the receiver module 120, the decoder module 124, the scheduling module 128, and the transmitter module 132 coupled with one other at least as shown. 120. Briefly, the decoder module 120. Briefly, the decoder module 124 may be used as a decoder module. identify transmissions, within the UE 108. The receiver module 120 and transmitter module 132 of the UE 108.
[0015] The UE 108 may include any number of suitable antennas. In various embodiments, the UE 108 may include at least as many antennas as a number of simultaneous spatial layers or streams received by the UE 108 from the eNBs, although the scope of the present disclosure may not be limited in this respect. The number of simultaneous spatial layers or streams may also be referred to as transmission rank, or simply rank.The UE 108 may include any number of suitable antennas. In various embodiments, the UE 108 may include at least a number of antennas as a number of antimicrobials. The number of simultaneous spatial layers or streams may also be mentioned.
[0016] One or more of the antennas 132 may be alternately used as transmit or receive antennas. Alternatively, or additionally, one or more of the antennas 132 may be dedicated receive antennas or dedicated transmit antennas. [0017] eNB 104 may include receiver module 136, scheduling module 140, encoder module 144, and transmitter module 148 coupled with one another at least as shown. In some embodiments, scheduling module 140 and/or encoder module 144 may be incorporated into the transmitter module 148. Receiver module 136 and transmitter module 148 may each be further coupled with one or more of a plurality of antennas 152 of the eNB 104. The eNB 104 may include any number of suitable antennas. In various embodiments, the eNB 104 may include at least as many antennas as a number of simultaneous transmission streams transmitted to the UE 108, although the scope of the present disclosure may not be limited in this respect. One or more of the antennas 152 may be alternately used as transmit or receive antennas. Alternatively, or additionally, one or more of the antennas 152 may be dedicated receive antennas or dedicated transmit antennas.One or more of the antennas 132 may be alternatively used as transmitting or receiving antennas. Alternatively, or additionally, one or more of the antennas may be dedicated to an antenna or dedicated transmit antenna. ENB 104 may include receiver module 136, scheduling module 140, encoder module 144, and transmitter module 148 coupled with one other at least as shown. 148 of the eNB 104. The transponder module and the transducer module. eNB 104 may include any number of suitable antennas. In some embodiments, the eNB 104 may include at least many antennas as a number of simultaneous transmission streams to the UE. One or more of the antennas 152 may be alternately used as transmit or receive antennas. Alternatively, or additionally, one or more of the antennas may be dedicated to an antenna or dedicated transmit antenna.
[0018] Though not shown explicitly, the eNB 112 may include modules/components similar to those of the eNB 104. [0019] With cross-carrier scheduling of a physical downlink shared channel (PDSCH), downlink control information (DCI) transmitted in the Pcell may provide downlink grant information pertaining to the Pcell or one of the Scells. The downlink grant information may be an indication of a downlink resource of the PDSCH that is to include data directed to the UE 108 through the corresponding serving cell. The DCI may include a carrier indication field (CIF) whose value indicates to which serving cell the downlink grant information pertains.The cross-carrier scheduling of a physical downlink shared channel (PDSCH), downlink control information (DCI) transmitted in. the Pcell may provide downlink grant information. The downlink grant information may be a reference to the UE 108 through the corresponding serving cell. The DCI may include a carrier indication field (CIF).
[0020] Conventionally, cross-carrier scheduling is restricted to downlink grant information being only applicable to subframes in which the DCI is transmitted. For example, DCI transmitted in subframe 1 would apply only to subframe 1, though it could be any serving cell.Conventionally, cross-carrier scheduling is restricted to downlink grant information in the DCI. For example, DCI transmitted in subframe 1 would apply only to subframe 1, though it could be any serving cell.
[0021] Various embodiments provide for multi-subframe cross-carrier (MSCC) scheduling on PDSCH. This may allow for DCI transmitted in a first subframe of the Pcell, to be applicable to a second subframe in one of the Scells that occurs later in the frame sequence than the first subframe. The MSCC described herein may even be used with CCs having different TDD UL/DL configuration. In some embodiments, this MSCC scheduling may be supported without increasing the DCI overhead to avoid DCI detection performance degradation. This may be done, in part through provision of predetermined subframe pairings as will be described.Various embodiments provide for multi-subframe cross-carrier (MSCC) scheduling on PDSCH. This is a subset of the first subframe of the subframe. The MSCC described can be used with CCs having different TDD UL / DL configuration. In some embodiments, this MSCC scheduling may not be supported by DCI detection performance degradation. This may be done in the form of a sub-grammar.
[0022] MSCC scheduling may include predetermined subframe pairings (x, y) in each half radio frame. The pairings may include a first pairing (0, 3) and a second pairing (1,4). These particular pairings may provide equal processing latency between the paired subframes. However, other embodiments may include other pairings.The MSCC scheduling may include predetermined subframe pairings (x, y) in each half radio frame. The pairings may include a first pairing (0, 3) and a second pairing (1.4). These particular pairings may provide equal processing latency between the paired subframes. However, other embodiments may include other pairings.
[0023] Generally, the predetermined subframe pairings may provide the option of DCI, and DL grant information within the DCI, in particular, transmitted in x subframe of the Pcell, identifying a downlink resource in the y subframe of the Scell. In some embodiments, the subframe pairing may only be implemented in the event that specific TDD UL/DL configurations of the CCs prevent transmission of DL grant information according to the conventional mechanism, i.e., transmitting DL grant information for the Scell in the same subframe of the Pcell.Generally, the predetermined subframe pairings may provide the option of DCI, and in particular, in the subframe of the subcellramine of the Scell. In some embodiments, the subframe pairing may not be the only TDD UL / DL configurations of the CCS preventive transmission of DL grant information in the same subframe of the subframe. the Pcell.
[0024] Embodiments provide that if the Pcell subframe y is a DL subframe, then the DCI for subframe y will be transmitted at Pcell subframe y. However, if the the Pcell subframe y is an UL subframe, thereby preventing transmission of DL grant information, then the DCI for subframe y of the Scell will be transmitted at Pcell subframe x. This may be seen with reference to scenarios depicted in Figures 2(a) - 2(c).Embodiments provide that if the Pcell subframe, then the DCI for subframe will be transmitted at Pcell subframe y. However, if the Pcell subframe is an UL subframe, then the DCI for the subframe is the Ptw subframe of the cell. Depicted in Figures 2 (a) - 2 (c).
[0025] Figure 2(a) illustrates a scenario in which a Pcell has a TDD configuration 0 with subframe 0 being a downlink subframe (D), subframe 1 being a special subframe (S), and subframes 2-4 being uplink subframes (U). The TDD configurations may be defined by table 1 below.Figure 2 (a) illustrates a scenario in which the Pcell has the TDD configuration 0 with subframe 0 being a sublink subframe (D), subframe 1 being a special subframe (S), and subframes 2-4 being uplink subframes ( U). The TDD configurations may be defined by table 1 below.
Table 1Table 1
[0026] The special subframe may include three fields: downlink pilot time slot (DwPTS), which may include the DCI, guard period (GP), and uplink pilot time slot (UpPTS).The special subframe may include three fields: downlink pilot time slot (DwPTS), which may include the DCI, guard period (GP), and uplink pilot time slot (UpPTS).
[0027] The Scell of Figure 2(a) has a TDD configuration 1 with subframes 0 and 4 being downlink subframes, subframe 1 being a special subframe, and subframes 2 and 3 being uplink subframes.The Scell of Figure 2 (a) is TDD configuration 1 with subframes 0 and 4 being downlink subframes, and subframes 2 and 3 being uplink subframes.
[0028] In some embodiments, subframe 0 of the Pcell may include DCI that identifies a downlink resource in subframe 0 of the Scell. It may be noted that subframe pairing with respect to (0, 3) is not required given that the 3rd subframe of the Scell is an uplink subframe and, therefore, will not need DL grant information.In some embodiments, subframe 0 of the Pcell may include DCI that identifies a downlink resource in subframe 0 of the Scell. (0, 3) is not required DL grant information.
[0029] Subframe 1 of the Pcell may include DCI that identifies a downlink resource in subframe 1 of the Scell and/or subframe 4 of the Scell. Subframe pairing (1,4) may be implemented, in this case, because the subframe y of the Pcell, i.e., subframe 4, is an uplink subframe.Subframe 1 of the Pcell may include DCI that identifies a downlink resource in the subframe 1 of the Scell. Subframe pairing (1,4) may be implemented in this case, because the subframe y of the Pcell, i.e., subframe 4, is an uplink subframe.
[0030] Figure 2(b) illustrates a scenario in which a Pcell has a TDD configuration 0 with subframe 0 being a downlink subframe, subframe 1 being a special subframe, and subframes 2-4 being uplink subframes. The Scell has a TDD configuration 2 with subframes 0,3, and 4 being downlink subframes, subframe 2 being a special subframe, and subframe 2 being an uplink subframe.Figure 2 (b) illustrates the scenario in which the Pcell has the TDD configuration 0 with subframe 0 being a sublink subframe, subframe 1 being a special subframe, and subframes 2-4 being uplink subframes. The Scell has a TDD configuration 2 with subframes of 0.3, and 4 being a downlink subframe, being a special subframe, and being an uplink subframe.
[0031] Subframe 0 of the Pcell may include DCI that identifies a downlink resource in subframe 0 and/or subframe 3 of the Scell. The subframe pairing (0, 3) may be implemented in this case because the subframe y of the Pcell, i.e., subframe 3, is an uplink subframe. Unlike the scenario of Figure 2(a), subframe 3 of the Scell is a downlink subframe and may therefore receive a DL grant.Subframe 0 of the Pcell may include DCI that identifies a downlink resource in subframe 0 and / or subframe 3 of the Scell. The subframe pairing (0, 3) may be implemented in the subframe y of the Pcell, i.e., subframe 3, is an uplink subframe. Subframe 3 of the Scell is a downlink subframe and may therefore receive a DL grant.
[0032] Subframe 1 of the Pcell may include DCI that identifies a downlink resource in subframe 1 and/or subframe 4 of the Scell. The subframe pairing (1,4) may be implemented in this case because the subframe y of the Pcell, i.e., subframe 4, is an uplink subframe.Subframe 1 of the Pcell may include DCI that identifies a downlink resource in a subframe 1 and / or subframe 4 of the Scell. The subframe pairing (1,4) may be implemented in the subframe y of the Pcell, i.e., subframe 4, is an uplink subframe.
[0033] Figure 2(c) illustrates a scenario in which a Pcell has a TDD configuration 1 with subframes 0 and 4 being downlink subframes, subframe 1 being a special subframe, and subframes 2 and 3 being uplink subframes. The Scell has a TDD configuration 2 with subframes 0, 3, and 4 being downlink subframes, subframe 2 being a special subframe, and subframe 2 being an uplink subframe.Figure 2 (c) illustrates the scenario in which the Pcell has a TDD configuration 1 with subframes 0 and 4 being a downlink subframes, and a subframe being 2 and 3 being uplink subframes. The Scell has a TDD configuration 2 with subframes 0, 3, and 4 being a downlink subframes, being a special subframe, and subframe 2 being an uplink subframe.
[0034] Subframe 0 of the Pcell may include DCI that identifies a downlink resource in subframe 0 and/or subframe 3 of the Scell. The subframe pairing (0, 3) may be implemented in this case because the subframe y of the Pcell, i.e., subframe 3, is an uplink subframe and subframe 3 of the Scell is a downlink subframe.Subframe 0 of the Pcell may include DCI that identifies a downlink resource in subframe 0 and / or subframe 3 of the Scell. The subframe pairing (0, 3) may be implemented in the case of the subframe y of the Pcell, i.e., subframe 3, is an uplink subframe and subframe 3 of the Scell is a downlink subframe.
[0035] Subframe 1 of the Pcell may include DCI that identifies a downlink resource in subframe 1. The subframe pairing (1,4) may not be implemented in this case because the subframe y of the Pcell, i.e., subframe 4, is a downlink subframe. Therefore, subframe 4 of the Pcell may include DCI for subframe 4 of the Scell.Subframe 1 of the Pcell may include DCI that identifies a downlink resource in a subframe 1. The subframe pairing (1,4) may not be implemented in the case of the subframe y of the Pcell, ie, subframe 4, also a downlink subframe. Therefore, subframe 4 of the Pcell may include DCI for subframe 4 of the Scell.
[0036] MSCC scheduling may be facilitated by use of MSCC table 300 shown in Figure 3 in accordance with some embodiments. MSCC table 300 may include mapping information for individual combinations of 3-bit CIF values and carrier aggregation levels as shown. The carrier aggregation level may refer to how many CCs, or serving cells, are configured for communication between the eNB 104 and the UE 108. The values within MSCC table 300 include designated CC, e.g., CC_0, CC_1, CC_2, or CC_3, and subframe pairing index, e.g., 0 and/or 1.MSCC scheduling may be facilitated by the use of MSCC table 300 shown in Figure 3. MSCC table 300 may include mapping information for 3-bit CIF values and carrier aggregation levels as shown. The values within MSCC table 300 include the assigned CC, eg, CC_0, CC_1, CC_2, or CC_3, and subframe pairing index, eg, 0 and / or 1.
[0037] If DCI includes a CIF value of Ό00,’ the DCI information may pertain to the Pcell, i.e., CC_0. If DCI includes a CIF value of Ό01,’ the DCI information may pertain to the first subframe of the subframe pair of the Scell, CC_1. For example, with reference to Figure 2(b), if DCI was transmitted in subframe 0 of the Pcell and included a CIF value of Ό01,’ then the downlink grant information would identify a downlink resource in subframe 0 of the Scell. If the DCI was transmitted in subframe 1 of the Pcell and included the same CIF value, then the downlink grant information would identify a downlink resource in subframe 1 of the Scell.If DCI includes a CIF value of Ό00, 'the DCI information may pertain to the Pcell, i.e., CC_0. If DCI includes a CIF value of Ό01, 'the DCI information may be the first subframe of the subframe pair of the Scell, CC_1. For example, with reference to Figure 2 (b), if DCI was transmitted in subframe 0 of the Pcell and included in the CIF value of Ό01; If the DCI was transmitted in the subframe 1, then the downlink grant would be the same.
[0038] If DCI includes a CIF value of Ό10,’ the DCI information may pertain to the second subframe of the subframe pair of the Scell, CC_1. For example, with reference to Figure 2(b), if DCI was transmitted in subframe 0 of the Pcell and included a CIF value of Ό10,’ then the downlink grant information would identify a downlink resource in subframe 3 of the Scell. If the DCI was transmitted in subframe 1 of the Pcell and included the same CIF value, then the downlink grant information would identify a downlink resource in subframe 4 of the Scell.If DCI includes a CIF value of Ό10, 'the DCI information may be the second subframe of the subframe pair of the Scell, CC_1. For example, with reference to Figure 2 (b), if DCI was transmitted in subframe 0 of the Pcell and included in the CIF value of Ό10; If the DCI was transmitted in the subframe 1, the downlink grant is the same CIF value, then the downlink grant is the same.
[0039] If DCI includes a CIF value of Ό1T and the CA level is either two or three, the DCI information may pertain to the first and second subframes of the subframe pair of the Scell, CC_1. For example, with reference to Figure 2(b), if DCI transmitted in subframe 0 of the Pcell and included a CIF value of Ό11,’ then the downlink grant information would identify a downlink resource in both subframes 0 and 3 of the Scell.If DCI includes a CIF value of Ό1T and the CA level is either two or three, the DCI information may be the first and second subframes of the Scell, CC_1. For example, with reference to Figure 2 (b), if DCI transmitted in subframe 0 of the Pt and included in the CIF value of Ό11, then the downlink grant information would be 0 and 3 of the Scell.
[0040] If DCI includes a CIF value of Ό1T and the CA level is either four or five, the DCI information may pertain to the first subframe of the subframe pair of a second Scell, CC_2. The remaining mapping information may be interpreted in similar manners.If DCI includes a CIF value of Ό1T and the CA level, or the DCI information may be the first subframe of the subframe pair of a second Scell, CC_2. The remaining mapping information may be interpreted in similar manners.
[0041] The CIF in MSCC table 300 is provided as a 3-bit value in order to be compatible with existing 3-bit CIF fields of DCI in LTE REL 10. While the eight states provided by the 3-bit value may not be enough to include every possible combination of CC/subframe index, it may be sufficient to account for the majority of desired scheduling operations. [0042] In some embodiments, CIF may be represented by more or less than 3 bits. In the event that CIF is represented by more than 3 bits, trade-offs between DCI decoding efficiency and increased MSCC scheduling represented by additional CIF states may be considered.The CIF in MSCC table 300 is a 3-bit value in order to be compatible with existing 3-bit CIF fields of DCI in LTE REL 10. it is sufficient to establish a CC / subframe index; In some embodiments, CIF may be represented by more or less than 3 bits. CIF is also considered to be a CIF.
[0043] The values selected to be included in a particular table may reflect a particular Scell priority scheme. In general, the tables may reflect a bias toward lower-level Scells based on an assumption that the eNB 104 will likely schedule PDSCH of the lowest Scells first. This may be due to some deployment scenarios utilizing a lower frequency band for the first Scell than for the subsequent Scells. However, different Scell priority schemes may prioritize different Scells in different manners.The value selected to be included in a particular table may be the particular Scell priority scheme. In general, the tables may reflect a bias towards lower-level scales. This is due to the use of a lower frequency band for the first Scell. However, different Scells in different manners.
[0044] Tables 404 and 408 of Figure 4 reflect various Scell priority schemes, which illustrate some of the flexibility that may be incorporated into the design of tables used in various embodiments.Tables 404 and 408 of Figure 4 reflect various scell priority schemes, which illustrate some of the various uses in the design of tables.
[0045] Table 404 provides an Scell priority scheme in which the first Scell, CC_1, is prioritized. Therefore, each possible subframe pairing index, e.g., O’, ’T, and ’0,1’, is provided for each CA level. If the CA level is four or greater, then the dual subframe scheduling, i.e., scheduling both subframes of the pair, is not supported for the higher CCs, e.g., CC_2, CC_3 and CC_4. Furthermore, when the CA level is five, the scheduling of the second value of the subframe pair is not supported for either CC_3 or CC_4.Table 404 also provides priority. Therefore, each possible subframe pairing index, e.g., O ',' T, and '0.1' is provided for each CA level. If the CA level is four or greater, then the scheduling of the subframes of the pair is not supported for the higher CCs, e.g., CC_2, CC_3 and CC_4. Additionally, when the CA level is not the same as CC_3 or CC_4.
[0046] Table 408 provides an Scell priority scheme in which first and second Scells are prioritized if the CA level is four or greater. If the CA level is four, then only the first value of the subframe pair is supported for CC_3. If the CA level is five, then only the first value of the subframe pair is supported for CC_3 and CC_4, and the dual subframe scheduling is not supported for CC_2.Table 408 provides a Scell priority scheme for the first and second level. If the CA level is four, then only the value of the subframe pair is supported for CC_3. If the CA level is five, then the two subframe scheduling is not supported for CC_2.
[0047] Figure 5 illustrates an MSCC scheduling of a radio frame in which a Pcell and an Scell are configured for communication in accordancewith some embodiments. The radio frame isa 10 ms radio frame with PDSCH transmissions on subframes 0 and 6 of the Pcell and subframes 1,3, 4, 5, 6, and 8 of the Scell.[0047] Figure 5 illustrates an MSCC scheduling of a frame in which a cell is configured for communication in accordancewith some embodiments. The radio frame is a 10 ms radio frame with PDSCH transmissions on subframes 0 and 6 of the Pcell and subframes 1.3, 4, 5, 6, and 8 of the Scell.
[0048] Chart 504 illustrates specific DCI that include CIF values and associated indicators. The MSCC scheduling reflected in the embodiment of Figure 5 may be based on table 300.Chart 504 illustrates specific DCIs that include CIF values and associated indicators. The MSCC scheduling reflected in Figure 300.
[0049] Subframe 0 of the Pcell may include, e.g., in a PDCCH transmission, DCI 508 and 512. Each DCI may include a CIF value and an associated indicator. The indicator is shown as where ci is the carrier index, either 0 or 1, and si is the subframe index.Subframe 0 of the Pcell may include, e.g., in a PDCCH transmission, DCI 508 and 512. Each DCI may include a CIF value and an associated indicator. The index is shown as the index of the carrier, either 0 or 1, and is the subframe index.
[0050] DCI 508 may include a CIF value of 000 and an indicator /)(7/θ By reference to table 300, the indicator may identify a downlink resource of a PDSCH transmission in subframe 0 of the Pcell, i.e., carrier 0, that is to include data directed to the UE 108.DCI 508 may include a CIF value of 000 and an indicator /) (7 / θ By reference to table 300, the indicator may be a PDSCH 0 of the Pcell, ie, carrier 0, that is the UE 108.
[0051] DCI 512 may include a CIF value of 010 and an indicator The indicator may identify a downlink resource of a PDSCH transmission in subframe 3 of the Scell, i.e., carrier 1, that is to include data directed to the UE 108. [0052] Subframe 1 of the Pcell may include DCI 516. DCI 516 may include a CIF value of 011 and an indicator DCl\ 4 .DCI 512 may include a CIF value of 010. 0052] Subframe 1 of the Pcell may include DCI 516. DCI 516 may include a CIF value of 011 and an indicator DCl
The indicator of DCI 516 may identify a downlink resource of a PDSCH transmission in subframes 1 and 5 of the Scell. In this embodiment, the identified resource may be in the same position in both subframes.The indicator of DCI 516 may identify a downlink source of a PDSCH transmission in subframes 1 and 5 of the Scell. In the same position in both subframes.
[0053] Subframe 5 of the Pcell may include DCI 520. DCI 520 may include a CIF value of 011 and an indicator DCll o 5,0 ·Subframe 5 of the Pcell may include DCI 520. DCI 520 may include a CIF value of 011 and an indicator DCll o 5.0 ·
The indicator of DCI 520 may identify a downlink resource of a PDSCH transmission in subframes 5 and 8 of the Scell. [0054] Subframe 6 of the Pcell may include DCIs 524 and 528. DCI 524 may include a CIF value of 000 and an indicator DCI^ t° identify a downlink resource of a PDSCH transmission in subframe 6 of the Pcell. DCI 528 may include a CIF value of 001 and an indicator DC/^ to identify a downlink resource of a PDSCH transmission in subframe 6 of the Scell.The indicator of DCI 520 may identify a downlink resource of a PDSCH transmission in subframes 5 and 8 of the Scell. Subframe 6 of the Pcell may include DCIs 524 and 528. DCI 524 may include a CIF value of 000 and an indicator DCI ° identify a a link DS DS DS DS DS DS DS DCI 528 may include a CIF value of 001 and an indicator DC / ^ to identify a PDSCH transmission in subframe 6 of the Scell.
[0055] Figure 6 is a flowchart illustrating an operation 600 of a user equipment, e.g., UE 108, in accordance with some embodiments.Figure 6 is also a flowchart illustrating operation 600, a UE 108 in inert with some embodiments.
[0056] At block 604, the operation may include receiving downlink control information. The DCI may be received by a decoder module, e.g., decoder module 124, decoding resources within a PDCCH of a Pcell. In some embodiments, the decoder may blindly decode blocks within a particular search space to receive the DCI. Upon receipt of the DCI, the decoder module may then provide the DCI to a scheduling module, e.g., scheduling module 128.At block 604, the operation may include receiving downlink control information. The DCI may be decoder module 124, decoding resources within a PDCCH of a Pcell. In some embodiments, the decoder may be blindly decode blocks within the particular search space to receive the DCI. Upon receipt of the DCI, the decoder module may then provide the scheduling module, e.g., scheduling module 128.
[0057] At block 608, the operation 600 may include determining corresponding resource. In some embodiments, the determining may be performed by the scheduling module accessing a table and identifying a value within the table based on a CIF value of the DCI. The scheduling module may then identify a resource within a PDSCH that is to include data directed to the UE, based on the value from the table. This identification may be performed as described above. The scheduling module may communicate the identified resource to the decoding module.The block 608, operation 600 may include determining resource. In some embodiments, the determining may be the value of the DCI. The scheduling module may then be based on the value of the UE. This identification may be as described above. The scheduling module may be the communicated resource to the decoding module.
[0058] At block 612, the operation 600 may include receiving data. The receipt of the data may be performed by the decoder module decoding the resource of the PDSCH transmission identified by the scheduling module in block 608. [0059] Figure 7 is a flowchart illustrating an operation 700 of a base station, e.g., eNB 104, in accordance with some embodiments.At block 612, the operation 600 may include receiving data. Figure 7 is the flowchart illustrating the operation 700 of a base station, eg, eNB 104, \ t iniant with some embodiments.
[0060] At block 704, the operation 700 may include scheduling DCI and data. The scheduling may be done by a scheduling module, e.g., scheduling module 140, scheduling the DCI in a PDCCH of a first subframe of a Pcell and the data into a PDSCH of a second subframe of the Scell. The DCI may identify the downlink resource carrying the data in the PDSCH of the second subframe of the Scell.At block 704, operation 700 may include scheduling DCI and data. The scheduling may be done by a scheduling module, e.g., scheduling module 140, scheduling the DCI in a PDCCH of the first subframe of the Scell. The DCI may be the second subframe of the Scell.
[0061] At block 708, the operation 700 may include encoding DCI and data. The DCI and data may be encoded by an encoder module, e.g., encoder module 144, encoding the DCI in the PDCCH of the first subframe of a Pcell and the data in the PDSCH of the second subframe of the Scell. The DCI may be encoded as a 3-bit CIF value.At block 708, operation 700 may include encoding DCI and data. The encoder module is encoded by an encoder module, e.g., encoder module 144, encoding the DCI in the PDCCH of the first subframe of the Scell. The DCI may be encoded as a 3-bit CIF value.
[0062] At block 712, the operation 700 may include transmitting the DCI and the data. The DCI and the data may be transmitted by a transmitter module, e.g., transmitter module 148.At block 712, operation 700 may include transmitting the DCI and the data. The DCI and the data may be transmitted by a transmitter module, e.g., transmitter module 148.
[0063] The modules described herein may be implemented into a system using any suitable hardware and/or software to configure as desired. Figure 8 illustrates, for one embodiment, an example system 800 comprising one or more processor(s) 804, system control logic 808 coupled with at least one of the processor(s) 804, system memory 812 coupled with system control logic 808, non-volatile memory (NVM)/storage 816 coupled with system control logic 808, and a network interface 820 coupled with system control logic 808.[0063] The modules described herein may be in the following manner. 804, system control 812 coupled with system control logic 808, non-system processor 804, system control logic 808 -Volatile Memory (NVM) / storage 816 coupled with system control logic 808;
[0064] The processor(s) 804 may include one or more single-core or multi-core processors. The processor(s) 804 may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, baseband processors, etc.).The processor (s) 804 may include one or more single-core or multi-core processors. The processor (s) include 804 processors and dedicated processors (eg, graphics processors, application processors, baseband processors, etc.).
[0065] System control logic 808 for one embodiment may include any suitable interface controllers to provide for any suitable interface to at least one of the processor(s) 804 and/or to any suitable device or component in communication with system control logic 808.[0065] System control logic 808 for one purpose may include any suitable interface controllers to provide one or more of the processors (s) 804.
[0066] System control logic 808 for one embodiment may include one or more memory controller(s) to provide an interface to system memory 812. System memory 812 may be used to load and store data and/or instructions, for example, for system 800. System memory 812 for one embodiment may include any suitable volatile memory, such as suitable dynamic random access memory (DRAM), for example.System control logic 808 for one or more memory controller (s) 812. System memory 812 may be used for load and store data and / or instructions, for example, for system 800. System memory 812 for one-to-one volatile memory (DRAM), for example.
[0067] NVM/storage 816 may include one or more tangible, non-transitory computer-readable media used to store data and/or instructions, for example. NVM/storage 816 may include any suitable non-volatile memory, such as flash memory, for example, and/or may include any suitable non-volatile storage device(s), such as one or more hard disk drive(s) (HDD(s)), one or more compact disk (CD) drive(s), and/or one or more digital versatile disk (DVD) drive(s), for example.NVM / storage 816 may include one or more non-transitory computer-readable media and / or instructions, for example. NVM / storage 816 may include any non-volatile storage device (s), such as one or more hard disk drive (s) (HDD) (s)), one or more compact disk (s), and / or one or more digital versatile disk (DVD) drive (s), for example.
[0068] The NVM/storage 816 may include a storage resource physically part of a device on which the system 800 is installed or it may be accessible by, but not necessarily a part of, the device. For example, the NVM/storage 816 may be accessed over a network via the network interface 820.The NVM / storage 816 may include the following: a. For example, the NVM / storage 816 may be accessed over the network interface 820.
[0069] System memory 812 and NVM/storage 816 may respectively include, in particular, temporal and persistent copies of logic 824. The logic 824 may include instructions that when executed by at least one of the processor(s) 804 result in the system 800 implementing one or modules, e.g., decoder module 124, scheduling module 128, scheduling module 140, and/or encoder module 144, to perform corresponding operations described herein. In some embodiments, the logic 824, or hardware, firmware, and/or software components thereof, may additionally/alternatively be located in the system control logic 808, the network interface 820, and/or the processor(s) 804.System memory 812 and NVM / storage 816 may include, in particular, temporal and persistent copies of logic 824. The logic 824 may include instructions that when executed by the processor (s) 804 result in the system 800, scheduling module 128, scheduling module 140, and performer operations; In some embodiments, the logic 824, or hardware firmware, and / or software components, can be found in the system control logic 808, and / or the processor (s) 804.
[0070] System memory 812 and NVM/storage 816 may also include data that may be operated on, or otherwise used in conjunction with, the implemented modules. For example, one or more MSCC tables may be stored in system memory 812 and/or NVM/storage 816 and accessible by the modules for implementing MSCC scheduling operations described herein.System memory 812 and NVM / storage 816 may also include data that may be operated on, or otherwise used. MSCC tables may be stored in system memory 812 and / or NVM / storage 816 and / or MSM scheduling operations described here.
[0071] Network interface 820 may have a transceiver 822 to provide a radio interface for system 800 to communicate over one or more network(s) and/or with any other suitable device. The transceiver 822 may implement receiver module 120 and/or transmitter module 132. In various embodiments, the transceiver 822 maybe integrated with other components of system 800. For example, the transceiver 822 may include a processor of the processor(s) 804, memory of the system memory 812, and NVM/Storage of NVM/Storage 816. Network interface 820 may include any suitable hardware and/or firmware. Network interface 820 may include a plurality of antennas to provide a multiple input, multiple output radio interface. Network interface 820 for one embodiment may include, for example, a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.The network interface 820 may have a transceiver 822 to provide a transceiver. The transceiver 822 may be used as a transducer. 812 may include any suitable hardware and / or firmware. Network interface 820 may include a plurality of antennas to provide a multiple input, multiple output radio interface. Network interface 820 for one, may include, for example, a network adapter, a wireless network adapter, a telephone modem, and / or a wireless modem.
[0072] For one embodiment, at least one of the processor(s) 804 may be packaged together with logic for one or more controller(s) of system control logic 808. For one embodiment, at least one of the processor(s) 804 may be packaged together with logic for one or more controllers of system control logic 808 to form a System in Package (SiP). For one embodiment, at least one of the processor(s) 804 may be integrated on the same die with logic for one or more controller(s) of system control logic 808. For one embodiment, at least one of the processor(s) 804 may be integrated on the same die with logic for one or more controller(s) of system control logic 808 to form a System on Chip (SoC).For one one, at least one of the processor (s) 804 may be packaged together with logic for one or more controller (s). 804 may be packaged together with logic for one or more controllers of the system in package (SiP). For one-on-one, the least one of the processors (s) The system is a Chip (SoC).
[0073] The system 800 may further include input/output (I/O) devices 832. The I/O devices 832 may include user interfaces designed to enable user interaction with the system 800, peripheral component interfaces designed to enable peripheral component interaction with the system 800, and/or sensors designed to determine environmental conditions and/or location information related to the system 800.The I / O devices 832 may include user interfaces designed to enable user interaction with the system 800, peripheral component interfaces. the system 800, and / or sensors;
[0074] In various embodiments, the user interfaces could include, but are not limited to, a display (e.g., a liquid crystal display, a touch screen display, etc.), a speaker, a microphone, one or more cameras (e.g., a still camera and/or a video camera), a flashlight (e.g., a light emitting diode flash), and a keyboard.In various embodiments, the user interfaces could include, but are not limited to, the display (eg, liquid crystal display, touch screen display, etc.), the speaker, the microphone, one or more cameras (e.g. , still camera and / or video camera), flashlight (eg, light emitting diode flash), and a keyboard.
[0075] In various embodiments, the peripheral component interfaces may include, but are not limited to, a non-volatile memory port, an audio jack, and a powersupply interface.Other embodiments, the peripheral component interfaces may include, but are not limited to, a non-volatile memory port, and a powersupply interface.
[0076] In various embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the network interface 820 to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.In various embodiments, the sensors may include, but are not limited to, a sensor, an accelerometer, a proximity sensor, and a positioning unit. The positioning unit may also be part of a positioning network, eg global positioning system (GPS) satellite.
[0077] In various embodiments, the system 800 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system 800 may have more or less components, and/or different architectures.In various embodiments, the system 800 may be a computing device, such as a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system 800 may have more or less components, and / or different architectures.
[0078] In various embodiments, an apparatus, e.g., a UE, is described including a scheduling module configured to: receive, from a base station, DCI in a first subframe of a Pcell of the base station, the DCI to include a CIF value and an indicator to indicate a downlink resource of a PDSCH transmission that is to include data directed to the apparatus; and determine, based on a predetermined subframe pairing and the CIF value, that the PDSCH transmission is in a second subframe of an Scell. The apparatus may further include a decoder module configured to decode the downlink resource of the PDSCH transmission based on the indicator and said determination that the PDSCH transmission is in the second subframe of the Scell. The downlink resource may be a physical resource block in some embodiments. [0079] In some embodiments, the predetermined subframe pairing may be a pairing between two subframes in each half-radio frame. For example, the pairing may be a pairing of subframe 0 and 3 or of subframe 1 and 4.The DCI to include a CIF is a CIF for a variety of embodiments, an apparatus, eg, a UE, a base station, a DCI in a subframe. value and an indicator for a downlink resource; and determination, based on a predetermined subframe pairing and CIF value; The apparatus may include, in particular, a decoder module for the determination of the PDSCH transmission of the second subframe of the Scell. The downlink resource may be a physical resource block in some embodiments. In some embodiments, the predetermined subframe pairing may be in a half-radio frame. For example, the pairing may be a pairing of subframe 0 and 3 or of subframe 1 and 4.
[0080] In some embodiments, the scheduling module is further configured to access mapping information based on the CIF value and a carrier aggregation level; and determine, based on the mapping information, the indicator applies to a first paired subframe of the predetermined subframe pairing, a second paired subframe of the predetermined subframe pairing, or to both the first and second paired subframe of the predetermined subframe pairing. The mapping information may be stored in an MSCC table that provides mapping information for individual combinations of CIF values and carrier aggregation levels.[0080] In some embodiments, the scheduling module is further configured to be mapping information based on the CIF value; subframe pairing, subframe pairing, subframe pairing, subframe pairing, or subframe pairing. The mapping information may be stored in an MSCC table that provides mapping information for CIF values and carrier aggregation levels.
[0081] In some embodiments, the CIF value may be a 3-bit value having eight states; the carrier aggregation level may be two, three, four, or five; and the mapping information may identify the Pcell if the CIF value is a first state and the CA level is two, three, four or five; the first paired subframe of a first Scell if the CIF value is a second state and the CA level is two, three, four, or five; the second paired subframe of the first Scell if the CIF value is a third state and the CA level is two, three, four, or five; the first and second paired subframes of the first Scell if the CIF value is a fourth state and the CA level is two or three; the first paired subframe of a second Scell if the CIF value is the fourth state and the CA level is four or five; the first paired subframe of the second Scell if the CIF value is a fifth state and the CA level is three; the second paired subframe of the second Scell if the CIF value is the fifth state and the CA level is four or five; the second paired subframe of the second Scell if the CIF value is a sixth state and the CA level is three; the first paired subframe of a third Scell if the CIF value is the sixth state and the CA level is four or five; the first and second paired subframes of the second Scell if the CIF value is a seventh state and the CA level is three; the second paired subframe of the third Scell if the CIF value is the seventh state and the CA level is four or five; and the first paired subframe of a fourth Scell if the CIF value is an eighth state and the CA level is five.In some embodiments, the CIF value may be a 3-bit value having eight states; the carrier aggregation level may be two, three, four, or five; and the mapping information may be the same as the CIF value for the CIF value; the first level of the CIF is also the second level of the CIF value of two, three, four, or five; the second paired subframe of the cif value is the third level and the CA level is two, three, four, or five; the first and second stage of the CIF is the level two or three; the first paired subframe of the second level is the fourth level; the first paired subframe of the second CIF value is the fifth level; the second paired subframe is the second level of the CIF value; the second paired subframe of the second cif value is the sixth state and the CA level is three; the first one is the third level of the CIF value; the second and the second level are the seventh state and the CA level is three; the second paired subframe of the third level; and the first level of the CIF value is the eighth state and the CA level is five.
[0082] In some embodiments, the CIF value may be a 3-bit value having eight states; the carrier aggregation level may be two, three, four, or five; and the mapping information may identify: the primary serving cell if the CIF value is a first state and the CA level is two, three, four or five; the first paired subframe of a first Scell if the CIF value is a second state and the CA level is two, three, four, or five; the second paired subframe of the first Scell if the CIF value is a third state and the CA level is two, three, four, or five; the first and second paired subframes of the first Scell if the CIF value is a fourth state and the CA level is two, three, four, or five; the first paired subframe of a second Scell if the CIF value is a fifth state and the CA level is three, four, or five; the second paired subframe of the second Scell if the CIF value is a sixth state and the CA level is three, four, or five; the first and second paired subframes of the second Scell if the CIF value is the seventh state and the CA level is three; the first paired subframe of a third Scell if the CIF value is the seventh state and the CA level is four or five; the second paired subframe of the third Scell if the CIF value is an eighth state and the CA level is four; and the first paired subframe of the fourth Scell ifthe CIF value is the eighth state and the CA level is five. [0083] In some embodiments, the CIF value may be a 3-bit value having eight states; the carrier aggregation level may be two, three, four, or five; the Scell may be a first Scell; and the mapping information may identify: the primary serving cell if the CIF value is a first state and the CA level is two, three, four or five; the first paired subframe of a first Scell ifthe CIF value is a second state and the CA level is two, three, four, or five; the second paired subframe of the first Scell ifthe CIF value is a third state and the CA level is two, three, four, orfive; the first and second paired subframes of the first Scell ifthe CIF value is a fourth state and the CA level is two, three, four, orfive; the first paired subframe of a second Scell ifthe CIF value is a fifth state and the CA level is three, four, orfive; the second paired subframe of the second Scell ifthe CIF value is a sixth state and the CA level is three, four, orfive; the first and second paired subframes of the second Scell ifthe CIF value is the seventh state and the CA level is three; the first and second paired subframes of the second Scell ifthe CIF value is the seventh state and the CA level is four; the first paired subframe of a third Scell ifthe CIF value is the seventh state and the CA level is five; the first paired subframe of the third Scell ifthe CIF value is an eighth state and the CA level is four; and the first paired subframe of the fourth Scell ifthe CIF value is the eighth state and the CA level is five.In some embodiments, the CIF value may be a 3-bit value having eight states; the carrier aggregation level may be two, three, four, or five; and the mapping information may be identified as the first level of the CIF value is two, three, four or five; the first level of the CIF is also the second level of the CIF value of two, three, four, or five; the second paired subframe of the cif value is the third level and the CA level is two, three, four, or five; the second level is the second level of the cif value of two, three, four, or five; the first paired subframe of a second cf value is the fifth state and the CA level is three, four, or five; the second paired subframe of the second cif value is the sixth state and the CA level is three, four, or five; the second and the second level is the second level; the first paired subframe of a third level; the second paired subframe of the third level; cif value is the eighth state and the CA level is five. In some embodiments, the CIF value may be a 3-bit value having eight states; the carrier aggregation level may be two, three, four, or five; the Scell may be the first Scell; and the mapping information may be identified as the first level of the CIF value is two, three, four or five; the first paired subframe of a CIF value is the second state and the CA level is two, three, four, or five; the second paired subframe of the first CIF value is a third, four or three; the first and second pairs of cif value are the two, three, four, orfive; the first paired subframe of a second cf value is the fifth, four, orfive; the second paired subframe of the second cf value is the sixth state and the CA level is three, four, orfive; the first and second paired subframes of the second level; the second and the second level are the CIF value is the seventh state and the CA level is four; a cif value is the seventh state and the CA level is five; the first one is the CIF value of the eighth state and the CA level is four; cif value is the eighth state and the CA level is five.
[0084] In some embodiments, the scheduling module may be configured to determine that the PDSCH transmission is in the second subframe of the secondary serving cell based further on a predetermined subframe pairing of the first subframe and the second sub frame.In some embodiments, the scheduling module may be configured to determine the second sub frame of the second sub frame.
[0085] In some embodiments, the Pcell and the Scell may include respective component carriers having different TDD configurations.In some embodiments, there are different TDD configurations.
[0086] In some embodiments, a plurality of component carriers are aggregated for communication between the apparatus and the base station and the scheduling module is further configured to determine that the PDSCH transmission is in the second subframe of the secondary serving cell based further on a number of the plurality of component carriers.[0086] In some embodiments, a plurality of component carriers are aggregated for the purpose of determining the PDSCH transmission of the second subframe. number of the plurality of component carriers.
[0087] In some embodiments, the Pcell utilizes a first common carrier and the Scell utilizes a second common carrier. [0088] In some embodiments, the scheduling module may be further configured to access mapping information in an MSCC table based on the CIF value and a carrier aggregation level; determine that the PDSCH transmission is in the second subframe based on the mapping information; and determine, based on the mapping information, that another PDSCH transmission of a third subframe of the secondary serving cell is also to include data directed to the apparatus. [0089] In other embodiments, an apparatus, e.g., an eNB, is described to include a scheduling module configured to: schedule DCI in a PDCCH of a first subframe of a first component carrier of a plurality of component carriers aggregated for communication between a user equipment and a base station; and schedule data for the user equipment in a PDSCH of a second subframe of a second component carrier of the plurality of component carriers, wherein the DCI is configured to identify the second subframe of the second component carrier and the second subframe occurs later in a frame sequence then the first subframe; and an encoder module configured to encode the DCI in the PDCCH and the data in the PDSCH.In some embodiments, the Pcell utilizes a second common carrier. In some embodiments, the scheduling module may be further configured to include mapping information in an MSCC table; determine that the PDSCH transmission is the second subframe based on the mapping information; and determining, based on the mapping information, another PDSCH transmission. DCI in a PDCCH user equipment and a base station; a second subframe of the second subframe of the second subframe of the second subframe of the second subframe of the second subframe. sequence then the first subframe; and an encoder module in the PDCCH and the data in the PDSCH.
[0090] In some embodiments, the transmitter module may be configured to transmit the DCI in the PDCCH and the data in the PDSCH.In some embodiments, the transmitter module may be configured to transmit the DCI in the PDCCH and the data in the PDSCH.
[0091] In some embodiments, the encoder module may be configured to encode the DCI to include a CIF value, e.g., with 3-bits, to identify the second subframe and the second component carrier.In some embodiments, the encoder module may be configured to encode the DCI, i.e., with 3-bits, to the second subframe and the second component carrier.
[0092] In some embodiments, a method is described to include identifying a downlink resource, in a first subframe of a first component carrier of a plurality of component carriers, that is to include data directed to a user equipment based on DCI received in a second subframe of a second component carrier of the plurality of component carriers, wherein the second subframe occurs earlier in a frame sequence than the first subframe; and decoding the downlink resource to receive data directed to the user equipment.[0009] In some embodiments, a method is described in the present invention. second subframe of the second subframe of component carriers; and decoding the downlink.
[0093] In some embodiments, the method may include accessing an MSCC table to retrieve mapping information based on a CIF value in the DCI and a carrier aggregation level; and identifying the downlink resource based on the mapping information.[0093] In some embodiments, the method may include accessing an MSCC table for retrieve mapping information based on a CIF value; and the downlink resource based on the mapping information.
[0094] In some embodiments, one or more computer-readable media having instructions that, if executed by one or more processors, cause an apparatus to perform various methods described herein.[0094] In some embodiments, one or more computer-readable media has instructions that, if executed by one or more processors, perform various methods described herein.
[0095] Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein.Though, a wide variety of alternate and / or equivalent implementations or implementations have been illustrated. the present disclosure. This application is intended to cover any of the implementations discussed herein.
Claims 1. A user equipment (108) comprising: a scheduling module (128) configured to: receive, from a base station, downlink control information, DCI, in a first subframe of a primary serving cell, PCell, of the base station (104), the DCI to include a carrier indication field, CIF, value and an indicator to indicate a downlink resource of a physical downlink shared channel, PDSCH, transmission that is to include data directed to the user equipment (108); access mapping information based on the CIF value and a carrier aggregation level, wherein the carrier aggregation level indicates how many component carriers are configured between the base station and the user equipment; determine, based on a predetermined subframe pairing and the CIF value, that the PDSCH transmission is in a subframe of a secondary serving cell, Scell, wherein the predetermined subframe pairing comprises a first paired subframe and a second paired subframe of the Scell, both paired to the first subframe of the Pcell; determine, based on the mapping information, whether the indicator applies to the first paired subframe of the predetermined subframe pairing, the second paired subframe of the predetermined subframe pairing, or to both the first and second paired subframes of the predetermined subframe pairing; and a decoder module (124) configured to decode the downlink resource of the PDSCH transmission based on the indicator and said determination that the PDSCH transmission is in a subframe of the Scell. 2. The user equipment (108) of claim 1, wherein the predetermined subframe pairing is a pairing between two subframes in a half-radio frame. 3. The user equipment (108) of claim 2, wherein the predetermined subframe pairing is a pairing of subframes 0 and 3 or of subframes 1 and 4. 4. The user equipment (108) of claim 1 wherein the mapping information is stored in a multi-subframe cross-carrier, MSCC, table (300) that provides mapping information for individual combinations of CIF values and carrier aggregation levels. 5. The user equipment (108) of any of the preceding claims, wherein: the Pcell and the Scell include respective component carriers having different time-division duplexing, TDD, configurations; or a plurality of component carriers are aggregated for communication between the user equipment and the base station (104) and the scheduling module (128) is further configured to: determine that the PDSCH transmission is in the second subframe of the secondary serving cell based further on a number of the plurality of component carriers; or the downlink resource is a physical resource block. 6. A method comprising: receiving, from a base station, downlink control information, DCI, in a first subframe of a primary serving cell, Pcell, of the base station (104), the DCI to include a carrier indication field, CIF, value and an indicatorto indicate a downlink resource of a physical downlink shared channel, PDSCH, transmission that is to include data directed to a user equipment (108); accessing mapping information based on the CIF value and a carrier aggregation level, wherein the carrier aggregation level indicates how many component carriers are configured between the base station and the user equipment; determining, based on a predetermined subframe pairing and the CIF value, that the PDSCH transmission is in a subframe of a secondary serving cell, Scell, wherein the predetermined subframe pairing comprises a first paired subframe and a second paired subframe of the Scell, both paired to the first subframe of the Pcell; determining, based on the mapping information, whether the indicator applies to the first paired subframe of the predetermined subframe pairing, the second paired subframe of the predetermined subframe pairing, or to both the first and second paired subframes of the predetermined subframe pairing; and decoding the downlink resource of the PDSCH transmission based on the indicator and said determination that the PDSCH transmission is in a subframe of the Scell. 7. The method of claim 6, further comprising: identifying (608) the downlink resource based on a predetermined subframe pairing that pairs two subframes in each half-radio frame and, optionally, the predetermined subframe pairing pairs subframes 0 and 3 or sub-frames 1 and 4. 8. One or more computer-readable media having instructions that, if executed by one or more processors, cause a user equipment to perform a method of any of claims 6 to 7.Claims 1. The user equipment (108) includes: a scheduling module (128) configured to: receive, from a base station, downlink control information, DCI, of the base station ( 104), a DCI to include a carrier indication field, CIF, value and an indicator for a downlink resource; access mapping information based on the level of the carrier aggregation level; a subtrame of subframe of the subframe of the subframe, a paired subframe of the subframe. the first subframe of the Pcell; subframe pairing; subframe pairing; subframe pairing; subframe pairing; and a decoder module (124) configured for decoding the PDSCH. 2. The user equipment (108) of claim 1, wherein the predetermined subframe pairing is a half-radio frame. 3. The user equipment (108) of claim 2, which is a mapping information is stored in. a multi-subframe cross-carrier, MSCC, table (300), providing mapping information for individual combinations of CIF values and carrier aggregation levels. 5. The user equipment (108) of any of the claims, including the time-division duplexing, TDD, configurations; or a plurality of component carriers (104) and the scheduling module (128) is further configured to determine the PDSCH transmission of the second subframe. is a number of the plurality of component carriers; or the downlink resource is a physical resource block. 6. A method: receiving, from a base station, downlink control information, DCI, in the first subframe of the primary station (104); value and an indicatorto indicate a downlink resource of a downlink shared channel, PDSCH; accessing mapping information based on the CIF value of the carrier aggregation level; a subtrame of subframe of the subframe of the subframe, a paired subframe of the subframe of the scell, both paired the first subframe of the Pcell; subframe pairing; subframe pairing; subframe pairing; and decoding the downlink resource of the PDSCH. Subframes of subframes in each half-radio frame and subframes of subframes 0 and 3 or sub- frames 1 and 4. 8. One or more computer-readable media with instructions that, if executed by one or more processors 6 to 7.
Patentansprüche 1. Endgerät (108), das Folgendes umfasst: ein Planungsmodul (128), das konfiguriert ist: von einer Basisstation Abwärtsstreckensteuerinformationen, DCI, in einem ersten Subrahmen einer primären Versorgungszelle, PCeil, der Basisstation (104) zu empfangen, wobei die DCI einen Trägerkennungsfeldwert, CIF-Wert, und einen Indikator enthalten sollen, um eine Abwärtsstreckenressource einer Übertragung über einen physischen, gemeinsam genutzten Abwärtsstreckenkanal, PDSCH, anzuzeigen, die Daten enthalten soll, die an das Endgerät (108) gerichtet sind; auf Abbildungsinformationen auf Basis des CIF-Werts und eines Trägeraggregationspegels zuzugreifen, wobei der Trägeraggregationspegel anzeigt, wieviele Komponententrägerzwischen der Basisstation und dem Endgerät konfiguriert sind; auf Basis einer vorbestimmten Subrahmenkopplung und des CIF-Werts zu ermitteln, dass die PDSCH-Übertragung in einem Subrahmen einer sekundären Versorgungszelle, Scell, ist, wobei die vorbestimmte Subrahmenkopplung einen ersten gekoppelten Subrahmen und einen zweiten gekoppelten Subrahmen der Scell umfasst und beide an den ersten Subrahmen der Pcell gekoppelt sind; auf Basis der Abbildungsinformationen zu ermitteln, ob der Indikator für den ersten gekoppelten Subrahmen der vorbestimmten Subrahmenkopplung, den zweiten gekoppelten Subrahmen der vorbestimmten Subrahmenkopplung oder sowohl für den ersten als auch den zweiten gekoppelten Subrahmen der vorbestimmten Subrahmenkopplung gilt; und ein Dekodiermodul (124), das konfiguriert ist, die Abwärtsstreckenressource der PDSCH-Übertragung auf Basis des Indikators und der Ermittlung zu dekodieren, dass sich die PDSCH-Übertragung in einem Subrahmen der Scell befindet. 2. Endgerät (108) nach Anspruch 1, wobei die vorbestimmte Subrahmenkopplung eine Kopplung zwischen zwei Subrahmen in einem halben Funkrahmen ist. 3. Endgerät (108) nach Anspruch 2, wobei die vorbestimmte Subrahmenkopplung eine Kopplung von Subrahmen 0 und 3 oder von Subrahmen 1 und 4 ist. 4. Endgerät (108) nach Anspruch 1, wobei die Abbildungsinformationen in einer trägerübergreifenden Mehrfach-Subrahmen-Tabelle (300), MSCC-Ta-belle, gespeichert sind, die Informationen für individuelle Kombinationen von CIF-Werten und Trägeraggregationspegeln bereitstellt. 5. Endgerät (108) nach einem der vorangehenden Ansprüche, wobei: die Pcell und die Scell jeweilige Komponententräger enthalten, die verschiedene Zeitduplexkonfigurationen, TDD-Konfigurationen, aufweisen; oder eine Vielzahl von Komponententrägern zur Kommunikation zwischen dem Endgerät und der Basisstation (104) aggregiert sind und das Planungsmodul (128) ferner konfiguriert ist: auf weiterer Basis einer Anzahl der Vielzahl der Komponententräger zu ermitteln, dass die PDSCH-Übertragung im zweiten Subrahmen der sekundären Versorgungszelle ist; oder die Abwärtsstreckenressource ein physischer Ressourcenblock ist. 6. Verfahren, das Folgendes umfasst:Patentansprüche 1. Endger (108), das Folgendes umfasst: ein Planungsmodul (128), das configurator: Einer Basisstation Abwärtsstreckensteuerinformationen, DCI, in einem erner, Subrahmen einer primer for Versorgung, PCeil, der Basisstation (104) zu empfangen, wobei die DCI et al. auf Abbildungsinformationen auf Basis des CIF-Werts und eigenbiggings; auf Basis einer vorbestimmt Subrahmenkopplung und des CIF-Werts zu ermitteln, dass die PDSCH-Übertragung in einem Subrahmen einer secondary Versorgung, Scell, wobei die vorbestimmte Subrahmenkopplung een erste gekoppelten Subrahmen der Pcell gekoppelt you; auf Basis der Abbildungsinformationen zu ermitteln, ob der Indikator Gebopen, Subrahmen der vorbestimmten Subrahmen der vorbestimmten; und ein Decodermodule (124), configured, d Abs abrärtsstreckenressource der PDSCH-Übertragung auf Basis des Indik and der Ermittlung zu dekodieren, dass sich die PDSCH-Übertragung in einem Subrahmen der Scell. 2. Endgers (108) nach Anspruch 1, wobei die vorbestimmte Subrahmenkopplung eine Kopplung zwischen zwei Subrahmen in einem fish in Funkrahmen. 3. Endgers (108) nach Anspruch 2, w / w as a sub-strain of Subrahmenkopplung e. 4. Endgers (108) nach Anspruch 1, wobei die Abbildungsinformationen in einer trägerübergreifenden Mehrfach-Subrahmen-Tabelle (300), MSCC-Ta-belle, gespeichert you, die Information for individual combinations of CIF-Werten und Trägeraggregationspegeln bereitstell. 5. Endgers (108) nach einem der vorangehenden Ansprüche, w / w: die Pcell und die Scell juvenile, Compound concentrator, die verschiedene, Zeitduplexconfiguration, TDD-Konfiguration, aufweisen; barrel or compound component of the communication system (104) from the configurator and / or sounder module (128): Versorgungszelle ist; oder die Abwärtsstreckenressource ein physischer Ressourcenblock ist. 6. Verfahren, das Folgendes umfasst:
Empfangen von Abwärtsstreckensteuerinformationen, DCI, von einer Basisstation in einem ersten Subrahmen einer primären Versorgungszelle, PCeil, der Basisstation (104), wobei die DCI einen Trägerkennungsfeldwert, CIF-Wert, und einen Indikator enthalten sollen, um eine Abwärtsstreckenressource einer Übertragung über einen physischen, gemeinsam genutzten Abwärtsstreckenkanal, PDSCH, anzuzeigen, die Daten enthalten soll, die an ein Endgerät (108) gerichtet sind;Empfangen von Abwärtsstreckensteuerinformationen, DCI, von einer Basisstation in einem erbe, subrahmen einer primer for Versorgung, PCeil, der Basisstation (104), w / w DCI et al. gemeinsam genutzten Abwärtsstreckenkanal, PDSCH, anzuzeigen, die Daten enthalten soll, die an ein Endgerät (108) gerichtet sind;
Zugreifen auf Abbildungsinformationen auf Basis des CIF-Werts und eines Trägeraggregationspegels, wobei der Trägeraggregationspegel anzeigt, wie viele Komponententräger zwischen der Basisstation und dem Endgerät konfiguriert sind;Zugreifen auf Abbildungsinformationen auf Basis des CIF-Werts und eigen trägeraggregationspegels, wobei der Trägeraggregationspegel anzeigt, wo.
Ermitteln auf Basis einer vorbestimmten Subrahmenkopplung und des CIF-Werts, dass die PDSCH-Übertragung in einem Subrahmen einer sekundären Versorgungszelle, Scell, ist, wobei die vorbestimmte Subrahmenkopplung einen ersten gekoppelten Subrahmen und einen zweiten gekoppelten Subrahmen der Scell umfasst und beide an den ersten Subrahmen der Pcell gekoppelt sind;A subbrahimplopung and des CIF-Werts, dass die PDSCH-Übertragung in einem Subrahmen einer secondary to Versorgung, Scell. der Pcell gekoppelt you;
Ermitteln auf Basis der Abbildungsinformationen, ob der Indikator für den ersten gekoppelten Subrahmen der vorbestimmten Subrahmenkopplung, den zweiten gekoppelten Subrahmen der vorbestimmten Subrahmenkopplung oder sowohl für den ersten als auch den zweiten gekoppelten Subrahmen der vorbestimmten Subrahmenkopplung gilt; undA subbrahimencopplung, subbrahimencopplung, or sowohl für den erb a nd a nd a nd i n g a ll g m o u g h o m u n a nd a nd a nd a nd g e s g m o n s subrahmen der vorbestimmten Subrahmenkopplung gilt; und
Dekodieren der Abwärtsstreckenressource der PDSCH-Übertragung auf Basis des Indikators und der Ermittlung, dass sich die PDSCH-Übertragung in einem Subrahmen der Scell befindet. 7. Verfahren nach Anspruch 6, das ferner Folgendes umfasst:The decoder der Abwärtsstreckenressource der PDSCH-Übertragung auf Basis des Indikators und der Ermittlung, dass sich die PDSCH-Übertragung in einem Subrahmen der Scell. 7. Verfahren nach Anspruch 6, das ferner Folgendes umfasst:
Identifizieren (608) der Abwärtsstreckenressource auf Basis einer vorbestimmten Subrahmenkopplung, die zwei Subrahmen in jedem halben Funkrahmen koppelt, und wobei die vorbestimmte Subrahmenkopplung optional die Subrahmen 0 und 3 oder die Subrahmen 1 und 4 koppelt. 8. Computerlesbares Medium oder mehrere computerlesbare Medien, das bzw. die Anweisungen aufweist bzw. aufweisen, die bewirken, wenn sie von einem oder mehreren Prozessoren ausgeführt werden, dass ein Endgerät ein Verfahren nach einem der Ansprüche 6 bis 7 ausführt.Identifizieren (608) der Abwärtsstreckenressource auf Basis einer vorbestimmten Subrahmenkopplung, die zwei in subrahmen in jedem fish. 8. Computerlesbares Medium or mehrere computerlesbare Medien, das bzw. die Anweisungen aufweist bzw. aufweisen, die bewirken, wenn sie von einem oder marerenen Prozessoren ausgeführt werden, dass ein Endgerät ein Verfahren nach einem der Ansprüche 6 bis 7 ausführt.
Revendications 1. Équipement utilisateur (108) comprenant : un module de planification (128) configuré pour : recevoir, en provenance d’une station de base, des informations de commande de liaison descendante, DCI (Downlink Control Information), dans une première sous-trame d’une cellule de desserte primaire, PCell, de la station de base (104), les DCI devant comprendre une valeur de Champ d’indication de Porteuse, CIF (Carrier Indication Field), et un indicateur devant indiquer une ressource de liaison descendante d’une transmission de canal partagé de liaison descendante physique, PDSCH (Physical Downlink Shared Channel), qui doit comprendre des données destinées à l’équipement utilisateur (108) ; des informations de mise en correspondance des accès ayant pour base la valeur CIF et un niveau d’agrégation de porteuses, dans lequel le niveau d’agrégation de porteuses indique combien de porteuses constitutives sont configurées entre la station de base et l’équipement utilisateur ; déterminer, sur la base d’un appariement de sous-trame prédéterminé et de la valeur CIF, que la transmission du PDSCH s’effectue dans une sous-trame d’une cellule de desserte secondaire, Scell, dans lequel l’appariementde sous-trames prédéterminé comprend une première sous-trame appariée et une deuxième sous-trame appariée de la cellule Scell, toutes deux appariées à la première sous-trame de la cellule Pcell ; déterminer, sur la base des informations de mise en correspondance, si l’indicateurs’applique à la première sous-trame appariée de l’appariement de sous-trames prédéterminé, à la deuxième sous-trame appariée de l’appariement de sous-trames prédéterminé, ou à la fois aux première et deuxième sous-trames appariées de l’appariementde sous-trames prédéterminé ; et un module décodeur (124) configuré pour décoder la ressource de liaison descendante de la transmission PDSCH sur la base de l’indicateur et de ladite détermination du fait que la transmission du PDSCH s’effectue dans une sous-trame de la cellule Scell. 2. Équipement utilisateur (108) selon la revendication 1, dans lequel l’appariement de sous-trames prédéterminé est un appariement entre deux sous-trames dans une demi-trame radio. 3. Équipement utilisateur (108) selon la revendication 2, dans lequel l’appariement de sous-trames prédéterminé est un appariement de sous-trames 0 et 3 ou de sous-trames 1 et 4. 4. Équipement utilisateur (108) selon la revendication 1, dans lequel les informations de mise en correspondance sont stockées dans une table inter-porteuses multi-sous-trames, MSCC (Multi-Subframe Cross-Carrier), (300) qui fournit des informations de mise en correspondance pour des combinaisons individuelles de valeurs CIF et de niveaux d’agrégation de porteuses. 5. Équipement utilisateur (108) selon l’une quelconque des revendications précédentes, dans lequel : la cellule Pcell et la cellule Scell comprennent des porteuses constitutives respectives ayant différentes configurations de duplexage par répartition temporelle, TDD (Time Division Duplexing) ; ou une pluralité de porteuses constitutives sont agrégées pour une communication entre l’équipement utilisateur et la station de base (104), et le module de planification (128) est en outre configuré pour : déterminer que la transmission du PDSCH s’effectue dans la deuxième sous-trame de la cellule de desserte secondaire en se fondant en outre sur le nombre de la pluralité de porteuses constitutives ; ou la ressource de liaison descendante est un bloc de ressources physiques. 6. Procédé consistant à : recevoir, en provenance d’une station de base, des informations de commande de liaison descendante, DCI, dans une première sous-trame d’une cellule de desserte primaire, Pcell, de la station de base (104), les DCI devant comprendre une valeur de champ d’indication de porteuse, CIF, et un indicateur devant indiquer une ressource de liaison descendante d’une transmission de canal partagé de liaison descendante physique, PDSCH, devant comprendre des données destinées à un équipement utilisateur (108) ; accéder à des informations de mise en correspondance sur la base de la valeur CIF et d’un niveau d’agrégation de porteuses, dans lequel le niveau d’agrégation de porteuses indique combien de porteuses constitutives sont configurées entre la station de base et l’équipement utilisateur ; déterminer, sur la base d’un appariement de sous-trames prédéterminé et de la valeur CIF, que la transmission du PDSCH s’effectue dans une sous-trame d’une cellule de desserte secondaire, Scell, dans lequel l’appariement de sous-trames prédéterminé comprend une première sous-trame appariée et une deuxième sous-trame appariée de la cellule Scell, toutes deux appariées à la première sous-trame de la cellule Pcell ; déterminer, sur la base des informations de mise en correspondance, si l’indicateur s’applique à la première sous-trame appariée de l’appariement de sous-trames prédéterminé, à la deuxième sous-trame appariée de l’appariement de sous-trames prédéterminé, ou à la fois aux première et deuxième sous-trames appariées de l’appariement de sous-trames prédéterminé ; et décoder la ressource de liaison descendante de la transmission PDSCH sur la base de l’indicateur et de ladite détermination du fait que la transmission du PDSCH s’effectue dans une sous-trame de la cellule Scell. 7. Procédé selon la revendication 6, consistant en outre à : identifier (608) la ressource de liaison descendante sur la base d’un appariement de sous-trames prédéterminé qui apparie deux sous-trames dans chaque demi-trame radio et, facultativement, l’appariement de sous-trames prédéterminé apparie les sous-trames 0 et 3 ou les sous-trames 1 et 4. 8. Un ou plusieurs supports lisibles par ordinateur portant des instructions qui, si elles sont exécutées par un ou plusieurs processeurs, amènent un équipement utilisateur à mettre en oeuvre un procédé selon l’une quelconque des revendications 6 à 7.Revendications 1. Équipement utilisateur (108) comprenant: and de facto de dementation des dendendante, dans une première sous -trame d'une cellule de desserte primaire, PCell, de la station de base (104), les DCI devant comprendre une valeur de Champ d'indication de Porteuse, CIF (Carrier Indication Field), et un indicatedur devant indiquer une ressource de descendante d'une transmission de canal partagé de liaison descendante physique, PDSCH (Physical Downlink Shared Channel), qui doit comprendre des données destinées à l'équipement utilisateur (108); des informations de mise en correspondence des accès de la c lé de dé le déagration, dans lequel le niveau d'agrégation de porteuse indique combien de porteuse constitutives sont configurées entre la station de l'équipement utilisateur; determiner, sur la base d'unqué de sous-trame preteret et de la valeur CIF, que la transmission du PDSCH s'effectue dans une sous-trame d'une cellule de desserte secondaire, Scell, dans lequel l'appariementde sous- trames prédéterminé comprend une première sous-trame appariée and une deuxième sous-trame appariée de la cellule Scell, toutes deux appariées à la première sous-trame de la cellule Pcell; determiner, sur la base des informations de l'appariement de sous-trame apparée de l'appariement de sous-trame appariée de l'appariement de sous-trames preeteterine, ou à la fois aux première et deuxième sous-trames appariées de l'appariementde sous-trames; et un module décodeur (124) configuré pour décoder la ressource de liaison descendante de la transmission de l'indicateur et de ladite determination de fe que la transmission du PDSCH s'effectue dans une sous-trame de la cellule Scell. 2. Equipement utilisateur (108) selon la revendication 1, dans lequel l'appariement de sous-trames prédéterminé est and appariement entre deux sous-trames dans une demi-trame radio. 3. Équipement utilisateur (108) selon la revendication 2, dans lequel l'appariement de sous-trames prédeterminé and appariement de sous-trames 0 et 3 ou de sous-trames 1 et 4. 4. Équipement utilisateur (108) selon la revendication 1, dans lequel les informations de m en lance sont stockées dans une table intertexte multi-sous-trames, MSCC (Multi-Subframe Cross-Carrier), (300) qui fournit des informations de correspondence pour des combinaisons individelles de valeurs CIF et de niveaux d'agrégation de porteuses. 5. Equipement utilisateur (108) selon lon quelconque des revendications précédentes, dans lequel: cell cell Pcell et la cellule Scell comprennent des porteuses constitutives respectives ayant differe configurations de duplexage for répartition temporelle, TDD (Time Division Duplexing); ou une pluralité de porteuses constitutives sont agrégées pour une communication entre l'équipement utilisateur et la station de base (104), deuxième sous-trame de la cellule de desserte de la pluralité de porteuses de la pluralité de porteuses constitutives; ou la ressource de liaison descendante est and bloc de ressources physiques. 6. Procédé consistant à: recevoir, en provenance d'une station de base, des informations de liaison descendante, DCI, dans une première sous-trame d'une cellule de desserte primaire, Pcell de la station de base (104) ), ddd devant comprendre une valeur de champ d'indication de porteuse, cif, et al., and denotation of the transplantation of the ductal descendante descendante physique, PDSCH, devant comprendre des données destinées à un équipement utilisateur (108); dé le dé le niveau d'agrégation de porteuses, dans lequel le niveau d'agrégation de porteuse indique combien de porteuse de porteuse indique combien de porteuses constitutives sont configurées entre la station de base et l ' équipement utilisateur; determiner, sur la base d'unqué de sous-trames, CIF, que la transmission du PDSCH s'effectue dans une sous-trame d'une cellule de desserte secondaire, Scell, dans lequel l'appariement de sous -trames prédéterminé comprend une première sous-trame appariée and une deuxième sous-trame appariée de la cellule Scell, toutes deux appariées à la première sous-trame de la cellule Pcell; determiner, sur la base des informations de la l'appariement de sous-trame apparée de l'appariement de sous-trame appariée de l'appariement de sous- trames prédeterminé, ou à la fois aux première et deuxième sous-trames appariées de l'appariement de sous-trames; et de dé de dé de dé de lée de l'indicateur et de ladite determination de fe ration de l'indicateur et de ladite de la cellule de la sou-trame de la cellule Scell. 7. Procédé selon la revendication 6, identifier (608) la ressource de liaison descendante sur la base d'un appariement de sous-trames prédéterminé qui apparie deux sous-trames dans chaque demi-trame radio et, facultativement, l'appariement de sous-trames prédéterminé apparie les sous-trames 0 et 3 ou les sous-trames 1 et 4. 8. Un ou plusieurs supports lisibles on ordinateur portant des instructions qui, si elles sont exécutées par un ou plusieurs processeurs, amènent un équipement utilisateur à mettre en oeuvre and procédé selon l'une quelconque des revendications 6 à 7.
REFERENCES CITED IN THE DESCRIPTIONREFERENCES CITED IN THE DESCRIPTION
This list of references cited by the applicant is for the reader’s convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.This is a list of references for the reader. It does not form part of the European patent document. Even though they have been taken in compiling the references, errors or omissions cannot be ruled out.
Non-patent literature cited in the description • Data scheduling in CA with different TDD UL-DL con figurations. 3GPP DRAFT; R1-113082 TDD DATA SCHEDULING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 04 October2011, vol. RAN WG1,20111010 [0003]Non-patent literature references in the description • Data scheduling in CA with different TDD UL-DL con figurations. 3GPP DRAFT; R1-113082 TDD DATA SCHEDULING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 04 October2011, vol. RAN WG1,20111010
Claims (8)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161556109P | 2011-11-04 | 2011-11-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
HUE035205T2 true HUE035205T2 (en) | 2018-05-02 |
Family
ID=47561765
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
HUE12846449A HUE035600T2 (en) | 2011-11-04 | 2012-03-28 | Small data techniques and configurations in a wireless communication network |
HUE12846485A HUE035205T2 (en) | 2011-11-04 | 2012-03-28 | Downlink resource scheduling |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
HUE12846449A HUE035600T2 (en) | 2011-11-04 | 2012-03-28 | Small data techniques and configurations in a wireless communication network |
Country Status (7)
Country | Link |
---|---|
JP (10) | JP2016059062A (en) |
CN (3) | CN105871429B (en) |
CA (1) | CA2932387C (en) |
HK (3) | HK1216465A1 (en) |
HU (2) | HUE035600T2 (en) |
MY (2) | MY175550A (en) |
RU (5) | RU2632902C1 (en) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017075828A1 (en) | 2015-11-06 | 2017-05-11 | 华为技术有限公司 | Method and device for device-to-device inter-cell interference cancellation |
CN107295624B (en) * | 2016-03-30 | 2021-11-26 | 日本电气株式会社 | Node synchronization method and node adopting same |
US9882640B1 (en) * | 2016-10-28 | 2018-01-30 | Wipro Limited | Visible light communication personal area network coordinator (VPANC) and associated method for selecting suitable VPANCs |
CN110603777B (en) * | 2017-05-05 | 2022-09-13 | 苹果公司 | Signaling of channel state information reference signal (CSI-RS) mapping configuration for New Radio (NR) systems |
US10425900B2 (en) | 2017-05-15 | 2019-09-24 | Futurewei Technologies, Inc. | System and method for wireless power control |
MX2020002662A (en) * | 2017-09-11 | 2020-07-22 | Ericsson Telefon Ab L M | Unified ul and dl beam indication. |
US11284316B2 (en) * | 2018-02-07 | 2022-03-22 | Qualcomm Incorporated | Mobile device centric clustering in wireless systems |
US11765720B2 (en) * | 2018-02-23 | 2023-09-19 | Interdigital Holdings, Inc. | System and method for bandwidth part operation |
US11617193B2 (en) | 2018-05-11 | 2023-03-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Control signalling for a repeated transmission |
US11956762B2 (en) * | 2018-09-28 | 2024-04-09 | At&T Intellectual Property I, L.P. | Facilitating improved performance in advanced networks with multiple transmission points |
Family Cites Families (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5261106A (en) * | 1991-12-13 | 1993-11-09 | S-Mos Systems, Inc. | Semaphore bypass |
US6956814B1 (en) * | 2000-02-29 | 2005-10-18 | Worldspace Corporation | Method and apparatus for mobile platform reception and synchronization in direct digital satellite broadcast system |
US7492828B2 (en) * | 2004-06-18 | 2009-02-17 | Qualcomm Incorporated | Time synchronization using spectral estimation in a communication system |
RU2382497C2 (en) * | 2005-06-30 | 2010-02-20 | Нокиа Корпорейшн | Device, method and computer software for operation of transmission antenna with feedback for systems using several antennae |
US8787344B2 (en) * | 2006-08-30 | 2014-07-22 | Qualcomm Incorporated | Method and apparatus for ACKCH with repetition in orthogonal systems |
US8837380B2 (en) * | 2006-11-01 | 2014-09-16 | Qualcomm Incorporated | Method and apparatus for cell search in an orthogonal wireless communication system |
CN100474101C (en) * | 2007-04-10 | 2009-04-01 | 苏州苏大维格数码光学有限公司 | Projection screen having image plane holographic structure |
EP2169856A4 (en) * | 2007-06-19 | 2014-11-05 | Ntt Docomo Inc | Base station device and communication control method |
EP2213046B1 (en) * | 2007-09-14 | 2018-07-04 | NEC Corporation | Method and system for optimizing network performances |
US8498647B2 (en) * | 2008-08-28 | 2013-07-30 | Qualcomm Incorporated | Distributed downlink coordinated multi-point (CoMP) framework |
EP2359630B1 (en) * | 2008-09-30 | 2013-07-17 | Telefonaktiebolaget L M Ericsson (PUBL) | Methods and apparatuses for detecting radio link failure in a telecommunications system |
WO2010039066A1 (en) * | 2008-09-30 | 2010-04-08 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and arrangements for dynamically adjusting the rate of sub cell searching in coordinated multiple point transmission/reception, comp, cells |
KR101481591B1 (en) * | 2008-12-03 | 2015-01-12 | 엘지전자 주식회사 | A method of transmitting and receiving a downlink reference signal in a wireless communication system having multiple antennas |
US8755807B2 (en) * | 2009-01-12 | 2014-06-17 | Qualcomm Incorporated | Semi-static resource allocation to support coordinated multipoint (CoMP) transmission in a wireless communication network |
CN101777941B (en) * | 2009-01-12 | 2014-10-08 | 华为技术有限公司 | Downlink mode of transmission, network devices and wireless device in the coordinated multiple-point transmission systems |
US20100189038A1 (en) * | 2009-01-23 | 2010-07-29 | Runhua Chen | Circuit and method for mapping data symbols and reference signals for coordinated multi-point systems |
CN101790188B (en) * | 2009-01-24 | 2014-10-08 | 华为技术有限公司 | Time offset adjusting method and user terminal |
JP2010258612A (en) * | 2009-04-22 | 2010-11-11 | Sharp Corp | Radio communication system, base station device, control method, program, and recording medium |
US20110158164A1 (en) * | 2009-05-22 | 2011-06-30 | Qualcomm Incorporated | Systems and methods for joint processing in a wireless communication |
JP2011023942A (en) * | 2009-07-15 | 2011-02-03 | Ntt Docomo Inc | Radio base station apparatus and modulating/coding scheme selecting method |
CN101626269A (en) * | 2009-08-17 | 2010-01-13 | 中兴通讯股份有限公司 | Downlink synchronous emission control method and system |
KR101367570B1 (en) * | 2009-09-27 | 2014-02-26 | 엘지전자 주식회사 | Method and apparatus of transmitting reference signal in wireless communication system |
KR20110040672A (en) * | 2009-10-12 | 2011-04-20 | 주식회사 팬택 | Method and device for transmitting and receiving control information in wireless communication system |
US8948028B2 (en) * | 2009-10-13 | 2015-02-03 | Qualcomm Incorporated | Reporting of timing information to support downlink data transmission |
US9042840B2 (en) * | 2009-11-02 | 2015-05-26 | Qualcomm Incorporated | Cross-carrier/cross-subframe indication in a multi-carrier wireless network |
CN102056206B (en) * | 2009-11-04 | 2015-06-10 | 中兴通讯股份有限公司 | Self-organization operation processing method and device |
US10111111B2 (en) * | 2009-11-19 | 2018-10-23 | Qualcomm Incorporated | Per-cell timing and/or frequency acquisition and their use on channel estimation in wireless networks |
WO2011071291A2 (en) * | 2009-12-07 | 2011-06-16 | 엘지전자 주식회사 | Method for transmitting a sounding reference signal in an uplink comp communication system, and apparatus for same |
WO2011075867A1 (en) * | 2009-12-23 | 2011-06-30 | Telefonaktiebolaget L M Ericsson (Publ) | Base station synchronisation |
US20110176461A1 (en) * | 2009-12-23 | 2011-07-21 | Telefonakatiebolaget Lm Ericsson (Publ) | Determining configuration of subframes in a radio communications system |
KR20110083443A (en) * | 2010-01-12 | 2011-07-20 | 김용우 | Spring Balance with Pulley |
CN101800593A (en) * | 2010-01-18 | 2010-08-11 | 北京东方信联科技有限公司 | Device and method for shaping TD-SCDMA radio frame signal |
US8305987B2 (en) * | 2010-02-12 | 2012-11-06 | Research In Motion Limited | Reference signal for a coordinated multi-point network implementation |
KR20130020885A (en) * | 2010-03-23 | 2013-03-04 | 인터디지탈 패튼 홀딩스, 인크 | Efficient signaling for machine type communication |
US8897228B2 (en) * | 2010-04-26 | 2014-11-25 | Sharp Kabushiki Kaisha | Mobile communication system, base station apparatus, mobile station apparatus and communication method |
JP5647676B2 (en) * | 2010-04-28 | 2015-01-07 | 京セラ株式会社 | Wireless communication system, high power base station, wireless terminal, low power base station, and wireless communication method |
CN102238595B (en) * | 2010-04-30 | 2014-02-26 | 华为技术有限公司 | Method and equipment for processing cell outage |
CN101924610B (en) * | 2010-08-02 | 2012-12-26 | 西安电子科技大学 | Method for designing and distributing channel state information reference signal (CSI-RS) in LTE-A (Long Term Evolution-Advanced) system |
CN101908937B (en) * | 2010-08-20 | 2012-12-26 | 西安电子科技大学 | Signal detecting method in downlink distribution type MIMO-OFDM (Multiple Input Multiple Output-Orthogonal Frequency Division Multiplexing) system |
CN102143593B (en) * | 2011-03-25 | 2013-09-11 | 电信科学技术研究院 | Combined adaptive resource allocation method and device for PDCCH (Physical Downlink Control Channel) |
EP3182624B1 (en) * | 2011-09-23 | 2018-08-01 | Lg Electronics Inc. | Method for transmitting control information and apparatus for same |
-
2012
- 2012-03-20 CA CA2932387A patent/CA2932387C/en active Active
- 2012-03-28 HU HUE12846449A patent/HUE035600T2/en unknown
- 2012-03-28 HU HUE12846485A patent/HUE035205T2/en unknown
- 2012-03-28 RU RU2016117322A patent/RU2632902C1/en active
- 2012-03-28 MY MYPI2014701048A patent/MY175550A/en unknown
- 2012-03-28 MY MYPI2014701068A patent/MY168109A/en unknown
- 2012-03-29 RU RU2016118360A patent/RU2643660C1/en active
- 2012-03-29 CN CN201610276115.2A patent/CN105871429B/en active Active
- 2012-06-05 CN CN201710477754.XA patent/CN107257252B/en active Active
- 2012-06-05 CN CN201510751241.4A patent/CN105337644B/en active Active
- 2012-06-05 RU RU2015138682A patent/RU2612411C2/en active
-
2015
- 2015-12-02 JP JP2015235687A patent/JP2016059062A/en active Pending
- 2015-12-25 JP JP2015254691A patent/JP6100878B2/en active Active
-
2016
- 2016-02-15 JP JP2016026362A patent/JP6267732B2/en active Active
- 2016-03-23 JP JP2016058055A patent/JP6279642B2/en active Active
- 2016-04-15 HK HK16104318.9A patent/HK1216465A1/en unknown
- 2016-10-24 HK HK16112166.5A patent/HK1224094A1/en unknown
- 2016-11-17 JP JP2016223861A patent/JP6371361B2/en active Active
- 2016-12-13 JP JP2016240783A patent/JP6326122B2/en active Active
-
2017
- 2017-02-21 RU RU2017105634A patent/RU2656234C1/en active
- 2017-02-23 JP JP2017032731A patent/JP6424398B2/en active Active
- 2017-12-22 JP JP2017246314A patent/JP6501210B2/en active Active
-
2018
- 2018-01-17 JP JP2018005414A patent/JP6726815B2/en active Active
- 2018-01-19 RU RU2018102117A patent/RU2669781C1/en active
- 2018-07-05 HK HK18108679.1A patent/HK1249286A1/en unknown
- 2018-07-12 JP JP2018132002A patent/JP6542439B2/en active Active
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
HUE035205T2 (en) | Downlink resource scheduling | |
US9019850B2 (en) | CSI reporting for multiple carriers with different system configurations | |
US10727920B2 (en) | Dynamic CSI-RS transmission for enhanced FD-MIMO | |
EP2774300B1 (en) | Downlink resource scheduling | |
US10631308B2 (en) | Methods and devices for data transmission without grant during measurement gap | |
US12113733B2 (en) | Processing relaxation for aperiodic CSI-RS | |
EP3058789B1 (en) | Downlink control management in an unlicensed or shared spectrum | |
US8934350B2 (en) | Channel state information feedback for carrier aggregation with flexible carrier configurations | |
KR101754281B1 (en) | Transmission point indication in coordinated multi-point system | |
WO2020131373A1 (en) | Small data transfer over configured grants for asynchronous non-orthogonal multiple access | |
WO2014071638A1 (en) | Channel state information reporting method, user equipment and base station thereof | |
US20170034843A1 (en) | Scheduler methods for data aggregation over multiple links | |
US20240406891A1 (en) | Method and device for time and phase synchronization between base stations in network cooperative communication | |
US10285172B2 (en) | Search space design for semi-persistent scheduling (SPS) in enhanced machine-type communications | |
EP3371911A1 (en) | Csi report for mtc operation | |
US11564210B2 (en) | Two stage control channel for peer to peer communication | |
KR101311627B1 (en) | Method for configuring phich carrier linkage | |
CN108293245B (en) | A data communication method, terminal device and network device | |
US20230371024A1 (en) | Methods for interference measurements and reporting in sidelink | |
US20140204863A1 (en) | Method of Reducing Reference Signals and Communication Device thereof | |
AU2015261598B2 (en) | Downlink resource scheduling | |
WO2023092275A1 (en) | Harq codebook and feedback for multi-pdsch repetitions |