Prioritizing transmissions by user equipment

Abstract

This application relates generally to prioritization of transmissions by a user equipment. This application relates to devices and components including apparatuses, systems, and methods for determining, by a user equipment (UE), a priority between a body proximity sensing (BPS) transmission and other transmissions (e.g., in frequency range 2 (FR2)).

Description

[0001] This application is a divisional application of the application with international application number PCT / CN2021 / 110830, international application date of August 5, 2021, entry into the Chinese national phase date of August 4, 2022, national application number 202180012900.6, and invention title "Prioritizing Transmissions by User Equipment". Background Technology

[0002] The 3GPP (3rd Generation Partnership Project) 5G New Radio (NR) provides communication between user equipment (UE) and a network (e.g., gNB or other base stations). Such communication may occupy frequency bands in frequency range 1 (FR1) (e.g., below 7.225 GHz), frequency range 2 (FR2) (e.g., 24.250 GHz and above, also known as mmWave), higher frequency ranges (e.g., between 52.6 GHz and 71 GHz or 114.25 GHz), and / or other frequency ranges. Attached Figure Description

[0003] Figure 1 A network environment according to some implementation schemes is shown.

[0004] Figure 2 An example of uplink (UL) gap configuration is shown, which can be provided to the UE by the gNodeB according to some implementation schemes.

[0005] Figure 3A An example is shown of prioritizing the transmission of scheduled UL signals by punching holes in the UL gap configuration, according to some implementation schemes.

[0006] Figure 3B An example is shown of prioritizing the transmission of scheduled UL signals by delaying UL gap time slots, according to some implementation schemes.

[0007] Figure 3C The prioritization of body proximity sensing (BPS) transmissions by discarding UL transmissions of signals scheduled for time slots in a UL gap configuration, according to some embodiments, is illustrated.

[0008] Figure 4 The operational flow / algorithm structure according to some implementation schemes is shown.

[0009] Figure 5 The operational flow / algorithm structure according to some implementation schemes is shown.

[0010] Figure 6 The operational flow / algorithm structure according to some implementation schemes is shown.

[0011] Figure 7 The operational flow / algorithm structure according to some implementation schemes is shown.

[0012] Figure 8 User equipment according to some implementation schemes is shown.

[0013] Figure 9 A base station according to some implementation schemes is shown. Detailed Implementation

[0014] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the embodiments. However, it will be apparent to those skilled in the art that various aspects of the embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B). For the purposes of this document, the phrase "A based on B" means "A is at least based on B".

[0015] The following is a glossary of terms that may be used in this disclosure.

[0016] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0017] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0018] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0019] As used herein, the term "user equipment" or "UE" refers to a device of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0020] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0021] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0023] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0024] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network devices, network nodes, virtualized network functions, etc.

[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or a data element that contains content. An information element may include one or more additional information elements. The term "obtain" is used to indicate any of its general meanings, such as calculation, derivation, receiving (e.g., from another element or device), and / or retrieval (e.g., from an array of storage elements).

[0027] A technique is described for the UE (e.g., in FR2) to determine the priority of body proximity sensing transmissions among other transmissions. Figure 1 A network environment 100 according to some embodiments is illustrated. Network environment 100 may include UEs 102, 104, and 106 and an access node (or “base station”) 108. Access node 108 may provide one or more radio access cells, such as 3GPP New Radio (NR) cells, through which one or more of UEs 102 / 104 / 106 may communicate with access node 108. In some aspects, access node 108 is a next-generation node B (gNB) providing one or more 3GPP New Radio (NR) cells. The air interfaces on which UE102 / 104 / 106 and access node 108 communicate are compatible with 3GPP technical specifications (TS), such as those defining the fifth-generation (5G) NR system standard, and can occupy frequency bands in frequency range 1 (FR1) (e.g., below 7.225 GHz), FR2 (e.g., 24.250 GHz and above, also known as mmWave) or higher frequency bands (e.g., between 52.6 GHz and 71 GHz or 114.25 GHz).

[0028] An access node (or "base station") 108, which may be a gNB, can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels to transport channels and mapping transport channels to physical channels. Logical channels can transmit data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH); the Physical Downlink Shared Channel (PDSCH); and the Physical Downlink Control Channel (PDCCH).

[0029] The PBCH can be used to broadcast system information that UE 102 / 104 / 106 can use for initial access to the serving cell. The PBCH can be transmitted together with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS) in the Synchronization Signal (SS) / PBCH block. The SS / PBCH block (SSB) can be used by UE 102 / 104 / 106 during the cell search process and for beam selection.

[0030] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (except for, for example, master information block (MIB)), and paging messages.

[0031] Access node 108 (e.g., a base station or gNB) can use PDCCH to transmit downlink control information (DCI) to UE 102 / 104 / 106. DCI provides uplink resource allocation on the Physical Uplink Shared Channel (PUSCH), downlink resource allocation on the PDSCH, and various other control information. DCI can also be used to provide uplink power control commands, configure timeslot formats, or indicate that preemption has occurred.

[0032] UE 102 / 104 / 106 can use the Physical Uplink Control Channel (PUCCH) to transmit uplink control information (UCI) to access node 108, which may include, for example, Hybrid Automatic Repeat Request (HARQ) acknowledgments, scheduling requests, or periodic and semi-persistent channel state information (CSI) reports.

