[go: up one dir, main page]

CN108683485B - Method and device for dynamically configuring UL/DL frame resource of TDD transmission - Google Patents

Method and device for dynamically configuring UL/DL frame resource of TDD transmission Download PDF

Info

Publication number
CN108683485B
CN108683485B CN201810332068.8A CN201810332068A CN108683485B CN 108683485 B CN108683485 B CN 108683485B CN 201810332068 A CN201810332068 A CN 201810332068A CN 108683485 B CN108683485 B CN 108683485B
Authority
CN
China
Prior art keywords
configuration
harq
network node
reference configuration
downlink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810332068.8A
Other languages
Chinese (zh)
Other versions
CN108683485A (en
Inventor
阿列克谢·胡尔耶夫
安德烈·切尔夫雅科夫
米哈伊尔·施洛夫
符仲凯
何宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Intel Corp
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority claimed from CN201380064664.8A external-priority patent/CN104885389B/en
Publication of CN108683485A publication Critical patent/CN108683485A/en
Application granted granted Critical
Publication of CN108683485B publication Critical patent/CN108683485B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/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
    • 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/0417—Feedback 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/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • 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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/0012—Hopping in multicarrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0016—Time-frequency-code
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • 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/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • 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/0058—Allocation criteria
    • H04L5/0062—Avoidance of ingress interference, e.g. ham radio channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0092—Indication of how the channel is divided
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • 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
    • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/762—Media network packet handling at the source 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431—Key distribution or pre-distribution; Key agreement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • 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/32—Hierarchical cell structures
    • 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/10—Scheduling measurement reports ; Arrangements for measurement reports
    • 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/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00692—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • 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/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • 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
    • 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/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/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • 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
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • H04W74/00—Wireless channel access
    • 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/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • 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/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • 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
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/24—Key scheduling, i.e. generating round keys or sub-keys for block encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80—Wireless
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • 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/0058—Allocation criteria
    • H04L5/0076—Allocation utility-based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/14—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
    • 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
    • Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
    • Y02B70/00—Technologies for an efficient end-user side electric power management and consumption
    • Y02B70/30—Systems integrating technologies related to power network operation and communication or information technologies for improving the carbon footprint of the management of residential or tertiary loads, i.e. smart grids as climate change mitigation technology in the buildings sector, including also the last stages of power distribution and the control, monitoring or operating management systems at local level
    • 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)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Technology Law (AREA)
  • Databases & Information Systems (AREA)
  • Environmental & Geological Engineering (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文涉及TDD传输的UL/DL帧资源动态配置的方法和装置。公开了用户设备(UE)中的装置、eNodeB的装置、非暂态机器可读存储介质、UE和网络节点。

Figure 201810332068

This document relates to a method and apparatus for dynamic configuration of UL/DL frame resources for TDD transmission. An apparatus in a user equipment (UE), an apparatus of an eNodeB, a non-transitory machine-readable storage medium, a UE, and a network node are disclosed.

Figure 201810332068

Description

Method and device for dynamically configuring UL/DL frame resource of TDD transmission
The present application is a divisional application of the inventive patent application having an application date of 2013, 10/8, and an application number of 201380064664.8 (international application number of PCT/US2013/063793), entitled "dynamic configuration of Uplink (UL) and Downlink (DL) frame resources for Time Division Duplex (TDD) transmission".
Technical Field
The present application relates to dynamic configuration of Uplink (UL) and Downlink (DL) frame resources for Time Division Duplex (TDD) transmissions.
Background
Wireless mobile communication technology uses various standards and protocols to communicate data between a node, such as a transmitting station or transceiver node, and a wireless device, such as a mobile device. Some wireless devices communicate using Orthogonal Frequency Division Multiple Access (OFDMA) in Downlink (DL) transmissions and single carrier frequency division multiple access (SC-FDMA) in Uplink (UL) transmissions. Standards and protocols for signal transmission using Orthogonal Frequency Division Multiplexing (OFDM) include the third generation partnership project (3GPP) Long Term Evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE)802.16 standards (e.g., 802.16e, 802.16m), which are colloquially referred to by the industry community as WiMAX (worldwide interoperability for microwave access), and the IEEE802.11 standard, which is colloquially referred to by the industry community as WiFi.
In a 3GPP Radio Access Network (RAN) LTE system, a Node may be a combination of an evolved universal terrestrial radio access network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB or eNB) and a Radio Network Controller (RNC), which communicates with wireless devices, referred to as User Equipment (UE). Downlink (DL) transmissions may be communications from a node (e.g., eNodeB) to a wireless device (e.g., UE), and Uplink (UL) transmissions may be communications from the wireless device to the node.
In a homogeneous network, nodes (also referred to as macro nodes) may provide basic radio coverage for wireless devices in a cell. A cell may be an area in which a wireless device is operable to communicate with a macro node. Heterogeneous networks (hetnets) can be used to handle the increased traffic load on macro nodes due to the increased density of deployed cells. Hetnets may include a planned high power macro node (or macro-eNB) layer overlaid with a layer of lower power nodes (small-eNB, micro-eNB, pico-eNB, femto-eNB, or home eNB (henb)) that may be deployed within the coverage area (cell) of the macro node in a less planned or even completely uncoordinated manner. The Lower Power Nodes (LPNs) may be generally referred to as "low power nodes," small nodes, or small cells.
Macro nodes may be used for basic coverage. Low power nodes may be used to fill coverage holes, increase capacity at hot zone or boundaries between coverage areas of macro nodes, improve indoor coverage where building structures obstruct signal transmission. Inter-cell interference coordination (ICIC) or enhanced ICIC (eicic) may be used for resource coordination to reduce interference between nodes, such as macro nodes and low power nodes in a HetNet.
Homogeneous networks or hetnets may use Time Division Duplexing (TDD) or Frequency Division Duplexing (FDD) for DL or UL transmissions. Time Division Duplexing (TDD) is an application of Time Division Multiplexing (TDM) to separate downlink and uplink signals. In TDD, the downlink signal and the uplink signal may be carried on the same carrier frequency, where the downlink signal uses a different time interval than the uplink signal so that the downlink signal and the uplink signal do not interfere with each other. TDM is a type of digital multiplexing in which two or more bit streams or signals (e.g., downlink or uplink) appear to be transmitted simultaneously as sub-channels in one communication channel, but are physically transmitted on different time resources. In Frequency Division Duplexing (FDD), uplink and downlink transmissions may operate using different frequency carriers. In FDD, DL-UL interference can be avoided because the downlink signal uses a different frequency carrier than the uplink signal.
Disclosure of Invention
In one exemplary aspect, the present application provides a User Equipment (UE) for dynamically reconfiguring an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration, having computer circuitry configured to: receiving a UL-DL reconfiguration indicator from a node, the reconfiguration indicator for dynamically reconfiguring a flexible subframe (FlexSF) from a semi-static UL-DL configuration to a different UL-DL transmission direction, wherein the FlexSF is capable of changing the UL-DL transmission direction; applying DL channel timing based on a DL favorable UL-DL configuration, wherein the DL favorable UL-DL configuration includes more DL subframes for the UE than a semi-static UL-DL TDD configuration; and applying UL channel timing based on the UL-favorable UL-DL configuration, wherein the UL-favorable UL-DL configuration includes more UL subframes for the UE than the semi-static UL-DL TDD configuration.
Drawings
The features and advantages of the present disclosure will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, the features of the present disclosure; and wherein:
fig. 1 illustrates a diagram relating to the use of dynamic uplink-downlink (UL-DL) reconfiguration in a Time Division Duplex (TDD) system, according to an example;
fig. 2 shows a diagram relating to a legacy Long Term Evolution (LTE) frame structure 2(FS2) with flexible subframes (FlexSF), according to an example;
fig. 3 shows a table (table 2) for hybrid automatic repeat request (HARQ) timing for a set of legacy Long Term Evolution (LTE) uplink-downlink (UL-DL) Time Division Duplex (TDD) configurations, according to an example;
fig. 4 illustrates a diagram relating to flexible subframes (flexsfs) in a set of legacy Long Term Evolution (LTE) uplink-downlink (UL-DL) Time Division Duplex (TDD) configurations, according to an example;
fig. 5 illustrates a diagram relating to hybrid automatic repeat request (HARQ) operation for a User Equipment (UE) with dynamic uplink-downlink (UL-DL) reconfiguration, according to an example;
fig. 6 depicts a flow diagram for a behavioral model for a User Equipment (UE) and an evolved Node B (eNB) with dynamic uplink-downlink (UL-DL) reconfiguration in a Long Term Evolution (LTE) Time Division Duplex (TDD) network, according to an example;
fig. 7 depicts a flow diagram for a method of dynamically reconfiguring an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration by an evolved Node B (eNB), according to an example;
fig. 8 depicts computer circuitry of a User Equipment (UE) operable to dynamically reconfigure an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration, according to an example;
fig. 9 illustrates a block diagram of a node (e.g., eNB) and a wireless device (e.g., UE) according to an example; and
fig. 10 shows a diagram of a wireless device (e.g., UE) according to an example.
Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended.
Detailed Description
Detailed Description
Before the present invention is disclosed and described, it is to be understood that this invention is not limited to the particular structures, process steps, or materials disclosed herein, but extends to equivalents thereof as would be recognized by those ordinarily skilled in the relevant art. It should also be understood that the techniques employed herein are for the purpose of describing particular examples only and are not intended to be limiting. Like reference symbols in the various drawings indicate like elements. The numerals provided in the flowcharts and steps are provided for clarity in illustrating the steps and operations and do not necessarily indicate a particular order or sequence.
Example embodiments
A preliminary overview of technical embodiments is provided below, followed by a more detailed description of specific technical embodiments. This preliminary summary is intended to assist the reader in understanding the present technology more quickly, and is not intended to identify key features or essential features of the present technology, nor is it intended to limit the scope of the claimed subject matter.
Time Division Duplexing (TDD) may provide flexible deployment without using a pair of spectrum resources. For TDD deployments, interference between Uplink (UL) and Downlink (DL) transmissions, including base-station-to-base-station (BS-to-BS) interference and UE-to-UE interference, may be considered when different uplink-downlink (UL-DL) configurations are used between cells in the network.
Fig. 1 illustrates a hierarchical HetNet deployment with different node transmission powers using Time Division Duplexing (TDD). The Node transmission power may refer to power generated by a Node type, such as a macro Node (e.g., a macro evolved Node B (eNB)) in a macro cell and a plurality of low power nodes (LPNs or small enbs) in a corresponding small cell. A cell, as used herein, may refer to a node or a coverage area of a node. The macro node may transmit at a higher power level (e.g., about 5 watts (W) to 40W) to cover the macro cell. Hetnets can be overlaid by Low Power Nodes (LPNs) that can transmit at much lower power levels, such as about 100 milliwatts (mW) to 2W. In an example, the available transmission power of the macro node may be at least ten times the available transmission power of the low power node. LPNs may be used in hot spots or hot zones, which refer to areas of wireless devices, such as User Equipment (UE), with high wireless traffic loads or large numbers of active transmissions. The LPN may be used in a micro cell, a pico cell, a femto cell, and/or a home network. Small cell 0 shows that wireless devices (e.g., UEs) heavily use downlink traffic, and small cell 1 shows that wireless devices heavily use uplink traffic. In the FDD example, the macro cell may use frequency band F1 for DL and F2 for UL, and the small cell may use frequency band F3 for DL and F4 for UL. In the TDD example, frequency band F1 (or F2) may be used by macro cells for DL or UL, and frequency band F3/F4 may be used by small cells for DL and UL. In another example, the macro cell and the small cell may use the same frequency band F1, F2, F3, or F4.
In some examples, allowing adaptive UL-DL configuration, which depends on traffic conditions in different cells, may significantly improve system performance. In the example shown in fig. 1, different UL-DL configurations may be considered in different cells. A network, such as a HetNet or homogeneous network, may involve the same carrier or different carriers deployed in the same frequency band by a single operator or different operators and in the same or different uplink-downlink (UL-DL) configurations. Different UL-DL configurations may be used by different cells in the network (e.g., HetNet), and different carriers deployed by different operators in the same frequency band may be used by employing the same or different uplink-downlink configurations. Interference may include adjacent channel interference (when different carrier frequencies are used) as well as co-channel interference (when the same carrier frequency is used), such as remote node-to-node interference (or BS-to-BS interference or eNB-to-eNB interference).
Various Radio Access Technologies (RATs), such as legacy (legacy) LTE TDD Release (Release)8, 9, 10, or 11 and advanced (advance) LTE TDD Release 12, may support asymmetric UL-DL allocations by providing uplink-downlink configurations of seven different semi-static configurations (i.e., legacy UL-DL TDD configurations). The legacy UL-DL TDD configuration may refer to the UL-DL TDD configuration described in LTE TDD release 8, 9, 10, or 11. Table 1 shows seven UL-DL configurations used in LTE, where "D" represents a downlink subframe, "S" represents a special subframe, and "U" represents an uplink subframe. In an example, the special subframe may function as or be treated as a downlink subframe.
Figure BDA0001628234780000061
TABLE 1
As shown in table 1, UL-DL configuration 0 may include 6 uplink subframes ( subframes 2,3,4, 7, 8, and 9) and 4 downlink and special subframes ( subframes 0, 1, 5, and 6); UL-DL configuration 5 may include one uplink subframe (subframe 2) and 9 downlink and special subframes ( subframes 0, 1, 3-9).
The legacy LTE UL-DL TDD configuration set may provide 40% -90% DL subframe allocation and 10% -60% UL subframe allocation as shown in table 1. At any given moment, the semi-static allocation may not match the instantaneous traffic situation. One mechanism for changing UL-DL allocations may be based on a system information change procedure in which UL and DL subframe allocations within a radio frame may be reconfigured by system information broadcast signaling, such as system information block 1(SIB 1). Thus, the configured UL-DL allocations can be expected to change semi-statically. For the SIB1 based mechanism, a minimum delay of approximately 640 milliseconds (ms) may be used for reconfiguration.
Therefore, legacy LTE networks may not adapt to UL-DL configurations based on cell-specific instantaneous traffic demands. Semi-static configuration of DL and UL frame resources across the network may not allow for adjustment of the amount of DL and UL resources based on instantaneous traffic demand. Since traffic conditions in small cells can vary widely, the inability to adjust DL and UL resources based on instantaneous traffic conditions can limit the small cells deployed in the macro cell coverage area. Dynamic allocation of DL and UL frame resource numbers may improve the performance of LTE small cell networks operating in TDD spectrum.
For example, some mechanisms may be used to support dynamic allocation of UL and DL subframes, such as the "flexible subframes" (flexsfs) shown in fig. 2, with a lower latency, such as 10 ms. The flexible subframes are capable of changing the uplink-downlink transmission direction for a set of legacy UL-DL TDD configurations. For example, in the legacy LTE UL-DL TDD configuration (fig. 4) of seven different semi-static configurations, subframes with subframe indices of 3,4, 7, 8, and 9 may vary between UL or DL subframes. Since the transmission direction of subframes 0, 1,2, 5, and 6 may be fixed to be primarily UL subframes (e.g., subframe 2) or DL subframes (e.g., DL subframes 0 and 5, special subframe 1, or DL or special subframe 6) for the legacy LTE UL-DL TDD configurations of seven different semi-static configurations, these subframes ( subframes 0, 1,2, 5, and 6) may be referred to as fixed subframes.
Techniques (e.g., methods, computer circuitry, nodes, configuration devices, processors, transceivers, or UEs) described herein may enable dynamic changes in subframe types (e.g., UL or DL) in signaling mechanisms and legacy UL-DL configurations to support dynamic allocation of DL and UL resources in LTE physical frame structures. The techniques may be compatible with legacy LTE networks (i.e., LTE release 8, 9, 10, or 11) and may have minimal impact on legacy terminals (e.g., UEs), and may provide lower implementation complexity for dynamic changes. The techniques may provide a fast adaptation time scale (e.g., 10ms) for dynamic reconfiguration of DL and UL frame resources in LTE TDD small cells.
Advanced UEs supporting UL-DL TDD reconfiguration (e.g., UEs supporting the functionality of LTE release 12) may dynamically reconfigure a semi-statically configured legacy LTE UL-DL TDD configuration to another configuration by configuring the FlexSF to a different transmission direction (e.g., UL to DL, or DL to UL). FlexSF may be transparent to legacy UEs using LTE TDD release 8, 9, 10 or 11, and UL or DL configuration of FlexSF may be semi-statically changed for legacy UEs through system information block type 1(SIB1) information bits. The node may be responsible for properly scheduling data transmissions for legacy UEs to ensure that the hybrid automatic repeat request-acknowledgement (HARQ-ACK) resources of the corresponding Physical Uplink Shared Channel (PUSCH) and Physical Downlink Shared Channel (PDSCH) and PUSCH remain valid even when the TDD configuration of advanced UEs supporting FlexSF is changed.
The downlink signals or channels may include data on a Physical Downlink Shared Channel (PDSCH) or control information on a Physical Downlink Control Channel (PDCCH). The PDCCH (or enhanced PDCCH) may carry a message called Downlink Control Information (DCI), which may include transmission resource allocation (such as PDSCH or PUSCH), and other control information for the UE or group of UEs. Many PDCCHs may be transmitted in a subframe. The uplink signal or channel may include data on a Physical Uplink Shared Channel (PUSCH) or control information on a Physical Uplink Control Channel (PUCCH). An automatic repeat request is a feedback mechanism by which the receiving terminal requests retransmission of packets detected as erroneous. Hybrid ARQ is a simultaneous combination of automatic repeat request (ARQ) and Forward Error Correction (FEC). When HARQ is used and if errors can be corrected by FEC, the entire retransmission may not be required, otherwise if errors can be detected but cannot be corrected, the entire retransmission may be requested. An Acknowledgement (ACK) signal may be transmitted to indicate that one or more data blocks, such as those in the PDSCH, have been successfully received and decoded. HARQ-ACK/negative acknowledgement (NACK or NAK) information may include feedback from the receiver to the transmitter to acknowledge correct reception of the packet or to require a new retransmission (via NACK or NAK). PDSCH HARQ may be transmitted in an uplink subframe after a PDSCH in a downlink subframe, and a PUSCH HARQ may be transmitted in a downlink subframe after a PUSCH in an uplink subframe. In legacy systems, the timing relationship between UL/UL grants (grant), DL/UL data allocation, and DL/UL harq feedback may be predetermined.
In old LTE, seven kindsEach of the semi-statically configured UL-DL TDD configurations may have PDSCH HARQ timing corresponding to a UL subframe and PUSCH scheduling timing and PUSCH HARQ timing corresponding to a DL subframe. For example, table 2 shows PDSCH HARQ timing for seven UL-DL configurations used in LTE, as shown in fig. 3. PDSCH transmissions may be indicated by detecting the corresponding PDCCH or PDCCH indicating the SPS version of the downlink within subframe(s) n-K, where K ∈ K and K defined in table 2 (also shown in table 10.1.3.1-1 of 3GPP Technical Specification (TS)36.213V11.0.0 (2012-09)) is a function of the M elements K of subframe n0,k1,…，kM-1The set of (c). For example, uplink subframe n in table 2 may be used to transmit PDSCH HARQ-ACK(s) for PDSCH in subframe(s) n-k.
For example, in TDD configuration 1 indicated by SIB1, UL subframe 2 may provide PDSCHHARQ-ACK for DL subframes 5 and 6 of the previous radio frame, UL subframe 3 may provide PDSCH HARQ-ACK for DL subframe 9 of the previous frame, UL subframe 7 may provide PDSCH HARQ-ACK for DL subframes 0 and 1 of the previous frame, and UL subframe 8 may provide PDSCH HARQ-ACK for DL subframe 4 of the previous frame. In an example, at least four subframes may occur between a downlink subframe and an uplink subframe to allow transmission, decoding, and processing of downlink transmissions, PDCCH, and/or uplink transmissions.
Table 3 shows PUSCH scheduling timing for seven UL-DL configurations used in LTE. For UL-reference (reference) UL/DL configuration and normal HARQ operation belonging to {1,2,3,4,5,6}, when a PDCCH or enhanced physical downlink control channel (EPDCCH or EPDCCH) with an uplink DCI format and/or physical hybrid automatic repeat request (ARQ) indicator channel (PHICH) transmission is detected in subframe n (which is intended for the UE), the UE may adjust the corresponding PUSCH transmission in subframe n + k according to PDCCH/EPDCCH information and PHICH information, where k is given in table 3 (also shown in table 8-2 of 3GPP Technical Specification (TS)36.213V11.0.0 (2012-09)). The physical hybrid ARQ indicator channel (PHICH) is a downlink physical channel that carries HARQ ACK/NACK information that indicates whether the node has correctly received a transmission on the PUSCH. For UL-reference UL/DL configuration0 and normal HARQ operation, the Least Significant Bit (LSB) of the UL index in DCI format 0/4 may be set to 1 in subframe n or the PHICH may be set to IPHICHThe UE may adjust the corresponding PUSCH transmission in subframe n +7, or the PHICH may be received in subframe n-0 or 5 in the corresponding resource, or subframe n-1 or 6.
Figure BDA0001628234780000091
TABLE 3
For example, in TDD configuration 1 indicated by SIB1, DL subframe 1 may schedule PUSCH in UL subframe 7, DL subframe 4 may schedule PUSCH in UL subframe 8, DL subframe 6 may schedule PUSCH in UL subframe 2 of a subsequent radio frame, and DL subframe 9 may schedule PUSCH in UL subframe 3 of a subsequent frame. In an example, at least four subframes may occur between a downlink subframe and an uplink subframe to allow transmission, decoding, and processing of downlink transmissions, PDCCH, and/or uplink transmissions.
Table 4 shows the timing of PUSCH HARQ for seven UL/DL configurations used in LTE. For PUSCH transmission scheduled by serving cell c in subframe n, the UE may decide subframe n + kPHICHCorresponding PHICH of serving cell c, where kPHICHGiven in table 4 (also shown in table 9.1.2-1 of 3GPP Technical Specification (TS)36.213V11.0.0 (2012-09)).
Figure BDA0001628234780000101
TABLE 4
For example, in TDD configuration 0 indicated by SIB1, the PUSCH HARQ-ACK for UL subframe 2 may be transmitted in DL subframe 6, the PUSCH HARQ-ACK for UL subframe 3 may be transmitted in DL subframe 9, the PUSCH HARQ-ACK for UL subframe 7 may be transmitted in DL subframe 1 of a subsequent radio frame, and the PUSCH HARQ-ACK for UL subframe 8 may be transmitted in DL subframe 4 of a subsequent frame. In an example, at least four subframes may occur between an uplink subframe and a downlink subframe to allow decoding and processing of downlink transmissions, uplink transmissions, and/or PHICHs.
The dynamic reconfiguration techniques described herein (e.g., methods, computer circuits, nodes, configuration devices, processors, transceivers, or UEs) may provide dynamic reconfiguration to UL-DL TDD configurations with minimal changes to the UE terminals and LTE specifications, while retaining full flexibility in traffic adaptation capabilities. Furthermore, the techniques may support fast adaptation on a time scale of approximately 10ms without adding new Physical (PHY) layer signaling or changing PHY layer signaling.
In an example, the techniques may use an existing legacy LTE UL-DL configuration without adding a new UL-DL configuration. Legacy UEs (e.g., LTE release 8-11 UEs) may operate using the semi-static UL-DL configuration broadcast in SIB1 such that dynamic reconfiguration has minimal or no impact on legacy UE behavior. The dynamic reconfiguration technique can support fast adaptation time scaling for advanced UEs (e.g., LTE release 12 UEs) without introducing additional physical layer signaling and without changing the LTE PHY physical structure. The dynamic reconfiguration technique may reuse the HARQ operation timeline defined for legacy UEs and preserve flexible traffic adaptation capability in small cells.
The dynamic reconfiguration technique may utilize a flexible subframe (FlexSF) mechanism as shown in fig. 4. In LTE TDD systems with dynamic UL-DL reconfiguration, subframes may be classified according to their likelihood of changing transmission direction between legacy LTE UL-DL configurations. For example, because subframes 0, 1, 5, and 6 of 7 legacy LTE UL-DL configurations are unlikely to change from the DL transmission direction, these subframes may be classified as normal (or static) DL subframes (i.e., including DL subframes and special subframes). Because subframe 2 is unlikely to change from the UL transmission direction, subframe 2 of the 7 legacy LTE UL-DL configurations may be classified as a normal or static UL subframe. Because subframes 3,4, 7, 8, and 9 of the 7 legacy LTE UL-DL configurations may be configured as DL subframes or UL subframes (i.e., changing the transmission direction from DL to UL or from UL to DL for the 7 legacy LTE UL-DL configurations) (depending on the legacy LTE UL-DL configurations), these subframes may be classified as flexible subframes. For example, subframe 3 may be configured as a UL subframe for LTE UL- DL configurations 0, 1, 3,4, and 6, or as a DL subframe for LTE UL- DL configurations 2 and 5. Fig. 4 shows the transmission directions of flexible subframes for 7 legacy LTE UL-DL configurations (i.e., LTE UL-DL configurations 0-6).
In another example, for advanced UEs, the transmission direction of flexible subframes (i.e., subframes 3, 7, and 8) configured as UL by UL-DL configuration 1 in SIB1 may be changed to DL. Dynamic reconfiguration of advanced UEs may imply compatible operation of legacy UEs, since legacy UEs may simply skip UL subframes if they are not scheduled or configured to transmit UL signals. Furthermore, if the serving cell is configured with UL-DL configuration in favor of UL (e.g., UL-DL configuration 0), dynamic reconfiguration of advanced UEs may not have an impact on traffic adaptation characteristics, since each flexible subframe may dynamically change the transmission direction from UL to DL and back to UL, as shown in fig. 1.
By default, the UE in the network may follow a legacy behavior according to the UL-DL configuration broadcast in SIB 1. If the network determines that dynamic resource allocation (e.g., traffic asymmetry) may improve traffic conditions, the network (e.g., via an eNB) may configure the served advanced UEs to operate in a dynamic mode that supports reconfiguration of subframe types. Higher layer signaling (e.g., radio resource control (PRC) signaling) or physical layer signaling may be used to activate the dynamic UL-DL configuration mode of advanced UEs linked to a cell (e.g., using cell-specific mechanisms). The activation of the dynamic UL-DL configuration mode of the advanced UEs may be performed in a UE-specific manner such that each advanced UE may be independently configured to initiate operation in the dynamic UL-DL reconfiguration mode. The dynamic UL-DL configuration mode may be activated by using a UL-DL reconfiguration indicator. For example, DCI (such as a DL DCI grant or a UL DCI grant) or PRC signaling may carry a UL-DL reconfiguration indicator and may be used to activate a dynamic UL-DL reconfiguration mode in a UE-specific manner. Activation of the dynamic UL-DL reconfiguration mode may be acknowledged by the eNB such that there is no ambiguity between the eNB and the UE in the UL/DL operation in subsequent subframes. ACK/NACK signaling may be used for dynamic UL-DL reconfiguration mode acknowledgement. Legacy UEs may not provide ACKs or may not be able to provide ACKs.
The default number of DL subframes of a radio frame may be controlled by the UL-DL configuration broadcast in SIB 1. The dynamic UL-DL reconfiguration technique may provide a mechanism for deciding which subframes may be considered or used as additional DL subframes for advanced UEs that have dynamic UL-DL reconfiguration capabilities. In an example, the UL-DL reconfiguration indicator may indicate that the additional set of flexible subframes is to be configured as DL subframes using an existing set of UL-DL reconfigurations. For example, UL-DL configuration 0 in favor of UL may be configured by RRC signaling, or UL-DL configuration 0 in favor of UL may be set via SIB1 or associated with the UL-DL configuration broadcast by SIB1, as shown in fig. 5. The DL-favorable UL-DL configuration 5 may also be configured by RRC signaling. The UL-DL reconfiguration indicator may configure subframes 4, 7, 8, and 9 as DL subframes (e.g., switching transmission direction from UL to DL), which may dynamically change a radio frame from legacy LTE UL-DL configuration 0 to legacy LTE UL-DL configuration 4(206), where subframe 3 is reconfigured from UL-DL configuration in favor of DL (230). In another configuration, DL-favorable UL-DL configuration 5, along with the UL-DL reconfiguration indicator, may configure subframe 3 as an UL subframe (e.g., switch the transmission direction from DL to UL), which may dynamically change the radio frame from DL-favorable UL-DL configuration 5(204) to legacy LTE UL-DL configuration 4 (206). In another example, since the UL-DL configuration does not correspond to one of the 7 legacy LTE UL-DL configurations, the UL-DL reconfiguration indicator may not configure subframe 3 as a DL subframe while leaving subframe 4 as a UL subframe. The UL-DL reconfiguration indicator may be used to dynamically configure an advanced UE from one legacy LTE UL-DL configuration to another without changing the SIB 1.
In another example, the network may use the existing set of legacy LTE UL-DL configurations and instruct advanced UEs to use UL-DL configurations with a specified number of DL subframes in favor of DL (e.g., legacy LTE UL-DL configuration 5(204) in fig. 5). DL-favorable UL-DL configurations may be signaled (e.g., RRC signaling) in a semi-static manner and updated infrequently. Once the advanced UE has been configured by the eNB with an additional, DL-favorable UL-DL configuration, the advanced UE may assume that an additional set of DL flexible subframes are available for future operation. Thus, advanced UEs may start to monitor these flexible subframes for allocation of DL grants and data transmissions. Thus, UL-DL configuration in favor of UL and UL-DL configuration in favor of DL may provide a boundary on the number of flexible subframes to monitor allocation of DL grants and data transmissions. For example, as shown in fig. 5, the UL-favorable UL-DL configuration may be a legacy LTE UL-DL configuration 0(208), the DL-favorable UL-DL configuration may be a legacy LTE UL-DL configuration 5(204), such that all 7 legacy LTE UL-DL configurations may be available for dynamic reconfiguration, and advanced UEs may monitor subframes 3,4, 7, 8, and 9 for allocation of DL grants and data transmissions. In another example, the UL-favorable UL-DL configuration may be a legacy LTE UL-DL configuration 6, the DL-favorable UL-DL configuration may be a legacy LTE UL-DL configuration 2, such that 3 LTE UL-DL configurations (i.e., legacy LTE UL- DL configurations 1,2, and 6) may be available for dynamic reconfiguration, and the advanced UE may monitor subframes 3,4, and 8 for DL grants and allocation of data transmissions. Configuring UL-DL configuration in favor of UL and UL-DL configuration in favor of DL may provide a reservation of "DL flexible subframes".
The dynamic change from "DL flexible subframes" to UL subframes may use various scheduling mechanisms. The DL DCI grant may schedule DL data allocation of a subframe if the DL grant is transmitted. Thus, if the eNB determines to use the legacy UL subframe for DL data transmission to one of its advanced 12 UEs (configured in a dynamic mode of operation), the eNB may schedule a DL grant in only one of the monitored "DL flexible subframes" (e.g., transmit a downlink DCI grant).
If the eNB determines to use "DL flexible subframes" as UL subframes, at least two options are available. In one option, the eNB may use an existing DCI message and allocate a UL grant in one of the previous subframes 240 to schedule a UL transmission in one of the "DL flexible subframes". For legacy UEs, the "DL flexible subframes" may be interpreted as UL subframes, as shown in legacy LTE UL-DL configuration 0(202) in fig. 5. For legacy and advanced UEs, the eNB may use the previous DL subframe for scheduling UL grants. Thus, the eNB may allocate UL grants for advanced or legacy UEs configured in dynamic mode using the same subframes. If the allocated UL grant points to one of the "DL flexible subframes," the UE may interpret the flexible subframe as a UL subframe and prepare data for future transmission at the flexible subframe. One advantage of using existing DCI messages is that the dynamic mode UL grant may not make any changes to existing DCI messages and may also be implemented by using an existing legacy HARQ timeline.
In another option, a new DCI message (including a UL-DL reconfiguration indicator) may be introduced to indicate that a particular DL subframe may be interpreted as DL and used for UL transmission. A new HARQ timeline may be defined using a new DCI message (e.g., a different DCI message type). The DCI message may carry an UL-DL configuration to be applied to a current or next frame and may be implemented in one of static DL subframes. Such new UL-DL configurations may be a subset of legacy UL-DL configurations, and the number of DL subframes may be less than the configured DL-favorable UL-DL configuration.
LTE HARQ timing (or HARQ timeline) may take asynchronous operation in DL data transmission and synchronous operation in UL data transmission. For example, there may be a fixed time between the DL scheduling grant and the ul harq feedback (i.e., DL data transmission); however, there is no strict timing relationship for DL retransmission of data. For uplink operation (i.e., UL data transmission), the allocation of UL grant, UL transmission, DL HARQ feedback may be determined by strict timing relationships, which may depend on the UL-DL configuration broadcast in SIB 1.
For network systems with dynamic allocation of UL and DL resources, the legacy HARQ timeline may be modified since subframes may dynamically change transmission direction. Generating a new HARQ timeline may introduce additional complexity at the UE terminal and eNodeB sides. Configuring terminals (e.g., UEs) with UE-specific timelines for DL and UL HARQ operations (e.g., reusing legacy HARQ timelines) for various dynamically configured LTE UL-DL configurations may remove some of the complexity of implementing HARQ timelines and provide a simpler solution for DL and UL HARQ operations in the case of dynamic UL-DL reconfiguration. To enable dynamic UL-DL reconfiguration, for advanced UEs, the existing HARQ timeline may be reused by configuring two independent HARQ timelines: one HARQ timeline for UL operations 224 and one HARQ timeline for DL operations 212, as shown in fig. 5. These UL-DL configurations may be configured independently for each UE in a cell, and may be overlaid on the legacy UL-DL configurations. UL-favorable and DL-favorable UL-DL configurations may automatically change the number of HARQ processes available for operation of advanced UEs. According to a specification, such as table 2 (fig. 3) of the LTE specification, the number of DL HARQ processes may be defined by a UL-DL configuration in favor of DL. According to a specification (e.g., table 4 of the LTE specification), the number of UL HARQ processes may be defined by UL-DL configuration in favor of UL.
In an example, for legacy UEs, the UL HARQ timeline may be set to be the same as the UL HARQ timeline defined by the UL-DL configuration transmitted by SIB1 (i.e., the same HARQ timeline may be used for UL HARQ operations). In another example, the DL HARQ timeline may be configured by higher level signaling (e.g., RRC signaling). Fig. 5 shows an example of modified HARQ timing operation and PUSCH transmission timing in case of LTE UL-DL configuration 0 in favor of UL and LTE UL-DL configuration 5 in favor of DL. For example, a DL configured subframe may use a DL-favorable UL-DL configuration for DL channel timing (e.g., PDSCH scheduling grant transmission timing 210, PDSCH transmission timing 210, and PDSCH HARQ feedback timing 212 (such as table 2 (fig. 3))). The subframe of the UL configuration may use UL-DL configuration in favor of UL for UL channel timing (e.g., PUSCH scheduling grant timing 220, PUSCH transmission timing 222 (such as table 3), PUSCH HARQ feedback timing 224 (such as table 4), and PUSCH HARQ retransmission timing). For advanced UE dynamic UL/DL configuration 206, DL subframe 5 may use DL channel timing 210 and 212, while flexible subframe 3 for UL configuration may use UL channel timing 220, 222, and 224. Many different combinations and variations are possible using the principles illustrated.
Fig. 6 shows an example of a flow diagram 300 for an advanced UE supporting dynamic traffic adaptation in an LTE TDD network. The network (via the eNB) may configure (302) UL-DL configurations in favor of UL or DL/UL balanced UL-DL configurations (e.g., DL-DL configurations in favor) according to a set of legacy UL-DL configurations. Advanced UEs (e.g., LTE release 12 UEs) may acquire the UL-DL configuration (i.e., legacy UL-DL configuration) broadcast in SIB1 (304). The SIB1 legacy UL-DL configuration may be a UL-DL configuration that favors UL (relative to other UL-DL configurations used in dynamic reconfiguration). The advanced UE may begin normal operation following the HARQ timing timeline defined by the legacy UL-DL configuration (306). The network may decide if more DL resources are needed (308). If additional DL resources are not needed, the advanced UE and eNB may continue normal operation (operation 306). If additional resources are needed, the eNB may activate dynamic UL/DL reconfiguration (e.g., send UL-DL reconfiguration indicator via RRC signaling or physical layer signaling) (310). The eNB may configure the DL and UL-DL configuration in favor of the UL according to the set of legacy lte UL-DL configurations (312). Advanced UEs may follow the new configuration for DL and UL HARQ timelines, and UL legacy subframes designated as DL by the new DL-favorable UL-DL configuration may be treated as potential DL subframes (314). The eNB may allocate a UL grant (316). If a UL grant is allocated, the advanced UE may use the UL HARQ timeline to decide the subframe in which to send UL data (if the UL grant points to a DL subframe, the subframe type is changed to a DL subframe). The network may determine whether the amount of traffic in the DL and UL transmissions is balanced (318). If the DL and UL traffic is not balanced, the network and advanced UEs may maintain the new network configuration, as shown in operation 314. If the DL and UL traffic is balanced, the eNB may deactivate 320 the dynamic UL-DL reconfiguration and restart from 302.
The dynamic reconfiguration techniques described herein may provide various advantages and benefits for LTE TDD systems. For example, the described techniques enable fast traffic adaptation capabilities by dynamically changing the amount of DL and UL resources. Additional physical layer signaling may not be required while still supporting fast 10ms adaptation time scaling, which may provide the advantage of improved performance. The described techniques may provide dynamic UL-DL reconfiguration for legacy and advanced (LTE release 12 UEs or terminals) for legacy (e.g., LTE release 11) compatible operations. The described techniques may reuse an existing HARQ timeline with flexible traffic adaptation capabilities. The described techniques may not introduce new UL-DL configurations to LTE systems; however, with some minor changes (e.g., HARQ timing processing), the technique can be extended to support new UL-DL configurations.
Another example provides a method 500 for dynamically reconfiguring an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration by an evolved node b (enb), as illustrated by the flow chart in fig. 7. The method may be performed as instructions on a machine, computer circuitry, or a processor of the UE, wherein the instructions are included on at least one computer-readable medium or one non-transitory machine-readable storage medium. The method includes an operation for configuring a User Equipment (UE) with a semi-static UL-DL TDD configuration (belonging to a set of legacy UL-DL TDD configurations), as in block 510. The next operation of the method may be to activate a dynamic UL-DL reconfiguration mode when additional DL or UL resources are needed for data traffic, as in block 520. The method may also include dynamically reconfiguring the semi-static UL-DL TDD configuration to another legacy UL-DL TDD configuration using the UL-DL reconfiguration indicator to change a UL-DL transmission direction of a flexible subframe (FlexSF), wherein the flexible subframe is capable of changing an uplink-downlink transmission direction of a set of legacy UL-DL TDD configurations, as in block 530.
In an example, dynamically reconfiguring the semi-static UL-DL TDD configuration to other legacy UL-DL TDD configurations may further include: reconfiguring DL channel timing based on a DL-favorable UL-DL configuration; reconfiguring UL channel timing based on UL-DL configuration in favor of UL; and communicating HARQ feedback for subframes in a frame using DL channel timing or UL channel timing, respectively. The DL-favorable UL-DL configuration may include more DL subframes for the UE than the semi-static UL-DL TDD configuration, and the DL channel timing may include Physical Downlink Shared Channel (PDSCH) scheduling grant transmission timing (e.g., 210 in fig. 5), PDSCH transmission timing (e.g., 210 in fig. 5), and PDSCH hybrid automatic repeat request (HARQ) feedback timing (e.g., 212 in fig. 5; table 2 (fig. 3)). The UL-DL configuration in favor of UL may include more UL subframes for the UE than the semi-static UL-DL TDD configuration or be the same as the semi-static UL-DL TDD configuration broadcast by SIB1, and the UL channel timing may include Physical Uplink Shared Channel (PUSCH) scheduling grant timing (e.g., 220 in fig. 5), PUSCH transmission timing (e.g., 222 in fig. 5; table 3), PUSCH HARQ feedback timing (e.g., 224 in fig. 5; table 4), and PUSCH HARQ retransmission timing.
In another example, third generation partnership project (3GPP) Long Term Evolution (LTE) UL-DL configuration 0 provides UL-DL configuration in favor of UL for UL- DL configurations 6, 1, 3, 2, 4, and 5. LTE UL-DL configuration 1 provides DL-favorable UL-DL configurations for UL- DL configurations 6 and 0 and provides UL-favorable UL-DL configurations for UL- DL configurations 3, 2, 4, and 5. LTE UL-DL configuration 2 provides DL-favorable UL-DL configurations for UL- DL configurations 3, 1, 6, and 0 and provides UL-favorable UL-DL configurations for UL-DL configuration 5. LTE UL-DL configuration 3 provides DL-favorable UL-DL configurations for UL- DL configurations 1, 6, and 0 and provides UL-favorable UL-DL configurations for UL- DL configurations 2, 4, and 5. LTE UL-DL configuration 4 provides DL-favorable UL-DL configurations for UL- DL configurations 3, 1, 6, and 0 and provides UL-favorable UL-DL configurations for UL-DL configuration 5. LTE UL-DL configuration 5 provides DL-favorable UL-DL configurations for UL- DL configurations 4, 2,3, 1, 6, and 0. LTE UL-DL configuration 6 provides DL-favorable UL-DL configurations for UL-DL configuration 0 and UL-favorable UL-DL configurations for UL- DL configurations 1, 3, 2, 4, and 5.
In another configuration, configuring the UE with the semi-static UL-DL TDD configuration further comprises broadcasting the semi-static UL-DL TDD configuration to the UE via system information block type 1(SIB 1). In another example, the UL-DL reconfiguration indicator may be indicated by using a DL Downlink Control Information (DCI) grant or a UL DCI grant in a DCI grant subframe. The DL DCI grant or the UL DCI grant may provide a grant for FlexSF.
In another configuration, when the semi-static UL-DL TDD configuration for data traffic is equalized, the method may further include deactivating the dynamic UL-DL reconfiguration mode. In another example, the operation of activating the dynamic UL-DL reconfiguration mode may further include: transmitting a dynamic UL-DL reconfiguration mode activation indicator for activating a dynamic UL-DL reconfiguration mode to the UE, receiving an Acknowledgement (ACK) from the UE indicating that the UE is in the dynamic UL-DL reconfiguration mode. The dynamic UL-DL reconfiguration mode activation indicator may be transmitted via DCI or Radio Resource Control (RRC) signaling. The operation of disabling the dynamic UL-DL reconfiguration mode may further include: transmitting a dynamic UL-DL reconfiguration mode deactivation indicator for deactivating the dynamic UL-DL reconfiguration mode to the UE; an Acknowledgement (ACK) is received from the UE indicating that the UE deactivates the dynamic UL-DL reconfiguration mode. The deactivation indicator may be transmitted via DCI or Radio Resource Control (RRC) signaling. The FlexSF may include subframes 3,4, 7, 8, or 9 configured as UL or DL subframes by a semi-static UL-DL TDD configuration.
In another configuration, the operation of dynamically reconfiguring a semi-static UL-DL TDD configuration to another legacy UL-DL TDD configuration may occur within a period of about one radio frame or about 10 milliseconds (ms). Legacy UL-DL TDD configurations may include third generation partnership project (3GPP) Long Term Evolution (LTE) UL-DL configurations 0-6. A Physical Downlink Control Channel (PDCCH) or enhanced PDCCH (epdcch) may convey a DL DCI grant.
Another example provides functionality of computer circuitry 600 on a User Equipment (UE) operable to dynamically reconfigure an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration, as shown in the flow diagram in fig. 8. The functionality may be implemented as a method or may be executed as instructions on a machine, where the instructions are included on at least one computer-readable medium or one non-transitory machine-readable storage medium. The computer circuitry can receive a UL-DL reconfiguration indicator from a node for dynamically reconfiguring a flexible subframe from a semi-static UL-DL configuration to a different UL-DL transmission direction, wherein the FlexSF is capable of changing the UL-DL transmission direction, as in block 610. The computer circuitry can also be configured to apply DL channel timing based on the DL-favorable UL-DL configuration, wherein the DL-favorable UL-DL configuration includes more DL subframes for the UE than the semi-static UL-DL TDD configuration, as in block 620. The computer circuitry can also be configured to apply UL channel timing based on the UL-DL favorable configuration, wherein the UL-DL favorable configuration includes more UL subframes for the UE than the semi-static UL-DL TDD, as in block 630. In another example, the computer circuitry can be further configured to apply the UL channel timing based on a UL-DL favorable configuration, wherein the UL-DL favorable configuration includes more UL subframes for the UE than the semi-static UL-DL TDD or is the same as the semi-static UL-DL TDD configuration broadcast by SIB 1.
In an example, the computer circuitry can be further configured to transmit HARQ feedback for a subframe in the frame using DL channel timing or UL channel timing. When FlexSF is configured as a DL subframe, the DL channel timing may include Physical Downlink Shared Channel (PDSCH) scheduling grant transmission timing (e.g., the grant may be DCI carried by PDCCH or EPDCCH), PDSCH transmission timing (e.g., may be the same subframe as the PDSCH scheduling grant), or PDSCH hybrid automatic repeat request (HARQ) feedback timing (e.g., may be carried in PUCCH or PUSCH) for subframes in the frame. When FlexSF is configured as a UL subframe, the UL channel timing may include Physical Uplink Shared Channel (PUSCH) scheduling grant transmission timing (e.g., the grant may be DCI carried by PDCCH or EPDCCH), PUSCH transmission timing, or PUSCH HARQ feedback timing (e.g., may be carried by physical hybrid ARQ indicator channel (PUICH)) for the subframe in the frame.
In another example, the computer circuitry can be further configured to: configuring, via Radio Resource Control (RRC) signaling, a UL-DL configuration that facilitates DL; and configuring, via Radio Resource Control (RRC), a UL-DL configuration in favor of UL, or setting the UL-DL configuration in favor of UL to an old UL-DL TDD configuration conveyed in system information block type 1(SIB 1). In another configuration, the computer circuitry can be further configured to: monitoring a Downlink Control Information (DCI) grant subframe of a DL DCI grant or a ul DCI grant (which provides a grant for a FlexSF); configuring the FlexSF as a UL subframe when the DCI grant subframe includes UL DCI grant for FlexSF; and configuring the FlexSF as a DL subframe when the DCI grant subframe includes a DL DCI grant for the FlexSF. The UL-DL reconfiguration indicator may be an authorization indication. The DCI grant subframe with DL DCI grant includes FlexSF in which a Physical Downlink Shared Channel (PDSCH) is received. The DCI grant subframe with UL DCI grant includes a DL subframe preceding FlexSF in which a Physical Uplink Shared Channel (PUSCH) is transmitted. A Physical Downlink Control Channel (PDCCH) or enhanced PDCCH (epdcch) may be transmitted in a DCI grant subframe.
In another example, third generation partnership project (3GPP) Long Term Evolution (LTE) UL-DL configuration 0 provides UL-DL configuration in favor of UL for UL- DL configurations 6, 1, 3, 2, 4, and 5. LTE UL-DL configuration 1 provides DL-favorable UL-DL configurations for UL- DL configurations 6 and 0 and provides UL-favorable UL-DL configurations for UL- DL configurations 3, 2, 4, and 5. LTE UL-DL configuration 2 provides DL-favorable UL-DL configurations for UL- DL configurations 3, 1, 6, and 0 and provides UL-favorable UL-DL configurations for UL-DL configuration 5. LTE UL-DL configuration 3 provides DL-favorable UL-DL configurations for UL- DL configurations 1, 6, and 0 and provides UL-favorable UL-DL configurations for UL- DL configurations 2, 4, and 5. LTE UL-DL configuration 4 provides DL-favorable UL-DL configurations for UL- DL configurations 3, 1, 6, and 0 and provides UL-favorable UL-DL configurations for UL-DL configuration 5. LTE UL-DL configuration 5 provides DL-favorable UL-DL configurations for UL- DL configurations 4, 2,3, 1, 6, and 0. LTE UL-DL configuration 6 provides DL-favorable UL-DL configurations for UL-DL configuration 0 and UL-favorable UL-DL configurations for UL- DL configurations 1, 3, 2, 4, and 5.
In another configuration, the computer circuitry can be further configured to: receiving a dynamic UL-DL reconfiguration mode activation indicator for activating dynamic UL-DL reconfiguration from a node; activating a dynamic UL-DL reconfiguration mode; and transmits an Acknowledgement (ACK) for the dynamic UL-Dl reconfiguration mode. The dynamic UL-DL reconfiguration mode activation indicator may be received via DCI or Radio Resource Control (RRC) signaling. The computer circuitry can be further configured to: receiving a dynamic UL-DL reconfiguration mode deactivation indicator from a node; disabling the dynamic UL-DL mode; and transmitting an Acknowledgement (ACK) to deactivate the dynamic UL-DL reconfiguration mode. The deactivation indicator may be received via DCI or Radio Resource Control (RRC) signaling.
In another example, the computer circuitry can be further configured to receive a semi-static UL-DL TDD configuration (belonging to a set of legacy UL-DL TDD configurations) via a system information block type 1(SIB1) prior to receiving the UL-DL reconfiguration indicator. The computer circuitry can dynamically reconfigure the UL-DL TDD configuration to another legacy UL-DL TDD configuration in a period of about one radio frame or about 10 milliseconds (ms). Legacy UL-DL TDD configurations may include third generation partnership project (3GPP) Long Term Evolution (LTE) UL-DL configurations 0-6. The FlexSF may include subframes 3,4, 7, 8, or 9.
In another configuration, the computer circuitry can be further configured to: converting the semi-static UL-DL TDD configuration to another legacy UL-DL TDD configuration based on the received UL-DL reconfiguration indicator; reconfiguring DL channel timing based on a DL-favorable UL-DL TDD configuration; and reconfiguring UL channel timing based on the UL-DL TDD configuration in favor of UL. The DL channel timing may include Physical Downlink Shared Channel (PDSCH) scheduling grant generic timing, PDSCH transmission timing, or PDSCH hybrid automatic repeat request (HARQ) feedback timing. The UL channel timing may include a Physical Uplink Shared Channel (PUSCH) scheduling grant timing, a PUSCH transmission timing, a PUSCH HARQ feedback timing, or a PUSCH HARQ retransmission timing.
Fig. 9 illustrates an example node 710 (e.g., eNB) and an example wireless device 720 (e.g., UE). The node may be configured to dynamically reconfigure an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration, as described in 500 of fig. 7. Referring back to fig. 9, the node may include a configuration device 712. The configuration device or node may be configured to communicate with the wireless device. The configuration device may be configured to dynamically reconfigure an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration. The configuration device may include a processor 714 and a transceiver 716. The processor may be configured to dynamically reconfigure the semi-static UL-DL TDD configuration to another legacy UL-DL TDD configuration by using a Downlink Control Information (DCI) grant or a UL DCI grant in a DCI grant subframe. The DL DCI grant or the UL DCI grant may provide a grant for a flexible subframe (FlexSF). The flexible subframes may be capable of changing the uplink-downlink transmission direction for a set of legacy UL-DL TDD configurations. The transceiver may be configured to transmit a DL DCI grant or a UL DCI grant to a User Equipment (UE) in a DCI grant subframe.
In another configuration, the processor 714 may be further configured to: applying DL channel timing based on the DL-favorable UL-DL configuration; UL channel timing is applied based on UL-DL configuration in favor of UL. The DL-favorable UL-DL configuration may include more DL subframes for the UE than the semi-static UL-DL TDD configuration, and the DL channel timing may include Physical Downlink Shared Channel (PDSCH) scheduling grant transmission timing, PDSCH transmission timing, and PDSCH hybrid automatic repeat request (HARQ) feedback timing. UL-DL configuration in favor of UL may include more UL subframes for the UE than semi-static UL-DL TDD configuration, and UL channel timing may include Physical Uplink Shared Channel (PUSCH) scheduling grant timing, PUSCH transmission timing, PUSCH hharq feedback timing, and PUSCH HARQ retransmission timing. The transceiver 716 can also be configured to transmit HARQ feedback for subframes in a frame using DL channel timing or UL channel timing.
In another example, the processor 714 may be further operable to: activating a dynamic UL-DL reconfiguration mode when data traffic requires additional DL resources; deactivating the dynamic UL-DL reconfiguration mode when the semi-static UL-DL TDD configuration for the data traffic is equalized; the transceiver 716 can also be configured to: transmitting a dynamic UL-DL reconfiguration mode activation indicator to the UE for activating a dynamic UL-DL reconfiguration mode, wherein the activation indicator may be transmitted via DCI or Radio Resource Control (RRC) signaling; receiving an Acknowledgement (ACK) from the UE, the ACK indicating that the UE activates a dynamic UL-DL reconfiguration mode; transmitting a dynamic UL-DL reconfiguration mode deactivation indicator for deactivating the dynamic UL-DL reconfiguration mode to the UE, wherein the deactivation indicator may be transmitted via DCI or Radio Resource Control (RRC) signaling; an Acknowledgement (ACK) is received from the UE, the ACK indicating that the UE is to deactivate the dynamic UL-DL reconfiguration mode.
The processor 714 may dynamically reconfigure the semi-static UL-DL TDD configuration to other legacy UL-DL TDD configurations within a period of about one radio frame or about 10 milliseconds (ms). Legacy UL-DL TDD configurations may include third generation partnership project (3GPP) Long Term Evolution (LTE) UL-DL configurations 0-6. The FlexSF may include subframes 3,4, 7, 8, or 9. A Physical Downlink Control Channel (PDCCH) or enhanced PDCCH (epdcch) may be transmitted in a DCI grant subframe. The DCI grant subframe with the DL DCI grant may include FlexSF in which a Physical Downlink Shared Channel (PDSCH) may be received; the DCI grant subframe with UL DCI may include a DL subframe before FlexSF in which a Physical Uplink Shared Channel (PUSCH) may be transmitted.
The node 710 may include a Base Station (BS), a node b (nb), an evolved node b (enb), a baseband unit (BBU), a Radio Remote Unit (RRU), a Central Processing Module (CPM).
The wireless device 720 may include a transceiver 724 and a processor 722. The wireless device may be configured to dynamically reconfigure an uplink-downlink (UL-DL) Time Division Duplex (TDD) configuration, as described in 600 of fig. 8.
Fig. 10 provides an example illustration of a wireless device (e.g., User Equipment (UE), Mobile Station (MS), mobile wireless device, mobile communication device, tablet, handset, or other type of wireless device). The wireless device may include one or more antennas configured to communicate with a node, a macro node, a Low Power Node (LPN), or a transmitting station (e.g., a Base Station (BS), an evolved node b (enb), a baseband unit (BBU), a Radio Remote Head (RRH), a Radio Remote Equipment (RRE), a Relay Station (RS), a Central Processing Module (CPM), or other type of Wireless Wide Area Network (WWAN) access point). The wireless device may be configured to communicate using at least one wireless communication standard, the wireless communication standard comprising: 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device may communicate using separate antennas for each wireless communication standard or may communicate using a shared antenna for multiple wireless communication standards. The wireless device may communicate in a Wireless Local Area Network (WLAN), a Wireless Personal Area Network (WPAN), and/or a WWAN.
Fig. 10 also provides an illustration of a microphone and one or more speakers that may be used for audio input and output of the wireless device. The display screen may be a Liquid Crystal Display (LCD) screen or other type of display screen (e.g., an Organic Light Emitting Diode (OLED) display). The display screen may be configured as a touch screen. The touch screen may use capacitive, resistive, or another type of touch screen technology. The application processor and the graphics processor may be coupled to internal memory to provide processing and display functions. The non-volatile memory port may also be used to provide data input/output options to a user. The non-volatile memory port may also be used to extend the storage capabilities of the wireless device. The keyboard may be integrated with or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard may also be provided using a touch screen.
Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc read only memories (CD-ROMs), hard drives, non-transitory computer-readable storage media, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. The circuit may include: hardware, firmware, program code, executable code, computer instructions, and/or software. The non-transitory computer readable storage medium may be a computer readable storage medium that does not include a signal. In the case of a programmable computer executing program instructions, the computing device may include: a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be: random Access Memory (RAM), erasable programmable read-only memory (EPROM), flash drives, optical drives, magnetic hard drives, solid state drives, or other media for storing electronic data. The node and the wireless device may further comprise: a transceiver module (i.e., a transceiver), a counter module (i.e., a counter), a processing module (i.e., a processor), and/or a clock module (i.e., a clock) or timer module (i.e., a timer). One or more programs that may implement or use the various techniques described herein may use an Application Program Interface (API), reusable controls, and the like. The programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
It should be appreciated that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as hardware circuitry comprising: custom Very Large Scale Integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors (e.g., logic chips, transistors, or other discrete components). A module may also be implemented in programmable hardware devices (e.g., field programmable gate arrays, programmable array logic, programmable logic devices, etc.).
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. These modules may be passive or active, including agents operable to perform desired functions.
Reference in the specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the invention. Thus, the appearances of the phrase "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.
As used in this application, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for use. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. Furthermore, various embodiments and examples of the present invention may be referred to herein along with alternatives for the various components thereof. It should be understood that these embodiments, examples, and alternatives are not to be construed as substantial equivalents of each other, but are to be construed as separate and autonomous representations of the present invention.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments, and in the following description, numerous specific details are provided (e.g., examples of layouts, distances, network examples, etc.) to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, arrangements, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
While the above examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the assistance of the inventors without departing from the principles and concepts of the invention. Accordingly, the invention is not intended to be limited, except as by the appended claims.

