WO2018031638A1 - Uplink transmission request for multiple numerologies - Google Patents

Uplink transmission request for multiple numerologies Download PDF

Info

Publication number
WO2018031638A1
WO2018031638A1 PCT/US2017/046075 US2017046075W WO2018031638A1 WO 2018031638 A1 WO2018031638 A1 WO 2018031638A1 US 2017046075 W US2017046075 W US 2017046075W WO 2018031638 A1 WO2018031638 A1 WO 2018031638A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
periodicity
transmission
uplink
numerology
Prior art date
Application number
PCT/US2017/046075
Other languages
French (fr)
Inventor
Ralf Matthias Bendlin
Joonyoung Cho
Hong He
Hwan-Joon Kwon
Gang Xiong
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201662373482P priority Critical
Priority to US62/373,482 priority
Priority to US201662402865P priority
Priority to US62/402,865 priority
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018031638A1 publication Critical patent/WO2018031638A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/12Dynamic Wireless traffic scheduling ; Dynamically scheduled allocation on shared channel
    • H04W72/1278Transmission of control information for scheduling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00Modulated-carrier systems
    • H04L27/26Systems using multi-frequency codes
    • H04L27/2601Multicarrier modulation systems
    • H04L27/2602Signal structure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/0064Rate requirement of the data, e.g. scalable bandwidth, data priority
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • H04L5/0094Indication of how sub-channels of the path are allocated

Abstract

Methods, apparatus, and computer-readable media are described to encode a first scheduling request (SR) for a first resource for transmission on a first physical uplink control channel (PUCCH) resource dedicated for the first resource. A periodicity of transmission of a SR for the first resource has a first periodicity. The first SR comprising a first quality of service (QoS) attribute. A second SR is encoded for a second resource for transmission on a second PUCCH resource dedicated for the second resource. A periodicity of transmission of a SR for the second resource has a second periodicity. The second SR comprising a second QoS attribute. A first uplink grant is decoded. The first link uplink grant includes a first allocated uplink resource based upon the first QoS attribute. A second uplink grant is decoded. The second link uplink grant includes a second allocated uplink resource based upon the second QoS attribute.

Description

PRIORITY CLAIM

[0001] This application claims priority to United States Provisional Patent Application Serial No. 62/373,482 filed August 1 1, 2016, entitled

"MECHANISMS TO REQUEST UPLINK TRANSMISSION FOR MULTIPLE NUMEROLOGIES IN NR" and to United States Provisional Patent

Application Serial No. 62/402,865 filed September 30, 2106, entitled

"REQUESTING UPLINK TRANSMISSION FOR MULTIPLE

NUMEROLOGIES IN R." both of which are incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

[0002] Various embodiments generally may relate to the field of wireless communications.

BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. The nel2 generation wireless communication system, fifth generation (5G), will provide access to information and sharing of data anywhere, anytime by various users and applications. 5G is expected to be a unified network/system that is targeted to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different sendees and applications. In general, 5G will evolve based on 3GPP Long-Term Evolution (LTE) Advanced with additional potential technologies to enrich people lives with better, simpler and seamless wireless connectivity solutions. 5G is expected to deliver fast, rich contents and services. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

[0005] FIG, 1 illustrates a design framework for a new radio (NR) flexible radio access technologies (RAT) according to some embodiments described herein.

[0006] FIG. 2 is a message diagram of a process for uplink data transmission in the legacy LIE specification.

[0007] FIG. 3 illustrates independent SR resources using different numerologies according to some embodiments described herein.

[0008] FIG. 4 illustrates an example of a TDD slot configuration comprising twelve downlink symbols followed by an uplink symbol separated by a guard interval according to some embodiments described herein.

[0009] FIG. 5 illustrates a frame structure with switching gaps for receiving an SR using a second numerology according to some embodiments described herein.

[0010] FIG. 6 illustrates multiple SR resources which are configured for uplink transmission request using one numerology according to some embodiments described herein.

[0011] FIG. 7 illustrates one example of an uplink data transmission procedure for multiple numerologies according to some embodiments described herein.

[0012] FIG. 8 illustrates an example of an uplink data transmission procedure for multiple numerologies according to some embodiments described herein.

[0013] FIG. 9 illustrates a PRACH preamble signature partition for uplink transmission request for multiple numerologies according to some embodiments described herein.

[0014] FIG. 10 illustrates different periodicities of SR resources targeting for services with different QoS requirements according to some embodiments described herein.

[0015] FIG. 11 illustrates an architecture of a system 1100 of a network in accordance with some embodiments.

[0016] FIG. 12 illustrates example components of a device 1200 in accordance with some embodiments. [0017] FIG. 13 illustrates example interfaces of baseband circuitry in accordance with some embodiments

[0018] FIG. 14 is an illustration of a control plane protocol stack in accordance with some embodiments.

[0019] FIG. 15 is an illustration of a user plane protocol stack in accordance with some embodiments.

[0020] FIG. 16 illustrates components of a core network in accordance with some embodiments.

[0021] FIG. 17 is a block diagram illustrating components, according to some example embodiments, of a system 1700 to support NFV.

[0022] FIG. 18 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 non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0023] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments.

However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with

unnecessary detail.

[0024] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. DESCRIPTION

[0025] In various examples described below, a unified framework is defined by a new radio (NR.) flexible radio access technologies (RAT) that provides support for the diverse requirements, applications, services, multiple frequency bands, licensed and unlicensed frequency and multiple partitions that may be used to support various 5G features. FIG. 1 illustrates a design framework for a new radio (NR.) flexible radio access technologies (RAT) according to some embodiments described herein. As shown in FIG. 1 , multiple partitions or applications in different or same frequency resource or frequency bands can be multiplexed in either time-division multiplexing (TDM), frequency-division multiplexing (FDM), code-division multiplexing (CDM) manner or a combination of the above. Further, different partitions may employ different subcarrier spacings, which can be tailored for different applications and use cases.

[0026] For example, the frequency spectrum may be divided in a mid/high band 110 and a low band 112. The frequency may be broken into various transmission time intervals (TTI). In an example, a band of frequency may support a short TTI partition 104, a normal TTI partition 102, and a long TTI partition 106. The different TTI partitions provide support for various applications/services that have different needs. For example, the short TTI partition 104 may be used to support mission critical machine-type

communications (MTC). The long TTI partition 102 allows MTC that need coverage enhancement. The normal TTI partition 106 may be used to support mobile broadband. Applications 120, 122, 124, and 126 may reserve various TTI. In FIG. 1, the applications 120 and 122 reserve TTIs that are FDM. While Applications 120, 124, and 126 reserve a TTI at the same frequency but TDM.

[0027] When multiple numerologies coexist within the system bandwidth, an evolved NodeB (gNB) or a new radio enhanced node (gNB) may operate the system using a base numerology. In the case where a user equipment (UE) supports multiple numerologies, the UE may request the uplink

transmission for a certain application. For example, the UE may request an uplink transmission for a low latency application, which may use a numerology which is different from the base numerology. Hence, certain mechanisms to request the uplink transmission using a different numerology from the base numerology may be desirable. Embodiments herein relate to mechanisms to request uplink transmission for multiple numerologies.

[0028] FIG. 2 is a message diagram of a process for uplink data transmission in the legacy LTE specification. When a UE 202 intends to transmit data in the uplink, the UE 202 will request the resource using a physical uplink control channel (PUCCH) format 1 for scheduling request (SR) 210. After successful detection of SR, an gNB 204 transmits on a physical downlink control channel (PDCCH) downlink control information (DO) containing an uplink grant to allocate the uplink resource 212. Subsequently, the UE sends a buffer status report (BSR) on a physical uplink shared channel (PUSCH) in the allocated uplink resource 214. The BSR MAC control element (CE) may be carried in a Medium Access Control (MAC) Protocol Data Unit (PDU), which is used to inform the gNB 204 on the amount of the data in UE's buffer for one specific Logical Channel Group (LCG) to be transmitted. Based on the BSR information, the gNB 204 allocates the appropriate resource and the modulation and coding scheme (MCS) which is included in a second uplink grant 216. After receiving the uplink grant, the 202 UE transmits the uplink data on the PUSCH 218.

[0029] According to LTE specifications, UEs support all the channel bandwidths of 1.4/3/5/10/15/20 MHz. This support enables gNBs to transmit

PDCCH and Physical Hybrid-ARQ Indicator Channel (PHICH) across the whole channel bandwidth without determining if each UE is capable of receiving the data. The Primary Synchronisation Signal (PSS), the Secondary Synchronisation Signal (SSS), and the Physical Broadcast Channel (PBCH) are designed so that the same structure applies to all the above bandwidths and the UEs can perform an initial cell search without knowledge of the network channel bandwidth.

[0030] On the other hand, the supported LTE bands and the combination of carrier aggregation (CA) bands are defined as UE capability parameters. These parameters are radio frequency (RF) related and do not impact the physical layer specifications. These RF parameters were introduced when the LTE network was about to be deployed. The LTE UE category was introduced and defined various parameters such as transport block bits, soft channel bits and number of spatial layers for downlink (DL) and uplink (UL), respectively. With introduction of advanced features such as carrier aggregation, 256 QAM, MTC and NB loT in a later phase, additional UE categories have been added, e.g., Cat 6 for CA, Cat 11 for 256-QAM, Cat Ml for MTC and Cat NB l for NB loT.

