WO2020167196A1 - Transmission et réception d'informations de commande en liaison montante et/ou d'une demande de planification - Google Patents

Transmission et réception d'informations de commande en liaison montante et/ou d'une demande de planification Download PDF

Info

Publication number
WO2020167196A1
WO2020167196A1 PCT/SE2020/050042 SE2020050042W WO2020167196A1 WO 2020167196 A1 WO2020167196 A1 WO 2020167196A1 SE 2020050042 W SE2020050042 W SE 2020050042W WO 2020167196 A1 WO2020167196 A1 WO 2020167196A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
pucch
uci
cell group
wireless device
Prior art date
Application number
PCT/SE2020/050042
Other languages
English (en)
Inventor
Min Wang
Jan Christoffersson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020167196A1 publication Critical patent/WO2020167196A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks

Definitions

  • Examples of the present disclosure relate to transmitting and receiving uplink control information (UCI) and/or a scheduling request (SR).
  • UCI uplink control information
  • SR scheduling request
  • Next generation systems e.g. new radio, NR, or 5G
  • NR new radio
  • 5G Next generation systems
  • the traffic pattern associated with many use cases is expected to consist of short or long bursts of data traffic with varying lengths of waiting period in between (herein called inactive state).
  • inactive state e.g., inactive state
  • both license assisted access and standalone unlicensed operation are to be supported in 3GPP.
  • the procedure of PRACH transmission and/or SR transmission in unlicensed spectrum shall be investigated in 3GPP.
  • NR-U NR in unlicensed spectrum
  • LBT Listen Before Talk
  • 3GPP has defined a study item on NR-based Access to Unlicensed Spectrum (also referred to as NR-U).
  • LAA LTE License Assisted Access
  • NR-U also needs to support Dual Connectivity (DC) and standalone scenarios, where the MAC procedures including RACH and scheduling procedure on unlicensed spectrum are subject to Listen Before Talk (LBT) failures.
  • DC Dual Connectivity
  • LBT Listen Before Talk
  • DRS discovery reference signal
  • PSS/SSS PSS/SSS
  • PBCH PBCH
  • CSI-RS control channel transmission
  • PUCCH/PDCCH physical data channel
  • PUSCH/PDSCH physical data channel
  • uplink sounding reference signal such as SRS transmission
  • the Radio Resource Management (RRM) procedures in NR-U may be similar to LAA, since NR-U may aim to reuse LAA/eLAA/feLAA technologies as much as possible to handle the coexistence between NR-U and other legacy Radio Access Technologies (RATs).
  • RRM measurements and reports may use a special configuration procedure with respect to channel sensing and channel availability. For example, channel access/selection for LAA was an important aspect for co-existence with other RATs such as Wi-Fi, including using carriers that are congested with Wi-Fi traffic.
  • a User Equipment may measure Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) of the downlink radio channel, and provide measurement reports to its serving eNB/gNB. However, these measurements don’t reflect the interference strength on the carrier. Another metric, Received Signal Strength Indicator (RSSI), can serve such a purpose.
  • RSSI Received Signal Strength Indicator
  • some reports of RSRP or RSRP may be blocked, either due to that the reference signal transmission (DRS) is blocked in the downlink or that the measurement report is blocked in the uplink.
  • DRS reference signal transmission
  • a RSSI measurement timing configuration includes a measurement duration (e.g. 1-5 ms) and a period between measurements (e.g. ⁇ 40, 80, 160, 320, 640 ⁇ ms).
  • Listen-before-talk is designed for unlicensed spectrum co-existence with other RATs.
  • a radio device applies a clear channel assessment (CCA) check (i.e. channel sensing) before any transmission.
  • CCA clear channel assessment
  • the transmitter performs energy detection (ED) over a time period compared to a certain threshold (ED threshold) in order to determine if a channel is idle (i.e. if occupation of the channel by another transmitter is not detected) .
  • ED threshold energy detection
  • the transmitter performs a random back-off within a contention window before next CCA attempt.
  • ACK acknowledgement
  • the transmitter must wait a short period after each busy CCA slot before doing back-off (since the back-off is a random time which may be zero).
  • the transmitter is only allowed to perform transmission up to a maximum time duration (namely, the maximum channel occupancy time (MCOT)).
  • MCOT maximum channel occupancy time
  • a channel access priority based on the service type has been defined. For example, there are four LBT priority classes defined for differentiation of contention window sizes (CWS) and MCOT between services.
  • PCell primary cell
  • SCell secondary cell
  • the SCell carrying PUCCH will be associated with a number of SCells and they together constitute one PUCCH cell group. So, in order to transmit a Scheduling Request (SR) to indicate new data to be transmitted on an SCell, the SR is transmitted on the cell on which the PUCCH has been configured in the PUCCH cell group to which the SCell belongs.
  • SR Scheduling Request
  • DC Dual Connectivity
  • a UE can only be configured with one PUCCH SCell, i.e. the UE can support up to two PUCCH cell groups as shown in Figure 1 , which shows an example of configuration of PUCCH on a SCell with two PUCCH cell groups (CGs).
  • Each cell group (PUCCH cell groups 1 and 2) includes four cells.
  • the two cell groups are mutually exclusive and cross-carrier scheduling between cell groups (CGs) is not allowed.
  • the PUCCH channel is in the PCell, while the other cell group contains a PUCCH SCell.
  • the PUCCH channel for the other cell group is deployed in the PUCCH SCell.
  • NR unlicensed access In the NR unlicensed access (NR-U) work item defined for 3GPP Rel-16, NR unlicensed operation needs to support both standalone and DC scenarios meaning that both RACH and PUCCH-SR signaling need to be transmitted over unlicensed spectrum cells, since a NR-U cell may operate as a primary cell.
  • NR-U NR unlicensed access
  • a UE in Carrier Aggregation can be configured with up to two PUCCH cell groups.
  • the UCI information of an SCell is only transmitted on the PUCCH-SCell (or PCell) within the same PUCCH Cell group.
  • One aspect of the present disclosure provides a method performed by a wireless device.
  • the method comprises transmitting uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a second cell in a second PUCCH cell group, wherein the second PUCCH cell group is different to the first PUCCH cell group.
  • the method comprises transmitting uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group.
  • a further aspect of the present disclosure provides a method performed by a base station.
  • the method comprises receiving, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device, wherein the second PUCCH cell group is different to the first PUCCH cell group.
  • a still further aspect of the present disclosure provides a method performed by a base station.
  • the method comprises receiving, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group for the wireless device.
  • the wireless device comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the wireless device is operable to transmit uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a second cell in a second PUCCH cell group, wherein the second PUCCH cell group is different to the first PUCCH cell group.
  • the wireless device comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the wireless device is operable to transmit uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group.
  • the base station comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the base station is operable to receive, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device, wherein the first PUCCH cell group is different to the first PUCCH cell group.
  • the base station comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the base station is operable to receive, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group for the wireless device.
  • Another aspect of the present disclosure provides a wireless device configured to transmit uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a second cell in a second PUCCH cell group, wherein the second PUCCH cell group is different to the first PUCCH cell group.
  • UCI uplink control information
  • SR scheduling request
  • Another aspect of the present disclosure provides a wireless device configured to transmit uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group.
  • UCI uplink control information
  • SR scheduling request
  • Another aspect of the present disclosure provides a base station configured to receive, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device, wherein the first PUCCH cell group is different to the first PUCCH cell group.
  • a base station configured to receive, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device, wherein the first PUCCH cell group is different to the first PUCCH cell group.
  • Another aspect of the present disclosure provides a base station configured to receive, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group for the wireless device.
  • Figure 1 shows an example of configuration of PUCCH on a SCell with two PUCCH cell groups
  • Figure 2 is a flow chart of an example of a method performed by a wireless device
  • Figure 3 is a flow chart of an example of another method performed by a wireless device
  • Figure 4 is a flow chart of an example of a method performed by a base station
  • Figure 5 is a flow chart of an example of another method performed by a base station
  • Figure 6 shows an example of a wireless network in accordance with some embodiments
  • FIG. 7 shows an example of a User Equipment (UE) in accordance with some embodiments
  • Figure 8 is a schematic block diagram illustrating a virtualization environment in accordance with some embodiments.
  • Figure 9 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • Figure 10 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments
  • FIG. 11 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 12 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 13 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 14 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and Figure 15 illustrates a schematic block diagram of virtualization apparatus in accordance with some embodiments.
  • Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a method is proposed on how to enhance PUCCH signaling transmission (e.g. Uplink Control Information, UCI, which may comprise or include scheduling request(s)) to overcome LBT failures for a UE in a carrier aggregation scenario where one or multiple serving cells are deployed on unlicensed spectrum (e.g. are using unlicensed spectrum).
  • UCI Uplink Control Information
  • the UE is allowed to perform PUCCH transmissions across PUCCH cell groups for UCI and SR signalling.
  • the UE may transmit UCI and SR of a serving cell in one cell group on a serving cell within the other cell group.
  • the transmission can be performed on PUSCH, PUCCH, or RACH.
  • the UCI may be extended to include one or more new fields to indicate information such as for example the index of cell group, triggered SR events and/or the associated PUCCH SR configurations/LCHs/LCGs/services, etc.
  • the UE may be configured with separate PUCCH resources in a cell group for transmission of PUCCH signaling intended for other cell groups.
  • the UE can trigger a RACH SR in the other cell group if the UE has experienced high channel occupancy and/or LBT failures in a cell group so that the PUCCH-SR transmission is subjected to LBT failures in that cell group.
  • Proposed methods may in some examples be enabled or disabled by the network for a UE based on measured channel occupancy or LBT statistics.
  • this disclosure provides a method performed by a wireless device, the method comprising transmitting uplink control information (UCI) for a first cell in a first physical uplink control channel (PUCCH) cell group on a second cell in a second PUCCH cell group.
  • UCI uplink control information
  • this disclosure provides a method performed by a base station, the method comprising receiving, from a wireless device, uplink control information (UCI) for a first cell in a first physical uplink control channel (PUCCH) cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device.
  • UCI uplink control information
  • PUCCH physical uplink control channel
  • Certain embodiments may provide one or more of the following technical advantage(s). For example, in some embodiments, additional transmission opportunities are provided for PUCCH signaling (e.g., UCI and SR). Additionally or alternatively, in some embodiments, there may be no need to extend the maximum number of PUCCH cell groups for a UE in CA can support, so that standardization efforts may be minimized, especially for the PUSCH based alternative.
  • PUCCH signaling e.g., UCI and SR
  • FIG. 2 is a flow chart of an example of a method 200 performed by a wireless device.
  • the method 200 comprises, in step 202, transmitting uplink control information (UCI) and/or a scheduling request (SR) for a first cell in a first physical uplink control channel (PUCCH) cell group on a second cell in a second PUCCH cell group, wherein the second PUCCH cell group is different to the first PUCCH cell group.
  • the UCI may comprise for example one or more scheduling requests (SRs), or the SR(s) may be transmitted separately from the UCI, and/or the UCI may comprise any other uplink control information.
  • the UCI and/or SR may be for the first cell (e.g. may otherwise be transmitted on a PUCCH on the first cell), or may be for multiple cells (e.g. all cells) in the first PUCCH cell group.
  • the UCI and/or SR may be transmitted on a second cell (in the same or different PUCCH cell group to the first cell).
  • the method may comprise transmitting the UCI and/or SR in a PUCCH on the second cell, in a physical uplink shared channel (PUSCH) on the second cell, a MAC control element (CE) on the second cell and/or in a Radio Resource Control (RRC) message on the second cell.
  • PUSCH physical uplink shared channel
  • CE MAC control element
  • RRC Radio Resource Control
  • the method may comprise comprising transmitting an indication of the first PUCCH cell group on the second cell. That is, for example, the indication may identify that the UCI and/or SR is associated with at least the first cell in the first PUCCH cell group, and may identify that the UCI and/or SR is associated with all of the cells in the first PUCCH cell group.
  • the UCI and/or SR may for example include the indication of the first PUCCH cell group.
  • the indication may for example indicate that the UCI is for at least the first cell in the first PUCCH cell group.
  • the UCI may include a scheduling request (SR), and the method may comprise transmitting an indication of a trigger event associated with the scheduling request on the second cell. Additionally or alternatively, the method may comprise transmitting an indication of PUCCH scheduling request configurations, logical channel groups (LCGs) and/or services associated with the scheduling request.
  • SR scheduling request
  • the method may comprise transmitting an indication of PUCCH scheduling request configurations, logical channel groups (LCGs) and/or services associated with the scheduling request.
  • LCGs logical channel groups
  • the method may comprise transmitting the UCI and/or SR in a predetermined time and/or frequency resource on the second cell, wherein the predetermined time and/or frequency resource is associated with the UCI and/or SR for at least the first cell. That is, for example, the UCI and/or SR transmitted in those resource(s) may indicate that the UCI is for a particular cell or cell group. As a result, in some examples, a separate indication to indicate the cell or cell group to which the UCI applies may not be needed.
  • the UCI and/or SR may in some examples comprise UCI and/or SR for at least one other cell in the first PUCCH cell group.
  • the first PUCCH cell group includes multiple cells including the first cell, and the UCI and/or SR may be for some or all of those cells.
  • the method comprises receiving a message from a base station associated with the first PUCCH cell group and/or the second PUCCH cell group, and wherein transmitting the UCI and/or SR for the first cell on the second cell in the second PUCCH cell group is performed in response to the message.
  • the method may comprise, before receiving the message, transmitting the UCI and/or SR for the first cell on a cell in the first PUCCH cell group.
  • the message may therefore be considered for example as an instruction from the base station to the wireless device to transmit the UCI and/or SR across the PUCCH cell groups, i.e. in the second cell in the second PUCCH cell group.
  • the message is received in response to sending a measurement of channel occupancy for a cell (e.g. the first cell) in the first PUCCH cell group and/or a number of failures of Listen Before Talk (LBT) on a cell (e.g. the first cell) in the first PUCCH cell group.
  • the measurement may for example indicate high occupancy or a high number or rate of LBT failures, and thus may prompt the base station to send an instruction to the wireless device to transmit the UCI and/or SR across PUCCH cell groups.
  • the message may be received in response to channel occupancy for a cell in the first PUCCH cell group being above a first threshold and/or a number of failures of Listen Before Talk (LBT) on a cell in the first PUCCH cell group being above a second threshold.
  • LBT Listen Before Talk
  • the message may be received in the absence of sending measurements or other reports to the base station, for example where the base station receives channel occupancy or LBT failure information from another source or derives the information itself.
  • At least one cell in the first PUCCH cell group uses unlicensed spectrum.
  • the first cell uses unlicensed spectrum. That is, for example, at least some (or all) of the bandwidth used by or allocated to the cell resides in unlicensed spectrum. In some examples, some or all of the cells of the first PUCCH cell group uses unlicensed spectrum.
  • each cell in the first and second PUCCH cell groups is associated with a respective carrier.
  • the method may comprise transmitting second UCI and/or SR for at least one cell in the second PUCCH cell group on the second cell. That is, for example, the UCI and/or SR and the second UCI and/or SR may be transmitted on the same cell, for example in the same PUCCH on the second cell.
  • the at least one cell in the second PUCCH cell group may for example include the second cell.
  • the first PUCCH cell group may in some examples comprise or include one of a primary cell (PCell) and a secondary cell (SCell) for the wireless device, and the second PUCCH cell group comprises or includes the other of the PCell and the SCell for the wireless device.
  • the method comprises using Carrier Aggregation (CA) for the first PUCCH cell group and the second PUCCH cell group. That is, for example, at least one cell from one group may be considered as a primary cell (PCell) and at least one cell from the other group may be considered as a secondary cell (SCell) for carrier aggregation purposes.
  • CA Carrier Aggregation
  • the first PUCCH cell group may comprise at least one cell including the first cell
  • the second PUCCH cell group comprises at least one cell including the second cell.
  • transmitting the UCI and/or SR comprises transmitting the UCI and/or SR to a base station associated with at least one cell in the first PUCCH cell group and/or at least one cell in the second PUCCH cell group. That is, for example, the base station is the base station for the cells, which may include the first cell and/or the second cell.
  • the base station may be a gNB in some examples.
  • the first PUCCH cell group is the same as the second PUCCH cell group. However, in other examples, the first PUCCH cell group is different to the second PUCCH cell group, e.g. cross-PUCCH cell group UCI and/or SR signalling.
  • the first cell is different to the second cell.
  • Figure 3 is a flow chart of an example of another method 300 performed by a wireless device.
  • the method comprises, in step 302, transmitting uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group.
  • the UCI includes the SR
  • the method 300 comprises transmitting an indication of a trigger event associated with the SR on the second cell.
  • the method 300 comprises transmitting the UCI and/or SR in a predetermined time and/or frequency resource on the second cell, wherein the predetermined time and/or frequency resource is associated with the UCI and/or SR for at least the first cell.
  • the UCI and/or SR may in some examples comprise UCI and/or SR for at least one other cell in the first PUCCH cell group.
  • At least one cell in the first PUCCH cell group uses unlicensed spectrum, and/or the first cell uses unlicensed spectrum.
  • the UCI and/or SR may in some examples be for all cells in the first PUCCH cell group
  • FIG. 4 is a flow chart of an example of a method 400 performed by a base station is provided.
  • the method comprises, in step 402, receiving, from a wireless device, uplink control information (UCI) and/or a scheduling request (SR) for a first cell in a first physical uplink control channel (PUCCH) cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device, wherein the second PUCCH cell group is different to the first PUCCH cell group.
  • the method performed by the base station may be performed as a counterpart to the method performed by the wireless device as described above.
  • the method comprises receiving the UCI and/or SR in a PUCCH on the second cell, in a physical uplink shared channel (PUSCH) on the second cell, in a MAC control element (CE) on the second cell and/or in a Radio Resource Control (RRC) message on the second cell.
  • PUSCH physical uplink shared channel
  • CE MAC control element
  • RRC Radio Resource Control
  • the method comprises receiving an indication of the first PUCCH cell group on the second cell.
  • the indication may indicate that the UCI and/or SR is associated with at least one cell in the first PUCCH cell group, such as the first cell.
  • the UCI and/or SR may include the indication of the first PUCCH cell group.
  • the indication may indicate that the UCI is for at least the first cell in the first PUCCH cell group.
  • the indication may be received from the wireless device.
  • the UCI and/or SR includes a scheduling request
  • the method comprises receiving, from the wireless device, an indication of a trigger event associated with the scheduling request on the second cell.
  • the UCI includes a scheduling request
  • the method comprises receiving, from the wireless device, an indication of PUCCH scheduling request configurations, logical channel groups (LCGs) and/or services associated with the scheduling request.
  • PUCCH scheduling request configurations e.g., PUCCH scheduling request configurations
  • LCGs logical channel groups
  • the method comprises receiving the UCI and/or SR in a predetermined time and/or frequency resource on the second cell, wherein the predetermined time and/or frequency resource is associated with UCI and/or SR for at least the first cell and/or UCI and/or SR from the wireless device.
  • the UCI and/or SR comprises UCI and/or SR for the wireless device and/or at least one other cell in the first PUCCH cell group.
  • the method may comprise sending a message to the wireless device to cause the wireless device to transmit the UCI and/or SR for the first cell on the second cell in the second PUCCH cell group.
  • the message could be considered for example as an instruction for the wireless device to transmit UCI and/or SR across PUCCH cell groups.
  • the method may therefore comprise, for example, before receiving the message, receiving, from the wireless device, the UCI and/or SR for the first cell on a cell in the first PUCCH cell group.
  • the message is sent in response to receiving, from the wireless device, a measurement of channel occupancy for a cell in the first PUCCH cell group and/or a number of failures of Listen Before Talk (LBT) on a cell in the first PUCCH cell group.
  • the message is sent in response to channel occupancy for a cell in the first PUCCH cell group being above a first threshold and/or a number of failures of Listen Before Talk (LBT) on a cell in the first PUCCH cell group being above a second threshold (as determined, for example, from a measurement from the wireless device or otherwise).
  • the cell in the first PUCCH cell group comprises the first cell.
  • At least one cell in the first PUCCH cell group may use unlicensed spectrum.
  • all cell groups in the first PUCCH cell group may use unlicensed spectrum.
  • the method comprises receiving, from the wireless device, second UCI and/or SR for at least one cell in the second PUCCH cell group on the second cell.
  • the at least one cell in the second PUCCH cell group includes the second cell.
  • the UCI and/or SR is for at least one further cell in the first PUCCH cell group and for the wireless device.
  • the UCI and/or SR is for all cells in the first PUCCH cell group and for the wireless device.
  • the first PUCCH cell group comprises or includes one of a primary cell (PCell) and a secondary cell (SCell) for the wireless device
  • the second PUCCH cell group comprises or includes the other of the PCell and the SCell for the wireless device.
  • the method comprises comprising using Carrier Aggregation (CA) for the first PUCCH cell group and the second PUCCH cell group.
  • CA Carrier Aggregation
  • the first PUCCH cell group comprises at least one cell including the first cell
  • the second PUCCH cell group comprises at least one cell including the second cell.
  • the first PUCCH cell group is the same as the second PUCCH cell group. However, in other examples, the first PUCCH cell group is different to the second PUCCH cell group.
  • the first cell is different to the second cell.
  • Figure 5 is a flow chart of an example of another method 500 performed by a base station.
  • the method comprises receiving, from a wireless device, uplink control information, UCI, and/or a scheduling request, SR, for a first cell in a first physical uplink control channel, PUCCH, cell group for the wireless device on a physical uplink shared channel, PUSCH, on a second cell in the first PUCCH cell group for the wireless device.
  • uplink control information UCI
  • SR scheduling request
  • the UCI includes the SR
  • the method 500 comprises receiving, from the wireless device, an indication of a trigger event associated with the scheduling request on the second cell.
  • the method 500 may in some examples comprise receiving the UCI and/or SR in a predetermined time and/or frequency resource on the second cell, wherein the predetermined time and/or frequency resource is associated with the UCI and/or SR for at least the first cell and/or UCI and/or SR from the wireless device
  • At least one cell in the first PUCCH cell group uses unlicensed spectrum, and/or the first cell uses unlicensed spectrum.
  • the UCI and/or SR is for all cells in the first PUCCH cell group.
  • NR-U NR unlicensed spectrum
  • a UE in carrier aggregation (CA) configured with one or more serving cells on unlicensed spectrum, is configured to transmit PUCCH control signaling (e.g., including uplink control information (UCI) and scheduling request (SR) etc) for a first cell on a second cell upon detection of high channel occupancy or high occurrence of LBT failures in the first cell.
  • the second cell may be a cell configured with PUCCH channel, or a cell without PUCCH channel configured.
  • the second cell may or may not belong to the same PUCCH Cell group with the first cell.
  • the PUCCH control signaling (such as UCI and SR etc) for the first cell is transmitted on PUSCH of the second cell.
  • the UCI may for example be extended as suggested below:
  • an indicator of the PUCCH cell group is added to the UCI fields, so that the PUCCH cell group which is associated with the reported UCI information can be indicated.
  • the indicator can be for example an index of the PUCCH cell group.
  • a single bit indicator may be defined for indication of PUCCH cell group.
  • the bit with the value“1” indicates the PUCCH cell group which includes the PCell, while the value“0” indicates the PUCCH cell group which doesn’t include the PCell.
  • the bit with the value“1” indicates the PUCCH cell group which doesn’t include the PCell, while the value“0” indicates the PUCCH cell group which includes the PCell.
  • the indicator(s) may be able to carry/indicate at least one of the following information:
  • the indicator may be able to indicate all these triggered SR events for multiple PUCCH SR configurations in a single extended UCI.
  • the transmission of PUCCH signaling (e.g., UCI and SR) on PUSCH may be performed in several ways such as
  • the PUCCH control signaling (such as UCI and SR etc) for the first cell is transmitted on PUCCH of the second cell.
  • PUCCH cell group there may be more than one cell configured with a PUCCH channel.
  • the second cell and the first cell may alternatively belong to different PUCCH cell groups, in which case there may be separate PUCCH control resources (in frequency domain and/or time domain) configured for a UE in one cell group intended for other cell groups.
  • the base station e.g. gNB
  • the base station e.g. gNB
  • the base station knows which cell group and which serving cell is associated with the received PUCCH control signaling, e.g. due to the particular time and/or frequency resource in which the signaling is received.
  • one or more indicators may additionally or alternatively be added to the UCI to indicate the associated PUCCH cell group.
  • a UE is experiencing high channel occupancy and/or high occurrence of LBT failures in one serving cell for PUCCH SR.
  • the UE is configured to transmit/trigger a RACH SR in the other serving cell.
  • the transmission on that cell may get through.
  • That cell may or may not belong to the same PUCCH cell group with the original serving cell where the PUCCH SR is triggered.
  • the function of transmission of PUCCH signaling (e.g., including UCI and SR etc) across PUCCH cell groups may be configured per UE. Therefore, a new UE capability bit may be introduced accordingly.
  • the function may be further configured per LCH/CG/service.
  • the configuration may be signaled for example via RRC signaling, MAC CE, or DCI based signaling.
  • the function of transmission of PUCCH signaling may be enabled or disabled by the base station (e.g. gNB) based on measured channel occupancy and/or LBT failure statistics.
  • the base station e.g. gNB
  • the function is enabled for a UE, while if the measured channel occupancy is below another given threshold (which could be the same or different), the function is disabled.
  • the measurement of channel occupancy may be collected every configured time period.
  • the function is enabled for a UE, while if the measured number of LBT failures is below another given threshold (which is the same or different), the function is disabled.
  • the measurement of LBT failures occupancy may be collected every configured time period.
  • a wireless network such as the example wireless network illustrated in Figure 6.
  • the wireless network of Figure 6 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ1 10, QQ1 10b, and QQ110c.
  • 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 QQ160 and wireless device (WD) QQ1 10 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.1 1 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 QQ106 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 QQ160 and WD QQ1 10 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.
  • 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 QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.
  • network node QQ160 illustrated in the example wireless network of Figure 6 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 QQ160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node QQ160 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 QQ160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, 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 QQ160.
  • Processing circuitry QQ170 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 QQ170 may include processing information obtained by processing circuitry QQ170 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 QQ170 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 QQ170 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 QQ160 components, such as device readable medium QQ180, network node QQ160 functionality.
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry QQ170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 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 QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units
  • some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 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 00170.
  • 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
  • Device readable medium QQ180 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 QQ170 and, utilized by network node QQ160.
  • Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ1 10. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 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
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 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 QQ162, interface QQ190, and/or processing circuitry QQ170 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 QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160.
  • network node QQ160 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 QQ187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. 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 QQ160 may include additional components beyond those shown in Figure 6 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • 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 WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (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 WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device QQ1 10 includes antenna QQ11 1 , interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137.
  • WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ1 10, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ1 10.
  • Antenna QQ11 1 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114.
  • antenna QQ11 1 may be separate from WD QQ1 10 and be connectable to WD QQ110 through an interface or port.
  • Antenna QQ1 11 , interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna QQ11 1 may be considered an interface.
  • interface QQ114 comprises radio front end circuitry QQ1 12 and antenna QQ11 1.
  • Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116.
  • Radio front end circuitry QQ1 14 is connected to antenna QQ11 1 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ11 1 and processing circuitry QQ120.
  • Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ1 11.
  • WD QQ1 10 may not include separate radio front end circuitry QQ1 12; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ11 1.
  • Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ1 12 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ1 18 and/or amplifiers QQ1 16. The radio signal may then be transmitted via antenna QQ1 11.
  • antenna QQ1 11 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112.
  • the digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ1 10 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ1 10 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ114.
  • RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ1 10, but are enjoyed by WD QQ1 10 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 QQ130 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 QQ120.
  • Device readable medium QQ130 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 QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ1 10. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ1 10. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ1 10. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 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 QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ1 10, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 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 QQ132 is also configured to allow output of information from WD QQ1 10, and to allow processing circuitry QQ120 to output information from WD QQ110.
  • User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ1 10 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 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 QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
  • Figure 7 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 QQ2200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE QQ200 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 7 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ21 1 , memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof.
  • Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure 7, 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 QQ201 may be configured to process computer instructions and data.
  • Processing circuitry QQ201 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 QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE QQ200 may be configured to use an output device via input/output interface QQ205.
  • 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 QQ200.
  • 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 QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.
  • 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 QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a.
  • Network QQ243a 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 QQ243a may comprise a Wi-Fi network.
  • Network connection interface QQ21 1 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 QQ211 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 QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 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 QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201.
  • ROM QQ219 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 QQ221 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 QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227.
  • Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium QQ221 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 QQ221 may allow UE QQ200 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 QQ221 , which may comprise a device readable medium.
  • processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231.
  • Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
  • Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b.
  • communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.1 1 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem QQ231 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 QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network QQ243b 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 QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
  • communication subsystem QQ231 may be configured to include any of the components described herein.
  • processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.
  • 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.
  • FIG 8 is a schematic block diagram illustrating a virtualization environment QQ300 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 QQ300 hosted by one or more of hardware nodes QQ330. 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 functions may be implemented by one or more applications QQ320 (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 QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment QQ300 comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, 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 QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360.
  • Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360.
  • Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
  • processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
  • hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 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) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
  • CPE customer premise equipment
  • 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 QQ340 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 QQ340, and that part of hardware QQ330 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 QQ340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225.
  • Radio units QQ3200 may communicate directly with hardware nodes QQ330 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 QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
  • a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411 , such as a radio access network, and core network QQ414.
  • Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c.
  • Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415.
  • a first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c.
  • a second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491 , QQ492 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 QQ412.
  • Telecommunication network QQ410 is itself connected to host computer QQ430, 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 QQ430 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 QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420.
  • Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 9 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430.
  • the connectivity may be described as an over-the-top (OTT) connection QQ450.
  • Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411 , core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications.
  • base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491.
  • base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.
  • host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500.
  • Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities.
  • processing circuitry QQ518 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 QQ510 further comprises software QQ511 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518.
  • Software QQ51 1 includes host application QQ512.
  • Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
  • Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530.
  • Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 10) served by base station QQ520.
  • Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510.
  • Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 10) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
  • Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, 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 QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532.
  • Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510.
  • an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510.
  • client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data.
  • OTT connection QQ550 may transfer both the request data and the user data.
  • Client application QQ532 may interact with the user to generate the user data that it provides.
  • host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 10 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure 9, respectively.
  • the inner workings of these entities may be as shown in Figure 10 and independently, the surrounding network topology may be that of Figure 9.
  • OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, 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 QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 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 QQ570 between UE QQ530 and base station QQ520 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 QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the transmission efficiency and/or reliability and thereby provide benefits such as improved network usage and/or connectivity.
  • 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 QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both.
  • sensors may be deployed in or in association with communication devices through which OTT connection QQ550 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 QQ51 1 , QQ531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
  • FIG. 1 1 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 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 1 1 will be included in this section.
  • the host computer provides user data.
  • substep QQ61 1 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application.
  • step QQ620 the host computer initiates a transmission carrying the user data to the UE.
  • step QQ630 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 QQ640 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 12 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 QQ730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG. 13 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 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • step QQ810 the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data.
  • substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application.
  • substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 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.
  • FIG 14 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 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 14 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 QQ930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • Figure 15 illustrates a schematic block diagram of an apparatus WW00 in a wireless network (for example, the wireless network shown in Figure 6).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 6).
  • Apparatus WW00 is operable to carry out the example method described with reference to Figure 2 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 2 is not necessarily carried out solely by apparatus WW00. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus WW00 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.
  • apparatus WWOO includes transmitting unit WW02 that is configured to transmit uplink control information (UCI and/or SR) for a first cell in a first physical uplink control channel (PUCCH) cell group on a second cell in a second PUCCH cell group.
  • UCI and/or SR uplink control information
  • PUCCH physical uplink control channel
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a method performed by a wireless device comprising:
  • uplink control information (UCI and/or SR) for a first cell in a first physical uplink control channel (PUCCH) cell group on a second cell in a second PUCCH cell group.
  • UCI and/or SR uplink control information
  • PUSCH physical uplink shared channel
  • SR is for at least the first cell in the first PUCCH cell group.
  • the method comprises transmitting an indication of PUCCH scheduling request configurations, logical channel groups (LCGs) and/or services associated with the scheduling request.
  • LCGs logical channel groups
  • the method of any of embodiments 1 to 10, comprising transmitting the UCI and/or SR in a predetermined time and/or frequency resource on the second cell, wherein the predetermined time and/or frequency resource is associated with UCI and/or SR for at least the first cell.
  • the method of embodiment 13, comprising, before receiving the message, transmitting the UCI and/or SR for the first cell on a cell in the first PUCCH cell group.
  • LBT Listen Before Talk
  • the first PUCCH cell group comprises or includes one of a primary cell (PCell) and a secondary cell (SCell) for the wireless device
  • the second PUCCH cell group comprises or includes the other of the PCell and the SCell for the wireless device.
  • the method of any of embodiments 1 to 25, comprising using Carrier Aggregation (CA) for the first PUCCH cell group and the second PUCCH cell group.
  • CA Carrier Aggregation
  • transmitting the UCI and/or SR comprises transmitting the UCI and/or SR to a base station associated with at least one cell in the first PUCCH cell group and/or at least one cell in the second PUCCH cell group.
  • a method performed by a base station comprising:
  • uplink control information (UCI and/or SR) for a first cell in a first physical uplink control channel (PUCCH) cell group for the wireless device on a second cell in a second PUCCH cell group for the wireless device.
  • UCI and/or SR uplink control information
  • PUCCH physical uplink control channel
  • the method comprises receiving, from the wireless device, an indication of PUCCH scheduling request configurations, logical channel groups (LCGs) and/or services associated with the scheduling request.
  • LCGs logical channel groups
  • any of embodiments 34 to 44 comprising receiving the UCI and/or SR in a predetermined time and/or frequency resource on the second cell, wherein the predetermined time and/or frequency resource is associated with UCI and/or SR for at least the first cell and/or UCI and/or SR from the wireless device.
  • the UCI and/or SR comprises UCI and/or SR for the wireless device and/or at least one other cell in the first PUCCH cell group.
  • the method of embodiment 47 comprising, before receiving the message, receiving, from the wireless device, the UCI and/or SR for the first cell on a cell in the first PUCCH cell group.
  • the method of embodiment 52 wherein the first cell uses unlicensed spectrum.
  • the method of any of embodiments 34 to 53 wherein each cell in the first and second PUCCH cell groups is associated with a respective carrier. 55.
  • the method of any of embodiments 34 to 54 comprising receiving, from the wireless device, second UCI and/or SR for at least one cell in the second PUCCH cell group on the second cell.
  • the first PUCCH cell group comprises or includes one of a primary cell (PCell) and a secondary cell (SCell) for the wireless device
  • the second PUCCH cell group comprises or includes the other of the PCell and the SCell for the wireless device.
  • a wireless device comprising:
  • the base station comprising:
  • er equipment the UE comprising:
  • 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;
  • processing circuitry being configured to perform any of the steps of any of the Group A embodiments;
  • 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
  • a battery connected to the processing circuitry and configured to supply
  • mmunication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • the method of the previous embodiment further comprising, at the base station, transmitting the user data.
  • a user equipment 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.
  • a communication system including a host computer comprising:
  • a communication interface configured to forward user data to a cellular
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • 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,
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment further including the UE.
  • 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 processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data
  • 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.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: - at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the method of the previous embodiment further comprising, at the UE, providing the user data to the base station.
  • the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • 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.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A
  • the method of the previous embodiment further comprising at the base station, receiving the user data from the UE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon un exemple, l'invention concerne un procédé mis en œuvre par un dispositif sans fil. Le procédé consiste à transmettre des informations de commande en liaison montante, UCI, et/ou une demande de planification, SR, pour une première cellule dans un premier groupe de cellules de canal physique de commande en liaison montante, PUCCH, sur une seconde cellule dans un second groupe de cellules de PUCCH, le second groupe de cellules de PUCCH étant différent du premier groupe de cellules de PUCCH.