[0033] It may be desirable to extend 5G NR to bands beyond those currently in use. For example, NR beyond 52.6 GHz up to 114.25 GHz could be considered. Frequencies between 52.6 GHz and 71 GHz are particularly interesting in the near term because they are close to below 52.6 GHz (current NR systems) and present emerging commercial opportunities for high data rate communications (e.g., unlicensed spectrum between 57 GHz and 71 GHz). 5G NR in unlicensed spectrum (NR-U) offers both licensed supplemental and standalone use of unlicensed spectrum.

[0034] To achieve such extensions, it may be desirable to utilize Frequency Range 2 (FR2) designs as much as possible. As used herein, FR2 can refer to a frequency range from 24.25 GHz to 52.6 GHz. For example, it may be beneficial to use aspects of existing waveforms (e.g., existing downlink (DL) / uplink (UL) NR waveforms) to support operation between 52.6 GHz and 71 GHz, and beyond, if feasible, to take advantage of such opportunities by minimizing specification burdens and required changes and maximizing the role of specific FR2-based implementations. Such aspects may include applicable sets of parameters, including subcarrier spacing (SCS), channel width (BW) (including maximum values), and their impact on the FR2 physical layer design to support system functionality that takes into account, for example, actual radio frequency (RF) attenuation; channel access mechanisms that assume beam-based operation to comply with specification requirements for unlicensed spectrum applicable between 52.6 GHz and 71 GHz, etc.

[0035] Further enhancements to FR2 coverage, signal quality, and / or UE performance may be desired. For example, improved power efficiency and / or overall system throughput may be desired. Some FR2 enhancements may involve operations that should be performed during runtime but may be incompatible with the transmission and / or reception of data or control signals (e.g., calibration and / or measurement operations). Due to unavoidable hardware sharing, various identified FR2 enhancements may rely on and benefit from periodic uplink (UL) gaps during which the UE can perform calibration and measurements (e.g., via the air interface and / or via the internal loop) without interrupting UL transmission / reception (Tx / Rx). Examples of such operations may include UE transmission (Tx) power management. For example, it may be desired for the UE to adaptively and efficiently adjust its output power to maximize UL coverage and / or throughput while maintaining regulatory compliance. Transmission power management may benefit from periodic monitoring of information from the surrounding environment (e.g., body proximity sensing or BPS).

[0036] Other self-calibration and / or monitoring operations are not excluded. At least some of the aforementioned self-calibration and monitoring mechanisms can be summarized into a basic scheme in which the UE sends and receives calibration signals via the air interface or via another internal loop between the Tx and Rx hardware. Since the hardware used for UL transmission is partially shared through self-calibration and monitoring, such operations can temporarily interrupt UL transmission. It may be desirable to minimize such interruptions by providing UE-specific and network-configured UL gaps during which the UE can perform operations for FR2 RF enhancement, such as calibration and / or measurements (e.g., transceiver calibration and Tx power management). The gNB does not expect to receive UL transmissions from the UE during UL gaps, and if the gNB does receive transmissions from the UE during UL gaps, it may ignore them as errors.

[0037] It may be expected that the UL gap configuration is UE-specific and network-configured (e.g., configured via Radio Resource Control (RRC) and / or Media Access Control-Control (MAC-CE) elements), specifying values ​​such as gap length, gap periodicity, and / or gap offset. In one example, gNB 108 may provide the UL gap configuration to UE 102 / 104 / 106 in an information element (e.g., ULGapConfig), which may be carried by an RRC message (e.g., an RRC reconfiguration message). The network may decide whether to provide the UL gap configuration to the UE.

[0038] The gNB 108 may provide UL gap configurations to UEs 102 / 104 / 106 in response to an event trigger request from the UE. Examples of such events may include an indication that the value of a monitored parameter has exceeded a specified threshold for that parameter. An example of such an indication could be that the UE detects that the temperature has risen above a specified threshold (e.g., indicating that the UE needs online calibration). Another example of such an event could be that the UE determines to perform Body Proximity Sensing (BPS). The UE can perform BPS sensing, for example, by having the transceiver transmit a signal (also known as a "BPS transmission") and then measuring the power of the reflected signal. BPS sensing can be used to estimate power management-maximum power reduction (P-MPR), and the UE's determination to perform BPS may occur in situations such as: 1) when the UE has a large amount of data to transmit, and / or 2) when the UE is at the cell edge and requires maximum transmission power for coverage. The gNB 108 may provide more than one UL gap configuration to UEs 102 / 104 / 106. UE 102 / 104 / 106 may indicate to gNB 108 its ability to perform BPS (e.g., via capability signaling).

[0039] Once the UL gap configuration is provided to the UE, it can be additionally activated or deactivated. For example, the gNB may be expected to activate and / or deactivate the UL gap configuration via MAC CE and / or DCI signaling. The UE may request activation of the UL gap configuration in response to a triggering event as described above (e.g., the UE detects that the temperature has risen above a specified threshold and the UE determines to perform BPS). Alternatively or otherwise, the gNB may implicitly activate the UL gap configuration in response to, for example, a Power Headroom (PHR) report from the UE (e.g., to minimize signaling).