[0031] NR. numerology parameters such as subcarrier spacing, slot duration, symbol durations are related with physical layer design, and may impact baseband implementations. The Physical layer may be designed and specified taking into account mandatory and optional features which are fully or optionally supported by NR. UEs. For example, if UEs are to support a set of subcarrier spacing, an initial synchronization signal can be designed taking into account the mandator}' set of subcarrier spacing. In cases that numerology support becomes an optional feature from a UE perspective and each UE is allowed to selectively implement a preferred subcarrier spacing, initial synchronization signal design may require logic for the UE to find and decode the initial synchronization signal. In addition, transmission and reception of data may be scheduled in the slots of the corresponding subcarrier spacing,

[0032] The following embodiments may be considered for UE capability on supported subcarrier spacing. Various embodiments focus on enhanced Mobile Broadband (eMBB) targeting UEs only. These embodiments may not consider different numerology capability depending on target services. In one embodiments, there is no mandator}' subcarrier spacing and each UE may choose a subcarrier spacing to implement. This embodiment may make the physical layer design and scheduling operations to accommodate UEs of different subcarrier spacing complicated. The added complexity, however, may be implemented and supported by various gNBs,

[0033] In another embodiment, a UE may implement an agreed set of subcarrier spacing. The agreed set of subcarrier spacing that each UE supports may depend on the UE category or may be a set that applies to all UEs and is independent of the UE category. In another approach, an agree set of subcarrier spacing may vary as a function of carrier frequency band. For example, 15 kHz or 30 kHz subcarrier spacing would be preferred in carrier frequency bands below 6 GHz. On the other hand, subcarrier spacing much larger than 15 kHz would be desirable and preferred in above 6 GHz and mid-tens GHz bands. As such, an agreed set of supported subcarrier spacing can be defined in accordance to the frequency bands which the respective UEs aim to support. In this case, the agreed set of subcarrier spacing is identical among the UEs on the carrier frequency the network operates.

[0034] Having no agreed upon subcarrier spacing may have less implementation burden, low cost, flexibility to tailor the implementation and design for the target services and deployments from the perspective of the UE, Defining, however, some basic numerology set would make clear the features each UE should support and would reduce potential inefficiency due to market fragmentation. The partially mandatory approach would be favored on network sides since the network implementation would be reduced. This is because a base set of numerologies are defined and guaranteed to be mandatorily supported by all the UEs. Then, the networks can operate time-frequency resource by utilizing the base set of numerologies, as all the UEs mandatorily support them . For the UEs which are capable to support additional numerologies, the network can schedule those UEs on the resources configured with the corresponding numerologies whenever necessary (service application, operation scenario, etc.). In an example, each service verticals (eMBB, Ultra Reliable and Low Latency Communications (uRLLC), Massive Machine-Type Communications (mMTC)) may define a different set of numerologies for mandatory implementations in the UEs, Also, each physical channel and signal may require support of another set of numerologies.

[0035] Typical subcarrier spacing values such as 15 kHz and multiples of

15 kHz may take higher priority than other subcarrier spacing and be taken as a baseline for physical layer design. For the selected subcarrier spacing values, corresponding time intervals, frame structure and physical layer procedures can be designed. Then how to configure and operate time-frequency resource is up to the network, as done in LTE TDD and FDD. Some numerologies may be decided as UE optional features. Among physical layer design issues, whether to define a mandatory numerology set may impact significantly the design of initial synchronization signals. This is because R UEs cannot be aware of which subcarrier spacing is applied in target NR networks when starting initial access procedure. Also, NR UEs experience more uncertainties during initial access than LTE UEs such as subcarrier spacing, beam directions for TRP Tx and UE Rx in cases with beamforming, and potentially more cells IDs than LTE 504 IDs, [0036] In an example, scheduling requests (SR) may be used to request resources for uplink transmission with different type of services. Each service may be associated with different Quality of Service (QoS) requirements, which may include delay sensitive or delay tolerant services. In an example, service with delay sensitive characteristic may use a first numerology, e.g., larger subcarrier spacing including 60kHz subcarrier spacing while service with delay tolerant characteristic may use a second numerology, e.g., reference subcarrier spacing with 15kHz subcarrier spacing. Thus, each service may be provided with resources that match the requirements or needs of the service.

[0037] In another option, services with different QoS requirements may employ a same numerology, e.g., 15kHz subcarrier spacing. However, service with delay sensitive characteristic may use a small number of symbols or a mini- slot for data transmission while service with delay tolerant characteristic may use regular slot or slot for data transmission.

[0038] For both options, the SR may be used to indicate which types of services the UE intends to request. As a further e'12ension, services with multiple QoS requirements may be defmed. In this case, an SR with separate resources may be defined to request resource for services with different QoS requirements. Alternatively, an enhanced SR may be specified to carry more information bits in the R physical uplink control channel (PUCCH). One example of a sen/ice ID for an enhanced SR is shown in Table 0. Each QoS requirement from Table 0 may correspond with a type of service. The type of service may then be mapped to corresponding subcarrier spacing and/or other QoS parameters.

Table Θ: Service ID for enha ced SR

Figure imgf000010_0001

[0039] When multiple numerologies coexist within the system bandwidth, a gNB may operate the system using a base numerology. In the case when the UE supports multiple numerologies, the UE may request the uplink transmission for a certain application, e.g., low latency application, which may use a numerology which is different from the base numerology. Hence, certain mechanisms are needed to request the uplink transmission using a different numerology from the base numerology. Such a request for an uplink transmission using a different numerology from the base numerology may be implicit or explicit. In the former case, the UE may request uplink resources for a specific

service/application/vertical which the gNB implicitly maps to a different numerology, For example, a first numerology may be associated with a mobile broadband application whereas a second numerology may be associated with an ultra-reliable low-latency application. A UE may signal the specific numerology or a group of possible numerologies. Alternatively, the UE may request resources for a particular type of application. The gNB may map the type of application to appropriate resources that provides adequate resources for the requested application.

[0040] In various embodiments, resources of different numerologies may be requested from an gNB by using SR. resources or Physical Random Access Channel (PRACH) resources or both. The UE may semi-statically receive a high layer message from the gNB, that includes a first information element (IE) to assign a first SR resource for requesting resource of first numerology and/or a second IE to assign a second SR resource for requesting resource of a second numerology. Both the first and second numerologies are supported by UE and may be indicated as part of UE capability.

[0041] The SR resource may be a PUCCH format resource according to a NR or a 5G system. In addition, the first or second IE may include an indication of time, resource index, and/or periodicity, numerology (e.g. subcarrier spacing) for each SR assignment or any subset thereof. In addition, the SR resource for each numerology may be valid for a limited time e.g., when the corresponding numerology is activated at UE side. The limited time may be specified to a fixed value. In some designs, the limited time is configured using a radio resource control (RRC) for each numerology.

[0042] In an example, a scheduling request resource may be configured separately for each of the numerologies or services/applications in a UE specific manner via dedicated radio resource control (RRC) signaling. In this case, the UE may transmit the SR using one numerology to request an uplink transmission for the same numerology or one associated numerology which may be configured by higher layers.

[0043] FIG. 3 illustrates one example of independent SR resource using different numerologies. A primary partition 302 using a first numerology and a secondary partition 304 using a second numerology are multiplexed in a frequency division multiplexing (FDM) manner. Further, SR resources may be independently configured for primary and secondary partitions, respectively, using the corresponding numerology. When the UE requests the uplink, transmission using a first numerology, the UE may transmit the SR 310 on the resource using the first numerology. Similarly, when the UE requests the uplink transmission using a second numerology, the UE may transmit the SR 312 on the resource using the second numerology. In case of resource overlapping in time domain, the UE may select one of the SR resources following a predefined priority rule. The priority rule may depend on the latency requirement of associated numerology.

[0044] In some examples, a new PUCCH format may be used to convey a numerology ID. The numerology ID (NID) field may be used to indicate the numerology ID, which is used to identify the requested numerology that is being scheduled. One example of a NID is shown in Table 1 . The shown NID includes a 2-bit NID field. This design provides more flexibility for SR resource allocation. For example, it is possible that only one SR resource is allocated using a basic numerology (e.g. 15 kHz carrier spacing) and still allow the UE to timely request different numerologies resources by using the different 2-bit NID values.

Figure imgf000012_0001

Numerology ID (NID) Numerology

conveyed in PUCCH

format

00 A first numerology configured by higher layers

01 A second numerology configured by higher layers

10 A third numerology configured by higher layers

1 1 A fourth numerology configured by higher layers [0045] If the gNB supports receiving multiple numerologies at the same time, the gNB may receive transmissions using a first numerology while

simultaneously receiving scheduling requests using a second numerology as depicted in Figure 3. If, however, the gNB does not support receiving multiple numerologies at the same time, the gNB receiver may switch numerologies. If the two numerologies are not symbol boundary aligned, this may result in some undefined samples between symbols of the different numerologies. For example, after receiving a symbol of a first numerology, the gNB receiver may have to wait for a period of time that is shorter than the symbol duration of either numerology until the start of a symbol of a second numerology. Conversely, after receiving a symbol of a second numerology, the gNB receiver may have to wait for a period of time that is shorter than the symbol duration of either numerology until the start of a symbol of a first numerology.

