WO2017180179A1 - Systèmes, procédés et dispositifs permettant une transmission d'octroi de liaison montante optimisée pour permettre une planification de multiples sous-trames - Google Patents

Systèmes, procédés et dispositifs permettant une transmission d'octroi de liaison montante optimisée pour permettre une planification de multiples sous-trames Download PDF

Info

Publication number
WO2017180179A1
WO2017180179A1 PCT/US2016/050655 US2016050655W WO2017180179A1 WO 2017180179 A1 WO2017180179 A1 WO 2017180179A1 US 2016050655 W US2016050655 W US 2016050655W WO 2017180179 A1 WO2017180179 A1 WO 2017180179A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink grant
uplink
lbt
subframe
transmissions
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.)
Ceased
Application number
PCT/US2016/050655
Other languages
English (en)
Inventor
Abhijeet Bhorkar
Qiaoyang Ye
Huaning Niu
Jeongho Jeon
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.)
Intel IP Corp
Original Assignee
Intel IP Corp
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 Intel IP Corp filed Critical Intel IP Corp
Priority to CN201680083918.4A priority Critical patent/CN108886805B/zh
Publication of WO2017180179A1 publication Critical patent/WO2017180179A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • 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
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • the present disclosure relates to uplink transmissions in cellular devices and more specifically to optimized uplink grant transmission to enable multi-subframe scheduling in a shared wireless medium.
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
  • Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long-Term Evolution
  • IEEE 802.16 Institute of Electrical and Electronics Engineers
  • WiMAX worldwide interoperability for microwave access
  • Wi-Fi wireless local area networks
  • the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node B also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB
  • RNC Radio Network Controller
  • RANs use a radio access technology (RAT) to communicate between the RAN Node and UE.
  • RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network.
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN enhanced data rates for GSM evolution
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN E-UTRAN
  • a core network can be connected to the UE through the RAN Node.
  • the core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).
  • SGW serving gateway
  • PGW packet data network gateway
  • ANDSF access network detection and selection function
  • ePDG enhanced packet data gateway
  • MME mobility management entity
  • FIG. 1 is a diagram illustrating a radio access network (RAN) system using Long- Term Evolution (LTE) and License Assisted Access (LAA) consistent with embodiments disclosed herein.
  • RAN radio access network
  • LTE Long- Term Evolution
  • LAA License Assisted Access
  • FIG. 2 is a table illustrating downlink control format (DCI) 0 fields consistent with embodiments disclosed herein.
  • DCI downlink control format
  • FIG. 3 is a table illustrating available interlace index assignments based on a starting interlace index consistent with embodiments disclosed herein.
  • FIG. 4 is a table illustrating fields for single subframe scheduling including interlace allocation consistent with embodiments disclosed herein.
  • FIG. 5 is a table illustrating fields for multi-subframe scheduling using scheme 1 consistent with embodiments disclosed herein.
  • FIG. 6 is a table illustrating schemes and bit length for multi-subframe scheduling consistent with embodiments disclosed herein.
  • FIG. 7 is a table illustrating fields for multi-subframe scheduling using scheme 8 consistent with embodiments disclosed herein.
  • FIG. 8 is diagram illustrating an indication of cross-transmission opportunity (TxOP) with explicit timing relationship consistent with embodiments disclosed herein.
  • FIG. 9 is a schematic diagram illustrating the structure of a Long-Term Evolution
  • LTE Long Term Evolution
  • FIG. 10 is a block diagram illustrating electronic device circuitry that may be radio access node (RAN) circuitry (such as an eNB circuitry), UE circuitry, network node circuitry, or some other type of circuitry consistent with embodiments disclosed herein.
  • RAN radio access node
  • UE User Equipment
  • network node circuitry or some other type of circuitry consistent with embodiments disclosed herein.
  • FIG. 11 is a block diagram illustrating example components of a user equipment (UE) or mobile station (MS) device consistent with embodiments disclosed herein.
  • UE user equipment
  • MS mobile station
  • FIG. 12 is block diagram of a method for consistent with embodiments disclosed herein.
  • FIG. 13 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a machine-readable storage medium) consistent with embodiments disclosed herein.
  • a machine-readable or computer-readable medium e.g., a machine-readable storage medium
  • UL LAA uplink
  • PUSCH physical uplink shared channel
  • B-IFDMA block interleaved frequency division multiple access
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
  • Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.11 standard, which is commonly known to industry groups as Wi-Fi.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long-Term Evolution
  • IEEE 802.16 Institute of Electrical and Electronics Engineers
  • WiMAX worldwide interoperability for microwave access
  • Wi-Fi IEEE 802.11 standard
  • the base station can include Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and/or Radio Network Controllers (RNCs) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • RNCs Radio Network Controllers
  • LTE Long-Term Evolution
  • LAA Licensed- Assisted Access
  • CA flexible carrier aggregation
  • LTE operation in the unlicensed spectrum includes but is not limited to (1) LTE operation in the unlicensed spectrum via dual connectivity (DC) - called DC based LAA herein, and (2) standalone LTE system in the unlicensed spectrum (or shared spectrum, shared medium or unlicensed medium), where LTE-based technology solely operates in the unlicensed spectrum without an "anchor" in the licensed spectrum - called MuLTEfire.
  • MuLTEfire combining the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments, is envisioned as a technology component to help meet increasing wireless traffic.
  • An unlicensed frequency band of interest in 3GPP is the 5 GHz band, which has wide spectrum with global common availability.
  • the 5 GHz band in the U.S. is governed by Unlicensed National Information Infrastructure (U-NII) rules by the Federal Communications Commission (FCC).
  • An incumbent system in the 5 GHz band is the Wireless Local Area Networks (WLAN), specifically those based on the IEEE 802.11 a/n/ac technologies. Since WLAN systems are widely deployed by both individuals and operators for carrier-grade access service and data offloading, sufficient care must be taken before the deployment.
  • This incumbent use implies that Listen-Before-Talk (LBT) be considered as a mandatory feature of Rel-13 LAA system for fair coexistence with the incumbent system.
  • LBT is a procedure whereby radio transmitters first sense a wireless medium for signals (which can include recognized signals, unrecognized signals or noise above a threshold) and transmit only if the wireless medium is sensed to be idle.
  • UL LAA design is being considered.
  • the UL LAA design is inherently different from the legacy LTE design in that the UE is required to perform LBT before transmission. Additionally there are additional restrictions for UL LAA transmissions to obey the regulations (e.g., ETSI).
  • multi-subframe scheduling (A) flexible timing and (B) cross- TxOP scheduling can be supported.
  • (A) flexible timing in Rel-14 eLAA WI/MF, flexible timing between UL grant and UL transmission can be supported.
  • PUSCH physical uplink shared channel
  • a single UL grant in a subframe for a UE can schedule a single PUSCH transmission in a single subframe while a UE can receive multiple UL grants in a subframe for PUSCH transmissions in different subframes. This is referred as single subframe scheduling herein.
  • cross-TxOP UL scheduling aims to address poor LAA UL
  • TxOP transmission burst
  • two options can be considered (but are not limited to only these two examples).
  • an eNB schedules the UE with a fixed time relationship between grant and transmission.
  • an eNB schedules the UE without a fixed time relationship between grant and transmission, and the UE transmits after receiving a trigger sent by eNB on C-PDCCH.
  • the UL grant can also include relevant information to schedule multiple subframes that may be present within a maximum channel occupancy time (MCOT) or outside MCOT or a combination of the two.
  • MCOT maximum channel occupancy time
  • indication Rel-13 LAA design restricts the MCOT or transmission opportunity (TxOP) after completion of LBT at the eNB to be 8 ms (if LAA co-exists with Wi-Fi) or 10 ms (otherwise).
  • UEs that are scheduled within a TxOP perform a single interval LBT or a short cat 4 LBT, for example, by puncturing the first symbol of PUSCH transmission. It is also possible that the UE performs no LBT (e.g., if UE has already completed UL LBT in the previous subframe within the MCOT).
  • a UL grant can indicate a type of LBT to be performed including no LBT, single interval LBT, and cat 4 LBT, which can use a total of 2 bits for such indication.
  • B-IFDMA block interleaved frequency division multiple access
  • EIRP Effective Isotropic Radiated Power
  • An interlace consists of equidistance physical resource blocks (PRBs) spread across the system bandwidth (which can also satisfy regulations, such as the PSD described above).
  • PRBs physical resource blocks
  • the number of interlaces is dependent on the inter-PRB distance and the system bandwidth. For example, 10 interlaces are supported for 20 MHz bandwidth in MF. It is possible that the distance between PRBs is randomized keeping the number of interlaces fixed according to the fixed PRB distance and simultaneously satisfy the regulations. Such randomizations can be useful for inter-cell interference randomization and intermodulation distortion.
  • a UE can be assigned multiple such interlaces.
  • the Resource Indication Value (RIV) UL grant may be optimized to indicate assigned interlaces rather than PRBs.
  • FIG. 1 is a diagram illustrating a radio access network (RAN) system using Long- Term Evolution (LTE) and licensed assisted access (LTE) consistent with embodiments disclosed herein.
  • LTE Long- Term Evolution
  • LTE licensed assisted access
  • FIG. 1 an example of a portion of a RAN system 100 that includes a single cellular air interface (such as an LTE/LTE- Advanced access link) being provided between the LTE RAN Node 104 and the UE 102 (i.e., on Access Link A), and an air interface (a supplemental network interface such as a wireless licensed assisted access (LAA) based interface) being provided between the LAA RAN Node 106 and the UE 102 (i.e., on Access Link B).
  • LAA wireless licensed assisted access
  • UE 102 is located in macro cell coverage 108.
  • the UE 102 determines that connection with a LAA RAN Node 106 will be beneficial to a user of the UE 102.
  • the UE 102 retains Access Link A to LTE RAN Node 104.
  • the UE 102 can offload some, part or all of wireless services onto Access Link B.
  • the UE 102 disconnects from Access Link A and moves all wireless services to Access Link B.
  • Access Link A uses a licensed medium (e.g., a licensed spectrum or bands) and Access Link B uses an unlicensed medium (e.g., an unlicensed spectrum or bands).
  • Access Link A and Access Link B use different frequencies (e.g., LTE licensed frequencies and unlicensed frequencies) and different link technology (e.g., LTE and LAA).
  • LTE Long Term Evolution
  • LAA Link technology
  • a UE can use DC based LAA by using Access Link A and Access Link B.
  • the UE can use access link B with MuLTEfire, as a standalone LTE system in the unlicensed spectrum, where LTE- based technology solely operates in unlicensed spectrum without an "anchor" in the licensed spectrum.
  • FIG. 2 is a table illustrating downlink control information (DCI) format 0 fields consistent with embodiments disclosed herein.
  • Legacy LTE design uses DCI format 0 and DCI format 4 for scheduling PUSCH transmission.
  • the bit assignment for DCI format 0 is described in table 200.
  • This DCI format 0 can be further extended to support enhanced LAA (eLAA) and multi-subframe (MF) design.
  • the uplink (UL) grant design is extended to support eLAA and multi-subframe design. Examples of such extentions can be seen in FIGs. 3 and 6.
  • LBT listen before talk
  • a listen before talk (LBT) indication field can be used to indicate UE behavior before transmitting on the UL (e.g., no LBT, single interval LBT, category 4 LBT (a.k.a. cat 4 or cat 4 LBT).
  • a transmission opportunity (TxOP) field can use one bit to indicate whether the UL transmission will be within TxOP or outside TxOP.
  • a transmission opportunity is a set of contiguous transmissions that can occur after the UE or LAA RAN Node accesses the medium.
  • a TxOP can be defined as 4 ms after the LAA RAN Node transmits a UL grant (other durations can be used, such as values between 4ms and 20ms).
  • An outside TxOP indicator can indicate a type of transmission outside of TxOP (e.g., a fixed time relationship to a UL grant or without a fixed time relationship to UL grant) using one bit (type 1 or type 2).
  • a 4 bit timing relationship field can be added. If a UL subframe is within TxOP, the UL grant indicates the offset between the UL grant that scheduled UL subframes and the first scheduled UL subframe. If a UL grant schedules via cross-TxOP, the UE indicates if UE is scheduled within TxOP or outside TxOP. The UE infers the valid subframe with respect to the first scheduled UL subframe outside TxOP.
  • the set of scheduled UL subframes can also be indicated by a field.
  • N max being a maximum number of subframes that can be
  • HARQ hybrid automatic repeat request
  • UL grant design for an eLAA MF design can include other modifications.
  • An RIV field can be reused for indicating the assigned interlaces (such as with 10 bits or optimized 6 bits for indication).
  • a FormatO-1 A-Flag is not used. It is expected that the LAA UL grant will use a different DCI format.
  • a frequency hopping flag is not used for eLAA if the frequency hopping across slots is not used within an interlace.
  • RV redundancy version
  • Information bits of a physical downlink control channel (PDCCH) can be appended with 16 bits before channel coding/rate matching. The channel coding can be performed with the tail biting convolutional code (TBCC) as per legacy PDCCH.
  • TBCC tail biting convolutional code
  • FIG. 3 is a table 300 illustrating available interlace index assignments based on a starting interlace index consistent with embodiments disclosed herein.
  • a UE may be assigned multiple logical interlaces.
  • Two design options can include an interlace ordering method and a bitmap method.
  • the interlace assignment is indicated by the starting interlace index and the number of interlaces to be assigned to the UE.
  • the possible interlace assignments up to 55 possible assignments in the case of single-user resource allocation
  • any of the 10 interlaces are possible for selection.
  • a starting interlace index of 1 only the 9 highest interlaces are possible for selection. This continues until there is a starting interlace index of 9, where only the highest interlace is possible for selection.
  • the indication of interlace assignment is performed via a bitmap.
  • the number of bits in the bitmap for each UE equals the number of interlaces, and each bit in the bitmap shows whether that interlace is assigned or not.
  • a 10-bit bitmap can be used, wherein each bit corresponds to an interlace.
  • Each UE would be indicated by a specific 10-bit bitmap, to indicate the interlaces that are assigned to it. For example, "0110010001" indicates that interlaces ⁇ 1, 2, 5, 9 ⁇ are assigned to the UE. For 20 MHz, with 10 interlaces, 10 bits are required.
  • FIG. 4 is a table 400 illustrating fields for single subframe scheduling including interlace allocation consistent with embodiments disclosed herein.
  • the UL grant indicates the required field for the operation of UL LBT. Additionally RIV is modified to indicate the interlace allocation. In one embodiment 6 bits are used to indicate interlace assignment. In another embodiment 10 bits are used for interlace assignment.
  • the UL grant for scheduling a single subframe for eLAA/MF can use up to 36 bits (with 6 bit interlace mapping). In comparison, DCI 0 uses 32 bits. Further description of these fields can be found in conjunction with FIG. 2.
  • FIG. 5 is a table illustrating fields for multi-subframe scheduling using a scheme 1 (as shown in FIG. 6) consistent with embodiments disclosed herein.
  • Multi-subframe scheduling may schedule multiple UL subframes in a flexible way, wherein different UL resources, MCS, HARQ ID, DI, and RV are indicated via DCI separately for each scheduled subframe.
  • PDCCH physical downlink control channel
  • a UE may need to blindly detect the PDCCH based on a number of scheduled UL transmissions based on scheduled UL subframes. This can increase UE complexity.
  • various design options can be considered that reduce the PDCCH overhead and blind detection at the UE.
  • the number of bits used for UL grant can be predesigned based on a maximum number of possible scheduled subframes (N max ).
  • a UE may need to perform blind decoding over possible choices of N max to the number of scheduled subframes.
  • table 500 an embodiment for a scheme of DCI fields is shown.
  • RIV, MCS, HARQ ID, NDI, RV, LBT information, and cross- TxOP info are separately indicated for each subframe.
  • a number of bits are 16 + 22 X N max + [log 2 N max .
  • N max 8 the number of bits required can be as large as 195 bits. This option is the most flexible option for multi-subframe scheduling.
  • FIG. 6 is a table illustrating schemes and bit length for multi-subframe scheduling in addition to the scheme 1 described in conjunction with FIG. 5.
  • the schemes illustrate different embodiments of DCI fields that can be used in multi-subframe scheduling.
  • Scheme 5 is a slight variation of scheme 3.
  • UL LBT is not separately indicated for each subframe.
  • the first subframe of the UL burst can perform single interval LBT or cat 4 LBT. This information is implicitly obtained based on cross-TxOP info. Thus, the two bits needed for LBT type indication are not needed. All subframes following the first subframe perform single interval LBT. In this option, the number of bits required are 31 + 5 X N max +
  • FIG. 8 is a diagram 800 illustrating an indication of cross-transmission opportunity (TxOP) with an explicit timing relationship consistent with embodiments disclosed herein.
  • TxOP cross-transmission opportunity
  • the presence of potential PUSCH transmission outside TxOP is indicated by the UL grant 806 in the previous TxOP with an explicit timing relationship.
  • the scheduled UE performs a cat 4 LBT 804 if it is scheduled outside TxOP.
  • the parameters for the cat 4 LBT 804 to be used can be based on the priority class associated with the traffic scheduled for the UE.
  • the UE is indicated if the subframe scheduled by UL grant 806 is within TxOP or outside TxOP. This indication is used to determine the LBT to be performed by the UE.
  • a scheduled UE in the next TxOP performs cat 4 LBT 804 with self-defer.
  • the scheduled UE can start the PUSCH transmission at the subframe boundary or after the second symbol of the subframe containing PUSCH transmission depending on the time of the cat 4 LBT 804 completion.
  • the e B performs blind detection to determine the start of the PUSCH transmission.
  • a scheduled UE may continue to perform LBT until it can successfully complete LBT before any of the scheduled UL subframes.
  • the behavior of the UE if the UE cannot complete LBT for the scheduled subframes outside TxOP, can include two options. For Option 1, the UE restarts the LBT for any future cross-TxOP scheduling if the UE cannot complete LBT before all scheduled UL subframes within the next TxOP. For Option 2, the UE may resume the LBT for any future cross-TxOP unless otherwise indicated by the eNB.
  • the UE can restart the LBT procedure if no scheduled UL subframe within Cross-TxOP is indicated by the eNB for a configured duration of time. In some embodiments, Option 2 is preferred due to its similarity with WLAN operation. After completion of the LBT, the UE can transmit on the scheduled UL subframe, as indicated by the UL grant and if the scheduled subframe occurs after the completion of the LBT.
  • FIG. 9 is a schematic diagram 900 illustrating the structure of a Long-Term Evolution (LTE) communication frame 905.
  • a frame 905 has a duration of 10 milliseconds (ms).
  • the frame 905 includes ten subframes 910, each having a duration of 1 ms.
  • Each subframe 910 includes two slots 915, each having a duration of 0.5 ms. Therefore, the frame 905 includes 20 slots 915.
  • Each slot 915 includes six or seven orthogonal frequency-division multiplexing (OFDM) symbols 920.
  • the number of OFDM symbols 920 in each slot 915 is based on the size of the cyclic prefixes (CP) 925.
  • CP cyclic prefixes
  • the number of OFDM symbols 920 in the slot 915 is seven while in normal mode CP and six in extended mode CP.
  • the smallest allocable unit for transmission is a resource block 930 (i.e., physical resource block (PRB) 930). Transmissions are scheduled by PRB 930.
  • a PRB 930 consists of 12 consecutive subcarriers 935, or 180 kHz, for the duration of one slot 915 (0.5 ms).
  • Each PRB 930 consists of 72 resource elements 940 in the case of extended mode CP.
  • FIG. 10 is a block diagram illustrating electronic device circuitry 1000 that may be radio access node (RAN) node circuitry (such as an eNB circuitry), UE circuitry, network node circuitry, or some other type of circuitry in accordance with various embodiments.
  • the electronic device circuitry 1000 may be, or may be incorporated into or otherwise a part of, a RAN Node (e.g., an eNB), a UE, a mobile station (MS), a BTS, a network node, or some other type of electronic device.
  • the electronic device circuitry 1000 may include radio transmit circuitry 1010 and receive circuitry 1012 coupled to control circuitry 1014 (e.g., baseband processor(s), etc.).
  • the transmit circuitry 1010 and/or receive circuitry 1012 may be elements or modules of transceiver circuitry, as shown.
  • some or all of the control circuitry 1015 can be in a device separate or external from the transmit circuitry 1010 and the receive circuitry 1012 (baseband processors shared by multiple antenna devices, as in cloud-RAN (C-RAN) implementations, for example).
  • C-RAN cloud-RAN
  • the electronic device circuitry 1010 may be coupled with one or more plurality of antenna elements 1016 of one or more antennas.
  • the electronic device circuitry 1000 and/or the components of the electronic device circuitry 1000 may be configured to perform operations similar to those described elsewhere in this disclosure.
  • the transmit circuitry 1010 can transmit UL data as shown in FIGs. 1 and 8.
  • the receive circuitry 1012 can receive downlink (DL) data, DCI data and/or an uplink grant as shown in FIGs. 1 and 8.
  • the transmit circuitry 1010 can transmit downlink (DL) data, DCI data and/or an uplink grant as shown in FIGs. 1 and 8.
  • the receive circuitry 1012 can receive UL data as shown in FIGs. 1 and 8.
  • the electronic device circuitry 1000 shown in FIG. 10 is operable to perform one or more methods, such as the methods shown in FIG. 12.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware
  • ASIC Application Specific Integrated Circuit
  • processor shared, dedicated, or group
  • memory shared, dedicated, or group
  • circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • FIG. 11 is a block diagram illustrating
  • example components of a user equipment (UE) or mobile station (MS) device 1100 may include application circuitry 1102, baseband circuitry 1104, Radio Frequency (RF) circuitry 1106, front-end module (FEM) circuitry 1108, and one or more antennas 1110, coupled together at least as shown in FIG. 11.
  • UE user equipment
  • MS mobile station
  • the UE device 1100 may include application circuitry 1102, baseband circuitry 1104, Radio Frequency (RF) circuitry 1106, front-end module (FEM) circuitry 1108, and one or more antennas 1110, coupled together at least as shown in FIG. 11.
  • RF Radio Frequency
  • FEM front-end module
  • the application circuitry 1102 may include one or more application processors.
  • the application circuitry 1102 may include one or more single- core or multi-core processors.
  • the processor(s) may include any combination of general- purpose processors and dedicated processors (e.g., graphics processors,
  • the processor(s) may be operably coupled and/or include memory/storage, and may be configured to execute instructions stored in the mem ory /storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 1104 may include one or more single-core or multi-core processors.
  • the baseband circuitry 1104 may include one or more baseband processors and/or control logic.
  • the baseband circuitry 1104 may be configured to process baseband signals received from a receive signal path of the RF circuitry 1106.
  • the baseband 1104 may also be configured to generate baseband signals for a transmit signal path of the RF circuitry 1106.
  • the baseband processing circuitry 1104 may interface with the application circuitry 1102 for generation and processing of the baseband signals, and for controlling operations of the RF circuitry 1106.
  • the baseband circuitry 1104 may include at least one of a second generation (2G) baseband processor 1104 A, a third generation (3G) baseband processor 1104B, a fourth generation (4G) baseband processor 1104C, other baseband processor(s) 1104D for other existing generations, and generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 1104 e.g., at least one of baseband processors 1104A-1104D
  • the radio control functions may include signal modulation/demodulation, encoding/decoding, radio frequency shifting, other functions, and combinations thereof.
  • modulation/demodulation circuitry of the baseband circuitry 1104 may be programmed to perform Fast-Fourier Transform (FFT), precoding, constellation mapping/demapping functions, other functions, and combinations thereof.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 1104 may be programmed to perform convolutions, tail-biting convolutions, turbo, Viterbi, Low Density Parity Check (LDPC) encoder/decoder functions, other functions, and combinations thereof.
  • Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and may include other suitable functions.
  • the baseband circuitry 1104 may include elements of a protocol stack.
  • elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • a central processing unit (CPU) 1104E of the baseband circuitry 1104 may be programmed to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry 1104 may include one or more audio digital signal processor(s) (DSP) 1104F.
  • the audio DSP(s) 1104F may include elements for compression/decompression and echo cancellation.
  • the audio DSP(s) 1104F may also include other suitable processing elements.
  • the baseband circuitry 1104 may further include memory/storage 1104G.
  • the memory/storage 1104G may include data and/or instructions for operations performed by the processors of the baseband circuitry 1104 stored thereon.
  • the memory/storage 1104G may include any combination of suitable volatile memory and/or non-volatile memory.
  • the memory/storage 1104G may also include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.
  • ROM read-only memory
  • DRAM dynamic random access memory
  • the memory/storage 1104G may be shared among the various processors or dedicated to particular processors.
  • Components of the baseband circuitry 1104 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1104 and the application circuitry 1102 may be implemented together, such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 1104 may provide for
  • the baseband circuitry 1104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 1104 is configured to support radio communications of more than one wireless protocol.
  • the RF circuitry 1106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 1106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1108, and provide baseband signals to the baseband circuitry 1104.
  • the RF circuitry 1106 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband circuitry 1104, and provide RF output signals to the FEM circuitry 1108 for transmission.
  • the RF circuitry 1106 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 1106 may include mixer circuitry 1106A, amplifier circuitry 1106B, and filter circuitry 1106C.
  • the transmit signal path of the RF circuitry 1106 may include filter circuitry 1106C and mixer circuitry 1106 A.
  • the RF circuitry 1106 may further include synthesizer circuitry 1106D configured to synthesize a frequency for use by the mixer circuitry 1106 A of the receive signal path and the transmit signal path.
  • the mixer circuitry 1106 A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1108 based on the synthesized frequency provided by synthesizer circuitry 1106D.
  • the amplifier circuitry 1106B may be configured to amplify the down-converted signals.
  • the filter circuitry 1106C may include a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 1104 for further processing.
  • the output baseband signals may include zero-frequency baseband signals, although this is not a requirement.
  • the mixer circuitry 1106A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1106 A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1106D to generate RF output signals for the FEM circuitry 1108.
  • the baseband signals may be provided by the baseband circuitry 1104 and may be filtered by filter circuitry 1106C.
  • the filter circuitry 1106C may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1106 A of the receive signal path and the mixer circuitry 1106 A of the transmit signal path may include two or more mixers, and may be arranged for quadrature downconversion and/or upconversion, respectively.
  • the mixer circuitry 1106 A of the receive signal path and the mixer circuitry 1106 A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 1106A of the receive signal path and the mixer circuitry 1106A may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 1106A of the receive signal path and the mixer circuitry 1106 A of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 1106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 1104 may include a digital baseband interface to communicate with the RF circuitry 1106.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 1106D may include one or more of a fractional -N synthesizer and a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1106D may include a delta-sigma synthesizer, a frequency multiplier, a synthesizer comprising a phase-locked loop with a frequency divider, other synthesizers and combinations thereof.
  • the synthesizer circuitry 1106D may be configured to synthesize an output frequency for use by the mixer circuitry 1106 A of the RF circuitry 1106 based on a frequency input and a divider control input.
  • the synthesizer circuitry 1106D may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1104 or the applications processor 1102 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1102.
  • the synthesizer circuitry 1106D of the RF circuitry 1 106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may include a dual modulus divider (DMD)
  • the phase accumulator may include a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • the DLL may provide negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • the synthesizer circuitry 1106D may be configured to generate a carrier frequency as the output frequency.
  • the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency, etc.) and used in conjunction with a quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 1106 may include an IQ/polar converter.
  • the FEM circuitry 1108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1110, amplify the received signals, and provide the amplified versions of the received signals to the RF circuitry 1106 for further processing.
  • the FEM circuitry 1108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1106 for transmission by at least one of the one or more antennas 1110.
  • the FEM circuitry 1108 may include a TX/RX switch configured to switch between a transmit mode and a receive mode operation.
  • the FEM circuitry 1108 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 1108 may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1106).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 1108 may include a power amplifier (PA) configured to amplify input RF signals (e.g., provided by RF circuitry 1106), and one or more filters configured to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1110.
  • PA power amplifier
  • the MS device 1100 may include additional elements such as, for example, memory/storage, a display, a camera, one of more sensors, an input/output (I/O) interface, other elements, and combinations thereof.
  • additional elements such as, for example, memory/storage, a display, a camera, one of more sensors, an input/output (I/O) interface, other elements, and combinations thereof.
  • FIG. 12 is block diagram of a method for multiple physical uplink transmissions using an unlicensed wireless medium. The method can be accomplished using systems such as those shown in FIG. 1 including LTE RAN Node 104, LAA RAN Node 106 and UE 102.
  • a UE processes an uplink grant from an eNB, the uplink grant comprising an interlace allocation assignment schedule for PUSCH transmissions using the unlicensed wireless medium.
  • the UE senses the unlicensed medium to determine if the unlicensed medium is idle at an physical resource block at an interlace allocation assignment.
  • the system uses the sensing to determine if the unlicensed medium is idle.
  • the UE when the unlicensed medium is determined to be idle, the UE generates a PUSCH transmission based at least in part on the schedule.
  • the UE when the unlicensed medium is determined to be busy, the UE prevents the PUSCH transmission during the schedule.
  • FIG. 13 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 13 shows a diagrammatic representation of hardware resources 1300 including one or more processors (or processor cores) 1310, one or more memory/storage devices 1320, and one or more communication resources 1330, each of which are communicatively coupled via a bus 1340.
  • the processors 1310 may include, for example, a processor 1312 and a processor 1314.
  • the memory/storage devices 1320 may include main memory, disk storage, or any suitable combination thereof.
  • the communication resources 1330 may include interconnection and/or network interface components or other suitable devices to communicate with one or more peripheral devices 1304 and/or one or more databases 1306 via a network 1308.
  • the communication resources 1330 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low
  • Instructions 1350 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1310 to perform any one or more of the methodologies discussed herein.
  • the instructions 1350 may reside, completely or partially, within at least one of the processors 1310 (e.g., within the processor's cache memory), the memory/storage devices 1320, or any suitable combination thereof.
  • any portion of the instructions 1350 may be transferred to the hardware resources 1300 from any combination of the peripheral devices 1304 and/or the databases 1306. Accordingly, the memory of processors 1310, the memory/storage devices 1320, the peripheral devices 1304, and the databases 1306 are examples of computer-readable and machine-readable media.
  • Example 1 is an apparatus of a user equipment (UE).
  • the apparatus contains storage designed to store an uplink grant configuration.
  • the apparatus contains a processor designed to process an uplink grant from radio access network node (RAN node), the uplink grant including the uplink grant configuration and a schedule for multiple physical uplink transmissions using an unlicensed wireless medium.
  • the apparatus further contains a processor designed to sense the unlicensed medium for signals or noise to determine if the unlicensed medium is idle when the unlicensed medium is determined to be idle, generate the multiple physical uplink transmissions during the schedule and when the unlicensed medium is determined to be busy, preventing the multiple physical uplink transmissions during the schedule.
  • Example 2 is the apparatus of Example 1, where the multiple physical uplink transmissions include physical uplink shared channel (PUSCH) transmissions or physical uplink control channel (PUCCH) transmissions.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • Example 3 is the apparatus of Example 1, where each of the multiple physical uplink transmissions include a subframe.
  • Example 4 is the apparatus of Example 1, where the uplink grant schedules one or more uplink subframes.
  • Example 5 is the apparatus of Example 1, where the uplink grant includes an indicator that the uplink grant is within maximum channel occupancy time (MCOT), allowing the UE to use a shorter listen before talk (LBT) protocol.
  • MCOT maximum channel occupancy time
  • LBT listen before talk
  • Example 6 is the apparatus of Example 5, where the shorter listen before talk (LBT) protocol is a single interval LBT.
  • Example 7 is the apparatus of Example 5, where the shorter listen before talk (LBT) protocol is a short category 4 LBT including puncturing a first symbol of a physical uplink transmission shared channel (PUSCH) transmission.
  • LBT listen before talk
  • Example 8 is the apparatus of Example 1, where the uplink grant includes an indicator that the uplink grant is outside a maximum channel occupancy time (MCOT).
  • MCOT maximum channel occupancy time
  • Example 9 is the apparatus of Example 8, where the uplink grant being outside the
  • MCOT causes the UE to use a category 4 listen before talk (LBT) protocol.
  • LBT listen before talk
  • Example 10 is the apparatus of Example 1, where no listen before talk (LBT) protocol is performed for sequential uplink transmissions after a LBT protocol was performed before a first transmission.
  • LBT listen before talk
  • Example 11 is the apparatus of Example 1, where the uplink grant indicates a type of uplink listen before talk (LBT) protocol.
  • LBT listen before talk
  • Example 12 is the apparatus of Example 1, where the uplink grant indicates that a scheduled transmission scheduled via a cross-transmission opportunity (TxOP) includes an explicit timing relationship between the uplink grant and a physical uplink transmission shared channel (PUSCH) transmission.
  • TxOP cross-transmission opportunity
  • PUSCH physical uplink transmission shared channel
  • Example 13 is the apparatus of Example 1, where the uplink grant indicates resource indication value (RIV), modulation and coding scheme (MCS), hybrid automatic repeat request identifier (HARQ ID), new data indicator ( DI), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) information separately for each subframe.
  • RRIV resource indication value
  • MCS modulation and coding scheme
  • HARQ ID hybrid automatic repeat request identifier
  • DI new data indicator
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 14 is the apparatus of Example 1, where the uplink grant indicates modulation and coding scheme (MCS), hybrid automatic repeat request identifier (HARQ ID), new data indicator (NDI), redundancy version (RV), listen before talk (LBT)
  • MCS modulation and coding scheme
  • HARQ ID hybrid automatic repeat request identifier
  • NDI new data indicator
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP information and cross-transmission opportunity separately for each scheduled subframe via a single uplink grant; and where resource indication value (RIV) is fixed for scheduled uplink subframes.
  • Example 15 is the apparatus of Example 1, where the uplink grant indicates hybrid automatic repeat request identifier (HARQ ID), new data indicator (NDI), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross- TxOP) separately for each subframe via a single UL grant; and where resource indication value (RIV), modulation and coding scheme (MCS), and redundancy version (RV) are fixed for scheduled uplink subframes.
  • HARQ ID hybrid automatic repeat request identifier
  • NDI new data indicator
  • RV redundancy version
  • LBT listen before talk
  • cross- TxOP cross-transmission opportunity
  • Example 16 is the apparatus of Example 1, where the uplink grant indicates hybrid automatic repeat request identifier (HARQ ID) and new data indicator (NOT) information separately for each subframe via a single UL grant; and where resource indication value (RIV), modulation and coding scheme (MCS), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes.
  • HARQ ID hybrid automatic repeat request identifier
  • NOT new data indicator
  • Example 17 is the apparatus of Example 1, where the uplink grant indicates new data indicator ( DI) information separately for each subframe and where resource indication value (RIV), modulation and coding scheme (MCS), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes, and where the uplink grant indicates a first hybrid automatic repeat request identifier (HARQ ID) for a first uplink subframe and subsequent HARQ IDs for remaining subframes are implicitly computed.
  • DI resource indication value
  • MCS modulation and coding scheme
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 18 is the apparatus of Example 1, where the uplink grant indicates redundancy version (RV) and new data indicator (NDI) information separately for each subframe, and where resource indication value (RIV), modulation and coding scheme (MCS), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes, and where the uplink grant indicates a first hybrid automatic repeat request identifier (HARQ ID) for a first uplink subframe and subsequent HARQ IDs for remaining subframes are implicitly computed.
  • RV redundancy version
  • NDI new data indicator
  • RIV resource indication value
  • MCS modulation and coding scheme
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 19 is the apparatus of Example 18, where the subsequent HARQ IDs for remaining subframes are implicitly computed by sequentially incrementing a subframe offset with respect to the first HARQ ID.
  • Example 20 is the apparatus of Example 1, where the uplink grant indicates the new data indicator (NDI) information, resource indication value (RIV), modulation and coding scheme (MCS), redundancy version (RV), listen before talk (LBT) information and cross- transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes, and where the uplink grant indicates a first hybrid automatic repeat request identifier (HARQ ID) for a first uplink subframe and subsequent HARQ IDs for remaining subframes are implicitly computed.
  • NDI new data indicator
  • RMV modulation and coding scheme
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross- transmission opportunity
  • Example 21 is an apparatus of enhanced node B (eNB).
  • the apparatus includes storage designed to store an uplink grant configuration.
  • the apparatus also includes a processor designed to generate an uplink grant, the uplink grant includes a schedule for multiple PUSCH transmissions using an unlicensed wireless medium and an indication of a type of listen before talk (LBT) sensing to use with the unlicensed medium to determine if the unlicensed medium is idle, when the unlicensed medium is determined to be idle, process the multiple PUSCH transmissions during the schedule.
  • LBT listen before talk
  • Example 22 is the apparatus of Example 21, where the uplink grant for multiple physical uplink transmissions is for physical uplink shared channel (PUSCH) transmissions or physical uplink control channel (PUCCH) transmissions.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • Example 23 is the apparatus of Example 1, where the uplink grant indicates if a scheduled subframe transmission is within a maximum channel occupancy time (MCOT) or outside the MCOT.
  • MCOT maximum channel occupancy time
  • Example 24 is a computer program product including a computer-readable storage medium that stores instructions for execution by a processor to perform operations of a user equipment (UE). The operations, when executed by the processor, to perform a method.
  • the method contains processing an uplink grant from an e B, the uplink grant including an interlace allocation assignment schedule for PUSCH transmissions using the unlicensed wireless medium.
  • the method further contains sensing the unlicensed medium to determine if the unlicensed medium is idle at a physical resource block at an interlace allocation assignment, when the unlicensed medium is determined to be idle, generate a PUSCH transmission based at least in part on the schedule.
  • the method further contains sensing the unlicensed medium to determine if the unlicensed medium is idle at a physical resource block at an interlace allocation assignment when the unlicensed medium is determined to be busy, preventing the PUSCH transmission during the schedule.
  • Example 25 is the computer program product of Example 24, where the uplink grant uses resource indication value (RIV) to indicate the interlace allocation.
  • RIV resource indication value
  • Example 26 is the computer program product of Example 24, where the uplink grant for a physical uplink transmission includes a grant for a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • Example 27 is the computer program product of Example 24, where each of the PUSCH transmissions includes a subframe.
  • Example 28 is the computer program product of Example 24, where the uplink grant includes an indicator that the uplink grant is within maximum channel occupancy time (MCOT), allowing the UE to use a shorter listen before talk (LBT) protocol.
  • MCOT maximum channel occupancy time
  • LBT listen before talk
  • Example 29 is the computer program product of Example 28, where the shorter listen before talk (LBT) protocol is a single interval LBT.
  • Example 30 is the computer program product of Example 28, where the shorter listen before talk (LBT) protocol is a short category 4 LBT including puncturing a first symbol of a physical uplink transmission shared channel (PUSCH) transmission.
  • LBT listen before talk
  • Example 31 is the computer program product of Example 24, where the uplink grant includes an indicator that the uplink grant is outside a maximum channel occupancy time (MCOT).
  • MCOT maximum channel occupancy time
  • Example 32 is the computer program product of Example 31, where the uplink grant being outside the MCOT causes the UE to use a category 4 listen before talk (LBT) protocol.
  • LBT listen before talk
  • Example 33 is the computer program product of Example 24, where no listen before talk (LBT) protocol is performed for sequential uplink transmissions after a LBT protocol was performed before a first transmission.
  • LBT listen before talk
  • Example 34 is the computer program product of Example 24, where the uplink grant indicates a type of uplink listen before talk (LBT) protocol.
  • LBT listen before talk
  • Example 35 is the computer program product of Example 24, where the uplink grant indicates that a scheduled transmission scheduled via a cross-transmission opportunity (TxOP) includes an explicit timing relationship between the uplink grant and a physical uplink transmission shared channel (PUSCH) transmission.
  • TxOP cross-transmission opportunity
  • PUSCH physical uplink transmission shared channel
  • Example 36 is the computer program product of Example 24, where the uplink grant uses a field present in a DCI 0 format.
  • Example 37 is the computer program product of Example 24, where the uplink grant indicates resource indication value (RIV), modulation and coding scheme (MCS), hybrid automatic repeat request identifier (HARQ ID), new data indicator ( DI), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross- TxOP) information separately for each subframe.
  • RRIV resource indication value
  • MCS modulation and coding scheme
  • HARQ ID hybrid automatic repeat request identifier
  • DI new data indicator
  • RV redundancy version
  • LBT listen before talk
  • cross- TxOP cross-transmission opportunity
  • Example 38 is the computer program product of Example 24, where the uplink grant indicates modulation and coding scheme (MCS), hybrid automatic repeat request identifier (HARQ ID), new data indicator (NDI), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) separately for each subframe; and where resource indication value (RIV) is fixed for scheduled uplink subframes.
  • MCS modulation and coding scheme
  • HARQ ID hybrid automatic repeat request identifier
  • NDI new data indicator
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 39 is the computer program product of Example 24, where the uplink grant indicates hybrid automatic repeat request identifier (HARQ ID), new data indicator (NDI), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) separately for each subframe; and where resource indication value (RIV), modulation and coding scheme (MCS), and redundancy version (RV) are fixed for scheduled uplink subframes.
  • HARQ ID hybrid automatic repeat request identifier
  • NDI new data indicator
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 40 is the computer program product of Example 24, where the uplink grant indicates hybrid automatic repeat request identifier (HARQ ID), new data indicator (NDI) information separately for each subframe; and where resource indication value (RIV), modulation and coding scheme (MCS), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes.
  • HARQ ID hybrid automatic repeat request identifier
  • NDI new data indicator
  • RV resource indication value
  • MCS modulation and coding scheme
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 41 is the computer program product of Example 24, where the uplink grant indicates new data indicator (NDI) information separately for each subframe, where resource indication value (RIV), modulation and coding scheme (MCS), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes, and where the uplink grant indicates a first hybrid automatic repeat request identifier (HARQ ID) for a first uplink subframe and subsequent HARQ IDs for remaining subframes are implicitly computed.
  • NDI resource indication value
  • MCS modulation and coding scheme
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 42 is the computer program product of Example 24, where the uplink grant indicates redundancy version (RV) and new data indicator (NDI) information separately for each subframe, where resource indication value (RIV), modulation and coding scheme (MCS), listen before talk (LBT) information and cross-transmission opportunity (cross- TxOP) are fixed for scheduled uplink subframes, and where the uplink grant indicates a first hybrid automatic repeat request identifier (HARQ ID) for a first uplink subframe and subsequent HARQ IDs for remaining subframes are implicitly computed.
  • RV redundancy version
  • NDI new data indicator
  • RIV resource indication value
  • MCS modulation and coding scheme
  • LBT listen before talk
  • cross- TxOP cross-transmission opportunity
  • Example 43 is the computer program product of Example 24, where the uplink grant indicates the new data indicator (NDI) information, resource indication value (RIV), modulation and coding scheme (MCS), redundancy version (RV), listen before talk (LBT) information and cross-transmission opportunity (cross-TxOP) are fixed for scheduled uplink subframes, and where the uplink grant indicates a first hybrid automatic repeat request identifier (HARQ ID) for a first uplink subframe and subsequent HARQ IDs for remaining subframes are implicitly computed.
  • NDI new data indicator
  • RMV modulation and coding scheme
  • RV redundancy version
  • LBT listen before talk
  • cross-TxOP cross-transmission opportunity
  • Example 44 is a method for providing an uplink grant with an interlace allocation assignment.
  • the method includes generating an uplink grant from a RAN Node, the uplink grant including an interlace allocation assignment schedule for physical uplink transmission shared channel (PUSCH) transmissions using an unlicensed wireless medium and an indication of a type of listen before talk (LBT) sensing to use with the unlicensed medium to determine if the unlicensed medium is idle when the unlicensed medium is determined to be idle, process a PUSCH transmission during the allocation assignment schedule.
  • PUSCH physical uplink transmission shared channel
  • LBT listen before talk
  • Example 45 is the method of Example 44, where the uplink grant includes a grant for a physical uplink control channel (PUCCH) transmission.
  • PUCCH physical uplink control channel
  • Example 46 is the method of Example 44, where the uplink grant uses resource indication value (RIV) to indicate the interlace allocation assignment.
  • RIV resource indication value
  • Example 47 is the method of Example 46, where the RIV indicates assigned interlaces.
  • Example 48 is the method of Example 46, where the RIV indicates assigned physical resource blocks.
  • Example 49 is the method of Example 46, where the RIV indicates a randomized distance between physical resource blocks while keeping a number of interlaces fixed using a fixed physical resource distance.
  • Example 50 is the method of Example 44, where the interlace allocation assignment is based on inter-physical resource block distance and system bandwidth.
  • Example 51 is the method of Example 50, where the interlace allocation assignment supports 10 interlaces when the system bandwidth is 20 MHz.
  • Example 52 is the method of Example 44, where the uplink grant uses a starting interlace index and a number of interlaces to be assigned to the UE to indicate the interlace allocation assignment.
  • Example 53 is the method of Example 44, where the uplink grant uses a bitmap to indicate the interlace allocation assignment.
  • Example 54 is an apparatus including method to perform a method as exemplified in any of Examples 44-53.
  • Example 55 is a machine-readable storage including machine-readable instructions, when executed, to implement a method or realize an apparatus as exemplified in any of Examples 44-53.
  • Example 56 is a machine readable medium including code, when executed, to cause a machine to perform the method of any one of Examples 44-53.
  • Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
  • a computer system may include one or more general- purpose or special-purpose computers (or other electronic devices).
  • the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
  • Suitable networks for configuration and/or use as described herein include one or more local area networks, wide area networks, metropolitan area networks, and/or Internet or IP networks, such as the World Wide Web, a private Internet, a secure Internet, a value-added network, a virtual private network, an extranet, an intranet, or even stand-alone machines which communicate with other machines by physical transport of media.
  • a suitable network may be formed from parts or entireties of two or more other networks, including networks using disparate hardware and network communication technologies.
  • One suitable network includes a server and one or more clients; other suitable networks may contain other combinations of servers, clients, and/or peer-to-peer nodes, and a given computer system may function both as a client and as a server.
  • Each network includes at least two computers or computer systems, such as the server and/or clients.
  • a computer system may include a workstation, laptop computer, disconnectable mobile computer, server, mainframe, cluster, so-called “network computer” or "thin client,” tablet, smart phone, personal digital assistant or other hand-held computing device, "smart” consumer electronics device or appliance, medical device, or a combination thereof.
  • Suitable networks may include communications or networking software, such as the software available from Novell®, Microsoft®, and other vendors, and may operate using TCP/IP, SPX, IPX, and other protocols over twisted pair, coaxial, or optical fiber cables, telephone lines, radio waves, satellites, microwave relays, modulated AC power lines, physical media transfer, and/or other data transmission "wires" known to those of skill in the art.
  • the network may encompass smaller networks and/or be connectable to other networks through a gateway or similar mechanism.
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD- ROMs, hard drives, magnetic or optical cards, solid-state memory devices, a nontransitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and nonvolatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or other medium for storing electronic data.
  • the e B (or other base station) and UE (or other mobile station) may also include a transceiver component, a counter component, a processing component, and/or a clock component or timer component.
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
  • Each computer system includes one or more processors and/or memory; computer systems may also include various input devices and/or output devices.
  • the processor may include a general purpose device, such as an Intel®, AMD®, or other "off-the-shelf microprocessor.
  • the processor may include a special purpose processing device, such as ASIC, SoC, SiP, FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.
  • the memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, or other computer storage medium.
  • the input device(s) may include a keyboard, mouse, touch screen, light pen, tablet, microphone, sensor, or other hardware with accompanying firmware and/or software.
  • the output device(s) may include a monitor or other display, printer, speech or text synthesizer, switch, signal line, or other hardware with accompanying firmware and/or software.
  • a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, or off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very large scale integration
  • a component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • Components may also be implemented in software for execution by various types of processors.
  • An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function. Nevertheless, the executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.
  • a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within components, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the components may be passive or active, including agents operable to perform desired functions.
  • a software module or component may include any type of computer instruction or computer-executable code located within a memory device.
  • a software module may, for instance, include one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that perform one or more tasks or implement particular data types. It is appreciated that a software module may be implemented in hardware and/or firmware instead of or in addition to software.
  • One or more of the functional modules described herein may be separated into sub-modules and/or combined into a single or smaller number of modules.
  • a particular software module may include disparate instructions stored in different locations of a memory device, different memory devices, or different computers, which together implement the described functionality of the module.
  • a module may include a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices.
  • Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network.
  • software modules may be located in local and/or remote memory storage devices.
  • data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne une conception d'octrois de liaison montante (UL pour UpLink) qui peut consister à planifier des transmissions d'accès assisté sous licence (LAA pour Licensed-Assisted Access) sur la liaison montante à trames multiples. Ces transmissions d'accès LAA sur la liaison montante peuvent comprendre un seul octroi de liaison montante dans une sous-trame pour qu'un équipement utilisateur (UE pour User Equipment) planifie de multiples transmissions de canal partagé de liaison montante physique (PUSCH pour Physical Uplink Shared CHannel) et/ou un seul octroi de liaison montante pour programmer des attributions d'entrelacement. La conception peut comprendre (1) une planification de multiples sous-trames, (2) une indication de LBT de liaison montante et/ou (3) une transmission à grappes multiples à l'aide d'une conception d'accès multiple par répartition en fréquence à entrelacement de blocs (B-IFDMA pour Block Interleaved Frequency Division Multiple Access).
