WO2022086433A1 - Procédés et systèmes de gestion de demandes de planification à haute priorité et d'informations de commande de liaison montante à basse priorité - Google Patents

Procédés et systèmes de gestion de demandes de planification à haute priorité et d'informations de commande de liaison montante à basse priorité Download PDF

Info

Publication number
WO2022086433A1
WO2022086433A1 PCT/SE2021/051074 SE2021051074W WO2022086433A1 WO 2022086433 A1 WO2022086433 A1 WO 2022086433A1 SE 2021051074 W SE2021051074 W SE 2021051074W WO 2022086433 A1 WO2022086433 A1 WO 2022086433A1
Authority
WO
WIPO (PCT)
Prior art keywords
priority
low
uci
srs
pucch
Prior art date
Application number
PCT/SE2021/051074
Other languages
English (en)
Inventor
Jonas FRÖBERG OLSSON
Sorour Falahati
Mattias Andersson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022086433A1 publication Critical patent/WO2022086433A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for handling high-priority Scheduling Requests (SRs) with low-priority Uplink Control Information (UCI).
  • SRs Scheduling Requests
  • UCI Uplink Control Information
  • Uplink Control Information consists of physical layer control information that can be Scheduling Request (SR), Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) (together, HARQ-ACK) feedback in response to Physical Downlink Shared Channel (PDSCH) receptions and Channel State Information (CSI).
  • SR Scheduling Request
  • HARQ Hybrid Automatic Repeat Request
  • ACK Acknowledgement
  • CSI Channel State Information
  • UCI can be sent on either Physical Uplink Control Channel (PUCCH) or on Physical Uplink Shared Channel (PUSCH) multiplexed with uplink (UL) data.
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • UL uplink
  • PUCCH format 0 and PUCCH format 1 are used when the number of UCI bits is 1 or 2, which only occurs when UCI consists of HARQ-ACK and/or SR
  • the other formats are used when number of UCI bits is more than two, which occurs if CSI is included (with or without HARQ-ACK/SR) or if the number of HARQ-ACK bits is more than two (with or without SR).
  • the PUCCH formats 0 and PUCCH format 2 are used for PUCCH transmissions over 1 or 2 symbols.
  • a SchedulingRequestResourceConfig is a resource configuration for opportunities for sending SR
  • the configuration consists of an identity pointing to a PUCCH resource and a periodicityAndOffset that determine time location and periodicity of the occasions for the SR transmission opportunities.
  • the PUCCH resource identified is a specification of starting frequency location (startingPRB) for the resource and also which PUCCH format shall be used on the resource.
  • startingPRB starting frequency location
  • the PUCCH format is either format 0 or format 1. All formats specify a time location within a slot using parameters startingSymbolIndex and nrofSymbols.
  • the PUCCH format 0, PUCCH format 1, and PUCCH format 4 use a single physical resource block (PRB) in the frequency domain while the other formats can be configured with multiple PRBs.
  • PRB physical resource block
  • the Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.313-g30 describes user equipment (UE) procedures for multiplexing HARQ-ACK or CSI with SR, or HARQ-ACK and CSI with SR in a slot. See, 3GPP TS 38.313- g30, Sections 9.2.5.1 and 9.2.5.2.
  • a UE is configured to transmit K PUCCHs for respective K SRs in a slot, as determined by a set of schedulingRequestResourceld and a schedulingRequestResourceld associated with schedulingRequestID-BFRSCell-r16, with SR transmission occasions that would overlap with a transmission of a PUCCH with HARQ-ACK information from the UE in the slot or with a transmission of a PUCCH with CSI report(s) from the UE in the slot.
  • a UE would transmit a PUCCH with positive SR and at most two HARQ-ACK information bits in a resource using PUCCH format 0, the UE transmits the PUCCH in the resource using PUCCH format 0 in PRB(s) for HARQ-ACK information as described in Clause
  • the UE determines a value of m 0 and m cs for computing a value of cyclic shift ⁇ [4, TS 38.211] where m 0 is provided by initialcyclicshift of PUCCH-formatO, and m cs is determined from the value of one HARQ-ACK information bit or from the values of two HARQ-ACK information bits as in Table 9.2.5-1 and Table 9.2.5-2, respectively. If the UE would transmit negative SR and a PUCCH with at most two HARQ-ACK information bits in a resource using PUCCH format 0, the UE transmits the PUCCH in the resource using PUCCH format 0 for HARQ-ACK information as described in Clause 9.2.3.
  • Table 92.5-1 Mapping of values for one HARQ-ACK information bit and positive SR to sequences for PUCCH format 0
  • Table 92.5-2 Mapping of values for two HARQ-ACK information bits and positive SR to sequences for PUCCH format 0
  • a UE would transmit SR in a resource using PUCCH format 0 and HARQ-ACK information bits in a resource using PUCCH format 1 in a slot, the UE transmits only a PUCCH with the HARQ-ACK information bits in the resource using PUCCH format 1.
  • the UE If the UE would transmit positive SR in a first resource using PUCCH format 1 and at most two HARQ-ACK information bits in a second resource using PUCCH format 1 in a slot, the UE transmits a PUCCH with HARQ-ACK information bits in the first resource using PUCCH format 1 as described in Clause 9.2.3. If a UE would not transmit a positive SR in a resource using PUCCH format 1 and would transmit at most two HARQ-ACK information bits in a resource using PUCCH format 1 in a slot, the UE transmits a PUCCH in the resource using PUCCH format 1 for HARQ-ACK information as described in Clause
  • a UE would transmit a PUCCH with 0 ACK HARQ-ACK information bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, as described in Clauses 9.2.1 and 9.2.3, bits representing a negative or positive SR, in ascending order of the values of schedulingRequestResourceld and a schedulingRequestResourceld associated with schedulingRequestlD- BFR-SCell-r16, are appended to the HARQ-ACK information bits and the UE transmits the combined UCI bits in a
  • PUCCH format 4 that the UE determines as described in Clauses 9.2.1 and 9.2.3. If one of the SRs is a positive LRR, the value of the bits indicates the positive LRR An all-zero value for the bits represents a negative SR value across all K SRs.
  • a UE would transmit a PUCCH with 0 CSI CSI report bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, bits representing corresponding negative or positive SR, in ascending order of the values of schedulingRequestResourceld and aa schedulingRequestResourceld associated with schedulingRequestID-BFRSCell-r16, are prepended to the CSI information bits as described in Clause 9.2.5.2 and the UE transmits a
  • a UE transmits a PUCCH with 0 ACK HARQ-ACK information bits, SR bits, and 0 CRC CRC bits using PUCCH format 2 or PUCCH format 3 in a PUCCH resource that includes PRBs, the
  • UE determines a number of PRBs for the PUCCH transmission to be the minimum number of PRBs, that is smaller than or equal to a number of PRBs provided respectively by nrofPRBs in PUCCH- format! or nrofPRBs in PUCCH-format3 and starts from the first PRB from the number of PRBs, that results to and, if , where Q m , and r are defined in Clause 9.2.5.2.
  • InterlaceAllocation-r16 and transmits a PUCCH with 0 ACK HARQ-
  • the UE transmits the PUCCH over the first interlace if otherwise, if the UE is provided a second interlace by interlace1 in PUCCH-format2 or PUCCH-format3, the UE transmits the PUCCH over the first and second interlaces.
  • a PUCCH resource is provided by pucch-CSI-ResourceList.
  • corresponding PUCCH resources can be provided by multi-CSI-PUCCH-ResourceList. If a UE is provided first and second PUCCH-Config, multi-CSI-PUCCH-ResourceList is provided by the first PUCCH-Config, and PUCCH-Resourceld in pucch-CSI- ResourceList oorr multi-CSI-PUCCH-ResourceList indicates a corresponding PUCCH resource in PUCCH-Resource provided by the first PUCCH-Config.
  • a UE If a UE is provided only one PUCCH resource set for transmission of HARQ-ACK information in response to PDSCH reception scheduled by a DCI format or in response to a SPS PDSCH release, the UE does not expect to be provided simultaneousHARQ-ACK-CSI.
  • a UE is configured by maxCodeRate a code rate for multiplexing HARQ-ACK, SR, and CSI report(s) in a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4.
  • a Part 1 CSI report refers either to a CSI report with only wideband CSI or to a Part 1 CSI report with wideband CSI and sub-band CSI.
  • Part 1 CSI report bits for CSI report with priority value n is a number of Part 2 CSI report bits, if any, for CSI report with priority value n [6, TS 38.214], and is a number of CSI reports that include overlapping CSI reports
  • ° r is a code rate given by maxCodeRate as in Table 9.2.5.2-1.
  • ° is a number of PRBs for PUCCH format 2, or PUCCH format 3, or PUCCH format 4, respectively, where is provided by nrofPRBs in PUCCH-format2 for PUCCH format 2 or by nrofPRBs in PUCCH-format3 for PUCCH format 3, and for PUCCH format 4
  • PUCCH format 4 where is a number of subcarriers per resource block [4, TS 38.211]
  • ° is equal to a number of PUCCH symbols for
  • PUCCH format 2 provided by nrofSymbols inPUCCH-format2.
  • PUCCH format 3 or for PUCCH format 4 is equal to a number of PUCCH symbols for PUCCH format 3 or equal to a number of PUCCH symbols for PUCCH format 4 provided by nrofSymbols in PUCCH-format3 or nrojSymbols in PUCCH-format4, respectively, after excluding a number of symbols used for DM-RS transmission for PUCCH format 3 or for PUCCH format 4, respectively [4, TS 38.211]
  • a UE has one or more CSI reports and zero or more HARQ-ACK/SR information bits to transmit in a PUCCH where the HARQ-ACK, if any, is in response to a PDSCH reception without a corresponding PDCCH
  • the UE is provided by multi-CSI-PUCCH-ResourceList with J ⁇ 2 PUCCH resources in a slot, for PUCCH format 2 and/or PUCCH format 3 and/or PUCCH format 4, as described in Clause 9.2.1, where the resources are indexed according to an ascending order for the product of a number of corresponding REs, modulation order Q m, and configured code rate r ;
  • PUCCH format 3 resource 0 or the PUCCH format 4 resource 0
  • the UE transmits a PUCCH conveying HARQ-ACK information, SR and CSI report(s) in a respective PUCCH where the UE uses the PUCCH format 2 resource j+1 , or the PUCCH format 3 resource j+1 , or the PUCCH format 4 resource j+1
  • the UE uses the PUCCH format 2 resource J -1 , or the PUCCH format 3 resource , or the PUCCH format 4 resource J -1 and the UE selects CSI report(s) for transmission together with HARQ-ACK information and SR, when any, in ascending priority value as described in [6, TS 38.214]
  • the UE transmits the bits in a PUCCH resource provided by pucch-CSI-ResourceList and determined as described in Clause 9.2.5
  • a UE If a UE has HARQ-ACK, SR and wideband or sub-band CSI reports to transmit and the UE determines a PUCCH resource with PUCCH format
  • the UE has HARQ-ACK, SR and wideband CSI reports [6, TS 38.214] to transmit and the UE determines a PUCCH resource with PUCCH format 3 or PUCCH format 4, where
  • the UE determines the PUCCH resource using the PUCCH resource indicator field [5, TS 38.212] in a last of a number of DCI formats with a value of a PDSCH- to-HARQ_feedback timing indicator field, if present, or a value of dl-DataToUL-ACK, or a value of dl- DataToUL-ACKForDCIFormatl 2 for DCI format 1_2, indicating a same slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ- ACK transmission, and the UE determines the PUCCH resource set as described in Clause 9.2.1 and Clause 9.2.3 for 0 UCI UCI bits and ° if
  • the UE transmits the HARQ-ACK, SR, and CSI reports bits by selecting the minimum number of the PRBs satisfying as described in Clauses 9.2.3 and 9.2.5.1;
  • the UE selects CSI report(s), from the
  • the UE has HARQ-ACK, SR and wideband or sub-band CSI reports to transmit, and the UE determines a PUCCH resource with PUCCH format 2, or the UE has HARQ-ACK, SR and wideband CSI reports to transmit and the UE determines a PUCCH resource with PUCCH format 3, where ° the UE determines the PUCCH resource using the
  • HARQ feedback timing indicator field indicating a same slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission
  • the UE determines the PUCCH resource set as described in Clauses 9.2.1 and 9.2.3 for 0 UCI UCI bits and if the UE transmits the HARQ-ACK, SR, and CSI reports bits in a PUCCH over the first interlace
  • PRBs by interlacel in PUCCH-format2 or PUCCH- format3 and if the UE transmits the HARQ-ACK,
  • the procedure is same as the corresponding one when the UE is provided PUCCH-ResourceSet by replacing with , or, if the UE is provided interlacel, by
  • a UE If a UE has HARQ-ACK, SR and sub-band CSI reports to transmit and the UE determines a PUCCH resource with PUCCH format 3 or
  • the UE determines the PUCCH resource using the
  • Part 2 CSI report priority value(s) it is the UE selects the first Part 2 CSI reports, according to respective priority value(s) [6, TS 38.214], for transmission together with the HARQ-ACK, SR and Part 1 CSI reports , where is the number of Part 1 CSI report bits for the n th CSI report and ° is the number of Part 2 CSI report bits for the n th CSI report priority value, is a number of CRC bits corresponding to , and a number of CRC bits corresponding to
  • the UE drops all Part 2 CSI reports and selects Part 1 CSI report(s), from the CSI reports in ascending priority value [6, TS 38.214], for transmission together with the HARQ-ACK and SR information bits where the value of satisfies and
  • the UE has HARQ-ACK, SR and sub-band
  • the UE determines the PUCCH resource using the
  • HARQ feedback timing indicator field indicating a same slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission
  • the UE determines the PUCCH resource set as described in Clauses 9.2.1 and 9.2.3 for 0 UCI UCI bits and
  • the procedure is same as the corresponding one when the UE is provided PUCCH-ResourceSet by replacing with , or, if the UE is provided interlacel, with
  • UE If UE transmits UCI comprising HARQ-ACKs and/or CSI reports(s) using PUCCH format 2, PUCCH format 3 or PUCCH format 4 multiplexed with SR, then UE adds bits representing a negative or positive SR to the transmitted UCI.
  • a UE can be configured with a maximum of four PUCCH resource sets, where each PUCCH resource set may consist of several PUCCH resources that can be used for a range of UCI sizes provided by configuration, including HARQ- ACK bits.
  • the first set is only applicable for one to two UCI bits including HARQ- ACK information and can have maximum of thirty-two PUCCH resources, while the other sets, if configured, are used for more than two UCI bits including HARQ-ACK and each can be realized using any one of up to a maximum of eight different PUCCH resources.
  • the UE determines a PUCCH resource set based on the number of HARQ-ACK information bits the UE has to send and the PUCCH resource indicator field in the last received DCI format 1_0 or DCI format 1_1 that has a value of PDSCH-to-HARQ feedback timing indicator indicating a slot for the PUCCH transmission that is the same as the slot associated with the next instance of one of the members of the PUCCH resource set.
  • the size of the determined PUCCH resource set is at most eight (3-bit PUCCH resource indicator field)
  • the PUCCH resource identity within the set is explicitly indicated by the PUCCH resource indicator field in the DCI. If the size of PUCCH resource set is more than eight, the PUCCH resource identity is determined by the index of first CCE for the PDCCH reception in addition to the PUCCH resource indicator field in the DCI.
  • the UE may have PUCCH resources for PUCCH transmissions of UCI that overlap in time.
  • the UE resolves the time overlap using a specified resolution procedure.
  • the result of this procedure is PUCCH resources that do not overlap in time and each cany UCI.
  • Different UCI types can be multiplexed or dropped if it is not possible to multiplex.
  • some specific Rel-15 rules result in dropping some UCI bits of a certain type, for example, CSI.
  • Rel-16 introduces a priority index where UCI can be of different priority. However, UCI of different priority index cannot be multiplexed. In Rel-16, UCI of the same priority are multiplexed essentially according to Rel-15 rules. If there is a remaining overlap between PUCCH(s)/PUSCH(s) of different priority indices, then the UE cancels the PUCCH(s)/PUSCH(s). There currently exist certain challenge(s). For example, transmission of a single high-priority SR can cancel many low-priority UCI bits which may have high impact on the low-priority traffic.
  • systems and procedures are provided for handling one or more high-priority SR with low-priority UCI by determining a PUCCH resource based on whether SR is positive or negative for the one or more high-priority SR.
  • a method by a wireless device for sending UCI to a network node includes determining, by the wireless device, that a PUCCH resource for sending one or more high-priority SRs at least partially overlaps in time with a PUCCH resource for sending low-priority UCI.
  • the wireless device sends the low priority UCI to the network node.
  • the low-priority UCI is sent using at least one out of one or more first uplink resources associated with the low-priority UCI.
  • all the one or more high-priority SRs are negative, the low-priority UCI is sent using a second uplink resource associated with the low-priority UCI.
  • a wireless device is adapted to determine, by the wireless device, that a PUCCH resource for sending one or more high-priority SRs at least partially overlaps in time with a PUCCH resource for sending low-priority UCI.
  • the wireless device is adapted to send the low priority UCI to the network node.
  • the low-priority UCI is sent using at least one out of one or more first uplink resources associated with the low-priority UCI.
  • all the one or more high-priority SRs are negative, the low-priority UCI is sent using a second uplink resource associated with the low- priority UCI.
  • a method by a network node for receiving UCI from a wireless device includes receiving low-priority UCI from a wireless device that has been configured to send one or more high-priority SRs on a PUCCH resource that overlaps at least partially in time with a PUCCH resource for sending low-priority UCI from the wireless device.
  • the low-priority UCI is received via at least one out of one or more first uplink resources associated with the low-priority UCI, at least one of the one or more high-priority SRs is positive.
  • the low-priority UCI is received via a second uplink resource associated with the low-priority UCI, all the one or more high-priority SRs are negative.
  • a network node for receiving UCI from a wireless device is adapted to receive low-priority UCI from a wireless device that has been configured to send one or more high-priority SRs on a PUCCH resource that overlaps at least partially in time with a PUCCH resource for sending low-priority UCI from the wireless device.
  • the low-priority UCI is received via at least one out of one or more first uplink resources associated with the low-priority UCI, at least one of the one or more high-priority SRs is positive.
  • the low-priority UCI is received via a second uplink resource associated with the low-priority UCI, all the one or more high-priority SRs are negative.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • certain embodiments provide a technical advantage since high-priority SR(s) can be multiplexed with low-priority UCI instead of cancelling low-priority UCI transmission (as in Rel-16) when the PUCCH for high-priority SR time overlaps with the PUCCH for low-priority UCI.
  • FIGURE 1 illustrates PUCCH resources that overlap in time but only partly overlap in frequency
  • FIGURE 2 illustrates PUCCH resources that overlap in frequency but only partly overlap in time
  • FIGURE 3 illustrates an example wireless network, according to certain embodiments
  • FIGURE 4 illustrates an example network node, according to certain embodiments.
  • FIGURE 5 illustrates an example wireless device, according to certain embodiments
  • FIGURE 6 illustrate an example user equipment, according to certain embodiments.
  • FIGURE 7 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 8 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 9 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 10 illustrates a method implemented in a communication system, according to one embodiment
  • FIGURE 11 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 12 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 13 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 14 illustrates an example method by a wireless device, according to certain embodiments
  • FIGURE 15 illustrates an example virtual apparatus, according to certain embodiments.
  • FIGURE 16 illustrates another example method by a wireless device, according to certain embodiments
  • FIGURE 17 illustrates another example virtual apparatus, according to certain embodiments
  • FIGURE 18 illustrates an example method by a network node, according to certain embodiments.
  • FIGURE 19 illustrates another example virtual apparatus, according to certain embodiments.
  • a wireless device e.g., UE
  • the X low-priority UCI bits may be low-priority HARQ-ACK bits and/or CSI report(s) bits and may or may not comprise low-priority SR information.
  • the PUCCH resource may or may not indicate positive or negative low-priority SR.
  • the UE is configured to send a high-priority SR on a PUCCH that overlaps with the PUCCH comprising the Xlow-priority UCI bits.
  • the UE is further configured with two PUCCH resources for sending the low-priority UCI bits wherein the UE is configured to use first PUCCH resource if the high-priority SR is a positive SR while a second PUCCH resource is used if the high-priority SR is negative.
  • the terms “positive” and “negative” are used to mean that the SR indicates that UE requests to be scheduled or not requests to be scheduled, respectively.
  • “positive” means tha the SR indicates that UE requests to be scheduled
  • “negative” means that the UE requests not to be scheduled.
  • the two PUCCH resources are configured to use the same time-frequency resources but different demodulation reference signal (DMRS) sequences.
  • DMRS demodulation reference signal
  • the two PUCCH resources are non-overlapping, neither in frequency nor time.
  • the PUCCH resources overlap in time but only partly overlapping in frequency as illustrated in FIGURE 1.
  • the PUCCH resources overlap in frequency but partly overlapping in time as illustrated in FIGURE 2.
  • the two PUCCHs can be partly overtyping both in time and frequency and use same or different DMRS sequences, in certain embodiments.
  • the UE is configured to send two or more high-priority SR on two or more PUCCHs overlapping with the PUCCH comprising the X low-priority UCI bits.
  • the UE may be configured with three or more PUCCH resources wherein:
  • the UE is configured to send k high-priority SRs on k PUCCHs overlapping with the PUCCH comprising the X low-priority UCI bits.
  • the UE may be configured with 2 k PUCCH resources wherein PUCCH resource i of the 2 k PUCCH resources is used if
  • I the decimal value of the binary k-tuple (x 0 , ... , x k _ 1 ), where x j represents the SR value (positive or negative) for the j -th high-priority SR ordered in ascending or descending ordered with respect to schedulingRequestld.
  • the UE is provided with a number of PRB offset by higher layers or implicit rules or default values. Different PRB offsets maybe used for different PUCCH formats based on a pre-defined rule or RRC configuration.
  • PRB offsets maybe used for different PUCCH formats based on a pre-defined rule or RRC configuration.
  • the UE assumes one PRB as offset for PUCCH formats over 1 PRB.
  • the UE may assume PUCCH formats 0, 1, and/or 4.
  • the frequency allocation for the second hop of the low priority PUCCH resource is used for the first hop and vice versa. Conversely, if SR is negative, the PUCCH is hopped following the allocated frequency allocations for the first hop and the second hop.
  • the low priority PUCCH resource is configured with maximum number of PRBs for PUCCH formats 2 and 3, starting from PBP x and ending in PRB y.
  • PRBs for PUCCH formats 2 and 3, starting from PBP x and ending in PRB y.
  • SR is triggered, a PRB offset is applied to x.
  • the PUCCH transmission is confined within the maximum allocated PRBs and not exceeding PRB index y.
  • the UCI are encoded and, if needed, dropped using max code rate to satisfy this condition.
  • a wireless network such as the example wireless network illustrated in FIGURE 3.
  • the wireless network of FIGURE 3 only depicts network 106, network nodes 160 and 160b, and wireless devices (WDs) 110.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 160 and WD 110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 160 and WD 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • FIGURE 4 illustrates an example network node 160, according to certain embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) andNRNodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NRNodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., Mobile Switching Centers (MSCs), Mobility Management Entities (MMEs)), Operations & Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved-Serving Mobile Location Centres (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BSCs base transceiver stations
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., Mobile Switching Centers (MSCs), Mobility
  • a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162.
  • network node 160 illustrated in FIGURES 3 and 4 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.
  • Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.
  • processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174.
  • radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate drips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same drip or set of chips, boards, or units
  • processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170.
  • some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 180 may comprise any form of volatile or nonvolatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170.
  • Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.
  • Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170.
  • Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • all or some of RF transceiver circuitry 172 may be considered a part of interface 190.
  • interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).
  • Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.
  • Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187.
  • an external power source e.g., an electricity outlet
  • power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187.
  • the battery may provide backup power should the external power source fail.
  • Other types of power sources, such as photovoltaic devices, may also be used.
  • network node 160 may include additional components beyond those shown in FIGURE 4 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.
  • FIGURE 5 illustrates an example WD 110, according to certain embodiments.
  • WD refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (V oIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehiclemounted wireless terminal device, etc.
  • V oIP voice over IP
  • PDA personal digital assistant
  • LOE laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to- everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • WD 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137.
  • WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.
  • Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface. As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116.
  • Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120, and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114. Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.
  • processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 120 of WD 110 may comprise a SOC.
  • RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 122 may be a part of interface 114.
  • RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
  • processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on die obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on die obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120.
  • Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120.
  • processing circuitry 120 and device readable medium 130 may be considered to be integrated.
  • User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110, and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.
  • Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to cany out any functionality described or indicated herein.
  • Power circuitry 137 may in certain embodiments comprise power management circuitry.
  • Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.
  • FIGURE 6 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 200 as illustrated in FIGURE 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although FGIURE 6 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 213, and/or any other component, or any combination thereof.
  • Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIGURE 6, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 201 may be configured to process computer instructions and data.
  • Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware- implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general- purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 200 may be configured to use an output device via input/output interface 205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 211 may be configured to provide a communication interface to network 243a.
  • Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243a may comprise a Wi-Fi network.
  • Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 219 may be configured to provide computer instructions or data to processing circuitry 201.
  • ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/0), startup, or reception of keystrokes from a keyboard that are stored in a non- volatile memory.
  • Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227.
  • Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a removable user
  • Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium
  • processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231.
  • Network 243a and network 243b may be the same network or networks or different network or networks.
  • Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b.
  • communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.
  • communication subsystem 231 may be configured to include any of the components described herein.
  • processing circuitry 201 may be configured to communicate with any of such components over bus 202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURE 7 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390.
  • Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360.
  • Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360.
  • Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.
  • processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.
  • hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine.
  • Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225.
  • Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.
  • FIGURE 8 illustrates an example communication system that includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414, according to certain embodiments.
  • Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c.
  • Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415.
  • a first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c.
  • a second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.
  • Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 430 may be under die ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420.
  • Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).
  • the communication system of FIGURE 8 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430.
  • the connectivity may be described as an over-the-top (OTT) connection 450.
  • Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications.
  • base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.
  • Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 9.
  • host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500.
  • Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities.
  • processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518.
  • Software 511 includes host application 512.
  • Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.
  • Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530.
  • Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 9) served by base station 520.
  • Communication interface 526 may be configured to facilitate connection 560 to host computer 510.
  • Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 9) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system
  • hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 520 further has software 521 stored internally or accessible via an external connection.
  • Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located.
  • Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538.
  • Software 531 includes client application 532.
  • Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510.
  • an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510.
  • client application 532 may receive request data from host application 512 and provide user data in response to the request data.
  • OTT connection 550 may transfer both the request data and the user data.
  • Client application 532 may interact with the user to generate the user data that it provides.
  • host computer 510, base station 520 and UE 530 illustrated in FIGURE 9 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 8, respectively.
  • the inner workings of these entities may be as shown in FIGURE 9 and independently, the surrounding network topology may be that of FIGURE 8.
  • OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, or extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing, etc.
  • the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520.
  • Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.
  • FIGURE 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 10 will be included in this section.
  • the host computer provides user data.
  • substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 640 the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 11 will be included in this section.
  • the host computer provides user data
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 12 will be included in this section.
  • step 810 the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application.
  • substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer.
  • step 840 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 13 is a flowchart illustrating an example method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • FIGURE 14 depicts a method 1000 in accordance with particular embodiments.
  • the method may be performed by a wireless device (e.g., wireless device 110 or UE 200).
  • the wireless device may comprise processing circuitry (e.g., processing circuitry 120 or 201) configured to execute a computer program to cause the wireless device to perform the method.
  • the method begins at step 1002 with the wireless device 110 determining one or more uplink resources (e.g., PUCCH resources) for sending one or more high-priority SRs and low-priority UCI to a network node 160.
  • the one or more uplink resources are determined based on whether the one or more high-priority SRs are positive or negative.
  • the method proceeds to step 1004 with sending the one or more high-priority SRs and the low-priority UCI via the one or more uplink resources determined in step 1002. Additional examples regarding the selection of the uplink resources are provided above and in the Group A examples below.
  • FIGURE 15 illustrates a schematic block diagram of an example virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the virtual apparatus may be implemented in a wireless device (e.g., wireless device 110 and/or UE 200).
  • Virtual apparatus 1200 is operable to carry out the example method described with reference to FIGURE 14 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 14 is not necessarily carried out solely by apparatus 1100. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause resource determining unit 1102, uplink transmission unit 1104, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.
  • virtual apparatus 1100 includes resource determining unit 1102 and uplink transmission unit 1104.
  • Resource determining unit 1102 is configured to determine one or more uplink resources (e.g., PUCCH resources) for sending one or more high-priority SRs and low-priority UCI to a network node. The one or more uplink resources are determined based on whether the one or more high-priority SRs are positive or negative. Additional examples regarding the selection of the uplink resources are provided above and in the Group A examples below.
  • Uplink transmission unit 1104 is configured to send the one or more high- priority SRs and the low-priority UCI via the one or more uplink resources determined by resource determining unit 1102. Uplink transmission unit 1104 may perform any suitable actions as may be needed to send an uplink transmission (e.g., encoding, multiplexing, etc.).
  • FIGURE 16 depicts another method 1200 by a wireless device 110 for sending uplink control information, UCI, to a network node 160.
  • the wireless device 110 may include a UE 200, according to certain embodiments.
  • the wireless device determines that a PUCCH resource for sending one or more high-priority SRs at least partially overlaps in time with a PUCCH resource for sending low-priority UCI.
  • the wireless device 110 sends the low priority UCI to the network node 160.
  • the low-priority UCI is sent using at least one out of one or more first uplink resources associated with the low-priority UCI.
  • the low-priority UCI is sent using a second uplink resource associated with the low- priority UCI.
  • the at least one out of one or more first uplink resources associated with the low-priority UCI may in some examples be a selected one of the one or more first uplink resources.
  • the at least one out of one or more first uplink resources associated with the low-priority UCI is different from the PUCCH resource for sending the one or more high-priority SRs, and/or a PUCCH format for the at least one out of one or more first uplink resources associated with the low-priority UCI is not format 0 and is not format 1.
  • the low-priority UCI comprises more than two UCI bits.
  • any two of the one or more first uplink resources associated with the low-priority UCI and the second uplink resource associated with the low-priority UCI are different from each other in at least one of that: they use different DMRS sequences; and they do not fully overlap in time and frequency.
  • any two of the one or more first uplink resources associated with the low- priority UCI are different from each other in at least one of that: the two of the one or more first uplink resources use different DMRS sequences; and the two of the one or more first uplink resources do not fully overlap in time and frequency.
  • any two of one of the one or more first uplink resources associated with the low-priority UCI and the second uplink resource associated with the low-priority UCI are different from each other in at least one of that: the two of one of the one or more first uplink resources and the second uplink resource use different DMRS sequences; and the two of one of the one or more first uplink resources and the second uplink resource do not fully overlap in time and frequency.
  • the at least one out of one or more first uplink resources associated with the low-priority UCI is the PUCCH resource for sending the low-priority UCI with which the PUCCH resource for sending one or more high- priority SRs at least partially overlaps in time.
  • the second uplink resource associated with the low-priority UCI is the PUCCH resource for sending the low-priority UCI with which the PUCCH resource for sending one or more high-priority SRs at least partially overlaps in time.
  • the wireless device 110 multiplexes the one or more high-priority SRs with the low-priority UCI.
  • the one or more high-priority SRs are determined to be positive when the one or more high-priority SRs indicate that the wireless device requests to be scheduled, and/or the one or more high-priority SRs are determined to be negative when the one or more high-priority SRs indicate that the wireless device does not request to be scheduled.
  • the low-priority UCI includes at least one of: one or more low-priority HARQ feedback bits, one or more low-priority CSI reporting bits, and one or more low-priority SR bits.
  • the at least one out of one or more first uplink resources comprise at least two uplink resources and, for each high-priority SR that is positive, the wireless device 110 determines one of the at least two uplink resources to use for sending the low-priority UCI based on a scheduling request value associated with the high-priority SR
  • the scheduling request value associated with the high- priority SR may be a schedulingRequestld.
  • the wireless device 110 when determining the one of the at least two uplink resources to use for sending the low-priority UCI, determines to use a first one of the at least two uplink resources when the scheduling request value associated with the high-priority SR is lower than a first threshold and determines to use a second one of the at least two uplink resources when the scheduling request value associated with the high-priority SR is higher than the first threshold.
  • the wireless device 110 determines a starting PRB offset for transmitting the low-priority UCI and applies a PRB offset to the starting PRB offset in response to determining to multiplex the low-priority UCI with a positive high-priority SR of the one or more high-priority SRs.
  • the wireless device receives the PRB offset via a RRC configuration.
  • frequency hopping is enabled and the frequency allocation used for sending the low-priority UCI depends on whether the one or more high-priority SRs are positive or negative.
  • a first frequency allocation is used for a first hop and a second frequency allocation is used for a second hop when the one or more high-priority SRs are all negative, and the second frequency allocation is used for the first hop and the first frequency allocation is used for the second hop when at least one of the high-priority SRs is positive.
  • FIGURE 17 illustrates a schematic block diagram of another example virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the virtual apparatus may be implemented in a wireless device (e.g., wireless device 110 and/or UE 200).
  • Virtual apparatus 1300 is operable to carry out the example method described with reference to FIGURE 16 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 16 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause determining unit 1302, sending unit 1304, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • virtual apparatus 1300 includes determining unit 1302 and sending unit 1304.
  • Determining unit 1302 is configured to determine that a PUCCH resource for sending one or more high-priority SRs at least partially overlaps in time with a PUCCH resource for sending low-priority UCI.
  • Sending unit 1304 is configured to send the low priority UCI to the network node 160.
  • the low-priority UCI is sent using at least one out of one or more first uplink resources associated with the low-priority UCI.
  • all the one or more high-priority SRs are negative, the low-priority UCI is sent using a second uplink resource associated with the low-priority UCI.
  • FIGURE 18 depicts an example method 1400 by a network node 160 for receiving UCI from a wireless device 110, according to certain embodiments.
  • the network node 160 receives low-priority UCI from a wireless device that has been configured to send one or more high-priority SRs on a PUCCH resource that overlaps at least partially in time with a PUCCH resource for sending low-priority UCI from the wireless device.
  • the low-priority UCI is received via at least one out of one or more first uplink resources associated with the low-priority UCI, at least one of the one or more high-priority SRs is positive.
  • the low-priority UCI is received via a second uplink resource associated with the low-priority UCI, all the one or more high-priority SRs are negative.
  • the at least one out of one or more first uplink resources associated with the low-priority UCI is different from the PUCCH resource for sending the one or more high-priority SRs, and/or a PUCCH format for the at least one out of one or more first uplink resources associated with the low-priority UCI is not format 0 and is not format 1.
  • the low-priority UCI comprises more than two UCI bits.
  • any two of the one or more first uplink resources associated with the low-priority UCI and the second uplink resource associated with the low-priority UCI are different from each other in at least one of that: the any two of the one or more first uplink resources and the second uplink resource use different demodulation reference signal, DMRS, sequences; and the any two of the one or more first uplink resources and the second uplink resource do not fully overlap in time and frequency.
  • the at least one out of one or more first uplink resources associated with the low-priority UCI is the PUCCH resource for sending the low-priority UCI with which the PUCCH resource for sending one or more high- priority SRs at least partially overlaps in time.
  • the second uplink resource associated with the low-priority UCI is the PUCCH resource for sending the low-priority UCI with which the PUCCH resource for sending one or more high-priority SRs at least partially overlaps in time.
  • the one or more high-priority SRs are multiplexed with the low-priority UCI, and the network node 160 demultiplexes the one or more high-priority SRs and the low-priority UCI.
  • the one or more high-priority SRs are positive when the one or more high-priority SRs indicate that the wireless device requests to be scheduled, and/or the one or more high-priority SRs are negative when the one or more high-priority SRs indicate that the wireless device does not request to be scheduled.
  • the low-priority UCI comprises at least one of: one or more low-priority HARQ feedback bits; one or more low-priority CSI reporting bits; and one or more low-priority SR bits.
  • the one or more first uplink resources comprise at least two uplink resources.
  • the low-priority UCI is received via a first one of the at least two uplink resources when a scheduling request value, associated with a high- priority SR that is positive, is lower than a first threshold.
  • the low- priority UCI is received via a second one of the at least two uplink resources when the scheduling request value associated with the high-priority SR that is positive, is higher than the first threshold.
  • the network node 160 sends, to the wireless device, a PRB offset for the wireless device to apply to a starting PRE offset for the low- priority UCI when the low-priority UCI is multiplexed with a positive high-priority SR of the one or more high-priority SRs.
  • the PRB offset is sent to the wireless device via a RRC configuration.
  • frequency hopping is enabled and the frequency allocation used for the low-priority UCI depends on whether the one or more high- priority SRs are positive or negative.
  • a first frequency allocation is used for a first hop and a second frequency allocation is used for a second hop when the one or more high-priority SRs are all negative.
  • the second frequency allocation is used for the first hop and the first frequency allocation is used for the second hop when at least one of the high-priority SRs is positive.
  • FIGURE 19 illustrates a schematic block diagram of another example virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the virtual apparatus may be implemented in a network node (e.g., network node 160).
  • Virtual apparatus 1500 is operable to cany out the example method described with reference to FIGURE 18 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 18 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving unit 1502 and any other suitable units of virtual apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
  • virtual apparatus 1500 includes receiving unit 1502.
  • Receiving unit 1502 is configured to receive low-priority UCI from a wireless device 110 that has been configured to send one or more high-priority SRs on a PUCCH resource that overlaps at least partially in time with a PUCCH resource for sending low-priority UCI from the wireless device 110.
  • the low-priority UCI is received via at least one out of one or more first uplink resources associated with the low-priority UCI, at least one out of the one or more high-priority SRs is positive.
  • the low-priority UCI is received via a second uplink resource associated with the low-priority UCI, all the one or more high-priority SRs are negative.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a computer program, computer program product or computer readable storage medium comprises instructions which when executed on a computer perform any of the embodiments disclosed herein.
  • the instructions are carried on a signal or carrier and which are executable on a computer wherein when executed perform any of the embodiments disclosed herein.
  • Example 1 A method performed by a wireless device, the method comprising: determining one or more uplink resources for sending one or more high-priority scheduling requests (SRs) and low-priority uplink control information (UCI) to a network node, the one or more uplink resources determined based on whether the one or more high-priority SRs are positive or negative; and sending the one or more high- priority SRs and the low-priority UCI via the one or more uplink resources.
  • SRs high-priority scheduling requests
  • UCI uplink control information
  • Example 2 The method of example 1, further comprising multiplexing the one or more high-priority SRs with the low-priority UCI.
  • Example 3 The method of any of examples 1-2, wherein: when the one or more high-priority SRs indicate that the wireless device requests to be scheduled, then the one or more high-priority SRs are determined to be positive; and when the one or more high-priority SRs indicate that the wireless device does not request to be scheduled, then the one or more high-priority SRs are determined to be negative.
  • Example 4 The method of any of examples 1-3, wherein the low-priority UCI comprises a number (X) of low priority bits.
  • Example 5 The method of any of examples 1-4, wherein the low-priority UCI comprises one or more low-priority hybrid automatic repeat request (HARQ) feedback bits and/or one or more low-priority channel state information (CSI) reporting bits.
  • HARQ hybrid automatic repeat request
  • CSI channel state information
  • Example 6 The method of any of examples 1-5, wherein the low-priority UCI comprises one or more low-priority SR bits.
  • Example 7 The method of any of examples 1-6, wherein an uplink resource for sending the one or more high-priority SRs overlaps with an uplink resource for sending the low-priority UCI.
  • Example 8 The method of any of examples 1-7, wherein determining the one or more uplink resources comprises: determining to use a first uplink resource to send the low priority UCI in response to determining that at least one of the one or more high-priority SRs is positive; and determining to use a second uplink resource to send the low priority UCI in response to determining that the one or more high-priority SRs are negative.
  • Example 9 The method of example 8, wherein the first uplink resource and the second uplink resource use the same time-frequency resources but different demodulation reference signal (DMRS) sequences.
  • DMRS demodulation reference signal
  • Example 10 The method of example 8, wherein the first uplink resource and the second uplink resource do not overlap in time and do not overlap in frequency.
  • Example 11 The method of example 8, wherein the first uplink resource and the second uplink resource use the same time resources but only partly overlap in frequency.
  • Example 12 The method of example 8, wherein the first uplink resource and the second uplink resource use the same frequency resources but only partly overlap in time.
  • Example 13 The method of example 8, wherein the first uplink resources partly overlap in time and partly overlap in frequency.
  • Example 14 The method of any of examples 10-13, wherein the first uplink resource and the second uplink resource use the same DMRS sequences.
  • Example 15 The method of any of examples 10-13, wherein the first uplink resource and the second uplink resource use different DMRS sequences.
  • Example 16 The method of any of examples 1-15, wherein the one or more uplink resources comprise an uplink resource configured for negative high-priority SRs and an uplink resource configured for positive high-priority SRs, and wherein determining the one or more uplink resources comprises: determining to use the uplink resource configured for negative high-priority SRs to send the one or more high- priority SRs in response to determining that each of the one or more high-priority SRs is negative (i.e., none of the high-priority SRs is positive); and determining to use the uplink resource configured for positive high-priority SRs to send the one or more high- priority SRs in response to determining that at least one of the one or more high- priority SRs is positive.
  • Example 17 The method of any of examples 1-16, wherein the one or more uplink resources comprise at least two uplink resources configured for positive high- priority SRs and, for each high-priority SR that is positive, determining the one more uplink resources to use for the high-priority SR is further based on a scheduling request value (e.g., schedulingRequestld) associated with the high-priority SR.
  • a scheduling request value e.g., schedulingRequestld
  • Example 18 The method of example 17, wherein the one or more high-priority SRs comprise a first positive high-priority SR associated with a first scheduling request value, and determining the one or more uplink resources for sending the first positive high-priority SR comprises: determining to use a first uplink resources configured for positive high-priority SRs if the first scheduling request value is lower than a first threshold; and determining to use a second uplink resource configured for positive high-priority SRs if the first scheduling request value is higher than the first threshold.
  • Example 19 The method of any of examples 1-8, further comprising: determining a starting physical resource block (PRB) offset for transmitting the low priority UCI; and applying a PRB offset to the starting PRB offset in response to determining to multiplex the low priority UCI with a positive high-priority SR of the one or more high-priority SRs.
  • PRB physical resource block
  • Example 20 The method of example 19, further comprising: encoding the low priority UCI and dropping using a maximum code rate in response to determining that applying the PRB offset would result in an uplink transmission exceeding a maximum number of PRBs allocated for the uplink transmission.
  • Example 21 The method of any of examples 1 -20, wherein frequency hopping is enabled and the frequency allocation used for sending the low priority UCI depends on whether the one or more high-priority SRs are positive or negative.
  • Example 22 The method of example 21, wherein: a first frequency allocation is used for a first hop and a second frequency allocation is used for a second hop when the one or more high-priority SRs are all negative; and the second frequency allocation is used for the first hop and the first frequency allocation is used for the second hop when at least one of the high-priority SRs is positive.
  • Example 23 The method of any of the previous examples, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.
  • Example 24 A method performed by a base station, the method comprising: receiving one or more high-priority scheduling requests (SRs) and low-priority uplink control information (UCI) from a wireless device, the one or more high-priority SRs and the low priority UCI received via one or more uplink resources determined based on whether the one or more high-priority SRs are positive or negative.
  • SRs high-priority scheduling requests
  • UCI uplink control information
  • Example 25 The method of example 24, wherein the one or more high-priority SRs and the low priority DCI are received via uplink resources determined according to any of examples 1-23.
  • Example 26 The method of any of examples 24-25, further comprising demultiplexing the one or more high-priority SRs and the low-priority UCI.
  • Example 27 The method of any of examples 24-26, further comprising: sending the wireless device a PRB offset for the wireless device to apply to a starting PRE offset for the low priority UCI when multiplexing the low priority UCI with a positive high-priority SR of the one or more high-priority SRs.
  • Example 28 The method of any of examples 24-27, further comprising performing an operation of the base station based on the one or more high-priority SRs and low-priority UCI received from the wireless device.
  • Example 29 The method of any of the previous examples, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.
  • Example 30 A wireless device, the wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A examples; and power supply circuitry configured to supply power to the wireless device.
  • Example 31 A base station, the base station comprising: processing circuitry configured to perform any of the steps of any of the Group B examples; power supply circuitry configured to supply power to the base station.
  • Example 32 A user equipment (UE), the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A examples; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • Example 33 A computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A examples.
  • Example 34 A computer program product comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A examples.
  • Example 35 A non-transitory computer-readable storage medium or carrier comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A examples.
  • Example 36 A computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group B examples.
  • Example 37 A computer program product comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group B examples.
  • Example 38 A non-transitory computer-readable storage medium or carrier comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group B examples.
  • Example 39 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B examples.
  • UE user equipment
  • Example 40 The communication system of the pervious example further including the base station.
  • Example 41 The communication system of the previous 2 examples, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example 42 The communication system of the previous 3 examples, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • Example 43 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B examples.
  • UE user equipment
  • Example 44 The method of the previous example, further comprising, at the base station, transmitting the user data.
  • Example 45 The method of the previous 2 examples, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
  • Example 46 A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 examples.
  • UE user equipment
  • Example 47 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A examples.
  • UE user equipment
  • Example 48 The communication system of the previous example, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Example 49 The communication system of the previous 2 examples, wherein: the processing circuitry of the host computer is configured to execute a host application n, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • Example 50 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A examples.
  • a communication system including a host computer, a base station and a user equipment (UE)
  • the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A examples.
  • Example 51 The method of the previous example, further comprising at the UE, receiving the user data from the base station.
  • Example 52 A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A examples.
  • UE user equipment
  • Example 53 The communication system of the previous example, further including the UE.
  • Example 54 The communication system of the previous 2 examples, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • Example 55 The communication system of the previous 3 examples, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • Example 56 The communication system of the previous 4 examples, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing die user data in response to the request data.
  • Example 57 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A examples.
  • UE user equipment
  • Example 58 The method of the previous example, further comprising, at the UE, providing the user data to the base station.
  • Example 59 The method of the previous 2 examples, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.
  • Example 60 The method of the previous 3 examples, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.
  • Example 61 A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B examples.
  • UE user equipment
  • Example 62 The communication system of the previous example further including the base station.
  • Example 63 The communication system of the previous 2 examples, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example 64 The communication system of the previous 3 examples, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • Example 65 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A examples.
  • UE user equipment
  • Example 66 The method of the previous example, further comprising at the base station, receiving the user data from the UE.
  • Example 67 The method of the previous 2 examples, further comprising at the base station, initiating a transmission of the received user data to the host computer.
  • ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