[0046] Moreover, if the gNB does not support full duplex, the gNB cannot receive a SR using a second numerology if the gNB is transmitting using a first numerology at the same time. FIG. 4 illustrates an example of a TDD slot configuration comprising twelve downlink symbols 402 followed by an uplink symbol separated by a guard interval 404. A second scheduling request may be received on a second numerology using the PUCCH 406. As mentioned above, the timing between the first numerology and second numerology may not be aligned , such that the gNB may need to wait a timing advance period of time 408 before receiving the SR that uses the second numerology.

[0047] For an gNB to receive SRs using a second numerology during an ongoing downlink transmission of a first numerology, additional switching gaps may be included in the frame stmcture as depicted in FIG 5. In this example, the gNB monitors for scheduling requests using a first numerology during uplink control regions of a first numerology 502 and monitors for scheduling requests using a second numerology during uplink control regions of a second

numerology 504. A receiver of the on-going downlink transmission 506 of the first numerology may or may not be aware of the additional switching guards 508 and uplink control regions of the second numerology 504. Receiving the downlink transmission 506 may include puncturing the on-going downlink transmission of the first numerology. Additional protection, however, may be provided to allow such a receiver to recover from the aforementioned puncturing.

[0048] In another embodiment, multiple SR resources using a first numerology may be configured in a UE specific manner via dedicated radio resource control (RRC) signaling. Each SR resource may correspond to an uplink transmission request to use a numerology or service/application linked to the SR resource. This cross-numerology uplink scheduling request mechanisms may be desirable when an gNB operates using a base numerology, while other numerologies are triggered or scheduled in a dynamic manner.

[0049] FIG. 6 illustrates one example of multiple SR resources which are configured for uplink transmission request using one numerology. Two SR resources 602 and 604, both using a first numerology, (e.g., a base numerology) are configured for one UE. In particular, one SR resource corresponds to an uplink transmission request for a first numerology or service/application 602 and the other SR 604 is used to request resources for a second numerology or service/application, respectively.

[0050] FIG. 7 illustrates one example of an uplink data transmission procedure for multiple numerologies or services/applications. At 712, an UE 702 may transmit a SR on a particular SR resource which is configured to request resource on a second numerology or service/application. The SR transmission itself is still based on a first numerology. At 714, an gNB 704 sends an UL grant scheduling the uplink transmission for the UE on UL resource using the second numerolog or service/application. At 716, a buffer status report (BSR) is sent by the UE 702 to the gNB 704 using the second numerology. At 718, the gNB 704 sends an UL grant to the UE 702 using the second numerology. The second UL grant is based upon the received buffer status report. At 718, the UE 702 provides data to the gNB 704 using the second numerology.

[0051] In another embodiment, a new Logical Channel ID in the Medium Access Control (MAC) layer may be defined to request the uplink transmission for different or services/applications or using different numerologies. Further, a corresponding MAC control element which may include the indicator for the uplink transmission request using one numerology. For instance, bit "00" may be used to indicate the uplink transmission request using a first numerology, or base numerology. Bit "01." may be used to indicate the uplink transmission request using a second numerology, etc.

[0052] This MAC control element may be transmitted in Msg3 in the RACH procedure or transmitted together with buffer status report (BSR) for uplink data transmission triggered by SR.

[0053] FIG. 8 illustrates another example of uplink data transmission procedure for multiple numerologies. In this example, one SR. resource is configured for all numerologies. At 810, a SR is transmitted from a UE 802 using a first numerology. At 812, in response to receiving the SR an g B 804 responds with a UL grant using the first numerology. After receiving the UL grant, the UE 802 may request to use a second numerology for the UE's data transmission. At 814, the UE 802 may transmit the MAC CE including uplink transmission request for a second numerology together with a BSR. At 816, the gNB 804 may schedule the uplink transmission using the second numerology. At 818, the UE 802 transmits its data to the gNB 804 using the second numerology.

[0054] In one embodiment, a 5G physical random access channel (PRACH) using different numerologies may be configured for the uplink transmission request for the corresponding numerology. In this case, the UE may transmit the PRACH using one numerology to request the uplink transmission for the corresponding numerology. Numerology used for PRACH may be different from that used for the uplink transmission. A one-to-one association may be defined to link the numerology used for PRACH and uplink transmission.

[0055] In one embodiment, a single numerology (e.g., a first numerology) is applied for PRACH transmission. Further, dedicated resource can be allocated for PRACH to request the uplink transmission using different numerologies. Upon successful detection of PRACH on the dedicated resource

(time/frequency/PRACH sequence/preamble), the gNB may allocate the resource for uplink transmission using the requested numerology.

[0056] PRACH resource for different numerologies may be multiplexed in a time division multiplexing (TDM), frequency division multiplexing (FDM) and/or code division multiplexing (CDM) manner or a combination thereof. The resource partition may be predefined or configured by higher layers via NR master information block (xMIB), NR system information block (11IB) or radio resource control (RRC) signaling. One or a plurality of signature sequences can be reserved for PRACH for uplink transmission request for one numerology. FIG. 9 illustrates one example of PRACH preamble signature partition for uplink transmission request for multiple numerologies. For example, the PRACH preamble may be divided into three resources 902, 904, and 906. Each resource may be reserved for a particular numerology. For example, the resource 902 may be reserved for a first numerology, the resource 904 may be reserved for a second numerology, and the resource 906 may be reserved for a third numerology.

[0057] In an embodiment, one or a plurality of frequency resources can be allocated for PRACH for uplink transmission request for one numerology. In an embodiment, one or a plurality of time resources can be allocated for PRACH for uplink transmission request for one numerology. For instance, PRACH for uplink transmission request for a first numerology can be transmitted in one or a multiple of slots 0, 2, 4, 6, 8 within one frame while PRACH used to request the uplink transmission scheme for a second numerology can be transmitted in one or a multiple of slots 1, 3, 5, 7, 9. In addition, a combination of TDM and/or FDM and/or CDM based multiplexed schemes can be used to separate the PRACH resources for uplink transmission request for different numerologies.

[0058] As described above, a scheduling request (SR) may be used to request resources for uplink data transmission. In LTE, the SR employs a simple on/off mechanism, where the information i s conveyed by the presence of energy on the corresponding PUCCH resource. If the UE does not request the uplink resource, the UE transmits nothing on the configured PUCCH resource.

[0059] To multiplex SRs for multiple UEs in the same resource, SR design for NR may be similar to LTE, e.g., using an on/off mechanism so as to allow gNB to perform a simple energy detector for SR detection. For long PUCCH, the SR based on on-off-keying modulation scheme may be supported for NR. Further, for short PUCCH, a length- 12 CAZAC sequence is applied on even or odd subcarriers within two PRBs employing OOK for the transmission of SR.

[0060] In addition, a SR may be combined with other Uplink Control

Information (UCI) feedbacks in NR PUCCH including a Channel State

Information (CSI) report and Hybrid ARQ (HARQ) ACK/N ACK feedback. In an embodiment, one bit information with positive or negative SR may be explicitly included in a NR PUCCH. [0061] With regard to SR resource allocation, several options can he considered for a NR. One option is a semi-static SR resource allocation. A SR resource can be semi-statically configured by higher layers to allow periodic opportunities for a UE to request resource for uplink transmission. Another option allows dynamic SR resource allocation. A SR resource may be dynamically indicated via a DCI in a UE specific or group/cell specific manner. In addition, a hybrid mode for SR resource allocation may be implemented. This option may be viewed as a combination of semi-static and dynamic resource allocation for SR. In particular, certain mechanism to activate and deactivate periodic SR resource via LI or L2 control signaling may be implemented for NR. This may help to ensure better forward compatibility and more efficient support of a dynamic TDD system. Periodic NR PUCCH resource may be released to reduce the overhead and thereby improve system level spectrum efficiency and may be configured or activated on an as needed basis, especially when considering symbol level configuration of SR resource for URLLC applications.

[0062] While allocating SR resource in a semi-static manner may be considered for a FDD sy stem or a TDD system with semi-static DL/UL configuration, SR resource allocation using dynamic or hybrid mode may be more desirable in the support of dynamic TDD system. In a dynamic TDD system, periodic NR PUCCH resource may not be needed.

[0063] For NR, SR may encode QoS attributes related to reliability target, latency budget or information on packet size. This information may be needed to properly handle SR request at the gNB side and process it accordingly . For instance, the UE may have traffic that requires ultra-reliable low latency communication (URLLC) or only low latency communication (LLC) without strict reliability targets.

[0064] To allow gNB to identify services with different QoS requirements requested from UE, the UE may be configured with multiple dedicated PUCCH resources for SR. The resource may be mapped to priority or numerology/TTI of the logical channel (LCH) that triggered the SR.

[0065] FIG. 10 illustrates different periodicities of SR resources targeting for services with different QoS requirements according to some embodiments described herein. For low latency application, e.g., URLLC, dedicated SR resource with shorter periodicity may be confi gured. The periodicity of the SR resource having a periodicity that is less than a slot periodicity is shown in graph 1000. This indicates that for U LLC service, the UE may be configured with dedicated SR resource with symbol level periodicity 1002 in order to meet stringent latency requirement. For eMBB, however, SR resource can be configured with slot level periodicity 1012. In this configuration, the periodicity of the SR resource may have a periodicity that is equal to a slot periodicity is shown in graph 1010. To support another QoS requirement, the SR resource periodicity may be longer than a slot periodicity.