[0040] Figure 2An example of a UL gap configuration for a network configuration that can be provided by gNB 108 to UE 102 / 104 / 106 according to some implementation schemes is shown. In this example, the UL / DL Time Division Duplex (TDD) configuration is DDDSU (e.g., as currently available in FR2 deployments). This TDD configuration includes three DL time slots (D), followed by a special time slot (S), followed by a UL time slot (U). The special time slot includes ten symbols for DL, followed by two symbols for the gap (e.g., for receive-transmit RF retuning), followed by two symbols for UL. The UL gap periodicity (e.g., as indicated in the UL gap configuration) may have values ​​such as 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, 320ms, or some other value. A typical UL gap periodicity (e.g., the length of one cycle of the UL gap configuration) may be, for example, 20ms. The UL gap duration (e.g., as indicated in the UL gap configuration) may have values ​​such as 62.5 µs, 125 µs, 250 µs, 500 µs, 1000 µs, or some other value. The UL gap length (e.g., as indicated in the UL gap configuration) may have values ​​such as one, two, four, or eight time slots, or some other value. It may be expected that the UL gap configuration includes values ​​for the UL gap duration (e.g., in microseconds) or values ​​for the UL gap length (e.g., in time slots). In this example, the gap length of the UL gap configuration is four time slots, and the four U time slots reconfigured by the UL gap configuration for the UL gap are outlined and labeled G. Figure 2 The document also indicates the UL time slot in which (e.g., on one or more OFDM symbols in that time slot) the periodic or semi-persistent (P / SP) configuration signal (e.g., as described below) is scheduled for transmission.

[0041] A conflict may occur if a BPS transmission is scheduled to occur in the same UL time slot as another UE transmission (e.g., a UL transmission). Figure 3A , Figure 3B and Figure 3C It shows Figure 2 The example shown illustrates such a conflict in an exemplary UL gap configuration. A relative priority can be established between BPS and UL transmissions (e.g., in one or more 3GPP specifications) to indicate which conflicting transmission should continue and which should be dropped. Such relative priority can be embodied, for example, in one or more priority rules.

[0042] UE 102 / 104 / 106 can apply different relative priorities between BPS and UL transmissions in different corresponding situations. For example, the relative priority to be applied may depend on the type of signal to be transmitted in the conflicting UL transmission. In one example, such signals can be broadly divided into two categories: periodic or semi-persistent (P / SP) configuration signals and dynamic configuration signals.

[0043] P / SP configuration signals may include UL symbols in any portion of the UL timeslot, and gNB 108 may provide configuration for P / SP configuration signals via, for example, RRC message transmission (e.g., in one or more information elements (IEs) within one or more RRC messages). Examples of P / SP configuration signals may include a scheduling request (SR), a beam fault recovery (BFR) signal on the PUCCH (PUCCH-BFR), a channel state indicator (CSI) signal for P / SP configuration on the PUCCH or PUSCH, a signal transmitted on the physical random access channel (PRACH), a probe reference signal (SRS) for P / SP configuration, a configuration grant (CG) signal on the PUSCH (CG-PUSCH), or a hybrid automatic repeat request acknowledgment (HARQ-ACK) for downlink semi-persistent scheduling (SPS) transmissions (e.g., on the PDSCH).

[0044] Several options for the priority rules between BPS transmissions and UL transmissions as P / SP configuration signals on static UL timeslots are now discussed. The term "static UL timeslot" indicates a timeslot that is configured as UL via RRC signaling and remains configured as UL until it is otherwise reconfigured via RRC signaling (e.g., a static UL timeslot is not otherwise reconfigured via DCI).

[0045] In the first option of the priority rule between BPS transmissions and UL transmissions as P / SP configuration signals on static UL time slots, the network schedules UL transmissions of P / SP configuration signals to avoid placing such transmissions in time slots that are configured or can be configured for UL time slots. However, such scheduling is difficult to implement for all UL time slots carrying P / SP configuration signals because the number of P / SP configuration signals is typically too large to accommodate such scheduling.

[0046] The second option of the priority rule between BPS transmission and UL transmission as a P / SP configuration signal on a static UL timeslot is to prioritize the transmission of the P / SP configuration signal. In a first example of this option, UE 102 / 104 / 106 can prioritize the transmission of the P / SP configuration signal by punching UL gap configuration. Figure 3AAn example of prioritizing the transmission of P / SP configuration signals by punching holes in the UL gap configuration is shown according to some embodiments. In this example, the UL gap time slots for which priority is given to UL transmissions instead of BPS transmissions are indicated by being crossed out.

[0047] In a second example of the option to prioritize the transmission of P / SP configuration signals, UE 102 / 104 / 106 can prioritize the transmission of P / SP configuration signals by delaying UL gap time slots. In this case, it may be desirable that UL time slots with periodicity and SP transmissions (e.g., CQI, SRS) are not considered static UL time slots. Due to the number of UL signals that can be configured in the UL channel, it is possible that at least one opportunity for the transmission of P / SP configuration signals has already been scheduled for each static UL time slot. It may be desirable to apply this second example only to the selected P / SP configuration signals. In this case, it may be desirable to apply another relative priority to other P / SP configuration signals (e.g., as described below). Figure 3B An example of prioritizing the transmission of P / SP configuration signals by delaying UL gap time slots, according to some implementation schemes, is shown. Such rules can be implemented to allow the UE to delay UL gap time slots to occur outside the UL gap configuration's gap length. Figure 3B In the example shown, the priority ordering of the P / SP configuration signal continues outside the UL gap configuration, and the two delayed gap slots occur two and four UL slots after the last slot of the UL gap configuration, respectively.

[0048] A third option of the priority rule between BPS transmissions and UL transmissions as P / SP configuration signals on static UL time slots is to prioritize BPS transmissions. UE 102 / 104 / 106 may prioritize BPS transmissions, for example, by discarding UL transmissions of P / SP configuration signals scheduled for time slots where conflicts occur. Figure 3C The diagram illustrates prioritizing BPS transmissions according to some implementations by discarding P / SP configuration signals (indicated by being crossed out) for time slot scheduling in UL gap configurations.