Claims (30)

1.一种用户设备UE中的装置，被配置来执行自适应时分双工TDD混合自动重复请求-确认HARQ-ACK报告，所述装置包括一个或多个处理器和存储器，被配置为：1. An apparatus in a user equipment UE configured to perform an adaptive time division duplex TDD hybrid automatic repeat request-acknowledgement HARQ-ACK report, the apparatus comprising one or more processors and a memory, configured as: 在所述UE处实施从网络节点接收的自适应上行链路-下行链路UL-DL配置；implementing at the UE the adaptive uplink-downlink UL-DL configuration received from the network node; 在所述UE处对从所述网络节点接收的、针对服务小区的下行链路DL HARQ参考配置进行处理，其中，DL HARQ参考配置用于实施自适应UL-DL配置；以及processing at the UE a downlink DL HARQ reference configuration for the serving cell received from the network node, wherein the DL HARQ reference configuration is used to implement an adaptive UL-DL configuration; and 在所述UE处，按照所述DL HARQ参考配置，对HARQ-ACK反馈进行格式化以在所述服务小区的物理上行链路控制信道PUCCH或物理上行链路共享信道PUSCH上传输。At the UE, the HARQ-ACK feedback is formatted for transmission on the physical uplink control channel PUCCH or physical uplink shared channel PUSCH of the serving cell according to the DL HARQ reference configuration. 2.如权利要求1所述的装置，还被配置来：基于从所述网络节点经由系统信息块SIB接收的参考UL-DL配置，执行上行链路调度和HARQ反馈。2. The apparatus of claim 1, further configured to perform uplink scheduling and HARQ feedback based on a reference UL-DL configuration received from the network node via a system information block SIB. 3.如权利要求1所述的装置，其中，所述DL HARQ参考配置是在所述UE处从所述网络节点经由更高层信令接收的。3. The apparatus of claim 1, wherein the DL HARQ reference configuration is received at the UE from the network node via higher layer signaling. 4.如权利要求1所述的装置，其中，所述DL HARQ参考配置是在所述UE处从所述网络节点经由专用信令接收的。4. The apparatus of claim 1, wherein the DL HARQ reference configuration is received at the UE from the network node via dedicated signaling. 5.如权利要求1所述的装置，其中，所述UE被配置来支持基于流量状况的自适应UL-DL配置。5. The apparatus of claim 1, wherein the UE is configured to support adaptive UL-DL configuration based on traffic conditions. 6.如权利要求1所述的装置，其中所述UE包括天线、触敏显示器屏幕、扬声器、麦克风、图形处理器、应用处理器、内部存储器或非易失性存储器端口。6. The apparatus of claim 1, wherein the UE comprises an antenna, a touch-sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, an internal memory, or a non-volatile memory port. 7.至少一个非暂态机器可读存储介质，其上包含指令，所述指令用于在用户设备UE处执行混合自动重复请求-确认HARQ-ACK操作，所述指令在被执行时实现以下操作：7. At least one non-transitory machine-readable storage medium containing instructions thereon for performing a hybrid automatic repeat request-acknowledgement HARQ-ACK operation at a user equipment UE, the instructions, when executed, achieve the following operations : 使用所述UE的一个或多个处理器激活自适应上行链路-下行链路UL-DL配置；activating adaptive uplink-downlink UL-DL configuration using one or more processors of the UE; 使用所述UE的所述一个或多个处理器识别针对服务小区的下行链路DL HARQ参考配置，其中，所述DL HARQ参考配置对应于所述自适应UL-DL配置；以及identifying, using the one or more processors of the UE, a downlink DL HARQ reference configuration for a serving cell, wherein the DL HARQ reference configuration corresponds to the adaptive UL-DL configuration; and 使用所述UE的所述一个或多个处理器，按照所述DL HARQ参考配置，向网络节点报告针对所述服务小区的自适应时分双工TDD HARQ-ACK反馈。Adaptive time division duplex TDD HARQ-ACK feedback for the serving cell is reported to a network node using the one or more processors of the UE and in accordance with the DL HARQ reference configuration. 8.如权利要求7所述的至少一个非暂态机器可读存储介质，还包括当被执行时实现以下操作的指令：在所述UE处对从所述网络节点接收的DL HARQ参考配置进行处理。8. The at least one non-transitory machine-readable storage medium of claim 7, further comprising instructions that, when executed, perform the following operations: performing at the UE a DL HARQ reference configuration received from the network node deal with. 9.如权利要求7所述的至少一个非暂态机器可读存储介质，还包括当被执行时实现以下操作的指令：基于从所述网络节点经由系统信息块SIB接收的参考UL-DL配置，执行上行链路调度和HARQ反馈。9. The at least one non-transitory machine-readable storage medium of claim 7, further comprising instructions that, when executed, implement: based on a reference UL-DL configuration received from the network node via a system information block (SIB) , perform uplink scheduling and HARQ feedback. 10.如权利要求7所述的至少一个非暂态机器可读存储介质，其中，所述DL HARQ参考配置是从所述网络节点经由更高层信令接收的。10. The at least one non-transitory machine-readable storage medium of claim 7, wherein the DL HARQ reference configuration is received from the network node via higher layer signaling. 11.如权利要求7所述的至少一个非暂态机器可读存储介质，其中，所述UE被配置来支持基于流量状况的自适应UL-DL配置。11. The at least one non-transitory machine-readable storage medium of claim 7, wherein the UE is configured to support adaptive UL-DL configuration based on traffic conditions. 12.如权利要求7所述的至少一个非暂态机器可读存储介质，其中所述UE包括天线、触敏显示器屏幕、扬声器、麦克风、图形处理器、应用处理器、内部存储器或非易失性存储器端口。12. The at least one non-transitory machine-readable storage medium of claim 7, wherein the UE comprises an antenna, a touch-sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, or a non-volatile memory port. 13.一种网络节点的装置，能够针对用户设备UE配置混合自动重复请求HARQ参考配置，所述装置包括一个或多个处理器和存储器，被配置为：13. An apparatus for a network node capable of configuring a hybrid automatic repeat request (HARQ) reference configuration for a user equipment (UE), the apparatus comprising one or more processors and a memory configured to: 由所述网络节点配置所述UE处的自适应上行链路-下行链路UL-DL配置；configuring, by the network node, an adaptive uplink-downlink UL-DL configuration at the UE; 由所述网络节点配置所述UE处针对服务小区的下行链路DL HARQ参考配置，其中，所述DL HARQ参考配置对应于所述自适应UL-DL配置；以及configuring, by the network node, a downlink DL HARQ reference configuration at the UE for the serving cell, wherein the DL HARQ reference configuration corresponds to the adaptive UL-DL configuration; and 在所述网络节点处，按照所述DL HARQ参考配置处理从所述UE接收的混合自动重复请求-确认HARQ-ACK反馈。At the network node, the received hybrid automatic repeat request-acknowledgement HARQ-ACK feedback from the UE is processed in accordance with the DL HARQ reference configuration. 14.如权利要求13所述的装置，其中，时分双工TDD HARQ-ACK反馈是按照所述DL HARQ参考配置从所述UE接收的。14. The apparatus of claim 13, wherein time division duplex TDD HARQ-ACK feedback is received from the UE in accordance with the DL HARQ reference configuration. 15.如权利要求13所述的装置，其中，所述DL HARQ参考配置经由专用信令被传送到所述UE。15. The apparatus of claim 13, wherein the DL HARQ reference configuration is communicated to the UE via dedicated signaling. 16.至少一个非暂态机器可读存储介质，其上包含指令，所述指令用于在网络节点处配置针对用户设备UE的混合自动重复请求-确认HARQ-ACK操作，所述指令在被执行时实现以下操作：16. At least one non-transitory machine-readable storage medium containing instructions thereon for configuring, at a network node, a hybrid automatic repeat request-acknowledgement HARQ-ACK operation for a user equipment UE, the instructions being executed When doing the following: 使用所述网络节点的一个或多个处理器识别针对服务小区的下行链路DL HARQ参考配置，其中，所述DL HARQ参考配置对应于在所述UE处实施的自适应UL-DL配置；以及identifying, using one or more processors of the network node, a downlink DL HARQ reference configuration for the serving cell, wherein the DL HARQ reference configuration corresponds to an adaptive UL-DL configuration implemented at the UE; and 使用所述网络节点的所述一个或多个处理器处理所述DL HARQ参考配置以传输到所述UE，其中，所述UE被配置来基于所述DL HARQ参考配置经由所述服务小区的物理上行链路控制信道PUCCH或物理上行链路共享信道PUSCH执行HARQ-ACK操作。using the one or more processors of the network node to process the DL HARQ reference configuration for transmission to the UE, wherein the UE is configured to, based on the DL HARQ reference configuration, via the serving cell's physical The uplink control channel PUCCH or the physical uplink shared channel PUSCH performs HARQ-ACK operation. 17.如权利要求16所述的至少一个非暂态机器可读存储介质，其中，在所述UE处执行的所述HARQ-ACK操作是时分双工TDD HARQ-ACK操作。17. The at least one non-transitory machine-readable storage medium of claim 16, wherein the HARQ-ACK operation performed at the UE is a time division duplex TDD HARQ-ACK operation. 18.如权利要求16所述的至少一个非暂态机器可读存储介质，其中，所述DL HARQ参考配置经由更高层信令被传送给所述UE。18. The at least one non-transitory machine-readable storage medium of claim 16, wherein the DL HARQ reference configuration is communicated to the UE via higher layer signaling. 19.如权利要求16所述的至少一个非暂态机器可读存储介质，其中，所述UE被配置来实施基于流量状况的自适应UL-DL配置。19. The at least one non-transitory machine-readable storage medium of claim 16, wherein the UE is configured to implement adaptive UL-DL configuration based on traffic conditions. 20.如权利要求16所述的至少一个非暂态机器可读存储介质，其中，所述网络节点包括基站BS、节点B NB、演进节点B eNB、基带单元BBU、射频拉远头RRH、射频拉远设备RRE、射频拉远单元RRU或中央处理模块CPM。20. The at least one non-transitory machine-readable storage medium of claim 16, wherein the network nodes comprise a base station BS, a Node B NB, an evolved Node B eNB, a baseband unit BBU, a remote radio head RRH, a radio frequency Remote equipment RRE, remote radio unit RRU or central processing module CPM. 21.一种用户设备UE，能够执行混合自动重复请求-确认HARQ-ACK操作，所述UE包括：21. A user equipment UE capable of performing a hybrid automatic repeat request-acknowledgement HARQ-ACK operation, the UE comprising: 激活装置，用于激活自适应上行链路-下行链路UL-DL配置；activating means for activating adaptive uplink-downlink UL-DL configuration; 识别装置，用于识别针对服务小区的下行链路DL HARQ参考配置，其中，所述DL HARQ参考配置对应于所述自适应UL-DL配置；以及identifying means for identifying a downlink DL HARQ reference configuration for a serving cell, wherein the DL HARQ reference configuration corresponds to the adaptive UL-DL configuration; and 报告装置，用于按照所述DL HARQ参考配置，从所述UE向网络节点报告针对所述服务小区的自适应时分双工TDD HARQ-ACK反馈。a reporting device configured to report adaptive time division duplex TDD HARQ-ACK feedback for the serving cell from the UE to a network node according to the DL HARQ reference configuration. 22.如权利要求21所述的UE，还包括用于在所述UE处对从所述网络节点接收的DL HARQ参考配置进行处理的装置。22. The UE of claim 21, further comprising means for processing, at the UE, a DL HARQ reference configuration received from the network node. 23.如权利要求21所述的UE，还包括用于基于从所述网络节点经由系统信息块SIB接收的参考UL-DL配置来执行上行链路调度和HARQ反馈的装置。23. The UE of claim 21, further comprising means for performing uplink scheduling and HARQ feedback based on a reference UL-DL configuration received from the network node via a system information block SIB. 24.如权利要求21所述的UE，其中，所述DL HARQ参考配置是从所述网络节点经由更高层信令接收的。24. The UE of claim 21, wherein the DL HARQ reference configuration is received from the network node via higher layer signaling. 25.如权利要求21所述的UE，其中，所述UE被配置来支持基于流量状况的自适应UL-DL配置。25. The UE of claim 21, wherein the UE is configured to support adaptive UL-DL configuration based on traffic conditions. 26.一种网络节点，能够配置针对用户设备UE的混合自动重复请求-确认HARQ-ACK操作，所述网络节点包括：26. A network node capable of configuring a hybrid automatic repeat request-acknowledgement HARQ-ACK operation for a user equipment UE, the network node comprising: 用于识别针对服务小区的下行链路DL HARQ参考配置的装置，其中，所述DL HARQ参考配置对应于在所述UE处实施的自适应UL-DL配置；以及means for identifying a downlink DL HARQ reference configuration for a serving cell, wherein the DL HARQ reference configuration corresponds to an adaptive UL-DL configuration implemented at the UE; and 用于处理所述DL HARQ参考配置以从所述网络节点向所述UE传输的装置，其中，所述UE被配置来基于所述DL HARQ参考配置经由所述服务小区的物理上行链路控制信道PUCCH或物理上行链路共享信道PUSCH执行HARQ-ACK操作。means for processing the DL HARQ reference configuration for transmission from the network node to the UE, wherein the UE is configured to via a physical uplink control channel of the serving cell based on the DL HARQ reference configuration PUCCH or Physical Uplink Shared Channel PUSCH performs HARQ-ACK operation. 27.如权利要求26所述的网络节点，其中，在所述UE处执行的所述HARQ-ACK操作是时分双工TDD HARQ-ACK操作。27. The network node of claim 26, wherein the HARQ-ACK operation performed at the UE is a time division duplex TDD HARQ-ACK operation. 28.如权利要求26所述的网络节点，其中，所述DL HARQ参考配置经由更高层信令被传送给所述UE。28. The network node of claim 26, wherein the DL HARQ reference configuration is communicated to the UE via higher layer signaling. 29.如权利要求26所述的网络节点，其中，所述UE被配置来实施基于流量状况的自适应UL-DL配置。29. The network node of claim 26, wherein the UE is configured to implement an adaptive UL-DL configuration based on traffic conditions. 30.如权利要求26所述的网络节点，其中，所述网络节点包括基站BS、节点B NB、演进节点B eNB、基带单元BBU、射频拉远头RRH、射频拉远设备RRE、射频拉远单元RRU或中央处理模块CPM。30. The network node according to claim 26, wherein the network node comprises a base station BS, a node B NB, an evolved node B eNB, a baseband unit BBU, a remote radio head RRH, a remote radio equipment RRE, a remote radio frequency Unit RRU or Central Processing Module CPM.
CN201810332068.8A 2013-01-17 2013-10-08 Method and device for dynamically configuring UL/DL frame resource of TDD transmission Active CN108683485B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201361753914P 2013-01-17 2013-01-17
US61/753,914 2013-01-17
CN201380064664.8A CN104885389B (en) 2013-01-17 2013-10-08 For the uplink (UL) of time division duplex (TDD) transmission and the dynamic configuration of downlink (DL) frame resource

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201380064664.8A Division CN104885389B (en) 2013-01-17 2013-10-08 For the uplink (UL) of time division duplex (TDD) transmission and the dynamic configuration of downlink (DL) frame resource