[0066] As described above, multiple SR resources may be multiplexed in a TDM manner. However, for a given time instance, multiple SR resources may be multiplexed in a FDM or CDM manner. For instance, distinct frequency resources or cyclic shift values may be configured for different SRs. For the support of wide system bandwidth, multiple bandwidth parts may be configured for a given UE, where each bandwidth part is associated with one numerology. In the case when PUCCH carrying SR is configured within different bandwidth parts, different numeroiogies may be employed for the transmission of SR.

[0067] As noted above, for a given time instance, multiple SR resources may fully or partially overlap in time. For example, when the UE intends to transmit data for both eMBB and URLLC, UE may need to send multiple PUCCHs carrying SR simultaneously. Distributed transmission may introduce inter- modulation distortion (IMD) or increase PAPR, which may degrade the performance for the UL control channel. Further, when different numeroiogies are configured for multiple SR resources, the UE may not be able to send multiple PUCCHs carrying SRs simultaneously if UE does not support FDM of different numeroiogies within the system bandwidth. In the case when the UE intends to request the resource for uplink data transmission for different services/applications, and if resources for multiple SR configurations overlap in time, the UE may only transmit one SR while delaying the other SR

transmission. In particular, the delaying rule may be defined according to the priority of services or numerology/periodicity configured for the SR. For instance, the UE could transmit the SR triggered by logical channel

corresponding to a higher priority, e.g., URLLC application while delaying the SR for the logical channel with a lower priority, e.g., eMBB. The UE, therefore, would not be expected to transmit multiple SRs for a given time instance, which can help to simplify UE implementation.

[0068] In LTE, when a UE intends to transmit the data in the uplink, the UE requests the resource using PUCCH format 1 for a SR. After successful detection of the SR, a gNB transmits a DCI via PDCCH containing uplink grant to allocate the uplink resource. Subsequently, the UE sends a BSR on PUSCH in the allocated resource, which is used to inform the gNB on the amount of data in the UE's buffer to be transmitted. Based on the BSR information, the gNB allocates appropriate resources and the modulation and coding scheme (MCS) in the uplink grant for the UE to transmit the uplink data on PUSCH.

[0069] For NR, a similar mechanism may apply for UL data scheduling. A mapping between logical channel group (LCG) and SR configuration can be defined so as to allow gNB to differentiate SR associated with a given service and properly handle it.

[0070] After successful detection of a SR on a dedicated resource for low latency application, a gNB may allocate resources for a BSR and uplink data transmission with appropriate numerology or TTI, e.g., using a larger subcarrier spacing or same numerology with shorter TTI, to provide low latency service. After receiving the UL grant, the UE may transmit the data from logical channels which are allowed to use the TTI/numerology.

[0071] FIG. 11 illustrates an architecture of a system 1100 of a network in accordance with some embodiments. The system 1100 is shown to include a user equipment (UE) 1 101 and a UE 1 102, The UEs 1101 and 1 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[0072] In some embodiments, any of the UEs 1101 and 1 102 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity- Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

[0073] The UEs 1101 and 1 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1110— the RAN 1 1 10 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Ne'12Gen RAN (NG RAN), or some other type of RAN. The UEs 1 101 and 1102 utilize connections 1 03 and 1104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 1 03 and 1104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular

communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR.) protocol, and the like.

[0074] In this embodiment, the UEs 1101 and 1 102 may further directly exchange communication data via a ProSe interface 1 05. The ProSe interface 1 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0075] The UE 1 102 is shown to be configured to access an access point

(AP) 1 106 via connection 1 107. The connection 1107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1106 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 1 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0076] The RAN 1 1 10 can include one or more access nodes that enable the connections 103 and 1104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (gNBs), nel2 Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 1 1 10 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1 1 11, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1112.

[0077] Any of the RAN nodes 1 11 and 1112 can terminate the air interface protocol and can be the first point of contact for the UEs 1 101 and 102. In some embodiments, any of the RAN nodes 111 1 and 1112 can fulfill various logical functions for the RAN 1110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0078] In accordance with some embodiments, the UEs 1101 and 1 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1 1 1 1 and 1112 over a multi carrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications ), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0079] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1 1 1 1 and 1112 to the UEs 1 101 and 1102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0080] The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs 1 101 and 1102. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 1101 and 1 02 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 1 1 1 1 and 1112 based on channel quality information fed back from any of the UEs 1101 and 1102. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 1101 and 1102.

[0081] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interieaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l , 2, 4, or 8).

[0082] Some embodiments may use concepts for resource allocation for control channel information that are an el2ension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[0083] The RAN 1 1 10 is shown to be communicatively coupled to a core network (CN) 1 120— -via an SI interface 1113. In embodiments, the CN 1120 may be an evolved packet core (EPC) network, a Nel2Gen Packet Core (NPC) network, or some other type of CN. In this embodiment the S I interface 1 113 is split into two parts: the Sl-U interface 11 14, which carries traffic data between the RAN nodes 111 1 and 1 112 and the serving gateway (S-GW) 1 122, and the SI -mobility management entity (MME) interface 11 15, which is a signaling interface between the RAN nodes 11 1 1 and 1112 and MMEs 1 121 .

[0084] In this embodiment, the CN 1120 comprises the MMEs 1121, the

S-GW 1 122, the Packet Data Network (PDN) Gateway (P-GW) 1123, and a home subscriber server (HSS) 1124. The MMEs 1121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS ) Support Nodes (SGSN). The MMEs 1 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 1124 may comprise a database for network users, including

subscription-related information to support the network entities' handling of communication sessions. The CN 1 120 may comprise one or several HSSs 1 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 1 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0085] The S-GW 1122 may terminate the SI interface 11 13 towards the

RAN 1110, and routes data packets between the RAN 1 1 10 and the CN 1 120. In addition, the S-GW 1122 may he a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0086] The P-GW 1 23 may terminate an SGi interface toward a PDN.

The P-GW 1123 may route data packets between the EPC network 1123 and el2ernal networks such as a network including the application server 1130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 1125. Generally, the application server 1 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 1123 is shown to be communicatively coupled to an application server 1130 via an IP communications interface 1125. The application server 1 130 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1 101 and 102 via the CN 1 120,

[0087] The P-GW 1123 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 126 is the policy and charging control element of the CN 1 20. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol

Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's ΪΡ- CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 1 126 may be communicatively coupled to the application server 1 130 via the P- GW 1 123. The application server 1130 may signal the PCRF 1 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 1130. [0088] FIG. 12 illustrates example components of a device 1200 in accordance with some embodiments. In some embodiments, the device 1200 may include application circuitry 1202, baseband circuitry 1204, Radio

Frequency (RF) circuitry 1206, front-end module (FEM) circuitry 1208, one or more antennas 1210, and power management circuitry (PMC) 1212 coupled together at least as shown. The components of the illustrated device 1200 may be included in a UE or a RAN node. In some embodiments, the device 1200 may include less elements (e.g., a RAN node may not utilize application circuitry 1202, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 1200 may include additional elements such as, for example, memory/ storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cioud-RAN (C-RAN) implementations).

[0089] The application circuitry 1202 may include one or more application processors. For example, the application circuitry 1202 may include circuitry such as, but not limited to, 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, application processors, etc.). The processors may be coupled with or may include memory/ storage and may be configured to execute instaictions stored in the memory/ storage to enable various applications or operating systems to run on the device 1200. In some embodiments, processors of application circuitry 1202 may process IP data packets received from an EPC.

[0090] The baseband circuitry 1204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1206 and to generate baseband signals for a transmit signal path of the RF circuitry 1206. Baseband processing circuity 1204 may interface with the application circuitry 1202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1206. For example, in some embodiments, the baseband circuitry 1204 may include a third generation (3G) baseband processor 1204 A, a fourth generation (4G) baseband processor 1204B, a fifth generation (5G) baseband processor 1204C, or other baseband

processor(s) 1204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), si!2h generation (6G), etc.). The baseband circuitry 1204 (e.g., one or more of baseband processors 1204 A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1206. In other embodiments, some or all of the functionality of baseband processors 1204 A-D may be included in modules stored in the memory 1204G and executed via a Central Processing Unit (CPU) 1.204E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1204 may include Fast-Fourier Transform (FFT), preceding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1204 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0091] In some embodiments, the baseband circuitry 1204 may include one or more audio digital signal processor(s) (DSP) 1204F. The audio DSP(s) 1204F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry 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 1204 and the application circuitry 1202 may be implemented together such as, for example, on a system on a chip (SOC).

[0092] In some embodiments, the baseband circuitry 1204 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1204 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPA ).

Embodiments in which the baseband circuitry 1204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0093] RF circuitry 1206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitiy 1206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1208 and provide baseband signals to the baseband circuitry 1204. RF circuitry 1206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitiy 1204 and provide RF output signals to the FEM circuitry 1208 for transmission.

| 0094 | In some embodiments, the receive signal path of the RF circuitry