[0049] It may be desirable for the UE to apply more than one relative priority between BPS transmissions and UL transmissions as P / SP configuration signals. The relative priority to be applied to a particular conflict can be based on, for example, the type of P / SP configuration signal scheduled for transmissions within UL gap slots. In one such example, when the P / SP configuration signal is PUCCH-BFR, the rule applied (e.g., by UE 102 / 104 / 106) for prioritizing the transmission of the P / SP configuration signal by puncturing the UL gap configuration (e.g., as referenced above) is used. Figure 3A (as described above); when the P / SP configuration signal is a HARQ-ACK for DL ​​SPS transmission, a rule for prioritizing the transmission of the P / SP configuration signal by delaying the UL gap time slot is applied (e.g., as referenced above). Figure 3B The above-mentioned rules apply to other P / SP configuration signals to prioritize BPS transmissions (e.g., as mentioned above). Figure 3C Other options in the relative priorities described above can also be implemented (e.g., based on the type of P / SP configuration signal scheduled for transmission in UL gap time slots).

[0050] The P configuration for a signal remains active until the signal is reconfigured (e.g., via RRC signaling). For the SP configuration of a signal, the timing at which the UE 102 / 104 / 106 receiving the configuration applies the SP configuration can vary depending on how the configuration is activated (also known as “triggered”). For example, the SP configuration for a signal such as a Type 2 CG-PUSCH or a HARQ-ACK for an SPS-PDSCH can be triggered by a DCI message. In this case, the UE can apply the SP configuration of the signal immediately after successful DCI decoding (e.g., typically within one time slot). The SP configuration for a signal such as an SP-CSI report on a PUCCH can be triggered by a MAC CE. In this case, the UE can apply the SP configuration of the signal according to a timeline such as the following (e.g., as described in Clause 5.2.1.5.2 of 3GPP TS38.214, “Physical layer procedures for data,” v16.5.0 (2021-04)): "When the UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, it should start from slot n+3N." 子帧，µ The indicated semi-persistent reporting settings are applied starting from the first time slot thereafter, where µ is the SCS configuration of PUCCH.

[0051] For example, the UE can transmit an ACK for the PDSCH carrying a MAC CE, and three milliseconds after the last symbol of the ACK is transmitted, the UE can apply the SP configuration of the signal. For the P / SP configuration signals discussed herein (e.g., Type 2 CG-PUSCH, HARQ-ACK for SPS-PDSCH, SP-CSI report on PUCCH), it may be expected that the UE will use the configuration discussed above (e.g., refer to...). Figure 3B The UL gap time slot is delayed to prioritize the transmission of P / SP configuration signals.

[0052] As per the above reference Figure 3CThe discussion may involve UE 102 / 104 / 106 prioritizing BPS transmissions over at least some types of P / SP configuration signals by discarding UL transmissions of P / SP configuration signals scheduled for slotting in the UL gap configuration. In one example, UE 102 / 104 / 106 applies such priority rules in the next cycle of the UL gap configuration after its activation (e.g., from the start of the next UL gap cycle). In another example, the timing of UE 102 / 104 / 106 applying such priority rules may vary depending on, for example, how the UL gap configuration is activated. For instance, if the UL gap configuration is activated by MAC CE, UE 102 / 104 / 106 may apply the UL gap configuration (and the rules for prioritizing BPS transmissions) three milliseconds after the last symbol of the ACK transmission of the PDSCH carrying the MAC CE. Alternatively, if the UL gap configuration is activated by DCI signaling, UE 102 / 104 / 106 may apply the UL gap configuration (and the rules for prioritizing BPS transmissions) immediately after successful DCI decoding.

[0053] Another type of relative priority between BPS and UL transmissions can be applied to UL transmissions as dynamic scheduling signals. The gNB 108 can provide configuration for dynamic scheduling signals via, for example, DCI or MAC CE signaling. Examples of dynamic scheduling signals may include a Dynamic Grant (DG) signal on the PUSCH (DG-PUSCH), an Aperiodic CSI (A-CSI) signal on the PUSCH, an Aperiodic SRS (A-SRS), or a HARQ-ACK for a DG signal on the PDSCH.

[0054] We will now discuss several options for priority rules between BPS transmissions and UL transmissions as dynamic scheduling signals. The first option for priority rules between BPS transmissions and UL transmissions as dynamic scheduling signals is to prioritize BPS transmissions. For example, the network scheduler can apply such priority rules by avoiding issuing dynamic grants for scheduling PUSCH transmissions, AP-CSI, A-SRS, or HARQ ACKs in UL gap time slots configured in UL gaps, and the UE can apply such priority rules by ignoring any such dynamic grants it receives from the gNB as errors.

[0055] A second option for the priority rule between BPS transmissions and UL transmissions as dynamic scheduling signals is to prioritize certain dynamic scheduling signals. For example, gNB 108 may issue dynamic authorization to UE 102 / 104 / 106 for type 3 HARQ feedback signals (e.g., type 3 HARQ codebook feedback). It may be desirable to prioritize type 3 HARQ feedback signals over conflicting BPS transmissions because type 3 HARQ feedback can carry important HARQ ACKs for multiple DL HARQ procedures. For example, gNB may request type 3 HARQ feedback signals to poll the UE for all existing HARQ-ACK feedbacks, regardless of the HARQ-ACK timeline.

[0056] Figures 4 to 7 Several operational flows / algorithm structures according to various aspects of this disclosure are illustrated. These operational flows / algorithm structures describe multiple operations within a specific sequence. However, the sequences shown are not limiting. That is, these operations can be performed in sequences other than those specifically shown.

