EP3896893B1 - Selbst- und trägerübergreifende planung - Google Patents

Selbst- und trägerübergreifende planung Download PDF

Info

Publication number
EP3896893B1
EP3896893B1 EP21178912.8A EP21178912A EP3896893B1 EP 3896893 B1 EP3896893 B1 EP 3896893B1 EP 21178912 A EP21178912 A EP 21178912A EP 3896893 B1 EP3896893 B1 EP 3896893B1
Authority
EP
European Patent Office
Prior art keywords
carrier
dci
downlink
transmission
search space
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
EP21178912.8A
Other languages
English (en)
French (fr)
Other versions
EP3896893A1 (de
Inventor
Alexander Golitschek Edler Von Elbwart
Hidetoshi Suzuki
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.)
Panasonic Intellectual Property Corp of America
Original Assignee
Panasonic Intellectual Property Corp of America
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 Panasonic Intellectual Property Corp of America filed Critical Panasonic Intellectual Property Corp of America
Priority to EP21178912.8A priority Critical patent/EP3896893B1/de
Publication of EP3896893A1 publication Critical patent/EP3896893A1/de
Application granted granted Critical
Publication of EP3896893B1 publication Critical patent/EP3896893B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • 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), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/0006—Assessment of spectral gaps suitable for allocating digitally modulated signals, e.g. for carrier allocation in cognitive radio
    • 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—Signaling for the administration of the divided path
    • 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—Signaling for the administration of the divided path
    • 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/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, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0808—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using carrier sensing, e.g. as in CSMA