PCT/US2016/050655 2016-04-15 2016-09-08 Systèmes, procédés et dispositifs permettant une transmission d'octroi de liaison montante optimisée pour permettre une planification de multiples sous-trames Ceased WO2017180179A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201680083918.4A CN108886805B (zh) 2016-04-15 2016-09-08 实现多子帧调度的优化上行链路授权传输的系统、方法及设备

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662323102P 2016-04-15 2016-04-15
US62/323,102 2016-04-15

Publications (1)

Publication Number Publication Date
WO2017180179A1 true WO2017180179A1 (fr) 2017-10-19

Family

ID=56940433

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/050655 Ceased WO2017180179A1 (fr) 2016-04-15 2016-09-08 Systèmes, procédés et dispositifs permettant une transmission d'octroi de liaison montante optimisée pour permettre une planification de multiples sous-trames

Country Status (2)

Country Link
CN (1) CN108886805B (fr)
WO (1) WO2017180179A1 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110022609A (zh) * 2018-01-09 2019-07-16 华为技术有限公司 一种通信方法及装置
CN110366248A (zh) * 2018-04-04 2019-10-22 中兴通讯股份有限公司 上行传输、通信方法、装置及基站、终端、存储介质
WO2020088775A1 (fr) * 2018-11-02 2020-05-07 Nokia Technologies Oy Amélioration du fonctionnement de réseaux cellulaires de communication sur des bandes de fréquences non autorisées
WO2020112861A1 (fr) * 2018-11-28 2020-06-04 Qualcomm Incorporated Mappage de ressources de fréquence pour canal physique de contrôle de liaison montante/accusé de réception (pucch/ack) et liaison montante autonome (aul) dans une nouvelle radio sans licence (nr-u)
CN111565460A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种上行传输方法及通信装置
CN111970706A (zh) * 2019-01-18 2020-11-20 Oppo广东移动通信有限公司 用于非授权频谱的无线通信方法和设备
CN112771961A (zh) * 2018-09-27 2021-05-07 瑞典爱立信有限公司 对已配置许可的动态灵活配置
CN114080831A (zh) * 2019-07-16 2022-02-22 高通股份有限公司 剩余信道占用时间指示
CN114175546A (zh) * 2019-08-05 2022-03-11 诺基亚技术有限公司 用于调度未授权nr中的配置的授权的重传的方法
US12089253B2 (en) 2019-02-15 2024-09-10 Apple Inc. System and method for channel occupancy time (COT) sharing in an unlicensed spectrum
US12408196B2 (en) 2020-03-05 2025-09-02 Qualcomm Incorporated Contiguous uplink transmission in contention-based access systems

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11909531B2 (en) * 2019-01-11 2024-02-20 Lg Electronics Inc. Method, user equipment, device, and storage medium for transmitting uplink, and method and base station for receiving uplink
CN111801983B (zh) * 2019-02-03 2022-01-04 Oppo广东移动通信有限公司 信道传输的方法和设备
US20220104259A1 (en) * 2019-02-13 2022-03-31 Apple Inc. Grant based and configured grant based pusch transmissions in an unlicensed spectrum
WO2021128177A1 (fr) * 2019-12-26 2021-07-01 北京小米移动软件有限公司 Procédé et appareil de transmission en liaison montante, dispositif de communication et support de stockage
CN111092634B (zh) * 2019-12-31 2024-04-19 中兴通讯股份有限公司 一种调度方法、装置、设备和存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6309900B2 (ja) * 2012-01-26 2018-04-11 インターデイジタル パテント ホールディングス インコーポレイテッド Ｌｔｅ共存のための動的パラメータ調整
US9743432B2 (en) * 2013-09-23 2017-08-22 Qualcomm Incorporated LTE-U uplink waveform and variable multi-subframe scheduling
US20150103782A1 (en) * 2013-10-14 2015-04-16 Qualcomm Incorporated Techniques for enabling asynchronous communications using unlicensed radio frequency spectrum
WO2015123816A1 (fr) * 2014-02-19 2015-08-27 华为技术有限公司 Procédé de traitement de données après libération de spectre non autorisé, et équipement d'utilisateur
CN105323049A (zh) * 2014-06-13 2016-02-10 中兴通讯股份有限公司 一种非授权载波的调度方法、设备和系统

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On UL Channel Access Procedures for PUSCH", vol. RAN WG1, no. Busan, Korea; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051080566, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160402] *
HUAWEI ET AL: "Scheduling design for eLAA", vol. RAN WG1, no. Busan, Korea; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051079977, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160402] *
INTERDIGITAL COMMUNICATIONS: "On UL data transmission for eLAA", vol. RAN WG1, no. Busan, Korea; 20160411 - 20160415, 1 April 2016 (2016-04-01), XP051079743, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160401] *
LG ELECTRONICS: "Multi-subframe scheduling in LAA", vol. RAN WG1, no. Busan, Korea; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051080204, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160402] *
ZTE: "UL framework for LAA", vol. RAN WG1, no. Anaheim, USA; 20151115 - 20151122, 15 November 2015 (2015-11-15), XP051003305, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20151115] *

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110022609A (zh) * 2018-01-09 2019-07-16 华为技术有限公司 一种通信方法及装置
US11606177B2 (en) 2018-01-09 2023-03-14 Huawei Technologies Co., Ltd. Communication method and communication apparatus
CN110022609B (zh) * 2018-01-09 2023-06-23 华为技术有限公司 一种通信方法及装置
CN110366248B (zh) * 2018-04-04 2024-04-30 中兴通讯股份有限公司 上行传输、通信方法、装置及基站、终端、存储介质
CN110366248A (zh) * 2018-04-04 2019-10-22 中兴通讯股份有限公司 上行传输、通信方法、装置及基站、终端、存储介质
CN112771961A (zh) * 2018-09-27 2021-05-07 瑞典爱立信有限公司 对已配置许可的动态灵活配置
US12022483B2 (en) 2018-09-27 2024-06-25 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic and flexible configurations for configured grants
WO2020088775A1 (fr) * 2018-11-02 2020-05-07 Nokia Technologies Oy Amélioration du fonctionnement de réseaux cellulaires de communication sur des bandes de fréquences non autorisées
US12127250B2 (en) 2018-11-02 2024-10-22 Nokia Technologies Oy Improving operation of cellular communication networks on unlicensed frequency bands
WO2020112861A1 (fr) * 2018-11-28 2020-06-04 Qualcomm Incorporated Mappage de ressources de fréquence pour canal physique de contrôle de liaison montante/accusé de réception (pucch/ack) et liaison montante autonome (aul) dans une nouvelle radio sans licence (nr-u)
US11109366B2 (en) 2018-11-28 2021-08-31 Qualcomm Incorporated Frequency resource mapping for physical uplink control channel/acknowledgement (PUCCH/ACK) and autonomous uplink (AUL) in new radio-unlicensed (NR-U)
US12052718B2 (en) 2018-11-28 2024-07-30 Qualcomm Incorporated Frequency resource mapping for physical uplink control channel/acknowledgement (PUCCH/ACK) and autonomous uplink (AUL) in new radio- unlicensed (NR-U)
CN111970706A (zh) * 2019-01-18 2020-11-20 Oppo广东移动通信有限公司 用于非授权频谱的无线通信方法和设备
US12041653B2 (en) 2019-01-18 2024-07-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for wireless communication on an unlicensed spectrum
CN111565460B (zh) * 2019-02-14 2024-02-02 华为技术有限公司 一种上行传输方法及通信装置
US12009931B2 (en) 2019-02-14 2024-06-11 Huawei Technologies Co., Ltd. Uplink transmission method and communications apparatus
CN111565460A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种上行传输方法及通信装置
US12089253B2 (en) 2019-02-15 2024-09-10 Apple Inc. System and method for channel occupancy time (COT) sharing in an unlicensed spectrum
CN114080831B (zh) * 2019-07-16 2024-03-01 高通股份有限公司 剩余信道占用时间指示
CN114080831A (zh) * 2019-07-16 2022-02-22 高通股份有限公司 剩余信道占用时间指示
CN114175546A (zh) * 2019-08-05 2022-03-11 诺基亚技术有限公司 用于调度未授权nr中的配置的授权的重传的方法
US12408196B2 (en) 2020-03-05 2025-09-02 Qualcomm Incorporated Contiguous uplink transmission in contention-based access systems