Publications (2)

Publication Number Publication Date
CN108683485A CN108683485A (en) 2018-10-19
CN108683485B true CN108683485B (en) 2021-03-12

Family

ID=51209990

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810332068.8A Active CN108683485B (en) 2013-01-17 2013-10-08 Method and device for dynamically configuring UL/DL frame resource of TDD transmission

Country Status (3)

Country Link
JP (1) JP6418665B2 (en)
CN (1) CN108683485B (en)
HK (1) HK1258360A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3876620A4 (en) * 2018-11-01 2021-11-24 Fujitsu Limited METHOD AND DEVICE FOR RESOURCE DISPLAY AND COMMUNICATION SYSTEM
CN111385858B (en) * 2018-12-29 2022-04-05 华为技术有限公司 Communication method and communication device
CN110086567B (en) * 2019-03-22 2021-11-23 西安电子科技大学 Method for enhancing DCI (Downlink control information) carrying mode information of HARQ (hybrid automatic repeat request) stop process

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102017758A (en) * 2008-04-29 2011-04-13 爱立信电话股份有限公司 Aggregation of resources over multiple frames in a TDD communication system
CN102075949A (en) * 2010-12-22 2011-05-25 大唐移动通信设备有限公司 Carrier aggregation (CA) technology-based data transmission method and device

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009097902A1 (en) * 2008-02-08 2009-08-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatuses for authorising provision of indirected content associated with a presentity of a presence service
WO2010053418A1 (en) * 2008-11-10 2010-05-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for enabling services and media in a communication network
KR101720334B1 (en) * 2010-01-12 2017-04-05 삼성전자주식회사 Method and apparatus for supporting discontinuous reception operation in mobile communication system
MY168733A (en) * 2010-11-02 2018-11-29 Ericsson Telefon Ab L M Methods and devices for media description delivery
US8769076B2 (en) * 2011-02-14 2014-07-01 Telefonaktiebolaget L M Ericsson (Publ) Methods and systems for presence publication using SIP register feature tags
US8849950B2 (en) * 2011-04-07 2014-09-30 Qualcomm Incorporated Network streaming of video data using byte range requests
US20120284785A1 (en) * 2011-05-05 2012-11-08 Motorola Mobility, Inc. Method for facilitating access to a first access nework of a wireless communication system, wireless communication device, and wireless communication system
US9160779B2 (en) * 2011-06-30 2015-10-13 Qualcomm Incorporated Dynamic adaptive streaming proxy for unicast or broadcast/multicast services

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102017758A (en) * 2008-04-29 2011-04-13 爱立信电话股份有限公司 Aggregation of resources over multiple frames in a TDD communication system
CN102075949A (en) * 2010-12-22 2011-05-25 大唐移动通信设备有限公司 Carrier aggregation (CA) technology-based data transmission method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Dynamic reconfiguration of TDD UL-DL configuration;Samsung;《3GPP TSG-RAN WG1 #69 R1-122267》;20120525;全文 *

