EP3906743A1 - Uci sur autorisation configurée - Google Patents

Uci sur autorisation configurée

Info

Publication number
EP3906743A1
EP3906743A1 EP19907588.8A EP19907588A EP3906743A1 EP 3906743 A1 EP3906743 A1 EP 3906743A1 EP 19907588 A EP19907588 A EP 19907588A EP 3906743 A1 EP3906743 A1 EP 3906743A1
Authority
EP
European Patent Office
Prior art keywords
wireless device
pusch
uci
indicator
transmit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP19907588.8A
Other languages
German (de)
English (en)
Other versions
EP3906743A4 (fr
Inventor
Jonas FRÖBERG OLSSON
Ying Sun
Alexey SHAPIN
Yufei Blankenship
Majid GERAMI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3906743A1 publication Critical patent/EP3906743A1/fr
Publication of EP3906743A4 publication Critical patent/EP3906743A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • SPS semi-persistent scheduling
  • UL uplink
  • RRC Radio Resource Control
  • Type 2 is partly RRC configured and partly dynamically indicated.
  • the RRC information element for configuration of Configured grant look as follows, see 38.331 Section 6.3.2:
  • resourceAllocationTypeO resourceAllocationTypeO
  • resourceAllocationTypel resourceAllocationTypel
  • timeDomainOffset INTEGER (0..5119), timeDomainAllocation INTEGER (0..15), frequencyDomainAllocation BIT STRING (SIZE(18)), antennaPort INTEGER (0..31), dmrs-Seqlnitialization INTEGER (0..1)
  • the information in rrc-ConfiguredUplinkGrant is Type 1 -specific.
  • corresponding information is provided by configured grant activation Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • the activation DCI for configured grant is scrambled with Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI).
  • CS-RNTI Configured Scheduling-Radio Network Temporary Identifier
  • the CG-UCI-OnPUSCH indicate if Uplink Control Information (UCI) coding offsets relative to data for configured grant, which may include beta-offsets, are dynamically indicated or semi-static.
  • beta-offsets shall be semi-static.
  • UCI such as Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) and Channel State Information (CSI) can be transmitted together with data on the configured grant if higher layers (i.e., Medium Access Control (MAC)_ layer) deliver (to Physical (PHY)) a transport block to be transmitted.
  • MAC Medium Access Control
  • PHY Physical
  • the UE shall not transmit anything on the resources configured by
  • ConfiguredGrantConfig if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant.
  • a Scheduling Request is not allowed to be transmitted in UCI on Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • the UE will only send the SR on the PUCCH if the PUSCH transmission is without Uplink-Shared Channel (UL-SCH) (i.e., without data) (See, Section 9 in 3GPP TS 38.213):
  • a UE would transmit on a serving cell a PUSCH without UL-SCH that overlaps with a PUCCH transmission on the serving cell that includes positive SR information, the UE does not transmit the PUSCH.
  • the MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied:
  • the MAC entity is configured with skipUplinkTxDynamic and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant;
  • the MAC PDU includes zero MAC SDUs
  • the MAC PDU includes only the periodic BSR and there is no data
  • HARQ-ACK and/or CSI may be transmitted as UCI on the configured grant resource if timing permits.
  • a UE has a PUSCH transmission that overlaps with a PUCCH transmission that includes HARQ-ACK information and/or semi-persistent/periodic CSI and the conditions in Subclause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied, the UE multiplexes the HARQ-ACK information and/or the semi- persistent/periodic CSI in the PUSCH.
  • the UL-SCH indicator field may be used to explicitly indicate to the UE that requested CSI shall be sent without UL-SCH.
  • UL-SCH indicator - 1 bit A value of" 1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH.
  • a UE is not expected to receive a DCI format 0 1 with UL-SCH indicator of "0" and CSI request of all zero(s).
  • PUCCH supports single-port transmission only. Tx diversity schemes for PUCCH have been discussed but are not adopted in Rel-15. Since PUSCH supports multi antenna transmission up to four ports, there may be a pre-coding/beamforming gain by transmitting UCI on PUSCH compared to PUCCH.
  • a method is provided wherein a wireless device such as a User Equipment, as an example, configured to use CG is further indicated to transmit Uplink Control Information (UCI) comprising one or more of a Scheduling Request (SR), Hybrid Automatic Repeat Request- Acknowledgment (HARQ-ACK) and Channel State Information (CSI) on Physical Uplink Shared Channel (PUSCH) on configured grant resources even if Uplink-Shared Channel (UL-SCH) is not present.
  • UCI Uplink Control Information
  • SR Scheduling Request
  • HARQ-ACK Hybrid Automatic Repeat Request- Acknowledgment
  • CSI Channel State Information
  • a method by a wireless device includes receiving at least one configured grant for transmitting on a PUSCH.
  • UCI is transmitted on the PUSCH though the wireless device does not have UL-SCH data to transmit.
  • a wireless device includes processing circuitry configured to receive at least one configured grant for transmitting on a PUSCH and transmit UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.
  • a method by a base station includes transmitting, to a wireless device, at least one configured grant for transmitting on a PUSCH.
  • UCI is received on the PUSCH from the wireless device though the wireless device does not have UL-SCH data to transmit.
  • a base station includes processing circuitry configured to transmit, to a wireless device, at least one configured grant for transmitting on a PUSCH and receive UCI on the PUSCH from the wireless device though the wireless device does not have UL-SCH data to transmit.
  • one technical advantage may be that certain embodiments provide simplified scheduling. Specifically, where wireless devices such as UEs with CG perform all uplink (UL) transmissions on the CG resource(s), the scheduler only need to manage PUSCH resources for UEs scheduled by other means. As another example, a technical advantage may be that certain embodiments use the spectrum more efficiently since the UE only requires reserving PUSCH spectrum to transmit both Uplink-Shared Chanel (UL-SCH) data, Downlink HARQ Acknowledgment/Negative Acknowledgment (DL HARQ A/N) and CSI report. Physical Uplink Control Channel (PUCCH) resources can be used for other UE’s PUCCH/PUSCH transmissions.
  • UL-SCH Uplink-Shared Chanel
  • DL HARQ A/N Downlink HARQ Acknowledgment/Negative Acknowledgment
  • CSI report Physical Uplink Control Channel (PUCCH) resources can be used for other UE’s PUCCH/PUSCH transmissions.
  • Still another advantage may be that UCI transmission may be more reliable due to pre coding/beamforming gain for PUSCH as compared to PUCCH.
  • a technical advantage may be that for a PUSCH of Uplink Configured Grant (UL CG), it may be useful to multiplex SR to PUSCH, where the SR indicates the scheduling request of dynamically scheduled UL data.
  • UL CG Uplink Configured Grant
  • both the periodic and aperiodic traffic can be Enhanced Mobile BroadBand (eMBB) or Ultra-reliable low latency communication (URLLC) traffic.
  • eMBB Enhanced Mobile BroadBand
  • URLLC Ultra-reliable low latency communication
  • FIGURE 1 illustrates an example wireless network, according to certain embodiments
  • FIGURE 2 illustrates an example network node, according to certain embodiments
  • FIGURE 3 illustrates an example wireless device, according to certain embodiments
  • FIGURE 4 illustrate an example user equipment, according to certain embodiments
  • FIGURE 5 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 6 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 7 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 8 illustrates a method implemented in a communication system, according to one embodiment
  • FIGURE 9 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 10 illustrates another 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 an example method by a wireless device, according to certain embodiments
  • FIGURE 13 illustrates an exemplary virtual computing device, according to certain embodiments
  • FIGURE 14 illustrates another example method by a wireless device, according to certain embodiments.
  • FIGURE 15 illustrates another exemplary virtual computing device, according to certain embodiments.
  • FIGURE 16 illustrates an example method by a network node, according to certain embodiments
  • FIGURE 17 illustrates another exemplary virtual computing device, according to certain embodiments.
  • FIGURE 18 illustrates another example method by a network node, according to certain embodiments.
  • FIGURE 19 illustrates another exemplary virtual computing device, according to certain embodiments.
  • a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node.
  • network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi -standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc), O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT, test equipment (physical node or software), etc.
  • MSR multi -standard radio
  • RNC radio
  • the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.
  • terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.
  • the information element for configured grant (CG) comprises:
  • sym640xl 4, syml024xl4, syml280xl4, sym2560xl4, sym5120xl4, sym6, symlxl2, sym2xl2, sym4xl2, sym5xl2, sym8xl2, syml0xl2, syml6xl2, sym20xl2, sym32xl2,
  • sym40xl2 sym64xl2, sym80xl2, syml28xl2, syml 60x12, sym256xl2, sym320xl2, sym512xl2, sym640xl2,
  • pathlossReferencelndex INTEGER (O. maxNrofPUSCH- PathlossReferenceRSs-1),
  • UE may send UCI on PUSCH without UL-SCH on a CG resource.
  • the text in Section 6.1.2.3 of 3GPP TS 38.214 may be modified as highlighted:
  • the UE shall not transmit anything on the resources configured by ConfiguredGrantConflg if uciWithoutUL-SCH is false and if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant. Also the text in Section 5.4.3.1.3 of 3GPP TS 38.321 may be modified as highlighted: The MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied:
  • the MAC entity is configured with skipUplinkTxDynamic and uciWithoutUL- SCH is false and the grant indicated to the HARQ entity was addressed to a C- RNTI, or the grant indicated to the HARQ entity is a configured uplink grant;
  • the MAC PDU includes zero MAC SDUs
  • the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR.
  • UE may be indicated whether UCI on configured grant PUSCH is allowed is semi-persistently indicated to UE in activation DCI.
  • the field“UL-SCH indicator” may indicate:
  • Radio Resource Control Information Element (RRC IE) ConfiguredGrantConfig may comprise uciWithoutUL-SCH, which is used together with semi-persistent indication using the DCI field“UL-SCH indicator” in the activation DCI.
  • RRC IE Radio Resource Control Information Element
  • the CSI request field may not be all zero, indicating a request for the UE to transmit CSI. If CSI request field indicates a CSI trigger state with a semi-persistent CSI configuration then a value“0” may indicate that UCI with the semi- persistent CSI corresponding the indicated trigger state is allowed to be sent on configured grant resource without UL-SCH; otherwise it is not allowed.
  • uciWithoutUL- SCH in ConfiguredGrantConfig may indicate that SR and/or HARQ-ACK and/or periodic CSI is allowed on configured grant resource without UL-SCH while“UL-SCH indicator” together with CSI request field in activation DCI of the configured grant may indicate whether or not additionally semi-persistent CSI may be comprised in UCI on PUSCH without UL-SCH on the configured grant resource.
  • NR Rel-15 does not allow SR to be multiplexed onto PUSCH. Only HARQ-ACK and CSI reports can be multiplexed in a PUSCH. For a PUSCH of UL CG, it is useful to multiplex SR to PUSCH, where the SR indicates the scheduling request of dynamically scheduled UL data. This need exists whenever the UE has simultaneous periodic and aperiodic UL traffic. Here both the periodic and aperiodic traffic can be eMBB or URLLC traffic.
  • the following revision to Section“9.3 UCI reporting in physical uplink shared channel” of 3GPP TS 38.213 provides beta offset for SR, when the SR is multiplexed onto PUSCH.
  • the higher layer parameter betaOffsetSR can be added to RRC IE PUSCH- Config, in which case betaOffsetSR is applicable to both dynamically scheduled PUSCH and UL CG PUSCH.
  • higher layer parameter betaOffsetSR can be added to RRC IE ConfiguredGrantConfig so that it is applicable to UL CG PUSCH only.
  • Offset values are defined for a UE to determine a number of resources for multiplexing SR, HARQ-ACK information and for multiplexing CSI reports in a PUSCH.
  • the offset values are signalled to a UE either by a DCI format scheduling the PUSCH transmission or by higher layers.
  • DCI format 0 or DCI format 0 1 that does not include a beta offset indicator field, schedules the PUSCH transmission from the UE, the UE applies the S 03 ⁇ 4et
  • SR offset S 03 ⁇ 4et is configured to values according to Table 9.3-1.
  • Higher layer parameter betaOffsetSR provides index 7 ® set for the UE to use if the UE multiplexes SR onto PUSCH.
  • a DCI format 0 1 schedules the PUSCH transmission from the UE and if DCI format 0_1 includes a beta_offset indicator field, as configured by uci-OnPUSCH, the UE is provided by betaOffsetSR a set of four 7 0 ® et indexes, by each of
  • betaOffsetACK-Indexl ⁇ betaOffsetACK-Indexl , betaOffsetACK-Index2, betaOffsetACK-Index3 ⁇ a set of four indexes, by each of ⁇ betaOffsetCSI-Partl -Index 7, betaOffsetCSI-Partl- Index2 ⁇ a set of four iff indexes and by each of ⁇ betaOffs etCSI-P art 2-Index 1 , betaOffsetCSI-Part2-Index2 ⁇ a set of four iff indexes from Table 9.3-1 and 9.3-2, respectively, for multiplexing HARQ-ACK information, Part 1 CSI reports, and Part 2 CSI reports, respectively, in the PUSCH transmission.
  • the beta offset indicator field indicates a ACK value, a iff value and a iff value from the respective sets of values, with the mapping defined in Table 9.3-3.
  • uciWithoutUL-SCH can be configured for one or plurality of ConfiguredGrctntConfig.
  • different rules can be applied to choose one transmission opportunity, e.g. first or last transmission opportunity in the slot, other conditions are not precluded.
  • the gNb may avoid inter UE pre-emption or multiplexing if there is a possibility of sending UCI in PUSCH, because UCI reliability must be ensured. This may be done by a scheduler, and no standard change required. However, it may be beneficial for the UE if the network cannot expect inter UE pre emption for this transmission.
  • UE may send UCI on PUSCH without UL-SCH on configured grant resource only once, i.e., there would not be repetition for UCI.
  • higher layer parameter for example rep_UCI_K>l
  • repK > rep JCI K
  • FIGURE 1 illustrates a wireless network, in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in FIGURE 1.
  • the wireless network of FIGURE 1 only depicts network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c.
  • 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 wireless device (wireless device) 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 wireless device 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 2 illustrates an example network node, 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) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • 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., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • 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 the example wireless network of FIGURE 1 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., aNodeB component and aRNC 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 chips (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 chip 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 non-volatile 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.
  • volatile or non-volatile 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
  • 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. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190.
  • 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 wireless devices 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 wireless devices 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 190 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 2 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 maher 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 3 illustrates an example wireless device, according to certain embodiments.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term wireless device 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 wireless device may be configured to transmit and/or receive information without direct human interaction.
  • a wireless device 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 wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) 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 vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • 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 (L
  • a wireless device 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 wireless device 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 wireless device and/or a network node.
  • the wireless device 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 wireless device 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 wireless device 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 wireless device 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 wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 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.
  • Wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 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 wireless device 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 wireless device 110 and be connectable to wireless device 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 wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.
  • 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 114 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.
  • wireless device 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.
  • 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 wireless devices 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. In other embodiments, 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 wireless device 110 components, such as device readable medium 130, wireless device 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 wireless device 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 wireless device 110, but are enjoyed by wireless device 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 wireless device. 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 wireless device 110, 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 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, 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.
  • 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 wireless device 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 wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction may be via a touch screen; if wireless device 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 wireless device 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 wireless device 110, and to allow processing circuitry 120 to output information from wireless device 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.
  • wireless device 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 wireless devices. 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 wireless device 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to carry 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 wireless device 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.
  • an external power source e.g., an electricity outlet
  • wireless device 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 wireless device 110 to which power is supplied.
  • FIGURE 4 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 2200 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 4, is one example of a wireless device 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 wireless device and UE may be used interchangeable. Accordingly, although FIGURE 4 is a UE, the components discussed herein are equally applicable to a wireless device, 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 233, 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 4, 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/O), 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 synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • 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 wireless device, 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 5 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 6 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system 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.
  • 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 the 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 6 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.
  • FIGURE 7 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • 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 7) 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 7) 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.
  • processing circuitry 528 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 7 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 6, respectively.
  • the inner workings of these entities may be as shown in FIGURE 7 and independently, the surrounding network topology may be that of FIGURE 6.
  • 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, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/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 8 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 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 8 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.
  • step 620 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 9 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 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 9 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 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 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 10 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.
  • 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 11 is a flowchart illustrating a method 1000 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 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 11 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.
  • FIGURE 12 depicts a method by a wireless device, according to certain embodiments.
  • the wireless device receives at least one grant for transmitting on a PUSCH.
  • the wireless device transmits UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • the at least one grant includes an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • the wireless device may determine that the wireless device does not have UL-SCH data to transmit and, based on the indicator, determine that the wireless device is allowed to transmit UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • the UCI may include at least one of a SR, a HARQ-ACK, and CSI.
  • FIGURE 13 illustrates a schematic block diagram of a virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 1).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1).
  • Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 12 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 12 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 receiving module 1110, transmitting module 1120, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1110 may perform certain of the receiving functions of the apparatus 1100. For example, receiving module 1110 may receive at least one grant for transmitting on a PUSCH.
  • transmitting module 1120 may perform certain of the transmitting functions of the apparatus 1100. For example, transmitting module 1120 may transmit UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • FIGURE 14 depicts a method 1200 by a wireless device 110, according to certain embodiments.
  • wireless device 110 receives at least one CG for transmitting on a PUSCH.
  • the wireless device 110 transmits UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • the at least one CG comprises an indicator indicating that the wireless device 110 is to transmit the UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • the wireless device 110 determines that the wireless device 110 does not have UL-SCH data to transmit and, based on the indicator, determines that the wireless device 110 is allowed to transmit UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • the indicator comprises a uciWithoutUL-SCH indicator and the indicator is set to true.
  • the UCI includes at least channel state information (CSI). Additionally or alternatively, in a particular embodiment, the UCI includes at least one of a SR and a HARQ-ACK.
  • CSI channel state information
  • the UCI includes at least one of a SR and a HARQ-ACK.
  • the at least one CG comprises a Type 1 configured grant.
  • the at least one CG comprises a Type 2 configured grant.
  • the wireless device 110 receives an indicator with an activation of DCI.
  • the indicator indicates that the wireless device 110 is to transmit the UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • the indicator is indicated to and received by the wireless device, and wherein the indicator is received as a RRC IE.
  • wireless device 110 determines, based on the indicator, a type of UCI that the wireless device is permitted to transmit even though the wireless device does not have UL-SCH data to transmit, and the type of UCI includes at least one of a SR, a HARQ-ACK, and CSI.
  • the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, and the wireless device 110 determines that wireless device 110 is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one grant.
  • the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, and wireless device 110 determines that the wireless device 110 is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • the indicator is a value of 0 and all of the fields in a CSI request are set to zero, and wireless device 110 determines that the wireless device 110 is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • the indicator is a value of 1 and all of the fields in a CSI request are set to zero, and wireless device 110 determines that wireless device 110 is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter.
  • the beta offset parameter is received as a radio resource control information element associated with a PUSCH configuration.
  • the at least one CG comprises a plurality of CGs and the indicator applies to the plurality of CGs.
  • wireless device 110 determines that only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.
  • wireless device 110 determines that repetition of UCI is permitted a first number of times, determines that repetition of UL-SCH data is permitted a second number of times, determines that the second number of times is greater or equal to the first number of times, and transmits the UCI on the PUSCH without UL-SCH data the first number of times.
  • FIGURE 15 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 1).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1).
  • Apparatus 1300 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 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 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 receiving module 1310, transmitting module 1320, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1310 may perform certain of the receiving functions of the apparatus 1300. For example, receiving module 1310 may receive at least one CG for transmitting on a PUSCH.
  • transmitting module 1320 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module 1320 may transmit UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • 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.
  • FIGURE 16 depicts a method 1400 by a network node 160, according to certain embodiments.
  • the network node transmits, to a wireless device, at least one grant for transmitting on a PUSCH.
  • the network node receives, from the wireless device, UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • the network node may include a base station.
  • the at least one grant includes an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit and receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL-SCH.
  • the network node may transmit an indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.
  • the UCI may include at least one of a SR, a HARQ-ACK, and CSI.
  • FIGURE 17 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 1).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1).
  • Apparatus 1500 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 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 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 transmitting module 1510, receiving module 1520, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • transmitting module 1510 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1510 may transmit, to a wireless device, at least one grant for transmitting on a PUSCH.
  • receiving module 1520 may perform certain of the receiving functions of the apparatus 1500. For example, receiving module 1520 may receive, from the wireless device, UCI on the PUSCH even if the wireless device does not have UL- SCH data to transmit.
  • FIGURE 18 depicts a method 1600 by a network node 160 such as, for example, a base station, according to certain embodiments.
  • the network node 160 transmits, to a wireless device 110, at least one CG for transmitting on a PUSCH.
  • network node 160 receives, from wireless device 110, UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • the at least one CG includes an indicator indicating that the wireless device 110 is to transmit the UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL-SCH.
  • network node 160 transmits the indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.
  • the UCI comprises at least CSI. Additionally or alternatively, the UCI may include at least one of a SR and HARQ-ACK.
  • the at least one CG comprises a Type 1 CG.
  • the at least one CG comprises a Type 2 CG.
  • network node 160 transmits an indicator with an activation of DCI.
  • the indicator indicates that wireless device 110 is permitted to transmit the UCI on the PUSCH without UL-SCH data.
  • the indicator is indicated to wireless device 110, and the indicator is transmitted as a RRC IE.
  • the indicator indicates a type of UCE that the wireless device is permitted to transmit without UL-SCH data
  • the type of UCI includes at least one of a SR, a HARQ-ACK, and CSI.
  • the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, and wireless device 110 is permitted to send SR and/or HARQ- ACK and CSI on the PUSCH using at least one resource indicated in the at least one CG.
  • the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, and wireless device 110 is permitted to send SR and/or HARQ- ACK on the PUSCH using at least one resource indicated in the at least one CG.
  • the indicator is a value of 0 and all of the fields in a CSI request are set to zero, and wireless device 110 is permitted to send SR and/or HARQ- ACK on the PUSCH using at least one resource indicated in the at least one CG.
  • the indicator is a value of 1 and all of the fields in a C SI request are set to zero, and wireless device 110 is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one CG.
  • the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter.
  • network node 160 transmits, to the wireless device 110, the at least one beta offset parameter as a radio resource control information element associated with a PUSCH configuration.
  • the at least one CG comprises a plurality of CGs and the indicator applies to the plurality of CGs.
  • only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.
  • repetition of UCI is permitted a first number of times
  • repetition of UL-SCH data is permitted a second number of times.
  • the second number of times is greater or equal to the first number of times
  • the UCI is received on the PUSCH without UL-SCH data the first number of times.
  • FIGURE 19 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 1).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1).
  • Apparatus 1700 is operable to carry 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 1700. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1700 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 transmitting module 1710, receiving module 1720, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
  • transmitting module 1710 may perform certain of the transmitting functions of the apparatus 1700. For example, transmitting module 1710 may transmit, to a wireless device 110, at least one CG for transmitting on a PUSCH.
  • receiving module 1720 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1720 may receive, from wireless device 110, UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.
  • 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.
  • Example Embodiment 1 A method performed by a wireless device, the method comprising: receiving at least one grant for transmitting on a physical uplink shared channel (PUSCH); and transmitting uplink control information (UCI) on the PUSCH even if the wireless device does not have uplink-shared channel (UL-SCH) data to transmit.
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • Example Embodiment 2 The method of Embodiment 1, wherein the at least one grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • Example Embodiment 3 The method of Embodiment 2, further comprising: determining that the wireless device does not have UL-SCH data to transmit; and based on the indicator, determining that the wireless device is allowed to transmit UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • Example Embodiment 4 The method of any one of Embodiments 2 to 3, wherein the indicator comprises a uciWithoutUL-SCH indicator and wherein the is set to true.
  • Example Embodiment 5 The method of any one of Embodiments 1 to 4, wherein the UCI comprises at least one of: a scheduling request (SR); a hybrid automatic repeat request acknowledgement (HARQ-ACK); and channel state information (CSI).
  • Example Embodiment 6 The method of any one of Embodiments 1 to 5, wherein the at least one grant indicates an allocation of at least one resource for transmitting on the PUSCH, and the UCI is transmitted on the PUSCH using the at least one resource.
  • SR scheduling request
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • CSI channel state information
  • Example Embodiment 7 The method of any one of Embodiments 1 to 6, wherein the at least one grant comprises a Type 1 configured grant.
  • Example Embodiment 8 The method of any one of Embodiments 1 to 6, wherein the at least one grant comprises a Type 2 configured grant.
  • Example Embodiment 9 The method of Embodiment 8, further comprising receiving an indicator with an activation of downlink control information (DCI), the indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • DCI downlink control information
  • Example Embodiment 10 The method of Embodiment 9, wherein the indicator is semi-persistently indicated to and received by the wireless device.
  • Example Embodiment 11 The method of Embodiment 9, wherein the indicator is received as a radio resource control information element (RRC IE).
  • RRC IE radio resource control information element
  • Example Embodiment 12 The method of any one of Embodiments 10 to 11, further comprising: determining, based on the indicator, a type of UCI that the wireless device is permitted to transmit even if the wireless device does not have uplink-shared channel (UL- SCH) data to transmit.
  • UL- SCH uplink-shared channel
  • Example Embodiment 13 The method of Embodiment 12, wherein the type of UCI comprises at least one of a scheduling request (SR), a hybrid automatic repeat request acknowledgement (HARQ-ACK), and channel state information (CSI).
  • SR scheduling request
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • CSI channel state information
  • Example Embodiment 14 The method of Embodiment 13, wherein, when the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 15 The method of Embodiment 13, wherein, when the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 16 The method of Embodiment 13, wherein, when the indicator is a value of 0 and all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 17 The method of Embodiment 13, wherein, when the indicator is a value of 1 and all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 18 The method of any one of Embodiments 1 to 16, wherein the UCI comprises a scheduling request (SR), and the method further comprises: multiplexing the SR onto the PUSCH.
  • SR scheduling request
  • Example Embodiment 19 The method of Embodiment 18, wherein the SR is multiplexed onto the PUSCH based on a beta offset parameter.
  • Example Embodiment 20 The method of Embodiment 19, wherein the beta offset parameter is received as a radio resource control information element associated with a PUSCH configuration.
  • Example Embodiment 21 The method of Embodiment 2, wherein the at least one grant comprises a plurality of grants and the indicator applies to the plurality of grants.
  • Example Embodiment 22 The method of any one of Embodiments 1 to 21, further comprising determining, by the wireless device, that no inter UE preemption applies to the transmission of the UCI on the PUSCH.
  • Example Embodiment 23 The method of any one of Embodiments 1 to 22, further comprising determining, by the wireless device that only a single transmission of the UCI is allowed on the PUSCH without uL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.
  • Example Embodiment 24 The method of any one of Embodiments 1 to 22, further comprising: determining that repetition of UCI is permitted a first number of times; determining that repetition of UL-SCH data is permitted a second number of times; determining that the second number of times is greater or equal to the first number of times; and transmitting the UCI on the PUSCH without UL-SCH data the first number of times.
  • Example Embodiment 25 A method performed by a base station, the method comprising: transmitting, to a wireless device, at least one grant for transmitting on a physical uplink shared channel (PUSCH); and receiving, from the wireless device, uplink control information (UCI) on the PUSCH even if the wireless device does not have uplink-shared channel (UL-SCH) data to transmit.
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • Example Embodiment 26 The method of Embodiment 25, wherein the at least one grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.
  • Example Embodiment 27 The method of any one of Embodiments 25 to 26, wherein receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL- SCH.
  • Example Embodiment 28 The method of any one of Embodiments 26 to 27, further comprising transmitting an indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.
  • Example Embodiment 29 The method of any one of Embodiments 25 to 28, wherein the UCI comprises at least one of: a scheduling request (SR); a hybrid automatic repeat request acknowledgement (HARQ-ACK); and channel state information (CSI).
  • SR scheduling request
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • CSI channel state information
  • Example Embodiment 30 The method of any one of Embodiments 25 to 29, wherein the at least one grant indicates an allocation of at least one resource for transmitting on the PUSCH, and the UCI is transmitted on the PUSCH using the at least one resource.
  • Example Embodiment 31 The method of any one of Embodiments 25 to 30, wherein the at least one grant comprises a Type 1 configured grant.
  • Example Embodiment 32 The method of any one of Embodiments 25 to 30, wherein the at least one grant comprises a Type 2 configured grant.
  • Example Embodiment 33 The method of Embodiment 32, further comprising transmitting an indicator with an activation of downlink control information (DCI), the indicator indicating that the wireless device is permitted to transmit the UCI on the PUSCH without UL-SCH data.
  • DCI downlink control information
  • Example Embodiment 34 The method of Embodiment 33, wherein the indicator is semi-persistently indicated to the wireless device.
  • Example Embodiment 35 The method of Embodiment 33, wherein the indicator is transmitted as a radio resource control information element (RRC IE).
  • RRC IE radio resource control information element
  • Example Embodiment 36 The method of any one of Embodiments 33 to 35 wherein the indicator indicates a type of UCE that the wireless device is permitted to transmit without UL-SCH data.
  • Example Embodiment 37 The method of Embodiment 36, wherein the type of UCI comprises at least one of a scheduling request (SR), a hybrid automatic repeat request acknowledgement (HARQ-ACK), and channel state information (CSI).
  • SR scheduling request
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • CSI channel state information
  • Example Embodiment 38 The method of Embodiment 36, wherein, when the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 39 The method of Embodiment 36, wherein, when the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 40 The method of Embodiment 36, wherein, when the indicator is a value of 0 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 41 The method of Embodiment 36, wherein, when the indicator is a value of 1 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.
  • Example Embodiment 42 The method of any one of Embodiments 25 to 41, wherein the UCI comprises a scheduling request (SR) multiplexed onto the PUSCH.
  • SR scheduling request
  • Example Embodiment 43 The method of Embodiment 42, wherein the SR is multiplexed onto the PUSCH based on a beta offset parameter.
  • Example Embodiment 44 The method of Embodiment 43, further comprising transmitting, to the wireless device, the beta offset parameter as a radio resource control information element associated with a PUSCH configuration.
  • Example Embodiment 45 The method of Embodiment 26, wherein the at least one grant comprises a plurality of grants and the indicator applies to the plurality of grants.
  • Example Embodiment 46 The method of any one of Embodiments 25 to 45, wherein no inter UE preemption applies to the transmission of the UCI on the PUSCH.
  • Example Embodiment 47 The method of any one of Embodiments 25 to 46, wherein only a single transmission of the UCI is allowed on the PUSCH without uL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.
  • Example Embodiment 48 The method of any one of Embodiments 25 to 46, wherein: repetition of UCI is permitted a first number of times; repetition of UL-SCH data is permitted a second number of times; the second number of times is greater or equal to the first number of times; and the UCI is received on the PUSCH without UL-SCH data the first number of times.
  • Example Embodiment 49 A wireless device comprising: processing circuitry configured to perform any of the steps of any of Embodiments 1 to 24; and power supply circuitry configured to supply power to the wireless device.
  • Example Embodiment 50 A base station comprising: processing circuitry configured to perform any of the steps of any of Embodiments 25 to 48; and power supply circuitry configured to supply power to the wireless device.
  • a user equipment 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 Embodiments 1 to 24; 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 Embodiment 52 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 Embodiments 25 to 48.
  • UE user equipment
  • Example Embodiment 53 The communication system of the pervious embodiment further including the base station.
  • Example Embodiment 54 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 55 The communication system of the previous 3 embodiments, 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 Embodiment 56 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 Embodiments 25 to 48.
  • UE user equipment
  • Example Embodiment 57 The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
  • Example Embodiment 58. The method of the previous 2 embodiments, 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 Embodiment 59 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 embodiments.
  • UE user equipment
  • Example Embodiment 60 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 Embodiments 1 to 24.
  • 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 Embodiments 1 to 24.
  • UE user equipment
  • Example Embodiment 61 The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Example Embodiment 62 The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • Example Embodiment 63 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 Embodiments 1 to 24.
  • UE user equipment
  • Example Embodiment 64 The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
  • Example Embodiment 65 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 Embodiments 1 to 24.
  • UE user equipment
  • Example Embodiment 66 The communication system of the previous embodiment, further including the UE.
  • Example Embodiment 67 The communication system of the previous 2 embodiments, 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 Embodiment 68 The communication system of the previous 3 embodiments, 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 Embodiment 69 The communication system of the previous 4 embodiments, 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 the user data in response to the request data.
  • Example Embodiment 70 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 Embodiments 1 to 24.
  • UE user equipment
  • Example Embodiment 71 The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
  • Example Embodiment 72 The method of the previous 2 embodiments, 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 Embodiment 73 The method of the previous 3 embodiments, 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 Embodiment 74 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 Embodiments 25 to 48.
  • UE user equipment
  • Example Embodiment 75 The communication system of the previous embodiment further including the base station.
  • Example Embodiment 77 The communication system of the previous 3 embodiments, 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 Embodiment 78 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 Embodiments 1 to 24.
  • UE user equipment
  • Example Embodiment 79 The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
  • Example Embodiment 80 The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • gNB gNode B (a base station in NR; a Node B supporting NR and connectivity to NGC)

