[go: up one dir, main page]

WO2014165690A1 - Virtual carrier sensing mechanism for long term evolution (lte) - Google Patents

Virtual carrier sensing mechanism for long term evolution (lte) Download PDF

Info

Publication number
WO2014165690A1
WO2014165690A1 PCT/US2014/032855 US2014032855W WO2014165690A1 WO 2014165690 A1 WO2014165690 A1 WO 2014165690A1 US 2014032855 W US2014032855 W US 2014032855W WO 2014165690 A1 WO2014165690 A1 WO 2014165690A1
Authority
WO
WIPO (PCT)
Prior art keywords
enb
transmission
confirmation
subsequent
notification
Prior art date
Application number
PCT/US2014/032855
Other languages
French (fr)
Inventor
Alexei Davydov
Vadim Sergeyev
Gregory Morozov
Apostolos Papathanassiou
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/141,179 external-priority patent/US20140301354A1/en
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Priority to PCT/US2014/032855 priority Critical patent/WO2014165690A1/en
Priority to CN201480011258.XA priority patent/CN105027469B/en
Publication of WO2014165690A1 publication Critical patent/WO2014165690A1/en
Priority to HK16104927.2A priority patent/HK1216952A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/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
    • 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
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/38—Transceivers, i.e. devices in which transmitter and receiver form a structural unit and in which at least one part is used for functions of transmitting and receiving
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • 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
    • H04L43/0823—Errors, e.g. transmission errors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • 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/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/613—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for the control of the source by the destination
    • 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
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1076—Resource dissemination mechanisms or network resource keeping policies for optimal resource availability in the overlay network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H04W36/0088—Scheduling hand-off measurements
    • 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H04W36/0094—Definition of hand-off measurement parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • 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/12—Wireless traffic scheduling
    • H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
    • 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
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/52—Allocation or scheduling criteria for wireless resources based on load
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • 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
    • 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
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • 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
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0636—Feedback format
    • H04B7/0639—Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1045—Proxies, e.g. for 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/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • 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
    • 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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points
    • 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