1206 may include mixer circuitry 1206 A, amplifier circuitry 1206B and filter circuitry 1206C. In some embodiments, the transmit signal path of the RF circuitry 1206 may include filter circuitry 1206C and mixer circuitry 1206A. RF circuitry 1206 may also include synthesizer circuitry 1206D for synthesizing a frequency for use by the mixer circuitry 1206 A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1206 A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1208 based on the synthesized frequency provided by synthesizer circuitry 1206D. The amplifier circuitiy 1206B may be configured to amplify the down-converted signals and the filter circuitry 1206C may be 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. Output baseband signals may be provided to the baseband circuitry 1204 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1206 A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect. [0095] In some embodiments, the mixer circuitry 1206 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 1206D to generate RF output signals for the FEM circuitry 1208. The baseband signals may be provided by the baseband circuitry 1204 and may be filtered by filter circuitry 1206C.

[0096] In some embodiments, the mixer circuitry 1206 A of the receive signal path and the mixer circuitry 1206A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry

1206 A of the receive signal path and the mixer circuitry 1206 A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1206 A of the receive si gnal path and the mi xer circuitry 1206 A may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1206 A of the receive signal path and the mixer circuitry 1206 A of the transmit signal path may be configured for superheterodyne operation.

[0097] In some embodiments, 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. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1204 may include a digital baseband interface to communicate with the RF' circuitry 1206.

[0098] In some dual-mode embodiments, a 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.

[0099] In some embodiments, the synthesizer circuitry 1206D may be a fractional-N synthesizer or 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. For example, synthesizer circuitry 1206D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00100] The synthesizer circuitry 1206D may be configured to synthesize an output frequency for use by the mixer circuitry 1206 A of the RF circuitry 1206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1206D may be a fractional N/N+l synthesizer.

[00101] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1204 or the applications processor 1202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the applications processor 1202.

[00102] Synthesizer circuitry 1206D of the RF circuitry 1206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or +l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle,

[00103] In some embodiments, synthesizer circuitry 1206D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a mul tiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF' circuitry 1206 may include an IQ/polar converter. [00104] FEM circuitry 1208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1206 for further processing. FEM circuitry 1208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF' circuitry 1206 for transmission by one or more of the one or more antennas 1210. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1206, solely in the FEM 1208, or in both the RF circuitry 206 and the FEM 1208.

[00105] In some embodiments, the FEM circuitry 1208 may include a

TX RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LN A to amplify received RF signals and provide the amplified received RF' signals as an output (e.g., to the RF circuitry 1206). The transmit signal path of the FEM circuitry 1208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1210).

[00106] In some embodiments, the PMC 1212 may manage power provided to the baseband circuitry 1204. In particular, the PMC 1212 may control power-source selection, voltage scaling, batter}' charging, or DC-to-DC conversion. The PMC 1212 may often be included when the device 1200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 1212 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[00107] While FIG. 12 shows the PMC 1212 coupled only with the baseband circuitry 1204. However, in other embodiments, the PMC 12 12 mav be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1202, RF circuitry 1206, or FEM 1208.

[00108] In some embodiments, the PMC 1212 may control, or otherwise be part of, various power saving mechanisms of the device 1200. For example, if the device 1200 is in an RC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1200 may power down for brief intervals of time and thus save power.

[00109 ] If there is no data traffic activity for an el2ended period of time, then the device 1200 m ay transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1200 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.

[00110] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00111] Processors of the application circuitry 1202 and processors of the baseband circuitry 1204 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1204, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1204 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[00112] FIG. 13 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 1204 of FIG. 12 may comprise processors 1204A-1204E and a memory 1204G utilized by said processors. Each of the processors 1204A-1204E may include a memory interface, 1304A-1304E, respectively, to send/receive data to/from the memory 1204G.

[00113] The baseband circuitry 1204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1312 (e.g., an interface to send/receive data to/from memory el 2ernal to the baseband circuitry 1204), an application circuitry interface 1314 (e.g., an interface to send/receive data to/from the application circuitry 1202 of FIG. 12), an RF circuitry interface 1316 (e.g., an interface to send/receive data to/from RF circuitry 1206 of FIG. 12), a wireless hardware connectivity interface 1318 (e.g., an interface to send/receive data to/from Near Field

Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 1320 (e.g., an interface to send/receive power or control signals to/from the PMC 1212).

[00114] FIG. 14 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane 1400 is shown as a communications protocol stack between the UE 1101 (or alternatively, the UE 1102), the RAN node 111 1 (or alternatively, the RAN node 1 1 12), and the MME 1121.

[00115] The PHY layer 1401 may transmit or receive information used by the MAC layer 1402 over one or more air interfaces. The PHY layer 1401 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 1405. The PHY layer 140 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.

[00116] The MAC layer 1402 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channel s onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[00117] The RLC layer 1403 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM), The RLC layer 1403 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 1403 may also execute re- segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[00118] The PDCP layer 1404 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[00119] The main services and functions of the RRC layer 1405 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures,

[00120] The UE 1101 and the RAN node 1111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 1401, the MAC layer 1402, the RLC layer 1403, the PDCP layer 1404, and the RRC layer 1405,

[00121] The non-access stratum (NAS) protocols 1406 form the highest stratum of the control plane between the UE 1101 and the MME 1121. The NAS protocols 1406 support the mobility of the UE 1 101 and the session management procedures to establish and maintain IP connectivity between the UE 1101 and the P-GW 1 123.

[00122] The SI Application Protocol (Sl-AP) layer 1415 may support the functions of the SI interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node 1111 and the CN 1120. The Sl- AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

[00123] The Stream Control Transmission Protocol (SCTP) layer

(alternatively referred to as the SC TP/IP layer) 1414 may ensure reliable delivery of signaling messages between the RAN node 1111 and the MME 1121 based, in part, on the IP protocol, supported by the IP layer 1413. The L2 layer 1412 and the L I layer 141 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[00124] The RAN node 1111 and the MME 1 121 may utilize an S l-MME interface to exchange control plane data via a protocol stack comprising the LI layer 1 1 1, the L2 layer 1412, the IP layer 1413, the SCTP layer 1414, and the S l -AP layer 1415.

[00125] FIG. 15 is an illustration of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 1500 is shown as a communications protocol stack between the UE 1 101 (or

alternatively, the UE 1 102), the RAN node 1111 (or alternatively, the RAN node

~ 3?— 1 1 12), the S-GW 122, and the P-GW 1 123 , The user plane 1500 may utilize at least some of the same protocol layers as the control plane 1400. For example, the UE 1101 and the RAN node 1 1 1 1 may utilize a Uu interface (e.g., an LTE- Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 1401, the MAC layer 1402, the RLC layer 1403, the PDCP layer 1404.

[00126] The General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 1504 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (UDP/IP) layer 1503 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 1 1 1 1 and the S-GW 1 22 may utilize an Sl- U interface to exchange user plane data via a protocol stack comprising the LI layer 141 1, the L2 layer 1412, the UDP/IP layer 1503, and the GTP-U layer 1504. The S-GW 1122 and the P-GW 1123 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 1411, the L2 layer 1412, the UDP/IP layer 1503, and the GTP-U layer 1504. As discussed above with respect to FIG. 14, NAS protocols support the mobility of the UE 1101 and the session management procedures to establi sh and maintain IP connectivity between the UE 1101 and the P-GW 1123.

[00127] FIG. 16 illustrates components of a core network in accordance with some embodiments. The components of the CN 1120 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some

embodiments, Network Functions Virtualization (NFV) is utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums

(described in further detail below). A logical instantiation of the CN 1120 may¬ be referred to as a network slice 1601. A logical instantiation of a portion of the CN 1120 may be referred to as a network sub-slice 1602 (e.g., the network sub- slice 1602 is shown to include the PGW 1 123 and the PCRF 1 126). [00128] NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

[00129] FIG. 17 is a block diagram illustrating components, according to some example embodiments, of a system 1700 to support NFV. The system 1700 is illustrated as including a virtualized infrastructure manager (VIM) 1702, a network function virtualization infrastructure (NFVI) 1704, a VNF manager (VNFM) 1706, virtualized network functions (VNFs) 1708, an element manager (EM) 1710, an NFV Orchestrator (NFVO) 1712, and a network manager (NM) 1714.

[00130] The VIM 1702 manages the resources of the NFVI 1704. The NF VI 1704 can include physical or virtual resources and applications (including hypervisors) used to execute the system 1700. The VIM 1702 may manage the life cycle of virtual resources with the NFVI 1704 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[00131] The VNFM 1706 may manage the VNFs 1708. The VNFs 1708 may be used to execute EPC components/functions. The VNFM^ 1706 may manage the life cycle of the VNFs 1708 and track performance, fault and security of the virtual aspects of VNFs 1708. The EM 1710 may track the performance, fault and security of the functional aspects of VNFs 1708. The tracking data from the VNFM 1706 and the EM 1710 may comprise, for example, performance measurement (PM) data used by the VIM 1702 or the NFVI 1704. Both the VNFM 1706 and the EM 1710 can scale up/down the quantity of VNFs of the sy stem 1700.

[00132] The NFVO 1712 may coordinate, authorize, release and engage resources of the NFVI 1704 in order to provide the requested service (e.g., to execute an EPC function, component, or slice). The NM 1714 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 1710).