PCT/SE2020/050042 2019-02-13 2020-01-17 Transmission et réception d'informations de commande en liaison montante et/ou d'une demande de planification WO2020167196A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962804881P 2019-02-13 2019-02-13
US62/804,881 2019-02-13

Publications (1)

Publication Number Publication Date
WO2020167196A1 true WO2020167196A1 (fr) 2020-08-20

Family

ID=69467655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050042 WO2020167196A1 (fr) 2019-02-13 2020-01-17 Transmission et réception d'informations de commande en liaison montante et/ou d'une demande de planification

Country Status (1)

Country Link
WO (1) WO2020167196A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230054081A1 (en) * 2021-08-17 2023-02-23 Qualcomm Incorporated Support signaling for beam strength prediction

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170280440A1 (en) * 2016-03-22 2017-09-28 Samsung Electronics Co., Ltd. Method and apparatus for transmitting uplink control information in wireless communication system
US20170310531A1 (en) * 2016-04-25 2017-10-26 Ofinno Technologies, Llc Media Access Control Mechanism in a Wireless Device
US20180242357A1 (en) * 2015-09-10 2018-08-23 Nec Corporation Communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180242357A1 (en) * 2015-09-10 2018-08-23 Nec Corporation Communication system
US20170280440A1 (en) * 2016-03-22 2017-09-28 Samsung Electronics Co., Ltd. Method and apparatus for transmitting uplink control information in wireless communication system
US20170310531A1 (en) * 2016-04-25 2017-10-26 Ofinno Technologies, Llc Media Access Control Mechanism in a Wireless Device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Scheduling request for NR-U", vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, 2 November 2018 (2018-11-02), XP051481855, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F104/Docs/R2%2D1817974%2Ezip> [retrieved on 20181102] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230054081A1 (en) * 2021-08-17 2023-02-23 Qualcomm Incorporated Support signaling for beam strength prediction
US12074675B2 (en) * 2021-08-17 2024-08-27 Qualcomm Incorporated Support signaling for beam strength prediction