Definitions

  • the main performance limiting factor is interference.
  • the interference results from transmissions of neighboring base stations (BSs)/evolved Node Bs (eNBs).
  • BSs base stations
  • eNBs evolved Node Bs
  • the current approach is to coordinate transmissions of eNBs in several cells so the cells do not affect, or at least have less impact on, the reception of users in neighboring cells.
  • LTE provides various mechanisms for such coordination in
  • CoMP Coordinated Multipoint
  • FIG. 1 illustrates a wireless network according to an embodiment
  • FIG. 2 illustrates a flow chart of a method for provide virtual carrier sensing for LTE according to an embodiment
  • FIG. 3 is a message flow diagram illustrating method for providing a notification based on virtual carrier sensing for LTE according to an embodiment
  • FIG. 4 is a message flow diagram illustrating method for providing a confirmation to a notification based on virtual carrier sensing for LTE according to an embodiment
  • Fig. 5 illustrates an evolved Node B (eNB) according to an embodiment
  • FIG. 6 illustrates a block diagram of an example machine for providing virtual carrier sensing mechanism for LTE according to an embodiment.
  • a mechanism is provided to coordinate interference from neighboring eNBs when there is poor connectivity between the eNBs. Potential downlink transmissions are detected in the neighboring cell similar to virtual carrier sensing used in WiFi. Interference mitigation according to an embodiment may be implemented with coordinating eNBs that do not have backhaul link. Therefore, the interference mitigation according to an embodiment is more robust and provides system performance improvement even for simple deployments.
  • radio frame collisions may occur when simultaneous transmissions from several stations to the same or different stations interfere with each other thus becoming impossible to decode.
  • an exchange of short control frames is used prior to sending the large frame with the data payload.
  • RTS Request to Send
  • CTS Clear to Send
  • Each of these frames contains an indication of a time interval that the transmission would occupy.
  • Fig. 1 illustrates a wireless network 100 according to an embodiment.
  • evolved Node B one i.e., eNB l 110
  • eNB2 120 is the interfering cell.
  • UE 2 122 experiences interference 114 from eNBl 110 and UE 1 112 experiences interference 124 from eNB2 120.
  • eNB small cell eNBs
  • BTS base transceiver stations
  • eNBs evolved node Bs
  • SC-eNBs small cell evolved node Bs
  • Base transceiver station (BTS) may also refer to radio base station (BS), node B (in third generation (3G) networks, or base station (BS).
  • BS radio base station
  • BS node B
  • 3G third generation
  • BS base station
  • eNB will be used herein.
  • LTE uses a backhaul link 130 between the coordinated eNBs 110, 120 to provide coordination between eNBs 110, 120 using CoMP (Coordinated Multipoint) specifications.
  • CoMP Coordinated Multipoint
  • the eNBs 110, 120 may be connected over the backhaul link 130 to a radio network controller (RNC) 140.
  • RNC radio network controller
  • the eNBs i.e., eNBl 110 and eNB2 120, may include a controller and thus the RNC 140 may not be provided.
  • the connectivity provided by the backhaul link 130 between the coordinating eNBs 110, 120 may fail if the connection is absent, if delay associated with the backhaul link 130 presents a problem or if the backhaul link 130 has insufficient throughput performance. In these cases, the CoMP approach fails.
  • the interference 114, 124 has even more impact in the deployment with small cells due to use of a very large number of small cell eNBs (SC-eNBs) and the inability of operators to provide a predetermined backhaul connectivity between them.
  • SC-eNBs small cell eNBs
  • Fig. 2 illustrates a flow chart 200 of a method for provide virtual carrier sensing for LTE according to an embodiment.
  • Enabling downlink interference coordination involves interfering eNB 2 being aware of potential downlink transmission from eNBl to UE 1 in the home cell, the cell provided by eNBl .
  • eNB 1 sends a notification of subsequent DL transmission to the UE 1 in the downlink 210.
  • the notification includes information of how many sub frames will be used by the subsequent transmission, and which frequency resources, physical resource blocks (PRBs), will be used.
  • PRBs physical resource blocks
  • the notification may be transmitted in the Downlink Control Information (DCI) field in order to enable the UE 1 to process the notification quickly, e.g., within up to 4 sub frames.
  • DCI Downlink Control Information
  • the eNB2 cannot hear this notification because the eNB2 is also transmitting in the same time-frequency resources.
  • UE 1 sends a confirmation of the received DL notification 220. In this confirmation, the UE 1 includes information of the DL frame resources that eNBl plans to use when sending data to UE 1.
  • eNB2 can overhear the confirmation, decode it and extract the information of the DL resources that eNB 1 is planning to use 230.
  • a determination is made whether eNB2 is already transmitting in the indicated DL resources 240. If not 242, eNB2 marks the indicated DL resources as busy and refrains from transmitting in those resources 250. If yes 244, a determination is made whether the eNB2 was going to occupy these resources itself to transmit data to UE 2 260. If not 262, the eNB2 does not reschedule the transmission to alternative resources 270. If yes 264, the eNB2 reschedules the transmission using alternative resources so that interference with eNB l to UE 1 transmission is avoided 280.
  • Fig. 3 is a message flow diagram 300 illustrating method for providing a notification based on virtual carrier sensing for LTE according to an embodiment.
  • two eNBs are shown: eNBl 310 and eNB2 320.
  • the eNBl 310 and eNB2 320 may operate in accordance with a Third Generation Partnership Project (3GPP) LTE/LTE-A (Long Term Evolution/Long Term Evolution- Advanced) or other suitable wireless wide area network (WWAN) protocol, and may include a configuration to provide wireless network communications in operation with an evolved packet core (EPC) 360, for communication of data to an Internet Protocol (IP) network 370.
  • 3GPP Third Generation Partnership Project
  • LTE/LTE-A Long Term Evolution/Long Term Evolution- Advanced
  • WWAN wireless wide area network
  • EPC evolved packet core
  • IP Internet Protocol
  • Both eNBl 310 and eNB2 320 plan to transmit to their respective UEs, UE 1 312 and UE 2 322, and, in accordance with their plans, transmissions are going to overlap in frequency.
  • the eNBl 310 sends a notification 330 to UE 1 312.
  • the potential eNBl/UE 1 transmission 340 is shown overlapping with the planned eNB2/UE 2 transmission 350.
  • Fig. 4 is a message flow diagram 400 illustrating method for providing a confirmation to a notification based on virtual carrier sensing for LTE according to an embodiment.
  • UE 1 412 sends a confirmation 460 to eNBl 410.
  • the eNBl 410 and eNB2 420 may again provide wireless network communications in operation with an evolved packet core (EPC) 460, for communication of data to an Internet Protocol (IP) network 470.
  • EPC evolved packet core
  • IP Internet Protocol
  • eNB2 420 overhears the confirmation 480 sent by UE 1 412.
  • the eNB2 420 may thus reschedule its planned transmission to the UE 2 422.
  • the reschedule eNB2/UE 2 transmission 450 does not overlap with the potential eNBl/UE 1 transmission 440.
  • Fig. 5 illustrates an evolved Node B (eNB) 500 according to an embodiment.
  • the eNB 500 contains at least one radio transmitter 510, receiver 512, an antenna system 514, a control section 516, memory 518 and a power supply 520.
  • the control section 516 of the eNB 500 may include a controller 530.
  • the controller may be arranged to provide resource management and logic control functions for allowing eNBs to directly communicate with each other.
  • the controller 530 of the eNB 500 may also provide functions including radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, scheduling and transmitting messages (incoming calls and connection requests), broadcast information coordination (system information), and measurement reporting (to assist in handover decisions).
  • RRM radio resource management
  • the controller 530 is further arranged to transmit PDSCH data and DM-RS to the UE(s).
  • the controller 530 Upon receiving CQI feedback from the UE(s), the controller 530 is arranged to apply and/or adjust the MCS and include the applied and/or adjusted MCS to the next PDSCH.
  • the eNB 500 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the controller 530 may be capable of executing instructions (sequential or otherwise) that specify actions to be taken by the eNB 500.
  • the term "controller” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
  • At least a part of one or more computer systems may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on at least one machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • At least one machine readable medium 580 may be used to store one or more sets of data structures or instructions 582 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 582 may also reside, at least partially, on additional machine readable memories such as memory 518, or within the controller 530 during execution thereof by the eNB 500.
  • additional machine readable memories such as memory 518, or within the controller 530 during execution thereof by the eNB 500.
  • one or any combination of the controller 530, the memory 518, etc. may constitute machine readable media.
  • the machine readable medium 580 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 582.
  • machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the eNB 500 and that cause the eNB 500 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
  • machine readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • the instructions 582 may further be transmitted or received over bus 552 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • FIG. 6 illustrates a block diagram of an example machine 600 for providing virtual carrier sensing mechanism for LTE according to an embodiment upon which any one or more of the techniques (e.g.,
  • the machine 600 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 600 may operate in the capacity of a server machine and/or a client machine in server-client network environments. In an example, the machine 600 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment.
  • the machine 600 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA Personal Digital Assistant
  • machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
  • cloud computing software as a service
  • SaaS software as a service
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • at least a part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors 602 may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on at least one machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform at least part of any operation described herein.
  • modules are temporarily configured, a module need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor 602 configured using software; the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • application or variants thereof, is used expansively herein to include routines, program modules, programs, components, and the like, and may be implemented on various system configurations, including single-processor or multiprocessor systems, microprocessor-based electronics, single-core or multi-core systems, combinations thereof, and the like.
  • application may be used to refer to an embodiment of software or to hardware arranged to perform at least part of any operation described herein.
  • Machine 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, at least some of which may communicate with others via an interlink (e.g., bus) 608.
  • the machine 600 may further include a display unit 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse).
  • the display unit 610, input device 612 and UI navigation device 614 may be a touch screen display.
  • the machine 600 may additionally include a storage device (e.g., drive unit) 616, a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • the machine 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (I )) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB)
  • parallel e.g., parallel, or other wired or wireless (e.g., infrared (I ) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • I infrared
  • the storage device 616 may include at least one machine readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 624 may also reside, at least partially, additional machine readable memories such as main memory 604, static memory 606, or within the hardware processor 602 during execution thereof by the machine 600.
  • main memory 604, static memory 606, or the storage device 616 may constitute machine readable media.
  • machine readable medium 622 is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 624.
  • machine readable medium may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 624.
  • machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and that cause the machine 600 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
  • machine readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • non- volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., electrically Erasable Programmable Read-Only Memory (EEPROM)
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., electrically Erasable Programmable
  • the instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks ((e.g., channel access methods including Code Division Multiple Access (CDMA), Time-division multiple access (TDMA), Frequency-division multiple access (FDMA), and Orthogonal Frequency Division Multiple Access (OFDMA) and cellular networks such as Global System for Mobile
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • CDMA 2000 lx* standards and Long Term Evolution (LTE) Plain Old Telephone
  • POTS Plain Old Telephone
  • IEEE Institute of Electrical and Electronics Engineers
  • WiFi IEEE 802.11 standards
  • WiMax® IEEE 802.16 standards
  • P2P peer-to-peer
  • the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 626.
  • the network interface device 620 may include a plurality of antennas to wirelessly communicate using at least one of single- input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques.
  • SIMO single- input multiple-output
  • MIMO multiple-input multiple-output
  • MISO multiple-input single-output
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 600, and includes digital or analog
  • embodiments may include fewer features than those disclosed in a particular example.
  • the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment.
  • the scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Embodiments for providing virtual carrier sensing for LTE are generally described herein. In some embodiments, a first evolved Node B (eNB) sends a notification of subsequent DL transmission to a first UE in a downlink. In the uplink, the first UE sends a confirmation of the received DL notification. A second eNB overhears the confirmation, decodes it and extracts the information of the DL resources that the first eNB is planning to use. If the second eNB is not already transmitting in the indicated DL resources, the second eNB marks the indicated DL resources as busy and refrains from transmitting in those resources. The second eNB may then reschedule its transmission using alternative resources so that interference from the second eNB1 may be avoided.

Description

VIRTUAL CARRIER SENSING MECHANISM FOR LONG TERM EVOLUTION (LTE)
CLAIM OF PRIORITY
[0001] This application claims the benefit of priority to U.S. Patent
Application Serial No. 14/141,179, filed on December 26, 2013, which claims the benefit of priority to U.S. Provisional Patent Application Serial No.
61/808,597, filed on April 4, 2013, each of which is incorporated herein by reference in its entirety.
BACKGROUND
[0002] In cellular communication systems working below 10 GHz, and LTE in particular, the main performance limiting factor is interference. In the downlink, the interference results from transmissions of neighboring base stations (BSs)/evolved Node Bs (eNBs). To reduce interference in the downlink, the current approach is to coordinate transmissions of eNBs in several cells so the cells do not affect, or at least have less impact on, the reception of users in neighboring cells.
[0003] LTE provides various mechanisms for such coordination in
CoMP (Coordinated Multipoint) specifications. However, this type of coordination uses a backhaul link between the coordinated eNBs. For example, current interference coordination mechanisms that use backhaul connectivity between the coordinating eNBs fail if the connection is absent, if the backhaul link delay presents a problem or if the backhaul link has insufficient throughput performance. In these cases, the CoMP approach fails. The interference problem has even more impact in the deployment with small cells due to very large number of small cell eNBs (SC-eNBs) and the inability of operators to provide a predetermined backhaul connectivity between them. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Fig. 1 illustrates a wireless network according to an embodiment;
[0005] Fig. 2 illustrates a flow chart of a method for provide virtual carrier sensing for LTE according to an embodiment;
[0006] Fig. 3 is a message flow diagram illustrating method for providing a notification based on virtual carrier sensing for LTE according to an embodiment;
[0007] Fig. 4 is a message flow diagram illustrating method for providing a confirmation to a notification based on virtual carrier sensing for LTE according to an embodiment;
[0008] Fig. 5 illustrates an evolved Node B (eNB) according to an embodiment; and
[0009] Fig. 6 illustrates a block diagram of an example machine for providing virtual carrier sensing mechanism for LTE according to an embodiment.
DETAILED DESCRIPTION
[0011] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass available equivalents of those claims.
[0012] According to an embodiment, a mechanism is provided to coordinate interference from neighboring eNBs when there is poor connectivity between the eNBs. Potential downlink transmissions are detected in the neighboring cell similar to virtual carrier sensing used in WiFi. Interference mitigation according to an embodiment may be implemented with coordinating eNBs that do not have backhaul link. Therefore, the interference mitigation according to an embodiment is more robust and provides system performance improvement even for simple deployments.
[0013] In Wi-Fi® networks, radio frame collisions may occur when simultaneous transmissions from several stations to the same or different stations interfere with each other thus becoming impossible to decode. To reduce the number of radio frame collisions in Wi-Fi® networks, an exchange of short control frames is used prior to sending the large frame with the data payload. These are Request to Send (RTS) and Clear to Send (CTS) frames that are sent, respectively, by initiator and recipient of the intended transmission. Each of these frames contains an indication of a time interval that the transmission would occupy. Thus stations around the initiator and recipient become aware of the intended transmission and keep silent for the indicated period, which allows the communication to be successfully sent.
[0014] Fig. 1 illustrates a wireless network 100 according to an embodiment. In Fig. 1 , evolved Node B one, i.e., eNB l 110, is the home cell, and eNB2 120 is the interfering cell. UE 2 122 experiences interference 114 from eNBl 110 and UE 1 112 experiences interference 124 from eNB2 120.
The interference problem is even more of a problem in networks with small cells due to very large number of small cell eNBs (SC-eNBs). Those skilled in the art will recognize the term eNB may be used to refer to base transceiver stations (BTSs), evolved node Bs (eNBs), small cell evolved node Bs (SC-eNBs), etc. Base transceiver station (BTS) may also refer to radio base station ( BS), node B (in third generation (3G) networks, or base station (BS). However, to provide clarity, eNB will be used herein. LTE uses a backhaul link 130 between the coordinated eNBs 110, 120 to provide coordination between eNBs 110, 120 using CoMP (Coordinated Multipoint) specifications. The eNBs 110, 120 may be connected over the backhaul link 130 to a radio network controller (RNC) 140. However, those skilled in the art will recognize that the eNBs, i.e., eNBl 110 and eNB2 120, may include a controller and thus the RNC 140 may not be provided. The connectivity provided by the backhaul link 130 between the coordinating eNBs 110, 120 may fail if the connection is absent, if delay associated with the backhaul link 130 presents a problem or if the backhaul link 130 has insufficient throughput performance. In these cases, the CoMP approach fails. The interference 114, 124 has even more impact in the deployment with small cells due to use of a very large number of small cell eNBs (SC-eNBs) and the inability of operators to provide a predetermined backhaul connectivity between them.
[0015] Fig. 2 illustrates a flow chart 200 of a method for provide virtual carrier sensing for LTE according to an embodiment. Enabling downlink interference coordination, in LTE for example, involves interfering eNB 2 being aware of potential downlink transmission from eNBl to UE 1 in the home cell, the cell provided by eNBl . To achieve this, eNB 1 sends a notification of subsequent DL transmission to the UE 1 in the downlink 210. The notification includes information of how many sub frames will be used by the subsequent transmission, and which frequency resources, physical resource blocks (PRBs), will be used. The notification may be transmitted in the Downlink Control Information (DCI) field in order to enable the UE 1 to process the notification quickly, e.g., within up to 4 sub frames. The eNB2 cannot hear this notification because the eNB2 is also transmitting in the same time-frequency resources. In the uplink, UE 1 sends a confirmation of the received DL notification 220. In this confirmation, the UE 1 includes information of the DL frame resources that eNBl plans to use when sending data to UE 1.
[0016] Since UE 1 sends its confirmation in the uplink resources, eNB2 can overhear the confirmation, decode it and extract the information of the DL resources that eNB 1 is planning to use 230. A determination is made whether eNB2 is already transmitting in the indicated DL resources 240. If not 242, eNB2 marks the indicated DL resources as busy and refrains from transmitting in those resources 250. If yes 244, a determination is made whether the eNB2 was going to occupy these resources itself to transmit data to UE 2 260. If not 262, the eNB2 does not reschedule the transmission to alternative resources 270. If yes 264, the eNB2 reschedules the transmission using alternative resources so that interference with eNB l to UE 1 transmission is avoided 280.
[0017] Fig. 3 is a message flow diagram 300 illustrating method for providing a notification based on virtual carrier sensing for LTE according to an embodiment. In Fig. 3, two eNBs are shown: eNBl 310 and eNB2 320. The eNBl 310 and eNB2 320 may operate in accordance with a Third Generation Partnership Project (3GPP) LTE/LTE-A (Long Term Evolution/Long Term Evolution- Advanced) or other suitable wireless wide area network (WWAN) protocol, and may include a configuration to provide wireless network communications in operation with an evolved packet core (EPC) 360, for communication of data to an Internet Protocol (IP) network 370. Both eNBl 310 and eNB2 320 plan to transmit to their respective UEs, UE 1 312 and UE 2 322, and, in accordance with their plans, transmissions are going to overlap in frequency. The eNBl 310 sends a notification 330 to UE 1 312. The potential eNBl/UE 1 transmission 340 is shown overlapping with the planned eNB2/UE 2 transmission 350.
[0018] Fig. 4 is a message flow diagram 400 illustrating method for providing a confirmation to a notification based on virtual carrier sensing for LTE according to an embodiment. In Fig. 4, UE 1 412 sends a confirmation 460 to eNBl 410. The eNBl 410 and eNB2 420 may again provide wireless network communications in operation with an evolved packet core (EPC) 460, for communication of data to an Internet Protocol (IP) network 470. However, eNB2 420 overhears the confirmation 480 sent by UE 1 412. The eNB2 420 may thus reschedule its planned transmission to the UE 2 422. The reschedule eNB2/UE 2 transmission 450 does not overlap with the potential eNBl/UE 1 transmission 440.
[0019] Fig. 5 illustrates an evolved Node B (eNB) 500 according to an embodiment. The eNB 500 contains at least one radio transmitter 510, receiver 512, an antenna system 514, a control section 516, memory 518 and a power supply 520. The control section 516 of the eNB 500 may include a controller 530. The controller may be arranged to provide resource management and logic control functions for allowing eNBs to directly communicate with each other.
[0020] The controller 530 of the eNB 500 may also provide functions including radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, scheduling and transmitting messages (incoming calls and connection requests), broadcast information coordination (system information), and measurement reporting (to assist in handover decisions). The controller 530 is further arranged to transmit PDSCH data and DM-RS to the UE(s). Upon receiving CQI feedback from the UE(s), the controller 530 is arranged to apply and/or adjust the MCS and include the applied and/or adjusted MCS to the next PDSCH.
[0021] In alternative embodiments, the eNB 500 may operate as a standalone device or may be connected (e.g., networked) to other machines. The controller 530 may be capable of executing instructions (sequential or otherwise) that specify actions to be taken by the eNB 500. Further, while a single controller 530 is illustrated, the term "controller" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. In an example, at least a part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more controller 530 may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on at least one machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
[0022] At least one machine readable medium 580 may be used to store one or more sets of data structures or instructions 582 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 582 may also reside, at least partially, on additional machine readable memories such as memory 518, or within the controller 530 during execution thereof by the eNB 500. In an example, one or any combination of the controller 530, the memory 518, etc. may constitute machine readable media. While the machine readable medium 580 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 582.
[0023] The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the eNB 500 and that cause the eNB 500 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The instructions 582, may further be transmitted or received over bus 552 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
[0024] Fig. 6 illustrates a block diagram of an example machine 600 for providing virtual carrier sensing mechanism for LTE according to an embodiment upon which any one or more of the techniques (e.g.,
methodologies) discussed herein may perform. In alternative embodiments, the machine 600 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 600 may operate in the capacity of a server machine and/or a client machine in server-client network environments. In an example, the machine 600 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 600 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
[0025] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, at least a part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors 602 may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on at least one machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
[0026] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform at least part of any operation described herein. Considering examples in which modules are temporarily configured, a module need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor 602 configured using software; the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. The term "application," or variants thereof, is used expansively herein to include routines, program modules, programs, components, and the like, and may be implemented on various system configurations, including single-processor or multiprocessor systems, microprocessor-based electronics, single-core or multi-core systems, combinations thereof, and the like. Thus, the term application may be used to refer to an embodiment of software or to hardware arranged to perform at least part of any operation described herein.
[0027] Machine (e.g., computer system) 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, at least some of which may communicate with others via an interlink (e.g., bus) 608. The machine 600 may further include a display unit 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In an example, the display unit 610, input device 612 and UI navigation device 614 may be a touch screen display. The machine 600 may additionally include a storage device (e.g., drive unit) 616, a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (I )) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
[0028] The storage device 616 may include at least one machine readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 624 may also reside, at least partially, additional machine readable memories such as main memory 604, static memory 606, or within the hardware processor 602 during execution thereof by the machine 600. In an example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute machine readable media.
[0029] While the machine readable medium 622 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 624.
[0030] The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and that cause the machine 600 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0031] The instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks ((e.g., channel access methods including Code Division Multiple Access (CDMA), Time-division multiple access (TDMA), Frequency-division multiple access (FDMA), and Orthogonal Frequency Division Multiple Access (OFDMA) and cellular networks such as Global System for Mobile
Communications (GSM), Universal Mobile Telecommunications System (UMTS), CDMA 2000 lx* standards and Long Term Evolution (LTE)), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802 family of standards including IEEE 802.11 standards (WiFi), IEEE 802.16 standards (WiMax®) and others), peer-to-peer (P2P) networks, or other protocols now known or later developed.
[0032] For example, the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 626. In an example, the network interface device 620 may include a plurality of antennas to wirelessly communicate using at least one of single- input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 600, and includes digital or analog
communications signals or other intangible medium to facilitate communication of such software.
[0033] The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as "examples." Such examples may include elements in addition to those shown or described.
However, also contemplated are examples that include the elements shown or described. Moreover, also contemplate are examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
[0034] Publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) are supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
[0035] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In the appended claims, the terms "including" and "in which" are used as the plain- English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to suggest a numerical order for their objects.
The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with others. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure, for example, to comply with 37 C.F.R. § 1.72(b) in the United States of America. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. However, the claims may not set forth features disclosed herein because embodiments may include a subset of said features. Further, embodiments may include fewer features than those disclosed in a particular example. Thus, the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment. The scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

CLAIMS What is claimed is:
1. A method for providing virtual carrier sensing for long term
evolution (LTE), comprising:
receiving in a first downlink transmission from an evolved Node B
(eNB) a notification of a subsequent downlink (DL) transmission, the notification including information identifying DL frame resources the eNB plans to use in a subsequent DL transmission; and
sending a confirmation of the received DL notification in an uplink, wherein the confirmation includes the information identifying DL frame resources the eNB plans to use in the subsequent DL transmission.
2. The method of claim 1 , wherein the receiving the notification including information identifying DL frame resources the eNB plans to use in the subsequent DL transmission comprises receiving the notification including information identifying how many sub frames will be used by the subsequent transmission, and which frequency associated with physical resource blocks (PRBs) will be used.
3. The method of claim 1 , wherein receiving the notification further comprises receiving the notification in a Downlink Control Information (DCI) field.
4. The method of claim 3 , wherein the receiving the notification in the Downlink Control Information (DCI) field comprises receiving the notification using a same time-frequency resource.
5. The method of claim 1 , wherein the sending the confirmation in the uplink comprises sending the confirmation in an uplink received by at least a second eNB for allowing the at least second eNB to reschedule its transmissions using a time-frequency resources different than time- frequency resources used in the subsequent transmission of the eNB.
6. The method of claim 1 further comprises operating in accordance with a Third Generation Partnership Project (3GPP) LTE/LTE-A (Long Term Evolution/Long Term Evolution- Advanced).
7. A method for providing virtual carrier sensing for long term evolution (LTE), comprising:
monitoring an uplink for an uplink transmission from a user equipment
(UE);
receiving a confirmation of a DL notification in an uplink transmission; and
processing the confirmation in the uplink transmission to identify DL frame resources at least a second eNB plans to use in a subsequent DL transmission by the at least second eNB.
8. The method of claim 7, wherein the receiving the confirmation further comprises receiving a confirmation from the UE in response to the UE receiving a notification including information identifying how many subframes will be used by the subsequent transmission, and which frequency associated with physical resource blocks (PRBs) will be used.
9. The method of claim 7 further comprises decoding the confirmation, extracting information from the decoded confirmation associated with the information identifying how many subframes will be used by the subsequent transmission, and which frequency associated with physical resource blocks (PRBs) will be used.
10. The method of claim 9 further comprising rescheduling transmissions based on the extracted information to uses a time-frequency resources different than time- frequency resources used in the subsequent transmission of the at least second eNB.
11. The method of claim 7 further comprising marking DL frame resources the at least second eNB plans to use in a subsequent DL transmission as busy and refraining from using the marked DL frame resources.
12. An evolved Node B (eNB), comprising:
a transceiver for receiving and transmitting signals; and
a controller, coupled to the transceivers, the controller arranged to provide virtual carrier sensing for long term evolution (LTE) by:
receiving in a first downlink transmission from an evolved Node B (eNB) a notification of a subsequent downlink (DL) transmission, the notification including information identifying DL frame resources the eNB plans to use in a subsequent DL transmission; and
sending a confirmation of the received DL notification in an uplink, wherein the confirmation includes the information identifying DL frame resources the eNB plans to use in the subsequent DL transmission.
13. The eNB of claim 12, wherein the controller further receives the notification including information identifying how many subframes will be used by the subsequent transmission, and which frequency associated with physical resource blocks (PRBs) will be used.
14. The eNB of claim 12, wherein the controller further receives the notification in a Downlink Control Information (DCI) field.
15. The eNB of claim 14, wherein the controller further receives the notification in the Downlink Control Information (DCI) field using a same time- frequency resource.
16. The eNB of claim 12, wherein the controller further sends the confirmation in an uplink received by at least a second eNB for allowing the at least second eNB to reschedule its transmissions using a time- frequency resources different than time- frequency resources used in the subsequent transmission of the eNB.
17. The eNB of claim 12, wherein the controller further operates in accordance with a Third Generation Partnership Project (3GPP) LTE/LTE-A (Long Term Evolution/Long Term Evolution- Advanced).
18. An evolved Node B (eNB) for providing virtual carrier sensing for long term evolution (LTE), comprising:
a transceiver for receiving and transmitting signals; and
a controller, coupled to the transceivers, the controller arranged to provide virtual carrier sensing for long term evolution (LTE) by:
monitoring an uplink for an uplink transmission from a user equipment (UE);
receiving a confirmation of a DL notification in an uplink transmission; and
processing the confirmation in the uplink transmission to identify DL frame resources at least a second eNB plans to use in a subsequent DL transmission by the at least second eNB.
19. The eNB of claim 18, wherein the controller further receives a confirmation from the UE in response to the UE receiving a notification including information identifying how many subframes will be used by the subsequent transmission, and which frequency associated with physical resource blocks (PRBs) will be used.
20. The eNB of claim 18, wherein the controller further decodes the confirmation and extracts information from the decoded confirmation associated with the information identifying how many subframes will be used by the subsequent transmission, and which frequency associated with physical resource blocks (PRBs) will be used.
21. The eNB of claim 20, wherein the controller further reschedules transmissions based on the extracted information to uses a time-frequency resources different than time- frequency resources used in the subsequent transmission of the at least second eNB.
22. The eNB of claim 18, wherein the controller further marks DL frame resources the at least second eNB plans to use in a subsequent DL transmission as busy and refrains from using the marked DL frame resources.
PCT/US2014/032855 2013-04-04 2014-04-03 Virtual carrier sensing mechanism for long term evolution (lte) WO2014165690A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/US2014/032855 WO2014165690A1 (en) 2013-04-04 2014-04-03 Virtual carrier sensing mechanism for long term evolution (lte)
CN201480011258.XA CN105027469B (en) 2013-04-04 2014-04-03 Virtual carrier detection mechanism for Long Term Evolution (LTE)
HK16104927.2A HK1216952A1 (en) 2013-04-04 2016-04-29 Virtual carrier sensing mechanism for long term evolution (lte) (lte)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US201361808597P 2013-04-04 2013-04-04
US61/808,597 2013-04-04
US14/141,179 US20140301354A1 (en) 2013-04-04 2013-12-26 Virtual carrier sensing mechanism for long term evolution (lte)
US14/141,179 2013-12-26
PCT/US2014/032855 WO2014165690A1 (en) 2013-04-04 2014-04-03 Virtual carrier sensing mechanism for long term evolution (lte)

Publications (1)

Publication Number Publication Date
WO2014165690A1 true WO2014165690A1 (en) 2014-10-09

Family

ID=94380292

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/032855 WO2014165690A1 (en) 2013-04-04 2014-04-03 Virtual carrier sensing mechanism for long term evolution (lte)

Country Status (3)

Country Link
CN (1) CN105027469B (en)
HK (1) HK1216952A1 (en)
WO (1) WO2014165690A1 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9191178B2 (en) 2013-04-04 2015-11-17 Intel IP Corporation Enhanced node B and method for RRC connection establishment for small data transfers
US9445338B2 (en) 2013-04-04 2016-09-13 Intel IP Corporation Reconfiguration control channel resource mapping collision avoidance
US9674757B2 (en) 2013-04-04 2017-06-06 Intel IP Corporation User equipment and methods for cell reselection using scaled time-to-trigger and A3 offset values
US9794876B2 (en) 2013-03-29 2017-10-17 Intel IP Corporation Extended paging discontinuous reception (DRX) cycles in wireless communication networks
US10587389B2 (en) 2013-01-03 2020-03-10 Apple Inc. Apparatus and method for single-tone device discovery in wireless communication networks
TWI717582B (en) * 2017-01-25 2021-02-01 宏碁股份有限公司 Method of mapping data packets and related apparatuses using the same
US11979236B2 (en) 2018-09-28 2024-05-07 Apple Inc. Physical uplink control channel resource determination and multiplexing of multiple hybrid automatic repeat request acknowledgement feedbacks and other uplink control information on physical uplink control channel and physical uplink shared channel

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108574986A (en) * 2017-03-10 2018-09-25 华为技术有限公司 Method, terminal device and the network equipment of notification information

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090124261A1 (en) * 2006-07-14 2009-05-14 Fujitsu Limited Mobile communication system and base station
US20090245182A1 (en) * 2008-03-25 2009-10-01 Qualcomm Incorporated Adaptively reacting to resource utilization messages including channel gain indication
WO2011119750A1 (en) * 2010-03-23 2011-09-29 Interdigital Patent Holdings, Inc. Method, apparatus and system for enabling resource coordination in cellular networks
US20120127938A1 (en) * 2009-05-22 2012-05-24 Huawei Technologies Co., Ltd. Multi-Subframe Scheduling Method, Multi-Subframe Scheduling System, Terminal, and Base Station
US20130010769A1 (en) * 2011-07-05 2013-01-10 Seoul National University R&Db Foundation Method and apparatus for reserving data channel in a wireless access system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1338125A2 (en) * 2000-11-03 2003-08-27 AT & T Corp. Tiered contention multiple access (tcma): a method for priority-based shared channel access

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090124261A1 (en) * 2006-07-14 2009-05-14 Fujitsu Limited Mobile communication system and base station
US20090245182A1 (en) * 2008-03-25 2009-10-01 Qualcomm Incorporated Adaptively reacting to resource utilization messages including channel gain indication
US20120127938A1 (en) * 2009-05-22 2012-05-24 Huawei Technologies Co., Ltd. Multi-Subframe Scheduling Method, Multi-Subframe Scheduling System, Terminal, and Base Station
WO2011119750A1 (en) * 2010-03-23 2011-09-29 Interdigital Patent Holdings, Inc. Method, apparatus and system for enabling resource coordination in cellular networks
US20130010769A1 (en) * 2011-07-05 2013-01-10 Seoul National University R&Db Foundation Method and apparatus for reserving data channel in a wireless access system

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10587389B2 (en) 2013-01-03 2020-03-10 Apple Inc. Apparatus and method for single-tone device discovery in wireless communication networks
US9794876B2 (en) 2013-03-29 2017-10-17 Intel IP Corporation Extended paging discontinuous reception (DRX) cycles in wireless communication networks
US9191178B2 (en) 2013-04-04 2015-11-17 Intel IP Corporation Enhanced node B and method for RRC connection establishment for small data transfers
US9445338B2 (en) 2013-04-04 2016-09-13 Intel IP Corporation Reconfiguration control channel resource mapping collision avoidance
US9674757B2 (en) 2013-04-04 2017-06-06 Intel IP Corporation User equipment and methods for cell reselection using scaled time-to-trigger and A3 offset values
US9930647B2 (en) 2013-04-04 2018-03-27 Intel IP Corporation Enhanced node B and method for RRC connection establishment for small data transfers
TWI717582B (en) * 2017-01-25 2021-02-01 宏碁股份有限公司 Method of mapping data packets and related apparatuses using the same
US11979236B2 (en) 2018-09-28 2024-05-07 Apple Inc. Physical uplink control channel resource determination and multiplexing of multiple hybrid automatic repeat request acknowledgement feedbacks and other uplink control information on physical uplink control channel and physical uplink shared channel
US12095570B2 (en) 2018-09-28 2024-09-17 Apple Inc. Physical uplink control channel resource determination and multiplexing of multiple hybrid automatic repeat request acknowledgement feedbacks and other uplink control information on physical uplink control channel and physical uplink shared channel

Also Published As

Publication number Publication date
CN105027469B (en) 2019-06-14
CN105027469A (en) 2015-11-04
HK1216952A1 (en) 2016-12-09

Similar Documents

Publication Publication Date Title
US20140301354A1 (en) Virtual carrier sensing mechanism for long term evolution (lte)
JP6940590B2 (en) Methods and equipment for beam information for independent links
US9609564B2 (en) Fast modulation and coding scheme adaptation protocol for long term evolution with multiple-user multiple input, multiple output
EP3416437B1 (en) User equipment, base station and corresponding computer readable hardware devices for mtc coexistence
CN115398962B (en) Measuring cross-link interference
JP7040617B2 (en) Signaling instruction and reception method, device and communication system
WO2014165690A1 (en) Virtual carrier sensing mechanism for long term evolution (lte)
US20170347286A1 (en) Method of enhanced interference measurements for channel state information (csi) feedback
KR20220003665A (en) User equipment use of dual-beam to support multi-connectivity in a wireless communication network
EP2963985B1 (en) Method, access point, server, and station used for coordinated transmission
CN112385171A (en) Sounding reference signal and channel state information reference signal enhancements for coordinated multipoint communication
CN114245979B (en) Uplink power control through MAC-CE messaging
EP3669570A1 (en) Configure measurement gaps for csi-rs from neighbor cells in nr
KR20240122433A (en) Cell wake-up signaling
CN105580411B (en) Base station, user terminal, and wireless communication method
US20220286179A1 (en) Channel state information for multiple communication links
US20240039669A1 (en) Reference signal transmission
CN119769052A (en) Techniques for dynamic transmission parameter adaptation
WO2022240993A1 (en) Uplink reference signal transmissions during power saving operations
CN116438758A (en) Enhanced decoding feedback for traffic type differentiation
CN116134753A (en) Techniques for beam switching in wireless communications
WO2024093983A1 (en) Concurrent or overlapping measurement gaps for layer one and layer three measurements
WO2024103197A1 (en) Overhead reduction for feedback on beam prediction results
CN115298985B (en) Transmission order determination for aperiodic channel state information
WO2023245481A1 (en) Deadline based hybrid automatic repeat request retransmission

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201480011258.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14779707

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14779707

Country of ref document: EP

Kind code of ref document: A1