[00133] FIG. 18 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 non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 18 shows a diagrammatic representation of hardware resources 1800 including one or more processors (or processor cores) 1810, one or more memory/ storage devices 1820, and one or more communication resources 1830, each of which may be communicatively coupled via a bus 1840. For embodiments where node virtual ization (e.g., NFV) is utilized, a hypervisor 1802 may be executed to provide an execution environment for one or more network slices/ sub-slices to utilize the hardware resources 1800

[00134] The processors 1810 (e.g., a central processing unit

(CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1812 and a processor 1814.

[00135] The memory/storage devices 1820 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1820 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random- access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc,

[00136] The communication resources 1830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1804 or one or more databases 1806 via a network 1808. For example, the communication resources 1830 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[00137] nstructions 1850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1810 to perform any one or more of the methodol ogies discussed herein. The instructions 1850 may reside, completely or partially, within at least one of the processors 1810 (e.g., within the processor's cache memory), the memory/storage devices 1820, or any suitable combination thereof. Furthermore, any portion of the instructions 1850 may be transferred to the hardware resources 1800 from any combination of the peripheral devices 1804 or the databases 1806. Accordingly, the memory of processors 1810, the memory/storage devices 1820, the peripheral devices 1804, and the databases 1806 are examples of computer-readable and machine-readable media.

[00138] Additional notes and examples:

[00139] Example 1 is an apparatus for a user equipment (UE), the apparatus comprising: memory; and processing circuitry configured to: encode a first scheduling request (SR) for a first resource for transmission on a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS) attribute; encode a second SR for a second resource for transmission on a second PUCCH resource dedicated for the second resource, a periodicity of transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute; decode a first uplink grant on a physical downlink control channel (PDCCH) based on transmission of the first SR to an evolved node, the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and decode a second uplink grant on the PDCCH based on transmission of the second SR to the evolved node, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute.

[00140] In Example 2, the subject matter of Example 1 includes, wherein the second periodicity is different than the first periodicity. [00141] In Example 3, the subject matter of Examples 1-2 includes, wherein the first and second SR resources are configured by radio resource control (RRC) signaling,

[00142] In Example 4, the subject matter of Examples 1-3 includes, wherein a first numerology is configured for the first SR resource and a second numerology is configured for the second SR resource.

[00143] In Example 5, the subject matter of Example 4 includes, wherein the second numerology is different than the first numerology.

[00144] In Example 6, the subject matter of Examples 1-5 includes, the processing circuitry further configured to: encode data for transmission on a physical uplink shared channel (PUSCH) using a logical channel, the first uplink grant comprising an indication of the logical channel.

[00145] In Example 7, the subject matter of Examples 1-6 includes, the processing circuitry further configured to: encode a first buffer status report (BSR) for transmission on a physical uplink shared channel (PUSCH) in the first allocated uplink resource, the BSR comprising an amount of data to be transmitted on a first logical channel group (LCG); decode a third uplink grant in response to the first BSR; and encode the data for transmission on the PUSCH using a logical channel from the first LCG.

[00146] In Example 8, the subject matter of Examples 1-7 includes, the processing circuitry further configured to encode second data for transmission on the PUSCH using a second logical channel, the second uplink grant comprising an indication of the second logical channel,

[00147] In Example 9, the subject matter of Examples 1-8 includes, the processing circuitry further configured to: determine transmission of the first SR and the second SR would overlap in time; and determine a delay of transmission of the second SR such that the first SR and the second SR do not overlap in time.

[00148] In Example 10, the subject matter of Example 9 includes, wherein the first resource is a higher priority compared to the second resource.

[00149] In Example 11, the subject matter of Examples 1—10 includes, wherein the first periodicity corresponds with a symbol level periodicity.

[00150] In Example 12, the subject matter of Example 1 1 includes, wherein the second periodicity corresponds with a slot level periodicity. [00151] In Example 13, the subject matter of Examples 1-12 includes, wherein the second periodicity and the first periodicity are the same.

[00152] In Example 14, the subject matter of Example 13 includes, wherein the QoS attribute of the first SR comprises multiple bits.

[00153] In Example 15, the subject matter of Examples 13-14 includes, wherein the second allocated uplink resource uses a third periodicity different than the first periodicity.

[00154] In Example 16, the subject matter of Examples 1-15 includes, wherein the first periodicity is stored in the memory.

[00155] In Example 17, the subject matter of Example 16 includes, a transceiver configured to receive the first uplink grant and the second uplink grant.

[00156] Example 18 is a non-transitory computer-readable medium comprising instructions to cause a user equipment (UE), upon execution of the instructions by processing circuitry of the UE, to: encode a first scheduling request (SR) for a first resource for transmission on a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS) attribute; encode a second SR for a second resource for transmission on a second PUCCH resource dedicated for the second resource, a periodicity of transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute; decode a first uplink grant on a physical downlink control channel (PDCCH) based on transmission of the first SR to an evolved nodeB (evolved node), the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and decode a second uplink grant on the PDCCH based on transmission of the second SR to the evolved node, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute.

[00157] In Example 19, the subject matter of Example 18 includes, wherein the second periodicity is different than the first periodicity.

[00158] In Example 20, the subject matter of Examples 18-19 includes, wherein the first and second SR resources are configured by radio resource control (RRC) signaling. [00159] In Example 21 , the subject matter of Examples 18-20 includes, wherein a first numerology is configured for the first SR resource and a second numerology is configured for the second SR resource,

[00160] In Example 22, the subject matter of Example 21 includes, wherein the second numerology is different than the first numerology.

[00161] In Example 23, the subject matter of Examples 18-22 includes, wherein execution of the instructions by processing circuitry further cause the UE to: encode data for transmission on a physical uplink shared channel (PUSCH) using a logical channel, the first uplink grant comprising an indication of the logical channel,

[00162] In Example 24, the subject matter of Examples 18-23 includes, wherein execution of the instructions by processing circuitry further cause the UE to: encode a first buffer status report (BSR) for transmission on a physical uplink shared channel (PUSCH) in the first allocated uplink resource, the BSR comprising an amount of data to be transmitted on a first logical channel group (LCG); decode a third uplink grant in response to the first BSR; and encode the data for transmission on the PUSCH using a logical channel from the first LCG.

[00163] In Example 25, the subject matter of Examples 18-24 includes, wherein execution of the instructions by processing circuitry further cause the UE to encode second data for transmission on the PUSCH using a second logical channel, the second uplink grant comprising an indication of the second logical channel.

[00164] In Example 26, the subject matter of Examples 18-25 includes, wherein execution of the instructions by processing circuitry further cause the UE to: determine transmission of the first SR and the second SR would overlap in time; and determine a delay of transmission of the second SR such that the first SR and the second SR do not overlap in time.

[00165] In Example 27, the subject matter of Example 26 includes, wherein the first resource is a higher priority compared to the second resource.

[00166] In Example 28, the subject matter of Examples 18-27 includes, wherein the first periodicity corresponds with a symbol level periodicity.

[00167] In Example 29, the subject matter of Example 28 includes, wherein the second periodicity corresponds with a slot level periodicity. [00168] In Example 30, the subject matter of Examples 18-29 includes, wherein the second periodicity and the first periodicity are the same.

[00169] In Example 31, the subject matter of Example 30 includes, wherein the QoS attribute of the first SR comprises multiple bits.

[00170] In Example 32, the subject matter of Examples 30-31 includes, wherein the second allocated uplink resource uses a third periodicity different than the first periodicity.

[00171] Example 33 is an apparatus comprising means for performing any of the operations of Examples 18-32.

[00172] Example 34 is an apparatus for an evolved node, the apparatus comprising: memory; and processing circuitry configured to: decode a first scheduling request (SR) for a first resource from a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS ) attribute; decode a second SR for a second resource from a second PUCCH resource dedicated for the second resource, a periodicity of transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute; encode a first uplink grant on a physical downlink control channel f (PDCCH) based on decoding of the first SR, the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and encode a second uplink grant on the PDCCH based on decoding of the second SR, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute.

[00173] In Example 35, the subject matter of Example 34 includes, wherein the second periodicity is different than the first periodicity.

[00174] In Example 36, the subject matter of Examples 34-35 includes, the processing circuitry further configured to: decode data on a physical uplink shared channel (PUSCH) using a logical channel, the first uplink grant comprising an indication of the logical channel.

[00175] In Example 37, the subject matter of Examples 34-36 includes, the processing circuitry further configured to: decode a first buffer status report (BSR) from a physical uplink shared channel (PUSCH) in the first allocated uplink resource, the BSR comprising an amount of data to be transmitted on a first logical channel group (LCG); encode a third uplink grant in response to the first BSR; and decode the data for transmission on the PUSCH using a logical channel from the first LCG.

[00176] In Example 38, the subject matter of Examples 34-37 includes, the processing circuitry further configured to decode second data from the

PUSCH using a second logical channel, the second uplink grant comprising an indication of the second logical channel,

[00177] In Example 39, the subject matter of Examples 34-38 includes, wherein the first periodicity corresponds with a symbol level periodicity.

[00178] In Example 40, the subject matter of Example 39 includes, wherein the second periodicity corresponds with a slot level periodicity.

[00179] In Example 41, the subject matter of Examples 34-40 includes, wherein the second periodicity and the first periodicity are the same.

[00180] In Example 42, the subject matter of Example 41 includes, wherein the QoS attribute of the first SR comprises multiple bits.