Abstract

La présente invention concerne un procédé mis en œuvre par un dispositif sans fil (110) qui comprend la réception d'au moins une autorisation configurée (CG) pour la transmission sur un canal partagé de liaison montante physique (PUSCH). Le dispositif sans fil transmet des informations de commande de liaison montante (UCI) sur le PUSCH, bien que le dispositif sans fil ne possède pas de données de canal partagé de liaison montante (UL-SCH) à transmettre.
EP19907588.8A 2019-01-04 2019-12-30 Uci sur autorisation configurée Pending EP3906743A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962788417P 2019-01-04 2019-01-04
PCT/SE2019/051346 WO2020141996A1 (fr) 2019-01-04 2019-12-30 Uci sur autorisation configurée

Publications (2)

Publication Number Publication Date
EP3906743A1 true EP3906743A1 (fr) 2021-11-10
EP3906743A4 EP3906743A4 (fr) 2023-01-04

Family

ID=71407226

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19907588.8A Pending EP3906743A4 (fr) 2019-01-04 2019-12-30 Uci sur autorisation configurée

Country Status (2)

Country Link
EP (1) EP3906743A4 (fr)
WO (1) WO2020141996A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022155387A1 (fr) * 2021-01-14 2022-07-21 Intel Corporation Multiplexage d'informations de commande de liaison montante 5g et 6g amélioré sur un canal partagé de liaison montante physique

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102130741B (zh) * 2010-11-09 2013-09-25 华为技术有限公司 一种信道质量信息的传输方法、基站及用户设备
WO2018038758A1 (fr) * 2016-08-23 2018-03-01 Intel IP Corporation Transmission d'informations de commande après autorisation de liaison montante