[0057] Figure 4 An operational flow / algorithm structure 400 according to some implementation schemes is shown. The operational flow / algorithm structure 400 may be executed or implemented by a UE such as, for example, UE 102, 104, 106 or 800; or by components such as baseband processor 804A.

[0058] The operation flow / algorithm structure 400 may include, at block 404, an application indicating the uplink gap configuration of multiple uplink gap time slots.

[0059] The operation flow / algorithm structure 400 may include, at block 408, obtaining first scheduling information indicating a signal to be transmitted during a first uplink gap time slot among a plurality of uplink gap time slots.

[0060] The operation flow / algorithm structure 400 may include, at block 412, determining the relative priorities of performing BPS transmission during the first uplink gap time slot and transmitting signals in the first uplink gap time slot.

[0061] Operational flow / algorithm structure 400 may include, at block 416, discarding or transmitting signals based on relative priority. Structure 400 may include, for example, determining that the signal indicated by the first scheduling information is an SRS, and, based on the determined relative priority, prioritizing the execution of BPS transmission over the transmission of the SRS, discarding the SRS and performing BPS transmission during the first uplink gap time slot. Alternatively, structure 400 may include determining that the signal indicated by the first scheduling information is a Channel Quality Indicator (CQI) signal, and, based on the determined relative priority, prioritizing the execution of BPS transmission over the transmission of the CQI signal, discarding the CQI signal and performing BPS transmission during the first uplink gap time slot.

[0062] Figure 5 An operational flow / algorithm structure 500 according to some implementation schemes is shown. The operational flow / algorithm structure 500 may be executed or implemented by a UE such as, for example, UE 102, 104, 106 or 800; or by a component thereof such as a baseband processor 804A.

[0063] The operation flow / algorithm structure 500 may include blocks 504, 508, 512, and 516, which may be similar to those in the reference above. Figure 4 Blocks 404, 408, 412, and 416 are mentioned above. The operation flow / algorithm structure 500 may include, at block 520, obtaining second scheduling information indicating a signal to be transmitted during a second uplink gap time slot among a plurality of uplink gap time slots.

[0064] The operation flow / algorithm structure 500 may include, at block 524, determining a second relative priority for performing BPS transmission during the second uplink gap time slot and for transmitting signals in the second uplink gap time slot.

[0065] Operational flow / algorithm structure 500 may include, at block 528, discarding or transmitting a second signal based on a second relative priority. Structure 500 may include, for example, determining that the second signal indicated by second scheduling information is a BFR signal to be transmitted on the PUCCH, and, based on the determined second relative priority, prioritizing the transmission of the BFR signal over performing BPS transmission, transmitting the BFR signal during the second uplink gap time slot. Alternatively, structure 500 may include determining that the signal indicated by the second scheduling information is a HARQ-ACK for DL ​​SPS transmission, and, based on the determined second relative priority, prioritizing the transmission of the HARQ-ACK over performing BPS transmission, transmitting the HARQ-ACK during the second uplink gap time slot. Structure 900 may include, based on the second relative priority, delaying the second uplink gap time slot.

[0066] Figure 6An operational flow / algorithm structure 600 according to some implementation schemes is shown. The operational flow / algorithm structure 600 may be executed or implemented by a UE such as, for example, UE 102, 104, 106 or 800; or by components thereof such as baseband processor 804A.

[0067] Operation flow / algorithm structure 600 may include, at block 604, receiving an uplink gap configuration indicating multiple uplink gap time slots. Block 604 may include, for example, receiving the uplink gap configuration in an RRC message (e.g., in one or more RRC IEs).

[0068] The operation flow / algorithm structure 600 may include, at block 608, receiving a command to activate the uplink gap configuration. The uplink gap configuration may include an uplink gap periodicity, and structure 600 may also include applying the uplink gap configuration starting from the next uplink gap periodicity after receiving the activation command.

[0069] Box 608 may include receiving an activation command in a DCI message. In this case, structure 600 may include applying uplink gap configuration immediately after decoding the DCI message. Alternatively, box 608 may include receiving an activation command in a MAC CE. In this case, structure 600 may include transmitting an ACK carrying the PDSCH of the MAC CE, and applying the uplink gap configuration three milliseconds after the last symbol of the ACK transmission.

[0070] The operation flow / algorithm structure 600 may include, at block 612, receiving first scheduling information indicating a signal to be transmitted during a first uplink gap time slot among a plurality of uplink gap time slots.

[0071] Box 612 may include receiving first scheduling information in a DCI message. In this case, structure 600 may include applying the first scheduling information immediately after decoding the DCI message. The first scheduling information may indicate, for example, that the signal to be transmitted is a HARQ-ACK for DLSPS transmission. Alternatively, the first scheduling information may indicate that the signal to be transmitted is a type 2 CG transmission on a PUSCH.

[0072] Alternatively, block 612 may include receiving first scheduling information in the MAC CE. In this case, structure 600 may include transmitting an ACK carrying the PDSCH of the MAC CE, and applying the first scheduling information three milliseconds after the last symbol of the ACK transmission. The first scheduling information may indicate, for example, that the signal to be transmitted is an SP-CSI report on the PUCCH.

[0073] Operation flow / algorithm structure 600 may include, at block 616, determining the relative priority of performing BPS transmission during the first uplink gap time slot and transmitting signals within the first uplink gap time slot. Operation flow / algorithm structure 600 may include, at block 620, transmitting signals based on the relative priority during the first uplink gap time slot.

[0074] Figure 7 An operational flow / algorithm structure 700 according to some implementation schemes is shown. The operational flow / algorithm structure 700 may be executed or implemented by a base station such as base station 108 or 900 or its components such as baseband processor 904A.