[00181] In Example 43, the subject matter of Example 42 includes, wherein the second allocated uplink resource uses a third periodicity different than the first periodicity.

[00182] Example 44 is a non-transitory computer-readable medium comprising instructions to cause an evolved node, upon execution of the instructions by processing circuitry of the for an evolved node, to: decode a first- scheduling request (SR) for a first resource from a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS) attribute; decode a second SR for a second resource from a second PUCCH resource dedicated for the second resource, a periodicity of transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute; encode a first uplink grant on a physical downlink control channel (PDCCH) based on decoding of the first SR, the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and encode a second uplink grant on the PDCCH based on decoding of the second SR, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute. [00183] In Example 45, the subject matter of Example 44 includes, wherein the second periodicity is different than the first periodicity.

[00184] In Example 46, the subject matter of Examples 44-45 includes, wherein execution of the instructions by processing circuitry further cause the evolved node to: decode data on a physical uplink shared channel (PUSCH) using a logical channel, the first uplink grant comprising an indication of the logical channel.

[00185] In Example 47, the subject matter of Examples 44-46 includes, wherein execution of the instructions by processing circuitry further cause the evolved node to: decode a first buffer status report (BSR) from a physical uplink shared channel (PUSCH) in the first allocated uplink resource, the BSR comprising an amount of data to be transmitted on a first logical channel group (LCG); encode a third uplink grant in response to the first BSR; and decode the data for transmission on the PUSCH using a logical channel from the first LCG.

[00186] In Example 48, the subject matter of Examples 44-47 includes, wherein execution of the instructions by processing circuitry further cause the evolved node to decode second data from the PUSCH using a second logical channel, the second uplink grant comprising an indication of the second logical channel.

[00187] In Example 49, the subject matter of Examples 44-48 includes, wherein the first periodicity corresponds with a symbol level periodicity.

[00188] In Example 50, the subject matter of Example 49 includes, wherein the second periodicity corresponds with a slot level periodicity.

[00189] In Example 51 , the subject matter of Examples 44-50 includes, wherein the second periodicity and the first periodicity are the same.

[00190] In Example 52, the subject matter of Example 51 includes, wherein the QoS attribute of the first SR comprises multiple bits.

[00191] In Example 53, the subject matter of Examples 51 -52 includes, wherein the second allocated uplink resource uses a third periodicity different than the first periodicity.

[00192] Example 54 is an apparatus comprising means for performing any of the operations of Examples 44-53. [00193] Example 55 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-54.

[00194] Example 56 is an apparatus comprising means to implement of any of Examples 1-54.

[00195] Example 57 is a system to implement of any of Examples 1-54.

[00196] Example 58 is a method to implement of any of Examples 1-54.

[00197] The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as "examples." Such examples may include elements in addition to those shown or described.

However, also contemplated are examples that include the elements shown or described. Moreover, also contemplate are examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.

[00198] Publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) are supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.

[00199] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In the appended claims, the terms "including" and "in which" are used as the plain- English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to suggest a numerical order for their objects.

[00200] The embodiments as described above may be implemented in various hardware configurations that may include a processor for executing instructions that perform the techniques described. Such instructions may be contained in a machine-readable medium such as a suitable storage medium or a memory or other processor-executable medium.

[00201] The embodiments as described herein may be implemented in a number of environments such as part of a wireless local area network (WLAN), 3rd Generation Partnership Project (3GPP) Universal Terrestrial Radio Access Network (UTRA ), or Long-Term-Evolution (LTE) or a Long-Term-Evolution (LTE) communication system, although the scope of the disclosure is not limited in this respect. An example LTE system includes a number of mobile stations, defined by the LTE specification as User Equipment (UE), communicating with a base station, defined by the LTE specifications as an gNB.

[00202] Antennas referred to herein may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MEMO) embodiments, antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result between each of antennas and the antennas of a transmitting station. In some MIMO embodiments, antennas may be separated by up to 1/10 of a wavelength or more.

[00203] In some embodiments, a receiver as described herein may be configured to receive signals in accordance with specific communication standards, such as the Institute of Electrical and Electronics Engineers (IEEE) standards including IEEE 802.11 standards and/or proposed specifications for WLANs, although the scope of the disclosure is not limited in this respect as they may also be suitable to transmit and/or receive communications in accordance with other techniques and standards. In some embodiments, the receiver may be configured to receive signals in accordance with the IEEE 802.16-2004, the IEEE 802.16(e) and/or IEEE 802.16(m) standards for wireless metropolitan area networks (WMANs) including variations and evolutions thereof although the scope of the disclosure is not limited in this respect as they may also be suitable to transmit and/or receive communications in accordance with other techniques and standards. In some embodiments, the receiver may be configured to receive signals in accordance with the Universal Terrestrial Radio Access Network (UTRAN) LTE communication standards. For more

information with respect to the IEEE 802.11 and IEEE 802.16 standards, please refer to "IEEE Standards for Information Technology— Telecommunications and Information Exchange between Systems" - Local Area Networks - Specific Requirements - Part 11 "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY), ISO/IEC 8802-11 : 1999", and Metropolitan Area Networks - Specific Requirements - Part 16: "Air Interface for Fixed Broadband Wireless Access Systems," May 2005 and related amendments/versions. For more information with respect to UTRAN LTE standards, see the 3rd Generation Partnership Project (3GPP) standards for UTRAN-LTE, including variations and evolutions thereof.

[00204] The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with others. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. However, the claims may not set forth every feature disclosed herein as embodiments may feature a subset of said features. Further, embodiments may include fewer features than those disclosed in a particular example. Thus, the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment. The scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

An apparatus for a user equipment (UE), the apparatus comprising: memory, and processing circuitry configured to: encode a first scheduling request (SR) for a first resource for transmission on a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS) attribute; encode a second SR for a second resource for transmission on a second PUCCH resource dedicated for the second resource, a periodicity of transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute, decode a first uplink grant on a physical downlink control channel (PDCCH) based on transmission of the first SR to an evolved node, the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and decode a second uplink grant on the PDCCH based on
transmission of the second SR to the evolved node, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute.
2. The apparatus of claim 1, wherein the second periodicity is different than the first periodicity.
3. The apparatus of claim 1, wherein the first and second SR resources are configured by radio resource control (RRC) signaling.
4. The apparatus of claim 1, wherein a first numerology is configured for the first SR resource and a second numerology is configured for the second SR resource,
5. The apparatus of claim 4, wherein the second numerology is different than the first numerology.
6. The apparatus of claim 1, the processing circuitry further configured to: encode data for transmission on a physical uplink shared channel (PUSCH using a logical channel, the first uplink grant comprising an indication of the logical channel,
7. The apparatus of claim 1, the processing circuitry further configured to: encode a first buffer status report (BSR) for transmission on a physical uplink shared channel (PUSCH) in the first allocated uplink resource, the BSR comprising an amount of data to be transmitted on a first logical channel group (LCG); decode a third uplink grant in response to the first BSR; and encode the data for transmission on the PUSCH using a logical channel from the first LCG,
8. The apparatus of any of claims 1-7, the processing circuitry further configured to encode second data for transmission on the PIJSCH using a second logical channel, the second uplink grant comprising an indication of the second logical channel.
9. The apparatus of any of claims 1-7, the processing circuitry further configured to: determine transmission of the first SR and the second SR would overlap in time, and determine a delay of transmission of the second SR such that the first SR and the second SR do not overlap in time.
10. The apparatus of claim 9, wherein the first resource is a higher priority compared to the second resource.
11. The apparatus of any of claims 1-7, wherein the first periodicity corresponds with a symbol level periodicity.
12. The apparatus of claim 11, wherein the second periodicity corresponds with a slot level periodicity,
13. The apparatus of claim 1, wherein the second periodicity and the first periodicity are the same,
14. The apparatus of claim 13, wherein the QoS attribute of the first SR comprises multiple bits.
15. The apparatus of any of claims 13-14, wherein the second allocated uplink resource uses a third periodicity different than the first periodicity.
16. The apparatus of any of claims 1-7, wherein the first periodicity is stored in the memory.
17. The apparatus of claim 16, further comprising a transceiver configured to receive the first uplink grant and the second uplink grant.
18. A non-transitory computer-readable medium comprising instructions to cause a user equipment (UE), upon execution of the instructions by processing circuitry of the UE, to; encode a first scheduling request (SR) for a first resource for
transmission on a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS) attribute; encode a second SR for a second resource for transmission on a second PUCCH resource dedicated for the second resource, a periodicity of
transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute; decode a first uplink grant on a physical downlink control channel (PDCCH) based on transmission of the first SR to an evolved nodeB (evolved node), the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and decode a second uplink grant on the PDCCH based on transmission of the second SR to the evolved node, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute.
19. The non-transitory computer-readable medium of claim 18, wherein the second periodicity is different than the first periodicity.
20. The non-transitory computer-readable medium of claim 18, wherein the first and second SR resources are configured by radio resource control (RRC) signaling.
21 . An apparatus comprising means for performing any of the operations of claims 18-20.
22. An apparatus for an evolved node, the apparatus comprising: memory; and processing circuitry configured to: decode a first scheduling request (SR) for a first resource from a first physical uplink control channel (PUCCH) resource dedicated for the first resource, a periodicity of transmission of a SR for the first resource having a first periodicity, the first SR comprising a first quality of service (QoS) attribute; decode a second SR for a second resource from a second PUCCH resource dedicated for the second resource, a periodicity of transmission of a SR for the second resource having a second periodicity, the second SR comprising a second QoS attribute; encode a first uplink grant on a physical downlink control channel
(PDCCH) based on decoding of the first SR, the first uplink grant comprising a first allocated uplink resource based upon the first QoS attribute; and encode a second uplink grant on the PDCCH based on decoding of the second SR, the second uplink grant comprising a second allocated uplink resource based upon the second QoS attribute.
23. The apparatus of claim 22, wherein the second periodicity is different than the first periodicity.
24. The apparatus of claim 22, the processing circuitry further configured to: decode data on a physical uplink shared channel (PUSCH) using a logical channel, the first uplink grant comprising an indication of the logical channel.
25. The apparatus of claim 22, the processing circuitry further configured to: decode a first buffer status report (BSR) from a physical uplink shared channel (PUSCH) in the first allocated uplink resource, the BSR comprising an amount of data to be transmitted on a first logical channei group (LCG); encode a third uplink grant in response to the first BSR; and decode the data for transmission on the PUSCH using a logical channel from the first LCG.
PCT/US2017/046075 2016-08-11 2017-08-09 Uplink transmission request for multiple numerologies WO2018031638A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US201662373482P true 2016-08-11 2016-08-11
US62/373,482 2016-08-11
US201662402865P true 2016-09-30 2016-09-30
US62/402,865 2016-09-30