Abstract

Un procédé exécuté par un dispositif sans fil consiste à déterminer (1202) qu'une ressource de canal de commande de liaison montante physique (PUCCH) permettant d'envoyer une ou plusieurs demandes de planification (SR) à haute priorité chevauche au moins partiellement dans le temps une ressource PUCCH permettant d'envoyer des informations de commande de liaison montante à basse priorité (UCI). Lorsqu'au moins une SR parmi la ou les SR à haute priorité est positive, le dispositif sans fil envoie (1204) les UCI à basse priorité en utilisant une ressource de liaison montante parmi une ou plusieurs premières ressources de liaison montante associées aux UCI à basse priorité, et lorsque toutes les SR à haute priorité sont négatives, le dispositif sans fil envoie (1204) les UCI à basse priorité en utilisant une seconde ressource de liaison montante associée aux UCI à basse priorité.
PCT/SE2021/051074 2020-10-23 2021-10-25 Procédés et systèmes de gestion de demandes de planification à haute priorité et d'informations de commande de liaison montante à basse priorité WO2022086433A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063104779P 2020-10-23 2020-10-23
US63/104,779 2020-10-23

Publications (1)

Publication Number Publication Date
WO2022086433A1 true WO2022086433A1 (fr) 2022-04-28

Family

ID=78463879

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/051074 WO2022086433A1 (fr) 2020-10-23 2021-10-25 Procédés et systèmes de gestion de demandes de planification à haute priorité et d'informations de commande de liaison montante à basse priorité