Also Published As

Publication number Publication date
EP3906743A4 (fr) 2023-01-04
WO2020141996A1 (fr) 2020-07-09

Similar Documents

Publication Publication Date Title
US11696278B2 (en) Methods, apparatus and computer-readable media related to semi-persistent scheduling configuration
US20220053532A1 (en) Methods of harq codebook determination for low latency communications
US20220166558A1 (en) Methods providing sidelink harq at access stratum and related wireless devices
US11937241B2 (en) UCI on grant-free PUSCH
US20230354432A1 (en) Random Access for Low-Complexity User Equipment
EP4138463A1 (fr) Codage de plmn efficace pour 5g
US11877284B2 (en) Integrated access and backhaul with reversed scheduling
EP3925111A1 (fr) Signalement de qualité de canaux en lte-m et en nb-iot
US20230024069A1 (en) Logical Channel Prioritization and Corresponding Uplink Grant
US11582775B2 (en) Methods of conveying buffer status with mixed critical and non-critical traffic
WO2020141996A1 (fr) Uci sur autorisation configurée
US11296825B2 (en) Configuration of additonal system information block repetitions
US20220006595A1 (en) Wireless Transmission with Aggregation Factor
US11916689B1 (en) HARQ feedback codebook for multicast and unicast
US20230180221A1 (en) Prioritization for scheduling request and physical uplink shared channel without logical channel association
WO2022086433A1 (fr) Procédés et systèmes de gestion de demandes de planification à haute priorité et d'informations de commande de liaison montante à basse priorité
EP4154672A1 (fr) Changement de configuration cp-pur demandé par un ue
EP4055760A1 (fr) Traitement de capacité associé à une indication de couche mimo par-bwp
WO2020165841A1 (fr) Configuration alignée pour un transfert intercellulaire sans canal d'accès aléatoire/changement de groupe de cellules secondaires
WO2020149773A1 (fr) Gestion optimisée de changement d'accès initié par une gestion de trafic

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210728

AK Designated contracting states

Kind code of ref document: A1

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

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

A4 Supplementary search report drawn up and despatched

Effective date: 20221206

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 1/16 20060101ALI20221130BHEP

Ipc: H04W 72/04 20090101ALI20221130BHEP

Ipc: H04W 72/14 20090101ALI20221130BHEP

Ipc: H04W 72/12 20090101AFI20221130BHEP