[0075] The operation flow / algorithm structure 700 may include, at block 704, sending an uplink gap configuration indicating multiple uplink gap time slots to the UE.

[0076] Operation flow / algorithm structure 700 may include, at block 708, sending a command to the UE to activate uplink gap configuration. Structure 900 may include receiving a request to activate uplink gap configuration, wherein the command is sent based on the request.

[0077] Operation flow / algorithm structure 700 may include, at block 712, after sending a command, sending to the UE a dynamic grant indicating a signal to be transmitted during an uplink gap time slot among multiple uplink gap time slots. Sending the dynamic grant may be determined based on the relative priority of performing BPS transmission during the uplink gap time slot and transmitting the signal in the uplink gap time slot, such that transmitting the signal takes precedence over performing BPS transmission. Block 712 may include, for example, sending the dynamic grant in a DCI message. The dynamic grant may indicate that the signal to be transmitted is a Type 3 HARQ feedback signal. The uplink gap time slot may be, for example, a static uplink time slot.

[0078] Figure 8 A UE 800 according to some implementation schemes is shown. The UE 800 may be similar to... Figure 1 UE 102, 104 or 106 and are basically interchangeable with them.

[0079] UE 800 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

[0080] UE 800 may include a processor 804, RF interface circuitry 808, memory / storage device 812, user interface 816, sensor 820, drive circuitry 822, power management integrated circuit (PMIC) 824, antenna structure 826, and battery 828. Components of UE 800 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 8 The block diagram is intended to show a high-level view of some of the components of the UE 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0081] The components of UE 800 can be coupled to various other components via one or more interconnects 832, which can represent any type of interface, input / output, bus (local, system, or extension), transmit line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0082] Processor 804 may include processor circuitry such as baseband processor circuitry (BB) 804A, central processing unit circuitry (CPU) 804B, and graphics processing unit circuitry (GPU) 804C. Processor 804 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage device 812, to cause UE 800 to perform the operations described herein.

[0083] In some implementations, the baseband processor circuit 804A can access the communication protocol stack 836 in the memory / storage device 812 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 804A can access the communication protocol stack to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 808.

[0084] The baseband processor circuit 804A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (“CP-OFDM”) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (“DFT-S-OFDM”) in the uplink.

[0085] Memory / storage device 812 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 836) that can be executed by one or more processors in processor 804 to cause UE 800 to perform the various operations described herein. Memory / storage device 812 includes any type of volatile or non-volatile memory that can be distributed throughout UE 800. In some embodiments, some memory / storage devices 812 may be located on processor 804 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 812 may be located external to processor 804 but accessible via a memory interface. Memory / storage device 812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0086] The RF interface circuit 808 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 800 to communicate with other devices via a radio access network. The RF interface circuit 808 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0087] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 826 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 804.

[0088] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 826.

[0089] In various implementations, the RF interface circuit 808 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0090] Antenna 826 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 826 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 826 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 826 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0091] User interface circuitry 816 includes various input / output (I / O) devices designed to enable users to interact with UE 800. User interface circuitry 816 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes "LEDs") and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 800.

[0092] Sensor 820 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0093] The driving circuit 822 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 800. The driving circuit 822 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 800. For example, the driving circuit 822 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of sensor circuit 820 and controlling and allowing access to sensor circuit 820; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0094] The PMIC 824 manages the power supplied to various components of the UE 800. Specifically, relative to the processor 804, the PMIC 824 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0095] In some implementations, the PMIC 824 may control or otherwise become part of various power-saving mechanisms of the UE 800, including DRX, as discussed herein.

[0096] Battery 828 can power UE 800, but in some examples, UE 800 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 828 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 828 may be a typical lead-acid automotive battery.

[0097] Figure 9 An access node 900 (e.g., a base station or gNB) according to some implementations is shown. Access node 900 may be similar to and substantially interchangeable with access node 108.

[0098] Access node 900 may include processor 904, RF interface circuit 908, core network (CN) interface circuit 912, memory / storage device circuit 916, and antenna structure 926.

[0099] The components of access node 900 can be coupled to various other components via one or more interconnectors 928.

[0100] The processor 904, RF interface circuit 908, memory / storage device circuit 916 (including communication protocol stack 910), antenna structure 926, and interconnect 928 are similar to those in the reference. Figure 8 Similar named elements are shown and described.

[0101] The CN interface circuit 912 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol such as Carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from access node 900 via fiber optic or wireless backhaul. The CN interface circuit 912 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 912 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0102] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0103] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0104] Example Further exemplary implementations are provided in the following sections.

[0105] Example 1 includes one or more computer-readable media having instructions that, when executed by one or more processors, cause a UE application to indicate an uplink gap configuration of a plurality of uplink gap time slots; obtain first scheduling information indicating a signal to be transmitted during a first uplink gap time slot among the plurality of uplink gap time slots; determine a relative priority for performing BPS transmission in the first uplink gap time slot and for transmitting the signal in the first uplink gap time slot; and discard or transmit the signal based on the relative priority.

[0106] Example 2 includes one or more computer-readable media according to Example 1 or some other embodiments herein, wherein the instructions, when executed by the one or more processors, further cause the UE to determine that the signal indicated by the first scheduling information is an SRS; and based on determining the relative priority, to prioritize the execution of the BPS transmission over the transmission of the SRS, discard the SRS and execute the BPS transmission during the first uplink gap time slot.