Publications (1)

Publication Number Publication Date
WO2018031638A1 true WO2018031638A1 (en) 2018-02-15

Family

ID=61162524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/046075 WO2018031638A1 (en) 2016-08-11 2017-08-09 Uplink transmission request for multiple numerologies

Country Status (1)

Country Link
WO (1) WO2018031638A1 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018127620A1 (en) * 2017-01-04 2018-07-12 Nokia Technologies Oy Scheduling request with different numerologies
WO2018160372A1 (en) * 2017-03-03 2018-09-07 Qualcomm Incorporated Signaling for multiplexing of low latency communication and sidelink communications
WO2019165968A1 (en) * 2018-03-01 2019-09-06 电信科学技术研究院有限公司 Uplink control information transmission method, uplink control information receiving method, and terminal, base station and device
WO2019191878A1 (en) * 2018-04-02 2019-10-10 北京小米移动软件有限公司 Data transmission method, device, system and storage medium
WO2019220648A1 (en) * 2018-05-18 2019-11-21 株式会社Nttドコモ User terminal and wireless communication method
WO2019233586A1 (en) * 2018-06-07 2019-12-12 Huawei Technologies Co., Ltd. Apparatus and method for efficient packet transmission
WO2020029783A1 (en) * 2018-08-07 2020-02-13 维沃移动通信有限公司 Pusch and sr processing method and device
US10608805B2 (en) 2018-04-20 2020-03-31 At&T Intellectual Property I, L.P. Supplementary uplink with LTE coexistence adjacent to frequency division duplex spectrum for radio networks
US10750564B2 (en) 2018-05-21 2020-08-18 Comcast Cable Communications, Llc Failure detection and recovery for multiple active resources

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120269154A1 (en) * 2010-01-13 2012-10-25 Min Wang Methods and arrangements in a wireless communication system
US20150110043A1 (en) * 2008-02-04 2015-04-23 Qualcomm Incorporated Simultaneous Transmission of Acknowledgement, Channel Quality Indicator and Scheduling Request
US20150373678A1 (en) * 2012-03-23 2015-12-24 Mediatek Inc. Method and Apparatus of Allocating Scheduling Request Resources in Mobile Communication Networks
WO2016010227A1 (en) * 2014-07-17 2016-01-21 Lg Electronics Inc. Method and apparatus for requesting scheduling in wireless communication system
EP3048847A1 (en) * 2015-01-26 2016-07-27 Panasonic Intellectual Property Corporation of America Improved scheduling request procedure
EP3051902A1 (en) * 2013-09-26 2016-08-03 NTT DoCoMo, Inc. User terminal, base station, and transmission control method

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150110043A1 (en) * 2008-02-04 2015-04-23 Qualcomm Incorporated Simultaneous Transmission of Acknowledgement, Channel Quality Indicator and Scheduling Request
US20120269154A1 (en) * 2010-01-13 2012-10-25 Min Wang Methods and arrangements in a wireless communication system
US20150373678A1 (en) * 2012-03-23 2015-12-24 Mediatek Inc. Method and Apparatus of Allocating Scheduling Request Resources in Mobile Communication Networks
EP3051902A1 (en) * 2013-09-26 2016-08-03 NTT DoCoMo, Inc. User terminal, base station, and transmission control method
WO2016010227A1 (en) * 2014-07-17 2016-01-21 Lg Electronics Inc. Method and apparatus for requesting scheduling in wireless communication system
EP3048847A1 (en) * 2015-01-26 2016-07-27 Panasonic Intellectual Property Corporation of America Improved scheduling request procedure

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018127620A1 (en) * 2017-01-04 2018-07-12 Nokia Technologies Oy Scheduling request with different numerologies
WO2018160372A1 (en) * 2017-03-03 2018-09-07 Qualcomm Incorporated Signaling for multiplexing of low latency communication and sidelink communications
US10244522B2 (en) 2017-03-03 2019-03-26 Qualcomm Incorporated Signaling for multiplexing of low latency communication and sidelink communications
KR20190107141A (en) * 2017-03-03 2019-09-18 퀄컴 인코포레이티드 Signaling for Multiplexing Low Latency Communications and Sidelink Communications
US10750489B2 (en) 2017-03-03 2020-08-18 Qualcomm Incorporated Signaling for multiplexing of low latency communication and sidelink communications
KR102116644B1 (en) 2017-03-03 2020-05-28 퀄컴 인코포레이티드 Signaling for multiplexing of low-latency communications and sidelink communications
WO2019165968A1 (en) * 2018-03-01 2019-09-06 电信科学技术研究院有限公司 Uplink control information transmission method, uplink control information receiving method, and terminal, base station and device
WO2019191878A1 (en) * 2018-04-02 2019-10-10 北京小米移动软件有限公司 Data transmission method, device, system and storage medium
US10608805B2 (en) 2018-04-20 2020-03-31 At&T Intellectual Property I, L.P. Supplementary uplink with LTE coexistence adjacent to frequency division duplex spectrum for radio networks
WO2019220648A1 (en) * 2018-05-18 2019-11-21 株式会社Nttドコモ User terminal and wireless communication method
US10750564B2 (en) 2018-05-21 2020-08-18 Comcast Cable Communications, Llc Failure detection and recovery for multiple active resources
WO2019233586A1 (en) * 2018-06-07 2019-12-12 Huawei Technologies Co., Ltd. Apparatus and method for efficient packet transmission
WO2020029783A1 (en) * 2018-08-07 2020-02-13 维沃移动通信有限公司 Pusch and sr processing method and device

Similar Documents

Publication Publication Date Title
US10477620B2 (en) Machine type communication relaying
US10716096B2 (en) Enabling network slicing in a 5G network with CP/UP separation
US20200186263A1 (en) Devices and Methods for Robust Measurement and Data Receiving
US20190132851A1 (en) Antenna panel switching and beam indication
US20190349904A1 (en) Transmission of group common pdcch (physical downlink control channel) for nr (new radio)
RU2678462C2 (en) User terminal and methods of time resources allocation and signaling for machine-to-machine (d2d) communications
EP3298715A1 (en) Physical downlink control channel for fifth-generation networks
US10555322B2 (en) Low latency contention based scheduling request
WO2017201273A1 (en) Subframe structure for discrete fourier transform (dft) spread orthogonal frequency division multiplexing (s-ofdm) waveforms
US20180152269A1 (en) Dynamic partition resource allocation in 5g networks
US10560174B2 (en) Latency reduction for wireless data transmission
US20190191453A1 (en) User equipment (ue), evolved node-b (enb) and methods for multiplexing new radio (nr) physical uplink shared channel (nr pusch) and nr physical uplink control channel (nr pucch)
US20200067590A1 (en) Beam management procedure triggering and signaling delivery in fall-back mode
US20190182890A1 (en) Multiple radio resource reservation for vehicle-to-everything communications
US10820348B2 (en) Intra- and inter-rat co-existence and congestion control for LTE PC5-based vehicle-to-vehicle (V2V) communication
US10602506B2 (en) Activation of secondary cell containing bandwidth parts
US20200178123A1 (en) Solution for vehicle-to-everything (v2x) communication authorization in 5g system
US10595309B2 (en) Downlink control channel transmissions
US10390354B2 (en) Evolved node-B (eNB), user equipment (UE) and methods for flexible duplex communication
US10779333B2 (en) Early data transmission in wireless communication system
US20200092876A1 (en) New radio (nr) short and long duration physical uplink control channel (pucch) design
US20190068352A1 (en) Enhanced resource mapping scheme
US20200296797A1 (en) 5G FDD Low Latency Transmission Subframe Structure System and Method of Use
US20190215906A1 (en) Signaling to support reduced processing time
US10771214B2 (en) System and method for uplink power contrl framework

Legal Events

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

Ref document number: 17840197

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17840197

Country of ref document: EP

Kind code of ref document: A1