Definitions

  • the present disclosure relates to scheduling in a band shared by two different radio access technology systems.
  • High-Speed Downlink Packet Access HSDPA
  • HSUPA High Speed Uplink Packet Access
  • LTE Long Term Evolution
  • LTE Long-Term Evolution
  • UTRA Evolved UMTS Terrestrial Radio Access
  • UTRAN UMTS Terrestrial Radio Access Network
  • LTE Rel. 8 The LTE system represents efficient packet-based radio access and radio access networks that provide full IP-based functionalities with low latency and low cost.
  • scalable multiple transmission bandwidths are specified such as 1.4, 3.0, 5.0, 10.0, 15.0, and 20.0 MHz, in order to achieve flexible system deployment using a given spectrum.
  • Orthogonal Frequency Division Multiplexing OFDM-based radio access was adopted because of its inherent immunity to multipath interference (MPI) due to a low symbol rate, the use of a cyclic prefix (CP) and its affinity to different transmission bandwidth arrangements.
  • MPI multipath interference
  • CP cyclic prefix
  • SC-FDMA Single-carrier frequency division multiple access
  • UE user equipment
  • Many key packet radio access techniques are employed including multiple-input multiple-output (MIMO) channel transmission techniques and a highly efficient control signaling structure is achieved in LTE Rel. 8/9.
  • the E-UTRAN consists of an eNodeB, providing the E-UTRA user plane (PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towards the user equipment (UE).
  • the eNodeB hosts the Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC) and Packet Data Control Protocol (PDCP) layers that include the functionality of user-plane header compression and encryption. It also offers Radio Resource Control (RRC) functionality corresponding to the control plane.
  • RRC Radio Resource Control
  • the eNodeBs are interconnected with each other by means of the X2 interface.
  • the eNodeBs are also connected by means of the S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility Management Entity) by means of the S1-MME and to the Serving Gateway (SGW) by means of the S1-U.
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the S1 interface supports a many-to-many relation between MMEs/Serving Gateways and eNodeBs.
  • the SGW routes and forwards user data packets, while also acting as the mobility anchor for the user plane during inter-eNodeB handovers and as the anchor for mobility between LTE and other 3GPP technologies (terminating S4 interface and relaying the traffic between 2G/3G systems and PDN GW).
  • the SGW terminates the downlink data path and triggers paging when downlink data arrives for the user equipment. It manages and stores user equipment contexts, e.g. parameters of the IP bearer service, or network internal routing information. It also performs replication of the user traffic in case of lawful interception.
  • user equipment contexts e.g. parameters of the IP bearer service, or network internal routing information. It also performs replication of the user traffic in case of lawful interception.
  • the MME is the key control-node for the LTE access-network. It is responsible for idle-mode user equipment tracking and paging procedure including retransmissions. It is involved in the bearer activation/deactivation process and is also responsible for choosing the SGW for a user equipment at the initial attach and at the time of intra-LTE handover involving Core Network (CN) node relocation. It is responsible for authenticating the user (by interacting with the HSS).
  • NAS Non-Access Stratum
  • the Non-Access Stratum (NAS) signaling terminates at the MME, and it is also responsible for the generation and allocation of temporary identities to user equipments. It checks the authorization of the user equipment to camp on the service provider's Public Land Mobile Network (PLMN) and enforces user equipment roaming restrictions.
  • PLMN Public Land Mobile Network
  • the MME is the termination point in the network for ciphering/integrity protection for NAS signaling and handles the security key management. Lawful interception of signaling is also supported by the MME.
  • the MME also provides the control plane function for mobility between LTE and 2G/3G access networks with the S3 interface terminating at the MME from the SGSN.
  • the MME also terminates the S6a interface towards the home HSS for roaming user equipments.
  • the downlink component carrier of a 3GPP LTE system is subdivided in the time-frequency domain in so-called subframes.
  • each subframe is divided into two downlink slots as shown in Fig. 2 , wherein the first downlink slot comprises the control channel region (PDCCH region) within the first OFDM symbols.
  • Each subframe consists of a give number of OFDM symbols in the time domain (12 or 14 OFDM symbols in 3GPP LTE (Release 8)), wherein each OFDM symbol spans over the entire bandwidth of the component carrier.
  • the OFDM symbols thus each consist of a number of modulation symbols transmitted on respective subcarriers.
  • N RB DL is the number of resource blocks within the bandwidth.
  • a physical resource block is defined as consecutive OFDM symbols in the time domain (e.g. 7 OFDM symbols) and consecutive subcarriers in the frequency domain as exemplified in Fig. 2 (e.g. 12 subcarriers for a component carrier).
  • a physical resource block thus consists of resource elements, corresponding to one slot in the time domain and 180 kHz in the frequency domain (for further details on the downlink resource grid, see for example 3GPP TS 36.211, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8)", section 6.2, available at http://www.3gpp.org and incorporated herein by reference).
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • R-UTRA Physical Channels and Modulation
  • One subframe consists of two slots, so that there are 14 OFDM symbols in a subframe when a so-called "normal” CP (cyclic prefix) is used, and 12 OFDM symbols in a subframe when a so-called “extended” CP is used.
  • a "resource block pair” or equivalent "RB pair” or "PRB pair”.
  • component carrier refers to a combination of several resource blocks in the frequency domain.
  • cell refers to a combination of downlink and optionally uplink resources.
  • the linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources.
  • the frequency spectrum for IMT-Advanced was decided at the World Radio communication Conference 2007 (WRC-07 ). Although the overall frequency spectrum for IMT-Advanced was decided, the actual available frequency bandwidth is different according to each region or country. Following the decision on the available frequency spectrum outline, however, standardization of a radio interface started in the 3rd Generation Partnership Project (3GPP). At the 3GPP TSG RAN #39 meeting, the Study Item description on "Further Advancements for E-UTRA (LTE-Advanced)" was approved. The study item covers technology components to be considered for the evolution of E-UTRA, e.g. to fulfill the requirements on IMT-Advanced.
  • 3GPP 3rd Generation Partnership Project
  • the bandwidth that the LTE-Advanced system is able to support is 100 MHz, while an LTE system can only support 20MHz.
  • the lack of radio spectrum has become a bottleneck of the development of wireless networks, and as a result it is difficult to find a spectrum band which is wide enough for the LTE-Advanced system. Consequently, it is urgent to find a way to gain a wider radio spectrum band, wherein a possible answer is the carrier aggregation functionality.
  • carrier aggregation two or more component carriers are aggregated in order to support wider transmission bandwidths up to 100MHz.
  • Several cells in the LTE system are aggregated into one wider channel in the LTE-Advanced system which is wide enough for 100 MHz even though these cells in LTE may be in different frequency bands.
  • All component carriers can be configured to be LTE Rel. 8/9 compatible, at least when the bandwidth of a component carrier does not exceed the supported bandwidth of an LTE Rel. 8/9 cell. Not all component carriers aggregated by a user equipment may necessarily be Rel. 8/9 compatible. Existing mechanisms (e.g. barring) may be used to avoid Rel-8/9 user equipments to camp on a component carrier.
  • a user equipment may simultaneously receive or transmit on one or multiple component carriers (corresponding to multiple serving cells) depending on its capabilities.
  • An LTE-A Rel. 10 user equipment with reception and/or transmission capabilities for carrier aggregation can simultaneously receive and/or transmit on multiple serving cells, whereas an LTE Rel. 8/9 user equipment can receive and transmit on a single serving cell only, provided that the structure of the component carrier follows the Rel. 8/9 specifications.
  • Carrier aggregation is supported for both contiguous and non-contiguous component carriers with each component carrier limited to a maximum of 110 Resource Blocks in the frequency domain (using the 3GPP LTE (Release 8/9) numerology).
  • a 3GPP LTE-A (Release 10)-compatible user equipment to aggregate a different number of component carriers originating from the same eNodeB (base station) and of possibly different bandwidths in the uplink and the downlink.
  • the number of downlink component carriers that can be configured depends on the downlink aggregation capability of the UE.
  • the number of uplink component carriers that can be configured depends on the uplink aggregation capability of the UE. It may currently not be possible to configure a mobile terminal with more uplink component carriers than downlink component carriers. In a typical TDD deployment the number of component carriers and the bandwidth of each component carrier in uplink and downlink is the same. Component carriers originating from the same eNodeB need not provide the same coverage.
  • the spacing between centre frequencies of contiguously aggregated component carriers shall be a multiple of 300 kHz. This is in order to be compatible with the 100 kHz frequency raster of 3GPP LTE (Release 8/9) and at the same time to preserve orthogonality of the subcarriers with 15 kHz spacing. Depending on the aggregation scenario, the n ⁇ 300 kHz spacing can be facilitated by insertion of a low number of unused subcarriers between contiguous component carriers.
  • the mobile terminal When carrier aggregation is configured, the mobile terminal only has one RRC connection with the network.
  • one cell At RRC connection establishment/re-establishment, one cell provides the security input (one ECGI, one PCI and oneARFCN) and the non-access stratum mobility information (e.g. TAI) similarly as in LTE Rel. 8/9.
  • the component carrier corresponding to that cell is referred to as the downlink Primary Cell (PCell).
  • PCell downlink Primary Cell
  • DL PCell downlink PCell
  • UL PCell uplink PCell
  • SCells Secondary Cells
  • carriers of the SCell being the Downlink Secondary Component Carrier (DL SCC) and Uplink Secondary Component Carrier (UL SCC).
  • DL SCC Downlink Secondary Component Carrier
  • UL SCC Uplink Secondary Component Carrier
  • RRC The configuration and reconfiguration, as well as addition and removal, of component carriers can be performed by RRC. Activation and deactivation is done via MAC control elements.
  • RRC can also add, remove, or reconfigure SCells for usage in the target cell.
  • dedicated RRC signaling is used for sending the system information of the SCell, the information being necessary for transmission/reception (similarly as in Rel-8/9 for handover).
  • Each SCell is configured with a serving cell index, when the SCell is added to one UE; PCell has always the serving cell index 0.
  • a user equipment When a user equipment is configured with carrier aggregation there is at least one pair of uplink and downlink component carriers that is always active.
  • the downlink component carrier of that pair might be also referred to as 'DL anchor carrier'. Same applies also for the uplink.
  • a user equipment When carrier aggregation is configured, a user equipment may be scheduled on multiple component carriers simultaneously, but at most one random access procedure shall be ongoing at any time.
  • Cross-carrier scheduling allows the PDCCH of a component carrier to schedule resources on another component carrier.
  • a component carrier identification field is introduced in the respective DCI (Downlink Control Information) formats, called CIF.
  • a linking, established by RRC signaling, between uplink and downlink component carriers allows identifying the uplink component carrier for which the grant applies when there is no cross-carrier scheduling.
  • the linkage of downlink component carriers to uplink component carrier does not necessarily need to be one to one. In other words, more than one downlink component carrier can link to the same uplink component carrier. At the same time, a downlink component carrier can only link to one uplink component carrier.
  • L1/L2 control signaling is transmitted on the downlink along with the data.
  • L1/L2 control signaling is multiplexed with the downlink data in a subframe, assuming that the user allocation can change from subframe to subframe.
  • user allocation might also be performed on a TTI (Transmission Time Interval) basis, where the TTI length can be a multiple of the subframes.
  • TTI length may be fixed in a service area for all users, may be different for different users, or may even by dynamic for each user.
  • the L1/2 control signaling needs only be transmitted once per TTI. Without loss of generality, the following assumes that a TTI is equivalent to one subframe.
  • the L1/L2 control signaling is transmitted on the Physical Downlink Control Channel (PDCCH).
  • PDCH Physical Downlink Control Channel
  • a PDCCH carries a message as a Downlink Control Information (DCI), which in most cases includes resource assignments and other control information for a mobile terminal or groups of UEs.
  • DCI Downlink Control Information
  • several PDCCHs can be transmitted in one subframe.
  • the information sent in the L1/L2 control signaling for assigning uplink or downlink radio resources can be categorized to the following items:
  • Downlink control information occurs in several formats that differ in overall size and also in the information contained in their fields as mentioned above.
  • the different DCI formats that are currently defined for LTE are as follows and described in detail in 3GPP TS 36.212, "Multiplexing and channel coding", section 5.3.3.1 (current version v12.4.0 available at http://www.3gpp.org and incorporated herein by reference).
  • the DCI formats and the particular information that is transmitted in the DCI please refer to the mentioned technical standard or to LTE - The UMTS Long Term Evolution - From Theory to Practice, Edited by Stefanie Sesia, Issam Toufik, Matthew Baker, Chapter 9.3 , incorporated herein by reference.
  • the PDCCH carries DCI on an aggregation of one or a plurality of consecutive control channel elements (CCEs).
  • CCEs control channel elements
  • a control channel element corresponds to 9 resource element groups (REG) of which each consists of four or six resource elements.
  • a search space indicates a set of CCE locations where the UE may find its PDCCHs.
  • Each PDCCH carries one DCI and is identified by the RNTI (radio network temporary identity) implicitly encoded in the CRC attachment of the DCI.
  • the UE monitors the CCEs of a configured search space(s) by blind decoding and checking the CRC.
  • Blind decoding means that the terminal has no or limited further information concerning the location of the information directed to it and carried in the search space. It has a limited knowledge about the employed number of aggregated CCEs either. Accordingly, the terminal has to try decoding the PDCCH by a trial-and-error method for several allowed or defined parameters, such as for different numbers of aggregated CCEs and for different resources within the search space. These decoding attempts are called blind decoding. The success of these decoding attempts is checked by checking CRC which is (for user-specific search space) scrambled with a temporary identity (RNTI) of the terminal to which the information is directed. Accordingly, assuming error-free transmissions, the CRC check will be only successful if the information is directed to the checking terminal.
  • CRC temporary identity
  • a search space may be a common search space and a UE-specific search space.
  • a UE is required to monitor both common and UE-specific search spaces, which may be overlapping.
  • the common search space carries the DCls that are common for all UEs such as system information (using the SI-RNTI), paging (P-RNTI), PRACH responses (RA-RNTI), or UL TPC commands (TPC-PUCCH/PUSCH-RNTI).
  • the UE-specific search space can carry DCls for UE-specific allocations using the UE's assigned C-RNTI, semi-persistent scheduling (SPS C-RNTI), or initial allocation (temporary C-RNTI).
  • DCls with exemplary field sizes are provided in the following tables, where especially the sizes depend on configurable option; therefore a size of "0" should be understood such that in certain configuration options the size is zero, however for other options it can be larger.
  • Table 1 DCI Format 0 fields / definitions Field Name Field Size Remarks Carrier indicator 3 Present only if configured Flag for format0/format1A differentiation 1 Value "0" for Format 0 Hopping flag/RA Type 1 MSB 1 Resource block assignment and hopping resource allocation 13 Modulation and coding scheme and redundancy version 5 New data indicator 1 TPC command for scheduled PUSCH 2 Cyclic shift for DM RS and OCC index 3 UL index or Downlink Assignment Index (DAI) 2 Present only for TDD; UL index for configuration 0, DAI for configuration 1-6 CSI request 2 2 bits if CA is configured and transmitted in UE-specific by C-RNTI; 1 bit otherwise SRS request 0 Present only if configured and if transmitted in UE-specific by C-RNTI Resource allocation type 1 Present only if
  • the DCI formats differ from each other by their length (sum of the column "Field Size", which is in units of bits. This is caused by the different purpose of the DCI formats and thus, different fields included therein.
  • LTE Long Term Evolution
  • Wi-Fi radio access technologies
  • LAA Licensed Assisted Access
  • CA Rel-12 carrier aggregation
  • the CA framework configuration as explained before comprises a so-called primary cell (PCell) carrier and one or more secondary cell (SCell) carriers.
  • CA supports in general both self-scheduling of cells (scheduling information and user data are transmitted on the same component carrier) and cross-carrier scheduling between cells (scheduling information in terms of PDCCH/EPDCCH and user data in terms of PDSCH/PUSCH are transmitted on different component carriers). This includes that a common DRX scheme is used for LAA, particularly if it does not result in a need for very short DRX cycles/very long Active Times.
  • common DRX means that the UE operates the same DRX for all aggregated and activated cells, including unlicensed and licensed cells. Consequently, the Active Time is the same for all serving cells, e.g. UE is monitoring PDCCH of all downlink serving cells in the same subframe; the DRX-related timers and parameters are configured per UE.
  • FIG. 3 A very basic scenario is illustrated in Fig. 3 , with a licensed PCell, licensed SCell 1, and various unlicensed SCells 2, 3, and 4 (exemplarily depicted as small cells).
  • the transmission/reception network nodes of unlicensed SCells 2, 3, and 4 could be remote radio heads managed by the eNB or could be nodes that are attached to the network but not managed by the eNB. For simplicity, the connection of these nodes to the eNB or to the network is not explicitly shown in the figure.
  • the basic approach envisioned at 3GPP is that the PCell will be operated on a licensed band while one or more SCells will be operated on unlicensed bands.
  • the benefit of this strategy is that the PCell can be used for reliable transmission of control messages and user data with high quality of service (QoS) demands, such as for example voice and video, while an SCell on unlicensed spectrum might yield, depending on the scenario, to some extent significant QoS reduction due to inevitable coexistence with other RATs.
  • QoS quality of service
  • LAA procedures comprise Dynamic Frequency Selection (DFS), Transmit Power Control (TPC), Listen Before Talk (LBT) and discontinuous transmission with limited maximum transmission duration.
  • DFS Dynamic Frequency Selection
  • TPC Transmit Power Control
  • LBT Listen Before Talk
  • discontinuous transmission with limited maximum transmission duration a single global framework for LAA which basically means that all requirements for different regions and bands at 5GHz have to be taken into account for the system design.
  • the listen-before-talk (LBT) procedure is defined as a mechanism by which an equipment applies a clear channel assessment (CCA) check before using the channel.
  • CCA clear channel assessment
  • the CCA utilizes at least energy detection to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear, respectively.
  • European and Japanese regulations mandate the usage of LBT in the unlicensed bands.
  • carrier sensing via LBT is one way for fair sharing of the unlicensed spectrum and hence it is considered to be a vital feature for fair and friendly operation in the unlicensed spectrum in a single global solution framework.
  • DFS is required for certain regions and bands in order to detect interference from radar systems and to avoid co-channel operation with these systems.
  • the intention is furthermore to achieve a near-uniform loading of the spectrum.
  • the DFS operation and corresponding requirements are associated with a master-slave principle.
  • the master shall detect radar interference, can however rely on another device, associated with the master, to implement radar detection.
  • the operation on unlicensed bands at 5-GHz is in most regions limited to rather low transmit power levels compared to the operation on licensed bands which results in small coverage areas. Even if the licensed and unlicensed carriers were to be transmitted with identical power, usually the unlicensed carrier in the 5GHz band would be expected to support a smaller coverage area than a licensed cell in the 2GHz band due to increased path loss and shadowing effects for the signal. A further requirement for certain regions and bands is the use of TPC in order to reduce the average level of interference caused for other devices operating on the same unlicensed band.
  • CCA Clear Channel Assessment
  • the energy detection for the CCA is performed over the whole channel bandwidth (e.g. 20 MHz in unlicensed bands at 5 GHz), which means that the reception power levels of all subcarriers of an LTE OFDM symbol within that channel contribute to the evaluated energy level at the device that performed the CCA.
  • the Channel Occupancy Time (see ETSI 301 893, under clause 4.8.3.1).
  • the Channel Occupancy Time shall be in the range of 1 ms to 10 ms, where the maximum Channel Occupancy Time could be e.g. 4ms as currently defined for Europe.
  • the UE can perform a new CCA, and so on. This transmission behaviour is schematically illustrated in Fig. 4 , the figure being taken from ETSI EN 301 893 (there Figure 2 : "Example of timing for Frame Based Equipment").
  • a prior art example is US 2015/124724 A1 .
  • Other prior art examples are: 3GPP TSG RAN WG1 Meeting #81, document R1-153135, Source: Ericsson, Title: “On Scheduling in LAA with Downlink and Uplink Transmissions "; 3GPP TSG-RAN WG1 Meeting #81, document R1-153144, Source: InterDigital Communications, Title: "On Scheduling and HARQ operation for LAA "; and 3GPP TSG RAN WG1 Meeting #81, document R1-153013, Source: ZTE, Title: "Control signalling and HARQ related issues for Licensed-assisted access ".
  • a mobile station or mobile node or user terminal or user equipment is a physical entity within a communication network.
  • One node may have several functional entities.
  • a functional entity refers to a software or hardware module that implements and/or offers a predetermined set of functions to other functional entities of a node or the network.
  • Nodes may have one or more interfaces that attach the node to a communication facility or medium over which nodes can communicate.
  • a network entity may have a logical interface attaching the functional entity to a communication facility or medium over which it may communicate with other functional entities or correspondent nodes.
  • radio resources as used in the set of claims and in the application is to be broadly understood as referring to physical radio resources, such as time-frequency resources.
  • unlicensed cell or alternatively “unlicensed carrier” as used in the set of claims and in the application is to be understood broadly as a cell/carrier in an unlicensed frequency band - alternative terminology includes license-exempt band, unlicensed spectrum, contention-based radio access etc.
  • licensed cell or alternatively “licensed carrier” as used in the set of claims and in the application is to be understood broadly as a cell/carrier in a licensed frequency band. Exemplarily, these terms are to be understood in the context of 3GPP as of Release 12/13 and the Licensed-Assisted Access Work Item.
  • DCI is signaling, which in presence of more configured carriers may be transmitted on the carrier to which the signaling relates (referred to in the following as “self-signaling” or “self-indicating”) or may be transmitted in another carrier (referred to in the following as “self-signaling” or “self-indicating”).
  • self-signaling or “self-indicating”
  • self-signaling or “self-indicating”
  • self-signaling or “self-indicating”
  • any signaling (control information) regarding other carriers may be transmitted, i.e. it is not limited to the scheduling control information.
  • a self-scheduling carrier is not limited to transmitting scheduling control information regarding the same carrier. Examples of such non-scheduling control information include communication configuration information such as power control information or TOO UL/DL configuration information.
  • Figure 5 illustrates a problem underlying the present invention.
  • the unlicensed band (band accessible by LBT) is incorporated into a multiple component carrier system as an additional component carrier (or cell).
  • the policies for signaling, including scheduling may be designed in various different manners.
  • the terminal has to monitor (i.e. blindly decode) a predetermined search space on the LBT carrier to receive control information relating to the LBT carrier.
  • This control information may be, for instance, scheduling information.
  • the control information may be power control information or other kinds of configurations of the LBT transmission.
  • the control information carried on PDCCH includes an uplink grant.
  • This downlink control information may fail to be received. This may be caused by the fact that the base station performing CCAfails to transmit the PDCCH since the CCA procedure reveals that the resources are used by other transmissions such as transmissions over WLAN. However, despite being transmitted by the base station it may be also caused by missing the PDCCH for instance due to bad channel conditions. If the DCI was received correctly, the corresponding PUSCH would be transmitted a defined period, e.g. four subframes, later, based on the reception of the uplink grant. However, in order to transmit the PUSCH, the UE has to perform CCA, i.e. check whether there is transmission pending on the relevant resources. In the example of Figure 5 , there is another transmission (such as WLAN) pending and thus, PUSCH cannot be transmitted in the granted resources.
  • DCI downlink control information
  • Figure 5 illustrates cross-indicating / cross-scheduling on the licensed carrier, i.e. carrier on which no LBT has to be performed before transmitting on the granted resources.
  • Such carrier may be a component carrier of the LTE, the resources of which are not shared with any other system.
  • uplink grants may be received for transmission in other carriers, possibly including the LBT carrier or a plurality of the LBT carriers. Since there is no LBT necessary before the base station transmits the PDCCH, the probability of losing the PDCCH by the UE is lower.
  • the PDCCH including an uplink grant for an LBT carrier. After reception of the grant, the UE has to perform carrier sensing of the LBT carrier before transmitting on the granted resources (same as when the grant is received over the LBT carrier in the self-scheduling example above.
  • the opportunistic transmission as performed in case of self-scheduling may be advantageously avoided by employing cross-scheduling on a non-LBT carrier.
  • cross-scheduling on a non-LBT carrier.
  • self-indicating vs. cross indicating of other control information which may be used for uplink transmissions such as power control DCI.
  • control signaling and the transmission of the data traffic is performed on one and the same carrier, in the same direction, and preferably in the same unit such as in the same subframe.
  • both DCI formats may be detected on the same cell and on a different cell, but after successful blind decoding, UL grants from the same cell and DL grants from a different cell would be seen as invalid and therefore be discarded which results in wasted effort.
  • DCI format 0 and DCI format 1A have the same size, when attempting decoding for that size, both formats are received.
  • Figure 6 exemplifies relations between self-indicating and cross-indicating DCls for the case of a plurality of component carriers, and the search space relations assuming that a single cell is scheduling/indicating three cells (or, in general a single cell is used to carry control information for three cells).
  • the cell carrying all the DCls is in this example identical to the PCell, and carries three - potentially overlapping - UE-specific search spaces (USS).
  • This cell carrying the DCI may also be called "Scheduling Cell", even though not all DCls transmitted in such cell are necessarily for scheduling data transmission.
  • the DCI may also carry TPC commands without including grants, elMTA reconfiguration or other signaling information used to configure data transmission.
  • the term "self-scheduling" and “cross-scheduling” are not necessarily mutually exclusive, nor complementary.
  • the PCell is in this case at the same time self-scheduling and cross-scheduling cell, while the other two cells/carriers are neither self-scheduling nor cross-scheduling.
  • a "carrier indicator field” may be included in the respective DCI formats (see 36.212 and the background section above) and indicates for which carrier the control information carried by the DCI is applicable.
  • the carrier indicator (CI) determines whether a DCI carried on the carrier A is applicable to carrier A, B, or C.
  • the value indicated in the CIF is identical to the corresponding n_CI value - e.g. in the example of Figure 6 , the CIF can take the values ⁇ 0, 1, 2 ⁇ .
  • a search space is associated, i.e. for each CIF value a subset of CCEs is defined which are monitored to receive DCI.
  • n_CI n_CI and the CIF values.
  • CIF serves to identify an intended carrier
  • the embodiments can be used without issues.
  • the present invention is not limited to use of a particular indication such as n_CI value for the purpose of distinguishing between carriers. There may be any indicator which enables distinguishing between the carriers such as CIF.
  • n_CI n_CI ⁇ 0, 1, 2 ⁇
  • Figure 6 relates to component carrier aggregation as defined in Rel-10 and later of LTE which is a licensed band system. Under assumption that unlicensed band is to be integrated into the LTE as one of the component carriers, similar approach is also to be applied to an LBT carrier.
  • carrier C may be an LBT carrier.
  • LBT carrier Such integration of LBT carrier into a non-LBT system thus also leads to a necessity of providing another search space associated with the Cl of the LBT carrier.
  • search space as described above may correspond to PDCCH and/or to EPDCCH.
  • EPDCCH is an enhancement of PDCCH region as described above.
  • all embodiments described herein are also applicable for any of PDCCH and EPDCCH.
  • the present invention is generally applicable not only to PDCCH and EPDCCH but for any channel carrying DCI.
  • the backhaul link between a base station and a relay may also use this approach.
  • Figure 7 shows behavior according to an embodiment for one licensed carrier (e.g. PCell) that supports self-indicating, as well as signaling for two other carriers that require an LBT procedure before access.
  • carrier A with carrier identification having value 0 is a licensed band carrier on which LBT is not necessary.
  • Carriers B and C with respective carrier identifier values of 1 and 2 are LBT carriers.
  • DL transmissions on carrier B and C can only be scheduled by a self-indicating DCI (shown by dash-dotted arrows), i.e. where the corresponding DCI is transmitted/detected within a search space located on resources of the corresponding LBT carrier B and C, respectively.
  • Figure 7 shows that on carrier A only one single (UE-specific) search space exists.
  • any search space on a cross-indicating carrier is associated with a carrier indication of a non-LBT carrier.
  • LBT carriers are not allowed to spawn any additional search space on the cross-indicating carrier which carries signalling for these LBT carriers.
  • the wireless communication system may be a cellular system such as LTE-A, operating in licensed band. If operating in licensed band, no LBT is necessary since the licensed resources are only used by the system they are licensed for. Thus, as soon as a resource is scheduled, the transmission can take place on the scheduled resource without further checking their usage by someone else.
  • LTE-A is only an example, but the present disclosure is equally applicable to any other licensed band system which also makes use of unlicensed bands, on which LBT is to be performed before the transmission.
  • Carrier aggregation has been described in the background section above. Accordingly, a plurality of component carriers corresponds to a plurality of cells, providing each a separate time-frequency resource grid.
  • component carrier is not to be confused with the term sub-carrier: each component carrier having an own resource grid is also formed by the set of sub-carriers.
  • component carrier in the following thus aggregated carriers of the licensed (non-LBT) will be denoted.
  • additional carrier or LBT carrier, carriers will be denoted which require LBT such as unlicensed band carriers.
  • a method of the present disclosure is illustrated in Fig. 8 and includes the following steps performed at the DCI receiver (UE): monitoring 850 a search space on a cross-scheduling component carrier for detecting 870 downlink control information having a carrier identification field indicating the cross-scheduling component carrier as well as for detecting 870 downlink control information with the carrier identification field indicating the additional carrier, wherein the search space is specified by a subset of resources, associated with carrier identification of the cross-scheduling component carrier but is not associated with carrier identification of the additional carrier, and receiving or transmitting 880 data on the carriers in accordance with the received downlink control information.
  • the monitoring of the search space is performed regularly as configured, i.e. on the resources assigned to the search space associated with the cross-indicating carrier (its CIF value).
  • the final processing step 880 generally includes applying the configuration received within the DCI in step 870. This applying may be, for instance, transmission of data if the DCI included UL grant, reception of data if the DCI included a DL grant or any other configuration of the carrier for which the DCI was issued, e.g. power control configuration.
  • the search space may be configured at first.
  • This configuration may be performed semi-statically by higher layers. For instance, this configuration may be performed by the RRC protocol when configuring or reconfiguring the corresponding bearer using PDSCH or PUSCH. Accordingly, the UE receives 850 the configuration and configures the search space accordingly.
  • a method to be executed at the DCI transmitter (base station, BS) side including the steps of: transmitting 820 in a search space on a cross-scheduling component carrier downlink control information having a carrier identification field indicating the cross-scheduling component carrier as well as downlink control information with the carrier identification field indicating the additional carrier, wherein the search space is specified by a subset of resources, associated with carrier identification of the cross-scheduling component carrier but is not associated with carrier identification of the additional carrier, and receiving or transmitting 830 data on the carriers in accordance with the transmitted downlink control information.
  • the search space i.e. the resources assigned to the search space on the component carrier, may be configured 810 by the base station before the transmission of the DCls and transmission/reception of data accordingly as mentioned above.
  • the base station transmits a DCI for a certain UE in the configured search space if there are data to be transmitted or received by the UE or if there is signaling for the UE concerning configuration for data transmission or reception.
  • a carrier identifiable within DCI by its carrier indication and requiring an LBT procedure before access to the granted resources does not spawn a (UE-specific) search space on a cross-indicating scheduling cell. Consequently, only one (UE-specific) search space is shown for carrier A in Figure 7 . This search space is used for the entire self-indicating of carrier A and cross-indicating of carriers B and C.
  • a DCI transmitted/detected therein needs to include the CIF, in order to determine for which of the carriers A, B and C corresponding to n_CI values of 0, 1, 2, respectively the control information is destined.
  • Carriers B and C each support only self-indication for DL transmissions. Thus, the DCls related to DL for carriers B and C cannot be cross-indicated on another carrier. Consequently, according to an embodiment, no CIF is included in the corresponding DCls related to DL of carriers B and C.
  • the downlink control information for the additional carrier transmitted in the search space(s) of the cross-scheduling cell, only includes grants for uplink but not for downlink.
  • the UE thus also performs monitoring a search space on the additional carrier for detecting downlink control information and relating to downlink data reception, and receives data in accordance with the downlink control information detected.
  • the downlink control information received on the additional carrier has no carrier identification field.
  • a configuration based on downlink control information detected in the search space of the cross-scheduling cell for the additional carrier is applied for the transmission only in case of grants for uplink but is discarded in case of grants for downlink. In other words, if a DCI with downlink configuration for the LBT carrier is received cross-indicated in the search space of the cross-scheduling carrier, then it is ignored and the control information included therein is not applied for the reception of data.
  • the UE may then perform the following (further) steps illustrated in Figure 9 :
  • DCI Format 0 and 1A include specification of the format. Based on the format, it is additionally clear whether it relates to UL or DL.
  • the format of the DCI is beneficially kept in the corresponding field for the reason of compliancy with the existing formats. In such case, this additional information may help to check the correct reception of the DCI (no DCI with UL grants should be received. If received, it should not be used for configuring the transmission).
  • an uplink component carrier is always linked to a corresponding downlink carrier. Accordingly, an uplink and the corresponding downlink carrier have the same CIF value.
  • the present invention is not limited to LTE or to LTE applying concept to LBT carriers same as to the component carriers. Thus, the present invention is also applicable if CIF is also direction specific. Thus, the decision on whether an UL or DL carrier in indicated may be performed based on the CIF value.
  • the UE configures the DL on the LBT carrier in accordance with the DCI received in step 930.
  • the UE judges whether the CIF value corresponds to the value of the non-LBT cross-indicating carrier (yes in step 940). If affirmative, the UE configures the non-LBT cross-indicating carrier accordingly in step 950, for UL or DL depending on the DCI format. If the CIF value corresponds to the value of an LBT carrier, the LBT carrier in UL is configured accordingly in step 960. The UE knows that only UL and no DL configuration may be received in this DCI and may use this information for checking the correct reception.
  • the length of the DCI formats to be detected is known a priori by the UE as a function of the configured transmission modes for UL and DL, and the applicable RNTI for the DCI format. Consequently the successfully detected length of a DCI is an indication for the type of the DCI and its content.
  • Figure 10 shows another example configuration based on the present disclosure.
  • Figure 10 illustrates UE (and also BS) behavior for two licensed carriers (e.g. PCell and one SCell), where the PCell supports indicating itself, as well as the other licensed carrier, as well as another carrier that requires an LBT procedure before access.
  • the PCell supports indicating itself, as well as the other licensed carrier, as well as another carrier that requires an LBT procedure before access.
  • DL-related configuration of carrier C can only be indicated by self-indicating DCI (shown by a dash-dotted arrow),
  • carrier A e.g. a carrier C, or further carriers D and E not shown in the figure
  • the DCI transmitted/detected therein need to include the CIF, in order to determine particularly whether an UL transmission is indicated for carrier A, B, or C corresponding to n_CI values of 0, 1, 2, respectively.
  • CIF is useful to specify for which carrier the DCI configuration is to be applied.
  • carrier C supports only self-indications for DL transmissions, there is no specific need to include a CIF in the corresponding DCI.
  • a CIF could be present in case it is desired, as a matter of configuration. Not including a CIF is beneficial since it allows a more compact DCI size, which has benefits in terms of a small control overhead, larger control information coverage, or a good error resilience of the control information against errors introduced by e.g. the (radio) channel, as already mentioned above.
  • a UE would then perform the following procedure.
  • control information signaling can be further improved in accordance with another embodiment described in the following and combinable with the above described embodiments and exampled.
  • the aim is to maintain the total blind decoding effort limited, preferably not exceeding the example of Fig. 6 .
  • DCls transmitted on the cross-indicating cell for LBT carriers are aligned in size to one of the existing DCI sizes in the cross-indicating cell.
  • the monitoring 850 is performed for the downlink control information for the cross-scheduling component carrier and the downlink control information for the additional carrier, wherein both DCls have the same predetermined size. This may be achieved, for instance by using the DCIs already defined to have the same size such as DCI Format 0 and DCI Format 1A.
  • the size of the downlink control information carrying an uplink grant for the additional carrier is advantageously padded to the size of a downlink control information carrying a downlink grant for the cross-scheduling carrier and/or other component carriers.
  • the downlink control information, DCI, carrying the uplink grant for the additional carrier corresponds to DCI Format 0 of 3GPP LTE-A and its size is padded to match the size of a DCI larger than DCI Format 0 and carrying downlink grants for the cross-scheduling carrier and/or other component carriers.
  • the preferred method is that the smaller DCI is padded to the larger DCI format by adding bits. If those padding bits have a predefined or predetermined value, they can further be utilized to improve correct detection of the DCI.
  • Fig. 10 merely shows component carrier A being a cross-indicating carrier and component carrier B for which signaling is only received on carrier A, this arrangement is not limiting for the present invention.
  • carrier B may also apply self-scheduling, for instance only for one direction such as downlink or for both uplink and downlink.
  • carrier B is completely self-scheduling, in terms of Fig.10
  • Carrier A would only schedule itself and carrier C, while carrier B would only schedule itself.
  • carrier B may also be cross-scheduling carrier in addition to carrier A to indicate carrier C. However, this may be a less interesting configuration due to a higher possibility of errors by false DCI detection.
  • Figure 11 illustrates DCI sizes applicable for formats used on the LBT and non-LBT carriers.
  • Figure 12 shows, where the respective DCI sizes are applied. In particular, the following format sizes are shown:
  • the DCI size for UL cross-indication (U1) is identical to the DCI size for DL and UL self-indication (A1), which is illustrated by shading the corresponding DCIs in Figure 11 . Then a CIF is necessary to distinguish between scheduling cell A (DL/UL) and cell B (UL).
  • the reason for possible need for including more fields or larger fields for cross-scheduling compared to self-scheduling is that additional control data may be necessary for instance for supporting asynchronous HARQ or further or enhanced features.
  • the downlink control information, DCI, carrying the uplink grant for the additional carrier on the component carrier has the same size as the DCI carrying uplink grant for the component carrier on which the DCI is received, and the size of a resource block allocation field in the DCI carrying uplink grant for the component carrier on which the DCI is received is larger than the size of the resource block allocation field in the DCI carrying the uplink grant for the additional carrier on the component carrier.
  • RBA field One candidate field to remove bits is thus the RBA field. Removing bits from the RBA field would limit the frequency resource scheduling flexibility. However, this seems acceptable considering that mainly large resource assignments are desirable for carriers that require an LBT procedure before access.
  • the detected CIF is used to distinguish a cross-indicating DCI format 1A from a self-indicating DCI Format 2D.
  • a cross-indicating DCI format 1A would be distinguished from a self-indicating DCI Format 2D by an additional information such as the CIF value.
  • TM-specific here denotes that formats, which are only used (and allowed, i.e. also recognized) for specific transmission mode configurations.
  • transmission modes are defined by a list of potential transmission schemes.
  • TM-specific formats are formats which are applicable to not all transmission modes such as the above mentioned format 2D (not applicable to DL transmission modes 1-9) or other formats such as format 1 (not applicable to DL transmission modes 3-6, 8-10).
  • DCI Format 1A is not a TM-specific DCI format since it is applicable to all defined DL transmission modes (1-10).
  • DCI Format 4 is TM-specific because it is not applicable to UL transmission mode 1, while DCI Format 0 is not TM-specific because it is applicable to all defined UL transmission modes 1-2.
  • TM-specific DCI Format has a larger size than a non-TM-specific DCI Format because more detailed configurations are necessary to be conveyed (such as precoding information, multiple codeword information).
  • the size A1 corresponds to DCI Format 0/1A.
  • Size A2 corresponds to TM-specific DL DCI Format, such as 2D.
  • Size A3 also corresponds to TM-specific UL DCI Format, e.g. 4.
  • U1 corresponds to DCI Format 0/1A
  • size U2 corresponds to TM-specific UL DCI Format, e.g. 4.
  • size D1 is a size of the DCI Format 0/1A
  • the size of D2 is size of a TM-specific DL DCI Format, e.g. 2D.
  • B1/B2/B3 corresponds in this context to A1/A2/A3.
  • DL cross-indicating may be supported by means of a cross-indicating TM-specific DCI format 2D that is aligned in size to the self-indicating DCI format 2D. Again the CIF is used to distinguish whether the DCI format 2D is self-indicating or cross-indicating.
  • the first example above relates to size alignment in which the size of DCls transmitted on the component carrier for configuring uplink of the component carrier A1 is the same as the size of DCls transmitted on the component carrier for configuring uplink of the additional carrier U1. Moreover, the same size alignment may also concern the size of DCls transmitted on the component carrier for configuring downlink of the additional carrier D1.
  • this size alignment may also be applied between DCls which are transmission mode specific between the cross-indicating downlink DCI D2 and the self-indicating downlink DCI of the cross-scheduling component carrier A2 and/or the additional component carrier B2 .
  • the size of DCls transmitted on the component carrier for configuring downlink of the component carrier A2 is the same as the size of DCls transmitted on the component carrier for configuring uplink of the additional carrier U1. This can be achieved by adding padding bits to the size of U1 to achieve size A2 as already mentioned above.
  • the DCI size for UL cross- indication is identical to the (preferably TM-specific) DCI size for DL self-indication.
  • U1, D1, and D2 differ in size, it is clear that size U1 cannot correspond to a DL cross-carrier indicating DCI.
  • the CIF is sufficient to know that size U1 with the corresponding CIF entry constitutes an uplink cross-carrier DCI.
  • the DCI corresponding to U1, A2, and D1 includes an uplink/downlink indication specifying whether the DCI relates to UL or DL direction.
  • This uplink/downlink indication may be carried in an uplink/downlink indication, preferably having size of 1 bit.
  • the distinction between the uplink and downlink may be performed by applying specific RNTI for uplink and a different specific RNTI for uplink to scramble the PDCCH (CRC).
  • the size of the downlink control information format carrying an uplink grant for the additional carrier U1 is padded to the size of a downlink control information format carrying a uplink grant for the cross-scheduling component carrier and/or other carriers A3, B3 which is larger than the downlink control information format carrying an uplink grant for the additional carrier U1.
  • This example assumes that there are two kinds of downlink control information formats carrying an uplink grant, namely a shorter format used for self-indicating and a longer format used for cross-indicating (such as DCI Format 0 and DCI Format 4).
  • the DCI size for UL cross-indication is identical to the (preferably "TM-specific") DCI size for UL self-indication, such as DCI Format 4.
  • TM-specific DCI size for UL self-indication
  • the CIF is sufficient to know that size U1 with the corresponding CIF entry constitutes an uplink cross-carrier assignment.
  • Figure 17 summarizes formats available in a cell A which is a cross-indicating cell (cross-scheduling component carrier) and in cell B which is a self-scheduling cell (additional LBT carrier).
  • the above cases can be further adapted to match a second DCI format of size U2 (e.g. DCI Format 4) for UL cross-indication to one of the self-scheduling sizes A1/A2/A3 by replacing U1 by U2.
  • a second DCI format of size U2 e.g. DCI Format 4
  • DCI Formats 0, 1A, 2D and 4 which are merely exemplary.
  • the disclosure related to DCI Formats 2D and 4, which are TM-specific DCI formats, can be applied to other TM-specific DCI Formats, such as DCI Formats 1, 1B, 1C, 1D, 2, 2A, 2B, 2C.
  • the disclosure related to DCI Formats 0 and 1A, which are not TM-specific DCI formats can be applied to other non-TM-specific DCI formats.
  • DCI Format 3 and 3A which does not include any scheduling information (grant) but merely a configuration concerning the respective carrier may be, for instance DCI Format 3 and 3A in LTE-A system.
  • DCI Formats 3 and 3A are preferably follow the disclosure applicable to non-TM-specific DCI formats.
  • Figure 18 shows exemplary apparatuses according to the present disclosure, which may be embodied in a terminal (UE) 1800A and in a base station (eNB) 1800B.
  • UE terminal
  • eNB base station
  • an apparatus 1800A for transmitting or receiving data in a wireless communication system, the wireless communication system supporting aggregation of a plurality of component carriers and an additional carrier accessible by a listen before talk approach.
  • the wireless communication system may be an LTE-A system or any other radio access system which incorporates into its dedicated band a band shared with another system in which carrier sensing is necessary even before a scheduled transmission.
  • the apparatus 1800A may be included in a UE, such as mobile phone, LTE interface card, IC for use in LTE interface of any device such as mobile phone, smart phone, computer, tablet or any other device.
  • such apparatus 1800A comprises a search space monitoring unit 1810 for monitoring a search space on a cross-scheduling component carrier for detecting downlink control information having a carrier identification field indicating the cross-scheduling component carrier as well as for detecting downlink control information with the carrier identification field indicating the additional carrier, wherein the search space is specified by a subset of resources, associated with carrier identification of the cross-scheduling component carrier but is not associated with carrier identification of the additional carrier.
  • the search space monitoring unit 1810 performs blind decoding on the preconfigured search space with the above described features and provides the decoded control information to further units which use it to perform configuration of or reception and/or transmission of data.
  • the apparatus 1800A includes at least one of further units which receive the decoded information and handle accordingly, namely a transmission unit 1820, reception unit 1830, and configuration unit 1840.
  • the transmission unit 1820 generates the data to be transmitted in accordance with the received grant. This includes taking the granted amount of data, modulation and coding scheme, and mapping the coded data as configured by the DCI onto the physical uplink resources, i.e. transmitting the data.
  • the granted carrier is an LBT carrier, performing the LBT procedure beforehand as described above.
  • the reception unit 1820 may also receive feedback from the UE and notify the search space monitoring unit 1810 accordingly. In particular, the configuration of the search space may be received.
  • the reception unit 1830 received the data in the granted resources and decodes them according to the received configuration (including coding and modulation scheme and further features configure).
  • the reception includes demapping the data from the granted resources according to the configuration specified in the DCI.
  • the configuration unit 1840 configures the UE according to the received information from the DCI for the purpose of future transmissions or receptions.
  • such configuration may be a power control information upon reception of which the configuration unit 1840 configures the transmission power on the respective carrier indicated by the DCI (implicitly or explicitly).
  • other configurations may be performed without at the same time signaling grant, i.e. scheduling data, such as configurations for TDD mode.
  • an apparatus 1800B for transmitting or receiving data in subframes of a wireless communication system, the wireless communication system supporting aggregation of a plurality of component carriers and an additional carrier accessible by a listen before talk approach.
  • Such apparatus 1800B may be implemented in a base station and/or a radio controller. In terms of LTE, it may be an eNB. In general, such apparatus is advantageously implemented in a device which performs scheduling and/or configuration of the devices 1800A exemplified above.
  • the apparatus 1800A includes a scheduling unit 1850 being a part of a transceiver unit for transmitting in a search space on a cross-scheduling component carrier downlink control information having a carrier identification field indicating the cross-scheduling component carrier as well as downlink control information with the carrier identification field indicating the additional carrier, wherein the search space is specified by a subset of resources, associated with carrier identification of the cross-scheduling component carrier but is not associated with carrier identification of the additional carrier, and for receiving or transmitting data on the carriers in accordance with the transmitted downlink control information.
  • the scheduling unit 1850 schedules the transmission of the DCI, i.e. selects resources in the search space, on which the DCI is transmitted. It may further schedule the UEs and thus generate the DCI with the corresponding configuration for the respective UEs.
  • the transmission unit 1860 then transmits the scheduled DCI with the information for scheduling and/or configuring the UE for transmission or reception of data.
  • the reception unit 1870 on the other hand may serve for receiving the scheduled data and/or feedback based on which the scheduling is performed (such as acknowledgements or indications of channel quality).
  • the present disclosure provides a search space configuration and DCI configuration particularly advantageous for systems with shared bandwidth co-existing with dedicated system bandwidth.
  • the search space monitoring unit may be configured to perform monitoring for the downlink control information for the cross-scheduling component carrier and the downlink control information for the additional carrier having the same predetermined sizes.
  • the size of DCls transmitted on the component carrier for configuring uplink of the component carrier (A1, A3) may be the same as the size of DCls transmitted on the component carrier for configuring uplink of the additional carrier (U1, U2). This provides additional benefits of reducing the number of blind decoding attempts.
  • the size of DCls transmitted on the component carrier for configuring uplink of the additional carrier (U1, U2) may be the same as the size of DCls transmitted on the component carrier for configuring downlink of the additional carrier (D1, D2).
  • the size of the downlink control information carrying an uplink grant for the additional carrier (U1) may be padded to the size of a downlink control information carrying a downlink grant for the cross-scheduling component carrier and/or other carriers (A2, B2).
  • the size of the downlink control information format carrying an uplink grant for the additional carrier (U1) may be padded to the size of a downlink control information format carrying a uplink grant for the cross-scheduling component carrier and/or other carriers (A3, B3) which is larger than the downlink control information format carrying an uplink grant for the additional carrier (U1).
  • the downlink control information, DCI, carrying the uplink grant for the additional carrier (U1) may correspond to DCI Format 0 of 3GPP LTE-A and its size is padded to match the size of DCI Format 2D which is larger than DCI Format 0 and carrying downlink grants for the cross-scheduling carrier and/or other carriers (A2, B2).
  • the downlink control information, DCI, carrying the uplink grant for the additional carrier on the cross-scheduling component carrier (U1) may have the same size as the DCI carrying uplink grant for the cross-scheduling component carrier on which the DCI is received (A1), and the size of a resource block allocation field in the DCI carrying uplink grant for the component carrier on which the DCI is received (A1) is larger than the size of the resource block allocation field in the DCI carrying the uplink grant for the additional carrier on the component carrier (U1).
  • the downlink control information transmitted in the search space of the cross-scheduling cell for the additional carrier only includes grants for uplink but not for downlink.
  • monitoring a search space may be performed on the additional carrier for detecting downlink control information having no carrier identification field and relating to downlink data reception on the additional carrier, and data are then received on the additional carrier in accordance with the downlink control information detected.
  • the downlink control information includes at least one of: a carrier indication field for identifying the carrier for which the grant is designated when the DCI is carried on the cross-scheduling component carrier and relates to uplink, an uplink/downlink indicator specifying whether the DCI relates to uplink or downlink if DCls relating to uplink and downlink have the same sizes.
  • a user terminal mobile terminal
  • an eNodeB base station
  • the user terminal and base station is adapted to perform the methods described herein, including corresponding entities to participate appropriately in the methods, such as receiver, transmitter, processors.
  • a computing device or processor may for example be general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, etc.
  • DSP digital signal processors
  • ASIC application specific integrated circuits
  • FPGA field programmable gate arrays
  • the various embodiments may also be performed or embodied by a combination of these devices.
  • each functional block used in the description of each embodiment described above can be realized by an LSI as an integrated circuit. They may be individually formed as chips, or one chip may be formed so as to include a part or all of the functional blocks. They may include a data input and output coupled thereto.
  • the LSI here may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI depending on a difference in the degree of integration.
  • the technique of implementing an integrated circuit is not limited to the LSI and may be realized by using a dedicated circuit or a general-purpose processor.
  • a FPGA Field Programmable Gate Array
  • a reconfigurable processor in which the connections and the settings of circuits cells disposed inside the LSI can be reconfigured may be used.
  • the various embodiments may also be implemented by means of software modules, which are executed by a processor or directly in hardware. Also a combination of software modules and a hardware implementation may be possible.
  • the software modules may be stored on any kind of computer readable storage media, for example RAM, EPROM, EEPROM, flash memory, registers, hard disks, CD-ROM, DVD, etc. It should be further noted that the individual features of the different embodiments may individually or in arbitrary combination be subject matter to another embodiment.
  • the invention relates to transmission and reception of data in a wireless communication system, the wireless communication system supporting aggregation of a plurality of component carriers and an additional carrier accessible by a listen before talk approach.
  • monitoring is performed of a search space on a cross-scheduling component carrier for detecting downlink control information having a carrier identification field indicating the cross-scheduling component carrier as well as for detecting downlink control information with the carrier identification field indicating the additional carrier, wherein the search space is specified by a subset of resources, associated with carrier identification of the cross-scheduling component carrier but is not associated with carrier identification of the additional carrier.
  • data are transmitted or received on the carriers in accordance with the received downlink control information.

Claims (14)

  1. Endgerätvorrichtung (1800A) für die Verwendung in einem drahtlosen Kommunikationssystem, das befähigt ist zum Aggregieren einer Vielzahl von Trägern einschließlich eines Komponententrägers und eines zusätzlichen Trägers, auf den durch einen Listen-before-Talk-Ansatz zugegriffen werden kann, wobei die Endgerätvorrichtung umfasst:
    einen Schaltungsaufbau, wobei der Schaltungsaufbau Suchraumüberwachungs-, Sende-, Empfangs- und Konfigurationseinheiten (1810, 1820, 1830, 1840) umfasst, die im Betrieb Folgendes ausführen: Überwachen eines Suchraums auf dem Komponententräger, und Erfassen von Downlink-Steuerinformationen (Downlink Control Information bzw. DCI) in dem überwachten Suchraum, wobei der überwachte Suchraum einen Teilsatz von Ressourcen, die mit dem Komponententräger assoziiert sind und nicht mit dem zusätzlichen Träger assoziiert sind, enthält und wobei die erfassten DCI ein Trägeridentifikationsfeld (Carrier Identification Field bzw. CIF), das den zusätzlichen Träger angibt, enthalten; Setzen einer Sendungskonfiguration für die Endgerätvorrichtung gemäß Konfigurationsinformationen in den erfassten DCI; Durchführen einer Uplink-Sendung auf dem zusätzlichen Träger, wenn die erfassten DCI Informationen in Bezug auf die Uplink-Sendung für den durch das CIF angegebenen zusätzlichen Träger enthalten; und Verwerfen von Informationen in Bezug auf eine Downlink-Sendung, wenn die erfassten DCI Informationen in Bezug auf die Downlink-Sendung für den durch das CIF angegebenen zusätzlichen Träger enthalten.
  2. Endgerätvorrichtung (1800A) nach Anspruch 1, wobei die Informationen in Bezug auf die Uplink-Sendung eine Uplink-Gewährung und/oder Uplink-Konfigurationsinformationen enthalten, wenn das CIF in den erfassten DCI den Komponententräger angibt.
  3. Endgerätvorrichtung (1800A) nach Anspruch 1, wobei die Informationen in Bezug auf die Downlink-Sendung eine Downlink-Gewährung und/oder Downlink-Konfigurationsinformationen enthalten, wenn das CIF in den erfassten DCI den Komponententräger angibt.
  4. Endgerätvorrichtung (1800A) nach Anspruch 1, die einen Empfänger (1830) umfasst, der im Betrieb die Konfigurationsinformationen in Bezug auf den Suchraum auf dem Komponententräger empfängt.
  5. Endgerätvorrichtung (1800A) nach Anspruch 1, wobei die Größe der DCI, die die Uplink-Sendung für den Komponententräger konfigurieren, gleich der Größe der DCI, die die Uplink-Sendung für den zusätzlichen Träger konfigurieren, ist.
  6. Endgerätvorrichtung nach Anspruch 1, wobei der Schaltungsaufbau (1810, 1840) im Betrieb einen Suchraum auf dem zusätzlichen Träger überwacht und DCI in dem überwachten Suchraum auf dem zusätzlichen Träger erfasst,
    wobei die auf dem zusätzlichen Träger erfassten DCI kein Trägeridentifikationsfeld enthalten.
  7. Endgerätvorrichtung (1800A) nach Anspruch 6, wobei der Empfänger im Betrieb eine Downlink-Sendung auf dem zusätzlichen Träger gemäß den auf dem zusätzlichen Träger erfassten DCI empfängt.
  8. Kommunikationsverfahren, das durch eine Endgerätvorrichtung in einem drahtlosen Kommunikationssystem implementiert wird, das befähigt ist zum Aggregieren einer Vielzahl von Trägern einschließlich eines Komponententrägers und eines zusätzlichen Trägers, auf den durch einen Listen-before-Talk-Ansatz zugegriffen werden kann, wobei das Kommunikationsverfahren umfasst:
    Überwachen (860) eines Suchraums auf dem Komponententräger, und Erfassen (910) von Downlink-Steuerinformationen (DCI) in dem überwachten Suchraum, wobei der überwachte Suchraum einen Teilsatz von Ressourcen, die mit dem Komponententräger assoziiert sind und nicht mit dem zusätzlichen Träger assoziiert sind, enthält und wobei die erfassten DCI ein Trägeridentifikationsfeld (Carrier Identification Field bzw. CIF), das den zusätzlichen Träger angibt, enthalten,
    Setzen einer Sendungskonfiguration (950) für die Endgerätvorrichtung gemäß Konfigurationsinformationen in den erfassten DCI,
    Durchführen einer Uplink-Sendung auf dem zusätzlichen Träger, wenn die erfassten DCI Informationen in Bezug auf die Uplink-Sendung für den durch das CIF angegebenen zusätzlichen Träger enthalten, und
    Verwerfen von Informationen in Bezug auf eine Downlink-Sendung, wenn die erfassten DCI Informationen in Bezug auf die Downlink-Sendung für den durch das CIF angegebenen zusätzlichen Träger enthalten.
  9. Kommunikationsverfahren nach Anspruch 8, wobei die Informationen in Bezug auf die Uplink-Sendung eine Uplink-Gewährung und/oder Uplink-Konfigurationsinformationen enthalten, wenn das CIF in den erfassten DCI den Komponententräger angibt.
  10. Kommunikationsverfahren nach Anspruch 8, wobei die Informationen in Bezug auf die Downlink-Sendung eine Downlink-Gewährung und/oder Downlink-Konfigurationsinformationen enthalten, wenn das CIF in den erfassten DCIU den Komponententräger angibt.
  11. Kommunikationsverfahren nach Anspruch 8, wobei die Konfigurationsinformationen in den erfassten DCI auf den Suchraum auf dem Komponententräger bezogen sind.
  12. Kommunikationsverfahren nach Anspruch 8, wobei die Größe der DCI, die die Uplink-Sendung für den Komponententräger konfigurieren, gleich der Größe der DCI, die die Uplink-Sendung für den zusätzlichen Träger konfigurieren, ist.
  13. Kommunikationsverfahren nach Anspruch 8, das umfasst:
    Überwachen eines Suchraums auf einen zusätzlichen Träger, und Erfassen von DCI in dem überwachten Suchraum auf dem zusätzlichen Träger,
    wobei die auf dem zusätzlichen Träger erfassten DCI kein Trägeridentifikationsfeld enthalten.
  14. Kommunikationsverfahren nach Anspruch 13, das umfasst:
    Empfangen einer Downlink-Sendung auf dem zusätzlichen Träger gemäß den auf dem zusätzlichen Träger erfassten DCI.
EP21178912.8A 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung Active EP3896893B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21178912.8A EP3896893B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
EP15180290.7A EP3128801B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP19169032.0A EP3547596B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP21178912.8A EP3896893B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung

Related Parent Applications (3)

Application Number Title Priority Date Filing Date
EP15180290.7A Division EP3128801B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP19169032.0A Division-Into EP3547596B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP19169032.0A Division EP3547596B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung

Publications (2)

Publication Number Publication Date
EP3896893A1 EP3896893A1 (de) 2021-10-20
EP3896893B1 true EP3896893B1 (de) 2023-10-25

Family

ID=53835929

Family Applications (3)

Application Number Title Priority Date Filing Date
EP21178912.8A Active EP3896893B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP15180290.7A Active EP3128801B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP19169032.0A Active EP3547596B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung

Family Applications After (2)

Application Number Title Priority Date Filing Date
EP15180290.7A Active EP3128801B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung
EP19169032.0A Active EP3547596B1 (de) 2015-08-07 2015-08-07 Selbst- und trägerübergreifende planung

Country Status (4)

Country Link
US (2) US10555329B2 (de)
EP (3) EP3896893B1 (de)
JP (1) JP6704417B2 (de)
WO (1) WO2017026086A1 (de)

Families Citing this family (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10687330B2 (en) 2016-07-21 2020-06-16 Qualcomm Incorporated Techniques for communicating on an uplink in a shared radio frequency spectrum band
US10775361B2 (en) * 2016-07-22 2020-09-15 Qualcomm Incorporated Monitoring control channel with different encoding schemes
US10687319B2 (en) * 2016-08-08 2020-06-16 Comcast Cable Communications, Llc Group power control for a secondary cell
US11153880B2 (en) * 2016-08-09 2021-10-19 Qualcomm Incorporated Power allocation across multiple carriers using shared and dedicated radio frequency spectrum
CN116782393A (zh) * 2016-08-12 2023-09-19 华为技术有限公司 一种系统信息发送方法及装置
WO2018072062A1 (zh) * 2016-10-17 2018-04-26 广东欧珀移动通信有限公司 信息传输方法和装置
US10925079B2 (en) * 2016-10-27 2021-02-16 Kt Corporation Method and device for scheduling uplink signal and downlink data channel in next generation wireless network
KR20180046358A (ko) 2016-10-27 2018-05-08 주식회사 케이티 차세대 무선 액세스망을 위한 스케줄링 방법 및 장치
US10327261B2 (en) * 2017-01-26 2019-06-18 Qualcomm Incorporated Directional listen before talk scheme
CN108574559B (zh) * 2017-03-13 2021-03-30 电信科学技术研究院 一种传输方法和装置
US10506630B2 (en) * 2017-03-24 2019-12-10 Kt Corporation Method for scheduling downlink data channel or uplink data channel in next radio network and apparatus thereof
CN109152069B (zh) 2017-06-15 2022-04-05 华为技术有限公司 传输控制信息的方法和设备
US11219023B2 (en) 2017-06-16 2022-01-04 Lg Electronics Inc. Method and apparatus for transmitting and receiving radio signals in a wireless communication system
WO2018231032A1 (ko) * 2017-06-16 2018-12-20 엘지전자 주식회사 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치
US10721723B2 (en) 2017-06-23 2020-07-21 Qualcomm Incorporated Dynamic padding field to match downlink and uplink downlink control information length
KR102443452B1 (ko) 2017-07-17 2022-09-15 삼성전자 주식회사 무선 통신 시스템에서 하향링크 제어정보를 전송하는 방법 및 장치
WO2019028816A1 (en) * 2017-08-11 2019-02-14 Qualcomm Incorporated SWITCHING BETWEEN STANDARD SUB-PRB AND PRB POWERS FOR EMTC PURPOSES
EP3497957B1 (de) * 2017-09-14 2020-11-04 Telefonaktiebolaget LM Ericsson (publ) Verfahren und vorrichtung zur trägermessung
CN111543074B (zh) * 2018-01-05 2022-12-27 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
BR112020014199A2 (pt) 2018-01-10 2020-12-01 Idac Holdings, Inc. método para uso em uma unidade de transmissão/recepção sem fio, unidade de transmissão/recepção sem fio, e, gnb
JP7078647B2 (ja) * 2018-01-12 2022-05-31 株式会社Ｎｔｔドコモ 端末、無線通信方法、基地局及びシステム
ES2837757T3 (es) 2018-03-26 2021-07-01 Asustek Comp Inc Método y aparato para la indicación de haz que considera la programación de portadora cruzada en un sistema de comunicación inalámbrica
EP3550748B1 (de) * 2018-04-05 2021-08-11 Siemens Aktiengesellschaft Verfahren zur erkennung von datenverfälschungen bei einer datenübertragung über eine fehlersichere kommunikationsverbindung
CN110475266B (zh) * 2018-05-11 2021-06-22 华为技术有限公司 通信方法、终端设备和网络设备
CN114157397A (zh) * 2018-05-11 2022-03-08 维沃移动通信有限公司 确定下行控制信息的方法和设备
CN110753398B (zh) * 2018-07-24 2022-03-01 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
ES2878163T3 (es) 2018-07-31 2021-11-18 Asustek Comp Inc Procedimiento y aparato para indicar el formato de ranura de una célula sin licencia en un sistema de comunicación inalámbrico
JP7100146B2 (ja) * 2018-09-10 2022-07-12 株式会社Ｎｔｔドコモ 端末、無線通信方法及びシステム
CN110972291B (zh) * 2018-09-29 2022-07-05 大唐移动通信设备有限公司 载波的搜索空间的确定方法、终端及网络设备
US11239939B2 (en) * 2019-03-22 2022-02-01 Samsung Electronics Co., Ltd. Scheduling in communication systems with multiple service types
US11178658B2 (en) 2019-03-29 2021-11-16 Lg Electronics Inc. Method and apparatus for transmitting and receiving control information for sidelink communication in wireless communication system
KR20210123405A (ko) * 2019-03-29 2021-10-13 엘지전자 주식회사 무선 통신 시스템에서 사이드링크 통신을 위한 제어 정보를 송수신하는 방법 및 장치
CN111867097A (zh) * 2019-04-30 2020-10-30 北京三星通信技术研究有限公司 接收下行控制信息的方法和设备
US11497054B2 (en) * 2019-05-02 2022-11-08 Qualcomm Incorporated Channel congestion measurement
US11582773B2 (en) * 2019-07-05 2023-02-14 Qualcomm Incorporated Multiple cross-carrier scheduling component carriers (CCs)
CN112399614B (zh) * 2019-08-12 2023-11-10 成都华为技术有限公司 一种通信方法及装置
CN112399436A (zh) * 2019-08-15 2021-02-23 华为技术有限公司 接收、发送下行控制信息的方法和装置
CN113225745B (zh) * 2020-01-21 2022-09-27 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
US11800518B2 (en) 2020-01-22 2023-10-24 Qualcomm Incorporated Techniques for physical downlink control channel (PDCCH) limits for multiple cells scheduling one cell in a wireless communication system
WO2021147116A1 (en) * 2020-01-24 2021-07-29 Qualcomm Incorporated Uplink adaptation in carrier aggregation
CN113225751B (zh) 2020-02-06 2023-05-05 维沃移动通信有限公司 搜索空间的监听方法和设备
CN113225817B (zh) * 2020-02-06 2023-04-07 维沃移动通信有限公司 调度方法、终端及网络侧设备
CN113382479B (zh) * 2020-02-25 2023-04-18 维沃移动通信有限公司 服务小区调度方法、终端设备和网络设备
EP4336941A2 (de) 2020-02-28 2024-03-13 Comcast Cable Communications, LLC Planung drahtloser kommunikationen
CN113543318A (zh) * 2020-04-15 2021-10-22 大唐移动通信设备有限公司 一种载波确定及指示方法、设备、装置、介质
US11700614B2 (en) * 2020-06-24 2023-07-11 Qualcomm Incorporated Configuring downlink control information to schedule multiple component carriers
US20220046688A1 (en) * 2020-08-06 2022-02-10 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
US11356906B1 (en) 2020-10-09 2022-06-07 Sprint Communications Company L.P. Addition thresholds for wireless access nodes based on frequency channel size
EP4327610A1 (de) * 2021-11-05 2024-02-28 ZTE Corporation Verfahren und systeme zur bestimmung des steuernachrichtenformats in drahtlosen netzwerken
WO2023211191A1 (ko) * 2022-04-27 2023-11-02 엘지전자 주식회사 무선 통신 시스템에서 신호 송수신 방법 및 장치

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8634374B2 (en) * 2009-12-17 2014-01-21 Lg Electronics Inc. Apparatus and method of avoiding control channel blocking
CN102792731A (zh) * 2010-05-11 2012-11-21 夏普株式会社 通信系统、通信装置、通信控制方法以及通信控制程序
US9420575B2 (en) * 2010-06-08 2016-08-16 Lg Electronics Inc. Method for searching control signal in a wireless access system supporting carrier aggregation (CA)
US20140119339A1 (en) * 2011-04-25 2014-05-01 Lg Electronics Inc. Method for controlling error for carrier aggregation and apparatus for same
WO2012157987A2 (ko) * 2011-05-17 2012-11-22 엘지전자 주식회사 무선통신 시스템에서 제어 정보를 전송 및 수신하는 방법과 이를 위한 장치
WO2013169003A1 (ko) * 2012-05-08 2013-11-14 엘지전자 주식회사 제어 신호 송수신 방법 및 이를 위한 장치
CN104734821B (zh) * 2013-12-19 2019-04-05 电信科学技术研究院 数据传输方法和装置
JP6425662B2 (ja) * 2013-12-27 2018-11-21 シャープ株式会社 端末装置、基地局装置および方法
KR101791845B1 (ko) * 2014-08-07 2017-10-31 엘지전자 주식회사 무선 통신 시스템에서 데이터를 송수신하기 위한 방법 및 이를 위한 장치
KR102068555B1 (ko) * 2015-03-17 2020-01-21 텔레폰악티에볼라겟엘엠에릭슨(펍) 허가된 어시스트 액세스에서의 스케줄링
CN107079053B (zh) * 2015-04-09 2020-07-07 华为技术有限公司 一种数据重传方法、设备及系统
US20160338023A1 (en) * 2015-05-14 2016-11-17 Sharp Laboratories Of America, Inc. User equipments, base stations and methods for license assisted access (laa)

Also Published As

Publication number Publication date
US10555329B2 (en) 2020-02-04
US11368967B2 (en) 2022-06-21
US20180152954A1 (en) 2018-05-31
EP3547596B1 (de) 2021-09-29
JP6704417B2 (ja) 2020-06-03
EP3128801A1 (de) 2017-02-08
EP3547596A1 (de) 2019-10-02
EP3896893A1 (de) 2021-10-20
EP3128801B1 (de) 2019-10-02
JP2018522452A (ja) 2018-08-09
US20200128565A1 (en) 2020-04-23
WO2017026086A1 (en) 2017-02-16

Similar Documents

Publication Publication Date Title
US11368967B2 (en) Self- and cross- carrier scheduling
JP7266184B2 (ja) 集積回路
EP3133888B1 (de) Uplink-übertragungsanzeige
EP3536078B1 (de) Verbesserte zweistufige berechtigungen in nicht lizenzierten zellen
CN109644485B (zh) 多个dci的冲突处理
AU2017353454B2 (en) Improved two-stage trigger procedure
US11985680B2 (en) Modulation order adaptation for partial subframes

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210611

AC Divisional application: reference to earlier application

Ref document number: 3128801

Country of ref document: EP

Kind code of ref document: P

Ref document number: 3547596

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

B565 Issuance of search results under rule 164(2) epc

Effective date: 20210916

REG Reference to a national code

Ref document number: 602015086300

Country of ref document: DE

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04L0005000000

Ipc: H04W0072120000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 74/08 20090101ALN20230331BHEP

Ipc: H04L 27/00 20060101ALI20230331BHEP

Ipc: H04W 72/12 20090101ALI20230331BHEP

Ipc: H04L 5/00 20060101AFI20230331BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 74/08 20090101ALN20230411BHEP

Ipc: H04L 27/00 20060101ALI20230411BHEP

Ipc: H04W 72/23 20230101ALI20230411BHEP

Ipc: H04L 5/00 20060101ALI20230411BHEP

Ipc: H04W 72/12 20090101AFI20230411BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20230525

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: PANASONIC INTELLECTUAL PROPERTY CORPORATION OF AMERICA

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AC Divisional application: reference to earlier application

Ref document number: 3128801

Country of ref document: EP

Kind code of ref document: P

Ref document number: 3547596

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015086300

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1626015

Country of ref document: AT

Kind code of ref document: T

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240126

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240225

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240126

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240125

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240226