Also Published As

Publication number Publication date
CN108886805A (zh) 2018-11-23
CN108886805B (zh) 2022-09-16

Similar Documents

Publication Publication Date Title
CN108886805B (zh) 实现多子帧调度的优化上行链路授权传输的系统、方法及设备
US11937302B2 (en) Devices and methods for ELAA multi-carrier LBT
US10849140B2 (en) Systems, methods and devices for radio access technology coordination
CN114070540B (zh) 用于非授权上行链路和所调度的传输的共存的方法、装置和存储介质
EP3873164B1 (fr) Conception d&#39;écoute avant transmission (lbt) pour fonctionnement par accès assisté sous licence en liaison montante (laa) dans une bande sans licence
US11064521B2 (en) Scheduling uplink transmissions for a user equipment (UE)
US10827525B2 (en) Systems, methods and devices for sharing a wireless medium using listen before talk
US10390236B2 (en) Systems, methods and devices for uplink transmissions with reduced signaling overhead
US11317398B2 (en) Semi-persistent scheduling for autonomous transmission activation and release
US20180227958A1 (en) Performing mission critical communications at a user equipment (ue)
US11368981B2 (en) Low latency physical random access channel design
WO2017099860A1 (fr) Dispositif pour une émission en liaison montante non planifiée dans le spectre non autorisé
US11102802B2 (en) Cross transmission opportunity (TxOP) scheduling
WO2017189034A1 (fr) Systèmes, procédés et dispositifs pour l&#39;amélioration d&#39;informations de commande de liaison montante
EP3498047B1 (fr) Multiples entités mac par équipement d&#39;utilisateur
HK1262518A1 (en) Systems, methods and devices for optimized uplink grant transmission to enable multi-subframe scheduling
HK1262504B (zh) 用於非授权上行链路和所调度的传输的共存的装置
HK1262504A1 (en) Apparatuses for co-existence of grantless uplink and scheduled transmissions

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16766781

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16766781

Country of ref document: EP

Kind code of ref document: A1