Similar Documents

Publication Publication Date Title
US11917694B2 (en) Random access procedure
US10965433B2 (en) Switching of bandwidth parts in wireless communication network
US20200196220A1 (en) Information Exchange for Initial User Equipment Access
US11974320B2 (en) Methods providing control signaling and related wireless devices and network nodes
US11696278B2 (en) Methods, apparatus and computer-readable media related to semi-persistent scheduling configuration
WO2019106536A1 (fr) Configuration de remise de compte rendu de mesure pour aider au tri de mesures de niveau de faisceau/cellule
US20220191966A1 (en) Extension of a discontinuous reception active time
US20220110161A1 (en) Two-step random access procedure
US11924874B2 (en) Enhanced channel occupancy sharing mechanism for random access and PUCCH in unlicensed spectrum
US12047996B2 (en) Scheduling information for transmission
US20220346157A1 (en) Configuration for Random Access Procedure
US20210044999A1 (en) Minimization of Driving Test Measurements
EP4014666A1 (fr) Signalisation de paramètres csma
WO2019215707A1 (fr) Message d&#39;accès aléatoire segmenté
US20220183061A1 (en) Transmitting and receiving an indication
EP4245012B1 (fr) Procedées et noeuds de réseau pour la calculation de l&#39;usage des bloques de resource physique
WO2020167196A1 (fr) Transmission et réception d&#39;informations de commande en liaison montante et/ou d&#39;une demande de planification
US20210058216A1 (en) Improved Reliability of DCI Decoding
US20230180221A1 (en) Prioritization for scheduling request and physical uplink shared channel without logical channel association
US20220061065A1 (en) Uplink transmissions using unlicensed frequency spectrum

Legal Events

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

Ref document number: 20703561

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20703561

Country of ref document: EP

Kind code of ref document: A1