Country Status (1)

Country Link
WO (1) WO2022086433A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190246416A1 (en) * 2017-05-03 2019-08-08 Lg Electronics Inc. Method for transmitting and receiving scheduling request between terminal and base station in wireless communication system and device for supporting same
US20190306922A1 (en) * 2018-06-18 2019-10-03 Gang Xiong Methods to multiplex control information in accordance with multi-slot transmissions in new radio (nr) systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190246416A1 (en) * 2017-05-03 2019-08-08 Lg Electronics Inc. Method for transmitting and receiving scheduling request between terminal and base station in wireless communication system and device for supporting same
US20190306922A1 (en) * 2018-06-18 2019-10-03 Gang Xiong Methods to multiplex control information in accordance with multi-slot transmissions in new radio (nr) systems

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.313-G30
OPPO: "Summary#2 on UCI enhancements for URLLC", vol. RAN WG1, no. Reno, USA; 20190513 - 20190517, 17 May 2019 (2019-05-17), pages 1 - 20, XP051740050, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F97/Docs/R1%2D1907777%2Ezip> [retrieved on 20190517] *
SPREADTRUM COMMUNICATIONS: "Remaining details on short-PUCCH", vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), XP051441605, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/> [retrieved on 20180520] *

Similar Documents

Publication Publication Date Title
CN111869141B (zh) 用于对信道状态信息报告排优先级的系统和方法
US20220053532A1 (en) Methods of harq codebook determination for low latency communications
EP3695676B1 (fr) Uci sur pusch sans octroi
US20220394708A1 (en) Signaling of multi-trp schemes in a wireless communication system
EP3925111A1 (fr) Signalement de qualité de canaux en lte-m et en nb-iot
US20230024069A1 (en) Logical Channel Prioritization and Corresponding Uplink Grant
US11296825B2 (en) Configuration of additonal system information block repetitions
WO2020141996A1 (fr) Uci sur autorisation configurée
US20230362939A1 (en) Configuring uplink control channels
US20230388090A1 (en) Physical downlink control channel limit handling for enhanced cross-carrier scheduling
WO2022086433A1 (fr) Procédés et systèmes de gestion de demandes de planification à haute priorité et d&#39;informations de commande de liaison montante à basse priorité
US11240759B2 (en) PCFICH reliability using power boosting
WO2020204788A1 (fr) Alignement de ressources de deux technologies d&#39;accès radio
EP4042614A1 (fr) Séquence de rv pour pusch à segments multiples amélioré
EP4055760A1 (fr) Traitement de capacité associé à une indication de couche mimo par-bwp

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: 21801255

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21801255

Country of ref document: EP

Kind code of ref document: A1