[0107] Example 3 includes one or more computer-readable media according to Example 1 or some other embodiments herein, wherein the instructions, when executed by the one or more processors, further cause the UE to determine that the signal indicated by the first scheduling information is a CQI signal; and based on determining the relative priority, to prioritize performing the BPS transmission over transmitting the CQI signal, discard the CQI signal and perform the BPS transmission during the first uplink gap time slot.

[0108] Example 4 includes one or more computer-readable media according to Example 1 or some other embodiments herein, wherein the instructions, when executed by the one or more processors, further cause the UE to obtain second scheduling information indicating a second signal to be transmitted during a second uplink gap time slot in the plurality of uplink gap time slots; and to determine a second relative priority for performing BPS transmission during the second uplink gap time slot and for transmitting the second signal in the second uplink gap time slot; and to discard or transmit the second signal based on the second relative priority.

[0109] Example 5 includes one or more computer-readable media according to Example 4 or some other embodiments herein, wherein the instructions, when executed by the one or more processors, further cause the UE to determine that the second signal indicated by the second scheduling information is a BFR signal to be transmitted on the PUCCH; and, based on determining the second relative priority, to prioritize the transmission of the BFR signal over the execution of the BPS transmission, and to transmit the BFR signal during the second uplink gap time slot.

[0110] Example 6 includes one or more computer-readable media according to Example 4 or some other embodiments herein, wherein the instructions, when executed by the one or more processors, further cause the UE to determine that the second signal indicated by the second scheduling information is a HARQ-ACK for DL ​​SPS transmission; and to transmit the HARQ ACK during the second uplink gap time slot based on determining the second relative priority, prioritizing the transmission of the HARQ ACK over the execution of the BPS transmission.

[0111] Example 7 includes one or more computer-readable media according to Example 4 or some other embodiments herein, wherein the instructions, when executed by the one or more processors, also cause the UE to postpone the second uplink gap time slot based on the second relative priority.

[0112] Example 8 includes a UE, the UE including processing circuitry configured to: receive an uplink gap configuration indicating a plurality of uplink gap time slots; receive a command to activate the uplink gap configuration; receive first scheduling information indicating a signal to be transmitted during a first uplink gap time slot among the plurality of uplink gap time slots; determine a relative priority between performing BPS transmission during the first uplink gap time slot and transmitting the signal during the first uplink gap time slot; and transmit the signal during the first uplink gap time slot based on the relative priority. The UE may further include a memory coupled to the processing circuitry, the memory being used to store the uplink gap configuration.

[0113] Example 13 includes a UE according to Example 8 or some other embodiments herein, wherein the processing circuitry is further configured to receive the activation command in a MAC CE.

[0114] Example 14 includes a UE according to Example 13 or some other embodiments herein, wherein the processing circuitry is further configured to transmit an ACK for the PDSCH carrying the MAC CE; and to apply the uplink gap configuration three milliseconds after transmitting the last symbol of the ACK.

[0115] Example 15 includes a UE according to Example 8 or some other embodiments herein, wherein the processing circuitry is further configured to receive the first scheduling information in a DCI message; and to apply the first scheduling information immediately after decoding the DCI message.

[0116] Example 16 includes a UE according to Example 15 or some other embodiments herein, wherein the first scheduling information indicates that the signal to be transmitted is a HARQ-ACK for DL ​​SPS transmission.

[0117] Example 17 includes a UE according to Example 15 or some other embodiments herein, wherein the first scheduling information indicates that the signal to be transmitted is a type 2 CG transmission on a PUSCH.

[0118] Example 18 includes a UE according to Example 8 or some other embodiments herein, wherein the processing circuitry is further configured to receive the first scheduling information in a MAC CE; transmit an ACK carrying the PDSCH of the MAC CE; and apply the first scheduling information three milliseconds after transmitting the last symbol of the ACK.

[0119] Example 19 includes a UE according to Example 18 or some other embodiments herein, wherein the first scheduling information indicates that the signal to be transmitted is an SP-CSI report on the PUCCH.

[0120] Example 20 includes a method of operating a base station, the method comprising: sending an uplink gap configuration indicating a plurality of uplink gap time slots to a UE; sending a command to the UE to activate the uplink gap configuration; and, after sending the command, sending a dynamic grant to the UE indicating a signal to be transmitted during an uplink gap time slot in the plurality of uplink gap time slots, wherein sending the dynamic grant is based on determining the relative priority of performing BPS transmission during the uplink gap time slot and transmitting the signal in the uplink gap time slot, such that transmitting the signal takes precedence over performing the BPS transmission.

[0121] Example 21 includes the method according to Example 20 or some other embodiments herein, wherein the method further includes receiving a request to activate the uplink gap configuration, wherein the command is sent based on the request.

[0122] Example 22 includes the method according to Example 20 or some other embodiments herein, wherein the method further includes sending the dynamic authorization in a DCI message.

[0123] Example 23 includes the method according to Example 20 or some other embodiments herein, wherein the dynamic authorization indicates that the signal to be transmitted is a type 3 HARQ feedback signal.

[0124] Example 24 includes the method according to Example 20 or some other embodiments herein, wherein the uplink gap time slot is a static uplink time slot.

[0125] Example 25 includes the method according to Example 20 or some other embodiments herein, wherein the method further includes configuring a second dynamic grant, the second dynamic grant indicating a second signal to be transmitted by the UE during an uplink time slot not in any of the plurality of uplink gap time slots; and sending the second dynamic grant to the UE after sending the command.

[0126] Example 26 includes the method described according to Example 25 or some other embodiments herein, wherein the second signal is data transmission on the PUSCH, an AP-CSI signal, an A-SRS, or a HARQ-ACK.