Also Published As

Publication number Publication date
JP6418665B2 (en) 2018-11-07
HK1258360A1 (en) 2019-11-08
JP2018057027A (en) 2018-04-05
CN108683485A (en) 2018-10-19

Similar Documents

Publication Publication Date Title
US11139932B2 (en) Dynamic configuration of uplink (UL) and downlink (DL) frame resources for a time division duplex (TDD) transmission
EP2847904B1 (en) A scheduling and hybrid automatic repeat request (harq) timing indication for an uplink-downlink (ul-dl) reconfiguration
US11330575B2 (en) Adaptation of communication parameters for a user equipment
US10405310B2 (en) Time division duplex (TDD) uplink downlink (UL-DL) reconfiguration
EP3111569B1 (en) Scheduling for an unlicensed carrier type
CN104584475B (en) Transmission of uplink control information in inter-eNB carrier aggregation
CN104205673B (en) Adaptive UL-DL TDD configurations in heterogeneous network
US10230502B2 (en) Hybrid automatic repeat request buffer configuration
JP2016508687A (en) Terminal communication method and apparatus in wireless communication system
CN104080187A (en) Dynamic time division duplex configuration method and base station using said method
CN108683485B (en) Method and device for dynamically configuring UL/DL frame resource of TDD transmission
JP2021520738A (en) Communication resource settings for dual connectivity
US20230247717A1 (en) Discontinuous reception alignment grouping for sidelink and cellular communication

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1258360

Country of ref document: HK

TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20200401

Address after: California, USA

Applicant after: INTEL Corp.

Address before: California, USA

Applicant before: INTEL IP Corp.

Effective date of registration: 20200401

Address after: California, USA

Applicant after: Apple Inc.

Address before: California, USA

Applicant before: INTEL Corp.

GR01 Patent grant
GR01 Patent grant