[0127] Example 27 includes the method according to Example 25 or some other embodiments herein, wherein sending the second dynamic authorization is based on determining a second relative priority that prioritizes performing the BPS transmission over transmitting the second signal.

[0128] Example 28 may include an apparatus comprising means for performing one or more elements of the method described or associated with any of Examples 1 to 27 or any other method or process described herein.

[0129] Example 29 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein as described or associated with any of Examples 1 to 27.

[0130] Example 30 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the method described or associated with any of Examples 1 to 27 or any other method or process described herein.

[0131] Example 31 may include a method, technique, or process, or a part or component thereof, described or associated with any of Examples 1 to 27.

[0132] Example 32 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform, or in part, the methods, techniques or processes described or associated with any of Examples 1 to 27.

[0133] Example 33 may include a signal, or a portion thereof, described or associated with any of Examples 1 to 27.

[0134] Example 34 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or otherwise in this disclosure, according to any of Examples 1 to 27.

[0135] Example 35 may include a signal encoded with data according to or associated with any of Examples 1 to 27, or a portion or component thereof, or otherwise described in this disclosure.

[0136] Example 36 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1 to 27, or otherwise described in this disclosure.

[0137] Example 37 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 27.

[0138] Embodiment 38 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any of Embodiments 1 to 27.

[0139] Example 39 may include signals in a wireless network as shown and described herein.

[0140] Example 40 may include methods for communicating in a wireless network as shown and described herein.

[0141] Example 41 may include a system for providing wireless communication as shown and described herein.

[0142] Example 42 may include devices for providing wireless communication as shown and described herein.

[0143] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0144] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method, the method comprising: Determine that multiple types of information can be transmitted in the uplink (UL) gaps of serving cells configured for frequencies above 24.25 GHz; The identified signal includes a Channel State Information (CSI) report; It is determined that the CSI report is included in the various types of information; as well as The signal is generated to be transmitted in the serving cell during the UL gap, based at least in part on the fact that the CSI report is included in the various types of information.

2. The method of claim 1, wherein the signal is scheduled to be transmitted on a UL shared channel to obtain authorization.

3. The method of claim 2, wherein the UL shared channel includes the Physical Uplink Shared Channel (PUSCH).

4. The method according to any one of claims 1 to 3, further comprising punching a UL gap time slot in the UL gap to transmit the signal.

5. The method according to any one of claims 1 to 3, further comprising: Determine the relative priority of performing body proximity sensing (BPS) transmissions during the UL gap time slot of the UL gap; as well as The signal transmission is permitted during the UL gap, at least in part, based on the relative priority.

6. The method according to any one of claims 1 to 3, wherein the CSI report comprises a semi-periodic (SP)-CSI report.

7. The method according to any one of claims 1 to 3, wherein the signal is dynamically scheduled to be transmitted during the UL gap.

8. The method according to any one of claims 1 to 3, further comprising: Receive a Media Access Control (MAC) control element (CE) that includes scheduling information, wherein the scheduling information indicates that the signal includes the CSI report.

9. An apparatus for: Determine that multiple types of information can be transmitted in the uplink (UL) gaps of serving cells configured for frequencies above 24.25 GHz; The identified signal includes a Channel State Information (CSI) report; It is determined that the CSI report is included in the various types of information; as well as The signal is generated to be transmitted in the serving cell during the UL gap, based at least in part on the fact that the CSI report is included in the various types of information.

10. The apparatus of claim 9, wherein the signal is scheduled to be transmitted on a UL shared channel to obtain authorization.

11. The apparatus of claim 10, wherein the UL shared channel includes a Physical Uplink Shared Channel (PUSCH).

12. The apparatus according to any one of claims 9 to 11, wherein the apparatus is further configured to: The UL gap time slot is punched to transmit the signal.

13. The apparatus according to any one of claims 9 to 11, wherein the apparatus is further configured to: Determine the relative priority of performing body proximity sensing (BPS) transmissions during the UL gap time slot of the UL gap; and The signal transmission is permitted during the UL gap, at least in part, based on the relative priority.

14. The apparatus according to any one of claims 9 to 11, wherein the CSI report comprises a semi-periodic (SP)-CSI report.

15. The apparatus according to any one of claims 9 to 11, wherein the signal is dynamically scheduled to be transmitted during the UL gap.

16. A method, the method comprising: Generate an uplink (UL) gap configuration indicating one or more UL gap time slots for transmission (Tx) power management and frequency range 2 (FR2) operation, the UL gap configuration being transmitted to the device, the UL gap configuration being configured for serving cells in a frequency range above 24.25 GHz; The determination signal includes a Channel State Information (CSI) report, which is included in a variety of information permitted to be transmitted within the UL gap; and At least in part, based on the fact that the CSI report is included in the various types of information, an authorization is generated for the signal to be transmitted in the serving cell during the uplink gap defined by the UL gap configured by the UL gap configuration, the authorization being used for transmission to the device.

17. The method of claim 16, wherein the method further comprises: The signal is received from the device during the UL gap; as well as Process the signal.

18. The method of claim 16 or claim 17, wherein the authorization is used to transmit the signal via a UL shared channel.

19. The method of claim 18, wherein the UL shared channel includes the Physical Uplink Shared Channel (PUSCH).

20. The method of claim 16 or claim 17, wherein the authorization is generated at least in part based on the determination that the relative priority of performing body proximity sensing (BPS) transmission during the UL gap and transmitting the signal in the UL gap is such that transmitting the signal takes precedence over performing the BPS transmission.

Images